Add shellcode generation for client both for windows x86 and x64 and linux

I just want to add a suggestion for adding an option that allows the user to generate x86/x64 shellcode for windows or linux

Hi there,
Not sure what you mean by this, reverse ssh is quite large in size (even with upx) so the shellcode would be several megabytes in size which isn't particularly useful for any exploitation I know of.
As it currently stands reverse ssh is solidly a post exploitation tool that enables more advanced "management" of targets.
Rather than your first tool through the door.
If you define what youre looking to accomplish a bit more I might be able to help, but for now this will probably me marked as won't fix sorry!

Well for post exploitation it would be nice to add the ability to generate the shellcode or possibly allow the user to invoke shellcode stored from an external address from a hosted webserver hosting the binary shellcode instead of taking the raw hexadecimal shellcode data and having to input it into another executable. So during runtime it could grab the shellcode from the external address and execute it into memory without storing the shellcode to disk. I don't know that was just an idea that I had from seeing another github repository with the same idea. Of course this isn't utilizing shellcode but instead using AES encryption but I thought it might be a good idea to do the same with shellcode as well but I just wanted to give my input on something that might be useful in the future.
https://github.com/TheD1rkMtr/FilelessPELoader

Oh also I have another issue. When generating a windows x64 compiled client I am able to setup the RSSH_HOMESERVER but when generating the client and running it. It doesn't connect back to the server but when adding the -d arguments it works for connecting back to the server. But the RSSH_HOMESERVER argument during compiling should've made it so that the executable during runtime would connect back to the server without providing an argument. This is the command I used
GOOS=windows GOARCH=amd64 RSSH_HOMESERVER=<IP_ADDRESS>:4200 make client

So. In further review of your request, and the provided example this already exists in RSSH.
The RSSH server can generate and provide portal executables via http and the link command in the server console. This lets you pull an RSSH client binary and from there its up to you to load it into memory however you wish.
If you're asking for me to implement something like the loader stage that would connect back to the RSSH server and pull said binary thats out of scope of this project.

As for your issue. I cannot replicate this. I have used your exact command line and can see the value is injected into the binary and when running with --foreground can see the client connects


The parameter of shape and scale become NaN

hello, I use to DeepRecurrentSurvivalMachines to model the staying length in ICU, the parameter of shape and scale become NaN after the first back propagation. how to deal with input data?

are you sure there are no nans in the input or the labels?

Thanks for your reply! I have fixed the problem. There is a zero value in survival time.

great,  Thank you 👍 :)


在Samsung   SM-N9200 Android 6.0.1  api23会崩溃

EasyPermissions.requestPermissions(this, getString(R.string.rationale_camera), RC_CAMERA_PERM, Manifest.permission.CAMERA);
时候会崩溃

@921668753 I'm sorry but I have to close this issue since it doesn't contain any debugging information in English.  Maybe try StackOverflow?


Resize CPU and Memory Resources assigned to Containers

This is a alpha version，default disable. How to enable this feature in Kubernetes v1.28?
Does it work with the static cpu manager policy feature?
I use this feature in Kubernetes v1.28. It can work when cpu manager policy set none.
But It can't work when cpu manager policy set static. so I have above question.

/kind support

@axi-lyp support tickets are not the correct platform for queries
You can always reach out in Kubernetes Slack for assistance
/close


revendor (org.opencontainers.ref.name -> org.opencontainers.image.ref…

….name)
Fix https://github.com/projectatomic/skopeo/issues/348
https://github.com/containers/image/pull/278#issuecomment-304257815
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

LGTM

reran vndr. some lines are updated by vndr

@AkihiroSuda after you edited vndr.conf you should have just ran:
vndr github.com/containers/image
vndr github.com/BurntSushi/toml

Please do that and discard any other fixes/changes you did, let's make a separate PR for that.

@AkihiroSuda after you edited vndr.conf you should have just ran:
vndr github.com/containers/image
vndr github.com/BurntSushi/toml

Please do that and discard any other fixes/changes you did, let's make a separate PR for that :heart:

That is locally convenient, but it also makes it way too easy for vendor.conf and the contents of vendor to drift away.
I guess both local vendor updates like the above (if the complete refresh happens frequently enough), and a full vndr re-run within an otherwise unrelated PR, are fine with me.
(Non-ABI-stable dependencies and vendoring and staying on a specific commit without future bugfixes is all problematic, *grumble* I don’t have a good solution given the existing ecosystem, *shuts up*.)

The current test failure looks like a missing git add.

revendored

I needed to use older vndr (LK4D4/vndr@78865), because the current vndr requires me to rewrite vendor.conf to the new format
Eliminated vendoring for toml (unneeded for this case)

This updates vendor.confto point to a newer containers/storage version, yet the PR is not actually updating containers/storage, and the dependency necessary for that new version is not listed either; that’s just a trap left for the next person to run vndr.
Please, either run vndr only containers/image, in which case leave the other repos in vendor.conf unmodified, or do a full vndr run where both the vendor directory and vendor.conf are fully consistent.

vndred containers/image@master only, PTAL?

LGTM but needs rebase

github says "Pull request successfully merged and closed" but it does not seems merged..

github says "Pull request successfully merged and closed" but it does not seems merged..

:confused: yeah, it seems closed actually.

I can't reopen it :confused:

np, https://github.com/projectatomic/skopeo/commit/63272a10d7f8116d06aca8324889ff1174db6f42 already contains this change

and hence rebase & push -f resulted in closing this PR


Make typer default to not generate --no-something for bool option

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Typer documentation, with the integrated search.
[X] I already searched in Google "How to X in Typer" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to Typer but to Click.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
import typer

def main(force: bool = typer.Option(False, "--force", help="very long and verbose string here")):
    print(f"{force = }")

if __name__ == "__main__":
    typer.run(main)

```sh
 ~  python foo.py --help

 Usage: foo.py [OPTIONS]

╭─ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --force                                                                                │
│ --install-completion          Install completion for the current shell.                                                                                │
│ --show-completion             Show completion for the current shell, to copy it or customize the installation.                                            │
│ --help                        Show this message and exit.                                                                                │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Description

There are more times when --no-something is simply not needed, since default values is False for options anyway.
--no-something wastes terminal space tremendously
writing something: bool = typer.Option(False, --something`) is especially meaningless and painful for multiple options.
Option can't be ditched away because we need help for it.

Wanted Solution
make typer Option behavior default to not generate --no-something, only --something for something = Option(...).
we can already generate --no-something using something = Option(..., '--something/--no-something).
Wanted Code
import typer

def main(force: bool = typer.Option(False, help="very long and verbose string here")):
    print(f"{force = }")

if __name__ == "__main__":
    typer.run(main)

Alternatives
pass ... to also indicate not generate --no-something?
Operating System
Linux
Operating System Details
No response
Typer Version
0.6.1
Python Version
Python 3.11.0rc2
Additional Context
with --no-something

without --no-something

Thanks for the suggestion! But it's by design, so that you could have a default of True as well, or you could change defaults down the line. But if you don't want those options or you want different names, you can still customize them.
Given that I'll close it, but thanks for the interest! ☕

the problem still isn't solved that in most cases you have to write everything twice.

Yep, that would depend on each app and use case. In yours, as you only use default False flags, I'm sorry the process is not as convenient. I might consider it again later, if I find a better way to support that, but for now I need to support other things and features.

yeah, however the problem with that solution is that everything needs to be type twice.


Not checking mimetype is uncompressed in Zip

From<EMAIL_ADDRESS>on September 17, 2013 13:12:06
PROBLEM: The epubcheck tool does not check that the mimetype entry in the Zip file is uncompressed, i.e. it is not following this part of the spec - http://www.idpf.org/epub/30/spec/epub30-ocf.html#sec-zip-container-mime
RESULT: At the moment epubs where the mimetype is compressed in the Zip erroneously pass the epubcheck tool
EXPECTED: If the mimetype is compressed in the epub, the epubcheck tool should fail the validation.
Original issue: http://code.google.com/p/epubcheck/issues/detail?id=304

I know this is old... but I couldn't reproduce. @adamretter would you still have a sample by any chance?

Resurrecting this rather old issue as we've recently encountered it issue ourselves and are able to provide some samples.
Attached zip file contains:

epub30-spec_uncompressed.epub - EPUB 3.0 specification in EPUB 3.0 format, mimetype entry stored uncompressed
epub30-spec_compressed.epub - EPUB 3.0 specification in EPUB 3.0 format, mimetype entry stored compressed
epub30-spec_uncompressed.epubcheck.xml - epubcheck 4.0.1 output when run against file epub30-spec_uncompressed.epub
epub30-spec_compressed.epubcheck.xml - epubcheck 4.0.1 output when run against file epub30-spec_compressed.epub

As the XML output shows, both epub files validate despite the mimetype entry being compressed in one of them. Viewing the "compressed" version in a hex editor shows an incomplete mimetype entry at byte offset 30, reading simply "mimetype".


chore: add prettier plugin to sort imports

Jira: LF-7839
Applies sorting using prettier - which means that if anyone runs prettier on save will get instant sorting of imports
I have ended up adding the format command to the pre-commit hook script execution so that even if anyone commits without first running prettier imports should be sorted to the correct order - this will impact the speed of the pre-commit validation.
I explored two plugin options on this PR the first one was trying to use @trivago/prettier-plugin-sort-imports. The second was @ianvs/prettier-plugin-sort-imports
@trivago/prettier-plugin-sort-imports matched the alphabetic that matches what VSCode currently does but it also moves around "side effect" - this isn't a good thing and in some circumstances can actually break things.
So I moved to using @ianvs/prettier-plugin-sort-imports instead. This doesn't move the side effect imports and is therefore a little bit safer. Its sorting of named variables tends to case insensitive thought and not match the VSCode way of doing things - I wonder if as we are using prettier and this would be consistent across all IDE's anyway that this would be less important?
Last prettier plugin I tried was prettier-plugin-organize-imports - this one doesn't take into account side effects but I think its the closest to the vscode formatting. Seem to do the minimal changes with some packages remaining unchanged by running the format command.
I've retained the code changes for each plugin as commits on this branch so that changes that each prettier plugin can be looked at and compared in terms of output. Probably good to have a discussion to decide if we are happy to use prettier-plugin-organize-imports.

Updated the yarn lock file this should be good to merge


Nulls  are shown in char fields in Teradata

Teradata base by ODBC.
sel 'i'(char(1)) shows NULL
It's true for any chars (varchar works)

Please check error/debug logs (https://github.com/serge-rider/dbeaver/wiki/Log-files). If you will find anything related to to CHAR column reading - post it here.

Are your drivers up to date?

Last drivers download helped! Thanks!

What driver version helped plz.
I am facing the same issue with version Teradata ODBC v16, thx

@vachastepan Is your question still actual?


Fix beam_job_api to conform to proto naming conventions.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @tgroh

Changes Unknown when pulling 3e3b69cb9480289745a442a3f140646a390f9537 on robertwb:job-api-proto into ** on apache:master**.

Fixed the merge conflict, please take a look.

R: @lukecwik

Coverage decreased (-0.003%) to 69.962% when pulling 4764883a19174f0887ec091aa109e36881e102bf on robertwb:job-api-proto into aef89dea884319bc12885286a3a705e24794de48 on apache:master.


Rope pulley crashes the server

Describe the Bug
The rope pulley seems to be repeatedly crashing my server due to something related to malformed JSON.
Reproduction Steps
I'm not too sure about how to reproduce the issue but we do have a large rope pulley so I'm thinking it may have something to do with that. I can provide world download as well as mod pack if need be.
Expected Result
I expect the server not to crash
Screenshots and Videos
No response
Crash Report or Log
https://gist.github.com/7z99/0f12b3d80982fd9da85dc2aba54d1169
Operating System
Windows 10
Mod Version
0.5.0i
Minecraft Version
1.19.2
Other Mods
Here's a list of all mods on the server:
amethyst_core-1.0.4+1.19.jar
amethyst_imbuement-1.19-28.jar
another_furniture-fabric-2.1.2-1.19.2.jar
architectury-6.5.69-fabric.jar
balm-fabric-4.5.2+0 (1).jar
bclib-2.1.6.jar
better-end-2.1.4.jar
better-nether-7.1.3.jar
bettervillage-fabric-1.19.2-2.0.0.jar
BOMD-1.4.6-1.19.2.jar
cardinal-components-api-5.0.2.jar
chipped-fabric-1.19.2-2.1.0.jar
cloth-config-8.2.88-fabric.jar
create-fabric-0.5.0.i-961+1.19.2.jar
ctm-fabric-1.0.0+1.19.jar
Decorative Blocks-fabric-1.19.2-3.0.0.jar
DimThread-1.2.7.jar
dragonloot-1.1.2.jar
Dynmap-3.4-fabric-1.19.1.jar
ecologics-fabric-1.19.2-2.1.11.jar
fabric-api-0.73.2+1.19.2.jar
fabric-language-kotlin-1.9.1+kotlin.1.8.10.jar
fabric-tree-chopper-0.8.10.jar
farmers-delight-fabric-1.19.X-1.3.9.jar
fzzy_core-0.1.2+1.19.jar
geckolib-fabric-1.19-3.1.40.jar
icarus-1.13.jar
libraryferret-fabric-1.19.2-3.0.0.jar
lithium-fabric-mc1.19.2-0.10.4.jar
mcda-2.4.3.jar
mcdar-1.5.3-1.19.jar
mcdw-5.0.5-1.19.jar
mcw-doors-1.0.8fabric-mc1.19.2.jar
mcw-fences-1.0.7-mc1.19.2fabric.jar
mcw-paintings-1.0.4fabric-mc1.19.2.jar
mcw-trapdoors-1.0.8-mc1.19.2fabric.jar
mcw-windows-2.1.2-mc1.19.2fabric.jar
memoryleakfix-1.19.1-0.7.0.jar
moonlight-1.19.2-2.2.13-fabric.jar
morevillagers-fabric-1.19-4.0.2.jar
naturalist-fabric-2.1.1-1.19.2.jar
NaturesCompass-1.19.2-2.1.0-fabric.jar
netherportalfix-fabric-1.19-10.0.0.jar
Oh_The_Biomes_You'll_Go-fabric-1.19.2-<IP_ADDRESS>.jar
owo-lib-0.8.5+1.19.jar
phosphor-fabric-mc1.19.x-0.8.1.jar
PuzzlesLib-v4.3.12-1.19.2-Fabric.jar
resourcefullib-fabric-1.19.2-1.1.22.jar
RoughlyEnoughItems-9.1.591.jar
styled-nicknames-1.1.2+1.19.jar
supplementaries-1.19.2-2.2.50-fabric.jar
TerraBlender-fabric-1.19.2-<IP_ADDRESS>.ja
toolleveling-fabric-1.19.2-1.4.1.jar
trade-cycling-fabric-1.19.2-1.0.5.jar
trinkets-3.4.2.jar
twilightforest-fabric-1.19.2-4.2.335.jar
UniversalEnchants-v4.2.15-1.19.2-Fabric.jar
wraith-waystones-3.0.5+mc1.19.2.jar
Additional Context
I did make a mod dependency override for chipped to not require CTM so that may or may not be related.
Also we pay for a server so it's possible that OS on the server is different. Can get it if needed. Also can provide the full log instead of just the crashlog if needed.

closing in favor of #892


cmd/cover: add  tag to HTML template in go cover report

add missing  tag to HTML template used by go tool cover
This will make the HTML code coverage report more compliant, as  tags
are generally required in valid HTML documents.

@googlebot I signed it!

moved this pull request to main Go repository:
https://github.com/golang/go/pull/38313
Thanks @stamblerre


openhcl/tdx: implement wbinvd exits

Implement WBINVD exits by signalling to the kernel to issue the corresponding flush before calling VP.ENTER.
PENDING: kernel change and package update

Kernel package has been merged now.


Android error..."Get Google Play Services"

Great App and instructions..Thank you
I am running on error trying to open detail view on Android Emulator and devices. The Emulator shows "Get Google Play Services" and when clicked crashes. On Device crashes on opening detailed view.
Works Perfect on iOS...
Any help is greatly appreciated. Thanks

@safadig  hello! you need to use a emulator that includes the google maps and services. Check this small tutorial: http://hmkcode.com/run-google-map-v2-on-android-emulator/

Great. Thanks


[PE-D][Tester D] Allows names with one additional whitespace

add command allows the user to add the name that is already present in the list with one extra whitespace as shown below.

This may just be a user's mistake in the real world and the application would allow the user's mistake to pass through which can be considered a feature flaw as seen below.

Labels: severity.Medium type.FeatureFlaw
original: notle1706/ped#2

Closing reason : Wont fix


Result mismatch of hash aggregation between Spark and Velox

Bug description
I have a sql query that runs in gluten and vanilla spark, its format is as follows:
select count(*) from ((
    select *
    from test1
    where xxx
  )a
  left join
  (
    select *
    from test2
    where xxx
    group by col_a
            ,col_b
            ,col_c
            ,col_d
            ,col_e
  )b
ON a.col1 = b.col1);

I get different number of rows. And I look at the spark ui, I found the reason is that the numbers of rows of the second subquery don't match.
vanilla spark:

gluten:

Actually, I found that some rows are duplicate.
So I think there might be a bug for hash aggregation.
I'm sorry for not having a small example.
System information
Velox System Info v0.0.2
Commit: 8e0181ef723854b438b8e56d72bf87cb0cb51333
CMake Version: 3.17.5
System: Linux-3.10.0-862.mt20190308.130.el7.x86_64
Arch: x86_64
C++ Compiler: /opt/rh/devtoolset-10/root/usr/bin/c++
C++ Compiler Version: 10.2.1
C Compiler: /opt/rh/devtoolset-10/root/usr/bin/cc
C Compiler Version: 10.2.1
CMake Prefix Path: /usr/local;/usr;/;/usr;/usr/local;/usr/X11R6;/usr/pkg;/opt
Relevant logs
No response

Sorry, it's not a bug from Velox


Unable to load lvm attributes [lvs.yaml] for version [2.02.188(2)]

:pancakes: Cookbook version
5.2.0
:woman_cook:  Chef-client Version
17.7.29
:tophat: Platform details
sles 12 sp5
Steps To Reproduce
lvm_volume_group vg01r1 do
  physical_volumes volumes
  physical_extent_size '32M'
  logical_volume 'data' do
    size '100%VG'
    filesystem 'ext3'
    mount_point location: '/data', options: 'noatime,nodiratime'
    stripes volumes.count
    stripe_size 4
  end
end

Error
[2021-11-21T13:11:08+00:00] FATAL: ArgumentError: lvm_volume_group[vg01r1] (litc-docker::database-disk-sliced line 18) had an error: ArgumentError: Unable to load lvm attributes [lvs.yaml] for version [2.02.188(2)]. The version/object may not be supported or you may need to upgrade the chef-ruby-lvm-attrib gem. Error [No such file or directory @ rb_sysopen - /opt/chef/embedded/lib/ruby/gems/3.0.0/gems/chef-ruby-lvm-attrib-0.3.3/lib/lvm/attributes/2.02.188(2)/lvs.yaml]

@roee73 it looks like you're using an older chef-ruby-lvm-attrib gem. Can you please update it to the latest and confirm it's still not working? I think it will still not work but I wanted to confirm before making an upstream PR to resolve this. Thanks!

Yeah, that should fix it once it's merged/released.


#925: Tab Completion

Could not find contribution guidelines, I hope I'm not missing anything huge.
Did not include this in an installation script, to not force unwanted defaults.
#925

One other thing that I noticed is that the ollama create command seems to get messed up when you're trying to specify the Modelfile location.

Thank you for submitting this!
Most of my comments are inline, but I did have one problem trying to get this to work, which was that I couldn't get the models to complete correctly to autoCompleteModelname(). I'm assuming this is something that is potentially misconfigured in zsh and bash? I tested it with both and wasn't able to get it to work.

@pdevine Thanks for the review :) I fixed your inline comments, but I'm not sure how to reproduce your problem with autocompletions, for me it works well for both zsh and bash. Could you share some reproduction steps? Maybe some dependencies (like bash-completion) are lacking?

One other thing that I noticed is that the ollama create command seems to get messed up when you're trying to specify the Modelfile location.

That one seems to be working fine for me too, could you comment some examples?
https://github.com/jmorganca/ollama/assets/47815003/b025b634-afec-4648-9ecf-5547cdd66daf

Hey there, this is really cool. I am not having the issue @pdevine mentioned. The one change I think is needed is to not autocomplete the models on pull. Since you want to pull models from the library and not from your local machine.

I don't know if this is a fish vs bash issue. Works great in fish

Hey there, this is really cool. I am not having the issue @pdevine mentioned. The one change I think is needed is to not autocomplete the models on pull. Since you want to pull models from the library and not from your local machine.

Right! Done ✅


Update sbt-scalafmt to 2.4.2

Updates org.scalameta:sbt-scalafmt from 2.4.0 to 2.4.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-scalafmt" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #84 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #84   +/-   ##
=======================================
  Coverage   86.39%   86.39%
=======================================
  Files          18       18
  Lines         272      272
  Branches        8        8
=======================================
  Hits          235      235
  Misses         37       37

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 5b12e32...d69a986. Read the comment docs.


Data not getting consumed from all Kafka partitions

Issue currently being faced one of our users.
Topic has 3 partitions

Data getting pushed to all 3 partitions

When table was created, it was consuming data from all 3 partitions

However, after 24 hours, it has been consuming data only from partition 1. partition 0 an 2 segments show in the CONSUMING state and their metadata is also present in PROPERTY_STORE.

Resetting the stuck segments didn't work as well.

Here is what segments status looks like
{
  "id": "tSCalibrationAttempt_REALTIME",
  "simpleFields": {
    "BATCH_MESSAGE_MODE": "false",
    "IDEAL_STATE_MODE": "CUSTOMIZED",
    "INSTANCE_GROUP_TAG": "tSCalibrationAttempt_REALTIME",
    "MAX_PARTITIONS_PER_INSTANCE": "1",
    "NUM_PARTITIONS": "13",
    "REBALANCE_MODE": "CUSTOMIZED",
    "REPLICAS": "1",
    "STATE_MODEL_DEF_REF": "SegmentOnlineOfflineStateModel",
    "STATE_MODEL_FACTORY_NAME": "DEFAULT"
  },
  "mapFields": {
    "tSCalibrationAttempt__0__0__20220505T1656Z": {
      "Server_pinot-server-0.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__0__1__20220506T1656Z": {
      "Server_pinot-server-0.pinot-server-headless.pinot.svc.cluster.local_8098": "CONSUMING"
    },
    "tSCalibrationAttempt__1__0__20220505T1656Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__1__20220506T1656Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__2__20220509T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__3__20220510T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__4__20220511T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__5__20220512T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__6__20220513T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__7__20220514T0456Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__1__8__20220516T0657Z": {
      "Server_pinot-server-1.pinot-server-headless.pinot.svc.cluster.local_8098": "CONSUMING"
    },
    "tSCalibrationAttempt__2__0__20220505T1656Z": {
      "Server_pinot-server-0.pinot-server-headless.pinot.svc.cluster.local_8098": "ONLINE"
    },
    "tSCalibrationAttempt__2__1__20220506T1656Z": {
      "Server_pinot-server-0.pinot-server-headless.pinot.svc.cluster.local_8098": "CONSUMING"
    }
  },
  "listFields": {}
}

Data is not getting consumed from partition 0 and 2. For Partition 2, here's what metadata looks like
{
  "id": "tSCalibrationAttempt__2__0__20220505T1656Z",
  "simpleFields": {
    "segment.crc": "2706892624",
    "segment.creation.time": "1651769803410",
    "segment.download.url": "http://pinot-controller-0.pinot-controller-headless.pinot.svc.cluster.local:9000/segments/tSCalibrationAttempt/tSCalibrationAttempt__2__0__20220505T1656Z",
    "segment.end.time": "1651847119229",
    "segment.flush.threshold.size": "100000",
    "segment.index.version": "v3",
    "segment.realtime.endOffset": "819",
    "segment.realtime.numReplicas": "1",
    "segment.realtime.startOffset": "746",
    "segment.realtime.status": "DONE",
    "segment.start.time": "1651648021433",
    "segment.time.unit": "MILLISECONDS",
    "segment.total.docs": "73"
  },
  "mapFields": {},
  "listFields": {}
}

{
  "id": "tSCalibrationAttempt__2__1__20220506T1656Z",
  "simpleFields": {
    "segment.creation.time": "1651856206431",
    "segment.flush.threshold.size": "10000",
    "segment.realtime.numReplicas": "1",
    "segment.realtime.startOffset": "819",
    "segment.realtime.status": "IN_PROGRESS"
  },
  "mapFields": {},
  "listFields": {}
}

Table config:
{
  "REALTIME": {
    "tableName": "tSCalibrationAttempt_REALTIME",
    "tableType": "REALTIME",
    "segmentsConfig": {
      "schemaName": "tSCalibrationAttempt",
      "replication": "1",
      "timeColumnName": "coeff.calTimestamp",
      "allowNullTimeValue": false,
      "replicasPerPartition": "1",
      "completionConfig": {
        "completionMode": "DOWNLOAD"
      }
    },
    "tenants": {
      "broker": "DefaultTenant",
      "server": "DefaultTenant",
      "tagOverrideConfig": {}
    },
    "tableIndexConfig": {
      "invertedIndexColumns": [],
      "streamConfigs": {
        "streamType": "kafka",
        "stream.kafka.topic.name": "tscalibrationattempt",
        "stream.kafka.broker.list": "",
        "stream.kafka.consumer.type": "lowlevel",
        "stream.kafka.consumer.prop.auto.offset.reset": "largest",
        "stream.kafka.schema.registry.url": "",
        "stream.kafka.consumer.factory.class.name": "org.apache.pinot.plugin.stream.kafka20.KafkaConsumerFactory",
        "stream.kafka.decoder.prop.schema.registry.rest.url": "",
        "sasl.mechanism": "PLAIN",
        "stream.kafka.decoder.prop.basic.auth.credentials.source": "USER_INFO",
        "stream.kafka.decoder.prop.schema.registry.basic.auth.user.info": "",
        "security.protocol": "SASL_SSL",
        "sasl.jaas.config": "org.apache.kafka.common.security.scram.ScramLoginModule required username=\"\" password=\"\";",
        "stream.kafka.decoder.class.name": "org.apache.pinot.plugin.inputformat.avro.confluent.KafkaConfluentSchemaRegistryAvroMessageDecoder",
        "realtime.segment.flush.threshold.rows": "0",
        "realtime.segment.flush.threshold.time": "24h",
        "realtime.segment.flush.threshold.segment.size": "150M"
      },
      "rangeIndexColumns": [
        "coeff.calTimestamp"
      ],
      "rangeIndexVersion": 2,
      "autoGeneratedInvertedIndex": false,
      "createInvertedIndexDuringSegmentGeneration": false,
      "sortedColumn": [
        "deviceId"
      ],
      "bloomFilterColumns": [],
      "loadMode": "MMAP",
      "onHeapDictionaryColumns": [],
      "varLengthDictionaryColumns": [],
      "enableDefaultStarTree": false,
      "enableDynamicStarTreeCreation": false,
      "aggregateMetrics": false,
      "nullHandlingEnabled": false
    },
    "metadata": {},
    "quota": {},
    "routing": {
      "instanceSelectorType": "strictReplicaGroup"
    },
    "query": {},
    "ingestionConfig": {
      "complexTypeConfig": {
        "fieldsToUnnest": [
          "coeff"
        ]
      }
    },
    "isDimTable": false
  }
}

Update:
Once the problematic segments (tSCalibrationAttempt__2__1__20220506T1656Z and tSCalibrationAttempt__0__1__20220506T1656Z) are deleted via API call (DELETE /segments/{tableName}/{segmentName}) , the consumption resumes succesfully for partition 2 but no segments still created for partition 0.

@Jackie-Jiang @npawar what can be going on here?

Offset of last record produced in Partition 2 - 1085
Start offset of segment consuming from partition 2 - 891

@KKcorps this sounds similar to https://github.com/apache/pinot/issues/8219. This had happened because the server was down/consumption was lagging and the offset expired before it could be consumed. More details in the PRs linked to the issue.
Can you check with them for logs, and if you can see the same log lines as mentioned in the issue?

Neither of the PRs linked fix it cleanly. I think we should go with the 2nd approach https://github.com/apache/pinot/pull/8321/files but see if we can catch the exception and do it only on getting an OOR

I checked the server logs and not getting this kind of issues anywhere:
[Consumer clientId=consumer-null-12, groupId=null] Fetch position FetchPosition{offset=5011308265, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[xxx (id: 0 rack: us], epoch=6}} is out of range for partition xx-xx-xx-xx-3, resetting offset
Also the retention time of topics is 24 hr

@npawar can we atleast put some alerts in such cases where no segments are in GOOD state still they stopped consuming. Otherwise it will be an issue and how we can come out quickly from this situation. Please suggest which metrics or api can help to see if segment has stopped working.

The issue for this error is still unclear. Most likely cause is the offset.retention period getting expired (which is different from topic retention period). Out of Range errors were not found in logs nor was any segment deleted manually. In future there are 2 ways to fix similar errors -

The new segment consumption resume API - https://github.com/apache/pinot/pull/8663

Handle out of range in Kafka consumer (should handle the offset expiry as well) - https://github.com/apache/pinot/pull/8321

The metrics which currently can be used to track consumptions can be found in https://docs.pinot.apache.org/configuration-reference/monitoring-metrics.
A new metric to track offset lag per Kafka topic partitions is also WIP - https://github.com/apache/pinot/pull/8280


suggestion to add "handlePaste" option to the component

I'm not sure is it right place to suggestions, but still. I faced the situation when i need to pass custom "onpaste" function to component, is it possible to add this functionality in near future or i need to do in by myself? Thanks

I think that's an uncommon use-case, so that I don't see that being added in the near future. Having said that, if there are more requests for that feature I'll surely add it.
I'll leave this issue open as of now, and check back again in a while to see if there are any 👍 on this. Hope that answers your question!

This option could really help us a lot!


Standardized labels - fixes #20

Standardized labels; added skos:prefLabel, also. Corrected some definitions.

So we will have skos:prefLabels and rdfs:labels everywhere?  I may be remembering incorrectly, but I thought we might not have both, but standardize on one or the other, or have the ontology-toolkit convert 1 to the other.

Ah, so #20 fixes this one?  If so, we can delete this PR and the branch.  @DanCarey404 @rjyounes, what say you?

How did we get #20 closed without merging the PR? When a PR is merged, the issue gets closed (if keyword included in title) and the branch is deleted.

@marksem I thought this issue was just to change the label text. We have another issue for deciding on which annotation to use.

@rjyounes , looking at the changes,  prefLabels are being added, not just corrected.
You can always close PRs w/o merging.  Sometimes they are overcome by events (OBE).


Calculate nadir_za

📋 Info
Artifact correction in L1B requires nadir_za. To avoid calculating it on the fly, which requires skyfield as a dependency in https://github.com/innosat-mats/MATS-L1-processing, it could be pre-calculated here, like we do for other angles etc., see
https://github.com/innosat-mats/level1a/blob/main/level1a/handlers/mats_utils/coordinates.py .
Getting rid of skyfield again will likely solve some issues for the automated L1B processing as well.
🏁 DoD

[ ] Calculate nadir_za and store it
[ ] Is de421.bsp the database we should use, or is there a newer version, better suited to our needs? If not, update!

The key word nadir_az is more suitable in my opinion for solar NADIR AZimuth angle


[Reopen] Detox is adding SocketRocket as a dependency to my Podfile.lock

Description
Re-opened from #1893 since this is still an issue.
The postinstall script of detox extracts the Detox-ios-src archive in node_modules. This includes the ios-src/SocketRocket folder, which includes a podspec that will be read by the use_native_modules! directive in the Podfile of the react-native ios project.
I'm not 100% sure if this is the root cause, but it definitely has something to do with the ios_src folder and SocketRocket as a dependency, since it is being added to Podfile.lock.
This leads to inconsistent builds, since I don't get the SocketRocket pod added locally, but it is added on CI (where there is no previous build cache installed).

[X] I have tested this issue on the latest Detox release and it still reproduces

Reproduction

Ensure that the framework cache is cleared by running detox clean-framework-cache in your react-native project root folder
Remove the node_modules folder
Install node_modules (yarn or npm)
Install pods (cd ios; pod install)

-> SocketRocket is added to Podfile.lock
Expected behavior
SocketRocket should not be added to Podfile.lock.
One way to achieve this (?) might be to delete the ios_src folder after the postinstall script has run.
Screenshots
/
Environment (please complete the following information):

Detox: 15.1.4
React Native: 0.61.0
Node: 10.18.1
Device: /
Xcode: 11.3.1
iOS: /
macOS: 10.15.3

Logs
If you are seeing a build problem (e.g. during npm install)

[x] I am providing the npm install log below:

detox-test npm i detox

><EMAIL_ADDRESS>install /Users/juras/src/misc/detox-test/node_modules/dtrace-provider
> node-gyp rebuild || node suppress-error.js

  ACTION binding_gyp_ndtp_target_build_ndtp .
  TOUCH Release/obj.target/ndtp.stamp

><EMAIL_ADDRESS>postinstall /Users/juras/src/misc/detox-test/node_modules/detox
> node scripts/postinstall.js

Extracting Detox sources...
Building Detox.framework from /Users/juras/src/misc/detox-test/node_modules/detox/ios_src...
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 117 packages from 167 contributors and audited 318 packages in 42.494s

3 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Detox does not modify and Podfile. This could be a bug in CocoaPods. I suggest opening an issue with them to ask why this is happening. Detox is at no point added as a dependency in Podfile, so none of its contents should make its way to CocoaPods.

this is because there is a SocketRocket.podspec in node_modules/detox/ios_src/SocketRocket/. it's picked up automatically by React-Native autolinking.
it can be disabled by adding
module.exports = {
    detox: {
      // do not autolink detox
      platforms: {
        ios: null,
        android: null,
      },
    },
};

to react-native.config.js
But it will be the best if we can somehow remove the Podspec file from the published module.


[BUG] Media - Images lose basic metadata (iOS)

Image files contain basic metadata about the image. Exif and other information is lost when processed by the picker.
Bug can reproduced by extracting an image from the camera roll and the same image from the app after it has been processed by the picker. Both images then inspected using the preview app on the mac show a significant loss of metadata.

TakePhoto also only contains just "Orientation", "ColorSpace", "PixelXDimension" and "PixelYDimension"

@jamesmontemagno I heard that when you save the photo to the app's directory, it won't let you retain the metadata. Please if you can expose an option to save the photo to the user's album and retain meta data info? Also if you can include it to the MediaFile return.
Thanks!

+1

Duplicate of #76?

Sooooo, I added a new flag to save to gallery:
https://github.com/jamesmontemagno/Xamarin.Plugins/issues/149
Is this good enough for everyone? Let me know.

I really need the image, which ends up in my application's folders, to contain all the images metadata. The fact that a copy can be saved to the gallery doesn't serve the fact that the images our app work with lose every bit of metadata in their binary.
We should be able to extract those images from our app (upload, itunes (or other tool that allows to get the files)) and inspect them for their metadata (using preview or photos - on the mac as an example) and seeing that it is still there. That data needs to remain in the *.jpg or *.png If the data which is normally in the file is not in it at the end, the change does not solve my problem at all.
I understand that for metadata such as GeoLocation, apple does not add it to the image's metadata directly in the image binary for "security" reasons, I'm ok with it just exposed in whichever way and left up to us to be handled, but there really needs to be no loss of metadata in the binary file.

@jamesmontemagno thanks for fixing that but it turns the App I'm working on needs to really save an image to the App directory so I searched for other solutions and found this PR from XLabs. If you could incorporate this to your plugin, it would be awesome.
@LostBalloon1 see above, basically extracting metadata info and saving it to the MediaFile JpegInfo property from the source image before saving to app directory and just process the embedding somewhere else. You might need to tweak some things to accommodate your goals though.
Hope that helps. :)

I am closing this and re-opening as a new "bug" because there is a lot of confusion as to what needs to be done.


Update README to reflect simpler install instructions now that Postgres is unnecessary

The README still contains instructions for the pg gem, and doesn't include any information about the PLANET#_NUMBER environment variables.

@atbaker Fixed by removing ENV dependencies, just hard-coded the numbers. a329fe3


when i logIn and then close app and try to open it again , i logIn again .

can you provide current FireBaseAccount || User , or any idea to handle that .
thanks for you package.

You can use FirebaseAccount.restore for that


Using "Today" and "Tomorrow" Issue  #311

Hey,
We have added "Today" and "Tomorrow" in addition to the dates for the pickup group updates (history).
:)

I would suggest to use momentjs fromNow() for this https://momentjs.com/docs/#/displaying/fromnow/. And it already supports i18n. Why just today/tomorrow as special?
Also please keep codestyle the same - it should look like one person wrote it. You can run eslint locally as a standalone command or there are many editor plugins for it. It is your friend :)

@nicksellen I guess what we're wanting to do here is have "Today" and "Tomorrow", and have the rest of the days written as they are right now (i.e. fullDateFormat). That is why we simply used the condition.

Feedback:

Translation needs to be possible
Code location could be improved

Moment.js with built-in translations
I agree with Lars and Nick, the messages should be translatable before I would merge.
The easiest option would be using the great moment.js library. I did a bit of research and there seem to be two built-in options, which are not exactly fitting.
Calendar
moment(entry.date).calendar()

fromNow
moment(entry.date).fromNow()

You can also customize those, read more in the documentation of moment.js. Maybe you can find a nice option? :)
Code location
I would prefer to have the code in the history component controller (components/group/_history). We currently have almost no code in the backend-facing data services, so it would be unexpected to find it there. But would also listen for reasons why it should be otherwise :)

Personally I like the fromNow() or calendar() (without the time bit). I only ever understand dates when specified relative to now. My mum always uses proper dates but I have to translate them first "aaah you mean in a week from now..."

I think this is a good example of a task where it was too precisely specified. "Using today and tomorrow" is one way to implement something. The real task is something like "use human friendly relative dates" possibly with a justification too.
Never be afraid to widen the scope of a task if it seems appropriate.

You can remove the time bit from calendar by giving moment.js a custom format, but then you'd have to provide translations as well.
Maybe play with fromNow() and from() until it's good. I think we don't need to show a headline for today at all.

@devishi Do you know when you will have time to continue working on this?

Hi,
I am really sorry for delaying this. My exams were going on. I will start working on it again in a week's time.
Thanks

No worries, good luck for your exams!

I guess we can close this?

Yes, I agree. Feel free to continue if you have some time again @devishi - there will be a lot of changes in master you'll have rebase onto though.


issue : #9102 /Update search.html

Please describe the problem you're fixing here. Include the issue number, if applicable.

atul/issue : #9102

Superseded by #12118

can i know please , am i doing this right or wrong --  or i will do incomplete


opt in threaded flag for client.search

coverage: 96.819% (+0.3%) from 96.495%
when pulling 0646c246f1223ea4cacc8519163d004e1bc41294 on feature/threaded-search
into c54249beaf9a4a1d2c3028ed3f9e201ff6a46281 on main.


Update CONTRIBUTING.md to remove the references to Bitcoin Core and produce an actual contribution guideline document

Describe the issue
The document outlining contribution guidelines for this project appears to still contain significant references to the Bitcoin Core project it was forked from. This would probably need to be addressed and an actual document specific to the Dogecoin Project produced with input from all current contributors.

Fair point. I don't think anyone ever considered updating that document, but it's good documentation to have.
I'll put it on my TODO for later on, and hope someone beats me to it 😁

Fair point. I don't think anyone ever considered updating that document, but it's good documentation to have.
I'll put it on my TODO for later on, and hope someone beats me to it 😁

Great! I might give it a look too, but have uni exams for the next 3 weeks so may not be able to get to it before you. Would be good to give a general outline in terms of a style guide, who needs to approve a pull request, etc!

don't worry about that.
that file was edited in 1.14.4-dev

hi guys how can i help you ? i can work on italia translate if you need it

I've raised https://github.com/dogecoin/dogecoin/pull/2111 which includes some earlier work as well, hopefully that's a step in the right direction.


Add translations for QBO Sync job

Needs the following PRs:

https://github.com/Expensify/Integration-Server/pull/7884
https://github.com/Expensify/Web-Expensify/pull/41838

Details
More context: https://github.com/Expensify/App/issues/41018#issuecomment-2078490952
Add missing translations coming from the Sync QBO job
The stages names come from here:
https://github.com/Expensify/Integration-Server/blob/7ef13d7fc79a24863e4310e71e5ea348457508c3/src/expensify/progress/ProgressStepMessage.java#L49-L54
These are the same translations from Web-Expensify:
https://github.com/Expensify/Web-Expensify/blob/dd2b65fb6dd4fd0941fa5c462710aa6fc3d9cef6/site/app/global/pushNotificationsTemplates.js#L70-L77
Fixed Issues

$ https://github.com/Expensify/App/issues/41015
$ https://github.com/Expensify/App/issues/41129 (crash)
PROPOSAL:
Tests

Create user
Create Workspace
Go to "More Settings" in the workspace's Settings
Enable "Accounting"
Go to Accounting
Connection QBO
After the connection is done, click the 3 vertical dots in the QBO menu item
Click "Sync now"

Verify that:

A spinner appears while the sync is happening
The translation of the stages are not missing
The spinner goes away after the sync finishes

It should look like this:
https://github.com/Expensify/App/assets/87341702/910b963c-e5dc-4e5d-9ba0-2a962212cd5e

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps
N/A

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

This looks like it just adds translations. Does this need a C+ review?

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

I said this in Slack, but I think we should get rid of the switch statement, create individual keys and use translateIfPhraseKey instead. Not gonna block this PR since the switch statement is already there.

I said this in Slack, but I think we should get rid of the switch statement, create individual keys and use translateIfPhraseKey instead. Not gonna block this PR since the switch statement is already there.

Follow up issue here: https://github.com/Expensify/App/issues/41248

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.67-7 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to staging by https://github.com/luacmartins in version: 1.4.68-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.67-7 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.68-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


RevisionMissing & kf-resource-quota Issue When Running Kfserving Sklearn Example

/kind bug
I installed KFserving together with Kubeflow on my k8s cluster, but when I tried to run the Sklearn example provided here: https://github.com/kubeflow/kfserving/:

Then I checked the resources under the namespace -- it was unsuccessful, and the STATUS i noticed is Revision Missing
NAME                                                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                             AGE
service/sklearn-iris-predictor-default-7tjcg           ClusterIP   <IP_ADDRESS>   <none>        80/TCP                              4m32s
service/sklearn-iris-predictor-default-7tjcg-private   ClusterIP   <IP_ADDRESS>   <none>        80/TCP,9090/TCP,9091/TCP,8022/TCP   4m32s

NAME                                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/sklearn-iris-predictor-default-7tjcg-deployment   0/1     0            0           4m32s

NAME                                                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   1         0         0       4m32s

NAME                                                               LATESTCREATED                          LATESTREADY   READY     REASON
configuration.serving.knative.dev/sklearn-iris-predictor-default   sklearn-iris-predictor-default-7tjcg                 Unknown

NAME                                                                CONFIG NAME                      K8S SERVICE NAME                       GENERATION   READY     REASON
revision.serving.knative.dev/sklearn-iris-predictor-default-7tjcg   sklearn-iris-predictor-default   sklearn-iris-predictor-default-7tjcg   1            Unknown   Deploying

NAME                                                       URL                                                                READY     REASON
route.serving.knative.dev/sklearn-iris-predictor-default   http://sklearn-iris-predictor-default.kfserving-test.example.com   Unknown   RevisionMissing

NAME                                                         URL                                                                LATESTCREATED                          LATESTREADY   READY     REASON
service.serving.knative.dev/sklearn-iris-predictor-default   http://sklearn-iris-predictor-default.kfserving-test.example.com   sklearn-iris-predictor-default-7tjcg                 Unknown   RevisionMissing

Also in the event: kubectl get event -n kfserving-test I saw error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c4598k2x" is forbidden: failed quota: kf-resource-quota: must specify memory
LAST SEEN   TYPE      REASON              OBJECT                                                                  MESSAGE
6m23s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c4598k2x" is forbidden: failed quota: kf-resource-quota: must specify memory
6m23s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45mdgks" is forbidden: failed quota: kf-resource-quota: must specify memory
6m23s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45xvlkq" is forbidden: failed quota: kf-resource-quota: must specify memory
6m23s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45rq2m4" is forbidden: failed quota: kf-resource-quota: must specify memory
6m22s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45845f8" is forbidden: failed quota: kf-resource-quota: must specify memory
6m22s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45n4wcc" is forbidden: failed quota: kf-resource-quota: must specify memory
6m22s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c452jvl8" is forbidden: failed quota: kf-resource-quota: must specify memory
6m22s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45xj4xj" is forbidden: failed quota: kf-resource-quota: must specify memory
6m21s       Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45grhdr" is forbidden: failed quota: kf-resource-quota: must specify memory
52s         Warning   FailedCreate        replicaset/sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45   (combined from similar events): Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c4544wbm" is forbidden: failed quota: kf-resource-quota: must specify memory
6m23s       Normal    ScalingReplicaSet   deployment/sklearn-iris-predictor-default-7tjcg-deployment              Scaled up replica set sklearn-iris-predictor-default-7tjcg-deployment-6495b57c45 to 1
6m37s       Warning   InternalError       serverlessservice/sklearn-iris-predictor-default-7tjcg                  failed to get private K8s Service endpoints: endpoints "sklearn-iris-predictor-default-7tjcg-private" not found
6m37s       Warning   InternalError       revision/sklearn-iris-predictor-default-7tjcg                           failed to update deployment "sklearn-iris-predictor-default-7tjcg-deployment": Operation cannot be fulfilled on deployments.apps "sklearn-iris-predictor-default-7tjcg-deployment": the object has been modified; please apply your changes to the latest version and try again
6m38s       Normal    Created             service/sklearn-iris-predictor-default                                  Created Configuration "sklearn-iris-predictor-default"
6m38s       Normal    Created             configuration/sklearn-iris-predictor-default                            Created Revision "sklearn-iris-predictor-default-7tjcg"
6m38s       Normal    Created             service/sklearn-iris-predictor-default                                  Created Route "sklearn-iris-predictor-default"
6m38s       Normal    FinalizerUpdate     route/sklearn-iris-predictor-default                                    Updated "sklearn-iris-predictor-default" finalizers
5m43s       Normal    Updated             inferenceservice/sklearn-iris                                           Updated InferenceService "sklearn-iris"
5m44s       Warning   InternalError       inferenceservice/sklearn-iris                                           Operation cannot be fulfilled on services.serving.knative.dev "sklearn-iris-predictor-default": the object has been modified; please apply your changes to the latest version and try again

I've also checked the Revision Missing section in the following guide still but no idea, I doubt it's related to Error creating: pods "sklearn-iris-predictor-default-7tjcg-deployment-6495b57c4598k2x" is forbidden: failed quota: kf-resource-quota: must specify memory
https://github.com/kubeflow/kfserving/blob/master/docs/KFSERVING_DEBUG_GUIDE.md

Istio Version: 1.6.13

Knative Version:

Kubeflow version:1.2.0

Kubernetes version: (use kubectl version): client:1.19.4, server:1.17

OS (e.g. from /etc/os-release): macOS Catalina

I got the same issue as above. I actually set resource limits and requests on my inferenceservice yaml file and same results. When I check the yaml output of the deployment, the first container as request and limits but the queue-proxy container only has a request for cpu. Obviously this has to be changed to have limits and requests for this container if you are working with quotas in your namespace.

@HassanOuda @snowneji  the queue proxy resource should be configurable https://github.com/knative/serving/blob/master/config/core/configmaps/deployment.yaml#L51-L75, can you help add this to the install guide for users enabling resource quota?

Queue proxy is configurable with Knative 0.16+, by default cpu and memory are enforced.


Restructure docs

Fixes #184, #125, #203.

splits documentation into General, Node operators, Developers and Core components. Now the docs URLs are not repository-based anymore (e.g. docs of oasis-sdk git module are now part of Developers component). Redirects are added for backward-compatibility.
moves aforementioned links to components to the top bar. Support and website links were moved to the top-right corner icon and the footer respectively,
adds guidelines for writing Oasis docs (docs structure, cross-referencing, using doccards etc.)
adds remark plugin which converts github.com documentation links from various Oasis repos to relative docs links,
implements correct Edit page link across all components and repositories,
moves Mainnet and Testnet categories from general to operators and Prerequisites, Maintenance, Advanced sections to set-up-your-node category
reduces the amount of sidebar entries by merging Overview chapters with category entry; removes any README.md containing just a table of contents with generated-index doc page type; renames overview.mdx files to README.mdx for consistency
flattens FAQ category which just had a single entry

Nice!
Probably "Oasis Core" should go under "Developers" instead of being its own tab?

On the Developers -> Oasis SDK page it seems that the "Oasis Core Runtime Layer" link points to GitHub.

I was thinking of solving those in a separate PR https://github.com/oasisprotocol/docs/issues/203.

On the Developers -> Oasis SDK page it seems that the "Oasis Core Runtime Layer" link points to GitHub.

Now implemented as part of this PR.

Because restructuring the docs is a big deal we should not rush it. In general I like the new structure, but I still have a few suggestions.

Mainnet Network Parameters and Mainnet Upgrade Logs should probably go into a Mainnet category under Node Operators
Testnet Network Parameters and Testnet Upgrade Logs should probably go into a Testnet category under Node Operators
Developers / Oasis SDK / Smart Contracts should probably be named Cipher ParaTime (similar to Emerald and Sapphire) and contain the API reference
Developers / Oasis SDK / Runtimes should probably have a more informative/call-to-action name, like Your Custom ParaTime or Roll your own ParaTime
I suspect we have three different groups of developers: contracts, runtimes, and core (last two could be merged?). Maybe we should rename "Developers" to "Contract Developers" and "Core" into "Core Developers"  (and also include Oasis SDK / Runtimes here).

Developers / Oasis SDK / Smart Contracts should probably be named Cipher ParaTime (similar to Emerald and Sapphire) and contain the API reference

On the other hand this seems weird as the Contract SDK documentation is general for any paratime using the contracts module.

In case we want to make this Cipher-specific we should probably move these contract docs outside the SDK repository? But then we are left without general contract SDK docs not specific to any paratime deployment?

I suspect we have three different groups of developers: contracts, runtimes, and core (last two could be merged?). Maybe we should rename "Developers" to "Contract Developers" and "Core" into "Core Developers" (and also include Oasis SDK / Runtimes here).

Agree that the SDK docs should probably be separate, especially if we move out the "Cipher ParaTime" docs? So the SDK contains a bunch of things (as mentioned in the docs):

Runtime SDK (for building runtimes)
Client SDK (for building clients that talk to runtimes)
WASM Contracts SDK (for building smart contracts using the WASM contrats module)

Note that all of these are general and unrelated to any specific runtime/paratime deployment.
But saying "Core Developers" and "Contract Developers" is way too long. In my mind the categories are something like:

contracts (evm / confidential evm / wasm),
SDK and
Core.

So maybe we should move the general WASM contracts section (and related API reference links) out under Contracts -> Cipher if this is possible to do.

Also one thing that is strange is the "Network Primer" (the "Why Oasis" and "ROSE Token Metrics" links lead there) as it seems like it is a completely separate thing instead of being a section in the main docs. I think it should be merged into the main docs now that we have reduced clutter there.

Mainnet Network Parameters and Mainnet Upgrade Logs should probably go into a Mainnet category under Node Operators
Testnet Network Parameters and Testnet Upgrade Logs should probably go into a Testnet category under Node Operators

Yeah this is probably right.

Note that all of these are general and unrelated to any specific runtime/paratime deployment.
In my mind the categories are something like:
* contracts (evm / confidential evm / wasm),
* SDK and
* Core.

Makes sense. Initially it has been bugging me that we promote ParaTimes, but then the docs aren't organized around them. But I am beginning to think that it makes a lot of sense to keep node operator and all developer docs paratime-agnostic and focused on the technological/functional aspects.
Lets imagine the following user story: I heard about the confidentiality features (replace with any other feature) of Sapphire (replace with other ParaTime). As a developer I want to develop a smart contract on Sapphire. Where do I start?
Because we promote ParaTimes, the solution would be if each ParaTime has a dedicated category under "General". It should clearly describe what it is (from contribute-to-the-network/run-a-paratime-node) and which technologies are being used with links to relevant developer docs.

The mainnet and testnet categories are now moved under operators/. I also moved prerequisites, maintenance-guides and advanced under set-up-your-node to reduce top-level clutter. Please check.

Looks like the "Network Parameters" are still in the General sidebar and clicking on it switches to the Node Operators tab.

Looks like the "Network Parameters" are still in the General sidebar and clicking on it switches to the Node Operators tab.

FYI this is deliberate so you can access current network parameters with a single click.

Why would someone that is not a node operator need to access network parameters?

Why would someone that is not a node operator need to access network parameters?

Fair point. :thinking: I was considering metamask wallet users, but URLs for emerald/sapphire endpoints are now in the Developers component and it takes the same amount of clicks to come there via network parameters page. I agree, let's remove the Network parameters sidebar entry.

I was considering metamask wallet users, but URLs for emerald/sapphire endpoints are now in the Developers component

Because Metamask wallet users are not developers, I would suggest that every ParaTime has a dedicated page in the "General" component and the Contract/SDK/Core developer components focus on the technologies (mentioned in https://github.com/oasisprotocol/docs/pull/200#issuecomment-1225840574).

My suggestions for node operators:

We create a subcategory Run a node on the Prerequisites level and put in this category Validator node, Non-Validator node, Seed node, etc. I think Run a ... is too repetitive.
Rename Sentry Node Architecture to Sentry Node and move it to Run a node category.
Move Amend Commission Schedule to Maintenance
Rename Mainnet and Testnet to Mainnet Parameters and Testnet Parameters
I think Create an Entity Package is deprecated.

I suspect we have three different groups of developers: contracts, runtimes, and core (last two could be merged?). Maybe we should rename "Developers" to "Contract Developers" and "Core" into "Core Developers" (and also include Oasis SDK / Runtimes here).

Agree that the SDK docs should probably be separate, especially if we move out the "Cipher ParaTime" docs? So the SDK contains a bunch of things (as mentioned in the docs):
* Runtime SDK (for building runtimes)

* Client SDK (for building clients that talk to runtimes)

* WASM Contracts SDK (for building smart contracts using the WASM contrats module)

Note that all of these are general and unrelated to any specific runtime/paratime deployment.
But saying "Core Developers" and "Contract Developers" is way too long. In my mind the categories are something like:
* contracts (evm / confidential evm / wasm),

* SDK and

* Core.

So maybe we should move the general WASM contracts section (and related API reference links) out under Contracts -> Cipher if this is possible to do.

I thought a bit about this and refactored the Developers component now. Please check: https://deploy-preview-200--trusting-archimedes-14c863.netlify.app/developers/

There seems to be some missing spacing:

Otherwise the new "Developers -> Ciper ParaTime" section is better and we can improve the SDK even more. The "Developers -> Oasis SDK -> Client" section seems a bit empty for now, probably we should move it to the bottom (as it doesn't provide anything beyond a link to the reference) instead of being at the top?

Thanks for this great work @matevz!
My main comment before we merge this restructuring would be around the naming and structuring of different sub-documentations.
Current variant:

General
Node Operators
Developers
Core
sounds inconsistent and a bit boring to me.

I'm thinking how we can make it more attractive and sort of "calling to action".
One idea would be:

Use Oasis (I don't know what URL to suggest. Ideas?)

I would move/duplicate the user-relevant part of how to use Emerald and Cipher on Mainnet here.

Run Node (or Operate Node) (URL: /node)
Create dApp (URL: /dapp)

I would change the structure to list the 3 ParaTimes with subsections on how to develop dApps for them.

Build ParaTime (URL: /paratime)

Things currently under Oasis SDK -> Runtimes

Develop Core (URL: /core or /oasis-core. Preferences?)

We could add this as well:

Join Community (or Contribute) (URL: /community or /contribute) that would include:

Some general info about our community and how to get in touch. similar to https://docs.avax.network/community.
Things we currently have under General -> Contribute to the Network.

I think this looks very good.
I would try to improve/augment the "Join Community" and generalize it to "Get Involved" with sections:
"Join our Community" -> page with links to our communities
"Become our Ambassador" -> external link to https://oasisprotocol.org/ambassador-program
"Become our Influencer" -> external link to: https://oasisprotocol.org/influencer
"Apply for Grant" -> https://oasisprotocol.org/grant-programs
"Join our University Program" -> https://oasisprotocol.org/university-program
"Run a Node" with subsections:

"Consensus Validator Node"
"ParaTime Node"

"Develop Oasis Core" (rename current "Contributing Guidelines")
"Network Governance"
"Delegation Policy"
"Token Delivery & KYC Guide"


groovebasin package

This is a package of Groove Basin - a music player server with a built in web interface.
The Nixpkgs Contributors Guide does not mention Node.js, so I followed the examples set by tessel and keybase.
package.nix is generated with npm2nix.

I used the postInstall step to do the build.

I don't understand this travis CI build error, does anyone else?

@andrewrk i kicked travis to rerun. lets see. otherwise the only comment i have is if you can add yourself as a maintainer.

weird ... looks like travis has hard to to apply this PR and get conflicts. let me build it locally

merged here


Formatting and fixes

These changes include code formatting, and a number of bugfixes.

Thank you for reviewing and approving the changes, I applied the suggested changes, and moved bugfix, API, and a subset of the refactoring commits, to other pull requests.

I went through the files that were changed since my review and I think this is ready to merge. @johnyf I'll let you choose between a merge, a rebase, or a squash.

Thank you for reviewing and approving the changes, I rebased and merged this pull request (moved the .gitattributes file to a branch).


Bold Breaking

When using the "literalMidWordAsterisks" option, there are a few circumstances which you would want bold to maintain, but it is instead keeping the literal asterisk.
**Bold:** vs **Bold**:
Will appear as Bold: vs **Bold**: while a , or . after the ** will properly display as un-bolded when the word is bold. Is there a way to make non-alphanumeric characters eligible to not break bolding?
Additionally, this option breaks bolding when creating a sub-list.
- **Bold**
    - Tier 2

Will display with the asteriks unless you add a space after it, which it will then display as formatted text.
All of the above previewed on v1.8.2 Showdown Editor

Should be fixed now.

As you know, ShowdownJS is a free library and it will remain free forever. However, maintaining and improving the library costs time and money. Currently, we're looking to improve showdown with automated tests in all browsers and a proper domain and webpage. 500$ should be enough to to keep showdown testing framework running for a year or two.

If you like our work and find our library useful, please donate through Pledgie or directly through paypal!! Your contribution will be greatly appreciated.

Thanks for the quick fix! Confirmed it is working now.


intellisense not work

Environment data
SDK de .NET Core (reflejando cualquier global.json):
Version:   2.1.301
Commit:    59524873d6
Entorno de tiempo de ejecución:
OS Name:     Windows
OS Version:  10.0.17134
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.301\
Host (useful for support):
Version: 2.1.1
Commit:  6985b9f684
VS Code version:
1.25.0
C# Extension version:
1.15.2
the intellisense not work in code web api
when i try to restar onmisharp see "command 'o.restart' not found"

@allnnde  Could you share your OmniSharp log ?( View --> Output --> OmniSharp Log)

i'm not have any log for Omnisharp

@allnnde Can you share your C# extension log?

i'm having the same issue.
No output for c# or omnisharp.
I opened the developer tools and found this:
[Extension Host] Activating extension 'ms-vscode.csharp' failed: Cannot find module 'rxjs/Subscription'.

@juwens Can you share your environment data (similar to @allnnde )

@rchande
`
PS C:\WINDOWS\system32> node --version
v10.4.1
PS C:\WINDOWS\system32> npm --version
5.6.0
PS C:> dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   2.1.300
Commit:    adab45bf0c
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.16299
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.300\
Host (useful for support):
Version: 2.1.0
Commit:  caa7b7e2ba
.NET Core SDKs installed:
2.0.0 [C:\Program Files\dotnet\sdk]
2.1.4 [C:\Program Files\dotnet\sdk]
2.1.100 [C:\Program Files\dotnet\sdk]
2.1.101 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.300 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
`

@rchande i tried that previously without success
But i found the source of the problem on my computer.
Apparently my (installed) npm 5.6.0 is not compatible with node 10.4.1.
So i updated it to 6.1.0.
Now omnisharp and intellisense work fine again.
PS C:\Users\juwens> npm install -g npm
npm WARN npm npm does not support Node.js v10.4.1
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

C:\Users\juwens\AppData\Roaming\npm\npm -> C:\Users\juwens\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
C:\Users\juwens\AppData\Roaming\npm\npx -> C:\Users\juwens\AppData\Roaming\npm\node_modules\npm\bin\npx-cli.js
+<EMAIL_ADDRESS>added 247 packages, removed 41 packages and updated 129 packages in 31.402s

@rchande As I said before, I do not have any log, sorry for my english

@allnnde
please try the following:
Help > Toggle Developer Tools
In Developer Tools go to Console an look for errors.

@juwens Interesting. npm isn't a requirement to use VS Code, but I guess it must try to use your local copy if you have one installed?

@juwens

I deleted in %userprofile% the folders .onmishap and .vscode\extensions\ms-vscode.csharp-1.15.2 and reinstall and now it is working ok

@allnnde Thanks for following up--glad you got it working!

Thanks @allnnde  your workround was wonderful  .  I found two folders vscode\extensions\ms-vscode.csharp-1.16.2 and vscode\extensions\ms-vscode.csharp-1.16.1 .
Uninstalled extension closed vs code , deleted these two folders and reinstalled .
Everything worked .
Even the intellisence which was not working started working.


libwacom: 0.32 -> 0.33

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libwacom/versions.
meta.description for libwacom is: '"Libraries, configuration, and diagnostic tools for Wacom tablets running under Linux"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.33 with grep in /nix/store/1aaranig4ys8hj3hr60l3dpzbw76mzdi-libwacom-0.33
directory tree listing: https://gist.github.com/8822c305e303a20c27538d8ff6f0578f
du listing: https://gist.github.com/845792fe8da6202a71eb54f888a1b608

Rebuild report (if merged into master) (click to expand)

4172 total rebuild path(s)
1455 package rebuild(s)
1455 x86_64-linux rebuild(s)
1379 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1338 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
adapta-gtk-theme
adwaita-qt
aj-snapshot
akonadi
akregator
albert
altcoins.bitcoin
altcoins.bitcoin-abc
altcoins.bitcoin-classic
amarok
amarok-kf5
android-file-transfer
anki
antimicro
antimony
ao
apitrace
apmplanner2
appstream-qt
aqemu
arc-theme
ark
arx-libertatis
audaciousQt5
avidemux
awesomebump
barrier
beets
bino3d
bitcoin
bitcoinarmory
blink
bluedevil
bomi
boomerang
breeze-gtk
breeze-icons
breeze-qt5
cadence
calamares
calaos_installer
calibre
candle
caneda
cantata
casperjs
cb2bib
chessx
chrome-gnome-shell
chrome-token-signing

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1aaranig4ys8hj3hr60l3dpzbw76mzdi-libwacom-0.33 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A libwacom https://github.com/r-ryantm/nixpkgs/archive/ed54e88a8998fd8221405eef8897a9abd4248e0c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1aaranig4ys8hj3hr60l3dpzbw76mzdi-libwacom-0.33
ls -la /nix/store/1aaranig4ys8hj3hr60l3dpzbw76mzdi-libwacom-0.33/bin

@GrahamcOfBorg eval


Improving loading and first execution times

I am opening this issue in response to a discussion we had on Slack regarding loading and execution times in Turing. Although there have been improvements in absolute loading time in newer versions of Julia, Turing remains about 2-3 times slower than Plots.
Loading Times
Julia 1.5.3
@time using Plots
  6.639685 seconds (12.61 M allocations: 797.037 MiB, 4.42% gc time)

@time using Turing
 16.071072 seconds (40.04 M allocations: 2.060 GiB, 4.11% gc time)

The absolute load times are better on nightly, but Turing is still relatively slow.
Nightly
@time using Plots
  2.841848 seconds (5.80 M allocations: 429.191 MiB, 5.07% gc time, 25.36% compilation time)

  @time using Turing
  9.306305 seconds (16.28 M allocations: 988.606 MiB, 3.80% gc time, 54.65% compilation time)

First Execution Time
Here are typical first execution times for the coinflip model described in the documentation.
Julia 1.5.3
@time chain = sample(coinflip(data), HMC(ϵ, τ), iterations; progress=false)
 10.453679 seconds (42.26 M allocations: 1.876 GiB, 5.53% gc time)
Chains MCMC chain (1000×10×1 Array{Float64,3}):

Nightly
@time chain = sample(coinflip(data), HMC(ϵ, τ), iterations; progress=false)
 18.583285 seconds (74.80 M allocations: 4.053 GiB, 6.13% gc time, 93.57% compilation time)

Nearly all of the first execution time is attributable to compilation. It should be noted that the improvement in loading time on nightly is offset by the increased first execution time.  There is also a lag of about 6-7 seconds for printing the first chain, but this seems to have improved quite a bit in recent versions.
Reducing  these times would be greatly appreciated, even if it is only by 2-3 seconds.
Versions
(@v1.5) pkg> st Turing Plots
Status `~/.julia/environments/v1.5/Project.toml`
  [91a5bcdd] Plots v1.9.1
  [fce5fe82] Turing v0.15.7

I agree, this should definitely be improved. However, it's a bit difficult to comment without any more detailed benchmarks and without knowing what parts cause these excessive compilation times. I assume a large part is caused by DistributionsAD and its hacks and type piracy, it would be interesting to see if it causes invalidations (maybe also some other parts cause them?). Can you check the compilation and loading times of DistributionsAD?
IIRC in the Slack discussion it was mentioned that dropping DynamicHMC and a more lightweight MLE/MAP implementation would allow to drop Requires. That is actually not true since it is used as well to optionally load AD support for Zygote and ReverseDiff. The optimization algorithm is supposed to be changed from Optim to GalacticOptim to make it more generally applicable but I am not sure how much this will help - we will have to depend at least on DiffEqBase which also depends on quite many packages (there is an issue in DiffEqBase to fix this and/or extract some parts to a more lightweight package: https://github.com/SciML/DiffEqBase.jl/issues/618). And even if Requires could be removed from Turing, other packages such as DistributionsAD still make heavy use of it...
Regardless of the loading times, maybe it would be good to move some additional parts (such as DynamicHMC integration) to separate packages to make the setup more modular.

Hi devmotion-
Here are the requested load times for DistributionsAD:
Julia 1.5.3
@time using DistributionsAD
2.845870 seconds (5.87 M allocations: 326.353 MiB, 1.62% gc time)
Nightly:
  @time using DistributionsAD
  2.632951 seconds (5.31 M allocations: 325.930 MiB, 2.58% gc time, 66.49% compilation time)

The improvement for nightly is small. I am not sure if that is expected. Let me know if there is any more info I can provide. Thanks for looking into this.

Thanks!
I think it would be even more realistic to check how much time it takes to load DistributionsAD + Tracker (+ ForwardDiff) since Turing loads both AD backends but DistributionsAD only depends on ForwardDiff and puts Tracker support in a @requires block. IIRC Requires mostly affects loading times if the optional dependency is loaded.

Is this what you are looking for?
Julia 1.5.3
@time using DistributionsAD, Tracker, ForwardDiff
  9.621758 seconds (22.21 M allocations: 1.217 GiB, 3.77% gc time)

Nightly
@time using DistributionsAD, ForwardDiff, Tracker
  6.568642 seconds (14.62 M allocations: 916.992 MiB, 5.09% gc time, 59.66% compilation time)

Yes, so it seems most time is spent with loading and compiling DistributionsAD and the AD backends which can't be fixed in Turing itself.
I had a quick look at how to analyze method invalidations but I am not sure how to interpret and fix the results yet. On Julia nightly I ran
julia> ] add SnoopCompileCore SnoopCompile Tracker ForwardDiff DistributionsAD#master

julia> using SnoopCompileCore

julia> invalidations = @snoopr begin
           using DistributionsAD, ForwardDiff, Tracker
       end
1701-element Vector{Any}:
...

julia> using SnoopCompile

julia> length(uinvalidated(invalidations))
510

julia> trees = invalidation_trees(invalidations)
17-element Vector{SnoopCompile.MethodInvalidations}:
...

I.e., as far as I can see loading DistributionsAD, ForwardDiff, and Tracker causes 510 method invalidations. I'll try to debug this more closely. BTW unfortunately it was not possible to perform the same analysis with Turing since Libtask_jll does not support Julia >= 1.6.

Tim Holy's tutorial on precompilation might be helpful. In case it is, you can find it here.

Tim Holy's tutorial on precompilation might be helpful. In case it is, you can find it here.


Provide way to define section/group header type and classes

Currently, section/group headers are hard coded to start with
. However, my homepage layout requires these headers to be
 or less to fit into the hierarchy.
Is it possible to provide a way to specify the header type as well as extra header styles?
It seems that these headers are actually the only (?) part of the framework, that cannot be specified by a html style.
Maybe instead of/in addition to specifying a div for every section, the header can be directly specified in the bibtex_structure?

->

Refereed Articles

It seems that you are able to get a header hierarchy of sections and groups, no idea how this would work with my suggestion above though.

Yes, I completely agree that it should be provided in the bibtex_structure.
Fixed in commits: bf15038f740da194b16c090f5b1ae1feb72808cb and e88bdee59ff0ef099eb691ebc3f2e24f26e12909
I've updated the wiki pages to reflect the changes so it should all be up to date.

Custom group headers
Academic Style

Note: there were some major changes to the academic style in order to have custom headers so you will have to change some html. For html code for the cost of flexibility.

Thanks a lot, u r awesome :+1:


Draft: bug fixing

Support writing and parsing "filesAnalyzed" into XML/JSON/YAML.
Fix parsers to support multiple packages per document.
All the tests are passing.

hi @yanyag can you please rebase this PR?
now that the six removal PR is merged, there are a few conflicts.

hi @yanyag  @itraviv ,
Please remember you still have this PR open that needs rebasing. It still contains merge conflicts.
Now the PR contains more fixes than initially pushed, and it becoming less trivial.
I think it will need more unit tests, with 2.2 file examples which proves that your code is actually working.

Gentle ping :)

hi, we will probably need some time until we'll be able to have this MR ready due to capacity. will ping when ready.

gentle ping :) Any update?

As this PR is still in draft mode and has not been receiving vital updates for over a year, I suggest closing it.
@yanyag, any objections?

Closing this due to inactivity, please ping if it should be reopened.