Please add extension settings in order to add default "Color Based On" value

Is it possible to add vscode extension settings?
In particular there could be map style/theme selection (exactly like Geo Data Viewer has it)
plus I would really appreciate a possiblity to have default FillColor -> Color Based On
option selectable on extension setting rather than for each execution.
Moreover, is it possible to FillColor from a particular property that stores color ?
In that case Color Scale is not needed.
For example I have geojson created for www.geojson.io, which expect the color to be in "fill" property,
it would be awesome to have the possibility.

If my suggestions are possible  I will be a very happy to become monthly ko-fi supporter.

@PawelStadnicki this unfolded map renderer extension was a one off for me to show what's possible with maps in vscode notebooks. It's very low in terms of installs or dev interest in vscode extensions marketplace for me to consider this feature enhancement.
I don't plant to maintain it, but I'll accept PRs & republish if @heshan0131 or @ibgreen & team would like to contribute it.


Allows to mock the config during tests.

This PR adds a safe way to modify the vara config during tests.
This is achieved by replacing the config with a copy that is tuned for testing using a context manager or decorator. This also allows to write tests that need access to a more-or-less complete tool-suite and benchbuild setup.

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 24

Complexity increasing per file
==============================
- varats/tables/table.py  4
- varats/settings.py  1
- varats/tables/tables.py  3
- tests/test_utils.py  3
- varats/tables/__init__.py  2
- varats/tools/driver_table.py  11
- varats/tables/diff_correlation_overview_table.py  6
- tests/data/test_diff_correlation_overview_table.py  3

Clones added
============
- varats/tables/tables.py  1
- varats/tools/driver_plot.py  1
- varats/tools/driver_table.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 13

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  3
- tests/test_utils.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 13

Complexity increasing per file
==============================
- tests/test_utils.py  3
- tests/data/test_diff_correlation_overview_table.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- tests/test_utils.py  3
- tests/data/test_diff_correlation_overview_table.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/utils/test_experiment_util.py  1
- tests/test_utils.py  3
- tests/data/test_diff_correlation_overview_table.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/test_utils.py  3
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/utils/test_experiment_util.py  1
- tests/test_utils.py  3
- tests/data/test_diff_correlation_overview_table.py  2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 2

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  2
- tests/utils/test_experiment_util.py  1
- tests/test_utils.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 2

Complexity increasing per file
==============================
- tests/test_utils.py  3
- tests/data/test_diff_correlation_overview_table.py  2
- tests/utils/test_experiment_util.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  2
- tests/utils/test_experiment_util.py  1
- tests/test_utils.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 8

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  5
- tests/utils/test_experiment_util.py  1

Clones added
============
- varats/projects/c_projects/qemu.py  1
- varats/projects/c_projects/vim.py  2
- tests/test_utils.py  2
- varats/experiments/commit_annotation_report.py  1
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/opus.py  1
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/libvpx.py  1

Clones removed
==============
+ varats/experiments/vara_full_mtfa.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/projects/c_projects/glibc.py  -1
+ varats/projects/c_projects/busybox.py  -1
+ varats/projects/c_projects/openssl.py  -1
+ varats/experiments/just_compile.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/experiments/commit_report_experiment.py  -2
+ varats/experiments/phasar_env_analysis.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 8

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  5
- tests/utils/test_experiment_util.py  1

Clones added
============
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/opus.py  1
- varats/experiments/commit_annotation_report.py  1
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/vim.py  2
- varats/projects/c_projects/libvpx.py  1
- varats/projects/c_projects/qemu.py  1
- tests/test_utils.py  2
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/x264.py  1

Clones removed
==============
+ varats/projects/c_projects/glibc.py  -1
+ varats/projects/c_projects/busybox.py  -1
+ varats/experiments/commit_report_experiment.py  -2
+ varats/experiments/just_compile.py  -1
+ varats/projects/c_projects/openssl.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/experiments/phasar_env_analysis.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/experiments/vara_full_mtfa.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  5
- tests/utils/test_experiment_util.py  1

Clones added
============
- varats/projects/c_projects/qemu.py  1
- varats/projects/c_projects/vim.py  2
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/libvpx.py  1
- varats/experiments/commit_annotation_report.py  1
- varats/projects/c_projects/opus.py  1
- tests/test_utils.py  2
- tests/utils/test_experiment_util.py  4

Clones removed
==============
+ varats/experiments/commit_report_experiment.py  -2
+ varats/experiments/vara_full_mtfa.py  -1
+ varats/projects/c_projects/openssl.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/experiments/just_compile.py  -1
+ varats/projects/c_projects/busybox.py  -1
+ varats/projects/c_projects/glibc.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/experiments/phasar_env_analysis.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 6

Complexity increasing per file
==============================
- tests/test_utils.py  5
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2

Clones added
============
- varats/projects/c_projects/vim.py  2
- tests/test_utils.py  2
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/opus.py  1
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/libvpx.py  1
- varats/projects/c_projects/qemu.py  1
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/gravity.py  1

Clones removed
==============
+ varats/experiments/blame_report_experiment.py  -1
+ varats/projects/c_projects/openssl.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/projects/c_projects/busybox.py  -1
+ varats/experiments/commit_report_experiment.py  -1
+ varats/projects/c_projects/glibc.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- tests/test_utils.py  5
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2

Clones added
============
- tests/test_utils.py  2
- varats/projects/c_projects/opus.py  1
- varats/projects/c_projects/vim.py  2
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/qemu.py  1
- varats/projects/c_projects/libvpx.py  1
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/xz.py  3

Clones removed
==============
+ varats/projects/c_projects/busybox.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/projects/c_projects/openssl.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/experiments/commit_report_experiment.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/projects/c_projects/glibc.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- tests/test_utils.py  5
- tests/data/test_diff_correlation_overview_table.py  2
- tests/utils/test_experiment_util.py  1

Clones added
============
- tests/test_utils.py  2
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/libvpx.py  1
- varats/projects/c_projects/opus.py  1
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/vim.py  2
- varats/projects/c_projects/qemu.py  1

Clones removed
==============
+ varats/projects/c_projects/openssl.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/projects/c_projects/glibc.py  -1
+ varats/experiments/commit_report_experiment.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/projects/c_projects/busybox.py  -1
+ varats/projects/c_projects/lz4.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- tests/utils/test_experiment_util.py  1
- tests/data/test_diff_correlation_overview_table.py  2
- tests/test_utils.py  5

Clones added
============
- varats/projects/c_projects/xz.py  3
- varats/projects/c_projects/x264.py  1
- varats/projects/c_projects/opus.py  1
- varats/projects/c_projects/gravity.py  1
- varats/projects/c_projects/vim.py  2
- tests/utils/test_experiment_util.py  4
- varats/projects/c_projects/libvpx.py  1
- varats/projects/c_projects/qemu.py  1
- tests/test_utils.py  2

Clones removed
==============
+ varats/projects/c_projects/openssl.py  -1
+ varats/projects/c_projects/gzip.py  -1
+ varats/experiments/blame_report_experiment.py  -1
+ varats/projects/c_projects/lz4.py  -1
+ varats/experiments/commit_report_experiment.py  -1
+ varats/projects/c_projects/glibc.py  -1
+ varats/projects/c_projects/busybox.py  -1

See the complete overview on Codacy


Parsing error on Windows 10 Entreprise 10.0.10586

Hello,
I have the following issue with a Windows 10 Enterprise 10.0.10586 dump:
$ pypykatz -v lsa minidump -e -o test.txt ../lsass.dmp
INFO:root:Parsing file ../lsass.dmp
DEBUG:root:Found ThreadListStream @630 Size: 436
DEBUG:root:Found ModuleListStream @7f0 Size: 8860
DEBUG:root:Found Memory64ListStream @7a26 Size: 8176
DEBUG:root:Found SystemInfoStream @a4 Size: 56
DEBUG:root:Found MiscInfoStream @dc Size: 1364
DEBUG:root:Found SystemMemoryInfoStream @2a8c Size: 492
DEBUG:root:SystemMemoryInfoStream parsing is not implemented (Missing documentation)
DEBUG:root:Found ProcessVmCountersStream @2c78 Size: 152
DEBUG:root:ProcessVmCountersStream parsing is not implemented (Missing documentation)
DEBUG:root:Found UnusedStream @0 Size: 0
DEBUG:root:Found UnusedStream @0 Size: 0
DEBUG:root:Found UnusedStream @0 Size: 0
DEBUG:root:Found UnusedStream @0 Size: 0
DEBUG:pypykatz:None
INFO:pypykatz:===== BASIC INFO. SUBMIT THIS IF THERE IS AN ISSUE =====
INFO:pypykatz:CPU arch: X64
INFO:pypykatz:OS: Windows 10
INFO:pypykatz:BuildNumber: 10586
INFO:pypykatz:MajorVersion: 6
INFO:pypykatz:MSV timestamp:<PHONE_NUMBER>
INFO:pypykatz:===== BASIC INFO END =====
ERROR:root:Error while parsing file ../lsass.dmp
[...]
Exception: Memory address 0x002c002a is not in process memory space

pip install or git clone give the same output.

Currently a bit busy here, will look into this when I get the time.
(need 2 find that specific windows version to get to the prroblem)

this should be fixed now. pls check and close the issue

Thanks for the update, it works fine.

Exception: Memory address 0x0a0007d0 is not in process memory space


Add new actions (add, upsert, get, getAll) (rebased on top of latest)

Basically #3 but with TokenPassport modifications removed (fixed in #5). @matmunn I kept you as author of the commit, hope that's okay.

@matmunn Do you have any examples on how to use upsert, upsertList, add? Thinking about adding some simple docs to the readme for each method (including the get* methods).


Trusty Unity  install freezing Chomebook when logging out

I have installed trusty with unity and chrome targets. When I logout of unity, it freezes my entire chromebook. Also, when using ctrl shift alt F1, it takes two key presses to switch back to the chroot from chrome os. Not sure if that has anything to do with it.
Is there a log or something I can see to try to troubleshoot?

@mojo6911 are you sure you are logging out as in exit from the chroot shell? Some DEs lets you "power off" and will shut down the whole chromebook from the chroot.

Yes, I am hitting "log out" and then confirming logout. It exits back to ChromeOS, but it is completely frozen. No mouse or keyboard response, whatsoever.

@mojo6911 is the chromebook on or off? any lights or signs that it is on?

Yes, the screen is powered on. I see the ChromeOS, just as I left it, but it is completely frozen. I have to hold down the power button and turn it back on.

@mojo6911 try making a chroot with xfce, if xfce logs out ok, and leaves ChromeOS up and usable, then unity could be broken.

@mojo6911 Please give the output of croutonversion This sounds like #1475 if so then please close this issue it is tracked there.

chronos@localhost / $ sudo enter-chroot -n trusty
Entering /mnt/stateful_partition/crouton/chroots/trusty...
(trusty)b0b@localhost:~$ croutonversion
crouton: version 1-20150511154233~master:392b84e4
release: trusty
architecture: amd64
xmethod: xorg
targets: xfce,unity,chrome
host: version 6812.83.0 (Official Build) stable-channel swanky
kernel: Linux localhost 3.10.18 #1 SMP Mon Apr 27 10:22:23 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: no

@mojo6911 Yep same issue as #1475 . Best solution if you want to exit the chroot, is to switch to chromeos and press ctrl-c in the shell window where you started the chroot. Just don't use the logout.  Please close this issue since it is already tracked in #1475. Thanks.

i had the same issue and closing the laptop and opening it backup usually fixed the problem and if it didn't i plugged in an external mouse


Added implementation for /v2/types/{entityType}

Fix for #119
Updated specification/quantumleap.yml for API method call.
Added query_1TNENA.py for handling APIs.
Added test_1TNENA.py for test cases related to API

@pooja1pathak should I go ahead and merge?

yes you can merge this in master :-)


[FALSE-POSITIVE]

Domains or links
Please list any domains and links listed here which you believe are a false positive.
More Information
How did you discover your web site or domain was listed here?

Website was hacked
Incorrectly marked as Phishing on Phishtank or OpenPhish?

Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelistings.
Additional context
Add any other context about the problem here.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR on the whitelist.me file

https://github.com/mitchellkrogza/Phishing.Database/blob/master/whitelist.me/whitelist.me
Please include the same above information to help speed up the whitelisting process.

whats your domain name? I don't have time to search through 500,000

If you can not provide me your domain name so I can whitelist you I am closing this


cmake opt-ins for E57_MAX_DEBUG, E57_VERBOSE and E57_MAX_VERBOSE

libE57Format has some internal conditional compilation for additional checks and logging.
This change puts these in reach of cmake.

Thanks Nigel.
Could you please remove the commented-out #defines for these in src/Common.h as well? No need for them with this PR.

In fact, why not put E57_DEBUG (default on) and E57_WRITE_CRAZY_PACKET_MODE (default off) in the cmake as well?

Sure.  Why not.

Done.

Thanks Nigel!

Thank you!


Alertmanager 422 response code doesn't show reason

Such as Opsgenie integration.
If you set wrong or not applicable string in field of Opsgenie. Thats just show
priority: P4
alertmanager level=error ts=2019-11-01T07:30:15.047Z caller=notify.go:367 component=dispatcher msg="Error on notify" err="cancelling notify retry for \"opsgenie\" due to unrecoverable error: unexpected status code 422"
alertmanager level=error ts=2019-11-01T07:30:15.047Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"opsgenie\" due to unrecoverable error: unexpected status code  ││ 422"

https://github.com/prometheus/alertmanager/blob/94d875f1227b29abece661db1a68c001122d1da5/notify/notify.go#L367
Opsgenie returns response body when this cases. This is useful if you try to send alert and get 422 but don't know what is wrong
{"message":"Request body is not processable. Please check the errors.","errors":"priority":"should be one of [ P1, P2, P3, P4, P5 ]"}

This is fixed with the latest Alertmanager release. Here is what I get from my side:
level=error ts=2019-11-04T08:43:57.082Z caller=dispatch.go:266 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"opsgenie\" due to unrecoverable error: unexpected status code 422: {\"message\":\"Request body is not processable. Please check the errors.\",\"errors\":{\"priority\":\"should be one of [ P1, P2, P3, P4, P5 ]\"},\"took\":0.001,\"requestId\":\"e08b61f2-cff3-4704-9ddf-33cf12258d47\"}"

For some reason, I'm getting this error even though I'm passing through a correct "P" value through my notification template.
{{ define "opsgenie.myorg.priority"}}  	{{ range .Alerts }} 		{{ if eq .Labels.severity "critical"}} 			P1 		{{ else }} 			P3 		{{ end }}  	{{ end }} {{ end }}
Is my block defined incorrectly?
error message:
level=error ts=2020-01-03T05:36:34.129Z caller=dispatch.go:301 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"opsgenie\" due to unrecoverable error: unexpected status code 422: {\"message\":\"Request body is not processable. Please check the errors.\",\"errors\":{\"priority\":\"should be one of [ P1, P2, P3, P4, P5 ]\"},\"took\":0.001,\"requestId\":\"c4589a15-34e6-4530-8dde-d45f3557f6f4\"}"

@romenyrr if you have more that one alert then the value can be P1P1P3...

@romenyrr if you have more that one alert then the value can be P1P1P3...

is there a solution for this scenario? how do we make multiple alerts not concatenate the P value into one big string?

@romenyrr if you have more that one alert then the value can be P1P1P3...

is there a solution for this scenario? how do we make multiple alerts not concatenate the P value into one big string?

The solution is to group the alerts by severity.
Here's a draft that you should be able to draw inspiration from:
  config:
    route:
      group_by: [severity]
    routes:
    - receivers:
       - name: opsgenie
         opsgenie_configs:
         - priority: {{ if eq .GroupLabels.severity "critical"}}P1{{else if eq .GroupLabels.severity "warning"}}P2{{else}}P3{{end}}


chore: test-python-jenkins to 0.0.5

chore: Promote test-python-jenkins to version 0.0.5

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Footnote support

I found it doesn't work. Does it?

Hi,
Parsedown, which is the package Laravel-Markdown is using, is based on the GitHub flavoured markdown, which does not support footnotes.


clarify scaling on withdrawals from RPC nodes

When fetching withdrawal information, we perform an RPC query to get a Block.
The Withdrawal::amount field is documented to be in Giga Wei.
We pass that through unaltered to trace_decoder, which treats it as an amount of eth.
This feels wrong

I think the issue is just on naming (my bad, I'm the one who originally wrote it). Amount transfers are processed in wei (to only deal with integer arithmetic), hence the $10^9$ scaling to convert the GWEI amounts of withdrawals to the lowest denomination, WEI. It should be named gwei_to_wei for consistency as we only use this method for withdrawals, though technically we proceed to the same shift hence why it was passing fine (and breaking if not applied).


[BACKLOG-21806][BACKLOG-21868] - Cleanup feature file so it will only…

… include bundles it needs

Build Skipped
:white_check_mark: There was nothing to build. The changes are probably excluded by the build rules. If this is an error, please contact your system administrator.


recent change to workaround #6 causes errors for me

I get lots of errors, although it seems to run the test:
>> doctest({'doctest'})
doctest ................................................ cat: invalid option -- 'X'
Try 'cat --help' for more information.
cat: invalid option -- 'X'
Try 'cat --help' for more information.
cat: invalid option -- 'X'
Try 'cat --help' for more information.
cat: invalid option -- 'X'
Try 'cat --help' for more information.
warning: connection to external pager lost (pid = 5300)
warning: flushing pending output (please wait)
PASS    6/6

Summary:

   PASS    6/6

1/1 targets passed, 0 without tests.

>>

This is surely related to my PAGER override :disappointed: Which operating system are you using?

GNU/Linux, Fedora 22, fairly stock.

Hm, I have a hard time reproducing. I've commented it out for now, could you have a glance (e326c57727eb39e3bb4487250edaf357be7e0690)?

You have to add PAGER_FLAGS('-', 'local'); to the override

Yes, that PAGER_FLAGS fixes those cat errors for me.


TA Review (HA): Implement Grammar

Summary
The following feedback should be implemented:

[x] Each cause should have its own label
[x] Definition of hazards should be more specific
[x] Some failures are just restating failure modes (Ex H4-2)
[x] Each cause should have its own recommended action and requirement. Reuse should refer to its first appearance (Ex. H1-2a)
[x] No hazards related to saving user data
[x] The second recommended action seems to be saying two things, since the user disconnecting is the cause of the hazard in the first place

Deadline
Jan 8th, 2024
Estimated Work Hours
2 Hours

HA updated to fix all TA feedback. In response to the "No hazards related to saving user data", the scope of the project changed and so no user data is being saved.

Completed in commit ID: 071fe99b40d19bf45277384b4a737ea5530ae219


⚠ Samsung has degraded performance

In 62cec08, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2352 ms

Resolved: Samsung performance has improved in 2cd15b2.


If Url is too long layout won't be shown

I have the main.js code below:
const app = express();

app.set('view engine', '.ejs');
app.set('layout', '../layouts/layout');

app.use('/public', express.static('public'));

app.get('/books/:bookId', getBookHandler);
app.get('/books/edit/:bookId', updateBookHandler);

If I open /books/1 the default layout is shown, but if I use /books/edit/1 the layout is no longer shown.
If I specify the layout explicitly, it doesn't work either.
If I change app.get('/books/edit/:bookId', updateBookHandler); to app.get('/test/:bookId', updateBookHandler); it works again.
My package.json
{
  "version": "1.0.0",
  "type": "module",
  "scripts": {
    "dev": "nodemon src/server/main.js",
    "start": "cross-env NODE_ENV=production node src/server/main.js",
    "build": "vite build"
  },
  "devDependencies": {
    "nodemon": "^3.1.4",
    "vite": "^5.0.2"
  },
  "dependencies": {
    "normalize.css": "^8.0.1",
    "express": "^4.18.2",
    "ejs": "^3.1.10",
    "express-ejs-layouts": "^2.5.1",
    "vite-express": "*",
    "cross-env": "^7.0.3"
  }
}

I have founded the cause!
In my head.ejs file I had the following:
<link rel="stylesheet" href="../css/header.css">
<link rel="stylesheet" href="../css/...">

I don't know if I understand it correctly, but the path to the styles changes, depending on the URL, but my styles working both on /authors/ and on /.
The solution is change paths to the CSS files:
<link rel="stylesheet" href="/css/header.css">
<link rel="stylesheet" href="/css/...">


Feature: Support automatically configuring uWSGI pass

Hi there,
We're currently not seeing distributed tracing being automatically configured when using a uwsgi_pass. It'd be ideal if this just worked upon loading of the module (similar to how HTTP proxy passes function). Would something like that be feasible as a feature?

Looking at functions with names like propagate_*_context in datadog_directive.cpp, our auto-propagation works by injecting configuration directives that tell these *_pass features to include headers relevant to tracing. The configuration directives are:

proxy_set_header for proxy_pass
fastcgi_param for fastcgi_pass
grpc_set_header for grpc_pass

It looks like we could use uwsgi_param in a manner analogous to how we use fastcgi_pass. This stackoverflow question makes me think that uWSGI has an HTTP_* convention for request headers -- I'd have to make sure that trace context is extracted that way by Datadog tracers (e.g. dd-trace-py).
Yeah, this is something we could implement.
For good measure, please also submit a feature request. The relevant "Impact" is "General Issue."
No promises on timeline.

The newest release, cut today, contains these changes.


Alphabetical order for name (A...Z a...z)

Not sure If we should capitalize initials by default. Also users could try to break the system by doing n/ABC vs n/aBc

Addressed in UG


Could the potion change show immideatly like in OSBuddy?

Currently it takes 1 minute or something before it shows "next change in xx seconds"
Could it show instantly like in OSbuddy?

but maybe show a "guess" right from the start, which may be incorrect like you say, but also might be correct, until it can show the 'for sure' correct one.

We could save the stat drain timer before the logout and then load it on login.

This should be already sort of implemented.


[WFCORE-325] : Allow socket-binding-group-refType to override default-interface.

Now you can redefine the default-interface in the socket-bindings element of a server definition in the host.xml like this :

Or in the domain.xml you may redefine the default-interface of a socket-binding-group like this:

Jira: https://issues.jboss.org/browse/WFCORE-325

Windows Build 724 is now running using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1

Linux Build 1012 is now running using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1

Core - Full Integration Build 299 is now running using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1

Windows Build 724 outcome was SUCCESS using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1
Summary: Tests passed: 2932, ignored: 95 Build time: 0:15:56

Linux Build 1012 outcome was SUCCESS using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1
Summary: Tests passed: 2932, ignored: 95 Build time: 0:19:52

Core - Full Integration Build 299 outcome was SUCCESS using a merge of 63d67f592abfd475d71223a9e36cc1d1be8d0de1
Summary: Tests passed: 2833, ignored: 430 Build time: 0:42:54


#230: Trains maintain their lanes

Fix submodule dependencies refs - point their master branch last commit
Submodule CSUtil.CameraControl updated from 420ec1 to a3b6cf
420ec1 was right ref
a3b6cf was your old
Submodule OptionsFramework updated from 802338 to 0da293
The same here
802338 - good
0da293 - old


fix error with missing id

on a fresh install I was getting this error:
** (Phoenix.LiveView.HTMLTokenizer.ParseError) lib/terminal_component.ex:9:7: attribute "phx-update" requires the "id" attribute to be set
    (phoenix_live_view 0.18.0-dev) lib/phoenix_live_view/html_engine.ex:1038: Phoenix.LiveView.HTMLEngine.validate_phx_attrs!/5
    (phoenix_live_view 0.18.0-dev) lib/phoenix_live_view/html_engine.ex:521: Phoenix.LiveView.HTMLEngine.handle_token/2
    (elixir 1.12.2) lib/enum.ex:2385: Enum."-reduce/3-lists^foldl/2-0-"/3
    (phoenix_live_view 0.18.0-dev) lib/phoenix_live_view/html_engine.ex:124: Phoenix.LiveView.HTMLEngine.handle_body/1
    (phoenix_live_view 0.18.0-dev) expanding macro: Phoenix.LiveView.Helpers.sigil_H/2
    lib/terminal_component.ex:7: Underthehood.TerminalComponent.render/1
    (elixir 1.12.2) lib/kernel/parallel_compiler.ex:319: anonymous fn/4 in Kernel.ParallelCompiler.spawn_workers/7

Thanks a lot!
This is quite embarrassing -- the PR makes perfect sense, of course. 🤦

@iwarshak Thanks again for catching this brown-paper-bag bug! ❤  I have no idea how that went unnoticed, my best explanation is that I've had some local modifications to the checkout when testing. 🤦
I now released version 0.1.3 of this package, including your fix. It now appears to work as intended. 😊


Make page after toc page 1

Is there a line that can be added to the YAML or the tex file so that the page number starts from the first page after the table of contents?

I've been using
header-includes:
  - \setcounter{page}{0} # So that the titlepage is the zeroth page

for the title page. I haven't tried this with the TOC though.

Thanks for the reply. Sadly using a title page and TOC it makes the title page jump around - it seems to be set to always be on page 1. Also, need to remove page number from bottom of initial pages.
Assuming need to setcounter, change page counter that title page appears, and add if statement to not show page number on pages 0 or below.

it seems to me, that in the default pandoc latex template \frontmatter is used before \maketitle, which would resolve the numbering issue.
for the time beeing i used in https://github.com/cagix/pandoc-thesis something like this as a workaround:
\usepackage{xpatch}
\xapptocmd{\frontmatter}{\setcounter{page}{3}}{}{}

(to be used as "header-include")

Bump, it'd be really neat with a flag for setting the page after title, and, if any, the TOC, to be page 1. And the page in the footer would be excluded on the title page, and the TOC page.

Hello,
I would like this for generating word files from markdown as well.


No registered object with name: PoseRendererGpu; Unable to find Calculator "PoseRendererGpu"

When i use mediapipe_holistic_tracking.aar in my android project, I get this Error:
No registered object with name: PoseRendererGpu; Unable to find Calculator "PoseRendererGpu"
mediapipe v0.8.7
build env : macOS 10.15.7
Here is my steps:
1.   build mediapipe_holistic_tracking.aar

WORKSPACE file: I use mediapipe-master/WORKSPACE,  and i deleted ios reference content , and edit sdk/ndk value to:

android_sdk_repository(
    name = "androidsdk",
    build_tools_version = "28.0.3",
    path = "/Users/zhengying/Library/Android/sdk",
)

android_ndk_repository(
    name = "androidndk",
    path = "/Users/zhengying/Library/Android/sdk/ndk/20.0.5594570",
)

BUILD file :  I use /Users/usename/doc/mediapipe-master/mediapipe/examples/android/src/java/com/google/mediapipe/apps/holistictrackinggpu/BUILD ,
the BUILD file all content is :

load("//mediapipe/java/com/google/mediapipe:mediapipe_aar.bzl", "mediapipe_aar")

mediapipe_aar(
    name = "mediapipe_holistic_tracking",
    calculators = ["//mediapipe/graphs/holistic_tracking:holistic_tracking_gpu_deps"],
)

bazel command :

bazel build -c opt --strip=ALWAYS   --host_crosstool_top=@bazel_tools//tools/cpp:toolchain
--fat_apk_cpu=arm64-v8a,armeabi-v7a
//mediapipe/examples/android/src/java/com/google/mediapipe/apps/holistictrackinggpu:mediapipe_holistic_tracking.aar

copy the aar package to project lib directory.

2 build binary graph
bazel command :
bazel build -c opt mediapipe/graphs/holistic_tracking:holistic_tracking_gpu

then copy holistic_tracking_gpu.binarypb and  mediapipe/modules/holistic_landmark/hand_recrop.tflite    to my project asserts directory .
this steps refer to https://google.github.io/mediapipe/getting_started/android_archive_library.html#steps-to-build-a-mediapipe-aar
3 this is my referenced code :
        eglManager = new EglManager(null);
        processor = new FrameProcessor(this,eglManager.getNativeContext(),
                "holistic_tracking_gpu.binarypb","input_video","output_video");
        processor.getVideoSurfaceOutput().setFlipY(true);

        ProtoUtil.registerTypeName(NormalizedLandmarkList.class, "mediapipe.NormalizedLandmarkList");

        processor.addPacketCallback("holistic_landmarks", new PacketCallback() {
            @Override
            public void process(Packet packet) {
                Log.d(TAG,  " packetCount " + i++);
                try {
                    NormalizedLandmarkList poseLandmarks = PacketGetter.getProto(packet, NormalizedLandmarkList.class);
                    String marks = getPoseLandmarksDebugString(poseLandmarks);
                    if (frameNum >= frameCount) return;
                    frameNum++;
                } catch (InvalidProtocolBufferException exception) {
                    Log.e(TAG, "Failed to get proto.", exception);
                }
            }
        });

when i use mediapipe_pose_tracking.aar (get from mediapipe v0.8.6) in my project, it not get this error.
complete error message:
E/AndroidRuntime: FATAL EXCEPTION: ExternalTextureConverter
    Process: com.ai.yijian, PID: 22445
    com.google.mediapipe.framework.MediaPipeException: not found: ValidatedGraphConfig Initialization failed.
    No registered object with name: PoseRendererGpu; Unable to find Calculator "PoseRendererGpu"
        at com.google.mediapipe.framework.Graph.nativeStartRunningGraph(Native Method)
        at com.google.mediapipe.framework.Graph.startRunningGraph(Graph.java:324)
        at com.google.mediapipe.components.FrameProcessor.startGraph(FrameProcessor.java:553)
        at com.google.mediapipe.components.FrameProcessor.maybeAcceptNewFrame(FrameProcessor.java:421)
        at com.google.mediapipe.components.FrameProcessor.onNewFrame(FrameProcessor.java:439)
        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.renderNext(ExternalTextureConverter.java:403)
        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.lambda$onFrameAvailable$0$ExternalTextureConverter$RenderThread(ExternalTextureConverter.java:338)
        at com.google.mediapipe.components.ExternalTextureConverter$RenderThread$$ExternalSyntheticLambda1.run(Unknown Source:4)
        at android.os.Handler.handleCallback(Handler.java:900)
        at android.os.Handler.dispatchMessage(Handler.java:103)
        at android.os.Looper.loop(Looper.java:219)
        at com.google.mediapipe.glutil.GlThread.run(GlThread.java:141)
E/RtgSchedManager: endActivityTransaction: margin state not match

Hi @wingdi , Could  you please find the duplicate issue https://github.com/google/mediapipe/issues/1994#issuecomment-892270523

Hi @wingdi , Could you please find the duplicate issue #1994 (comment)

Yes, i have read that comment before, that not solve my problem.   I build gpu verison , not cpu verison

Can you double check if you use the latest version of https://github.com/google/mediapipe/blob/master/mediapipe/graphs/holistic_tracking/holistic_tracking_gpu.pbtxt? I don't see that the holistic graph uses the pose gpu renderer and not sure why "PoseRendererGpu" is required. The holistic tracking gpu graph has its standalone rendering component at https://github.com/google/mediapipe/blob/master/mediapipe/graphs/holistic_tracking/holistic_tracking_gpu.pbtxt#L58.

@jiuqiant  very thanks your reply .
Today i  use the lastest code build to generate the new holistictrackinggpu.aar and holistic_tracking_gpu.bin, and put them in my project.   But i didn't find relative *.tflite file in path " //mediapipe/modules/holistic_landmark ", in the path i only find a hand_recrop.tflite.  And i put hand_recrop.tflite in project's assets folder.   does the .tflite is necessary ?  After running my project, It did't have previous error, but i got this Error:
java.lang.ExceptionInInitializerError
        at com.google.common.flogger.backend.Platform$LazyHolder.access$100(Platform.java:65)
        at com.google.common.flogger.backend.Platform.getCallerFinder(Platform.java:189)
        at com.google.common.flogger.FluentLogger.forEnclosingClass(FluentLogger.java:70)
        at com.google.mediapipe.framework.Graph.<clinit>(Graph.java:33)
        at com.google.mediapipe.components.FrameProcessor.initializeGraphAndPacketCreator(FrameProcessor.java:139)
        at com.google.mediapipe.components.FrameProcessor.<init>(FrameProcessor.java:96)
        at com.ai.yijian.test.BaseMediaPipeActivity.onCreate(BaseMediaPipeActivity.java:85)

I thinks this maybe because lacking relative .tflite file,  how can i get/generate *.tflite file ?
thanks.


Does not match expected packet size

Sometimes when I type the help command（ ./mcrcon -p "password" -H IP -P Port "help"）, it returns "Warning: recv() return value (1408) does not match expected packet size (3133)."

Same for me i have no idea what is due too

The fix was easy simply fork it and do this https://github.com/joinandplaycoop/mcrcon/commit/30c39b7ddfe526621d60b30644d6d84df0180e35

Sometimes when I type the help command（ ./mcrcon -p "password" -H IP -P Port "help"）, it returns "Warning: recv() return value (1408) does not match expected packet size (3133)."

What Minecraft server version you are using?

If your not port forwarding a specific port you set in the server.properties file for the RCON in the server folder then the RCON will not work. I had the same problem when trying to connect to port 25560 but when i tried to connect to my server port which was 25565 that port was being port forwarded it said what it told you what you will have to do is specify something other then port 25565 in the server.properties file in the server folder for the RCON port and then you will have to change the enabled rcon to true then specify a password which i would reccomend doing and when your typing in the ip make sure its your public ip and not your private ip address then it should work fine

I'm having this issue too.
I tried both mcrcon and rconc and both produced the same error complaining insufficient read byte numbers. And the error occurs inconsistently, i.e. command sometimes succeeds.
I'm using Spigot server for Minecraft version 1.14.4

I think this SO post explains it.
In some situation data transmission may be fragmented and recv should handle this case but mcrcon does not.

@northkillz thank you!
This internet protocol and recv() fragmentation behaviour is definately something I had overlooked and I will probably merge your pull request after some testing.
But there is something that bothers me. According to my tests /help command shouldn't even produce packets bigger than ~500 bytes.
Original issue description mentions expected packet size of 3133 which suggests that the server is trying to send more data than I would ever expect from /help command response.
First I was thinking it might be trying to send multi-packet responses (it's in Source RCON spec but wasn't supported by Minecraft at the time mcrcon was written) but maximun allowed single packet size is 4096 so it doesn't make sense to split the packet if the response size is only 3133 bytes.
For now I cannot reproduce the problem on my local network (with Vanilla 1.14.4 or Spigot 1.14.4) so it's still kinda mystery what exactly is going on.
I would be grateful if someone could provide pcap packet capture when this problem happens.
!!! Be careful not to include password in the capture !!!

When I issue help, server returns
/advancement (grant|revoke)
/ban <targets> [<reason>]
/ban-ip <target> [<reason>]
/banlist [ips|players]
/bossbar (add|get|list|remove|set)
/clear [<targets>]
/clone <begin> <end> <destination> [filtered|masked|replace]
/data (get|merge|modify|remove)
/datapack (disable|enable|list)
/debug (report|start|stop)
/defaultgamemode (adventure|creative|spectator|survival)
/deop <targets>
/difficulty [easy|hard|normal|peaceful]
/effect (clear|give)
/enchant <targets> <enchantment> [<level>]
/execute (align|anchored|as|at|facing|if|in|positioned|rotated|run|store|unless)
/experience (add|query|set)
/fill <from> <to> <block> [destroy|hollow|keep|outline|replace]
/forceload (add|query|remove)
/function <name>
/gamemode (adventure|creative|spectator|survival)
/gamerule (announceAdvancements|commandBlockOutput|disableElytraMovementCheck|disableRaids|doDaylightCycle|doEntityDrops|doFireTick|doLimitedCrafting|doMobLoot|doMobSpawning|doTileDrops|doWeatherCycle|keepInventory|logAdminCommands|maxCommandChainLength|maxEntityCramming|mobGriefing|naturalRegeneration|randomTickSpeed|reducedDebugInfo|sendCommandFeedback|showDeathMessages|spawnRadius|spectatorsGenerateChunks)
/give <targets> <item> [<count>]
/help [<command>]
/kick <targets> [<reason>]
/kill <targets>
/list [uuids]
/locate (Buried_Treasure|Desert_Pyramid|EndCity|Fortress|Igloo|Jungle_Pyramid|Mansion|Mineshaft|Monument|Ocean_Ruin|Pillager_Outpost|Shipwreck|Stronghold|Swamp_Hut|Village)
/loot (give|insert|replace|spawn)
/me <action>
/msg <targets> <message>
/op <targets>
/pardon <targets>
/pardon-ip <target>
/particle <name> [<pos>]
/playsound <sound> (ambient|block|hostile|master|music|neutral|player|record|voice|weather)
/recipe (give|take)
/reload
/replaceitem (block|entity)
/save-all [flush]
/save-off
/save-on
/say <message>
/schedule function <function> <time>
/scoreboard (objectives|players)
/seed
/setblock <pos> <block> [destroy|keep|replace]
/setidletimeout <minutes>
/setworldspawn [<pos>]
/spawnpoint [<targets>]
/spreadplayers <center> <spreadDistance> <maxRange> <respectTeams> <targets>
/stop
/stopsound <targets> [*|ambient|block|hostile|master|music|neutral|player|record|voice|weather]
/summon <entity> [<pos>]
/tag <targets> (add|list|remove)
/team (add|empty|join|leave|list|modify|remove)
/teammsg <message>
/teleport (<destination>|<location>|<targets>)
/tell -> msg
/tellraw <targets> <message>
/time (add|query|set)
/title <targets> (actionbar|clear|reset|subtitle|times|title)
/tm -> teammsg
/tp -> teleport
/trigger <objective> [add|set]
/w -> msg
/weather (clear|rain|thunder)
/whitelist (add|list|off|on|reload|remove)
/worldborder (add|center|damage|get|set|warning)
/xp -> experience

(I inserted new lines for readability)
I don't have any knowledge of RCON protocol, but if it's sent as ascii, that would be 2616 bytes (+ 10 bytes of header). I can't provide packet captures, because I'm using private tunnel to access the server, so packets are encrypted.
Anyway the only RCON protocol spec. I could find is Valve's Source RCON protocol, There's guarantee that data greater than maximum possible size (4096) will be split. But it does not mention the other case. So I think the behavior of sending data lesser than 4096 bytes is implement specific.

Thank you.
That output listing was helpful. Looks like new server versions are pushing the help listing without pagination which explains the bigger packet sizes and makes the fragmentation problem more likely.
So basically they changed the behaviour a bit. Too bad they still didn't fix missing newlines in vanilla server.
Anyway, I merged your patch and it should be fine for now.


Problems linking with (external) Spectrum MPI

I would like to build Open-CE to use the system installed MPI library, which is IBM Spectrum MPI.  I am building Open-CE in a Singularity image based on the Docker image here:
https://github.com/open-ce/open-ce/blob/master/images/builder-cuda-ppc64le/Dockerfile.cuda-10.2
I am running the build on a system with Spectrum MPI installed to a path that is exposed to the image with a -B binding.  I am running the following command:
./open-ce/open-ce/open-ce build env --output_folder /path/to/condabuild --mpi_types system --build_types cuda --cuda_versions 10.2 ./open-ce-environments/envs/lightgbm-env.yaml

When building LightGBM, cmake fails to find MPI:
-- Could NOT find MPI_C (missing: MPI_C_WORKS)
-- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS)
CMake Error at /dev/shm/anaconda/conda-bld/lightgbm-base_1613696077157/_build_env/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find MPI (missing: MPI_C_FOUND MPI_CXX_FOUND)

      Reason given by package: MPI component 'Fortran' was requested, but language Fortran is not enabled.

Looking at the CMakeError.txt output, I can see that it fails to find some dependent libraries like libopen-pal and libopen-rte while trying a test link:
/dev/shm/anaconda/conda-bld/lightgbm-base_1613696077157/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: warning: libopen-rte.so.3, needed by /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-2020.08.19/lib/libmpi_ibm.so, not found (try using -rpath or -rpath-link)
/dev/shm/anaconda/conda-bld/lightgbm-base_1613696077157/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: warning: libopen-pal.so.3, needed by /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-2020.08.19/lib/libmpi_ibm.so, not found (try using -rpath or -rpath-link)
/dev/shm/anaconda/conda-bld/lightgbm-base_1613696077157/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: warning: libz.so.1, needed by /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-2020.08.19/lib/libmpi_ibm.so, not found (try using -rpath or -rpath-link)
/dev/shm/anaconda/conda-bld/lightgbm-base_1613696077157/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: warning: libhwloc_ompi.so.15, needed by /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-2020.08.19/lib/libmpi_ibm.so, not found (try using -rpath or -rpath-link)

I have nearly hacked around the problem by listing a set of libraries in LDFLAGS, however that leads to another problem.
Is there a recommended way to build with Spectrum MPI?
I could perhaps add it to the container image, but I'm wondering if there are other recommended steps.  Thanks.

I'm looking into this.

@adammoody - What is the path in the image where spectrum MPI libs are present?
I tried installing spectrum-mpi using conda install spectrum-mpi -c https://public.dhe.ibm.com/ibmdl/export/pub/software/server/ibm-ai/conda in the container itself and did the LightGBM build using the command you mentioned, and it went just fine.

Thanks for looking into this, @npanpaliya .  I don't currently have Spectrum MPI installed in the image.  Instead it is installed on the host system on which the image is running, and that external MPI is exposed by starting the image with a -B option listing that host install path.  I want to be sure that the Open-CE build is compatible with the MPI library that is installed on the host and figured that was safer than installing a different MPI in the image itself which could be a different version or even the same version but configured in a different way that makes it incompatible.
Having said that, I'll try the conda install spectrum-mpi step you mention here as a potential work around / fix.  I'll get back to you on that.  In case we end up needing to build against this external Spectrum MPI, I'll also provide more detail on my setup.
We have multiple versions of Spectrum MPI installed on the host system, and each is installed to its own directory path.  At any given time, one of those is identified as the default, though users can select other versions if needed.  For now, I'm just trying to build Open-CE against our default MPI.  This happens to be installed to a path like: /path/to/spectrum-mpi/spectrum-mpi-rolling-release-xl-2020.11.12.  In starting the Singularity image, this external directory tree on the host is bound into the image with singularity shell -B /path/to/spectrum-mpi open-ce-builder.sif.
Before running the opence command, I also add the bin and lib directories for MPI to PATH and LD_LIBRARY_PATH so that mpicc is in the path and to help any configure step that might rely on the lib path:
# add path to pick up system install of Spectrum MPI
export PATH="/path/to/spectrum-mpi/spectrum-mpi-rolling-release-xl-2020.11.12/bin:$PATH"
export LD_LIBRARY_PATH="/path/to/spectrum-mpi/spectrum-mpi-rolling-release-xl-2020.11.12/lib:$LD_LIBRARY_PATH"

./open-ce/open-ce/open-ce build env --output_folder /path/to/condabuild --mpi_types system --build_types cuda --cuda_versions 10.2 ./open-ce-environments/envs/lightgbm-env.yaml

It's under this configuration that CMake throws the above error when testing for MPI.  It tries to link a test program, and that link fails because it can't find a number of libraries that libmpi_ibm.so depends on.  I have found that I can help CMake find those libraries by listing all of those libraries in LDFLAGS like so:
export LDFLAGS="-L/path/to/spectrum-mpi/spectrum-mpi-rolling-release-xl-2020.11.12/lib -lopen-pal -lopen-rte -levent_pthreads -lhwloc_ompi -levent -L/usr/lib64 -lz"

That almost works, but then some of those settings lead to other problems.
In case we end up needing to build against this external Spectrum MPI, are you able to reproduce this?

I can verify that conda install spectrum-mpi leads to a successful build:
conda install spectrum-mpi -c https://public.dhe.ibm.com/ibmdl/export/pub/software/server/ibm-ai/conda

In particular, those CMake tests for LightGBM now pass:
-- Found MPI_C: /dev/shm/anaconda/lib/libmpiprofilesupport.so (found version "3.1")
-- Found MPI_CXX: /dev/shm/anaconda/lib/libmpiprofilesupport.so (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- MPI libraries: /dev/shm/anaconda/lib/libmpiprofilesupport.so/dev/shm/anaconda/lib/libmpi_ibm.so
-- MPI C++ libraries: /dev/shm/anaconda/lib/libmpiprofilesupport.so/dev/shm/anaconda/lib/libmpi_ibm.so

Hopefully those packages will work.  Thanks, @npanpaliya .
That also sheds a clue on why CMake is failing to link with my external MPI library.  I can see that the Spectrum MPI that is installed by conda has an embedded RPATH setting of $ORIGIN/. and so it finds its dependent libs in the same directory where it is installed:
Singularity> readelf -d /dev/shm/anaconda/lib/libmpi_ibm.so | grep RPATH
 0x000000000000000f (RPATH)              Library rpath: [$ORIGIN/.]

Singularity> ldd /dev/shm/anaconda/lib/libmpi_ibm.so
        linux-vdso64.so.1 =>  (0x00007ffff7f90000)
        libopen-rte.so.3 => /dev/shm/anaconda/lib/./libopen-rte.so.3 (0x00007ffff7d10000)
        libopen-pal.so.3 => /dev/shm/anaconda/lib/./libopen-pal.so.3 (0x00007ffff7c20000)
        librt.so.1 => /lib64/librt.so.1 (0x00007ffff7be0000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00007ffff7bb0000)
        libhwloc_ompi.so.15 => /dev/shm/anaconda/lib/./libhwloc_ompi.so.15 (0x00007ffff7b30000)
        libm.so.6 => /lib64/libm.so.6 (0x00007ffff7a40000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007ffff7a10000)
        libevent-2.1.so.6 => /dev/shm/anaconda/lib/./libevent-2.1.so.6 (0x00007ffff7980000)
        libevent_pthreads-2.1.so.6 => /dev/shm/anaconda/lib/./libevent_pthreads-2.1.so.6 (0x00007ffff7940000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ffff7900000)
        libc.so.6 => /lib64/libc.so.6 (0x00007ffff7710000)
        /lib64/ld64.so.2 (0x00007ffff7fb0000)

There is an RPATH entry in my external Spectrum MPI library, but it looks like it still points to a temporary build path and not the install location:
Singularity> readelf -d /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-rolling-release/lib/libmpi_ibm.so | grep RPATH
 0x000000000000000f (RPATH)              Library rpath: [/__SMPI_build_dir_______________________________________/exports/optimized/lib:/__SMPI_build_dir________________________/hwloc/hwloc-2.0.3p0_ompi-cuda-10.1-libevent-2.1.8/hwloc_install/lib:/__SMPI_build_dir________________________/libevent/libevent-2.1.8/lib]

Singularity> ldd /usr/tce/packages/spectrum-mpi/ibm/spectrum-mpi-rolling-release/lib/libmpi_ibm.so
        linux-vdso64.so.1 =>  (0x00007ffff7f90000)
        libopen-rte.so.3 => not found
        libopen-pal.so.3 => not found
        librt.so.1 => /lib64/librt.so.1 (0x00007ffff7dd0000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00007ffff7da0000)
        libz.so.1 => /lib64/libz.so.1 (0x00007ffff7d60000)
        libhwloc_ompi.so.15 => not found
        libm.so.6 => /lib64/libm.so.6 (0x00007ffff7c70000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007ffff7c40000)
        libevent-2.1.so.6 => not found
        libevent_pthreads-2.1.so.6 => not found
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ffff7c00000)
        libc.so.6 => /lib64/libc.so.6 (0x00007ffff7a10000)
        /lib64/ld64.so.2 (0x00007ffff7fb0000)

I'm guessing that maybe if I fix the RPATH in my external installed Spectrum MPI lib that might fix things.  I suppose that could be done the forceful way with chrpath or readelf, but maybe there is a better way?
Do you know if anything was done to address that in the spectrum-mpi installed by conda?

Thank you @adammoody for summarizing your setup. I'll try recreate the problem and see how it can be fixed.
I'm also checking spectrum-mpi conda recipe and don't see any special setting for RPATHs. I'll explore more on this and revert.

I found that I can get LightGBM to build with my system install of Spectrum MPI, but I had to do two things.
First, I set the RPATH in my Spectrum MPI libraries with something like:
chrpath -r '$ORIGIN' libmpi_ibm.so
chrpath -r '$ORIGIN' libmpiprofile.so

For good measure, I also did this with libopen-rte.so and libopen-pal.so, though I'm not sure those are really necessary.
That resolved the missing MPI libs.  However, I still hit a problem in the CMake configure step due to undefinded symbols from libz, like deflate.
/dev/shm/anaconda/conda-bld/lightgbm-base_1614122849133/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: warning: libz.so.1, needed by /usr/global/tools/opence/blueos_3_ppc64le_ib_p9/singularity/tempsmpi/spectrum-mpi/lib/libmpi_ibm.so, not found (try using -rpath or -rpath-link)
/dev/shm/anaconda/conda-bld/lightgbm-base_1614122849133/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: /usr/global/tools/opence/blueos_3_ppc64le_ib_p9/singularity/tempsmpi/spectrum-mpi/lib/libopen-rte.so.3: undefined reference to `inflateEnd'
/dev/shm/anaconda/conda-bld/lightgbm-base_1614122849133/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld: /usr/global/tools/opence/blueos_3_ppc64le_ib_p9/singularity/tempsmpi/spectrum-mpi/lib/libopen-rte.so.3: undefined reference to `deflate'

To get past that, I also set LDFLAGS to point to the libz in my anaconda/lib like so:
export LDFLAGS="-L/dev/shm/anaconda/lib -lz"

The link uses ld from this package:
/dev/shm/anaconda/conda-bld/lightgbm-base_1614122849133/_build_env/bin/../lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/../../../../powerpc64le-conda_cos7-linux-gnu/bin/ld

Apparently that ld doesn't know to link to libs in either /usr/lib64 or the conda lib directory, both of which have contain a libz.so.
I think this second step is not needed when using the conda-installed Spectrum MPI, because libmpi_ibm.so is installed into the conda lib directory anaconda/lib, so that then the RPATH entry of $ORIGIN/. in libmpi_ibm.so happens to point the same directory that also contains a libz.so.

This does seem to track back to using powerpc64le-conda_cos7-linux-gnu/bin/ld when trying to link to libraries outside of the conda/lib directory, like an external install of Spectrum MPI.  I can reproduce this problem excluding Open-CE with just a CMake build of a simple MPI project using the conda-installed gcc/ld tools.
A simple MPI program:
// testmpi.c
#include <stdlib.h>
#include "mpi.h"
int main (int argc, char* argv[])
{
  MPI_Init(&argc, &argv);
  MPI_Finalize();
  return 0;
}

A CMakeLists.txt file to build the program:
# CMakeLists.txt
PROJECT(TESTMPI)
CMAKE_MINIMUM_REQUIRED(VERSION 2.8)
FIND_PACKAGE(MPI REQUIRED)
ADD_EXECUTABLE(testmpi testmpi.c)
INSTALL(PROGRAMS testmpi DESTINATION bin)

Commands to install anaconda, cmake, and gcc/ld, then attempt to build under that environment.
bash ./Miniconda3-latest-Linux-ppc64le.sh -b -f -p anaconda
source anaconda/bin/activate
conda install -y cmake gxx_linux-ppc64le=7.3

mkdir build
cd build
cmake ../

This fails with the same errors reported above.
Setting LDFLAGS to point to those external libs just before the cmake command resolves the problem:
export LDFLAGS="-L/path/to/spectrum-mpi/lib -lopen-rte -lopen-pal -lhwloc_ompi -levent -levent_pthreads -L/usr/lib64 -lz"

I'm still not sure of the best fix yet, but these pages also shed some light on things.
This page describes the conda compiler tools and their motivation:
https://www.anaconda.com/blog/utilizing-the-new-compilers-in-anaconda-distribution-5
It sounds the goal is to set the tools up to make it hard to build against software outside of conda by design, in order to be sure that the resulting package only has internal dependencies.  That makes sense.
In fact, the ld being used apparently takes measures to avoid linking to system software.  The link_libgcc entry in gcc specs file has been modified to add an rpath to the anaconda lib directory where internal dependencies are expected to be installed:
https://conda.io/projects/conda-build/en/latest/resources/compiler-tools.html#
The specs file being used here seems to be at anaconda/lib/gcc/powerpc64le-conda_cos7-linux-gnu/7.3.0/specs
One could perhaps modify that same gcc specs file to list -L flags to other directories, like the path to the external install of Spectrum and libz, though that seems like a big hammer:
https://stackoverflow.com/questions/7493620/inhibit-default-library-paths-with-gcc
Another idea I've seen suggested is to place symlinks to the external libs in the anaconda/lib directory, which would make it seem as though the software is installed in anaconda.  I haven't tried that yet.
I'm still searching for clean ways to request that version of ld to link to external libs with less hacking.

The system compiler workaround should resolve this issue, but we opened a new issue to specifically address this shortcoming:
https://github.com/open-ce/open-ce-builder/issues/104


feat: export macros

The new macros EXTISM_EXPORT_AS and EXTISM_EXPORTED_FUNCTION enable easily exporting functions from code similar to how library functions are exported on other platforms, avoiding the need to modify linker flags to export functions.
For example:
EXTISM_EXPORT_AS("count_vowels")
int32_t count_vowels(void) {...}

or even easier:
int32_t EXTISM_EXPORTED_FUNCTION(count_vowels)(void){...}

I'm happy to make another PR updating the docs and examples if we think these methods should be the default way to export functions.
EXTISM_EXPORT_AS was intentionally not named EXTISM_EXPORT in-case something like EMSCRIPTEN_KEEPALIVE can be done some day, avoiding including the export name in the macro. Unfortunately, the technique used by EMSCRIPTEN_KEEPALIVE is not viable as it uses a special clang backend https://github.com/WebAssembly/tool-conventions/issues/64

Cool, I think EXTISM_EXPORT_AS makes a lot of sense, but I wonder if the EXTISM_EXPORTED_FUNCTION should just include the return type and empty parameter list like:
#define EXTISM_EXPORTED_FUNCTION(f) EXTISM_EXPORT_AS(#f) int32_t f(void)

EXTISM_EXPORTED_FUNCTION(test){
    ...
}

On one hand it's a little more opaque, but on the other it reduces the number of possible errors when defining a function that is going to be exported. What do you think?

If extism exported functions always have to return an int32_t and we don't expect to change it, that sounds reasonable. I'd then also typedef int32_t ExtismReturn; and use that instead in-case we do change it.

Added. Set to void instead of empty parameter list to avoid users accidentally passing unused arguments.


odd behaviour of new_with_braces fixer

The PHP version you are using:
$ php -v
PHP 7.0.25
PHP CS Fixer version you are using:
$ php-cs-fixer -V
PHP CS Fixer 2.7.2
@@ -22,7 +22,7 @@ final class DateAndTimeOfTimeslot

     public static function fromDateTime(\DateTimeInterface $dateTime): self
     {
-        return new static(
+        return new static()(
             new DateTimeImmutable($dateTime->format(\DateTime::ISO8601))
         );
     }

This is applied by the new_with_braces fixer. Is this to be expected?

Thanks for reporting!
Currently @julienfalque is working on a patch related to this;
https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3208

Thanks for the report, this definitely looks like a bug. I suspect it has the same cause than #3202, could you check whether #3208 fixes the issue?

#3208 does not fix it.

Ok, thanks for checking, I'll have a look then.

@alcohol #3208 has been merged with additional work from @SpacePossum regarding this issue so it should be fixed.


Create usage examples

Please create examples to see how to use CRFSuite in nodejs

[ ] Train a dataset
[ ] Tag a test sample

Hello!
I would like to use node-crfsuite but I would really need some doc/example. Could you add some in the examples folder?

I have had an intent to add the examples, including format of training/tagging data. Before i have done or wait someone can help. There are several real projects used node-crfsuite that you can refer to.

https://github.com/vntk/vntk-tagger/blob/master/experiment.js
https://github.com/cuongcnb/kv-tagger
https://github.com/SimonBoorer/node-ingredient-phrase-tagger


Upgrade buttons say Error checking upgrades even if their specific library was not removed

Version - master 2/4
Steps:

Add glusterfs catalog with newest version
Go to main stack page (not how the Upgrade button says "Up to date"
Go to settings page
Disable or enable the community Contributed library

Results:  You will get sent back to Stack page and the glusterfs stack now says "Error checking upgrades"
Expected:  glusterfs is not part of the community library, so it shouldn't be in error.

This is just another way in which you're changing the catalog setting, it restarts the catalog API, and it's not up yet when you go ask for upgrade info.  Don't we already have an issue for that?

Version - master 3/8
Yes, I think we have another issue for this.


python3Packages.nix-prefetch-github: 6.0.1 -> 7.0.0

Description of changes
nix-prefetch-github was update to version 7.0.0.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Looks good! There are a few dozen usages of nix-prefetch-github in update scripts -- could those be updated in this PR to use the new hash field?

Do I need to do anything?

I added some commits to do this in https://github.com/seppeljordan/nixpkgs/pull/1. Can you review and merge into this PR if it looks good to you?

We're a bit unlucky: https://github.com/NixOS/nixpkgs/pull/242130 introduced a conflict as well.

@tjni I addressed the conflict.

Result of nixpkgs-review pr 242092 run on aarch64-darwin 1

1 package marked as broken and skipped:

solana-validator

20 packages built:

element-desktop
element-desktop-wayland
emacsPackages.evil-textobj-tree-sitter
emacsPackages.evil-tree-edit
emacsPackages.helm-tree-sitter
emacsPackages.pygn-mode
emacsPackages.symex
emacsPackages.tree-sitter
emacsPackages.tree-sitter-ess-r
emacsPackages.tree-sitter-indent
emacsPackages.tree-sitter-ispell
emacsPackages.tree-sitter-langs
emacsPackages.tsc
lemmy-server
nix-prefetch-github (python310Packages.nix-prefetch-github)
nix-prefetch-github.dist (python310Packages.nix-prefetch-github.dist)
python311Packages.nix-prefetch-github
python311Packages.nix-prefetch-github.dist
schildichat-desktop
schildichat-desktop-wayland

We have another (more complicated) merge conflict in https://github.com/NixOS/nixpkgs/pull/242979/. Do you mind if I take over this PR? It is taking awhile to get committed, and I feel bad that you have to deal with all of these conflicts related to what I've asked you to push.

@tjni sure, go ahead.

Continued in https://github.com/NixOS/nixpkgs/pull/243018.


Update SlackUploadFileStep help-channel to use channel ID instead of …

…channel name to fix misleading docs issue

Testing done

Submitter checklist

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Ok, I thought it would support both. But tried many times. Only id worked. Neither channel-name nor #channel-name was able to work. I had a look at the source code. Yes some support codes were there. But no result. Maybe this is a bug. Let me check it out again.


Use the command building DSL

Coverage remained the same at 100.0% when pulling 66cefab04819f0bd6dc584da17ece803c7b78755 on command_dsl into a5b8a21496e1341b1ad1a2101abd09541f299551 on master.


Make apiRoot empty by default

Fix #157

Coverage remained the same at 100.0% when pulling 76b08f3588e4c831646b1e292e48aa2c9708feef on refactor/api-root into 06e6206cb7ffaabfc87431392975906df96355cb on master.


Bump Garden Linux VM to latest image

Description
Bumping the image used for Garden Linux testing.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
Green CI should be enough.

Once stackrox/kernel-packer#256 is merged and the crawler adds the packages, this PR should have a passing Garden Linux test.


Request: Config property or build variable for debugging production builds (allowing console.log and enabling Vue devtools)

Figuring out how to enable console.logs and Vue devtools in production build took me longer than I'd like to admit :X
As for the dev-property, I think the docs aren't clear enough of what this does.
How about a property like debugProduction: true in nuxt.config.js
Or npm run generate --debug
that set the following:
  dev: true,

  vue: {
    config: {
      productionTip: true,
      devtools: true,
    },
  },

And add this to the docs on a new page, maybe "Debugging" or "Troubleshooting"

We are approaching the Nuxt 2 EOL date (June 30, 2024) - see this article for more information. I'm closing this issue as it's marked as a Nuxt 2 related enhancement and it's not a critical issue.
That doesn't mean it might not be relevant for Nuxt 3. If it is, please feel free to open a new issue (or just comment, and I can reopen it). 🙏
Thank you for your understanding and for your contribution to Nuxt! 🎉


(PUP-9185) Fix logging exceptions at debug level

Puppet.log_exception had an option to change the log level which only
worked in a very specific case (where the exception is a
Puppet::ParseErrorWithIssue and the message argument is :default).
This makes the argument work consistently.

Interesting, were there other tests relying on this bug?

Nothing else tried to use this feature as far as I could tell.

Well I thought I ran this with everything, maybe it stopped working when I rebased it. I'll look into it.

CLA signed by all contributors.


Integrate MegaLinter Github Action into Workflow

Mega linter has a Github Action that can easily be added to the existing workflow. This will help with code reviews by adding markdown validation, spell check, and other useful linting checks. You'll need to disable config validation as we intentionally have malformed config files for testing.

Hi, I would like to take this issue. I have a PR in progress already: https://github.com/Boeing/config-file-validator/pull/218
My solution:

Add the megalinter githab action, include the security steps.
Lint the code as necessary to ensure pipeline success.

If the number of commits in my PR are excessive, I will squash them together.

Ready for review: https://github.com/Boeing/config-file-validator/pull/218


TypeError on simple request

After the most basic setup, as included in the README.md:
>>> import requests
>>> from requests_cloudkit import CloudKitAuth
>>> auth = CloudKitAuth(key_id=YOUR_KEY_ID, key_file_name=YOUR_PRIVATE_KEY_PATH)
>>> requests.get("https://api.apple-cloudkit.com/database/[version]/[container]/[environment]/public/zones/list", auth=auth)

I am getting the following error:
File "/opt/anaconda3/[...]/lib/python3.7/site-packages/requests_cloudkit/cloudkit.py", line 45, in make_signature
signature = "{}:{}:{}".format(formatted_date, self.encode_body(body), path)
File "/opt/anaconda3/[...]/lib/python3.7/site-packages/requests_cloudkit/cloudkit.py", line 62, in encode_body
h = hashlib.sha256(body)
TypeError: Unicode-objects must be encoded before hashing
I have tried encoding the body variable within the encode_body() method, but that did not change anything. I have also tried multiple key files and multiple containers, still no change (All of these work normally with CloudKitJS or my custom Java wrapper).

I'm getting the same issue! Have you made any progress here?

Actually, encoding the body variable in the encode_body method helped me (just pulled latest master of this repo) past that error. Still getting 401 unauthorized though, so not sure if it's reading the private key correctly

Hey, I was playing with the whole code for multiple days and eventually found a way around. Will try to find the solution during the weekend and send it here.

@matyasbohacek did you get past this? I'm still trying to get a CSV dump of CloudKit data. TX

@app4g I got past this, but the workaround endpoint eventually got shut down by Apple, which led me to choose a different DB. Sorry for the bad news!


Gray screen

Environment data

VS Code version: 1.57.1
Jupyter Extension version (available under the Extensions sidebar): 2021.6.999406279
Python Extension version (available under the Extensions sidebar): 2021.6.944021595
OS (Windows | Mac | Linux distro) and version: W10
Python and/or Anaconda version: 3.8.8 64-bit
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): CONDA
Jupyter server running: Local | Remote | N/A: Local

Expected behaviour
Showing notebook while running
Actual behaviour
I was training an RL model usign stable lines 3 with pytorch cuda versión. suddently during training the screen turned gray. I cannot even see the taskbar for saving the model or stoping the kernel.
It says the cell is still running, but I do not know for shure. I think it is since the GPU's fans are still working hard.

Steps to reproduce:
Not sure, I have trained the same model before without issues

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)
Output is empty

XXX

Sorry for the trouble @svh02.
Could you upload the output from the Jupyter output panel and the Developer Tools panel? (Help | Toggle Developer Tools, and View | Output)
Thanks.

Hi David,
I restarted de app and is now working fine. So I wont be able to upload the output.
Thanks for the answer. I will keep working and hopefully it won't cause any more trouble

Good to know that its working!
Feel free to reopen this issue if it happens again.


Collective selection truncated on virtual card page

https://opencollective.com/opencollective/admin/host-virtual-cards
It should show the full name of what you click.

Is this the same issue, on the host reports screen when filtering by a Collective

By design, we show the avatar of the collective instead of the name in these multi-pickers to save some space. Maybe we could do that only when there are a few selected? Ping @opencollective/design


Add support for cargo --explain

The error messages in the compiler are being tweaked and will likely drop the
rustc --explain part of the error message in favor of --explain. In that
case you're expected to basically take whatever tool you're using and pass
--explain to it with an error code, so let's add it to Cargo as well!

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

r? @brson
cc @wycats, @jonathandturner, @nikomatsakis

May want to not merge this until https://github.com/rust-lang/rust/pull/32756 is approved, but may also be good regardless either way.

Should all subcommands that can pass-through errors support this too? E.g. cargo build => error with explain => user tries cargo build --explain E0000.

Hm perhaps? We need to be careful about hijacking top-level arguments, however, as cargo subcommands may be using them in various ways.

I think I prefer leaving it just cargo --explain for now and see if it ends up causing confusion.

:umbrella: The latest upstream changes (presumably #2590) made this pull request unmergeable. Please resolve the merge conflicts.

@bors r+

:pushpin: Commit f73d55a has been approved by brson

:lock: Merge conflict

@bors: r=brson 8dad57e

:hourglass: Testing commit 8dad57e with merge b462d50...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Binary Representation

💥 Proposal
A binary representation where we will calculate maximum 0's between 1's and vice versa.
Have you read the [Contributing Guidelines on Pull Requests]
YES

/assign


The path signature must be unique even for distinct HTTP methods

Kiota fails to generate the SDK when it detects that the same path signature was used multiple times even if the HTTP method is different:
Error:
OpenAPI error: #/paths//businessunits/{id} - The path signature '/businessunits{}' MUST be unique.
For:
GET /businessunits/{id}
PUT /businessunits/{name}
Expected:
Allow paths resolving to same template but with different methods

Hi @Aburel ,
Thanks for using kiota and for reaching out.
If you try to change name by ID in the description, and change potential path parameters, do you still get the same error?

Hi @baywet,
Thanks for your reply.
Same issue when using:
GET /businessunits/{id}
PUT /businessunits/{id}
Like the error states, the path signature '/businessunits{}' MUST be unique

Hey everyone,
Can you share a small description to repro it please?

Hi @baywet,
Here are step by step instructions:

I created a C$ controller:
==> Note that both the POST and the DELETE methods have the same route signature.

[ApiController]
[Route("v1/tests")]
public class TestController : Controller
{
    [HttpPost]
    [Route("{key}/emails/{emailId}/attachments/{clientKey}/")]
    public async Task<ActionResult> UploadAttachment(Guid key, int emailId, Guid clientKey)
    {
        return Ok();
    }

    [HttpDelete]
    [Route("{key}/emails/{emailId}/attachments/{attachmentKey}")]
    public async Task<ActionResult> DeleteAttachment(Guid key, int emailId, Guid attachmentKey)
    {
        return Ok();
    }
}

generated the swagger file:

openapi: 3.0.1
info:
  title: Internal VelocityApi - v1
  version: v1
servers:
  - url: /
paths:
  '/v1/tests/{key}/emails/{emailId}/attachments/{clientKey}':
    post:
      tags:
        - Test
      parameters:
        - name: key
          in: path
          required: true
          schema:
            type: string
            format: uuid
        - name: emailId
          in: path
          required: true
          schema:
            type: integer
            format: int32
        - name: clientKey
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Success
  '/v1/tests/{key}/emails/{emailId}/attachments/{attachmentKey}':
    delete:
      tags:
        - Test
      parameters:
        - name: key
          in: path
          required: true
          schema:
            type: string
            format: uuid
        - name: emailId
          in: path
          required: true
          schema:
            type: integer
            format: int32
        - name: attachmentKey
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Success

I tried generating a typescript sdk using this command:
kiota generate --co -l typescript -c testV1 -o ./src/testSdk -d TestApi.swagger.yaml

I got this error:

fail: Kiota.Builder.KiotaBuilder[0]
      OpenAPI error: #/paths//v1/tests/{key}/emails/{emailId}/attachments/{attachmentKey} - The path signature '/v1/tests/{}/emails/{}/attachments/{}' MUST be unique.

I hope this helps recreating the issue.
Thanks

Thanks for sharing the context.
Out of curiosity, if you replace those two lines:
    [Route("{key}/emails/{emailId}/attachments/{attachmentKey}")]
    public async Task<ActionResult> DeleteAttachment(Guid key, int emailId, Guid attachmentKey)

by
    [Route("{key}/emails/{emailId}/attachments/{clientKey}")]
    public async Task<ActionResult> DeleteAttachment(Guid key, int emailId, Guid clientKey)

Do you still get the error?

After the update suggested above, the error message changes to:
fail: Kiota.Builder.KiotaBuilder[0]
      OpenAPI error: #line=33 - (Lin: 33, Col: 2, Chr: 695) - (Lin: 33, Col: 64, Chr: 757): Duplicate key

what does the description look like after the update?

The description after the update is:
fail: Kiota.Builder.KiotaBuilder[0]
OpenAPI error: #line=33 - (Lin: 33, Col: 2, Chr: 695) - (Lin: 33, Col: 64, Chr: 757): Duplicate key

Can you also share the OpenAPI description that is generated? This will help us. Thanks!

C# code:
[ApiController]
[Route("v1/tests")]
public class TestController : Controller
{
    [HttpPost]
    [Route("{key}/emails/{emailId}/attachments/{clientKey}/")]
    public async Task<ActionResult> UploadAttachment(Guid key, int emailId, Guid clientKey)
    {
        return Ok();
    }

    [HttpDelete]
    [Route("{key}/emails/{emailId}/attachments/{clientKey}")]
    public async Task<ActionResult> DeleteAttachment(Guid key, int emailId, Guid clientKey)
    {
        return Ok();
    }
}

OpenAPI generated:
openapi: 3.0.1
info:
  title: Internal VelocityApi - v1
  version: v1
servers:
  - url: /
paths:
  '/v1/tests/{key}/emails/{emailId}/attachments/{clientKey}':
    post:
      tags:
        - Test
      parameters:
        - name: key
          in: path
          required: true
          schema:
            type: string
            format: uuid
        - name: emailId
          in: path
          required: true
          schema:
            type: integer
            format: int32
        - name: clientKey
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Success
    delete:
      tags:
        - Test
      parameters:
        - name: key
          in: path
          required: true
          schema:
            type: string
            format: uuid
        - name: emailId
          in: path
          required: true
          schema:
            type: integer
            format: int32
        - name: clientKey
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Success

Note that the above OpenAPI text will be accepted by Kiota. No error!

Thanks for the additional information.
Since this was an issue with the description that didn't conform with the specification, and since kiota is behaving as expected, I'll go ahead and close it.
Let us know if you need anything else.

Can you please explain what description did not confirm to the specification? And also, what specification is that?
I provided an example of valid code where Kiota reports errors.
In that case the description is valid. I can adjust my code to go around this bug in Kiota but in my opinion this is still a bug in Kiota.

Here is the detail https://spec.openapis.org/oas/latest#path-templating-matching

Thank you!
I agree that my failing example is similar to this, and seems to be invalid.
The following paths are considered identical and invalid:

  /pets/{petId}
  /pets/{name}


Use nfpm to Create RPM, deb, and apk Packages

Well detailed description of the change :

Add the ability to create RPMs, debs, and apks as well as upload the compiled binary for easy download and use per release.
Depending on if this is something we want to do, we'd need to update the github action to create the packages and upload them to the release when new releases are created.

Resolves: #

Type of change:

[ ] Bug fix

[x] New feature

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Housekeeping

[ ] Tests have been updated to reflect the changes done within this PR (if applicable).

[ ] Documentation has been updated to reflect the changes done within this PR (if applicable).

Preview (Screenshots) :

This looks nice thank you! I've not personally used nFPM before but will take a look into it, thanks. Adding files to a release should be fine, there are a couple of actions available for it on the market place so we can use them / draw inspiration from those

I think this is ready to go.

Thanks for this! Due a release soon so will see what happens


BlazorApp.styles.css: not found

I have tried both the cli and ws2022 version of the BlazoApp tutorial and in both cases i get a 404 for BlazorApp.styles.css
I imagine that something is not  ok with isolation?

Hello @mellogrand - Can you please provide some more info?:

Can you please share the link to the specific tutorial you were following? If you can also indicate the page, that would be great.
What .NET version are you using?

thank you again.
I solved the issue related to a strange inheritance of environment not from
the json file in the project but from windows settings. I had test
instead of development.
In net 6 was not affecting, but in 7 and 8 it was. Strange, but solved.
Il giorno lun 2 ott 2023 alle ore 19:26 Carlos Sánchez López <
@.***> ha scritto:

Hello @mellogrand https://github.com/mellogrand - Can you please
provide some more info?:

Can you please share the link to the specific tutorial you were
following? If you can also indicate the page, that would be great.
What .NET version are you using?

—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/core/issues/8797#issuecomment-1743447339, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5KYVJUBSLTGIM5ZY2FCB3X5L2MZAVCNFSM6AAAAAA5K2VFOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGQ2DOMZTHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Conditionally require cause

@wouterw Thanks for grabbing this one. I already fixed this in #136, which I just merged. Sorry for the confusion!


null for Artillery

Is it still supported?
When I'm trying to convert to artillery this sample collection: https://github.com/Blazemeter/taurus/blob/master/examples/functional/postman-sample-collection.json
I'm getting null

@joszo,
In the example, the host is split into subdomain strings. Line 34-36 in the example.
Whereas the tool was developed with url host as string.
I suggest to pick another example to do the conversion, while I will open a new ticket to fix this issue.

@rupeshmore thanks for the answer:
I've changed the host for the "host": "test", and the file was created correctly.


How to stop to get GPS location once we request for continous update?

Is there any way to stop location monitoring after some time when we request for continous GPS location update.
 LocationManager.shared.locateFromGPS(subscription, accuracy: .any) { (location) in     }

@kumardiwa I have this issue also, so how to stop this update ?


Allow for YAML rendering pre/post processing.

This is a BC break since it changes the contract. Classes implementing the Winter\Storm\Parse\Processor\Contracts\YamlProcessor interface should instead extend the Winter\Storm\Parse\Processor\YamlProcessor abstract to maintain parity with the interface.
This change is in preparation of a change that I intend to make for the Builder plugin to ensure that the version.yaml uses quoted version keys when generating the migrations.

How does this interact with #21 and the related PR?

It should be entirely compatible with that PR (besides changing the processor to extend the abstract class as opposed to implementing the interface). These new methods are for rendering though, so while that PR ensures that our older version files can still be read, this will allow us to ensure that the YAML files are correctly written as well.

@bennothommo what's the status of this?

@LukeTowers it should be ready to go.

@bennothommo looks like the tests need to be fixed for this PR

@LukeTowers fixed up the tests


reconnect only once for multi job forks

Reconnecting redis for every job isn't needed.
For a system that reconnecting occurs thousands times per second, the patch will do some help. In our case, prevented 900 reconnection per second resulted about 5% down of CPU usage for a cache.m1.large aws instance.

The latest version on rubygems was released more than 1 year ago, can I ask you to bump version for those recently changes?

@stulentsev Thank you!

Note that Resque::Worker#reconnect was added in 1.24 but this gemspec specifies ~> 1.22. Need to bump to ~> 1.24.


Sidebar should be collapsible so only icons show

🚀 Feature Proposal
The sidebar should be collapsible so only the icons show to maximize screen space.
This should be a user controlled behavior with some sort of expand/collapse icon.
This should automatically happen when the screen becomes a smaller screen.
Motivation
The sidebar should be collapsible so only the icons show to maximize screen space.
Example
See #103 for a detailed discussion and some examples.

I think I can help with this. Should I start working on this?

@rabbihossain I've assigned this issue to you! let anyone on @HospitalRun/core-maintainers know if you need any help!

Thanks for assigning this to me. I have already started working on it. I will get back to you once I finish implementing it.

hello @jackcmeyer ,
I am almost done implementing this. here is a preview of how the sidebar collapse toggle works.

Please let me know if you have any feedback. Should I make a pull request?

This is awesome! Please open a PR 😀

@jackcmeyer, I am trying to make a pull request but when I run npm run commit (as it was written on the project readme document), it always fails on npm run test:ci step. Am I doing anything wrong?

@rabbihossain try to run this command:

yarn
yarn lint:fix
yarn commit

thanks @tehKapa for helping me out. Looks like my changes broke some of the test cases. So I updated those test cases according to my changes. I also made a pull request.


Not using fully qualified name results in using the wrong database/schema for a resource by reverting to connection ones.

Perhaps I am making mistakes or perhaps the package is simply not mature enough at the moment but I am deeply struggling to to the simplest things with it.
Is there a possibility to explain how you actually envision this project being used in production? I.e. what roles to use for connection. How to structure the project? How to declare resources and how to build the plans?
Example:

CREATE NETWORK POLICY TITAN_TEST_NETWORK_POLICY ALLOWED_NETWORK_RULE_LIST = (TITAN_TEST_NETWORK_RULE) COMMENT = $$Demo network policy for testing purposes of titan[core].$$  will error because titan does not use fully qualified names. Network rule 'TITAN_TEST_DB.PUBLIC.TITAN_TEST_NETWORK_RULE' does not exist or not authorized. when the actual resource is declared explicitly as:

titan_test_network_rule = NetworkRule(
    name="TITAN_TEST_NETWORK_RULE",
    type="IPV4",
    value_list=["<IP_ADDRESS>"],
    mode="INGRESS",
    comment="Demo network rule resticting access to home Wifi only.",
    owner="SYSADMIN",
    database=titan_test_db,
    schema=titan_test_schema,
)

titan_test_network_policy = NetworkPolicy(
    name="TITAN_TEST_NETWORK_POLICY",
    comment="Demo network policy for testing purposes of titan[core].",
    owner="SYSADMIN",
    allowed_network_rule_list=[titan_test_network_rule],
    blocked_network_rule_list=None,
    allowed_ip_list=None,
    blocked_ip_list=None,
    database=titan_test_db,
    schema=titan_test_schema,
)

How many different plans do I need to create, how many different connections do I need to manage to use titan in a complex real world Snowflake setup?

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Fixed in v0.9


Initialize Provider outside request-pipeline

New behavior initializes provider once middleware is executed during app. startup.
Previous behavior delayed this until the first request flowed through the middleware. This prevented using Feature implementations during app. startup (i.e. DI via IRouteConstraint implementations).

Previous behavior fails here and then here since the value is null.


Apply spell correction to OCR

There are many trivial errors in the transcribed text which could be fixed using some knowledge of English and NYC-area nouns.
Trivial errors fall into a few classes:

Problems with dates

"JdTy 5, 1930." --> "July 5, 1930"
"Cune 18, i930" --> "June 18, 1930"
"Anril 1923"
"arch 1925."
"April 39" -> "April 30"
"Augst 27, 1933."

Number/letter mixups:

"S9th Sttreet"
"3O1" (O vs. 0)
"186O" (O vs 0)
"196h."→"1964."
"8treets"→"Streets"
"Sth"→"8th"
"18V8"→"1898"
"1s"→"is"
"193S"→"1935"

Wrong repetitions:

"SSecond"
"Sttreet"
"IIn"
"IIt"
"lIsland"

Dumb typos:

"Sduare"→"Square"
"Suare"→"Square"
"autoaobile"→"automobile"
"subsecuently"→"subsequently"
"New YoNk"→"New York"
"nrooklyn"→"Brooklyn"
"dorner"→"corner"
"fhe"→"the"
"Nobth"→"North"
"NoNth"→"North"
"aultiple"→"multiple"
"Tsland"→"Island"
"nearlv"→"nearly"
"colontal"→"colonial"
"wiews"→"views"
"Hhdson"→"Hudson"
"Paralueling"→"Paralleling"
"antioipates"→"anticipates"
"3roadway"→"Broadway"
"Muthority"→"Authority"
"Vest 51st"→"West 51st"
"14th Str et"→"14th Street"
"Gatholic Ghurch"→"Catholic Church"
"Viewa"→"Views"

Anecdotally, pyenchant doesn't do a particularly good job of getting the correct replacement in the top spot. Rolling my own spell checker ala Peter Norvig using validated transcriptions as a source of words might work better.

Realistically, I'm not going to revisit this. Users are doing a fine job all on their own.


rebol lexer: unclosed character class in regex

(Original issue 1467 created by thomaswaldmann on 2018-08-16T20:21:08.215964+00:00)
https://bitbucket.org/birkenfeld/pygments-main/src/7941677dc77d4f2bf0bbd6140ade85a9454b8b80/pygments/lexers/rebol.py#lines-242
See how it misses the backslash before the square bracket.
Compare to the regex 3 lines above that.
re module does not like that:
#!python
>>> text='          REBOL['
>>> re.search(r'\s*REBOL\s*[', text, re.IGNORECASE)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "env/lib/python2.7/re.py", line 146, in search
    return _compile(pattern, flags).search(string)
  File "env/lib/python2.7/re.py", line 251, in _compile
    raise error, v # invalid expression
sre_constants.error: unexpected end of regular expression

Issue was found by the pycharm code checker:
"unclosed character class"
Found it in 2.1.3, but it is still there in current code.

This has been fixed in the meantime.


lodash chaining filter method has wrong type

_.flatten() has the correct return type, but _(...).flatten() does not:
interface Item { }
var items: Item[] = [];
var arrayWrapper = _.flatten(items); // type = Item[]
var arrayStatic = _(items).flatten().value(); // type = {}[]

The definitions look correct so I'm not even sure what's wrong.  Do any of you recent contributors know how to fix it, @bczengel, @anthonychu, @szarouski, @motemen, @andrewvc, @dmorgantini?

The return type of the chainable version of flatten can't be inferred. You have to specify it.
_(items).flatten<Item>().value()

@altano I think the issue can be closed, isn't it?

Yeah, this can be modeled using new features in TS such as union types and it looks like the .d.ts for lodash has been overhauled to make use of these new features, so this issue is irrelevant.


L5.PRP.VA.42	The tool shall average less than 1 second execution time when content validation is disabled.

Our current benchmarks (see below) still take 10 minutes for large files (GBs) and 4-8 seconds for smaller files (MBs). This is a significant improvement from before, but deliveries involve thousands of products, so validate is still taking days instead of hours to run on one delivery. We need to figure out where else we can improve performance.
This new requirements is specific to improving all parts of validation separate from content validation.
Large test data sets are on pds-dev-el7:/path/to/test/data/insight_cameras

NOTE: You may need to execute with a catalog file or against multiple products to see improved performance. The initial loading of schemas/going out to internet will always take some time.

@jordanpadams Jordan, can you give exact path of the test data you indicated in the description?

Before adding a command chain, time command returns
11.675u 0.557s 0:04.00 305.5%	0+0k 0+0io 0pf+0w
After adding 'pds4.label.skip.content' command chain, time command returns
11.373u 0.561s 0:03.79 314.7%	0+0k 0+0io 0pf+0w


feat: Add tips

Description
Briefly describe the purpose of this pull request.
Changes Made
Provide a list of changes made in this pull request.
Related Issues
Reference any related issues using keywords like "Fixes #issue-number".
Additional Notes
Add any other notes or screenshots that might be helpful for the reviewers.

Can you reduce the gap between the end of the timetable grid and the tips?

No I can't, it's another issue actually