Add menu for rewards

Description of new idea or improvement on existing one
I propose the idea of a menu with level rewards. Example level 100 minor I unlock a new pickaxe. But not automatically, you would have to go to / jobs menu, choose our job and click on the reward.
Detailed information what should do what and when
Add the / jobs menu command. Which displays the jobs available.
Once on the job that you want, you have all the vision on the available rewards.
Example: level 10 -> 15 gold ingot
level 20 -> ///
level 100 -> New pickaxe
level 200 -> ///
And when we click on the rewards not available a message says "You do not have the reward for the moment"

Maybe possible to unlock with shops...
But you could also just give permissions to essential kits with the rewards too

Maybe possible to unlock with shops...
But you could also just give permissions to essential kits with the rewards too

I do not understand what you want "with shops" can you enlighten me? I hadn't thought of the kits. but in this case it is necessary to set the conditions of job level: x?
did you manage to do what I'm looking for? if so would it be possible to show me?

I do not understand what you want "with shops" can you enlighten me? I hadn't thought of the kits. but in this case it is necessary to set the conditions of job level: x?
did you manage to do what I'm looking for? if so would it be possible to show me?

https://i.imgur.com/hlH0uhD.gif
We have a bunch of different things set up at different levels, it costs points, and I haven't figured out if there is a way to do onetime only usage, but you could add shop items that give permissions to a one time use kit if you needed to.

https://i.imgur.com/hlH0uhD.gif
We have a bunch of different things set up at different levels, it costs points, and I haven't figured out if there is a way to do onetime only usage, but you could add shop items that give permissions to a one time use kit if you needed to.

I don’t think this feature should be in Jobs, as it’s not tied to doing the work. It would be unnecessary to add this, as there are plenty of plugins that would work with the Jobs plugin if its author adds the plugin as a dependency. This is, for example, AdvancedAchievements, which was recently added as a dependency by the author.

I don’t think this feature should be in Jobs, as it’s not tied to doing the work. It would be unnecessary to add this, as there are plenty of plugins that would work with the Jobs plugin if its author adds the plugin as a dependency. This is, for example, AdvancedAchievements, which was recently added as a dependency by the author.

I dont think it's related to JobsReborn. but i saw someone using it on their server.
But it would be interesting to add it!
Example:
Since we have the possibility to configure the rewards in the "example.yml" in the "orders" category,
you need a command like / jobs rewards  or / jobs  and display all the rewards.

I dont think it's related to JobsReborn. but i saw someone using it on their server.
But it would be interesting to add it!
Example:
Since we have the possibility to configure the rewards in the "example.yml" in the "orders" category,
you need a command like / jobs rewards  or / jobs  and display all the rewards.

i saw someone using it on their server.

They probably uses an unique or a public plugin which has compatibility with jobs.
There are some options in jobs config called, conditions, permissions and commands. With this users can configure the level-up, level-from when the players can get reward commands or even payout. https://github.com/Zrips/Jobs/blob/master/src/main/resources/jobs/_EXAMPLE.yml#L509-L564

i saw someone using it on their server.

They probably uses an unique or a public plugin which has compatibility with jobs.
There are some options in jobs config called, conditions, permissions and commands. With this users can configure the level-up, level-from when the players can get reward commands or even payout. https://github.com/Zrips/Jobs/blob/master/src/main/resources/jobs/_EXAMPLE.yml#L509-L564

https://imgur.com/a/lC97Yvs

https://imgur.com/a/lC97Yvs

That is called Command Panel, Chest Commands or BetterGui

That is called Command Panel, Chest Commands or BetterGui

Can you help me?
How could I go about putting the <commands / permission> in a bettergui?

Can you help me?
How could I go about putting the <commands / permission> in a bettergui?

Please look at the well-documented page of that plugin or ask the author. It provides much more documentations on how to use. We can't help you with that. https://github.com/BetterGUI-MC/BetterGUI/wiki/Basic-tutorial

Please look at the well-documented page of that plugin or ask the author. It provides much more documentations on how to use. We can't help you with that. https://github.com/BetterGUI-MC/BetterGUI/wiki/Basic-tutorial

Is even more gui menu plugins out too.

Is even more gui menu plugins out too.


gtf2gtf endless processing

Hello.
I'm having an issue on which I run the gtf2gtf script, the process starts but never ends and the 'top' task manager also showed no signs of any processes apparently derived from the script. I left it idle for about half an hour to absolutely no difference in either the task manager or the running script itself.
I have some screenshots of the commands and the behaviour.

Hi,
The script is waiting for input. This is because gtf2gtf takes its input
from the stdin. If you wish to direct a file in, then use the option
--stdin/-I before the name of the input file.


Update sitewide settings

Codecov Report

Merging #28 (b1dbf1b) into master (5bd3ec9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #28   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Leaderboard in Pro ver

Hi, how i add Leaderboard in Pro ver? I see Leaderboard in config, but when i add the coordinate, they don't show up

I'm working on it. I hope tommorow it will work.

Yeah, thanks
On Wed, Apr 22, 2020, 4:48 AM VixikHD<EMAIL_ADDRESS>wrote:

I'm working on it. I hope tommorow it will work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GamakCZ/SkyWars/issues/68#issuecomment-617431829, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUCES7NLHIJOOJRYPQUOPTRNYICDANCNFSM4MNQ4BRQ
.


Remove names from the package lists returned to VS.

The only optimization that I've been aware of that hadn't been done.  I'll close https://github.com/Microsoft/RTVS/issues/1328 after this.
This reduces the length of the JSON by 100kb, saving on serialization/transport/deserialization, and removes the special case of empty lists on deserialization.
We'll also now be able to have the same package be listed twice for "installed packages", which was not possible before with named lists.  I'm still preventing duplicates from happening right now, as I'm not sure the UI would expect it, but we can stop removing duplicates later.

:+1:

👍


Fix invalid UUID breaking related images query

Fixes

Related to #729 by @AetherUnbound
Description

This PR uses @krysal 's suggestion to add an IndexError handling for when there are no hits in the search controller:
https://github.com/WordPress/openverse-api/blob/7414174a16ba4cbd6af70773ce6d19b92b0e96de/api/catalog/api/controllers/search_controller.py#L344
Testing Instructions

On main, if you go to http://localhost:8000/v1/images/000000000000000000000000000000000000/related/, you would get a 500 error.
On this branch, you should get a 404.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Also, do you know why something that looks like a valid UUID (follows the pattern) doesn't cause the 500? Why doesn't it throw an IndexError as well like the same-length-but-not-UUID-pattern string does when queried for?

@sarayourfriend, actually, that's not the case, but it took me some time to figure it out :)
The example you gave in the issue (da5cb478-c093-4d62-b721-cda18797e3fz) looks like UUID for humans, because we don't notice that z(the last letter of the string) is not in the pattern, it's only a-f for the hex numbers.

Ah!! I forgot that UUID had rules :sweat_smile: Good catch! Sorry for the false lead :scream:

Ah!! I forgot that UUID had rules 😅 Good catch! Sorry for the false lead 😱

It was actually a great opportunity to learn more about what's happening when we search for something 👍


Acid text for macOS fails

Node Version: v15.13.0 node, 7.7.6 npm
Platform MacOS 11.3
Compiler : Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin20.3.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Acid test for macos fails even though `xcode-select -print-path` shows `/Applications/Xcode.app/Contents/Developer`

That path would correspond to Solution #1 where the full Xcode has been installed.  Can you please make sure that Xcode is up-to-date?

That path would correspond to Solution #1 where the full Xcode has been installed.
Can you please make sure that Xcode is up-to-date?

Yep, I reinstalled XCode yesterday as certain things stopped working and says CLI tools weren't to be found


Added the Main Tinder Functionality of the Application

This adds the main functionality to the application.
Includes:

Cat Image
Cat Bio

Name
Age
Gender
Location
Hobbies

Liking/Disliking Cats
Teleporting Screen on Close
Jumpscares

Looking good so far, make sure the checks are passing before you merge the code. I fixed the linting config file in dev so merge those changes and it will update.

Don't bother with a PR if you're not looking for comments. Just commit right into main. It will make this process faster.


Remove alert for not-supported feature.

Found from a forum post (https://forum.mendixcloud.com/link/questions/102481). Actually, we do support nested-object or nested-array when exporting Json.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @fazzdev . Maybe would be good as the SME here if you posted on the Forum this is not supported and doc has been updated?

Good idea! and done.


dm: reduce gSet.String() usage by using zeroGSet for checking empty

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/9676
What is changed and how it works?
reduce gSet.String() usage by using zeroGSet for checking empty
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/run-dm-integration-tests

/run-dm-integration-tests

/retest


Replace manual work with arrays / lists

Instead of making \authorA..\authorN then make an array/list of authors. Maybe its possible to loop over this array/list, so there is less manual work in setting up authors/emails/supervisors. This is probably pretty advanced and could lead to user confusion when editing these things.

Ok it works. Now find a way to make it work in \author and hyperref setup so there is no manual work required to get it to work properly.

I made it work with hyperref setup. Now the last thing to do is make it work with \author

\author doesnt work with special characters as \patchcmd fucks up somehow


Add PowerToys shortcuts to Shortcut Guide

Description of the new feature / enhancement
Could you please add the various PowerToys keyboard shortcuts to the Shortcut Guide as well? I'm sure I'll have trouble remembering them all, and this would be very helpful.
Scenario when this would be used?
This would be useful when the user can't remember a particular PowerToy keyboard shortcut.
Supporting information
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #15405
Besides: would adding the shortcuts to the existing fly-out be sufficient?


don't subtract startrec from fldcount

What changes does this PR introduce?
(Bug fix, feature, docs update, ...)
Bug fix: this is a pretty subtle and small change to pkg/ctrl/ctrl_get_gen_rec
What is the current behaviour?
(You can also link to an open issue here)
In ctrl_get_gen_rec, count0 and count1 are the variables used to determine which records to read from xx_gentim2d_file.effective.## (e.g. xx_tauu.effective.##). These are currently computed as follows:
count0 = fldcount0 - startrec + 1
count1 = fldcount1 - startrec + 2

With this implementation, count0 ALWAYS starts at 1. This means that the "effective" file only has the minimum number of records for the current simulation.
What is the new behaviour
(if this is a feature change)?
It is quite convenient to run for a short time period, but use a control vector from a longer run. As a concrete example, consider running only during 2009 of ECCO. Here it would be ideal to provide the same control vector from ECCO, which has hundreds of entries, and only access the entries relevant to the current run (we'd only need ~52 or so control records from ECCO for a single year). It would be extremely difficult to line up the start of the 2009 simulation with the exact record number needed. However, the following simple change seems to do the trick (this is the entire PR):
count0 = fldcount0
count1 = fldcount1

For this 2009 simulation, the ctrl package makes xx_gentim2d.effective files which have length: (number of records for start of ECCO to start of 2009) + (number of records for 2009 simulation), and only these last records are accessed.
Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
This doesn't break anything, and I've even tested this with the adjoint everything seems to be cool.
Other information:
The funny thing is, this modification is commented out in the original code. I can't think of a reason for adding -startrec+1 etc, but I would be interested if @gaelforget (or anyone else) knows why these lines were commented out. It seems to only make this more difficult!
I know @raphaeldussin and @antnguyen13 found this useful, perhaps others will too.
Suggested addition to tag-index
(To avoid unnecessary merge conflicts, please don't update tag-index. One of the admins will do that when merging your pull request.)

I agree. please see line 168-169 of
http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm_contrib/ecco_darwin/v4_llc270/code/ctrl_get_gen_rec.F?view=markup

LGTM +1


using retry_on_exception with class function is not working

Hello,
trying the following code is not working
def catch_general_exception(self,ex):
       return isinstance(ex,Exception)

@retry(retry_on_exception=catch_general_exception)
def do_some_code:
       # do some code
       try:
              # some ode
       except Exception as ex:

passing catch_general_exception is not accepted even i passed self.catch_general_exception

I suspect that you meant something like this:
class SomeClass:
    def catch_general_exception(self, ex):
        return isinstance(ex,Exception)

    @retry(retry_on_exception=self.catch_general_exception)
    def do_some_code(self):
        # do some code
        try:
            # some ode
        except Exception as ex:
            raise

This won't work because self isn't defined when the @retry decorator is being created.
This should work, though:
def catch_general_exception(ex):
    return isinstance(ex,Exception)

class SomeClass:

    @retry(retry_on_exception=catch_general_exception)
    def do_some_code(self):
        # do some code
        try:
            # some ode
        except Exception as ex:
            raise

This might even work: @retry(retry_on_exception=lamba ex: isinstance(ex, Exception)

Actually, after doing more reading, your use case is already supported:
@retry(
    retry_on_exception=(Exception,)
)


installing the raspiblitz

At the stage of installing the raspiblitz operating system image from a flash drive, installation is not going on. Hangs on this line. Set with 2 different memory cards.

What could be the problem?

This reminds me of this issue that we still havent found a solution to:
https://github.com/rootzoll/raspiblitz/issues/195
If you have the time it would be great if you can try exchange also the RaspiberryPi board and also try to start up without the HDD. Even trying to start it on another Internet connection. And let us know if that changed anything.

Give thanks. Disable HDD. The process has progressed further. But it was still.

I have the same issue.
After working for several months, my raspiblitz now hangs on boot.
Tried version 1.0, 1.1 and 1.2, with and without hdd and network cable.
Since the raspiblitz doesn’t boot I have no idea what to check further.

When the Raspiblitz stopped working I was still on version 1.1. And I'm not able to boot on this version.
With version 1.2 I was able to SSH back into Raspiblitz. (PS I do not have an LCD).
Now it appears that bitcoind and LND do not start automatically, since I cannot get past the hardware test in SSH.
Below is the output for the debug logs. (./XXdebugLogs.sh)
What should I do next?
I have off-chain funds and channel funds on the HDD, created under version 1.1.

RASPIBLITZ DEBUG LOGS

blitzversion: 1.2
chainnetwork: bitcoin / main
18:39:16 up 17 min,  2 users,  load average: 0.03, 0.15, 0.22
*** BCLOCKHAIN SYSTEMD STATUS ***
● bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; disabled; vendor preset: enabled)
Active: inactive (dead)
*** LAST BCLOCKHAIN ERROR LOGS ***
sudo journalctl -u bitcoind -b --no-pager -n8
-- No entries --
*** LAST BCLOCKHAIN 20 INFO LOGS ***
sudo tail -n 20 /mnt/hdd/bitcoin/debug.log
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
*** LND SYSTEMD STATUS ***
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; disabled; vendor preset: enabled)
Active: inactive (dead)
*** LAST LND ERROR LOGS ***
sudo journalctl -u lnd -b --no-pager -n12
-- No entries --
*** LAST 30 LND INFO LOGS ***
sudo tail -n 30 /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log
tail: cannot open '/mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log' for reading: No such file or directory
*** LAST 20 RTL LOGS ***
-- No entries --
*** HARDWARE TEST RESULTS ***
UndervoltageReports in Logs: 5
powerFAIL=0
powerWARN=2
powerMIN='1243800 microVolt'
tempFAIL=0
tempWARN=0
tempMAX='6010 centiGrad'
IMPORTANT: There are some hardware issues with your setup.
'Run Hardwaretest' in main menu or: sudo /home/admin/05hardwareTest.sh
*** SYSTEM STATUS (can take some seconds to gather) ***
localIP='<IP_ADDRESS>'
tempCelsius='53.1'
uptime=1060
startcountBlockchain=0
bitcoinActive=0
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
bitcoinErrorShort='Error found in Logs'
bitcoinErrorFull='0'
OK: log 'ERROR: Error found in Logs' written to /home/admin/systemd.blockchain.log
startcountLightning=0
lndActive=0
scriptRuntime=0

This is the error I get after the hardware test during boot in SSH.

RASPIBLITZ DEBUG LOGS

blitzversion: 1.2
chainnetwork: bitcoin / main
20:16:41 up  1:05,  2 users,  load average: 0.95, 0.54, 0.26
*** BCLOCKHAIN SYSTEMD STATUS ***
● bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; disabled; vendor preset: enabled)
Active: inactive (dead)
*** LAST BCLOCKHAIN ERROR LOGS ***
sudo journalctl -u bitcoind -b --no-pager -n8
-- No entries --
*** LAST BCLOCKHAIN 20 INFO LOGS ***
sudo tail -n 20 /mnt/hdd/bitcoin/debug.log
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
*** LND SYSTEMD STATUS ***
● lnd.service - LND Lightning Daemon
Loaded: loaded (/etc/systemd/system/lnd.service; disabled; vendor preset: enabled)
Active: inactive (dead)
*** LAST LND ERROR LOGS ***
sudo journalctl -u lnd -b --no-pager -n12
-- No entries --
*** LAST 30 LND INFO LOGS ***
sudo tail -n 30 /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log
tail: cannot open '/mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log' for reading: No such file or directory
*** LAST 20 RTL LOGS ***
-- No entries --
*** HARDWARE TEST RESULTS ***
UndervoltageReports in Logs: 5
powerFAIL=0
powerWARN=7
powerMIN='1243800 microVolt'
tempFAIL=0
tempWARN=2
tempMAX='6550 centiGrad'
IMPORTANT: There are some hardware issues with your setup.
'Run Hardwaretest' in main menu or: sudo /home/admin/05hardwareTest.sh
*** SYSTEM STATUS (can take some seconds to gather) ***
localIP='<IP_ADDRESS>'
tempCelsius='56.3'
uptime=3958
startcountBlockchain=0
bitcoinActive=0
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
tail: cannot open '/mnt/hdd/bitcoin/debug.log' for reading: No such file or directory
bitcoinErrorShort='Error found in Logs'
bitcoinErrorFull='0'
OK: log 'ERROR: Error found in Logs' written to /home/admin/systemd.blockchain.log
startcountLightning=0
lndActive=0
scriptRuntime=6
*** OPTION: SHARE THIS DEBUG OUTPUT ***
An easy way to share this debug output on GitHub or on a support chat
use the following command and share the resulting link:
/home/admin/XXdebugLogs.sh | nc termbin.com 9999
UNKOWN STATE - there is blockain data config, but blockchain service is not running
It seems that something went wrong during sync/download/copy of the blockchain.
Or something with the config is not correct.
Sometimes a reboot helps --> sudo shutdown -r now

Had to manually start bitcoins and LND. This I have to do every reboot of Raspiblitz.
Node is running again.
Still some commands are not working yet, and had to reinstall RTL.
Managed to withdraw all on-chain funds, however still working on the channel funds.

The hanging on boot is a replica issue of #195 - so I am closing this issue. But feels free to report your further progress here.


FlagParser

Create a thin wrapper around std flags.parse

Too much has changed since this draft was started. Will need a complete rework.


Random encounter table

fix #91

This is very nice. There's one problem, though. The width of the dropdown for selecting a table is unbounded, so if you have a very long name (which, if you've selected a number of creatures, is the default), the dropdown becomes arbitrarily large. Please add a max-length to it (and make sure to check the smallest breakpoint, where form elements change and realign).
Also, you left a console.log in the library.service.js file.
Please take care of those issues and this can be merged.
Thanks!

Will do! I also knew there'd be conflicts if you merged the filter warning, so I have a little cleaning up to do anyway. Coming right up... thanks!

The conflicts are pretty simple, it's just stuff that's been added in the same locations. If that and the console.log had been the only issues I would have taken care of it myself, but the width thing was just beyond the level of effort I've got the motivation for at the moment.

I hear that! Should be fixed now. Thanks for all the work you've put in, by the way... awesome tool, and a pleasure to work on.

Changed the max width of the dropdown to 300px. I realize this doesn't quite work on the narrower screens, but 605px just felt too large to me.
Thanks!

Yeah I thought 300 made more sense too,  I just didn’t want to unilaterally make it smaller than the other controls under 768px.


data: project addition by  Abishek Upadhyay

Add a new project to the list
I want to add a new project to the list  which is known as DePay, it is a blockchain based money lending app using tech-stacks like solidity, next js etc. It is not an individual project of mine but has been made alongside my teammates.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Completed. Thanks for your contributions 🎉 ❤


[RFC]: support for structured package data

Description
This RFC proposes adding structured package data to facilitate automation and scaffolding.
Overview
The need for structured package data has been discussed at various points during stdlib development. This need has become more paramount when seeking to automate specialized package generation for packages which wrap "base" packages for use with other data structures. The most prominent example being math/base/special/* APIs which are wrapped to generate a variety of higher-order packages, including

math/iter
math/strided
math/ generics supporting ndarrays, arrays, and scalars

and more recently in work exposing those APIs in spreadsheet contexts. In each context, one needs to

specify parameters, including types, names, and descriptions
add example values
generate random values for benchmarking, examples, and tests
specify aliases
specify related keywords

and in some contexts

create native implementations

While various attempts have been made to automate scaffolding of higher-order packages, where possible, each attempt has relied on manual entry of necessary scaffold data, including parameter names, descriptions, and example values. To date, we have not created a centralized database from which we pull desired package meta data.
Proposal
In this RFC, I propose adding structured meta data to "base" packages. This structured meta data can then be used in various automation contexts, most prominent of which is automated scaffolding.
The meta data would be stored as JSON in a subfield of the __stdlib__ configuration object of package.json files. The choice of JSON stems from the ability to use JSON Schema for validation and linting.
Examples
I've included two examples below.
math/base/ops/add:
{
    "$schema"<EMAIL_ADDRESS>    "base_alias": "add",
    "alias": "add",
    "pkg_desc": "add two double-precision floating-point numbers",
    "desc": "adds two double-precision floating-point numbers",
    "short_desc": "",
    "parameters": [
        {
            "name": "x",
            "desc": "first input value",
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",
                "dtype": "float64"
            },
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],
            "rand": {
                "prng": "random/base/uniform",
                "parameters": [
                    -10.0,
                    10.0
                ]
            },
            "example_values": [
                -1.2,
                2.0,
                -3.1,
                -4.7,
                5.5,
                6.7
            ]
        },
        {
            "name": "y",
            "desc": "second input value",
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",
                "dtype": "float64"
            },
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],
            "rand": {
                "prng": "random/base/uniform",
                "parameters": [
                    -10.0,
                    10.0
                ]
            },
            "example_values": [
                3.1,
                -4.2,
                5.0,
                -1.0,
                -2.0,
                6.2
            ]
        }
    ],
    "returns": {
        "desc": "sum",
        "type": {
            "javascript": "number",
            "jsdoc": "number",
            "c": "double",
            "dtype": "float64"
        }
    },
    "keywords": [
        "sum",
        "add",
        "addition",
        "total",
        "summation"
    ],
    "extra_keywords": []
}

stats/base/dists/arcsine/pdf:
{
    "$schema"<EMAIL_ADDRESS>    "base_alias": "pdf",
    "alias": "pdf",
    "pkg_desc": "arcsine distribution probability description function (PDF)",
    "desc": "evaluates the probability density function (PDF) for an arcsine distribution with parameters `a` (minimum support) and `b` (maximum support)",
    "short_desc": "probability density function (PDF) for an arcsine distribution",
    "parameters": [
        {
            "name": "x",
            "desc": "input value",
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",
                "dtype": "float64"
            },
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],
            "rand": {
                "prng": "random/base/uniform",
                "parameters": [
                    -10.0,
                    10.0
                ]
            },
            "example_values": [
                2.0,
                5.0,
                0.25,
                1.0,
                -0.5,
                -3.0
            ]
        },
        {
            "name": "a",
            "desc": "minimum support",
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",
                "dtype": "float64"
            },
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],
            "rand": {
                "prng": "random/base/uniform",
                "parameters": [
                    -10.0,
                    10.0
                ]
            },
            "example_values": [
                0.0,
                3.0,
                -2.5,
                1.0,
                -1.25,
                -5.0
            ]
        },
        {
            "name": "b",
            "desc": "maximum support",
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",
                "dtype": "float64"
            },
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],
            "rand": {
                "prng": "random/base/uniform",
                "parameters": [
                    10.0,
                    20.0
                ]
            },
            "example_values": [
                3.0,
                7.0,
                2.5,
                2.0,
                10.0,
                -2.0
            ]
        }
    ],
    "returns": {
        "desc": "evaluated PDF",
        "type": {
            "javascript": "number",
            "jsdoc": "number",
            "c": "double",
            "dtype": "float64"
        }
    },
    "keywords": [
        "probability",
        "pdf",
        "arcsine",
        "continuous",
        "univariate"
    ],
    "extra_keywords": []
}

Annotated Overview
{
    // Each configuration object should include the schema name and version so that tooling can gracefully handle migrations and eventual schema evolution:
    "$schema"<EMAIL_ADDRESS>// math/base indicates that this schema applies those packages within the math/base namespace. Different namespaces are likely to have different schema needs; hence, the requirement to specify which schema the structured package meta data is expected to conform to.

    // The "base" alias is the alias without, e.g., Hungarian notation prefixes and suffixes:
    "base_alias": "add",

    // The alias is the "base" alias and any additional type information:
    "alias": "add",

    // The package description used in the `package.json` and README:
    "pkg_desc": "add two double-precision floating-point numbers",

    // The description used when documenting JSDoc and REPL.txt files:
    "desc": "adds two double-precision floating-point numbers",

    // A short description which can be used by higher order packages or in other contexts:
    "short_desc": "",

    // A list of API parameters:
    "parameters": [
        {
            // The parameter name as used in API signatures and JSDoc:
            "name": "x",

            // A parameter description:
            "desc": "first input value",

            // Parameter type information as conveyed in various implementation contexts:
            "type": {
                "javascript": "number",
                "jsdoc": "number",
                "c": "double",

                // This field would have more prominence in higher-order APIs, such as those involving ndarrays, where the JavaScript value may be `ndarray`, but we want to ensure we use an ndarray object having a float64 data type:
                "dtype": "float64"
            },

            // The mathematical domain of accepted values (note: this is an array as some math functions have split domains):
            "domain": [
                {
                    "min": "-infinity",
                    "max": "infinity"
                }
            ],

            // Configuration for generating valid random values for this parameter:
            "rand": {
                // A package name for a suitable PRNG:
                "prng": "random/base/uniform",

                // Parameter values to be supplied to the PRNG:
                "parameters": [
                    -10.0,
                    10.0
                ]
            },

            // Concrete values to be used in examples (note: these could possibly be automatically generated according to the `rand` configuration above):
            "example_values": [
                -1.2,
                2.0,
                -3.1,
                -4.7,
                5.5,
                6.7
            ]
        },
        ...
    ],

    // Configuration for the return value (if one exists):
    "returns": {
        // Return value description, as might be used in JSDoc and REPL.txt:
        "desc": "sum",

        // Return value type information:
        "type": {
            "javascript": "number",
            "jsdoc": "number",
            "c": "double",
            "dtype": "float64"
        }
    },

    // A list of keywords without all the boilerplate keywords commonly included in `package.json`:
    "keywords": [
        "sum",
        "add",
        "addition",
        "total",
        "summation"
    ],

    // Additional keywords (e.g., the built-in API equivalent, such as Math.abs):
    "extra_keywords": []
}

Discussion

The most prominent risk is that this is yet another place where meta data can drift and something more we need to maintain. While true, I think having structured meta data has benefits which outweigh the additional costs, particularly when we consider how commonly we often wrap "base" functionality as part of higher order APIs. Given that we've had a recurring need for such meta data, we'll eventually need some sort of standardized way of storing this meta data.
One benefit of having this structured meta data is that this could better enable AI tools, such as those provided by OpenAI, to scaffold new packages involving "base" implementations.

Related Issues
No.
Questions

What other data, if any, should be included?
One open question is whether we should include support for constraints? E.g., in the arcsine PDF function a < b. In the example JSON, I've simply manually adjusted the PRNG parameters and the example values to ensure we don't run afoul of that constraint. It was not clear to me how we might include such constraints in a universal way which is machine parseable and actionable in scaffolding tools.
Which other package namespaces might benefit from structured meta data and how would their schemas differ from the examples above?

Other
No.
cc @Planeshifter
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Planeshifter Given your previous efforts to build scaffolding tooling, would be good to get your opinion on the above proposal and what, if any, additional structured information might be useful.

@Planeshifter Pinging you here, in case you have forgotten about this issue.

@kgryte is this in the works?

@Snehil-Shah Sort of. We've created a Google sheet for collecting this information, but that effort has stalled. Something like this would be rather useful, but it involves a fair amount of manual labor, and we haven't had the bandwidth to push forward.

Opening up a tracking issue for this one should help us move forward with since it does require a good number of additions to be made. Should we open one ?

From what I gather resolving this will help in the scaffolding process of both the Gsheets project and developing C implementations,  right ?

@adityacodes30 Before opening up a tracking issue, we need to settle on the desired path forward. But, yes, this is also relevant to the scaffolding process for both GSheets and the C implementation work.

Generally, I think we should start with math/base/special, the second priority would be blas/ext/base. But this is as pertains to Gsheets. Would have to see what the community thinks

My my main concern, and it is for me a serious one, is that this increases duplication of package documentation even more, which is already quite excessive. If we undertake this, I think it's necessary to at the same time build tooling (either LLM-assisted or just deterministic) that scaffolds out the required other files such as repl.txt. There is a trap that this will be decently easy to add for existing packages but then cause an additional burden when trying to add new packages. I feel we have encountered this several times in the past so we should have a good answer to address this concern.
As for the proposed schema, it seems sensible. I would drop keywords and extra_keywords and instead follow the previously discussed approach of excluding all boilerplate keywords from the keywords array of the package.json in the development repo and then populate them during the release process.
Here are my answers to the raised questions:

What other data, if any, should be included?

Not sure. Maybe something for testing. Should it support options object definitions?

One open question is whether we should include support for constraints? E.g., in the arcsine PDF function a < b. In the example JSON, I've simply manually adjusted the PRNG parameters and the example values to ensure we don't run afoul of that constraint. It was not clear to me how we might include such constraints in a universal way which is machine parseable and actionable in scaffolding tools.

This is a pretty deep rabbit hole and not something that should be encoded in metadata, I think. Burden would be on the person populating the metadata to make sure any constraints are satisfied.

Which other package namespaces might benefit from structured meta data and how would their schemas differ from the examples above?

Probably most that have base implementations and those that need package variants that operate on ndarrays and strided arrays. So stats/base/dists, string, etc.  But keeping scope limited and not branching out to all kinds of packages seems prudent.

The proposal above suggests adding the meta data to package.json files. This could lead to bloat in the package.json files. Another possibility is putting such info in a separate .stdlibrc file in the root package directory. Would this be preferrable?

In my view, bloat will not be an issue. Metadata would be stripped when publishing packages, so this would only affect the development environment. package.json is familiar to folks as source of package metadata, and easily loadable as JSON. Custom file would be unfamiliar to developers.

Re: extra keywords. The point here is that there are keywords which are universal for a particular conceptual function and which should be included in all downstream scaffolded packages, and others which are not universal and which scaffolding tool may, or may not, be interested in using.

increases duplication of package documentation even more...this will be decently easy to add for existing packages but then cause an additional burden when trying to add new packages.

I don't have a simple answer here. To me, it is a balance of trade-offs. Right now, the situation is not tenable, as we need to individually define example ranges, aliases, etc, for all higher order packages (e.g., strided, iter, ndarray), which vastly outweighs the maintenance and creation burden if we bite the bullet when creating a base package in the first place.


CommComm work catchall for light agenda days

@bnb and I talked about doing some work on meeting days when there is little to no agenda.
Please drop your work suggestions here and we can build out specific issues if need be.

Working on meta documents would be nice. There's a decent number of documents that are somewhat outdated, and processes or goals we were hopeful to implement but never actually did.

Updating the CommComm section on the current website.

I've unarchived this repo so I can close all PRs and issues before re-archiving.


build: allow c++17 standard to be used for compilation

This will allow compiling with the c++17 standard, which on some distributions (macOS, FreeBSD) is required when using system dependencies.
Draft - depends on #3560
Enables resolution of #3547 and simplifies macOS custom builds.

ACK. Built and tested unit tests and qa suite on x86_64-pc-linux-gnu 22.04.

Also ACK but I'll review after #3560 is merged and this is rebased.

Rebased and pulled out of draft now.


Map - map-markers request sync bug for continuous overlay variables

To reproduce on qa at the moment:
Megastudy
Bar markers (though probably donuts will do this too)
Bar variable = collection start date
Then draw a region on the timeslider - all is well
Then draw a different region on the timeslider - you should see a 500 in dev tools and probably a pink warning on screen.
The problem appears to be an outdated overlayConfig sent to the back end.

@bobular @moontrip
I seem to recall that DK has a solution for this in a PR. Is that correct?

@dmfalke well, I never saw this ticket till your mentioning, so nope 😓

Okay, thanks! I might be thinking of #572

@dmfalke Ah I see. Yes it was assigned to me and I am examining it now 👍

@bobular I tested this a lot but I could not replicate the issue. It might have been a backend issue (e.g., incomplete data etc.) at that time?

Let's leave this open until I've finished with #794 - I'll check it's still OK and then close this.

This isn't reproducible but there's another issue which I will make a ticket for...


I can't find my snapshot store but everything is working

Hi I am working with akka.Persistence with Mongo, below is my HOCON
 <akka>
    <hocon>
      <![CDATA[

    akka {
      loglevel = INFO
      }

      akka.persistence {
          journal {
          plugin = "akka.persistence.journal.mongodb"
	          mongodb {
		          # qualified type name of the MongoDb persistence journal actor
		          class = "Akka.Persistence.MongoDb.Journal.MongoDbJournal, Akka.Persistence.MongoDb"

		          # connection string used for database access
		          connection-string = "mongodb://<IP_ADDRESS>:27017/akkaPersistence"

		          # should corresponding journal table's indexes be initialized automatically
		          auto-initialize = on

		          # dispatcher used to drive journal actor
		          plugin-dispatcher = "akka.actor.default-dispatcher"

		          # MongoDb collection corresponding with persistent journal
		          collection = "EventJournal"

		          # metadata collection
		          metadata-collection = "Metadata"
	          }
          }

          snapshot-store {
	          mongodb {
		          # qualified type name of the MongoDB persistence snapshot actor
		          class = "Akka.Persistence.MongoDb.Snapshot.MongoDbSnapshotStore, Akka.Persistence.MongoDb"

		          # connection string used for database access
		          connection-string = "mongodb://<IP_ADDRESS>:27017/akkaPersistence"

		          # should corresponding snapshot's indexes be initialized automatically
		          auto-initialize = on

		          # dispatcher used to drive snapshot storage actor
		          plugin-dispatcher = "akka.actor.default-dispatcher"

		          # MongoDb collection corresponding with persistent snapshot store
		          collection = "akkaShots"
	          }
          }
      }
    }

  ]]>
</hocon>

What's interesting is I checked my database, there is no collection that holds the snapshots. But everything works just fine. I restarted my system and still no collection yet snapshots get restored (so no in-memory, I know restarting the console would have worked too, but I thought it's my database that's not showing it to me).
I have the collection that holds the EventJournal, I am curious as to where are the snapshots restored from.
I am using
SaveSnapshot(actorState);  // to store the state
Recover<SnapshotOffer>(x=> {..});  // to restore

A default snapshot store stores snapshots as files under ./snapshot directory.

@Horusiath Ahh, on the windows file system that'll be in users? Next  thing, what's wrong with my HOCON? why isn't it using mongo when the message persistence works just fine.

@ImCarrot you've specified akka.persistence.journal.plugin = akka.persistence.journal.mongodb correctly, but you haven't done the same for snapshot. You need akka.persistence.snapshot-store.plugin = akka.persistence.snapshot-store.mongo in your HOCON config.


Simultaneous @api-see annotations don't work

Apparently using two @api-see annotations on the same @api-data doesn't work.
/**
 * @api-data metadata.connections.versions (object) - Information about the versions of this video.
 * @api-see \Vimeo\Api\Representation\Connection::create metadata.connections.versions
 * @api-see self::getVersions
 */

When that's generated, only the @api-see self::getVersions is picked up. Everything from \Vimeo\Api\Representation\Connection::create is ignored.
// @kenyavs

Fixed this in 3.0.

Fixed this in 3.0.


Create travis builds for all components

Those travis builds will build docker images and push those to docker hub on commit.
node-example: https://github.com/dirkwall/github-service
java-example: https://github.com/keptn-sockshop/carts
Following files are needed in the repository:

.travis.yml: contains the build information and is preconfigured to work with the git flow branching model and name restrictions for branches (if the names are not correct, no build is triggered)
MANIFEST: template file for including artifact information within the container
./writeManifest.sh: script that is used during the build to populate the MANIFEST with values
version: this holds the current version of the artifact; irrelevant to feature, bugfix, hotfix, and develop branches; relevant for release/x.x.x branches and master

Furthermore, a small change in the Dockerfile is necessary that prints the content of the MANIFEST in the logs, e.g. changing from
FROM java:openjdk-8-alpine
WORKDIR /usr/src/app
COPY target/*.jar ./app.jar
ENTRYPOINT ["java","-Djava.security.egd=file:/dev/urandom","-jar","./app.jar", "--port=8080"]

to
FROM java:openjdk-8-alpine
WORKDIR /usr/src/app
COPY ./target/*.jar ./app.jar
COPY ./MANIFEST /
CMD ["sh", "-c", "cat /MANIFEST && java -Djava.security.egd=file:/dev/urandom -jar ./app.jar --port=8080"]

or from
FROM node:10-alpine
ENV NODE_ENV "production"
ENV PORT 8080
EXPOSE 8080
RUN addgroup mygroup && adduser -D -G mygroup myuser && mkdir -p /usr/src/app && chown -R myuser /usr/src/app

# Prepare app directory
WORKDIR /usr/src/app
COPY package.json /usr/src/app/
RUN npm install -g tsc
RUN npm install -g concurrently
RUN npm install -g typescript
RUN npm install -g copyfiles

COPY . /usr/src/app
RUN ls -la /usr/src/app/*
RUN npm install
RUN npm run build-ts
USER myuser

# Start the app
CMD ["/usr/local/bin/npm", "start"]

to
FROM node:10-alpine
ENV NODE_ENV "production"
ENV PORT 8080
EXPOSE 8080
RUN addgroup mygroup && adduser -D -G mygroup myuser && mkdir -p /usr/src/app && chown -R myuser /usr/src/app

# Prepare app directory
WORKDIR /usr/src/app

COPY package.json /usr/src/app/
RUN npm install -g tsc
RUN npm install -g concurrently
RUN npm install -g typescript
RUN npm install -g copyfiles

COPY . /usr/src/app

RUN ls -la /usr/src/app/*

RUN npm install
RUN npm run build-ts

USER myuser

# Start the app
CMD ["sh", "-c", "cat MANIFEST && /usr/local/bin/npm start"]

Repos in which the travis build is setup:

[ ] github-service
[ ] jenkins-service
[ ] servicenow-service
[ ] ...


refactor: fix sort order

I want to merge this change because it fixes #170
Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted to .pot file.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Thanks for contributing to Saleor! We'll try to review the PR as soon as possible. But before we can merge it, you need to fix the tests as they're now failing on CI (see the Travis check above).


Posgress SLL on local V3 deployment

Can we get / disable SSL on postgres connection?

It's still actively in development, so I would ask to please not open any issues on v3 as of yet :)
I'm trying to make SSL optional for sure as I'm sure many self-hosted options won't require SSL certificates. Will definitely be as user-friendly as possible when it's completed.

I see, thanks for the fast response. Just pretty curious to try but blocked by SSL postgres. Good work as always.


⚠ Bofrost.lu has degraded performance

In ae66fdf, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1396 ms

Resolved: Bofrost.lu performance has improved in e56c4a3 after 6 minutes.


exampleSite themesDir added; Next and Prev will be deprecated, use NextPage a…

…nd PrevPage respectively
the changes on single.html from the layouts dir of Prev and Next to PrevPage and NextPage come from the most recent hugo

Thank you so much for you pull request. I am not always aware of changes between new versions, so this kind of support is always welcome.


Unable to run init container "patch-log-dirs" without root user

We are using this chart in the company, to install in our AKS clusters. Here we have some security restrictions for containers while running. For example  they can´t run as root user and can´t have privileged access to file system, so we needed to create this security context.
SecurityContext:
    capabilities:
      drop:
        - NET_RAW
    readOnlyRootFilesystem: true
    runAsNonRoot: true
    runAsUser: 20000
    runAsGroup: 20000
    allowPrivilegeEscalation: false

But if we check the values.yaml is says:
"To collect container logs and journald logs, it will run the agent as a root user.
To run it as non root user, uncomment below securityContext options.
Setting runAsUser and runAsGroup to a non root user enables an init container that patches group
permissions of container logs directories on the host filesystem to make logs readable by this non root user."
But as the restrictions of the container that I already mentioned and because of the security context (this is for ALL containers, including init), Daemonset pods are unable to start. Log of pod is just saying:
Error from server (BadRequest): container "otel-collector" in pod "test-08-splunk-otel-collector-agent-5c9fm" is waiting to start: PodInitializing
Error log of init container:
ownership of '/var/addon/splunk/otel_pos/receiver_journald_docker' retained as 20000:20000
ownership of '/var/addon/splunk/otel_pos/receiver_filelog_' retained as 20000:20000
ownership of '/var/addon/splunk/otel_pos/receiver_journald_kubelet' retained as 20000:20000
ownership of '/var/addon/splunk/otel_pos' retained as 20000:20000
mode of '/var/addon/splunk/otel_pos' retained as 2775 (rwxrwsr-x)
setfacl: /var/log/pods/monitoringapps_spc-test-08-splunk-otel-collector-agent-5c9fm_d51656c3-007e-4018-bba5-c1154cd6610d/patch-log-dirs/6.log: Operation not permitted
setfacl: /var/log/pods/monitoringapps_spc-test-08-splunk-otel-collector-agent-5c9fm_d51656c3-007e-4018-bba5-c1154cd6610d/patch-log-dirs/5.log: Operation not permitted
setfacl: /var/log/pods/monitoringapps_spc-test-08-splunk-otel-collector-agent-5c9fm_d51656c3-007e-4018-bba5-c1154cd6610d/migrate-checkpoint/0.log: Operation not permitted

I asume is because the patch log initcontainer  now doesn´t have the access to the Fylesystem files.
Is there a way we can use this chart other way. Probably without any initcontainer and moving the volumes to a PVC with ReadWriteMany access mode?
I´m sure we are not the only ones trying to implement this in a company with security restrictions.
We would appreciate your help.
Thank you.

UPDATE.
I did what I suggested and created the PVC as indicated in image for varlog and varlibdockercontainers
and it worked, pods are running...but! If I got to splunk cloud I don´t see any logs being sent from the cluster :(
So I rolled it back as it was ( without pvc  and also user 0 as the default user with no security context), and deployed the helm  chart in a namespace with no security restrictions, and logs are being sent to splunk cloud platform with no problem.

Here are the logs of the running pod.
2023/04/17 18:34:12 settings.go:331: Set config to [/conf/relay.yaml]
2023/04/17 18:34:12 settings.go:384: Set ballast to 165 MiB
2023/04/17 18:34:12 settings.go:400: Set memory limit to 450 MiB
2023-04-17T18:34:12.318Z        info    service/telemetry.go:90 Setting up own telemetry...
2023-04-17T18:34:12.318Z        info    service/telemetry.go:116        Serving Prometheus metrics      {"address": "<IP_ADDRESS>:8889", "level": "Basic"}
2023-04-17T18:34:12.318Z        info    extension/extension.go:148      Stability level of component is undefined       {"kind": "extension", "name": "k8s_observer"}
2023-04-17T18:34:12.319Z        info    kube/client.go:101      k8s filtering   {"kind": "processor", "name": "k8sattributes", "pipeline": "logs", "labelSelector": "", "fieldSelector": "spec.nodeName=aks-regularapps-35984879-vmss000000"}
2023-04-17T18:34:12.320Z        info    memorylimiterprocessor@v0.72.0/memorylimiter.go:113     Memory limiter configured       {"kind": "processor", "name": "memory_limiter", "pipeline": "logs", "limit_mib": 450, "spike_limit_mib": 90, "check_interval": 2}
2023-04-17T18:34:12.403Z        info    service/service.go:140  Starting otelcol...     {"Version": "v0.72.0", "NumCPU": 4}
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:41     Starting extensions...
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:44     Extension is starting...        {"kind": "extension", "name": "file_storage"}
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:48     Extension started.      {"kind": "extension", "name": "file_storage"}
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:44     Extension is starting...        {"kind": "extension", "name": "health_check"}
2023-04-17T18:34:12.403Z        info    healthcheckextension@v0.72.0/healthcheckextension.go:45 Starting health_check extension {"kind": "extension", "name": "health_check", "config": {"Endpoint":"<IP_ADDRESS>:13133","TLSSetting":null,"CORS":null,"Auth":null,"MaxRequestBodySize":0,"IncludeMetadata":false,"Path":"/","CheckCollectorPipeline":{"Enabled":false,"Interval":"5m","ExporterFailureThreshold":5}}}
2023-04-17T18:34:12.403Z        warn    internal/warning.go:51  Using the <IP_ADDRESS> address exposes this server to every network interface, which may facilitate Denial of Service attacks
        {"kind": "extension", "name": "health_check", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:48     Extension started.      {"kind": "extension", "name": "health_check"}
2023-04-17T18:34:12.403Z        info    extensions/extensions.go:44     Extension is starting...        {"kind": "extension", "name": "k8s_observer"}
2023-04-17T18:34:12.404Z        info    extensions/extensions.go:48     Extension started.      {"kind": "extension", "name": "k8s_observer"}
2023-04-17T18:34:12.404Z        info    extensions/extensions.go:44     Extension is starting...        {"kind": "extension", "name": "memory_ballast"}
2023-04-17T18:34:12.502Z        info    ballastextension@v0.72.0/memory_ballast.go:52   Setting memory ballast  {"kind": "extension", "name": "memory_ballast", "MiBs": 165}
2023-04-17T18:34:12.502Z        info    extensions/extensions.go:48     Extension started.      {"kind": "extension", "name": "memory_ballast"}
2023-04-17T18:34:12.502Z        info    extensions/extensions.go:44     Extension is starting...        {"kind": "extension", "name": "zpages"}
2023-04-17T18:34:12.502Z        info    zpagesextension@v0.72.0/zpagesextension.go:64   Registered zPages span processor on tracer provider     {"kind": "extension", "name": "zpages"}
2023-04-17T18:34:12.502Z        info    zpagesextension@v0.72.0/zpagesextension.go:74   Registered Host's zPages        {"kind": "extension", "name": "zpages"}
2023-04-17T18:34:12.502Z        info    zpagesextension@v0.72.0/zpagesextension.go:86   Starting zPages extension       {"kind": "extension", "name": "zpages", "config": {"TCPAddr":{"Endpoint":"localhost:55679"}}}
2023-04-17T18:34:12.502Z        info    extensions/extensions.go:48     Extension started.      {"kind": "extension", "name": "zpages"}
2023-04-17T18:34:12.502Z        info    internal/resourcedetection.go:136       began detecting resource information    {"kind": "processor", "name": "resourcedetection", "pipeline": "logs"}
2023-04-17T18:34:12.607Z        info    internal/resourcedetection.go:150       detected resource information   {"kind": "processor", "name": "resourcedetection", "pipeline": "logs", "resource": {"azure.resourcegroup.name":"s00175rgaksvmsscloudappsd01-1","azure.vm.name":"aks-regularapps-35984879-vmss_0","azure.vm.scaleset.name":"aks-regularapps-35984879-vmss","azure.vm.size":"Standard_E4s_v3","cloud.account.id":"535d8f2e-f08c-4475-8608-3b8136d13cbd","cloud.platform":"azure_aks","cloud.provider":"azure","cloud.region":"eastus2","host.id":"c9b603f6-de1a-4899-8992-daa8dfeec480","host.name":"aks-regularapps-35984879-vmss_0","os.type":"linux"}}
2023-04-17T18:34:12.608Z        info    adapter/receiver.go:56  Starting stanza receiver        {"kind": "receiver", "name": "filelog", "data_type": "logs"}
2023-04-17T18:34:12.608Z        info    fileconsumer/file.go:337        Resuming from previously known offset(s). 'start_at' setting is not applicable. {"kind": "receiver", "name": "filelog", "data_type": "logs", "component": "fileconsumer"}
2023-04-17T18:34:12.614Z        warn    fileconsumer/file.go:63 no files match the configured include patterns  {"kind": "receiver", "name": "filelog", "data_type": "logs", "component": "fileconsumer", "include": ["/var/log/pods/*/*/*.log"], "exclude": ["/var/log/pods/monitoringapps_spc-test-012-splunk-otel-collector*_*/otel-collector/*.log"]}
2023-04-17T18:34:12.615Z        warn    internal/warning.go:51  Using the <IP_ADDRESS> address exposes this server to every network interface, which may facilitate Denial of Service attacks
        {"kind": "receiver", "name": "otlp", "data_type": "logs", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-04-17T18:34:12.615Z        info    otlpreceiver@v0.72.0/otlp.go:94 Starting GRPC server    {"kind": "receiver", "name": "otlp", "data_type": "logs", "endpoint": "<IP_ADDRESS>:4317"}
2023-04-17T18:34:12.615Z        warn    internal/warning.go:51  Using the <IP_ADDRESS> address exposes this server to every network interface, which may facilitate Denial of Service attacks
        {"kind": "receiver", "name": "otlp", "data_type": "logs", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2023-04-17T18:34:12.615Z        info    otlpreceiver@v0.72.0/otlp.go:112        Starting HTTP server    {"kind": "receiver", "name": "otlp", "data_type": "logs", "endpoint": "<IP_ADDRESS>:4318"}
2023-04-17T18:34:12.615Z        info    healthcheck/handler.go:129      Health Check state change       {"kind": "extension", "name": "health_check", "status": "ready"}
2023-04-17T18:34:12.615Z        info    service/service.go:157  Everything is ready. Begin running and processing data.

The container logs live on the hostPath, not on the PVC you create.
We pick up the k8s logs from the hostPath and they are owned root:root by default, so the init container requires root to configure the agent pod, then finishes leaving no pod running as root.
To pick up k8s logs from the host you will require elevated privileges at some point. So you'll need to speak with your k8s admins.
Kubernetes has not solved for the kubelet putting the logs down as root:root by default as far as I know.

ok thanks @matthewmodestino understood. We´ll see how we figure this out.
thank you.

Closing as inactive. Please reopen if the issue is still occurring.


Bulding with RC1 CoreCLR produces 'unable to resolve ...' errors under 1.0.0-rc1-final on OS X

I've encountered that problem when working with RC1 builds (but now confirmed with final RC1 installed via official package) and people are reporting this as well on generator-aspnet:
https://github.com/OmniSharp/generator-aspnet/issues/509
Steps to repeat:

clone this repo
make sure to using latest bits
switch to samples/1.0.0-rc1-final/HelloMvc
make sure your runtime is CoreCLR:

dnvm use -r coreclr 1.0.0-rc1-final

dnvm list
Active Version              Runtime Architecture OperatingSystem Alias
------ -------              ------- ------------ --------------- -----
  *    1.0.0-rc1-final      coreclr x64          darwin          default
       1.0.0-rc1-final      mono                 linux/osx

run dnu restore which ends fine:

Restore complete, 5073ms elapsed

NuGet Config files used:
    /Users/piotrblazejewicz/.config/NuGet/nuget.config
    /Users/piotrblazejewicz/git/Home/samples/1.0.0-rc1-final/nuget.config
    /Users/piotrblazejewicz/git/Home/samples/1.0.0-rc1-final/HelloMvc/nuget.config

Feeds used:
    https://nuget.org/api/v2/
    https://www.myget.org/F/aspnetrc1/api/v2/

run dnu build, which fails:

Using Package dependency System.Threading 4.0.0
    Source: /Users/piotrblazejewicz/.dnx/packages/System.Threading/4.0.0
  Unable to resolve dependency fx/mscorlib
  Unable to resolve dependency fx/System
  Unable to resolve dependency fx/System.Core
  Unable to resolve dependency fx/Microsoft.CSharp
....
Build failed.
    1 Warning(s)
    64 Error(s)

Time elapsed 00:00:05.7016511
Total build time elapsed: 00:00:05.8210009
Total projects built: 1

I'd be more then happy to move it to related project (coreclr or dnx?), if this one is not proper one.
Somehow related (at least could be found via Google/Bing):
https://github.com/aspnet/dnx/issues/2566
Thanks!

You can't build for dnx451 with coreclr on Unix systems

@BrennanConroy
Does it mean that some part of .NET Core are not yet available under CoreCLR and requires .NET or Mono?
And should I simply point people to check status on dotnet/coreclr project?
Thanks! (and sorry for questions)

For this particular case you need mono in order to build the 451 target

@BrennanConroy Thanks!

This is actually caused by a few factors:
When you call "dnu build" without specifying a target framework, it will attempt to build ALL targets specified in the project.json file.
For instance:
dnxcore50
dnx451
If you are currently using "dnu" from a CoreCLR version of the runtime, it will fail to build the dnx451 target framework as it is unable to resolve framework dependencies. The correct solution, for the time being is to do one of the following:

Build the dnxcore50 target (only) using the CoreCLR:

dnvm use default -r coreclr && dnu build --framework dnxcore50

Build both targets using the CLR (or Mono):

dnvm use default -r mono && dnu build

This problem also seems to happen if you target dnx46, even if it's the only target you have and if you're using mono. (I'm trying to build the app in Ubuntu using Mono <IP_ADDRESS> and runtime 1.0.0-rc1-final)
Any ideas why this happens? Or a workaround?

dnx46 isn't supported by mono, I don't believe... so you would have to stick with 4.5.1 for now for xplat.

That's definitely unfortunate, but I'll stick to 4.5.1 then.
Thank you for the answer


Add compatibilty matrix

Hi team
Applying this Pull request the compatibility matrix is created with the information about the versions tested in the CI system.
Thanks!

If possible, we should update the compatibility matrix with data from testing environments (see #13).

Updated @lnovara ;)
Thanks!


When will there be a Java version of the Server SDK?

We use Java on the back end, and if we use the Go server SDK, we will use Java to call the GO service through RPC.

hi @hweeeeeei, a Java server SDK isn't currently in our roadmap. However, we would love to see community efforts here. It should be possible by using Twirp for Java
additionally, you could use the server APIs via HTTP Posts. details here

Thank you for your reply. I will consider encapsulating the Twirp service interface of HTTP calling GO language in Java and using JSON to transmit data.

If I complete the Java-SDK, I will upload it to my Git repository and open source it


Syntax highlighting problem with triple-quotes

I am using Juno on Ubuntu 16.04 and I use triple quotes for documentation in my project. But it seems Juno does not handle syntax highlighting when opening """ is followed by newline as shown in the following figure.

while when line start right after opening """ it looks fine

Is there any solution to this problem or it is an intended behavior.

I can't reproduce this. Is your version of language-julia up to date?

@pfitzseb The problem is _ (underscore). If you put underscore then you will be able to reproduce the error.

Oh, I see. This is because _ starts an italic scope in Markdown, i.e. _italic_ -> italic.
You can just put the _a in a code block using backticks:
`_a`

Also related: https://github.com/JuliaLang/atom-language-julia/issues/33

I'll close this is in favour of the issue over at atom-language-julia.

I'm having the same issue. Although there's an underscore in my docstring, it doesn't seem to be the source of the problem:

Removing the underscore doesn't change anything. Atom 1.10.2 with all packages updated a few minutes ago.

That's a different problem though (or rather not a problem at all, probably). The scope at the cursor in the first picture is string.docstring.julia, while it's string.quoted.triple.double.julia -- the difference in highlighting is probably due to your syntax theme highlighting docstring differently than string.
Which syntax theme are you using?

I use Solarized Dark.

Yeah, solarized dark doesn't support highlighting .string without it also being .quoted. Maybe open an issue over at atom-language-julia regarding that, or at the solarized dark repo to add a language specific stylesheet.

Thanks. Open issue: https://github.com/atom/solarized-dark-syntax/issues/74.


Add a way to make the preview editor tab more visually distinct

I like the preview editor tab feature (single click to open a file in a preview mode), but currently the preview tab is not visually distinct enough for me. I'd love to be able to configure the preview tab title/content/open-editors-entry to be a different colour, have a separate icon or somehow more easily distinguished from other tabs as italics in the title isn't very noticable.
This should also reduce the confusion of people new to the editor about how the editor tabs behave.

Assuming this is about previewing markdown.

No, this is about the "workbench.editor.enablePreview": true feature.


Avoid NPE on getSubnetIp()

Avoids direct access to node field, which may be null.

Jenkins failure is unrelated! Details to follow in mailing list.

LGTM - this now matches the code in master. Merging into 0.9.x branch.


Make gometalinter work again

They changed their logic to use related paths instead of absoluut paths (see here)
This fixes the linter by also using relative paths…

Updated to use ale#Escape(l:filename) instead.
About the regex part... I guess it's more pure to escape everything properly, but I doubt if it's really needed as I never saw an issue about the current value passed to the --include flag.
Not here and not with vim-go, so it feels like fixing something that isn't actually broken... If you insist on adding the escaping, I need some help in doing so as I don't know how that should be done in a nice way in vimscript.

The escaping will probably be needed for Windows support, where paths mostly use backslashes.

Use something like this:
l:path_regex = substitute(l:path, '\([.\\]\)', '\\\1', 'g')

Just add more characters than just . and \, put it in a function, and test that function with Vader tests.

I'll take this and sort the regex escaping out.

I did have look at it, but didn't manage to get a working test in place before I needed to continue with my day job.... So thanks for getting this fix in!

For anyone finding this issue and/or having issues with gometalinter, please first run :GoUpdateBinaries within [n]vim or go get -u github.com/alecthomas/gometalinter within your terminal. Most likely that will fix your problems...