Introduction - Introductory Assignments

[x] bit
[x] nibble
[x] byte
[x] binary numbers
[x] decimal
[x] unary
[x] octal
[x] hexadecimal
[x] How many bits in 6 GB
[x] Computation
[x] Software

I started writing descriptions, examples, and exercises.
It is intended as an example of self-contained content.
I hope this meets the expectations? @ckirsch

Looks very nice! Don't forget to spell check.
First and foremost, as far as the computer is concerned, there is no way to move "past numbers" because, to the computer, everything is a number. A computer stores everything as a series of 0's and 1's. This representation is called a bit. A bit can only have one of two values, which are most commonly represented as either a 0 or 1. The value 1 means high voltage, and the value 0 means low voltage in computer systems.
->
First and foremost, as far as computers are concerned, everything is a number, in fact a binary number. A computer stores everything as a series of 0's and 1's. This representation is called a bit. A bit can only have one of two values, which are most commonly represented as a 0 and a 1. In actual electronic hardware, value 1 is typically represented by high voltage, and value 0 by low voltage.

Thank you very much for the feedback, I will include it immediately. I will pay more attention to the spellchecker.

Should we make a separate file for each topic?
Or should everything be in one file?

Hey, @Blazefrost  could you take a look at the file to see if you see any room for improvement?

@ckirsch Should we make a separate file for each topic?
Or should everything be in one file?

everything in one file please. selfie style :)

@ckirsch I finished version 1 of Introductory Assignments.
It would only be important to check that everything is correct.
Maybe @Blazefrost can also take a look at it?

Looks very nice. Let's talk later today during the group meeting.

I've read through the document and I think it looks very nice :+1:
I've got some very minor nitpicks, though:

In the chapter "State Space" or "Byte", we could add the smallest/largest (positive) number that a byte can represent. This might even be a good exercise!
In the subchapter "Decimal to Binary" we could clarify that we divide with the floored result of the previous division.
You've mentioned ASCII twice without specifying it further. Can we assume that people will be familiar with it in the introduction?

What are your thoughts on these points?

@Blazefrost Sounds all good. Please go ahead and add your suggestions to the grader branch. Ad ASCII: mention the notion of an ASCII table that maps characters to 7-bit binary numbers.

@Blazefrost Sounds all good. Please go ahead and add your suggestions to the grader branch. Ad ASCII: mention the notion of an ASCII table that maps characters to 7-bit binary numbers.

@Blazefrost  I found an ASCII table written in Markdown, we could add it to the first topic. It takes up a lot of space since we have over 127 lines.

@ckirsch Done!
@aemonk Maybe we could add it as a separate markdown file and link to that, if the usage terms of the Markdown table allow for that. This way everything relevant is in the repo but the assignment markdown will still be lean.

@Blazefrost added the ASCII-table as a separate file and linked it into the introductory-assignments file.


Translate typechecking-with-proptypes

Not sure about certain words.... Anyway....

This should be good. Thank you for the good work mas @rizafahmi


Update problem_instance.schema.0.0.1.json required fields to refer to…

… "tasks" instead of "instance_data"

I'm not sure if the automatic schema validation script is currently working.  I think I need to update something on that.  But watch out for that script anyway when these changes go in.


Modified function ReverseWords.py

Modified function ReverseWords.py

@hkbagh you can do issue #17

Ok I am doing #17


CLI implementation

Added CLI capability to 'examples/train_model.py' using argparse.
The wandbLogger class call was moved into main to use its save location as part of the CLI implementation.

adding @asogaard @RasmusOrsoe fyi. For some reason I cannot add a reviewer in the github webpage interface.

Temporally closed, pending further implementation


Question. Background Color, color doesn't seem to be available, can the Color Index be used?

HI All
I've been working with someone to create an excel file for a monthly report.  When it was first created it was created using the old Com objects and needed to be run manually.  We are trying to update the script to use Export-Excel to create the report and ran into a minor issue that I"m stuck on.
The problem is related to the background colors.  I have found how to use the Conditional Text setting and I'm able to get some colors working, but others don't seem to work.  An example is trying to use "light orange" as the background color.  Light Orange doesn't seem to be available but i found that  Dark Orange and Orange work.
Since i know the Color Index numbers, is there a way to use those instead of using the name? Or maybe the RGB number? Is there a different way I can set the background color that I have overlooked?
if you look at the link below, I know i need color 40 and 45 but just can't seem to find a matching color with conditional formatting.
https://www.pk-anexcelexpert.com/wp-content/uploads/VBATutorial/VBA-36.jpg
any suggestions and assistance is greatly appreciated.
Thanks
Greg

Try FromArgb
$xlfile = "$env:TEMP\test.xlsx"
rm $xlfile -ErrorAction SilentlyContinue

$data = ConvertFrom-Csv @"
Region,Item,TotalSold
South,saw,100
West,screws,100
West,peach,98
South,pear,26
West,hammer,75
East,melon,74
North,kiwi,48
East,orange,26
South,peach,48
West,banana,48
"@

$ct = New-ConditionalText -Text South -BackgroundColor ([System.Drawing.Color]::FromArgb(217,217,217)) -ForeGroundColor Green

Export-Excel -InputObject $data -Path $xlfile -Show -ConditionalText $ct

That works exactly like i need it too.  Thanks for the help and quick response.
Greg


build: update spdkrs, dependencies, nixpkgs, cargo

A lot of code changes, related to clippy more strict rules.

bors try

bors try

bors try

bors try

bors merge

bors merge


ENH adding python 2.7

Hi! This is the friendly automated conda-forge-webservice.
I've added python 2.7 as instructed in #3.
Merge this PR to enable Python 2.7.
WARNING: Python 2.7 reached end-of-life on 2020-01-01. conda-forge provides no support for Python 2.7 builds and all existing builds are provided on an "as-is" basis. Python 2.7 builds on the win platform are not possible since we do not build against vs2008 in our CI providers.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


sync docusaurus plugin versions

Yesterday I merged https://github.com/badges/shields/pull/9600
When I was working on shields today, I realised that docusaurus was outputting
[ERROR] Invalid docusaurus-plugin-content-docs version 2.4.1.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (2.4.3).
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?
[ERROR] Invalid docusaurus-plugin-content-blog version 2.4.1.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (2.4.3).
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?
[ERROR] Invalid docusaurus-plugin-content-pages version 2.4.1.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (2.4.3).
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?
[ERROR] Invalid docusaurus-plugin-sitemap version 2.4.1.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (2.4.3).
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?
[ERROR] Invalid docusaurus-theme-classic version 2.4.1.
All official @docusaurus/* packages should have the exact same version as @docusaurus/core (2.4.3).
Maybe you want to check, or regenerate your yarn.lock or package-lock.json file?

This didn't cause anything to fail in CI - it just logged the errors to the console, which is why I didn't notice it.
The place where this is checked is https://github.com/facebook/docusaurus/blob/v2.4.3/packages/docusaurus/src/server/siteMetadata.ts#L75-L92
There doesn't appear to be any command or switch that can make this a hard error but I would really like this mismatch to cause a CI fail so I don't forget this next time. I am going to raise an issue about this upstream, but in the meantime I have cobbled together a crude bash script we can use. It is not very efficient because we have to build the whole frontend, but it is better than a kick in the teeth.
If you follow the commit history, you can see the build fails on the commit where I've added the check and then passes on the commit where I have fixed it.
FWIW, this particular mismatch (2.4.1 / 2.4.3) doesn't appear to actually be causing any issues, but I'd like to get this one reviewed/merged sooner rather than later.

raised https://github.com/facebook/docusaurus/issues/9342 - we'll see where it goes..

Thanks for finding, explaining, and fixing. It's the type of thing that would've had me in a helpless :shrug: had I seen myself


mac: automate installing apps from terminal

with brew you can install mas-> https://github.com/mas-cli/mas
this command allow you to install applications from the app store

This is pretty cool, I wasn't aware of it, thanks!

Resolved with fa639ae87da9bec0bf7c2a194f587269166bf258


build system

Implement a build system based on gradle.  This system should be capable of:

building the Docker image
starting a Docker container with test-only Cloudant credentials
running automated tests against that running container

@jasonpet has offered to look into scaffolding a generic build solution for all docker-based service providers.


[Constraint solver] Gather constraints from adjacencies of equiv class.

When gathering constraints for a type variable, we were gathering all of
the constraints for the members of the equivalence class, and then for
the adjacencies of the representative of the equivalence class, but not
from the adjacencies of other members of the equivalence class.
For example for:
#3 = $T3
#4 = $T4 equivalent to $T3
#5 = $T5 as $T4.Element
after binding $T3 we would collect the constraints related to $T3 and
$T4, but not $T5. The end result can be that we finish examining all
disjunctions and type bindings but still have inactive constraints in
the constraint graph, which is treated as a failure in the solver.
Fixes SR-5120 / rdar://problem/32618740.
(cherry picked from commit 687624e3173db98a91345157501fe03ae97b9865)

@swift-ci Please test

@swift-ci Please test source compatibility


WIP: 1.7pg-a4

@cheungpat, thanks for your PR! By analyzing the annotation information on this pull request, we identified @rickmak to be a potential reviewer


Remove generateSWString from workbox-build

I'm considering removing the generateSWString mode from the workbox-build build tool from Workbox v5.
I don't believe that this is a widely used mode (compared to injectManifest and generateSW), and one of the reasons it was kept around is because it was used under the hood in the workbox-webpack-plugin. That's going to change in Workbox v5 as well.
If you have a strong use case for generateSWString that can't be filled by generateSW, please let me know.

This was removed in #2068.


#137  - Moving Admission button - Chezlin Benson

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Moving admission button to it's own container below fees container
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #137
📸: Screenshots
Kindly attach screenshots if available

Checklist:

[*] My code follows the style guidelines of this project
[*] I have carefully reviewed my own code
[*] I have commented my code
[*] I have updated any documentation

This PR has no file changes, can we close this?


Jetty + CE3

Changes Introduced
Trying the Jetty backend w/ CE3
Applicable linked issues
Checklist (check all that apply)

[ ] This change maintains backwards compatibility
[ ] I have introduced tests for all new features and changes
[ ] I have added documentation covering all new features and changes
[ ] This pull-request is ready for review

Codecov Report

Merging #135 (6326e15) into main (1d11c1d) will increase coverage by 0.50%.
The diff coverage is 78.40%.

@@            Coverage Diff             @@
##             main     #135      +/-   ##
==========================================
+ Coverage   88.64%   89.15%   +0.50%
==========================================
  Files          87       87
  Lines        2492     2544      +52
  Branches       56       62       +6
==========================================
+ Hits         2209     2268      +59
+ Misses        283      276       -7

Impacted Files
Coverage Δ

.../scala/kinesis/mock/KinesisMockServiceConfig.scala
0.00% <0.00%> (ø)

...cala/kinesis/mock/api/AddTagsToStreamRequest.scala
100.00% <ø> (ø)

...n/scala/kinesis/mock/api/CreateStreamRequest.scala
100.00% <ø> (ø)

...ock/api/DecreaseStreamRetentionPeriodRequest.scala
100.00% <ø> (ø)

...n/scala/kinesis/mock/api/DeleteStreamRequest.scala
100.00% <ø> (ø)

...sis/mock/api/DeregisterStreamConsumerRequest.scala
100.00% <ø> (ø)

...cala/kinesis/mock/api/DescribeLimitsResponse.scala
100.00% <ø> (ø)

...nesis/mock/api/DescribeStreamConsumerRequest.scala
100.00% <ø> (ø)

...scala/kinesis/mock/api/DescribeStreamRequest.scala
100.00% <ø> (ø)

...inesis/mock/api/DescribeStreamSummaryRequest.scala
100.00% <ø> (ø)

... and 26 more

Continue to review full report at Codecov.

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


Heroku Installation

Hi,
I'm getting an error on heroku when trying to install taglib-ruby.
I have taglib installed at /app/vendor/taglib but not sure how to set Heroku bundle configs to do the --with-opt-dir
Any help would be appreciated
Thanks!

Try setting the CONFIGURE_ARGS environment variable to --with-opt-dir=/app/vendor/taglib. It would also be good to have a look at the log files, they might include a clue as to what's going wrong.
Other than that, I'm afraid I can't really help with Heroku much.


Set argv opt to false for cosmiconfig

Proposed changes
This fixes an issue with invocation of cosmiconfig while being used with webpack(through postcss-loader). By default, cosmiconfig looks for --config flag value. Relevant docs - davidtheclark/cosmiconfig#argv. This conflicts with the webpack flag. Setting argv to false resolves the issue.
Related issue - davidtheclark/cosmiconfig#77
Types of changes
Bug (non-breaking change which fixes an issue)
Checklist

[x] I have read the CONTRIBUTING guide
[x] Lint and unit tests pass with my changes
[ ] I have added tests that prove my fix is effective/works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes are merged and published in downstream modules

Further comments
I have not added any tests for this change as postcss-loader is probably the more appropriate place to have the test in.
Reviewers: @michael-ciniawsky, @ertrzyiks

:warning: Pull Request - Issues :warning:

Commit: b9b78c462080f16005a459d5dac333cfac0b086b
Commits must be in the following format: %{type}(%{scope}): %{description}

This message was auto-generated by https://gitcop.com

Coverage remained the same at 100.0% when pulling fea6d0a6f8c6a0904d9e0b100465ea9b9f6dbdf7 on sudo-suhas:fix_cosmiconfig_argv_opt into bd714f23deb5a3a5d97d3f6e0d21433878f0ce84 on michael-ciniawsky:master.

I normally set this in postcss-loader already, could you post your current configs (webpack.config.js && postcss.config.js) + [npm] scripts please 😛 . The reason it isn't set in postcss-load-config is because of other PostCSS runners like e.g postcss-cli., so I need to be careful to not break other usecases

@michael-ciniawsky I didn't realise that. The issues were reported by @maksimr and @pcourt. @pcourt had shared some details for stack trace and the package.json in this comment - https://github.com/davidtheclark/cosmiconfig/issues/77#issuecomment-317396035

Looks like @pcourt is using<EMAIL_ADDRESS>which did not set the option.argv - https://github.com/postcss/postcss-loader/blob/1.2.1/index.js#L71.

I think we can close this PR.

No rush :), lets wait for confirmation on his side to make sure 😛

@pcourt reported that<EMAIL_ADDRESS>fixed his issue - https://github.com/davidtheclark/cosmiconfig/issues/77#issuecomment-317655117. Closing PR.


go get throwing an error

I am trying to download this dependency using
go get -u github.com/sparrc/go-ping

go: github.com/sparrc/go-ping upgrade => v0.0.0-20201022122018-3977ed72668a
go get<EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: github.com/go-ping/ping
                but was required as: github.com/sparrc/go-ping

Any idea how I can fix this?

The repo has been moved, you need to update your code to use github.com/go-ping/ping.


 Here is a website that you can generate and test cron expression.
But by the screenshots you post, they do not match.
By the example you give, I test it on the Davinci, here is the result:

Please check it to confirm it's a screenshot misoperation or  a potential Davinci bug.


terminate called after throwing an instance of 'pwgen::PwgenException'   what():  Driver error:

Hi @jkjung-avt,
During conversion from onnx to TRT I am getting an error as: terminate called after throwing an instance of 'pwgen::PwgenException'   what():  Driver error. May I know the cause of this error?
Thanks,
Darshan

I have not seen this error before.  I googled the error message and found the following references, based on which I think you should check your CUDA driver/libraries installation.

https://forums.developer.nvidia.com/t/pwgenexception-when-building-a-cuda-engine/154469/6
https://github.com/stereolabs/zed-docker/issues/28

Hi @jkjung-avt ,
Thank you very much for your reply.
I reinstalled cuda driver, cuda, cudnn, and tensorrt and it worked perfectly.
Thanks,
Darshan


Github actions, junit dependency fix

This fixes a missing junit 3.8 (!) dependency.
Besides that, it's adding a Github actions workflow that simply does the Maven build with all LTS JDKs.
And it's adding dependabot for updating the plugins / dependencies.

The changes look good to me, so please clarify when you think the changes are ready for the merge

This is now ready for a merge.
Thanks for the quick response, this is much appreciated.

It is strange the build succeeds with Java 21.
I guess it means the plugin tests are not executed during the build somehow :-/

The integration tests still have issues: https://github.com/tulipcc/ph-javacc-maven-plugin/pull/28
I am not confident in releasing it as is without fixing the tests. It would be great if you could help with the failures

Interesting .. I was not aware of that.
[INFO] Caused by: java.lang.ClassNotFoundException: org.apache.maven.reporting.AbstractMavenReport sounds much like the change being the cause.
You're totally right, JDK 21 is a corner case. IMHO it's better to carefully update the dependencies / plugin versions with the dependabot introduced and the CI test added in #20
Obviously these need a certain composition to match to each other.

I agree the current failures have nothing to do with java 21, however, I would like to resolve them before releasing


,  : Add Device.WiFi mapper

Reason for change: Device.WiFi variables must be converted to
SSIDProfiles for Easymesh Controller to operate properly. Both
during initial bootup and after variable modifications.
Test Procedure: Use CLI or GUI to change SSID and/or KeyPassphrase.
Risks: Low
Signed-off-by: Engin Akca<EMAIL_ADDRESS>

Hi @meycint (Engin) - please make a trivial change to the pull request and if presented with a way to sign the CLA, do so.  (This repo has a CLA while the other one does not.)  There was a problem in CLA checking which is why this is stuck.  I'm sorry for the inconvenience. - Martin

https://jenkins.code.rdkcentral.com/job/github-triggered/16327/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/52201/ started.

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/119910/


[QUESTION] Could we get a more noob-friendly documentation section of the X-Frame-Options: ALLOWORIGIN docs?

Question
I'm gonna try and frame this from the reference of the beginner, as that's what I am (I think), and I think the docs assume the reader has more of a fundamental understanding than they may actually have. I would also like to add that I have not yet been able to get this to work, and I have been trying for some time now, so hopefully someone can swoop in and save us normies that are still a little green.
The issue pertaining to my discussion surrounds that of the pop-up modal/workspace view not being able to display due to the X-Frame-Options: ALLOWORIGIN not being passed or set correctly (I think). I am using the docker container, as I was unable to build the app from source because I had an issue setting up the environment, which may be more related to the distro I'm using.
Part 1
The first thing I came across when trying to troubleshoot this was the docs, where it says :
Refused to Connect in Modal or Workspace View#
This is not an issue with Dashy, but instead caused by the target app preventing direct access through embedded elements.

As defined in [RFC-7034](https://datatracker.ietf.org/doc/html/rfc7034), for any web content to be accessed through an embedded element, it must have the [X-Frame-Options](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options) HTTP header set to ALLOW. If you are getting a Refused to Connect error then this header is set to DENY (or SAMEORIGIN and it's on a different host). Thankfully, for self-hosted services, it is easy to set these headers.

These settings are usually set in the config file for the web server that's hosting the target application, here are some examples of how to enable cross-origin access with common web servers:

So my first thought was to try and see what webserver dashy was running on. I had a little bit of trouble at first figuring that out, but I am assuming now it runs on express.js. I couldn't figure out how to add the X-Frame-Options: ALLOWORIGIN bit to that server, as the docs mention NGINX, Caddy, Apache, and LightHttpd. So I tried spinning up both nginx and nginx proxy manager, and no matter what set of configurations I threw at it, including setting the X-Frame-Options and a wide open CORS config, I cannot seem to get a proper configuration up and working.
I also tried adding webServer: headers: X-Frame-Options: ALLOWORIGIN to the conf.yaml file with no luck either.
One thing I will note, is that sometimes the Response Headers X-Frame-Options will come back with ALLOWORIGIN, sometimes deny, even though I have seemingly set them to be ALLOWORIGIN, in the config, and further still sometimes they will refuse to display even when coming back with ALLOWORIGIN. I could not even begin to tell you why that is.

Part 2
What I am asking for here is for the docs to be updated to explain some of the more elementary steps involved in resolving this, as from the perspective a beginner that has just spun up a docker container, getting this error and trying to figure out what in the world is going on is a bit daunting, never-mind even resolving the issue (I still have not, will keep trying). If you could explain whether or not these settings need to be applied inside the docker container somewhere, outside it, or both, and where, etc., As resources surrounding the topic are a bit scant.

I will keep looking for a way to solve this on my own in the meantime, and update this feed as I learn what I messed up on to try and shed some light for others that may be stuck in my same conundrum.
This has been tried from multiple machines, both locally and remote, from LAN and from WAN, all on the docker container.
Please let me know if there is anything I can provide to help troubleshoot.
Cheers.
Category
Documentation
Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this question hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

IFRAMES do not work on all sites, the site has to allow remotes (e.g: you) to embedded the page in a different website. This obviously can be bad, think of a fakebank.com doing a full iframe around chase.com with a little custome js to steal the content.
This validity is actually checked by your browser ironicly.
You can get a browser plugin such as https://addons.mozilla.org/fr/firefox/addon/ignore-x-frame-options-header/ that can let you "Ignore X-IFrame".
I needed to do this to view several managed systems to make them display in an iframe (like the workspaces). Hope that helps someone.


GitHub Add external link icon

As requested by @demerzel3 I added an external link icon beside branch name to highlight that's a link.
Feel free to propose other icons

?


fixing log entity

quick fix to entity and related routes

Your Pull Request code is being promoted!  Please follow the link below.
Main Merge Workflow


Add a schema for flags

I just found the Payment link in the Routes wasn't showing because it depends on flag.allow_payment which I didn't have in ACUS.

packages/amber/views/Settings/AddNewYearDialog.tsx # 60
60,1: const flags = ['flag.allow_game_signup', 'flag.allow_registration', 'flag.display_gamebook', 'flag.display_schedule']
Flags in database in table setting:
flag.display_virtual_details
flag.dev_use_detail_room_quantities
flag.is_beta
flag.send_admin_email
flag.display_schedule
flag.allow_registration
flag.allow_game_signup
flag.display_gamebook
flag.allow_payment

Right now allow_payment isn't reset for a new year.


 Maybe it's from torch? Or a default Python thing?

Can you share some code to reproduce the error?

Closing since this can not be reproduced


I got some Problem in compile DLL with dynamic method

fastJSON is a great basic library that I use for years in most of my programs.
In order to use dynamic I decide to upgrade from 1.0  to 2.1.5.
But when I compiled, the method ToDynamic is not exists in the DLL.
I found the compile condition net4 seems to working in VS2015 and SharpDeveloper.
So I tried to remove the compile condition line in the following code:
#if net4
        /// <summary>
        /// Create a .net4 dynamic object from the json string
        /// </summary>
        /// <param name="json"></param>
        /// <returns></returns>
        public static dynamic ToDynamic(string json)
        {
            return new DynamicJson(json);
        }
#endif

Then I compiled in vs2015 and got the DLL with ToDynamic().
But SharpDevelop was unable to compile and raised Error CS0246: unabled to find “DynamicJson”.
I think there must be a better way to compile DLL with dynamic.
Can anyone help me , thanks .

Put a net4 directive in the Release conditional compile option in the project file.


Ensure proper redirects of partial paths

It has always been the idea to redirect paths like /docs/introduction/
to the first page in that section. Though it wasn't known that Netlify
doesn't apply redirects for "shadowed" content:
https://docs.netlify.com/routing/redirects/rewrites-proxies/#shadowing
This change enforces redirects regardless of the presence of any actual
page behind the redirect source.

Works as desired in the preview:

https://deploy-preview-1768--prometheus-docs.netlify.app/docs/
https://deploy-preview-1768--prometheus-docs.netlify.app/docs/prometheus/
https://deploy-preview-1768--prometheus-docs.netlify.app/docs/introduction/overview/index.html


Update view command in UG

Currently the ss are not attached

Codecov Report

Merging #164 (9d8a34c) into master (002414f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #164   +/-   ##
=========================================
  Coverage     60.80%   60.80%
  Complexity      613      613
=========================================
  Files           101      101
  Lines          2531     2531
  Branches        322      322
=========================================
  Hits           1539     1539
  Misses          855      855
  Partials        137      137

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 002414f...9d8a34c. Read the comment docs.


Update to Yara 4.3

This is a work in progress, as Yara 4.3 is not out yet.
Most of the small work has been done, what's left is:

[x] Add tlsh & md5 hash in elf module (https://github.com/VirusTotal/yara/pull/1624)
[x] Add authenticode parsing in pe module (https://github.com/VirusTotal/yara/pull/1623)
[ ] Add new warnings (https://github.com/VirusTotal/yara/pull/1806)

[ ] Needs a warning system, not yet done in boreal

[ ] Add xor key flag in boreal-cli (https://github.com/VirusTotal/yara/pull/1745)
[ ] Add module names flag in boreal-cli ? (https://github.com/VirusTotal/yara/pull/1801)
[ ] Realignment on SectionAlignment in pe module, see https://github.com/VirusTotal/yara/pull/1561

@vthib, by following a link in YARA's repository I landed here and discovered this project. I don't know if you have seen https://github.com/VirusTotal/yara-x, but the goals are very similar: a complete implementation of YARA in Rust, that solves some of the pain points experienced by YARA users (like slow rules that should be actually fast) and developers (like the parser tightly coupled with YARA itself that disallows its reuse).
The approach however is different. YARA-X converts rule conditions into WebAssembly code, that in turns gets translated into native code. This makes conditions that rely heavily on loops much faster. The goal is that condition evaluation is 10x faster than the existing YARA on average. I see that you seem to have experience in Rust (more than myself, I'm gradually learning Rust with the YARA-X project), so if you would like to contribute to YARA-X in some way you are really welcomed. The project is still immature and unstable, but I've made a lot of progress already, and have implemented most of the condition evaluation logic.

So this is failing only on linux32, and it took me longer than expected to understand why. Running boreal-cli has no issues, running the tests on linux32 does give invalid values for not_before and not_after fields in the authenticode certificates.
Turns out, this is a linker issue. When linking the final binary, there are two libraries that have functions with the same names:

libyara.a version 4.3, compiled through yara-rust, with the new authenticode library
libauthenticode.a, compiled through the authenticode-parser crate, with this authenticode library as well.

So the linker can pick any of those two and we can't control it.

For boreal-cli, this is not an issue, we do not link against yara, so there is a single solution.
For the tests, we link against yara to check conformance, hence the conflict. This is all fine if both libraries have the same code, but because of this commit: https://github.com/vthib/authenticode-parser-1/commit/fd91356ef51c142c6245d48019ba26e695ebaf06, the objects do not have the same size. We end up linking against the yara authenticode functions, but use the bindings on the authenticode-parser version. Those types differ only on linux32 (time_t = 32 bits != int64_t), causing the crashes.

Fun...


Developement 1

The project contains two sections portfolio setup and mobile-first. The toolbar section and the headline section contain the media link and an introduction.

I have made the necessary changes.
now what should I do


Fail to run Kong from compiled source code as mentioned on DEVELOPER.md

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
3.4.0
Current Behavior
I use a clean Ubuntu 22.04 LTS on a x86_64 machine. And I want to compile Kong from source code. The following bash script is majorly from DEVELOPER.md and I run them as root user:
cd ~
sudo apt update \
&& sudo apt install -y \
    automake \
    build-essential \
    curl \
    file \
    git \
    libyaml-dev \
    libprotobuf-dev \
    m4 \
    perl \
    pkg-config \
    procps \
    unzip \
    valgrind \
    zlib1g-dev \
    docker-compose
git clone https://github.com/Kong/kong
cd kong
git checkout 3.4.0
export GITHUB_TOKEN=github_xxx
make build-venv

When finish building Kong, I use the following code originally from DEVELOPER.md try to start Kong:
source /root/kong/bazel-bin/build/kong-dev-venv.sh # venv
start_services
kong migrations bootstrap
kong start

When executes on kong start, I met this exception:
# kong start
2023/09/12 20:52:26 [warn] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
2023/09/12 20:52:26 [warn] ulimit is currently set to "1024". For better performance set it to at least "4096" using "ulimit -n"
Error: ...azel-bin/build/kong-dev/share/lua/5.1/kong/cmd/start.lua:98: nginx: [error] init_by_lua error: ...el-bin/build/kong-dev/share/lua/5.1/kong/tools/utils.lua:786: error loading module 'kong.plugins.opentelemetry.handler':
...s/kong/bazel-bin/build/kong-dev/share/lua/5.1/protoc.lua:342: module load error: opentelemetry/proto/collector/trace/v1/trace_service.proto
	opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	./opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	/usr/local/kong/include/opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	/usr/local/opt/protobuf/include//opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	/usr/include/opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	kong/include/opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
	spec/fixtures/grpc/opentelemetry/proto/collector/trace/v1/trace_service.proto: No such file or directory
stack traceback:
	[C]: in function 'error'
	...s/kong/bazel-bin/build/kong-dev/share/lua/5.1/protoc.lua:342: in function 'f'
	...s/kong/bazel-bin/build/kong-dev/share/lua/5.1/protoc.lua:1149: in function 'do_compile'
	...s/kong/bazel-bin/build/kong-dev/share/lua/5.1/protoc.lua:1165: in function 'compilefile'
	...s/kong/bazel-bin/build/kong-dev/share/lua/5.1/protoc.lua:1178: in function 'loadfile'
	...g-dev/share/lua/5.1/kong/plugins/opentelemetry/proto.lua:9: in function 'load_proto'
	...g-dev/share/lua/5.1/kong/plugins/opentelemetry/proto.lua:12: in main chunk
	[C]: in function 'require'
	...ng-dev/share/lua/5.1/kong/plugins/opentelemetry/otlp.lua:1: in main chunk
	[C]: in function 'require'
	...dev/share/lua/5.1/kong/plugins/opentelemetry/handler.lua:4: in main chunk
	[C]: at 0x7f55a26e0310
	[C]: in function 'xpcall'
	...el-bin/build/kong-dev/share/lua/5.1/kong/tools/utils.lua:777: in function 'load_module_if_exists'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:154: in function 'load_plugin_handler'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:260: in function 'load_plugin'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:312: in function 'load_plugin_schemas'
	...ong/bazel-bin/build/kong-dev/share/lua/5.1/kong/init.lua:629: in function 'init'
	init_by_lua:3: in main chunk
stack traceback:
	[C]: in function 'error'
	...el-bin/build/kong-dev/share/lua/5.1/kong/tools/utils.lua:786: in function 'load_module_if_exists'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:154: in function 'load_plugin_handler'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:260: in function 'load_plugin'
	...bin/build/kong-dev/share/lua/5.1/kong/db/dao/plugins.lua:312: in function 'load_plugin_schemas'
	...ong/bazel-bin/build/kong-dev/share/lua/5.1/kong/init.lua:629: in function 'init'
	init_by_lua:3: in main chunk

  Run with --v (verbose) or --vv (debug) for more details

Expected Behavior
The Kong should start normally.
Steps To Reproduce
(Please see "Current Behavior" section, I have paste all the script I executed there)
Anything else?
n/a

By the way, I fixed it by executing make install as root user. However, this behavior has not been mentioned in DEVELOPER.md. I am curious if other users are able to start their development environment successfully without executing make install?

Eventually I found the reason why Kong raises Error: ...azel-bin/build/kong-dev/share/lua/5.1/kong/cmd/start.lua:98: nginx: [error] init_by_lua error..., you need to switch your working directory to ~/kong/ (or your kong source code directory) then execute kong start

If you meet exception from opentelemetry or PATH, you need to execute the following code:
echo 'PATH=$PATH:~/home/user/kong/bazel-bin/build/kong-dev/openresty/bin' | sudo tee -a ~/.bashrc
echo 'PATH=$PATH:~/home/user/kong/bazel-bin/build/kong-dev/openresty/nginx/sbin' | sudo tee -a ~/.bashrc
echo 'PATH=$PATH:~/home/user/kong/bazel-bin/build/kong-dev/bin' | sudo tee -a ~/.bashrc

The user mentioned above could be /root, these code from .github/workflows/perf.yml:63


Theme package

Separate out micro:bit branding for clarity if folks deploy alternative versions
Parameterise the app name
Don't pull purple in just for links

Known changes:

Tooltips have shrunk but are now consistent with Python

I'm going to go ahead and merge this now as it's going to be a painful source of conflicts otherwise. I'll update current PRs as needed.


District level details to have Active, Recovered, Deaths, Delta

Is your feature request related to a problem? Please describe.
When we click on State (table) to show District wise breakup (row), it is not showing all colums like for state e.g. Active, Recovered, Deceased and their Deltas.
Only DISTRICT, CNFMD are shown
Describe the solution you'd like
It is Low hanging fruit.
Low cost, High return
Step-1) Just add Deltas and these column values in api response for
https://api.covid19india.org/state_district_wise.json
Step-2)row.json to have columns head and values similar to as in table.json
I can raise PR if u can do step-1 or Tell me repo or where to do that
Describe alternatives you've considered
Not any at moment
Additional context

Please go through old issues before posting a new one


Import megatron.data.helpers failing

Following the documented steps for training in the README resulted in import errors in Python 3.9.16 when trying to train a model.  Similar problems were reported a while ago in the megatron mailing list when python3-config was not present.  However that is not the situation in my case.
Traceback (most recent call last):
  File "/src/gpt-neox/train.py", line 27, in <module>
    pretrain(neox_args=neox_args)
  File "/src/gpt-neox/megatron/training.py", line 203, in pretrain
    ) = build_train_valid_test_data_iterators(neox_args=neox_args)
  File "/src/gpt-neox/megatron/data/data_utils.py", line 400, in build_train_valid_test_data_iterators
    train_ds, valid_ds, test_ds = build_train_valid_test_datasets(
  File "/src/gpt-neox/megatron/data/data_utils.py", line 139, in build_train_valid_test_datasets
    train_dataset = build_dataset(0, "train")
  File "/src/gpt-neox/megatron/data/data_utils.py", line 127, in build_dataset
    dataset = GPT2Dataset(
  File "/src/gpt-neox/megatron/data/gpt2_dataset.py", line 52, in __init__
    self.doc_idx, self.sample_idx, self.shuffle_idx = _build_index_mappings(
  File "/src/gpt-neox/megatron/data/gpt2_dataset.py", line 173, in _build_index_mappings
    from megatron.data import helpers
ImportError: cannot import name 'helpers' from 'megatron.data' (/src/gpt-neox/megatron/data/__init__.py)

To Reproduce

pip install -r requirements/requirements.txt
python ./megatron/fused_kernels/setup.py install
python prepare_data.py -d ./data
python ./deepy.py train.py -d configs 19M.yml local_setup.yml

Environment
Python 3.9.16
GPU: RTX A5000
CUDA 11.6

Looks like the C++ dataset helpers.so failed to build. Can you head to gpt-neox/megatron/data, run make, and post the error message here?

Thanks to @Quentin-Anthony who found the underlying cause. He pointed out to me (outside this ticket) that the library helpers.cpython-38-x86_64-linux-gnu.so  references Python 3.8 whereas I was using Python 3.9.  With that information I was able to track down the underlying cause. The python3-config in the provider's standard Cloud GPU VM was misconfigured:
$ ls -al $(which python3)
lrwxrwxrwx 1 root root 18 Jan 25 15:26 /usr/local/bin/python3 -> /usr/bin/python3.9
$ ls -al $(which python3-config)
lrwxrwxrwx 1 root root 16 Mar 13 2020 /usr/bin/python3-config -> python3.8-config

I have filed a ticket with the provider.
So the underlying cause is similar to other cases online of megatron.data.helpers not being built because of problems withpython3-config.
The following temporary workaround solved the problem: Changing python3-config in
gpt-neox/megatron/data/Makefile to python3.9-config to match the python3.9 executable I am using.

@convexstrictly I'm not very familiar with Cython, but is this something where we can make modifications to make the code more flexible? If your temporary work-around is general, would it make sense to add a warning to the readme?

@StellaAthena What happened here is that the megatron.data Makefile uses python-3.config to construct the name of the dynamically linked library: helpers.cpython-38-x86_64-linux-gnu.so for Python 3.8, or helpers.cpython-38-x86_64-linux-gnu.so for Python 3.9.  Since the provider's VM had a python3-config that was misconfigured, a helper.*.so with the wrong version was being generated, and because Python could not find the shared library, it complained that helpers did not exist.
My workaround is not general.  I hard-coded it to use python3.9-config.  I could modify the Makefile to call a shell-script that attempts to find the right python3-config.  But there are two problems:

I am uncertain how robust my shell script would be; given the variety of ways in which Python is set up.
even assuming the script works correctly, I wonder how many cases of misconfiguration my script would actually cover given the variety of ways environments can be misconfigured.

I suggest two possible courses of action (not mutually exclusive) :

Create a Troubleshooting section, and document what to look for if they encounter this error.
Create a shell or Python script that checks for problems in their environment.  It does not try to work around the errors, merely finds them, reports on them, and suggests workarounds.

I think the second course of action is particularly attractive if you get questions about failures that tend to be problems with users' environments, the same questions get asked repeatedly, and you decide not to workaround these issues in the code base.  I am happy to document workarounds for this error in the Troubleshooting section, or help with writing a shell/Python script to detect commonly-occurring problems with users' environments.


partitions with only 1 PE in non-smp mode hang during inter-partition communication

Original issue: https://charm.cs.illinois.edu/redmine/issues/310

No body.

Original date: 2013-10-23 02:57:04

Commit 3d684fc786beed84ab792351f72c7ee421e103cf resolves this issue.


Refactor/fmt

Some small linting fixes using golint and ran go fmt on all files so we start clean.
We have configured our IDEs to do fmt before save.

Fine for me, but now conflicts with the master, because of the previous merges, please rebase.

Changes Unknown when pulling f7a44c8c2194811e620366ab03463548586d04c2 on refactor/fmt into ** on master**.

Fixed the conflicts.


Update docs / warnings prior to next release

We need to make changes on the following points:

The docs on contributing solver interfaces incorrectly describes the default conic form for the vectorized PSD cone. Our SDP solvers (CVXOPT, SCS, MOSEK) all use different formats. CVXOPT uses the format built-in to conic_solver.py, while SCS and MOSEK have their own formatting functions.
The error message for lack of a mixed-integer solver needs to be updated. Right now it doesn't tell users that ECOS_BB is once again an option. Users should be presented with a message that refers them to web documentation for detailed discussion. The discussion should mention that ECOS_BB is an option out of the box, but due to possible correctness issues, the solver will never be called automatically.
In discussion on mixed-integer solvers, NAG is mentioned as an option. Our NAG interface doesn't actually have mixed-integer support. The file cvxpy/reductions/solvers/defines.py should be checked to make sure NAG isn't miscategorized. (Misclassifications here are my fault.)
The release notes should mention changes to the MOSEK interface. It might actually be worth having some longer discussion on the solver page about the changes.

The NAG interface at least has no mixed integer support.

This should be linked to #1138


table heading should be frozen

Description
Right now if you have a large table and the scroll wheel is enabled the header disappears.
heading should be frozen for readability

Code example
No response
Method of implementation
No response

Also implemented in the latest version of the repo.
Louis

Works as expected! Thanks


feat(message): Upload Message to IPFS

This is no longer a work in progress, is ready for @christroutner to review
PR related to this trello task --> https://trello.com/c/WUa72yUM

:tada: This PR is included in version 1.4.0 :tada:
Your semantic-release bot :package::rocket:


get rid of alerts.

LGTM

Maybe you use console.error instead of console.log, because application does not work, when you do not get results from youtube app.

thanks @ElliDy I corrected that.


Custom primitive TypeHandlers are ignored in MyBatis 3.3

In MyBatis 3.2.8, we registered primitive TypeHandlers using XML like this:
<typeHandler javaType="java.lang.Boolean"
    handler="com.mycompany.myproject.ibatis.MyBooleanHandler"/>

This registered our custom handler for both the primitive and wrapper types. Because of issue #165, I understand that in MyBatis 3.3.0 we need register our TypeHandler twice if we want it to handle both primitive and wrapper types:
<typeHandler javaType="boolean"
    handler="com.mycompany.myproject.ibatis.MyBooleanHandler"/>
<typeHandler javaType="java.lang.Boolean"
    handler="com.mycompany.myproject.ibatis.MyBooleanHandler"/>

However, instead of registering the handler for both types, this XML configuration registers the handler for the wrapper type twice. As a result, primitive types are handled by the default BooleanHandler and not our custom TypeHandler. I have verified this by tracing calls to the TypeHandlerRegistry.register() function:
register(class java.lang.Boolean, null, class java.lang.Boolean);
register(boolean, null, class java.lang.Boolean);
register(class java.lang.Byte, null, class java.lang.Byte);
register(byte, null, class java.lang.Byte);
...
register(class java.lang.Character, null, class java.lang.Character);
register(char, null, class java.lang.Character);
register(com.mycompany.myproject.ibatis.MyBooleanHandler);
register(com.mycompany.myproject.ibatis.MyBooleanHandler);

Hi @Poobslag thanks for the bug report.
Whic one is the wrong line?

Here is the list of built-in type aliases.
http://mybatis.github.io/mybatis-3/configuration.html#typeAliases
As you can see, boolean is an alias for java.lang.Boolean.
To specify primitive boolean type, you have to write _boolean.

Thank you Iwao. I think we can close this one then.

Thanks, I'm sorry for the false bug report. MyBatis 3.3.0 is the first release where I needed to distinguish between "_boolean" and "boolean", but that all makes sense now.


Broken links in README

Broken links to reactjs/history get incorrectly forwarded to mjackson/history.  This fixes those links to point to the correct location

Thanks!


Please restore ability to work without a configuration file

The old Dependabot Preview was capable of discovering all package managers used in a repository and "just worked". The new GitHub version now requires a vendor-specific yaml file in my git repository.
At the very least, this change should be documented in the documentation "Differences between Dependabot Preview and GitHub-native Dependabot"

Related to https://github.com/dependabot/dependabot-core/issues/3597

Ah sorry, I tried searching for duplicates but didn't find that issue.

@intgr, I've prepped a docs change and it'll be out once I can get it reviewed.
As for the use case--is it the same as what was mentioned earlier (desire for config to live outside the repo), or something else?

Sorry I forgot to reply to this.
I guess my main point is that Dependabot should follow "Convention over configuration". If all my package management files are at their standard locations, Dependabot should be able to discover them and just work with no config file.

While this is the behavior for security updates, I'm not sure I agree with enabling dependabot version updates by default for all ecosystems in a repo. I think that folks generally do want to have some control over the update schedule (at a minimum), so we either need to build a UI to change this, or provide the same config file.

folks generally do want to have some control over the update schedule

The "Enable Dependabot" feature on GitHub suggests interval: "daily", which seems fine to me and I'll bet for many other users as well. If it's the "default", why do I need any configuration for it? :)
For the kinds of repositories that I maintain, I frankly don't care about the schedule, it could be any time of day or weekly or hourly. I handle them like ordinary pull requests: after they come in, when I find free time I take a look and make a decision.
For people who want more control, sure, why not make them have a configuration file in their repo.

I'll have to think about the details a bit more, but in general, I think that we'll want to move the product to be:

enabled via an API/UI (like what we've got for security updates)
configurable via config file (same file controlling both) (so if you want to opt out of version updates you'd say something like schedule.interval: 'alert_only' or schedule.interval: 'never' to turn off an individual manifest entirely)

I don't think this is going to come soon, as it'll require some work on APIs and a UI, but I do think it's a good long term direction.

👋 Hello! Product Manager for Dependabot here. I’m currently doing research into adding/improving configuration for security updates, and am looking for user input. This issue is similar to things I’m thinking about, so if you’re subscribed to this and you’re open to a short conversation with me, please feel free to select a time in my calendar that fits your schedule here: https://calendar.app.google/7RSxjJJo9FdvRHNz7


Add Hints and example for Data Neo4j.

This PR provides Neo4jRepositoriesHints and Neo4jReactiveRepositoriesHints, triggered by the appropriate auto configuration classes in the latest Spring Boot 2.4.
The hints have been added to RepositoriesHints.
In addition, data-neo4j as an examples has been added. It's basically a copy of the data-mongo sample, with the same domain and the same queries, but for Neo4j.
For a successful run of build.sh, a locally running Neo4j instance is required. The easiest way to get one is
docker run --publish=7474:7474 --publish=7687:7687 -e 'NEO4J_AUTH=neo4j/secret' neo4j:4.1

Please feel free to adapt as necessary.
cc @christophstrobl @meistermeier

Thanks for this contribution @michael-simons. We currently can't use Docker on Docker, so we would need to install Neo4j on our spring-graalvm-native Docker image which will be not straightforward because Neo4j requires requires Java 11+. Since it will require some work on that side I move it to 0.8.2.

I think using neo4j:3.5 (requiring JDK 8) should work equally well. I need to add in some config for the connection to work, but that's easily doable.
How are you running MongoDB or elastic? Did you install those on the base image? I cannot imagine you're running their products natively… If so, we would like to have your help making Neo4j native runnable, too :D

So, I switched the compose script to Neo4j 3.5 and added a hint to the pom about the need for all security services when people might want to use an encrypted connection. Please let me know if this works for you.

Nice, we can maybe try to make it runnable for 0.8.1 then.
Do you want to try to add support yourself based on what we did for elasticsearch in https://github.com/spring-projects-experimental/spring-graalvm-native/commit/fe0e651de4890708bd814deeda87dc1b3e095dc4 and https://repo.spring.io/milestone/org/springframework/experimental/spring-graalvm-native-docs/0.8.0/spring-graalvm-native-docs-0.8.0.zip!/reference/index.html#_using_container_based_build_environment ?

Hi, I tried but I failed miserably. Our deb package is complaining about openjdk not installed (and also about package daemon). The later is fixable of course, but it seems not reasonable to replace the jdk.
I started the CI container with docker run -it spring-graalvm-native-dev:20.2-dev-java8  /bin/bash to run my experiments.
When I fix the daemon package (with apt-get install daemon), and than do the following:
curl -LO https://dist.neo4j.org/deb/neo4j_3.5.21_all.deb \
 && dpkg  --force-all -i neo4j_3.5.21_all.deb

In the container, I end up with
Setting up neo4j (1:3.5.21) ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.

Here are our instructions
https://neo4j.com/docs/operations-manual/3.5/installation/linux/debian/
The dl link to the deb is above, tarball would be https://neo4j.com/artifact.php?name=neo4j-community-3.5.22-unix.tar.gz
If you can help me getting the service installed, I can add the missing config bits.

I managed to add a running Neo4j 3.5 to the container (also removed the tons of elastic search stack traces), but I cannot manage to get anything build in either the dev or master image. However, mongo or elastic fail as well. I guess this is unrelated.

Ok thanks I will have a deeper look.

I will take care of merging this PR.

Merged with a remaining issue (#300) which is maybe a regression on our side. Thanks a lot @michael-simons, great work.


Import through postMessage

Is there any way to get the resultant xml of import functions by sending a postMessage?
I am trying to open importable files in a blank document directly from NextCloud.
I managed to get it by using the loadTemplate App function, but of course I am being cors-blocked when drawio is hosted in a different domain

Sending a postMessage to/from where?

From an external app (in this case Nextcloud) to the editor.
Something like
editor.postMessage(JSON.stringify({
         action: "import",
         file: //file or url
}), "*");

It would allow to import a file without using the interface.

Ah so this would be with an existing file open with draw.io running in embed mode in an iframe?

Exactly.
I have been looking through the whole code, but I wasn't able to find anything that could help me to achieve this. Is there something I missed?

No, we currently don't support this in the JSON protocol. But for this to be pushed from the outside, there would be an import button in the page that contains the iframe, not in the UI of draw.io?

The goal is to support diferent extensions in NextCloud, so, by opening an example.vsdx file automaticlly creates a example.vsdx.xml blank file, opens it with drawio in the iframe and imports the example.vsdx.
It's a bit weird, but will be easier for the user.

Ah, good use case. So another option would be to allow for VSDX (other supported file formats) in the load message?

Yes, that would be even better, it would be loaded with only one message

Support for all supported file formats will be added in the load action message in the next release. Please use data:application/vnd.visio;base64,... for VSD and VSDX files.


update Gopkg lock so dep ensure doesn't keep changing it

Fixes #14
Proposed Changes

update Gopkg.lock with digest field by using dep 0.5.0

/assign @bobcatfish

Thanks for jumping on this so fast @pivotal-nader-ziada ! :D
We don't have a /meow command yet (#15) so I'll have to add this manually:


Move keyv-memcache to @keyv/memcache

Will NPM handle the redirect or do we need to do dual publishing? Need to validate this first

@jaredwray we can deprecate the current package and change package name in package.json. The warning will appear for current users like this WARNING: This project has been renamed to {your-new-package-name}. Install using new-package-name instead.

@alphmth - makes sense. Will get that scheduled for the next 30 days.


[DCOS-58389] Role propagation and enforcement support for Mesos Dispatcher

Reference PR#66
What changes were proposed in this pull request?
This PR adds role propagation and enforcement capabilities to Mesos Dispatcher.
Currently, there's no mechanism for enforcing quotas for all Spark applications submitted to a single dispatcher. Users can always provide spark.mesos.role as a part of their spark-submit configuration and override any role specified in spark.mesos.dispatcher.driverDefault.. This PR adds new functionality to Dispatcher:

new spark.mesos.dispatcher.role.enforce configuration property triggers a role override verification and rejects submit requests if a user tries to override the default role
the role of the Dispatcher is propagated to all the drivers by default. If role enforcement is not enabled, users can still override the default role

Does this PR introduce any user-facing change?
No
How was this patch tested?

Unit Test Added

This PR is just for reference, so final and effective change has been moved to #69.


THRIFT-5214: Reset read deadline in socketConn

Client: go
This is a slightly different, and less error-prone approach from the
fix in e382275.
The previous approach relies on passing the set socket timeout into the
underlying socketConn from TSocket and TSSLSocket. But since we have so
many different constructors for TSocket and TSSLSocket, some makes the
initial connection in the constructor and some does not, there are so
many different places we would need to remember to pass socketTimeout
into socketConn. In the future, when we add another constructor to them,
we could either forget to pass the socket timeout into socketConn, or
try to pass it while we haven't constructed socketConn yet (which will
cause panic), both are bad.
In this approach we just clear the read deadline in the connectivity
check read. Because that's a non-blocking read, it would work just fine
without a read deadline.

[x] Did you create an Apache Jira ticket?  (not required for trivial changes)
[x] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[x] Did you squash your changes to a single commit?  (not required, but preferred)
[x] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

@dcelasun

This does seem cleaner. I'm not a fan of relying on comments for correct behaviour but that seems like a good trade-off here.

I also added more comment on socketConn.IsOpen to explicitly call out the side-effect (I thought I pushed that last night, but apparently I forgot to do git commit before git push so push did nothing 😬)
In most cases there shouldn't be anything between pushDeadline and actual Read, as the whole purpose of doing pushDeadline is to set the deadline used by the Read. But I just added the comment there in case in the future someone tries to do something without realizing the side-effect. I agree that is not ideal but I don't know if there's any better solutions here.

I agree that is not ideal but I don't know if there's any better solutions here.

I can't think of anything either. Anyway, LGTM.


Create diamonds instead of triangles when collapsing tree

shortest branch length on the side and longest branch length for the center (the angle between side divided by 2)

A better approach might be to make the shortest branch length on the left, the median branch length of the right and the longest branch for the center.


Adding service to get the market

Coverage decreased (-0.9%) to 33.684% when pulling 8e27049282cb94f0ddd9b31130d00177862319b2 on dev into 1f035e7cf1454d1f8b79f2d80369adff03e1e44c on master.

Coverage decreased (-1.4%) to 33.171% when pulling c98e5dd6ea96ada5fccc166cb76385b6c3451dcb on dev into 1f035e7cf1454d1f8b79f2d80369adff03e1e44c on master.


[PROPOSAL] Add restricted API for soft deleting packages

This PR extends the existing DELETE /api/v2/package/{ID}/{version} API to allow the soft deletion of packages. Currently, this endpoint can be used by any unlist scoped API key to unlist a package. This endpoint is mainly used by the nuget.exe delete and dotnet nuget delete commands to unlist packages from the command line.
The soft delete behavior is triggered by including a request body in the DELETE that has the following shape:
{
  "Type": "SoftDelete"
}

If no request body is included, the "Type" property defaults to "Unlist". This maintains backwards compatibility. In other words, the default DELETE behavior for nuget.org remains to unlist but a client can opt-in to the soft delete behavior with a request body parameter.
The intent of this API is to enable automation for test data clean up, i.e. the packages published by NugetTestAccount during gallery functional tests and E2E tests.
The soft delete gesture is gated on the following conditions:

(existing, same as unlist) The target package must exist. You can still operate on a soft deleted package.
(existing, same as unlist) The API key must have the "unlist" scope.
(existing, same as unlist) The API key must have a package ID scope matching the target package.
(existing, same as unlist) The package ID must not be locked.
(new, only for soft delete) The user must be in the NuGetGallery.DeletePackageApi flight.
(new, only for soft delete) The user must not be an admin. I don't want the risk of deleting stuff unintentionally.
(new, only for soft delete) The package download count must not be greater than or equal to 1000.

I will present a full design before moving forward, but generally my plan is to roll this out and write a simple task in the Gallery.Maintenance job to call this delete API on packages owned by NugetTestAccount.
I chose to make this a REST API so that the complex, multistep delete logic is deployed only to a single location (gallery front-end) instead of multiple places (gallery front-end and some delete job). I have no intent of opening this API up to anyone but NugetTestAccount, but the code is written in such a way that it could be extended to future scenarios.

The user must not be an admin. I don't want the risk of deleting stuff unintentionally.

Could you expand your reasoning here? From my understanding an admin would need to manually craft a request to call this API, which seems unlikely to happen by accident.

Could you expand your reasoning here?

The plan for API is just for test data clean-up. There's no need for having more access. Personally, I like the current admin delete flow where you have to type your signature and click a confirmation pop-up before a delete goes through. These safeguards don't exist for an API. As far as I know, we have not needed an API for an administrative package deletion so however small the risk I don't see value in allowing it. If the need comes up in the future we can easily remove this check after we have considered the non-zero risk.


OMP not properly disabled

gradients_X_weave in stationary has not been 'pragma'fied, to make sure that omp disabled when the config flag is set to False. Happy to fix just need to make a note of it. :)

Now weave has been basically dropped, the problem has moved but is still there. Will take a look when I get back in September but might be useful to get this sorted before the next Summer School if anyone wants to take a look?


Custom CLI Commands

This allows users to create their own commands like Laravel Artisan's ones.
Quorra PR: https://github.com/quorrajs/Quorra/pull/12
Github page PR: https://github.com/quorrajs/quorrajs.github.io/pull/4
PS: Check failed by bithound are not about this feature

Rewritten in ES5, in the next days I'll move the Command.js in Positron rewriting it in ES5


Bidders not moving to "Last Round" after end of bid

The latest bidders is not moving to "Last Round" after end of bid, this issue when "max_roi" turned on.

Hi, the problem seems resolved when API enabled, closed topic


Sorting by price should use less than or equal

Right now assertion checking for sorting by price on category page is checking using "less than". But it should use "less than or equal" to cover situations where you have 2 products with the same price

CI failures seems unrelated.


Ensure specifying directory input works

Several issues were found, in particular regarding git-rm, which can remove working directory and for linux and mac, just re-creating it does not suffice; it is necessary to chdir into the directory again so it points to a valid directory entry in the filesystem. A matter of chdir "$(pwd)".
As far as tests went, it is working fine now either for new branches and existing ones, creating pull requests.

This issue has been transferred to retypeapp/action-github#2.


[3.0] Fix bsc#1072242: Use keyboard layout from admin installation.

The keyboard layout the user was using during the installation will be
used in the autoyast generated to bootstrap additional nodes.
Requires kubic-project/caasp-container-manifests#195

 Bug 1072242 - Keyboard selection not reflected in AutoYast file


Revert "Correct trigger definition"

This reverts commit b7f682ae5581f85ec94e4326f6ad0837a346f435.
The trigger was on insert to the history table, not the main
table. Triggering on delete to the history table doesn’t make
sense and it’ll always error because the function uses NEW.
The original example is a little unclear. It records the user
who caused a history entry to be created, so it is saving which
user was responsible for deleting the old state of the record,
rather than recording only when a user deletes a record with a
DELETE on the main table.

Thank you for merging this PR!


MSIINSTALLPERUSER and INSTALLDIR not working for MSI

Originally repoted in https://github.com/microsoft/vscode-java-installer/issues/53#issuecomment-683832774
Run the Adopt MSI with below options:

MSIINSTALLPERUSER=1
INSTALLDIR=C:\Users\admin\AppData\Local\Programs\AdoptOpenJDK

But the JDK was wrongly installed into "C:\Program Files\AdoptOpenJDK\jdk-<IP_ADDRESS>-hotspot"
...
MSI (s) (68:8C) [00:05:11:832]: Command Line: MSIINSTALLPERUSER=1 INSTALLDIR=C:\Users\admin\AppData\Local\Programs\AdoptOpenJDK ADDLOCAL=FeatureJavaHome,FeatureEnvironment,FeatureJarFileRunWith REBOOTPROMPT=S CURRENTDIRECTORY=C:\Users\admin\AppData\Local\Temp\1fIPpovDGCeTmgxsgBFJybvqTBE CLIENTUILEVEL=2 CLIENTPROCESSID=2070612
...
MSI (s) (68:8C) [00:05:30:468]: Doing action: PerMachineInstall
MSI (s) (68:8C) [00:05:30:468]: Note: 1: 2205 2:  3: ActionText
Action ended 00:05:30: FileCost. Return value 1.
MSI (s) (68:8C) [00:05:30:469]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\Program Files\AdoptOpenJDK\jdk-<IP_ADDRESS>-hotspot\'.
Action start 00:05:30: PerMachineInstall.
MSI (s) (68:8C) [00:05:30:469]: Skipping action: PerUserInstall (condition is false)
...

full logs:
AdoptOpenJDK-MSI.log

Does the same apply with non admin user ?

MSI (s) (68:8C) [00:05:30:469]: Skipping action: PerUserInstall (condition is false)

I can't say more, the install path is ignored because the installer switch to PerMachineInstall

This is the critical line:
MSI (s) (68:8C) [00:05:11:832]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.

It's like with https://github.com/AdoptOpenJDK/openjdk-installer/issues/196. MSIs aren't a great fit for multiple installations.

@aahlenst About the critical line you mentioned, is it saying the user has installed AdoptOpenJDK before, and it is a) exact the same version 11.0.8, b) per machine ?
From the PATH I can say the user did have Oracle JDK installed, but not sure about AdoptOpenJDK (because AFAIK Adopt will modify PATH).
PATH: C:\Program Files (x86)\Google\Chrome\Application;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Python\Python3.8.5\Scripts;C:\Python\Python3.8.5\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\MinGW\bin;C:\Users\admin\AppData\Local\Microsoft\WindowsApps;C:\Users\admin\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\admin\AppData\Roaming\npm;C:\Program Files\Docker Toolbox;C:\Program Files\Docker Toolbox;C:\Program Files\Docker Toolbox;D:\soft\IntelliJ IDEA Community Edition 2020.2\bin;;C:\Program Files\Redis;

I think @Rupeshiya would be willing to help if you need more details to figure out why it happened.

a) exact the same version 11.0.8
not the exact the same see below

see https://github.com/AdoptOpenJDK/openjdk-installer/blob/master/wix/Build.OpenJDK_generic.cmd
L172-184
SET SOURCE_TEXT_GUID=!PRODUCT_CATEGORY!-!PRODUCT_MAJOR_VERSION!-!PLATFORM!-!PACKAGE_TYPE!
=>
PRODUCT_CATEGORY=JRE vs JDK
PRODUCT_MAJOR_VERSION=11 vs others
PLATFORM=x86 vs x64
PACKAGE_TYPE=hotspot vs openj9
b) per machine ?
yes

@Eskibear any other question ? can we close it ?

@Eskibear any other question ? can we close it ?

Thanks for the clarification.

Thanks for the clarification.


DoTestCleanUp fails if the VM is not in running state

DoTestCleanUp expects the vm to be running, but the test case might leave the vm in another state on purpose or it can just fail.
If this method: DoTestCleanUp is run, the vms should be put on running state (or at least try to set them on running state).
Here is the problem:
https://github.com/LIS/LISAv2/blob/a6755bf517d52c1f869db4af24c8757cb9501db4/Libraries/Test-Framework.psm1#L530
The same workflow should be followed:
https://github.com/LIS/LISAv2/blob/a6755bf517d52c1f869db4af24c8757cb9501db4/Libraries/Test-Framework.psm1#L534

Internally recorded.


The call to twopass_out() after LimitReached is emitted by receive_packet() doesn't contain data

https://github.com/xiph/rav1e/blob/8f273bcbde77e5f3711138a57c13dec9dc793973/src/bin/rav1e.rs#L170-L180
This chunk is never executed when it should. twopass_out() should return the final version of the buffer with the updated header, but it doesn't. Can be reproduced with the C API as well (see ffmpeg wrapper).

Not setting the bitrate produces this sort of erratic behavior, we are discussing how to make it impossible with the minimal API change, but it is not how you are supposed to use the rate control.
(this after I spent most of the day scanning through the commits to find a known-working one)


New way of naming component or zipped package...

Hi all,
I have used Atom for a few weeks and really love it. I found that there is a portable version of Atom to use in the USB sticks (at Sourceforge). I copied the files in ~ .atom folder the respective folder in the USB so that all plugins are available to use for the portable version.
However I have encountered problems:

Plugins sometime have filename/path exceed 256 chars. Using explorer copy function doesn't work.
Update of plugins, for both of installed and portable version sometime took too long to complete.

My question are:
Is there any kind of "enhance proposal" or standard to make Atom more convenient in handling components/plugins? For example, all plugin are packed in a zip-based archives so that installation and update of these stuffs become more convenient and faster. It also make disk access faster someway because normally there are too many files in the plugin folder.
Thanks!
TN

There is currently no way to "make Atom more convenient in handling [packages]", though the next Atom beta (1.10.0) will have an updated version of npm which should fix the path length issue.  That update of npm might also make package updating faster.
Also, we're trying to control the amount of Issues that we have to triage and track. For general questions, the Atom message board is where you'll probably be able to find answers faster.


Smart selector - Person - new person

Please reduce space. It looks like the labels are attached to the wrong field. (This is from Comprehensive task)

This is an unusual behavior and not the correct space. Where is the context of this to look if is inheriting a class

Sorry, I didnt saw the comment at the button. looking


plotTracks() sizes error when trackList contains OverlayTrack()

When the trackList argument of the plotTracks function contains an OverlayTrack the size argument throws an error.
This issue did not occur with R 4.1 and Gviz 1.38.3.
library(Gviz)

set.seed(0)
gr1 <- GRanges(seqnames = "chrI", ranges = IRanges(start = 1:10, width = 1), score = sample(x = 1:10 / 10, size = 10, replace = TRUE))
gr2 <- GRanges(seqnames = "chrI", ranges = IRanges(start = 1:10, width = 1), score = sample(x = 1:10 / 10, size = 10, replace = TRUE))
gr3 <- GRanges(seqnames = "chrI", ranges = IRanges(start = 1:10, width = 1), score = sample(x = 1:10 / 10, size = 10, replace = TRUE))

dt1 <- DataTrack(range = gr1, type = "l", name = "Track 1")
dt2 <- DataTrack(range = gr2, type = "l", col = "blue", name = "Track 2")
dt3 <- DataTrack(range = gr3, type = "l", col = "red", name = "Track 3")

plotTracks(trackList = list(dt1, dt2, dt3), chromosome = "chrI", sizes = c(0.2, 0.3, 0.5))

plotTracks(trackList = list(OverlayTrack(trackList = list(dt1, dt2)), dt3), chromosome = "chrI", sizes = c(0.7, 0.3))
# Error in .setupTextSize(list(tmpThisTrack[[1]]), sizes, title.width, spacing = innerMargin) :
#   The 'sizes' vector has to match the size of the 'trackList'.

sessionInfo()
# R version 4.2.0 (2022-04-22)
# Platform: x86_64-pc-linux-gnu (64-bit)
# Running under: Ubuntu 18.04.6 LTS
#
# Matrix products: default
# BLAS:   /usr/lib/x86_64-linux-gnu/blas/libblas.so.3.7.1
# LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.7.1
#
# locale:
#   [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=en_US.UTF-8
# [4] LC_COLLATE=en_US.UTF-8     LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
# [7] LC_PAPER=en_US.UTF-8       LC_NAME=C                  LC_ADDRESS=C
# [10] LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
#
# attached base packages:
#   [1] grid      stats4    stats     graphics  grDevices utils     datasets  methods   base
#
# other attached packages:
#   [1] Gviz_1.40.0          GenomicRanges_1.48.0 GenomeInfoDb_1.32.1  IRanges_2.30.0
# [5] S4Vectors_0.34.0     BiocGenerics_0.42.0

Hi @robert-gnuegge,
Thanks for reporting, fixed both in devel and release.


Added the ability to configure braces

Previous variants could only use standard braces ({}) Now other braces are possible such as (<>, ::, &&)
It is up to the user to check whether the chosen braces conflict with the remaining syntax.

@akx What do you think is the best way to set the braces configuration?

We could send it through the generators and samplers' constructors, but that seems like it would be easy to forget to add.
We could make it a required argument but that might make it cumbersome to instantiate the classes.
Perhaps a global configuration object, although that feels a little messy

thoughts?

@akx What do you think is the best way to set the braces configuration?

I think we'll need a general Context style object á la Jinja2 sooner or later anyway - so not a global object, but a single object containing all sorts of configuration that can be passed around.


ENYO-442: Utilize method for temporarily suppressing events.

Issue
We are currently using a pair of silence and unsilence calls to temporarily suppress events in situations where it is either required (to prevent undefined object errors) or helpful (to prevent unnecessary execution of change handlers). We've added a muzzle function that can be utilized now.
Fix
moon.DatePicker has been updated to use the muzzle function, while we've added the use of muzzle for moon.TimePicker to prevent unnecessary execution of change handlers.
Notes
This PR is dependent on https://github.com/enyojs/enyo/pull/922.
Enyo-DCO-1.1-Signed-off-by: Aaron Tam<EMAIL_ADDRESS>

@aarontam  - should we close this PR since the Jira is closed?  Thanks

@lishammel Yep let's do that. Closing for now as this is not needed.


[Feature request] Import and Export of character presets for 1.5

Regarding this post and the request to file a new issue:
https://github.com/PixelRick/CyberpunkSaveEditor/issues/5#issuecomment-1050359924

@vulpes9 Can you please open a new issue for this ? (Also if you can tell a bit more about it: Has CyberCAT got this feature ? What data a "character preset" should include ?)

The way I understand it, CyberCAT offers de- and re-compression of saves and can parse data of them:
https://github.com/WolvenKit/CyberCAT
This was the GUI offshot:
https://github.com/Deweh/CyberCAT/tree/dev
https://github.com/Deweh/CyberCAT-SimpleGUI
Both are in development hell since Apr/Aug 2021 respectively.
Characters are im- and exported in JSON arrays alike:
https://github.com/Deweh/CyberCAT-SimpleGUI/blob/master/CP2077SaveEditor/Resources/FemaleDefault.preset
Basically I am asking to mod the app clipboard to allow exporting characters (as files) without having to share the whole save. I don't know your stance about the Nexus, but I guess for ease of access having your tool would mean more work, but lots of happy people. So hold that thought, I'll gladly download anywhere. Github is fine ;)
https://forums.nexusmods.com/index.php?showtopic=9475693/#entry105842433
It would feel really good knowing there is at least one up-to-date tool being able to handle presets again without damaging the saves, in case CDPR changes the serialization (again).
We are glad to have a smart mirror redscript mod that gives access to slow manual character editing slider by slider, but it would be much faster for sharing to have these presets back as file:
{"DataExists":true,"Unknown1":0,"UnknownFirstBytes":"AwAAAAAA","FirstSection":{"AppearanceSections":[{"SectionName":"TPP","MainList":[{"Hash":11127614498395143143,"FirstString":"h0_000_pwa__basehead__03_ca_senna","SecondString":"skin_type_01","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16043278657831145316,"FirstString":"he_000_pwa__basehead__15_gradient_light_blue","SecondString":"eyes_color","TrailingBytes":"AAAAAAAAAAA="},{"Hash":5580371224339221950,"FirstString":"heb_pwa__basehead__02_blonde","SecondString":"eyebrows_color7","TrailingBytes":"AAAAAAAAAAA="},{"Hash":5491315604699331944,"FirstString":"h0_000_pwa__scars_01__scar_01","SecondString":"scars","TrailingBytes":"AAAAAAAAAAA="},{"Hash":17416343193870066273,"FirstString":"i0_000_pwa__earring__03_black","SecondString":"piercings_09","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4335264894338256315,"FirstString":"female_ht_000__basehead","SecondString":"teeth","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7841373126957531331,"FirstString":"hx_000_pwa__morphs_makeup_freckles_01__03_light_brown","SecondString":"makeupCheeks_02","TrailingBytes":"AAAAAAAAAAA="},{"Hash":10193113560071498966,"FirstString":"hx_000_pwa__basehead_pimples_01__brown_01","SecondString":"makeupPimples_03","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[{"FirstString":"eyes","SecondString":"h111","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"nose","SecondString":"h032","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"mouth","SecondString":"h113","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"jaw","SecondString":"h064","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"ear","SecondString":"h135","TrailingBytes":"AAAAAAAAAAA="}]},{"SectionName":"FPP","MainList":[{"Hash":10731250262594030950,"FirstString":"n0_000_pwa_fpp__neck__03_ca_senna","SecondString":"neck","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"hairs","MainList":[{"Hash":12652197010004652555,"FirstString":"01_blonde_platinum","SecondString":"hair_color14","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"character_customization","MainList":[{"Hash":11127614498395143143,"FirstString":"h0_000_pwa__basehead__03_ca_senna","SecondString":"skin_type_01","TrailingBytes":"AAAAAAAAAAA="},{"Hash":12652197010004652555,"FirstString":"01_blonde_platinum","SecondString":"hair_color14","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16043278657831145316,"FirstString":"he_000_pwa__basehead__15_gradient_light_blue","SecondString":"eyes_color","TrailingBytes":"AAAAAAAAAAA="},{"Hash":5580371224339221950,"FirstString":"heb_pwa__basehead__02_blonde","SecondString":"eyebrows_color7","TrailingBytes":"AAAAAAAAAAA="},{"Hash":5491315604699331944,"FirstString":"h0_000_pwa__scars_01__scar_01","SecondString":"scars","TrailingBytes":"AAAAAAAAAAA="},{"Hash":17416343193870066273,"FirstString":"i0_000_pwa__earring__03_black","SecondString":"piercings_09","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4335264894338256315,"FirstString":"female_ht_000__basehead","SecondString":"teeth","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7841373126957531331,"FirstString":"hx_000_pwa__morphs_makeup_freckles_01__03_light_brown","SecondString":"makeupCheeks_02","TrailingBytes":"AAAAAAAAAAA="},{"Hash":10193113560071498966,"FirstString":"hx_000_pwa__basehead_pimples_01__brown_01","SecondString":"makeupPimples_03","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[{"FirstString":"eyes","SecondString":"h111","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"nose","SecondString":"h032","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"mouth","SecondString":"h113","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"jaw","SecondString":"h064","TrailingBytes":"AAAAAAAAAAA="},{"FirstString":"ear","SecondString":"h135","TrailingBytes":"AAAAAAAAAAA="}]}]},"SecondSection":{"AppearanceSections":[{"SectionName":"holstered_default_tpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4185585899683046648,"FirstString":"a0_000_pwa_base__nails_grey_light","SecondString":"nails_color_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":18255181641299694784,"FirstString":"a0_000_pwa_base__03_ca_senna","SecondString":"h_default_arms_colors_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_default_fpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7789881357550050267,"FirstString":"a0_000_pwa_fpp__nails_grey_light","SecondString":"nails_color_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":1951233403238964808,"FirstString":"a0_000_pwa_base__03_ca_senna","SecondString":"h_default_arms_colors_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_strong_tpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":17608390161697568906,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"h_strong_arms_colors_base_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":17114838716404445585,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"h_strong_arms_colors_cyberware01_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_strong_fpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16990187420757166753,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"h_strong_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":11522684623843550794,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"h_strong_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"unholstered_strong","MainList":[{"Hash":6349005316216539408,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"u_strong_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":10258929172936258939,"FirstString":"female_a0_000_strong_arms__03_ca_senna","SecondString":"u_strong_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_nanowire_tpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4185585899683046648,"FirstString":"a0_000_pwa_base__nails_grey_light","SecondString":"nails_color_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":15905102067097217885,"FirstString":"female_a0_000_personal_link__03_ca_senna","SecondString":"h_monowire_arms_colors_base_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_nanowire_fpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7789881357550050267,"FirstString":"a0_000_pwa_fpp__nails_grey_light","SecondString":"nails_color_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":1306664051472799422,"FirstString":"female_a0_000_personal_link__03_ca_senna","SecondString":"h_monowire_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"unholstered_nanowire","MainList":[{"Hash":7789881357550050267,"FirstString":"a0_000_pwa_fpp__nails_grey_light","SecondString":"nails_color_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":10615025493550468539,"FirstString":"female_a0_000_personal_link__03_ca_senna","SecondString":"u_monowire_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"character_customization","MainList":[{"Hash":4185585899683046648,"FirstString":"a0_000_pwa_base__nails_grey_light","SecondString":"nails_color_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":18255181641299694784,"FirstString":"a0_000_pwa_base__03_ca_senna","SecondString":"h_default_arms_colors_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"personal_link_simple","MainList":[{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"personal_link_advanced","MainList":[{"Hash":10365434196603567427,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_advanced","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_launcher_tpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4185585899683046648,"FirstString":"a0_000_pwa_base__nails_grey_light","SecondString":"nails_color_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":8176614337494735084,"FirstString":"female__03_ca_senna","SecondString":"h_launcher_arms_colors_base_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":17371119636816561915,"FirstString":"female__03_ca_senna","SecondString":"h_launcher_arms_colors_cyberware01_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_launcher_fpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7789881357550050267,"FirstString":"a0_000_pwa_fpp__nails_grey_light","SecondString":"nails_color_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":2276572548010059327,"FirstString":"female__03_ca_senna","SecondString":"h_launcher_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":11950704061544772736,"FirstString":"female__03_ca_senna","SecondString":"h_launcher_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"unholstered_launcher","MainList":[{"Hash":5126128806554524844,"FirstString":"female__03_ca_senna","SecondString":"u_launcher_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7745136095954041807,"FirstString":"female__03_ca_senna","SecondString":"u_launcher_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":121866437883897908,"FirstString":"a0_000_pwa_base__nails_beige","SecondString":"u_launcher_nails_color","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_mantis_tpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4185585899683046648,"FirstString":"a0_000_pwa_base__nails_grey_light","SecondString":"nails_color_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":15020998300600289572,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"h_mantis_arms_colors_base_tpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":15785262664659153011,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"h_mantis_arms_colors_cyberware01_tpp","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"holstered_mantis_fpp","MainList":[{"Hash":13328453398705956150,"FirstString":"holstered_arms_data_female","SecondString":"holstered_data","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7789881357550050267,"FirstString":"a0_000_pwa_fpp__nails_grey_light","SecondString":"nails_color_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":15768631978898956071,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"h_mantis_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":7562701651359576520,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"h_mantis_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":16407952206209645574,"FirstString":"female_a0_000_personal_link","SecondString":"personal_link_simple","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"unholstered_mantis","MainList":[{"Hash":2747349617996698706,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"u_mantis_arms_colors_base_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":2853248466956479269,"FirstString":"female_a0_000_mantisblade__03_ca_senna","SecondString":"u_mantis_arms_colors_cyberware01_fpp","TrailingBytes":"AAAAAAAAAAA="},{"Hash":4288886144569452246,"FirstString":"a0_000_pwa_base__nails_beige","SecondString":"u_mantise_nails_color","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]}]},"ThirdSection":{"AppearanceSections":[{"SectionName":"FPP_Body","MainList":[{"Hash":14920680558686302904,"FirstString":"t0_000_pwa_fpp__03_ca_senna","SecondString":"fpp_body_color","TrailingBytes":"AQAAAAEAAAA="},{"Hash":18052529923140282516,"FirstString":"t0_000_pwa_fpp__03_ca_senna","SecondString":"fpp_body_color_censored","TrailingBytes":"AQAAAAAAAAA="},{"Hash":1270113483780776886,"FirstString":"scars_pwa_001__03_ca_senna","SecondString":"body_scars_01","TrailingBytes":"AAAAAAAAAAA="},{"Hash":18171731966644557866,"FirstString":"female_001","SecondString":"underpants","TrailingBytes":"AQAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"TPP_Body","MainList":[{"Hash":13876824607332389147,"FirstString":"t0_000_pwa_base__03_ca_senna","SecondString":"body_color","TrailingBytes":"AQAAAAEAAAA="},{"Hash":6124762102644877205,"FirstString":"t0_000_pwa_base__03_ca_senna","SecondString":"body_color_censored","TrailingBytes":"AQAAAAAAAAA="},{"Hash":17949477145130904651,"FirstString":"female_i0_002_base__nipple__03_ca_senna","SecondString":"nipples_03","TrailingBytes":"AQAAAAEAAAA="},{"Hash":1270113483780776886,"FirstString":"scars_pwa_001__03_ca_senna","SecondString":"body_scars_01","TrailingBytes":"AAAAAAAAAAA="},{"Hash":18171731966644557866,"FirstString":"female_001","SecondString":"underpants","TrailingBytes":"AQAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"character_creation","MainList":[{"Hash":13876824607332389147,"FirstString":"t0_000_pwa_base__03_ca_senna","SecondString":"body_color","TrailingBytes":"AQAAAAEAAAA="},{"Hash":6124762102644877205,"FirstString":"t0_000_pwa_base__03_ca_senna","SecondString":"body_color_censored","TrailingBytes":"AQAAAAAAAAA="},{"Hash":17949477145130904651,"FirstString":"female_i0_002_base__nipple__03_ca_senna","SecondString":"nipples_03","TrailingBytes":"AQAAAAEAAAA="},{"Hash":1270113483780776886,"FirstString":"scars_pwa_001__03_ca_senna","SecondString":"body_scars_01","TrailingBytes":"AAAAAAAAAAA="},{"Hash":3178724759333055970,"FirstString":"i0_000_pwa_base__genitals_none__03_ca_senna","SecondString":"genitals_04","TrailingBytes":"AQAAAAEAAAA="},{"Hash":18171731966644557866,"FirstString":"female_001","SecondString":"underpants","TrailingBytes":"AQAAAAAAAAA="},{"Hash":6997184798500539635,"FirstString":"l0_000_pwa_base__03_ca_senna","SecondString":"lifted_feet","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[{"FirstString":"breast","SecondString":"t0_000_wa_base__full_breast_small","TrailingBytes":"AQAAAAEAAAA="}]},{"SectionName":"genitals","MainList":[{"Hash":3178724759333055970,"FirstString":"i0_000_pwa_base__genitals_none__03_ca_senna","SecondString":"genitals_04","TrailingBytes":"AQAAAAEAAAA="}],"AdditionalList":[]},{"SectionName":"breast","MainList":[],"AdditionalList":[{"FirstString":"breast","SecondString":"t0_000_wa_base__full_breast_small","TrailingBytes":"AQAAAAEAAAA="}]},{"SectionName":"lifted_feet","MainList":[{"Hash":6997184798500539635,"FirstString":"l0_000_pwa_base__03_ca_senna","SecondString":"lifted_feet","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]},{"SectionName":"flat_feet","MainList":[{"Hash":5979156899619118120,"FirstString":"l0_000_pwa_base__03_ca_senna","SecondString":"flat_feet","TrailingBytes":"AAAAAAAAAAA="}],"AdditionalList":[]}]},"StringTriples":[{"FirstString":"FPP_Body","SecondString":"FPP_Body","ThirdString":"TPP_Body"},{"FirstString":"holstered_default","SecondString":"holstered_default_fpp","ThirdString":"holstered_default_tpp"},{"FirstString":"holstered_strong","SecondString":"holstered_strong_fpp","ThirdString":"holstered_strong_tpp"},{"FirstString":"holstered_nanowire","SecondString":"holstered_nanowire_fpp","ThirdString":"holstered_nanowire_tpp"},{"FirstString":"holstered_launcher","SecondString":"holstered_launcher_fpp","ThirdString":"holstered_launcher_tpp"},{"FirstString":"holstered_mantis","SecondString":"holstered_mantis_fpp","ThirdString":"holstered_mantis_tpp"}],"Strings":["blonde_platinum","Buzz"]}

Thanks for having voiced interest in it! Hope you can find the time if real life allows it.

Thanks for having opened a new issue.
This looks like a section that is fully parsed and accessible already in one of the tabs of the editor.
Thus, it would only require the json import/export via file/clipboard.
I will add this to my roadmap.

Oh yes this is great! I wonder though if previous CyberCAT .preset files will continue working. If not maybe a different extension should be picked. Just a consideration, I'll go back to silent lurking in the meantime.

The current .preset files have unparsed bytes. It's still possible to code a special import.. just more work ^^

I guess this can be closed.

Eh, not longer needed ?

More like preventing extra work ;)
There are several other mods now that do this directly on the mirror feature ingame using redscript
https://www.nexusmods.com/cyberpunk2077/mods/3850
The mod saves characters as plain ASCII textfiles. Since this directly moved sliders it has a high chance of being cross version compatible for a long time, even if the save format changes again with the expansion.
It is unlucky that this came out 2 days after I opened my issue! But I felt like making sure it won't cause extra work.

Have a great evening sir.

Thanks! You too and happy to check back whenever they drop the new content next year ;)
Else there will always be the now announced next game in the Cyberpunk universe. I'm confident it will have a better launch on new/current gen. Be it this or UE5.


New id attribute for glaciers

This adds a new id attribute to glaciers. By default this is set to a random 5 character sequence but can be specified at init.
Also corrected some spelling mistakes.
Closes #187

Thanks @Holmgren825 ! Much appreciated as always


Updated EmberJS 5.4

The update will be done in two stages. At first the project will be updated to Ember V4.12 and after that the project will be updated to Ember V5.4.
The Update to Ember V4.12 is almost done. The update is being worked on on the 1.4.0.dev-branch in the Frontend project.