[Bug]: Checksum check failing for OpenSearch

Describe the bug
OpenSearch Dashboards out-of-the-box experience downloads a snapshot of OpenSearch to start up and run some integration tests and functional tests. However, there is logic before starting OpenSearch artifact automatically downloaded to verify the checksum. Today, I started noticing that this logic fails when attempting to run integration tests locally:
artifact downloaded from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz does not match expected checksum
      expected: a5083ba0bcb0fa5aec8011171af440ed12c8587823f178190ad59032d94988a9656676140ff7b7e736cc8b9b197ee00e4f518871336e92a0917778c553fc4a71
      received:<PHONE_NUMBER>a9456373a7d5af958f19d7658bf5edd61c4537399651bb4e43dd690688e2f95cd3d330f5dbbe829ef0403a1d46762969affb2b75a95ad90e847493

It also causes the jenkins test run to fail.
Related to #1497
To reproduce
To reproduce:
Ensure no running version of OpenSearch
unset TEST_OPENSEARCH_FROM
git checkout main
yarn osd bootstrap
yarn test:jest_integration

Notice failure in integration tests.
Expected behavior
Integration tests work out of the box and thus the CI will succeed. Developers should be able to run yarn test:jest_integration without setting TEST_OPENSEARCH_FROM
Screenshots
No response
Host / Environment

Local ubuntu
Jenkins

Additional context
No response
Relevant log output
artifact downloaded from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz does not match expected checksum
      expected: a5083ba0bcb0fa5aec8011171af440ed12c8587823f178190ad59032d94988a9656676140ff7b7e736cc8b9b197ee00e4f518871336e92a0917778c553fc4a71
      received:<PHONE_NUMBER>a9456373a7d5af958f19d7658bf5edd61c4537399651bb4e43dd690688e2f95cd3d330f5dbbe829ef0403a1d46762969affb2b75a95ad90e847493

We havent even start 3.0 building process, the auto pipeline run is either not producing a working tarball or it is failing.
We are focusing on 2.0.0 GA release for now.

We may have a problem here (or two).

Whatever automation is downloading the .tar.gz should not be trying to download 3.0, even though it's already being built. The next major is 2.0.
The checksum not matching would be a surprise, but I don't know whether we're signing -SNAPSHOT builds at all?

You should download from ci.opensearch.org not artifacts.opensearch.org, we havent use the old pipeline for years, even though we are still updating /snapshots it depends on we have a good build on dev jenkins, and you didnt show us which checksum you are comparing against the tarball.
@dblock there is no signing at all for any staging, we are here talking about the checksum.

Thanks.

@joshuarrrr Please let us know if ^ doesn't help?

@joshuarrrr  Can you please check the above comments and confirm?

In dashboards, the artifact URL was set to artifacts.opensearch.org in this PR: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/466
I'll check with the team, but we may need further guidance on how to update the various scripts that reference that base path.

We can update the reference we might run into the caching issue again with the checksum. With the new reference do we know if the checksum cache buster is more aggressive than the "deprecated" reference?

ci.opensearch.org bust every 10min or something or even shorter.
artifacts.opensearch.org bust every 24hrs because that is production.

@joshuarrrr Do you need any additional details?

@bbarani,
Yes will be prioritizing this in our repo. However, looking at the bucket and the code I'm not able to figure out where an example OpenSearch Snapshot. Do you or @peterzhuamazon have an example?
Thanks!

You should be able to get the updated snapshot -min artifact from https://artifacts.opensearch.org/snapshots/core/opensearch/3.0.0-SNAPSHOT/opensearch-min-3.0.0-SNAPSHOT-linux-x64-latest.tar.gz

Hey @joshuarrrr can you please add some updates, if you are still having any issue?
Thank you

We suggest using the ci.opensearch.org repo instead of the artifacts.opensearch.org repo.
Sample: https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.1.0/latest/linux/x64/tar/builds/opensearch/dist/opensearch-min-2.1.0-linux-x64.tar.gz
The latest url is also existing there.

Sounds good! Thank you!

We will keep this open for now as we have these notes:

For Dashboards, depends on how the implementation is, could directly pull the artifacts from ci.opensearch.org instead of artifacts.opensearch.org.
For OpenSearch, the distribution downloader (?) function that every other plugin uses during their integration, is hardcoded to artifacts.opensearch.org, we need to first switch in the core repo to point to ci.opensearch.org then the downstream can consume that change.
This means we might need to add sha512 to every artifacts in ci.opensearch.org, as both opensearch and dashboards are using the checksum to verify the downloads (confirmed on dashboards part at least).

@saratvemulapalli How hard is to make the base URL dynamic in distribution downloader?

Hi @bbarani @prudhvigodithi I just find the old PRs we worked on for this particular case with @mch2.
https://github.com/opensearch-project/OpenSearch/pull/904
As you can see there are two places you need to change.

Change the snapshot ivy repo to ci.opensearch.org
Change the path of snapshot to whatever path leads to the artifacts on ci.opensearch.org.

Additional concerns:

Do we need to build new artifacts particularly with --snapshot param or does the distribution downloader plugin can natively taking artifacts built without --snapshot while still considering it as a snapshot artifact.

Thanks.

@saratvemulapalli How hard is to make the base URL dynamic in distribution downloader?

@bbarani  It is some effort. But its already done :)
See documentation[1], users can use PcustomDistributionUrl to override the url dynamically.
[1] https://github.com/opensearch-project/opensearch-plugins/blob/main/TESTING.md#distribution-download-plugin

@saratvemulapalli It looks like the plugin teams prefer to modify it without using PcustomDistributionUrl parameter
https://github.com/opensearch-project/opensearch-build/issues/2216#issuecomment-1196027202

Well, thats the only configuration we have. Is infra team going to deprecate use of artifacts.opensearch.org?
Why do we have two different endpoints?

@bbarani
Well, thats the only configuration we have. Is infra team going to deprecate use of artifacts.opensearch.org? Why do we have two different endpoints?

Hi @saratvemulapalli

We are not deprecating artifacts.opensearch.org endpoint.
When we 1st start opensearch there is no proper staging bucket, therefore we put both snapshots and releases on the production artifacts.opensearch.org bucket.
Now we have proper staging bucket we want to switch the snapshots artifacts back to staging on ci.opensearch.org.

Thanks.

@saratvemulapalli Can you provide your inputs?

I believe we can close this issue, as no changes are being made in terms of snapshots retrieval artifacts.opensearch.org should continue to work, it worth to reopen a new issue, if snapshots retrieval is being changed from artifacts.opensearch.org to ci.opensearch.org, which is actually the right thing to do ;).
Closing this issue, please re-open if required.
Thank you


Add ROW-BOX alignment options

Add options to align the contents of the row-box either top-, middle-, baseline-, or bottom-aligned.

See #11


RAPL code issues

Describe the bug
There are some code issues on pkg/power module RAPL side.

In pkg/power/component/power.go, for platforms which support RAPL sysfs, there is no chance to reach the RAPL msr side, not sure if the rapl_msr*.go are dead code or not?
In pkg/power/component/source/rapl_sysfs_util.go, current code to get cpuNum and cpuPackage is low efficient, could be refined.
In pkg/power/component/source/rapl_msr_util.go, current code for CPU package and core mapping has logical error.
See function "mapPackageAndCore" in rapl_msr_util.go:
https://github.com/sustainable-computing-io/kepler/blob/main/pkg/power/components/source/rapl_msr_util.go#L81
The "id" here is the specific core's physical_package_id, i.e. On two-sockets platforms, the "id" should be either 0 or 1, so the "packageMap" concept is wrong after the for loop.

Expected behavior

See function "getNumPackage" and "getNumCPUs" in rapl_sysfs_util.go.
For Server CPUs like Intel 4th Xeon SP and AMD EYPC Genoa, etc, there might be hundreds of cores per package, the more efficient way to get cpu number and package number is leveraging the output of "lscpu“ command:

Ubuntu system example:
$ lscpu |grep -E "CPU(s)|Socket(s)"
CPU(s):                          128
On-line CPU(s) list:             0-127
Socket(s):                       2
NUMA node0 CPU(s):               0-31,64-95
NUMA node1 CPU(s):               32-63,96-127
RHEL system example:
$ lscpu |grep -E "CPU(s)|Socket(s)"
CPU(s):              224
On-line CPU(s) list: 0-223
Socket(s):           2
NUMA node0 CPU(s):   0-55,112-167
NUMA node1 CPU(s):   56-111,168-223
For CPU number, maybe need some more code to fetch the exact number; for package number, just "lscpu |grep Socket" is enough.

If the RAPL MSR code is not dead code, we need to fix the issue mentioned above.

@jiere On certain environment (hyper V if my memory is right), the RAPL sysfs files are missing, but msr are accessible. That gave rise to the msr code. If you find that is not the case any more, we can remove the msr code.

Thanks @rootfs for your quick reply, I will check later and get you tuned.

my hardware (x86 PC) support msr but no RAPL_sysfs, so the MSR is used in my env..
[root@localhost ~]# ls /dev/cpu/0/msr
/dev/cpu/0/msr
[root@localhost ~]# ls /sys/class/powercap/intel-rapl/
ls: cannot access /sys/class/powercap/intel-rapl/: No such file or directory
[root@localhost ~]#

Update from my side, I tried on my laptop:
host CPU: 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
host OS: Windows 11 Enterprise
I enabled Hyper-V and provisioned a new VM:
jie@jie-Virtual-Machine:~/Desktop$ uname -r
5.15.0-27-generic
jie@jie-Virtual-Machine:~/Desktop$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04 LTS"
...
In the VM's sysfs, there is dTPM framework visible under powercap, but no intel-rapl also.
jie@jie-Virtual-Machine:~/Desktop$ ls /sys/class/powercap
dtpm
jie@jie-Virtual-Machine:~/Desktop$ ls /sys/class/powercap/dtpm -l
lrwxrwxrwx 1 root root 0 Mar 20  2023 /sys/class/powercap/dtpm -> ../../devices/virtual/powercap/dtpm
While msr path is accessible:
jie@jie-Virtual-Machine:~/Desktop$ ls /dev/cpu/0/msr
/dev/cpu/0/msr

my hardware (x86 PC) support msr but no RAPL_sysfs, so the MSR is used in my env..
[root@localhost ~]# ls /dev/cpu/0/msr
/dev/cpu/0/msr
[root@localhost ~]# ls /sys/class/powercap/intel-rapl/
ls: cannot access /sys/class/powercap/intel-rapl/: No such file or directory
[root@localhost ~]#

Could you also list your PC CPU and OS info? Thanks.

here you go
[root@localhost ~]# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 45
Model name:            Intel(R) Xeon(R) CPU E5-2470 0 @ 2.30GHz
Stepping:              7
CPU MHz:               1199.902
CPU max MHz:           3100.0000
CPU min MHz:           1200.0000
BogoMIPS:              4599.59
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0-7,16-23
NUMA node1 CPU(s):     8-15,24-31
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca                                                                                cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1g                                                                                b rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_t                                                                                sc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx                                                                                16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave a                                                                                vx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid xs                                                                                aveopt dtherm ida arat pln pts md_clear flush_l1d
[root@localhost ~]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@localhost ~]# uname -a
Linux localhost.localdomain 5.4.231-1.el7.elrepo.x86_64 #1 SMP Sat Feb 4 13:55:47 EST 2023 x86_64 x86_64 x86_64 GNU/Linux

@jichenjc , please try below command to check if the RAPL is not enabled in your current kernel config:
$ grep RAPL /boot/config-$(uname -r)
CONFIG_PERF_EVENTS_INTEL_RAPL=y
CONFIG_PROC_THERMAL_MMIO_RAPL=m
CONFIG_INTEL_RAPL_CORE=m
CONFIG_INTEL_RAPL=m

um.. you are right
my env didn't enable RAPL currently seems
# grep RAPL /boot/config-$(uname -r)
CONFIG_PERF_EVENTS_INTEL_RAPL=m

but the MSR seems ok to read

Not sure if the MSR socket is workable on your side, I used current kepler code and wrote a test main.go to check the result, different platforms have different behavior.. some of them are unexpected..
Let me figure out a proper way to fix, thanks for your confirm anyway.


ansible-galaxy: fix wrong file name

Another tiny correction for the ansible-galaxy tutorial

I had the same commit in my branch :)

Ah sorry hehe, I commited quickly before forgetting it

no problem!


Ability to mint access_tokens with restricted scope.

There are many scenarios where it'd be useful to be able to give a client or AS or bot or widget or some other service limited access to your account:

To limit access to other APIs (e.g. to forbid an untrusted client from being able to read account_data, or to read your 3PID bindings, or attempt E2EE etc).
To hand access to a subset of rooms to a limited account (e.g. a read-only HUD)
To allow a double-puppetted bridge to send messages as your real user, but only in bridged rooms

In the past this has got a bit derailed by the idea of replacing our auth system entirely by OAuth2: https://github.com/matrix-org/matrix-doc/issues/2615 - and meanwhile an MSC trying to do something very similar to this got abandoned: https://github.com/matrix-org/matrix-doc/issues/531.  So I'm reopening this as a high level issue for folks to upvote and coordinate via.

Yes I would certainly like to see this!
A few thoughts I've had on this, although they don't completely match the bullet points you have listed as they are rather thought of mostly with bot accounts in mind:

There would be a relation from the managed sub-account and the (multiple) parent/controller accounts. It would be configurable if the sub-account can remove this relation.
There would be a set of commands the parent account can make happen in the sub-account. In particular, there could be a way to reset the password of a sub-account. This would allow easily e.g. managing a group of accounts (e.g. family, company, team) without any particular administrative bits in the system. Disabling account is of course also one of the commands
There would be a set of commands the sub-account can issue. This would be useful for e.g. bot accounts, for webchat accounts.
Inspired by what you wrote: you could attach to your account a set of commands another account can cause in your account. It would be like the same as previous points, but configured in reverse.

Set of commands could be an endpoint-oriented JSON pattern "firewall list" like: [{"PUT: "/r0/rooms/([^/]*)/send/m.room.message/.*", "permit": true}, {"GET": ".*", "permit":  false}, {"PUT": ".*", "permit":  false}] which would be very close to the protocol and would likely need the least amount of work both in clients and the servers to implement. Instead of regular expressions some other more structured way of expressing patterns could be used, which would likely be easier to manipulate programmatically. Similar approach could be used for filtering messages a bot can receive in a room and it would be easy-ish for clients to determine if a message should be sent a bot in an e2ee room (and thus only send appropriate keys to the bot only in those cases).
Obviously there's a big risk of scope creep here 🙄.

fwiw https://github.com/turt2live/matrix-oauth exists as a very early proof of concept for this sort of thing, with intentions of expanding it out as a playground before a formal MSC.

related https://github.com/matrix-org/synapse/issues/5323

Given I spent a decent amount of time on https://github.com/matrix-org/matrix-doc/issues/531 and I'm no longer a pumpkin, I'd love to take this up again and implement it in Dendrite. This issue wasn't as important 5.5 years ago when I wrote that issue, but is definitely more important now as Matrix has a strong native community which has accounts which want to be protected.

MSC laying out the path for this: #2967
This is part of a larger work aiming to replace Matrix authentication with OAuth 2.0

MSC laying out the path for this: #2967
This is part of a larger work aiming to replace Matrix authentication with OAuth 2.0

Yes I would certainly like to see this!
A few thoughts I've had on this, although they don't completely match the bullet points you have listed as they are rather thought of mostly with bot accounts in mind:
1. There would be a relation from the managed sub-account and the (multiple) parent/controller accounts. It would be configurable if the sub-account can remove this relation.

2. There would be a set of commands the parent account can make happen in the sub-account. In particular, there could be a way to reset the password of a sub-account. This would allow easily e.g. managing a group of accounts (e.g. family, company, team) without any particular administrative bits in the system. Disabling account is of course also one of the commands

3. There would be a set of commands the sub-account can issue. This would be useful for e.g. bot accounts, for webchat accounts.

4. Inspired by what you wrote: you could attach to your account a set of commands another account can cause in your account. It would be like the same as previous points, but configured in reverse.

Set of commands could be an endpoint-oriented JSON pattern "firewall list" like: [{"PUT: "/r0/rooms/([^/]*)/send/m.room.message/.*", "permit": true}, {"GET": ".*", "permit": false}, {"PUT": ".*", "permit": false}] which would be very close to the protocol and would likely need the least amount of work both in clients and the servers to implement. Instead of regular expressions some other more structured way of expressing patterns could be used, which would likely be easier to manipulate programmatically. Similar approach could be used for filtering messages a bot can receive in a room and it would be easy-ish for clients to determine if a message should be sent a bot in an e2ee room (and thus only send appropriate keys to the bot only in those cases).
Obviously there's a big risk of scope creep here roll_eyes.

I think there is a significant use case for accounts controlling parts of other accounts as you outline here. I have two concerns however with this:

There should be a way to create temporary scoped access tokens. This could be used to give widgets temporary access to a user's account.
While the firewall idea is an ideal way to specify capabilities for an account, when used in the widget scenario, it may be too complex to effectively convey to users what permissions are being granted, like the current push notification system.


chore: simplify chat messages retrieval

Turns out from wasn't necessary. Not a big change 😄

Okay, added a new fix that actually has UX impact. Noticed that I keep seeing the offline screen for a long time before the fully loaded channels suddenly pop into view. Redid some of the loading/rendering logic and that cleaned up the experience 😄


Fix listing processes on Android 7 and above

Android 7 and above uses toybox, which outputs multiple items on one line. Pass the -1 flag to make sure each item gets its own line.
The -1 flag causes problems on Android < 7, so check for that, too.

/cc @bartsaintgermain


GoSquared Integration

Hey Sacha, was curious about the reason that GoSquared integration was removed? It seems like just the input on the settings page for the account ID has been removed, but the tracking and events code is still in place.
https://github.com/TelescopeJS/Telescope/search?utf8=✓&q=gosquared
I've added that input back in on my fork, added my ID and it seems to work fine. Just want to make sure I'm not doing something that problematic. Thanks man!

No it's fine, I just removed it in prevision of overhauling the analytics/tracking system to use Segment.io instead. There will also be a simple API so you can easily add new analytics providers too.
See: https://github.com/TelescopeJS/meteor-events

ooooh. This is really great news! Somehow I missed the #analytics channel on slack. Thanks man.

Hey, @jamiewilson! Telescope has changed a lot in the past months, and there is a new React-based version, Telescope Nova (intro video). If you know Crater, it runs on the latest version.
The Legacy version is no longer supported. I'm closing this issue.
I invite you to check the new version, it's awesome!
Happy hacking! 🚀
Ps: by the way, don't hesitate to join the Slack to ask any question, you are welcome! 👍


Check the code for memory leaks

I haven't done this in a while, so we should probably look for memory leaks. I've had issues in the past with valgrind because if I ran with --leak-check=full, valgrind would report literally millions of errors and quit. These errors seem to be coming from within BLAS/LAPACK. I think the issue comes from the fact that cblas and LAPACKE actually provide two interfaces: the "middle-level" interface, which is identical to the Fortran API, and the "high-level" interface, which abstracts some of the workspace variables. Maybe valgrind is reporting uninitialized value errors or something like that. Or maybe BLAS and LAPACK are just hostile towards valgrind. I don't know. But I was able to run without that option and still catch some memory errors. Anyway, another fun project for someone to do.

I've run a few tests over the past few days, and I was able to fix a few memory errors. The only errors I'm seeing out of valgrind now are strange errors (not leaks) from LAPACKE and a few other nit-picky things from valgrind that I think we can disregard. If someone wants to explore these errors further, they are certainly welcome, but for now I think we can put this issue to rest.


10/03 PM Publish

Learn Build status updates of commit 2131ca0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.github/CODEOWNERS
:white_check_mark:Succeeded

.github/dependabot.yml
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/00-hacktoberfest.yml
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/01-article.yml
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/02-bug.yml
:white_check_mark:Succeeded

.github/ISSUE_TEMPLATE/config.yml
:white_check_mark:Succeeded

.github/messages/expectations.md
:white_check_mark:Succeeded

.github/PULL_REQUEST_TEMPLATE.md
:white_check_mark:Succeeded

.github/workflows/checklist.yml
:white_check_mark:Succeeded

.github/workflows/expectations.yml
:white_check_mark:Succeeded

.gitignore
:white_check_mark:Succeeded

.markdownlint.yaml
:white_check_mark:Succeeded

.markdownlint-cli2.yaml
:white_check_mark:Succeeded

.vscode/cSpell.json
:white_check_mark:Succeeded

.vscode/cspell/azmodules/cspell.yaml
:white_check_mark:Succeeded

.vscode/cspell/azmodules/dictionaries/azps.txt
:white_check_mark:Succeeded

.vscode/cspell/psdocs/cspell.yaml
:white_check_mark:Succeeded

.vscode/cspell/psdocs/dictionaries/externalCommands.txt
:white_check_mark:Succeeded

.vscode/cspell/psdocs/dictionaries/fictionalCorps.txt
:white_check_mark:Succeeded

.vscode/cspell/psdocs/dictionaries/fileExtensions.txt
:white_check_mark:Succeeded

.vscode/cspell/psdocs/dictionaries/psdocs.txt
:white_check_mark:Succeeded

.vscode/cspell/psdocs/dictionaries/pwshAliases.txt
:white_check_mark:Succeeded

.vscode/extensions.json
:white_check_mark:Succeeded

docs-conceptual/azps-8.3.0/upcoming-breaking-changes.md
:white_check_mark:Succeeded
View (azps-8.3.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Add CSP nonce on inline script in storage-change-detection.html

fixes #1387

 thread 'docbuilder::rustwide_builder::tests::test_build_crate' panicked at 'assertion failed: `(left == right)`
  left: `false`,
 right: `true`', src/docbuilder/rustwide_builder.rs:735:13

Same issue as before; unrelated to this change.


Drop redundant pointers and decoders

Changes

:broom: Drop unnecessary double-pointers in decoding logic.
:broom: Replace decoder.Decode with json.Unmarshal where they are equivalent anyway. This also avoids unnecessary byte buffers.

/kind cleanup

Release Note

NONE

Docs

/assign @julz

/cherry-pick release-0.25

/cherry-pick release-0.24

/cherry-pick release-0.23

/cherry-pick release-0.22


[Dev] Review, Test and merge PRs with libraries/fx versions updates

There are multiple PRs automatically created by MSFT which upgrade versions of frameworks/libraries in many cases due to security issues or other improvements.
We need to be compliant with it and upgrade to those versions when possible.
https://github.com/Azure/mec-app-solution-accelerator/pulls

Please, Review, Test and merge PRs with versions updates.
It's critical to test each PR before merging to DEV and MAIN just in case it can break the code compatibility.

Closing


Turned on high resolution option for LSM303DLHC accelerometer, added pin...

...Mode() initializations for ml8511_init(), turned on temperature sensor for LSM303DLHC magnetometer, added functions for retrieving raw accelerometer, gyro, magnetometer, gyro temperature, and magnetometer temperature

Ben
Yes, I have been busy over the past week or so.  If you recall, I sent you an e-mail asking about the addition of raw sensor readings and temperature from the inertial sensors (accelerometer and gyro).  Rather than going back and forth, I have cloned (or forked, in GitHub terms) the ArdusatSDK and added functions to retrieve raw readings, at least from the acclerometer, gyro, and magnetometer.  In addition, I enabled the temperature sensor on the LSM303DLHC (it turns out it is part of the magnetometer, and not the accelerometer, but at least the 2 die are inside the same packaging), and provided functions for retrieving the raw temperature from both the gyro and the magnetometer.  The scale factor on the gyro temperature is -1 LSB/degree C, but the offset is not clear.  I am not sure about the scaling and offset for the magnetometer temperature sensor; I need to retest this.
While I was at it, I found the accelerometer readings did not go up or down in increments of 1.  It turns out if you want normal (meaning high) resolution, there is a bit you need to set in one of the accelerometer control registers.  I have made this change as well, and the raw accelerometer readings now appear to have the correct resolution (can go up and down in increments of 1).  Note the scale factor has not changed (it is still configured for +/- 2g range, giving a scale factor of 1000 LSB/g), so the readings obtained from the existing engineering unit accelerometer read function will also benefit from the improved resolution.
Finally, I added the pinMode() calls for the ultraviolet sensor right in the ml8511_init() function, as this eliminates the need for the user sketch to do this.

Interesting finds! I did a little googling on the High Resolution mode and found:

The accelerometer gives low-resolution 10-bit readings by default (the lowest 6 bits of the output are always 0). To get the full 12-bit resolution, you must set the HR (high resolution) bit in the CTRL_REG4_A register.

So this change should indeed help things out. At some point the SDK will need to gain functionality to auto-scale and/or adjust the range/sensitivity as well, since +/- 2g isn't really suitable for all applications.
Thanks for submitting the PR! I'll test it out on some hardware tomorrow, but from glancing over it, it looks good!

Hi @mkirkhart! I had a chance to review the changes, they seem to work well. Two quick points:

This is pretty pedantic, but I'm trying to keep commits fairly clean & atomic, with easy-to-read commit messages. Could you break this into 2 commits: 1 for the updates to the initializers for pinMode & high res mode, and one for the raw temp + raw values additions? You can do this by running git reset ac93039, then adding in the changes piecemeal using git add -p. If possible, try to keep commit messages to 80 characters or less on the first line (if you run git commit, it should launch you into a multi-line editor, so you can have an 80 character summary, then put details on subsequent lines)

There's a typo in the function name ld3gd20h_getRawTemperature.

Sorry to be so pedantic. The functionality looks great, I'll merge it in as soon as you update the commits!

Ben
I think I fixed everything you wanted.  Redoing the changes as separate commits caused me some problems when I tried to push it back to the GitHub repo; it would not accept the changes, thus forcing me to do a pull - fix merge conflicts - push.
That's it for now.  Hope I got this right.


Get-Module -ListAvailable -Name MSOnline always returns an empty collection when run from .NET Core C#

Steps to reproduce
        public void Process(out string error)
        {
            using (var ps = PowerShell.Create())
            {
                ps.AddScript("Get-Module -ListAvailable -Name MSOnline");

                var results = ps.Invoke();

                if (results.Count == 0)
                {
                    error = "You do not have the PowerShell MSOnline module installed.  Please run Install-Module MSOnline in PowerShell, then restart this app.";
                }
                else
                {
                    error = null;
                }
            }
        }

I can run the same command directly in PowerShell & it lists MSOnline without an issue.  However, when run from within my .NET project, I get nothing.
I have NuGet packages installed:
Microsoft.PowerShell.SDK 6.2.0
Microsoft.PowerShell.Commands.Diagnostics 6.2.0
Microsoft.WSMan.Management 6.2.0
I have also attempted this in a clean console application with the above code only, on another machine and see the same results!
Expected behavior
Results should contain one result listing MSOnline.
Actual behavior
Results is an empty collection

I believe this is down to $env:PSModulePath not being defined in this kind of setup. No assumptions are made about PowerShell actually being installed here, nor where modules might be. You're going to have to set that value appropriately first. :)

Hmm, interesting.  I have just run $env:PSModulePath from the C# app and can see it does have some path variables set, and those folders contain some modules.
I've tried running Get-Module -ListAvailable from the console app and also get no results.  Considering I do have some module paths, surely I should get at least something?

Assuming they're compatible with PowerShell Core 6.2 I think so.
This kind of issue came up once before, but I can't find the issue right now. I'm sure someone else here has a better idea of where it is, but if not I'll keep looking a bit later.

Thanks :)
Just to add to this, I have checked the ps.Stream.Errors (and other) collections and am not seeing any errors or warnings or anything else.

Why was this issue marked as answered?  I don't see any entries above that even come close to answering it.  Others were able to recreate the issue above, but were just as perplexed as the original poster above.  I am experiencing this exact same issue, 2 years after the posts above.  I have not been able to find a solution to it.  It works fine within the PowerShell app and in PowerShell add-in is MS Code.  But, calling it from C# returns 0 results.  I respectfully request that this thread be reopened and that the "Answered" designation be removed.  I am trying to find the solution or explanation for this issue.  If I find it, I will come back here and post it, if I can.  Not even sure if this message will post.

still no answer ?


update default OS versions

centos/rhel 7.4 -> 7.5
ubuntu 16.04 -> 18.04
Signed-off-by: Sage Weil<EMAIL_ADDRESS>

We have 7.6 images for RHEL and CentOS

I don't know why unit tests are hardcoded to the default os version, but this patch requires to fix teuthology/test/test_get_distro_version.py


Probably wrong description for LibraryFlag

Based on XSD LibraryFlag should be HEX value like LocaleId:
<xs:simpleType name="ST_LibFlagCom">
      <xs:restriction base="xs:string">
          <xs:pattern value="[0-9a-fA-F]"/>
      </xs:restriction>
  </xs:simpleType>

https://github.com/microsoft/msix-packaging/blob/master/resources/AppxPackaging/Manifest/Schema/2015/AppxManifestTypes.xsd
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 96c0035f-43d3-9516-63c3-8aa2cdc810c3
Version Independent ID: dd304347-376a-c733-13a5-cdd4ae9e7520
Content: com:Version - Windows UWP applications
Content Source: winrt-related-src/schemas/appxpackage/uapmanifestschema/element-com-version.md
Product: uwp
Technology: winrt-reference
GitHub Login: @drewbatgit
Microsoft Alias: drewbat

Thanks for reporting this issue. The format for this attribute has been corrected in the documentation.


"Owning Corporation" part of moon structures seem to be broken

Hi,
I decided to fully map up the moons of my home system and the citadels of the "occupied" moons, however whenever I try to add the owning corporation of the athanor's nothing comes up to corp name, nor the corp tag (while it can perfectly find my own).
It's not even that they are really fresh corps as some has been close to 10 year old. 1 such example corporation for testing purposes would be "76RUS - YAR Group"

Did you loaded your database? Please refer to 'Update Alliance and Corporation data' in the Wiki.
Am 24. Juli 2019 17:56:44 WESZ schrieb Destroyer140<EMAIL_ADDRESS>
Hi,
I decided to fully map up the moons of my home system and the citadels
of the "occupied" moons, however whenever I try to add the owning
corporation of the athanor's nothing comes up to corp name, nor the
corp tag (while it can perfectly find my own).
It's not even that they are really fresh corps as some has been close
to 10 year old. 1 such example corporation for testing purposes would
be "76RUS - YAR Group"
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/chrRtg/eve-skylizer/issues/23

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Hi,
Sorry for the late response. I wasn't aware that skylizer is a tool you were meant to install and used it on  what I assume to be it's home page https://skylizer.eve-tools.info/index.
Is this something you are supposed to host on a server or something or could it work as an "on demand" tool that I just run and use locally whenever I need?

@Destroyer140
Skylizer is an open source project that can be loaded your own web server to be served to the public or access within your LAN for personal use.

@tonytonyistony is perfectly right, thanks for your answer.
While the original question seems to be answered I'll close this issue. Feel free to re-open or to submit a new in case you found a problem or have a suggestions.


chore(master): release 0.14.0

:robot: I have created a release beep boop
0.14.0 (2024-12-01)
Features

updating from newer svd2rust (#105) (69dbc60)
updating from newer svd2rust (#106) (00c1870)
updating from newer svd2rust (#98) (49b11bf)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/xmc-rs/xmc4200/releases/tag/v0.14.0 :sunflower:


Grammar

Just a quick scan through the readme to correct some spelling errors.

Missed one more it says drodowns on line 80, should be dropdowns

Missed another!! Instalation should be Installation


Fix issue 465: “/event/scrub” block long time

Signed-off-by: Sun Jianjiao<EMAIL_ADDRESS>

recheck

recheck

Please rebase and commit again. MongoDB location have been changed and InfluxDB have been removed.

@jduranf The PR‘s target branch is california,  california branch still has influxdb.

@unanao you are right, I didn't notice the target was california... anyway, delhi will be released in a couple of weeks, why not close this PR and create a new PR targeting master branch? This PR should be done anyway
Also, if you still want to target california branch, there are a couple of checks which fails and should be solved. And you modified several snap files, which shouldn't be modified in this PR.

@unanao you are right, I didn't notice the target was california... anyway, delhi will be released in a couple of weeks, why not close this PR and create a new PR targeting master branch? This PR should be done anyway
Also, if you still want to target california branch, there are a couple of checks which fails and should be solved. And you modified several snap files, which shouldn't be modified in this PR.

@jduranf  I create a new pull request for master.


Configurable log levels when deploying in a K8S cluster

Is your feature request related to a problem? Please describe
When deploying DefectDojo in a K8S cluster, there is no way to change the default log levels that are configured in files such as settings_dist.py, or the extra configuration files.
Describe the solution you'd like
At least I would like to be able to set log levels when deploying DefectDojo. I would then be able to just set the log levels in the values.yaml and these log levels would be applied.
Describe alternatives you've considered
It would be even better if the log levels could be changed while the containers are running, without restart.

I think this is now resolved with DD_LOG_LEVEL


cluster, node: support optional other_nodes for wait_other_notice

When stopping more than one node in parallel and waiting for other to notice
we want to skip nodes that may be stopping concurrently.
Provide an optional other_nodes parameter for the caller to pass
only those nodes that require noticing.

BYO test run: byo_build_tests_dtest/321

ping @nyh

Note: this is related (and possibly should close) https://github.com/scylladb/scylla-ccm/issues/124.
The problem is also mentioned (among other problems) in https://github.com/scylladb/scylla-dtest/issues/795.
I'll review now.

I'm marking approval because the code is correct and can be used to fix real dtest problems, and is general and future-proof.
But I'd still like to comment that I would have gone a different route to solve just the problem we actually encounter: As explained in #124, the code already, correctly, doesn't wait for non-live nodes to notice the event. But the problem is nodes can die while we wait for it to notice. So the fix should be: while waiting on another node's log to mention "noticing" the event, we should also be on the lookout for messages about the node going down, and if that happens - we should stop waiting on this log (and accept this as a success - not a failure). If we did this, the user would not need to manually build a list of nodes to wait for as this patch allows him to.

I see your point.  It is more complicated and can be added in the future.


ISSUE 76 - update email links

added new command to update links in email template ISSUE AB#76

@manisfdcsfdx please update branch and re raise


Move the _is_created assignment to the top

Description
Now playing with the Shapes layer, I found an issue with the _is_creating flag.
I am creating a plugin which is connecting the set_data event of the layer to identify when data is changed.
However, during the creation of a Path shape (should also happen for Polygon) I want to wait until the editing is finished and skip the update if it is still in creation.
Therefore, I use:
...
    layer.events.set_data.connect(self.my_func)
...

def my_func(self, event):
     if event.source._is_creating:
          return
      ....
....

But it turns out, that I cannot rely on the _is_creating flag, because it is set too late in the drawing process.
Therefore, I propose to move the assignment before the creation of the very first vertex.
Before (The False after the very first click on the left side):

After:

Addition (The True after the very first click on the left side):
If one clicks two times while polygon or path is selected, an error is thrown. I also added a test and a fix for this scenario.
Type of change

[X] Bug-fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)

Sounds like a reasonable change! However, should we then somehow expose this publicly a bit more clearly? Maybe by having a separate event for like shape_completed?

To be honest I am not sure if a shape_completed event will make it more clearl as it furthers separates the way Point and Shapes layers and different Shapes within the Shapes layer behave.
I would rather add a flag about the current state of the event much like we did with the parent attribute in the Source layer: https://github.com/napari/napari/pull/5028
That way the information would be present in the set_data event itself?

Yeah, maybe we can somehow stick this in the Event object, which does have machinery to handle arbitrary kwargs. I'm not super familiar with its usage in napari, though. @Czaki maybe has some insight?

That way the information would be present in the set_data event itself?

You could pass arbitrary kwargs when emmit event. But You need to update the docstring and all places where the event is emitted.

Hello @brisvag and @Czaki  :)
What is the status of this change?
Shall we first keep it as it is or should we work on a solution which includes this into the Event itself?

I would suggest to go directly for the Event approach, and do as @Czaki suggested and simply add a kwarg to this event, called completed or something like that.

@Czaki @brisvag given the long wait time on this and that this solves a real issue and has tests to go with it, what do you think about merging it as-is and leaving a proper fix until a later PR?

Discussed at the PR party, we'd like @melonora to weigh in also.

If we do want to merge this, I pushed some changes to use read_only_mouse_event instead of ReadOnlyWrapper. The tests changed passed locally, so hopefully they pass on CI too.

@melonora would you have time to update the PR with those changes? It would be good to get this over the line...

ping @melonora

Ok, tests are passing, there are three approvals, and it's been marked ready to merge for the last week (seems like plenty of time). Thank you @melonora!


Route coordinates issue

Hello, I was using tibialyzer 1.3 and route feature was working fine. Now I've updated to Tibialyzer <IP_ADDRESS> and when I click on the route button it shows some random coordination instead of my current location. Anyone got an idea of how could I fix this?
-I've already tried to install .NET framework 4.6.1 developer pack

This was an issue with incorrectly using the X coordinate as the Z coordinate (see 86f202a5b2d6df26844a705967ff3e6423ce58c4). It should be fixed in the code now, but I haven't uploaded a new version yet. If you compile from source it will work, though.


[Readme.md] New modern logo + Improved sales pitch

New modern logo

Hi Adam,
This branch is ready to be merged. I wanted to start contributing to this fantastic project by working on the readme, to help attract more users and developers to the project. The logo is designed to flow from left to right, going from the traditional django green, to the blue and purples and pinks, as an expression of going from traditional django to the new world of reactive web components. The wings spread out like individual components, and the tips of the wings are like smaller child components. It's also meant to evoke a little bit of a phoenix to suggest similar ethos to phoenix liveview.
While I know it's good to have the installation process in one place (the docs) I think the GitHub repo is a place where people will judge the completeness of the project and expect a little bit of information on how to get started, without having to visit the docs. So I migrated the basics over to make it easy for people to get started.
Hope you like the changes! And if you merge, I'll definitely keep contributing. Really love what you've started. It's brilliant.
Cheers,
Dan
P.S. You can preview the new readme here: https://github.com/dancaron/django-unicorn/tree/New-modern-logo

Ready to be merged.

Wow! Thanks for all of the readme updates and the logo. I'll take a look through them and let you know what I think over the next couple of days!

The logo is designed to flow from left to right, going from the traditional django green, to the blue and purples and pinks, as an expression of going from traditional django to the new world of reactive web components. The wings spread out like individual components, and the tips of the wings are like smaller child components. It's also meant to evoke a little bit of a phoenix to suggest similar ethos to phoenix liveview.

I really appreciate all the thought and work that went into this logo redesign. Maybe this is pedantic, but one worry I have is that adding wings means that it isn't technically a "unicorn" anymore. I am conflicted, though, because I really do like the way the wings look (and the Django pony does have wings), especially with the color gradients. Any ideas about how to keep the same concepts, but maybe without the wings? Or do you think the wings are ok even though it's called "unicorn"?

Appreciate it. Yeah, I thought it was a natural extension of the django pony, but with the unicorn horn. I personally like the wings because I feel like the project gives the developer wings. I mean, it can really take the dev experience to new heights. You can build crazy rich UI without react or vue. And I think the wings express that freedom. If you really want, I can try to remake it without the wings. But considering the django pony has wings, I think we're on brand.

One other thought: can you make the unicorn's horn slightly longer? Thanks!

Thanks again for this PR! Closing this because I had to merge it manually.

@all-contributors add @dancaron for doc

@adamghill Awesome! Check the logo I don't think it's loading properly in the readme.


Kubernetes experimental version 1.22.5-rancher1-1 is not showing up for rke1 downstream clusters on a rancher patch version

Rancher Server Setup

Rancher version: v2.6.3-patch1-rc3
Installation option (Docker install/Helm Chart): Docker install

If Helm Chart, Kubernetes Info: k3s
Cluster Type (RKE1, RKE2, k3s, EKS, etc):
Node Setup: 1 node
Version: v1.21.7+k3s1

Proxy/Cert Details: self-signed

Describe the bug
For the infrastructure providers, kubernetes version v1.22.5-rancher1-1 is not showing up in the kubernetes versions' dropdown.
Expected Result
Expected the k8s 1.22 experimental version to be present in the kubernetes dropdown
Screenshots
2.6.3-patch1-rc3 version:

2.6.3:

Additional context
<!--Add any other context about the problem here.—>

Verified the k8s version 1.22.5-rancher1-1 experimental is showing up on rancher v2.6.3-patch1-rc3
docker run -d --privileged --restart=unless-stopped -p 80:80 -p 443:443 -e  CATTLE_SERVER_VERSION=v2.6.3-patch1 rancher/rancher:v2.6.3-patch1-rc3


Curl/sh install comand error on Ubuntu

Hi
when I copy
curl http://j.mp/spf13-vim3 -o - | sh
into my terminal on Ubuntu 11.10, I got
sh: Syntax error: newline unexpected
I thought this was happening because Ubuntu use dash instead of bash but when I switch into bash I got
sh: line 1: syntax error near unexpected token newline' sh: line 1: '
Am I doing something wrong or it is Ubuntu issue?

Same here. The Installer will not work.
There is a second problem: The install-script tries to install command-t, but command-t was replaced with ctrlp :-)

Fixed the command T issue.
I think there's a patch coming in to fix the other.
Quick fix is to do a curl http://j.mp/spf13-vim3 -L -o - | sh instead.

Works fine here (Ubuntu 11.10), problem solved. Thanks for quick fix.

I am using ubuntu 14.04 LTS and getting this error.

that's for a meteor installer.  and in this case, copy and pasting the text is sufficient. no screenshot is required.

Sure...Now meteor started working.


Adds test for translate-nl

And some reasonable additional tests.

@Kaiepi well, it was not tested, so while I was on the file I decided to include that too.

These tests are broken. You're testing the literal \ and n instead of the actual newline characters and the non-Windows branch is missing :translate-nl argument.
Also, please use is-deeply routine instead of ok, so failures would actual show the differences between  expected and got versions.

:+1: Thanks!

Thanks for reviewing and spotting the errors :-)


Added an option to keep template arguments (disabled by default)

Thanks for the PR. Closing as the changes are already in but in a slightly different way.
Appreciated.


Normalize plot

[x] Normalize horizontal plot by year
~Add value at the top of each bar~
[x] Write title: Spare time spenditure by year

Repeat for

Done in df712af


OutputDebugString and UWP (Windows 10)

Outside of UWP app, OutputDebugString works fine.
But if I try a direct call to OutputDebugString from inside a UWP style app (Windows 10), DebugView++ never shows the message.
I would like to observe OutputDebugString output without attaching Visual Studio debugger.
Is there a way to use your DebugViewPP with UWP ?
It should be available because SysInternals Debug View is able to show UWP messages.

Has there been any traction to fix this? I just stumble upon this bug on one my apps.

There is probably no easy way to get debug information from an uwp APP.
I use windbg preview from the microsoft store for this.

This isn't anything I can do (I think) the hooks that SysInternals Debug View is using are kernel hooks that I can't access, (if anybody knows how to do it, please chime in)
However, you can open send UDP or TCP messages to debugview++ from any application...

Not sure what kernel hooks you were trying to access, but in the past when things are sort of prohibited in certain windows applications, and I tend to access them by loading the library that contains those functions. For more info go to: https://stackoverflow.com/questions/8696653/dynamically-load-a-function-from-a-dll
I applied this technique to create very simple call stack in one of my window store applications calling forbidden class from kernel32.dll and Dbghelp.dll.

The problem is, you want to hook into the DbgPrint calls that other applications are calling, this is possible if you write a small kernel driver and I believe this is what Dbgview does. At startup it exacts a .dll, containing the kernel driver that hooks into DbgPrint and copies the messages into a piece of shared memory, that is then retrieved by dbgview. I don't have the knowledge/experience to do this. And although I would like it if debugview++ could do this, I don't consider it worth my time to learn this. The use-cases where I really needed it, I just write messages to a logfile and tail that using debugview++, or send UDP messages.


Setting for TwitterKit 3

First of all, I appreciate to your hard work @chroa .
I'm just testing with your new branch for Twitter Kit3
It's working now in my environment with some edit as follows:
AppDelegate.m
#import "AppDelegate.h"
#import "MainViewController.h"
// added
#import <TwitterKit/TwitterKit.h>

@implementation AppDelegate
- (BOOL)application:(UIApplication*)application didFinishLaunchingWithOptions:(NSDictionary*)launchOptions
{
    self.viewController = [[MainViewController alloc] init];
    // added
    [[Twitter sharedInstance] startWithConsumerKey:@"xxxxxxxxxxxxxx" consumerSecret:@"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"];
    return [super application:application didFinishLaunchingWithOptions:launchOptions];
}

// added
- (BOOL)application:(UIApplication *)app openURL:(NSURL *)url options:(NSDictionary<NSString *,id> *)options {
    return [[Twitter sharedInstance] application:app openURL:url options:options];
}

@end

and see my PR
https://github.com/chroa/twitter-connect-plugin/pull/7
Environment
iOS 11.0.1
Xcode 9.0
Cordova 7.0.1
Thanks!

Hi, I am very interested in this update so I can use Twitter in my current iOS 11 project (with Twitter integration stopped due to Twitter-connect-plugin problem). What should I do to apply the corrections made by you?
Thanks in advance!

Thanks for all your help @donuzium! :) Will update according to that.


Add a command to delete a community

Is your feature request related to a problem? Please describe.
I was testing and created a community but later found no command to delete it.
Describe the solution you'd like
A command to delete or better docs if there's a way to thus already (I couldn't find)
Describe alternatives you've considered
Didn't find any.
Additional context

Now you can find a button to delete a community after run /mycomms

Awesome! Thank you for such a fast fix!


Allow customization of LocalChannel instances that are being created …

…by LocalServerChannel.
Motivation
It's possible to extend LocalChannel as well as LocalServerChannel but the LocalServerChannel's
serve(peer) method is hardcoded to create only instances of LocalChannel.
Modifications
Add a protected factory method that returns by default new LocalChannel(...) but users may override
it to customize it.
Result
It's possible to customize the LocalChannel instance on either end of the virtual connection.

lgtm

Cherry-picked into 4.1 (b2379e62f4ae50b55bce7c43e5bd008cf9aacfd1) and 4.0 (40a6b045b489c85a5dadfbf4dc92f575e783569e).
@rkapsi thanks


Please add support for new PhpStorm EAP

It says plugin is incompatible and tries to downgrade to 2.6:

PhpStorm 2019.2 EAP
Build #PS-192.4205.18, built on May 22, 2019
Runtime version: 11.0.3+12-b262.1 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

Yeah fix it please

For now, plugin supports builds 192<.
First of all, I'll have to test it across the 192 build and I'll get back to you soon.

Any news about testing?

Works for me .ignore 2.6.2 with PhpStorm 2019.2 EAP; Build #PS-192.5118.33, built on June 13, 2019, I don't see the reported picture.

Duplicate of #587

Please see 587 for details


feat: redirect to PageContent's changelist when the root page is not public

Description
Now a user is redirected to PageContent's changelist when the root page is not public.
It solves issue #7763
Checklist

[x] I have opened this pull request against develop-4
[x] I have added or modified the tests when changing logic
[ ] I have followed the conventional commits guidelines to add meaningful information into the changelog
[x] I have read the contribution guidelines  and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

Nice! Well done, @erkesado !!


AttributeError: 'float' object has no attribute '_blockchain'

I tried latest master (573c5db363e26fd7ef2bbdda87c48f69e77bb7b2) + graphenelib 1.1.10, and gon an error:
Traceback (most recent call last):
  File "./test_graphene_no_attrib_blockchain.py", line 12, in <module>
    market.orderbook()
  File "/home/vvk/devel/golos/python-bitshares/bitshares/market.py", line 249, in orderbook
    orders["asks"],
  File "/home/vvk/devel/golos/python-bitshares/bitshares/market.py", line 247, in <lambda>
    blockchain_instance=self.blockchain,
  File "/home/vvk/devel/golos/python-bitshares/bitshares/price.py", line 146, in __init__
    Price.__init__(*args, **kwargs)
  File "/home/vvk/.local/share/virtualenvs/market-scripts-BfRrkhQ4/lib/python3.6/site-packages/graphenecommon/instance.py", line 34, in __init__
    slf.__init__(self, *args, **kwargs)
  File "/home/vvk/devel/golos/python-bitshares/bitshares/instance.py", line 14, in __init__
    AbstractBlockchainInstanceProvider.__init__(self, *args, **kwargs)
  File "/home/vvk/.local/share/virtualenvs/market-scripts-BfRrkhQ4/lib/python3.6/site-packages/graphenecommon/instance.py", line 22, in __init__
    self._blockchain = None
AttributeError: 'float' object has no attribute '_blockchain'

Here is the example code:
#!/usr/bin/env python

from bitshares import BitShares
from bitshares.asset import Asset
from bitshares.market import Market

bitshares = BitShares()
quote = Asset('RUDEX.GOLOS', bitshares_instance=bitshares)
base = Asset('RUBLE', bitshares_instance=bitshares)
market = Market(bitshares_instance=bitshares, base=base, quote=quote)

market.orderbook()

Resolved in develop new release candidate coming


Set the following file as main file popup

I am quite happy with the plugin. I use it for syntax highlighting and autocompletion, since I have a buildscript which allready works I didnt bother changing that.
My problem is that every time I enter a '' a popup occures that basically says:
Set the following file as main file
$path to my root which i set in .latexcfg$
Reason: The configuration file setting.

Is there any way to stop that popup? I dont see the point in it

Yes, that is bug, it has been fixed in a PR, should be fixed in next update :-)


Vuepress documentation broken

Describe the bug
Vuepress docs build is broken
To Reproduce
Steps to reproduce the behavior:
npm run docs:build
Expected behavior
Build as usual
Screenshots
Error: Rule can only have one resource source (provided resource and test + include + exclude) in {
  "exclude": [
    null
  ],
  "use": [
    {
      "loader": "cache-loader",
      "options": {
        "cacheDirectory"<EMAIL_ADDRESS>     ...

Desktop (please complete the following information):

System:

OS: macOS 11.1
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 318.13 MB / 32.00 GB
Shell: 5.8 - /bin/zsh

Binaries:

Node: 16.0.0 - ~/.nvm/versions/node/v16.0.0/bin/node
npm: 7.23.0 - ~/.nvm/versions/node/v16.0.0/bin/npm

Browsers:

Chrome: 97.0.4692.71
Safari: 14.0.2

Additional context
I had recurrent issues with Vuepress in the past and too many extra dependencies that somehow pollute the konviw nestjs repository.
An alternative would be the to move the docs to another repository or to move vuepress or vitepress into a folder with another package.json removing dependencies risks with konviw.

@MeStrak do you have any recommendation on the better structure for the documentation and avoiding the complexity of the devDependencies based on the pure documentation package?

@MeStrak do you have any recommendation on the better structure for the documentation and avoiding the complexity of the devDependencies based on the pure documentation package?

This is indeed annoying. I would avoid splitting docs to a separate repo - better to have a separate package.json if the errors keep happening. Vuepress 2 is also in beta 33 so possibly the right time to begin the migration.

@PiiXiieeS I noticed in the currently deployed docs that the embedded iFrames don't seem to be working (400 errors). I'm working on separating the package.json - I'll take a look at this too but if you have any quick pointers that would be helpful.
https://sanofi-iadc.github.io/konviw/demoNoTitle.html

@PiiXiieeS I noticed in the currently deployed docs that the embedded iFrames don't seem to be working (400 errors). I'm working on separating the package.json - I'll take a look at this too but if you have any quick pointers that would be helpful.

I found that the issue is with the nozoom parameter. It works perfectly on a local version, but does not work on the deployed version on Vercel.
Works:
https://konviw.vercel.app/cpv/wiki/spaces/konviw/pages/32981?type=title&theme=light
Does not work:
https://konviw.vercel.app/cpv/wiki/spaces/konviw/pages/32981?type=title&theme=light&nozoom
Is the deployed version on Vercel up to date with the latest release?
The docs build issue is fixed in this PR: https://github.com/Sanofi-IADC/konviw/pull/296, and I also added a CI script to auto publish new versions of docs and also give visibility of failing docs builds within the PR.

@PiiXiieeS I noticed in the currently deployed docs that the embedded iFrames don't seem to be working (400 errors). I'm working on separating the package.json - I'll take a look at this too but if you have any quick pointers that would be helpful.

I found that the issue is with the nozoom parameter. It works perfectly on a local version, but does not work on the deployed version on Vercel.
Works: https://konviw.vercel.app/cpv/wiki/spaces/konviw/pages/32981?type=title&theme=light
Does not work: https://konviw.vercel.app/cpv/wiki/spaces/konviw/pages/32981?type=title&theme=light&nozoom
Is the deployed version on Vercel up to date with the latest release?
The docs build issue is fixed in this PR: #296, and I also added a CI script to auto publish new versions of docs and also give visibility of failing docs builds within the PR.

I fixed that.


[RESOLVED] High CPU utilization (over 90% for 5m)

Problem started at 16:43:24 on 2023.06.03
Problem name: High CPU utilization (over 90% for 5m)
Host: Zabbix server
Severity: Warning
Operational data: Current utilization: 97.86 %
Original problem ID: 23226
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=22384&eventid=23226

Problem has been resolved in 1m 0s at 16:44:24 on 2023.06.03
Problem name: High CPU utilization (over 90% for 5m)
Host: Zabbix server
Severity: Warning
Original problem ID: 23226


Filter and sort in the main view

Could there be a filter, with its corresponding sorting, in the main view?

Hi @jcsanchezrb
that 's a good idea - But at the moment not possible with the current design.
Best
didiatworkz

Superb.


Slower performance with 1.12.0 Fetching source index

I just happened upon 1.12.0 after release tonight, so maybe this is too soon to report this as a problem, but here's what I'm seeing consistently: about a 10 second increase in index time with 1.12.
[chrismo@momac bundler]$ cat Gemfile
source 'https://rubygems.org'

gem 'rack'
[chrismo@momac bundler]$ bundle --version
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
Bundler version 1.11.2
[chrismo@momac bundler]$ time bundle install --path zz
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
Fetching gem metadata from https://rubygems.org/...............
Fetching version metadata from https://rubygems.org/..
Installing rack 1.6.4
Using bundler 1.11.2
Bundle complete! 1 Gemfile dependency, 2 gems now installed.
Bundled gems are installed into ./zz.

real	0m4.837s
user	0m1.077s
sys	0m0.265s
[chrismo@momac bundler]$ gem install bundler -v 1.12.0
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
Fetching: bundler-1.12.0.gem (100%)
Successfully installed bundler-1.12.0
Parsing documentation for bundler-1.12.0
Installing ri documentation for bundler-1.12.0
Done installing documentation for bundler after 5 seconds
1 gem installed
[chrismo@momac bundler]$ rm -r zz
[chrismo@momac bundler]$ time bundle install --path zz
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
Fetching source index from https://rubygems.org/
Installing rack 1.6.4
Using bundler 1.12.0
Bundle complete! 1 Gemfile dependency, 2 gems now installed.
Bundled gems are installed into ./zz.

real	0m14.847s
user	0m7.124s
sys	0m1.269s

What's the output of bundle install --verbose for you on 1.12?

[chrismo@momac bundler]$ bundle install --verbose
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
Using rack 1.6.4
0:  rack (1.6.4) from /private/tmp/bundler/zz/ruby/2.2.0/specifications/rack-1.6.4.gemspec
Using bundler 1.12.0
0:  bundler (1.12.0) from /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source
Bundle complete! 1 Gemfile dependency, 2 gems now installed.
Bundled gems are installed into ./zz.```

I don't see how that could possibly be any slower, its not even making any network requests!

oh in that case, i didn't blow away the local zz dir I installed to. I did that and just re-ran with debug output:
[chrismo@momac bundler]$ rm -r zz
[chrismo@momac bundler]$ DEBUG=1 bundle 2>&1 | tee output.txt
/Users/chrismo/.rbenv/versions/2.2.4/bin/ruby: warning: RUBY_HEAP_MIN_SLOTS is obsolete. Use RUBY_GC_HEAP_INIT_SLOTS instead.
HTTP GET https://index.rubygems.org/versions
Bundler::Fetcher::CertificateFailureError: Could not verify the SSL certificate for https://index.rubygems.org/versions.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
/Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/downloader.rb:53:in `rescue in request'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/downloader.rb:41:in `request'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/downloader.rb:16:in `fetch'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:76:in `block in compact_index_client'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:23:in `call'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:23:in `update'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:63:in `update'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:54:in `update_and_parse_checksums!'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:63:in `available?'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:15:in `call'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/fetcher.rb:154:in `use_api'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `block in api_fetchers'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `select'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:331:in `api_fetchers'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:336:in `block in remote_specs'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/index.rb:10:in `build'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:335:in `remote_specs'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source/rubygems.rb:82:in `specs'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/lazy_specification.rb:56:in `__materialize__'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:91:in `block in materialize'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:88:in `map!'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/spec_set.rb:88:in `materialize'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/definition.rb:140:in `specs'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/definition.rb:129:in `resolve_remotely!'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:195:in `resolve_if_need'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:70:in `run'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/installer.rb:22:in `install'
  /Users/chrismo/.rbenv/rbenv.d/exec/gem-rehash/rubygems_plugin.rb:27:in `install'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli/install.rb:102:in `run'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli.rb:175:in `install'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/cli.rb:11:in `start'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/exe/bundle:27:in `block in <top (required)>'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
  /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/exe/bundle:19:in `<top (required)>'
  /Users/chrismo/.rbenv/versions/2.2.4/bin/bundle:23:in `load'
  /Users/chrismo/.rbenv/versions/2.2.4/bin/bundle:23:in `<main>'
HTTP GET https://index.rubygems.org/api/v1/dependencies
Fetching source index from https://rubygems.org/
Need to query more than 500 gems. Downloading full index instead...
HTTP GET https://rubygems.org/quick/Marshal.4.8/rack-1.6.4.gemspec.rz
HTTP 302 Moved Temporarily
HTTP GET https://rubygems.global.ssl.fastly.net/quick/Marshal.4.8/rack-1.6.4.gemspec.rz
HTTP 200 OK
Installing rack 1.6.4
0:  rack (1.6.4) from /private/tmp/bundler/zz/ruby/2.2.0/specifications/rack-1.6.4.gemspec
Using bundler 1.12.0
0:  bundler (1.12.0) from /Users/chrismo/.rbenv/versions/2.2.4/lib/ruby/gems/2.2.0/gems/bundler-1.12.0/lib/bundler/source
Bundle complete! 1 Gemfile dependency, 2 gems now installed.
Bundled gems are installed into ./zz.

full index download ...

Ah!
Bundler::Fetcher::CertificateFailureError: Could not verify the SSL certificate for https://index.rubygems.org/versions.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Would be the issue, most likely. @indirect want to check why the index.rg.org cert isn't being picked up?

Just to double-check, debug output with 1.11.2 appears to be fine. I can paste if you need - but I'm guessing you don't and it's long.

Nope, its the difference between connecting to bundler.rubygems.org and index.rubygems.org. We thought we updated the bundled CA certs in 1.12 for that change, but something must've slipped through.

Would that cause this situation: >100k specs in the index just before it says it needs to go download the whole index?

That should be the same between 1.12 and 1.11

cool

@segiddins PR rubygems/rubygems#1583 and associated PR #4448 might alleviate this? Since they generate/pick the certs programmatically and not via a manual process.

@RochesterinNYC nope, that PR wouldn't change anything related to this

Right now bundle install is ways faster with 1.11.2.
There has been a uri.host change affecting 1.12.x in 0904c9a (and maybe elsewhere) aiming for performance gains per 32ab479; Possibly still a work in progress.

I got the same issue just starting from today
with Bundler::Fetcher::CertificateFailureError
Worked around with downgrading bundler to 1.11.x

Anyone with this issue, I was able to resolve locally by ensuring i have a recent openssl installed and re-installing Ruby. What does ruby -ropenssl -e 'puts OpenSSL::OPENSSL_VERSION' output for those with problems? Mine used to be 1.0.2a (I think, I actually forgot to copy it before upgrading), it's now OpenSSL 1.0.2h  3 May 2016

@chrismo: I had the same issue yesterday and the workaround was to downgrade bundler to v1.11.2

@caioproiete I 'fixed' it in 1.12 by updating my openssl version. Can you share what version of openssl your ruby is linked to? ruby -ropenssl -e 'puts OpenSSL::OPENSSL_VERSION'

@chrismo Interesting. So apparently Ruby is not using the latest openssl I have on the machine.

Yeah, it has to be re-built is my understanding. So, presuming rbenv - rbenv uninstall 2.3.0 && rbenv install 2.3.0 is what I did.

I have rebuilt ruby but problem still exists
$ ruby -ropenssl -e 'puts OpenSSL::OPENSSL_VERSION'
OpenSSL 1.0.2h  3 May 2016

$ bundle update --verbose
HTTP GET https://index.rubygems.org/versions
Bundler::Fetcher::CertificateFailureError: Could not verify the SSL certificate for https://index.rubygems.org/versions.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Thanks @chrismo. Reinstalling Ruby fixed the issue.
I reinstalled Ruby:
rvm get stable
rvm reinstall ruby-2.3.0 --with-openssl-dir=`brew --prefix openssl`

and now it is using the latest OpenSSL installed:
$ ruby -r openssl -e 'puts OpenSSL::OPENSSL_VERSION'
OpenSSL 1.0.2h  3 May 2016

I then updated Bundler to v1.12.5, and it is as fast as v1.11.2.
$ bundler --version
Bundler version 1.12.5

$ bundle update --verbose
HTTP GET https://index.rubygems.org/versions
HTTP 206 Partial Content
Fetching gem metadata from https://rubygems.org/

Just try 1.12.5 again now it works without issue
I haven't re-install ruby or upgrade openssl since my last comment submitted

@chrismo this issue is resolved yea?

Yeah, I'd say so.


Shell randomly shuts down terminal

Hi,
I am fairly new to zsh and customisations.  I installed znap and have the following for my .zshrc file:
# start znap
source ~/git/zsh-snap/znap.zsh

# `znap prompt` makes your prompt appear in ~40ms. You can start typing right away!
znap prompt denysdovhan/spaceship-prompt

# Use `znap source` to load only those parts of Oh-My-Zsh or Prezto that you really need:
znap source sorin-ionescu/prezto
znap source sorin-ionescu/prezto \
  modules/{environment,completion,terminal,editor,history,directory,syntax-highlighting,history-substring-search,utilit
y}

znap source ohmyzsh/ohmyzsh \
  lib/{git,theme-and-appearance} \
  plugins/git

# Use `znap source` to load your plugins:
znap source zsh-users/zsh-completions
znap source zsh-users/zsh-syntax-highlighting
znap source momo-lab/zsh-abbrev-alias
znap source ael-code/zsh-colored-man-pages

SPACESHIP_PROMPT_SEPARATE_LINE=false
SPACESHIP_USER_SHOW=always

For some reason I am getting random crashes of my shell where it just shuts down in the middle of a session (sometimes at the start too) - I cannot see a pattern that is causing it to shutdown.  What is the easiest way to debug the shell?  Is there a way of seeing a log to see what is causing the shutdown?
Thank you,
Martyn

The easiest way to debug is to restart your shell with exec zsh -xv.

Did you notice there's an unwanted line break in this statement?
znap source sorin-ionescu/prezto \
  modules/{environment,completion,terminal,editor,history,directory,syntax-highlighting,history-substring-search,utilit
y}

Or is that just a copy-paste error?

If I fix that line break, your .zshrc file works just fine for me. I'm not seeing any crashes. Do you have any other config files and if so, what's in them? The full list of possible config files that Zsh reads on startup can be found here: http://zsh.sourceforge.net/Doc/Release/Files.html#Files-2

Did you notice there's an unwanted line break in this statement?
znap source sorin-ionescu/prezto \
  modules/{environment,completion,terminal,editor,history,directory,syntax-highlighting,history-substring-search,utilit
y}

Or is that just a copy-paste error?

I will check if that is an error when I get home.  I will also look at your other suggestions and try and work out what causes it to shutdown.
Thank you!

It seems to happen when I am holding down a key for some reason (eg holding down space while looking at the output of a more command).  It suddenly just closes?  I can't reproduce it reliably though.
Martyn

It seems to happen when I am holding down a key for some reason (eg holding down space while looking at the output of a more command).

That definitely has nothing to do with Znap. You could try asking for help on the Zsh mailing list: http://zsh.sourceforge.net/Arc/mlist.html

I can confirm this issue while using znap but I cannot reproduce it reliably either.
From a crash I've experimented a few mins ago as root : zsh: error on tty read: Input/output error
Unfortunately, I am unable to provide you with any additional information. This happens while running znap without any plugins or configuration.

@martynwheeler @notsocafe Can you reproduce the bug with this template?
$ znap pull
$ cd $(mktemp -d)  # Create a temp dir and enter it.
$ ZDOTDIR=$PWD HOME=$PWD exec zsh -f  # Restart Zsh without config files in this dir.
% source /path/to/zsh-snap/znap.zsh
% # Test and document the steps to reproduce the problem.

I have moved to a different distro and am no longer facing an issue
On Tue, 23 Mar 2021, 08:54 Marlon Richert, @.***> wrote:

@martynwheeler https://github.com/martynwheeler @notsocafe
https://github.com/notsocafe Can you reproduce the bug with this
template?
$ znap pull
$ cd $(mktemp -d)  # Create a temp dir and enter it.
$ ZDOTDIR=$PWD HOME=$PWD exec zsh -f  # Restart Zsh without config files in this dir.
% source /path/to/zsh-snap/znap.zsh
% # Test and document the steps to reproduce the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/marlonrichert/zsh-snap/issues/28#issuecomment-804730284,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGVUFNJFOSDF3TH2H3BSQLTFBJNPANCNFSM4XCMGISA
.

I'm also doubtful this is an issue with Znap. Apart from compiling scripts and functions in the background (which finished very quickly), Znap doesn't actively do anything after the shell has started up.


what is format parameter? in :formatter="format"

May I ask a beginner's question?
What is the parameter "format" in line :formatter="format"  within input tag?
I can't find this parameter in other place.
full input tag:
    <input
      ref="input"
      v-model="phone"
      type="tel"
      :placeholder="placeholder"
      :state="state"
      :formatter="format"
      :disabled="disabled"
      :required="required"
      :autocomplete="autocomplete"
      :name="name"
      :class="inputClasses"
      :maxlength="maxLen"
      @blur="onBlur"
      @input="onInput"
    >

@diamond520, good one! It was a prop of b-form-input since we used to use bootstrap before. We removed the bootstrap dependency but forgot to remove its legacy:
https://github.com/EducationLink/vue-tel-input/commit/3ada71c023aabfb833f07ce839d589720c52d359#diff-029d3271680c99a3ce1bf50ce7e838f8
I will remove it, thank you!

Closed by 1312cf537fae330ea34612fd581e85bedbd4ce07


Errors upgrading to Chef Infra Server 14.6.32

When installing Chef Infra Server 14.6.32 from scratch, I was having errors related to the oc-id integration with my Supermarket server.
I've created a paired down config with Test Kitchen to try and isolate the error.
I used the example format from https://docs.chef.io/server/config_rb_server_optional_settings/#oc-id-14
/etc/opscode/chef-server.rb looks like this:

# This file is managed by Chef. Manual modifications will be overwritten.
fqdn 'defaultcentos79-abc-xyz-123'
api_fqdn 'chef.vagrant.dev.local'
notification_email<EMAIL_ADDRESS>default_orgname 'videocloud'

license['nodes'] = 99999

estatsd['enable'] = true
estatsd['vip'] = '<IP_ADDRESS>'
estatsd['port'] = 8125
estatsd['protocol'] = 'statsd'
oc_id['applications'] ||= {}
oc_id['applications']['supermarket'] = {
'redirect_uri' => 'https://supermarket.mycompany.com/auth/chef_oauth2/callback',
}

rabbitmq['enable'] = false
rabbitmq['management_enabled'] = false
rabbitmq['queue_length_monitor_enabled'] = false
opscode_expander['enable'] = false
dark_launch['actions'] = false

And when I run chef-server-ctl reconfigure I get this error:

Recipe: private-chef::oc_id
* oc_id_application[supermarket] action create

================================================================================
Error executing action `create` on resource 'oc_id_application[supermarket]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
STDOUT: W, [2021-07-20T19:00:20.294254 #1126] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /opt/opscode/embedded/service/gem/ruby/2.7.0/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
CHEF_SECRETS_FD=5
I, [2021-07-20T19:00:20.294903 #1126] INFO -- : Raven 3.1.2 configured not to capture errors: DSN not set
STDERR: Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.19). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.19`.
Please specify a valid ruby command or the path of a script to run.
Run 'rails runner -h' for help.

undefined method `confidential' for #<Doorkeeper::Application:0x0000000008160eb0>
---- End output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
Ran veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' returned 1

Cookbook Trace: (most recent call first)
----------------------------------------
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:64:in `create!'
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:27:in `block (2 levels) in class_from_file'
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:26:in `block in class_from_file'

Resource Declaration:
---------------------
# In /var/opt/opscode/local-mode-cache/cookbooks/private-chef/recipes/oc_id.rb

205: oc_id_application name do
206: write_to_disk node['private_chef']['insecure_addon_compat']
207: redirect_uri app['redirect_uri']
208: only_if { is_data_master? }
209: end
210: end

Compiled Resource:
------------------
# Declared in /var/opt/opscode/local-mode-cache/cookbooks/private-chef/recipes/oc_id.rb:205:in `block in from_file'

oc_id_application("supermarket") do
action [:create]
default_guard_interpreter :default
declared_type :oc_id_application
cookbook_name "private-chef"
recipe_name "oc_id"
write_to_disk true
redirect_uri "https://supermarket.mycompany.com/auth/chef_oauth2/callback"
only_if { #code block }
end

System Info:
------------
chef_version=16.13.16
platform=centos
platform_version=7.9.2009
ruby=ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]
program_name=/opt/opscode/embedded/bin/chef-client
executable=/opt/opscode/embedded/bin/chef-client

Running handlers:
Running handlers complete
Chef Infra Client failed. 21 resources updated in 25 seconds
[2021-07-20T19:00:21+00:00] FATAL: Stacktrace dumped to /var/opt/opscode/local-mode-cache/chef-stacktrace.out
[2021-07-20T19:00:21+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2021-07-20T19:00:21+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: oc_id_application[supermarket] (private-chef::oc_id line 205) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
STDOUT: W, [2021-07-20T19:00:20.294254 #1126] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /opt/opscode/embedded/service/gem/ruby/2.7.0/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
CHEF_SECRETS_FD=5
I, [2021-07-20T19:00:20.294903 #1126] INFO -- : Raven 3.1.2 configured not to capture errors: DSN not set
STDERR: Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.19). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.19`.
Please specify a valid ruby command or the path of a script to run.
Run 'rails runner -h' for help.

undefined method `confidential' for #<Doorkeeper::Application:0x0000000008160eb0>
---- End output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
Ran veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' returned 1

This looks like a bug to me, but maybe I'm doing something out of the ordinary.  Can you see if you can reproduce this error?
To Reproduce

Start a CentOS 7.9 machine.
Download and install chef-server

curl -L -O https://packages.chef.io/stable/el/7/chef-server-core-14.6.32-1.el7.x86_64.rpm
yum install chef-server-core-14.6.32-1.el7.x86_64.rpm

edit /etc/opscode/chef-server.rb

fqdn 'chef.vagrant.dev.local'
api_fqdn 'chef.vagrant.dev.local'
notification_email<EMAIL_ADDRESS>
license['nodes'] = 99999

estatsd['enable'] = true
estatsd['vip'] = '<IP_ADDRESS>'
estatsd['port'] = 8125
estatsd['protocol'] = 'statsd'
oc_id['applications'] ||= {}
oc_id['applications']['supermarket'] = {
'redirect_uri' => 'https://supermarket.mycompany.com/auth/chef_oauth2/callback',
}

rabbitmq['enable'] = false
rabbitmq['management_enabled'] = false
rabbitmq['queue_length_monitor_enabled'] = false
opscode_expander['enable'] = false
dark_launch['actions'] = false

run chef-server-ctl reconfigure

And I get the error
Expected behavior
Chef Reconfigure should works successfulyl as per something like this:
Chef Infra Client finished, 413/884 resources updated in 02 minutes 05 seconds
Chef Server Reconfigured!
Actual behavior
Reconfigure fails and produces error:

Recipe: private-chef::oc_id
* oc_id_application[supermarket] action create

================================================================================
Error executing action `create` on resource 'oc_id_application[supermarket]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
STDOUT: W, [2021-07-20T19:00:20.294254 #1126] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /opt/opscode/embedded/service/gem/ruby/2.7.0/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
CHEF_SECRETS_FD=5
I, [2021-07-20T19:00:20.294903 #1126] INFO -- : Raven 3.1.2 configured not to capture errors: DSN not set
STDERR: Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.19). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.19`.
Please specify a valid ruby command or the path of a script to run.
Run 'rails runner -h' for help.

undefined method `confidential' for #<Doorkeeper::Application:0x0000000008160eb0>
---- End output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
Ran veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' returned 1

Cookbook Trace: (most recent call first)
----------------------------------------
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:64:in `create!'
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:27:in `block (2 levels) in class_from_file'
/var/opt/opscode/local-mode-cache/cookbooks/private-chef/resources/oc_id_application.rb:26:in `block in class_from_file'

Resource Declaration:
---------------------
# In /var/opt/opscode/local-mode-cache/cookbooks/private-chef/recipes/oc_id.rb

205: oc_id_application name do
206: write_to_disk node['private_chef']['insecure_addon_compat']
207: redirect_uri app['redirect_uri']
208: only_if { is_data_master? }
209: end
210: end

Compiled Resource:
------------------
# Declared in /var/opt/opscode/local-mode-cache/cookbooks/private-chef/recipes/oc_id.rb:205:in `block in from_file'

oc_id_application("supermarket") do
action [:create]
default_guard_interpreter :default
declared_type :oc_id_application
cookbook_name "private-chef"
recipe_name "oc_id"
write_to_disk true
redirect_uri "https://supermarket.mycompany.com/auth/chef_oauth2/callback"
only_if { #code block }
end

System Info:
------------
chef_version=16.13.16
platform=centos
platform_version=7.9.2009
ruby=ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]
program_name=/opt/opscode/embedded/bin/chef-client
executable=/opt/opscode/embedded/bin/chef-client

Running handlers:
Running handlers complete
Chef Infra Client failed. 21 resources updated in 25 seconds
[2021-07-20T19:00:21+00:00] FATAL: Stacktrace dumped to /var/opt/opscode/local-mode-cache/chef-stacktrace.out
[2021-07-20T19:00:21+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2021-07-20T19:00:21+00:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: oc_id_application[supermarket] (private-chef::oc_id line 205) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
STDOUT: W, [2021-07-20T19:00:20.294254 #1126] WARN -- : You are setting a key that conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at /opt/opscode/embedded/service/gem/ruby/2.7.0/gems/omniauth-1.3.2/lib/omniauth/auth_hash.rb:34. This can cause unexpected behavior when accessing the key as a property. You can still access the key via the #[] method.
CHEF_SECRETS_FD=5
I, [2021-07-20T19:00:20.294903 #1126] INFO -- : Raven 3.1.2 configured not to capture errors: DSN not set
STDERR: Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.19). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.19`.
Please specify a valid ruby command or the path of a script to run.
Run 'rails runner -h' for help.

undefined method `confidential' for #<Doorkeeper::Application:0x0000000008160eb0>
---- End output of veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' ----
Ran veil-env-helper --use-file -s chef-server.webui_key -s oc_id.sql_password -s oc_id.secret_key_base -- bin/rails runner -e production 'app = Doorkeeper::Application.find_or_create_by(:name => "supermarket");
app.update_attributes(:redirect_uri => "https://supermarket.mycompany.com/auth/chef_oauth2/callback");
puts app.to_json
' returned 1

https://github.com/chef/customer-bugs/issues/439

fixed with: https://docs.chef.io/release_notes_server/?v=14.7.13


adds padded gray box and styles the share link all pretty

What's this PR do?
Adds a new variable for our favorite lightest gray! Adds a new pattern for the padded gray box! Puts the custom share link in the padded gray box wherever it appears! Puts the social share buttons above the link!
How should this be reviewed?
tell us, how can we review, to test that this works
share modal:

voter reg modal:

competition modal:

Relevant tickets
Fixes #6923
Fixes #6919
Checklist

[ ] Tested on staging.

cc: @lkpttn @ngjo

👍


Use the DEFAULT_ORG variable instead of ID

Now, we have a variable DEFAULT_ORG in the settings and we should use it to set the default org of new objects.

Check/Update all models that are using default org by ID
Update the unit tests

I tried to do it because I thought it would be fast, but I was wrong. Other time...


BibTeX link doesn't work correctly

Looks like it's linking to the test DataCite API which presumably is down to some funky outcome of the logic here: https://github.com/NaturalHistoryMuseum/ckanext-doi/blob/main/ckanext/doi/theme/templates/doi/snippets/package_citation.html#L49?
As an example, the dataset: https://doi.org/10.5519/zi6w507p has a BibTeX link to https://api.test.datacite.org/dois/application/x-bibtex/10.5519/zi6w507p when it should be https://api.datacite.org/dois/application/x-bibtex/10.5519/zi6w507p (note the lack of "test" in the URL's domain).

This might be another issue with CKAN's DEBUG/debug config option that we keep running into at the moment

Maybe add a get_debug_value to ckantools.