text:
add more unit test

Signed-off-by: kevin xu cming.xu@gmail.com

Codecov Report

Merging #461 into master will decrease coverage by 0.03%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master     #461      +/-   ##
==========================================
- Coverage   43.12%   43.09%   -0.04%
==========================================
  Files          27       34       +7
  Lines       11815    12130     +315
==========================================
+ Hits         5095     5227     +132
- Misses       5443     5612     +169
- Partials     1277     1291      +14

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 8a54e6f...190fb30. Read the comment docs.

authors: cmingxu codecov-io

repo: Dataman-Cloud/swan


text:
Refactor test data

It seems like the test data including whole period of results for each indicator is ready to be used. If it is correct, I'm planning to write unit tests using xlsx files in each indicator directory. Is it available now?

https://github.com/DaveSkender/Stock.Indicators/pull/553

Can I know the reason why you are not using them?

Can I know the reason why you are not using them?

I tend to clean up the Excel files for formatting so they tend to not have a stable layout that might break the test data importer.  Since I tend to do TDD, it's not unusual for me to come back and revise the reconcile calculations throughout the development process.
I do actually review the full results and compare them.  In the spreadsheets, you'll see manual calcs (blue table) and indicator output (yellow); so essentially I am already doing a full compare.
It makes the whole test much slower overall to import results.  CSV import is much faster than Excel and JSON; however, CSV is still a lot slower than sampling.  Sampling is still a statistically acceptable approach.
I'm lazy and it's a low ROI effort.  There are several alternate test scenarios for each indicator and it could be a lot of work to switch them over, with only a little added benefit.  It would have been much easier to start with that approach.

Your words make sense. I thought using spreadsheet having whole period of results can make writing unittest faster, without losing its original goal.
Anyway, I'll put off switching it.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Crash-protocol witness for XCGLogger.DestinationProtocol.process(logDetails: XCGLogger.LogDetails) -> () in conformance XCGLogger.BaseDestination : XCGLogger.DestinationProtocol in XCGLogger

Crash in DestinationProtocol.process. Can anyone check this?
XCGLogger
protocol witness for XCGLogger.DestinationProtocol.process(logDetails: XCGLogger.LogDetails) -> () in conformance XCGLogger.BaseDestination : XCGLogger.DestinationProtocol in XCGLogger :0
XCGLogger
XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.String, fileName: Swift.String, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () XCGLogger.swift:335
XCGLogger
XCGLogger.XCGLogger.logln(: XCGLogger.XCGLogger.Level, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any], closure: () -> Any?) -> () XCGLogger.swift:313
XCGLogger
merged XCGLogger.XCGLogger.verbose(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> ()
XCGLogger
XCGLogger.XCGLogger.debug(: @autoclosure () -> Any?, functionName: Swift.StaticString, fileName: Swift.StaticString, lineNumber: Swift.Int, userInfo: [Swift.String : Any]) -> ()
Sample
Sample.SyncManager.getLine(line: Swift.String) -> Swift.String SyncManager.swift:759

Might be the same bug we've seen:

authors: everlof manojverma-cs

repo: DaveWoodCom/XCGLogger

license: mit

license_source: bigquery


text:
Setting Up Chinese proxy

What would I set my environment variable to in order to get a chinese proxy? Running it straight from my command prompt gives: API returned error (The current country is blocked by the API); response body: {"code":2119, "msg":"user_ip_country 美国"}
Which is expected, but there's nothing in the example about how to set up a proxy. So what would I set my "PROXY" environment variable to?

On Linux you can do the following for setting the environment variable when running the example script:
PROXY="socks5://ip:host" python example.py

supposing the proxy is a socks5 proxy, otherwise change the protocol to socks4, https or whatever

repo: David-Lor/python-qqddm

license: ISC


text:
MD033: Organizing information with collapsed sections

According to github docs: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections
I use:
<details><summary>
Example (Click to expand):
</summary>

But I get error:
MD033/no-inline-html: Inline HTML [Element: details]

What should I do?

If you want to include inline HTML in your Markdown, you should disable the no-inline-html rule. The README shows multiple ways to do so.

I don't think the CommonMark specification (or GFM extensions) offers a way to do that.

There are many things that can be done in HTML that cannot be done in Markdown. If you want to do many of them, you can disable this rule. If you want to do some of them, you can customize the rule to allow the relevant elements: https://github.com/DavidAnson/markdownlint/blob/main/doc/md033.md

The rule exists to block HTML and keep Markdown content pure - for people who want that. The specific scenario raised above does not seem to be more special than any other. In fact, this issue may be the first time it has come up.

authors: DavidAnson Obegg

repo: DavidAnson/markdownlint


text:
blanks-around-tables (like MD031 and MD032 for fences/lists)

Original issue for context: https://github.com/DavidAnson/vscode-markdownlint/issues/43

An incomplete babelmark2 reproduction of
# 1

- aa
  | key | value
  |-----|-------
  | 1   | xx
  | 2   | yy
- bb

  | key | value
  |-----|-------
  | 1   | xx
  | 2   | yy

- cc
    | key | value
    |-----|-------
    | 1   | xx
    | 2   | yy
- dd

    | key | value
    |-----|-------
    | 1   | xx
    | 2   | yy

- ee

This was after bumping into blackfriday rendering issues which I need to wait for our internal Go lang based git repository has been updated to the most recent blackfriday so I can check how it behaves now.

Example from Microsoft Team Foundation Server, rendering markdown file.
Code:
#### 0x0209 [1] Offset

Request:
| Field    | Type    | Meaning         |
| :------- | :------ | :-------------- |
| address  | uint8_t | Device address. |
| standard | float   | Standard value. |

Answer: empty.

#### 0x020a [1] Scale

Request:

| Field    | Type    | Meaning         |
| :------- | :------ | :-------------- |
| address  | uint8_t | Device address. |
| standard | float   | Standard value. |

Answer: empty.

Screenshot:

0x0209 [1] Offset
Request:

Field
Type
Meaning

address
uint8_t
Device address.

standard
float
Standard value.

Answer: empty.
0x020a [1] Scale
Request:

Field
Type
Meaning

address
uint8_t
Device address.

standard
float
Standard value.

Answer:

authors: A-2f DavidAnson jpluimers riuson


text:
Firebase backend

*Added environment variables for the firebase configuration properties
*Created config folder under MENTANA-backend/src for the Firebase-config.js file
*implemented the firebase configuration and initialized it
*Created middleware folder under MENTANA-backend/src
*Created the class Middleware with its decodeToken function
*under MENTANA-backend/src/interfaces/http/server.js instantiated the middleware class and applied the decodetoken function as a middleware to access to the information which for now if succeed will show the message "Hello World"
Middleware tested with a valid token from the frontEnd, works as expected.

the check and is failing in the github action is due to the env variables for the firebase configuration is not added to the github actions variables

source: gharchive/pull-request

repo: Davoyandun/MENTANA-backend

license: MIT


text:
Small path middleware change

update-in can take extra args

We only take patches against the develop branch.
Given how tiny the change is, I'll just manually do it across on develop.
**But thanks for the tweak. **


text:
Fixed doc files from getMintingInfo to getMiningInfo

What kind of PR is this?:

/kind feature
What this PR does / why we need it:
Changed various .md files that uses getMintingInfo() in code examples.
Which issue(s) does this PR fixes?:

Fixes #230
Additional comments?:
This PR does not change the docs in testcontainers as the containers do not have getMiningInfo() as a shorthand method like they have with getMintingInfo(). An issue has been created to address this. #376

/kind docs

authors: aikchun fuxingloh

repo: DeFiCh/jellyfish


text:
Support more Resolutions

Currently only supported 1280x720 in none fullscreen

Feature has been added


text:
Question about switches

I've been trying to get all the different switches to work in my MangaRack.txt file...
How do I utilise the --source command for a file called MangaList.txt?
I've tried -s E:\Manga\MangaList.txt -s MangaList.txt
Do I need to put the output in front of EACH URL for EACH Manga series?
ie.
--output E:\Manga URL
--output E:\Manga URL
--output E:\Manga URL
. . . etc

or can I state the address for all URL's in a text file so i don't have to repeat the directory each time?
ie.
--output E:\Manga
URL
URL
. . . etc

is there anywhere I can go to learn this stuff by myself? Any help in this is greatly appreciated, I've got a big library and I'm considering splitting it up across multiple directories.

Hi, I learned by trying too. You can add the switch at the start of each url, but this is useful only for certian switches (i.e. start by chapter/volume).
It's easier to add the switches to the bat file which starts the operation. This can be done in "cascade".
In my case I have a bat file which check for updates and then starts other batches for each alphabet letter.
Like this:
call npm update -g mangarack
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\Download#.bat
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\Download~KissManga.bat
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\Download~MangaFox.bat
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\Download~Manhwa.bat
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\DownloadA.bat
call H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\DownloadB.bat
These batches are like this:
call %AppData%\npm\mangarack --generalize --source H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA-\Liste\A.txt --output H:#ARCHIVIO\BIBLIOTECA\MANGA#MANGA\A
each list (by letter) is like:
//ONGOING
url1
-chapter xx url2
url3
//COMPLETE
#url4
This way I have different folders for each letter, I'm able to update only a certian list and to keep things separate and clean.
I'm sure there would be better ways to do it, but these are my two cents. Hope it can help :)

I believe that you are using the Windows .bat helper file. Open it and you will see the following line:
call %AppData%\npm\mangarack

This means that MangaRack runs without arguments, and thus uses a source file for batch-mode. Each line in the source file is handled as if it was a command line argument, which is why you can use switches on each line (e.g. -v 2 http://...). But, the line from the file is actually executed as a joined line of the real command line arguments and the ones from the file. Imagine you have this in your .bat file:
call %AppData%\npm\mangarack --output F:\Manga

And this in your batch file:
-c 100 http://mangafox.me/manga/fairy_tail/
-c 150 http://mangafox.me/manga/skip_beat/

Then this is executed as:
--output F:\Manga -c 100 http://mangafox.me/manga/fairy_tail/
--output F:\Manga -c 150 http://mangafox.me/manga/skip_beat/

You can see that the arguments from the .bat file are prepended to each line from the source file. So if you want to affect everything in your source file, that's the way to go. Then, as @XellossMetallium mentioned, you can also chain multiple mangarack invocations for different settings with different batch files.
Very powerful stuff right there. Does this help you? :-)

Closing this for now. Feel free to open if there are further questions.

authors: Deathspike XellossMetallium damidget


text:
feat(@vtmn/svelte): add VtmnDropdown component

Refer to #1051
Based on the work of @jb-thery
Changes description

This P.R adds the Svelte dropdown component
Context

Related issue #364
Checklist

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on related showcases.
[x] If it includes design changes, please ask for a review with a core team designer.

Does this introduce a breaking change?

No

Other information

Need to update code, refer A11y -> #1113

Need to update code, refer A11y -> #1113

What do you mean @Tlahey by this comment?

@Tlahey thanks! Is it ok for you? If yes we will take this PR ready for review again :)

@lauthieb yes it's good for me :)

FYI : add max-height 260px to fit 5 items without scroll on the dropdown

@jb-thery & @Tlahey , AWESOME!! Thanks :tada:

authors: Tlahey lauthieb

repo: Decathlon/vitamin-web


text:
Fix TX frame length parameter comments in driver

TX frame length parameter does not include the CRC length from auto-FCS Transmission
Clarify maximum with auto-FCS Transmission

Thanks @Beetix, I've also updated this in uwb-core which replaces this repo as of today.

authors: Beetix ncasaril


text:
Can't kekulize mol.

When I ran the code below（same as the demo in retrosynthesis tutorial）
from torchdrug import data, datasets, utils
from torchdrug.utils import plot
from torchdrug import core, models, tasks

synthon_dataset = datasets.USPTO50k("~/data", as_synthon=True,
                                    node_feature="synthon_completion",
                                    kekulize=True)
torch.manual_seed(1)
synthon_train, synthon_valid, synthon_test = synthon_dataset.split()
synthon_model = models.RGCN(input_dim=synthon_dataset.node_feature_dim,
                            hidden_dims=[256, 256, 256, 256, 256, 256],
                            num_relation=synthon_dataset.num_bond_type,
                            concat_hidden=True)
synthon_task = tasks.SynthonCompletion(synthon_model, feature=("graph",))
synthon_optimizer = torch.optim.Adam(synthon_task.parameters(), lr=1e-3)
synthon_solver = core.Engine(synthon_task, synthon_train, synthon_valid,
                             synthon_test, synthon_optimizer,
                             gpus=[0], batch_size=128)
synthon_solver.train(num_epoch=10)
synthon_solver.evaluate("valid")
synthon_solver.save("~/data/g2gs_synthon_model.pth")

an exception appeared:
    Chem.Kekulize(mol)
rdkit.Chem.rdchem.KekulizeException: Can't kekulize mol.  Unkekulized atoms: 11

Have anyone encountered that case, and how did you solve?
Vary appreciated for relpies!

I met the same question

I solve the problem by changing Chem.Kekulize(mol) to Chem.Kekulize(mol, clearAromaticFlags=True)

When I ran the code below（same as the demo in retrosynthesis tutorial）
from torchdrug import data, datasets, utils
from torchdrug.utils import plot
from torchdrug import core, models, tasks

synthon_dataset = datasets.USPTO50k("~/data", as_synthon=True,
                                    node_feature="synthon_completion",
                                    kekulize=True)
torch.manual_seed(1)
synthon_train, synthon_valid, synthon_test = synthon_dataset.split()
synthon_model = models.RGCN(input_dim=synthon_dataset.node_feature_dim,
                            hidden_dims=[256, 256, 256, 256, 256, 256],
                            num_relation=synthon_dataset.num_bond_type,
                            concat_hidden=True)
synthon_task = tasks.SynthonCompletion(synthon_model, feature=("graph",))
synthon_optimizer = torch.optim.Adam(synthon_task.parameters(), lr=1e-3)
synthon_solver = core.Engine(synthon_task, synthon_train, synthon_valid,
                             synthon_test, synthon_optimizer,
                             gpus=[0], batch_size=128)
synthon_solver.train(num_epoch=10)
synthon_solver.evaluate("valid")
synthon_solver.save("~/data/g2gs_synthon_model.pth")

an exception appeared:
    Chem.Kekulize(mol)
rdkit.Chem.rdchem.KekulizeException: Can't kekulize mol.  Unkekulized atoms: 11

Have anyone encountered that case, and how did you solve? Vary appreciated for relpies!

Sorry for the inconvience. I've changed rdkit version to 2021.9.2, which can address the problem in my case. Maybe you can have a try.
If it doesn't work for you, could you please tell us your pytorch and rdkit version? Since I'm not a developer for the retrosynthesis part, maybe @KiddoZhu and @shichence will help you on this.

Sorry for the inconvience. I've changed rdkit version to 2021.9.2, which can address the problem in my case. Maybe you can have a try.
If it doesn't work for you, could you please tell us your pytorch and rdkit version? Since I'm not a developer for the retrosynthesis part, maybe @KiddoZhu and @shichence will help you on this.
thx！The problem was solved with the version you offered, the reason may be the incompatibility of version, which I previously used is 2022.9.3 .

Sorry for the inconvience. I've changed rdkit version to 2021.9.2, which can address the problem in my case. Maybe you can have a try.
If it doesn't work for you, could you please tell us your pytorch and rdkit version? Since I'm not a developer for the retrosynthesis part, maybe @KiddoZhu and @shichence will help you on this.

Thx! The problem is solved with the rdkit version you offered, the version I previously used is 2022.9.3 .

For anyone working on OSX (M1), I was able to succeed using version 2021.9.4.
pip install rdkit-pypi-2021.9.4

I'm encountering the same issue with rdkit-pypi v 2022.9.5 and torch v 2.2.1+cu121

repo: DeepGraphLearning/torchdrug


text:
timetamps end in 0s

This was closed because it was apparently a bug of opencv


text:
Re-translations - developer metadata

To solve a re-translation issue, you can store translated pairs as developer metadata. In the DeepLTranslate() function, you should check if the "sourceLang|targetLang|input" key already exists, if so, there is no need to translate and the metadata value for the key can be used. If the key doesn't exist, the translation should be performed and the result stored as the metadata with the appropriate key. Similarly for glossaries. There could be a macro to delete all developer metadata to enable re-translation.
Small example to store and read metadata:
  var sheet = SpreadsheetApp.getActive();
  var row = sheet.getRange("1:1");
  row.addDeveloperMetadata("en-GB|de|Hello world!", "Hallo Welt!");
  var test=row.getDeveloperMetadata()[0];
  console.log(test.getKey());
  console.log(test.getValue());

Hi @machj, thank you for the suggestion! This is a great idea. I looked into the developer metadata documentation and unfortunately there is a limit of 30K characters per sheet.
We could minimize the cache size by hashing the input text, but I think it will be common to hit that limit. It's probably still worth looking into though.

authors: daniel-jones-deepl machj

repo: DeepLcom/google-sheets-example


text:
!>(STREAMs!) Newcastle v Arsenal LIVE FreE 02.11.2024

!>(STREAMs!) Newcastle v Arsenal LIVE FreE 02.11.2024

sdsd

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.
.
.
fgfg

Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/
Watch Live STREAM Here: https://stream247.online/

repo: DeepSourceCorp/good-first-issue


text:
Broken UI

The UI in the Stamina System ( #6 ) is broken, and resizes when the game is fullscreen or in any resolution other than Unity's default. This needs to be addressed before the Feature-Update branch can be merged

I finally managed to squash this bug and I updated the UI to look more modern. Check the notes on the Feature-Update branch

repo: Default-Cube-Studios/Movement-Template


text:
python3 compat?

Hi,
I got this running example, after adding () to print() in dojo_populate.py, i got this one.
» ❯ python3 dojo_populate.py
Traceback (most recent call last):
  File "dojo_populate.py", line 27, in <module>
    dd = defectdojo.DefectDojoAPI(host, api_key, user, debug=False)
  File "/home/cyril/trydefectdojoapi/venv/lib/python3.7/site-packages/defectdojo_api/defectdojo.py", line 37, in __init__
    if host.split('/') > 3:
TypeError: '>' not supported between instances of 'list' and 'int'

Thanks for help

I have the same problem.

seems an error in one of the scripts.
@Martin2877 @cyrinux  The code your referring to was modified by @aaronweaver on Aug 14, 2018
=> https://github.com/DefectDojo/defectdojo_api/commit/0eab5e58028f4a9044af6a06c06985a37b243248#diff-398ee4538a05ce9f45dc774f83e67aa783e808ab48aa91ad9ec26ce22bd2fb26

Any updates on this?

You can quickfix it in ste-packages/defectdojo_api/defectdojo.py
Replace:
if host.split('/') > 3:
By:
if len(host.split('/')) > 3:
I'll make a PR for it

FYI: this piece of code was removed in https://github.com/DefectDojo/defectdojo_api/commit/0eab5e58028f4a9044af6a06c06985a37b243248#diff-398ee4538a05ce9f45dc774f83e67aa783e808ab48aa91ad9ec26ce22bd2fb26.
Should it be more simple to update the module to a new version?


text:
Update deduplication fields for Trufflehog (and other scanners...)

⚠ Is your feature request related to a problem? Please describe
I'm always frustrated with deduplication with Trufflehog parser.
Any change from Trufflehog scanner or Security Operators might impact the description field, which is used as a key for deduplication.
✔ Describe the solution you'd like
As a Security Operator, I want to update the deduplication mechanism so that updating the description field won't impact duplicate issues.
💡 Describe alternatives you've considered
There are two main solutions, both of them consist of updating the hashcode configuration.
Solution A
We can rely on the payload field which would be filled with the Raw or RawV2 field from Trufflehog. Adding the file_path, would ensure that we capture several findings if a same secret is found across several files/repositories:

'Trufflehog Scan': ['payload', 'file_path']

Solution B ⭐
We can rely on the url field which would be filled with the link field from Trufflehog. The link value is a unique identifier: https://github.com/[organization]/[project]/blob/[commit_hash]/[file_path]#[line_number]

'Trufflehog Scan': ['url']

➕ Additional context
Migration step
payload and url are not sent to DefectDojo as a default. A migration step would require to calculate these fields for existing findings. Otherwise duplicates will be based on empty fields, causing a lot of unwanted duplicates.
Pros and Cons
Also, each solution comes with both pros and cons:

Solution A

Pros: Most straightforward solution. Customers can easily customize how they want to consider duplicates: 1 finding / secret, 1 finding / secret / project, 1 finding / secret / file... etc
Cons: It can be very difficult to retrieve the payload field for existing findings

Solution B ⭐

Pros: The url field can calculated for old findings. If we consider that one project in DefectDojo = 1 repository in Github, we just need to parse the existing description field to build an url path (organization, project, commit_hash, file_path and line_number are all known)
Cons: The url field is not exactly meant to receive this value (but rather an external source of documentation instead)

Finally, Solution B seems the most realistic.
This thinking process is applicable to Trufflehog, but not only. There are several parsers calculating duplicate findings based on the description field which could be updated as well.

See https://github.com/DefectDojo/django-DefectDojo/pull/10118 for Solution B proposal

repo: DefectDojo/django-DefectDojo


text:
feat(clair parser): parse component name and version

On behalf of DB Systel GmbH

are these fields always present, or do they need a safer way to read them from the dict?

are these fields always present, or do they need a safer way to read them from the dict?

@valentijnscholten @madchap As I understand how Clair works, it's how the tool works. First it detect the component+version, second, it check with vuln data to produce a finding. You can't have a finding without a component.
For me this pull request is a must have. Users of Clair will see as normal to see component in the UI.

@valentijnscholten @madchap As I understand how Clair works, it's how the tool works. First it detect the component+version, second, it check with vuln data to produce a finding. You can't have a finding without a component.
For me this pull request is a must have. Users of Clair will see as normal to see component in the UI.

Yea, seems it's ok.
https://github.com/arminc/clair-scanner/blob/master/clair.go#L18-L20 and https://github.com/arminc/clair-scanner/blob/master/clair.go#L93

Yea, seems it's ok.
https://github.com/arminc/clair-scanner/blob/master/clair.go#L18-L20 and https://github.com/arminc/clair-scanner/blob/master/clair.go#L93

I will take a look @valentijnscholten

I will take a look @valentijnscholten

authors: alles-klar damiencarol madchap valentijnscholten


text:
Research Cosmos-based Blockchains and Custom Modules to support the Cosmos Indexer

The Cosmos Indexer is an opensource indexer implementation written in Go that works directly with the Cosmos SDK to index Cosmos SDK based blockchains.
The indexer is written to be generic, in that it is intended to index any blockchain that is based on the Cosmos SDK. This is possible due to the common set of data points that are queryable across the Cosmos ecosystem and the availability of similar data shapes that are indexable.
There is one caveat to this: the Cosmos SDK allows new modules to be included in blockchains that use it. This provides developers with the flexibility to create new behavior, but it makes it difficult for indexers to know the shape of data for new blockchains.
The goal of this task is to:

Support the Cosmos Indexer opensource repo by researching Cosmos SDK-based chains
Discover new custom chain modules of interest
Document the Transaction message types and how to build them
Make contributions to the Cosmos Indexer Modules repo to support new chains

Resources

Blockchain Indexing Explained
cosmos-indexer repo - the main indexer implementation
cosmos-indexer-modules - plug-and-play modules for supporting new chains

These downstream issues will be useful for starting references:

https://github.com/DefiantLabs/cosmos-indexer-modules/issues/3
https://github.com/DefiantLabs/cosmos-indexer-modules/issues/4
https://github.com/DefiantLabs/cosmos-indexer-modules/issues/5

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

repo: DefiantLabs/volunteer


text:
angular material $mdDialog.show(fullscreen: true)

Angular material $mdDialog has the fullscreen option that TSD definition does not implement.
$mdDialog.show({
      controller: DialogController,
      templateUrl: 'dialog1.tmpl.html',
      parent: angular.element(document.body),
      targetEvent: ev,
      clickOutsideToClose:true,
      fullscreen: $mdMedia('sm') && $scope.customFullscreen
    })

from the JS tab
https://material.angularjs.org/latest/demo/dialog

I think you've got the wrong repo. Try opening it up over at https://github.com/DefinitelyTyped/DefinitelyTyped, which holds all the type definitions.

authors: blakeembrey gabrielmuresan

repo: DefinitelyTyped/tsd


text:
[Enhancement] Migration from official securecompliance/gvm image

Describe the solution you'd like
Many folks, including myself, are using the official but outdated image securecompliance/gvm.  It would be nice to be able to switch from that image to this more actively developed one.
When using deineagenturug/gvm:latest-data-full as a drop in replacement for securecompliance/gvm:debian-master-data there are problems with PostgreSQL.  Likely because of the version differences.
A check on first start and migration would be really excellent.  Failing that - a method to migrate existing data would be great.
ALSO - I'm capable and willing to clone and send pull requests if you can give me a basic overview of how the check/migration should work.  At this point its not clear and I'd need to get up to speed before attempting to contribute changes.

I started on this see the mention in #14
I would check the version in the database storage path, and them it need to update major version to the next major version, excepted of this behavior is all pre 10 major version.
I‘m not sure currently how much versions need to migrated so my initial Dockerfiles includes more then I think that are needed.
11to12 and 12 to 13 should work easy only from 13 to 14 needs additional steps.
If you like to contribute, you are welcome. But I need to know this, else I will do it myself hopefully by end of the next week.
regards Josef

Btw. It will not work within the default container and should be done in an extra image that can reused with other installations (#14)

If you like to contribute, you are welcome. But I need to know this, else I will do it myself hopefully by end of the next week.

Hi Josef,
I tried to get going on this but won't have time before next week with the holidays and all.

I started with a initial setup here: https://github.com/DeineAgenturUG/greenbone-gvm-openvas-for-docker/tree/db_upgrade
It will need for sure more work, maybe a other way. I try how I can fix the issues that I see.

Here a working development build.
⚠ Please make sure you have shutdown/stopped the old GVM container from securecompliance or whatever your old image might be!!!!
Once you have done, please make sure you have a backup created before you running this following steps.
We will not touch the old data, but you'll know it is better to have a backup, then sorry. We create a temp copy of the Database before we starting the upgrade process.
Also this step create the right permissions for the new database. So you don't need to have a eye on this. Right after all steps are done, you can use our image deineagenturug/gvm:latest with the new database.
docker pull deineagenturug/pgdb-upgrade-develop:latest

docker run -ti --rm -v "/path/to/old/securecompliance/database:/mnt/pg_old/data" -v "/path/to/new/deineagenturug/database:/mnt/pg_new/data" deineagenturug/pgdb-upgrade-develop:latest bash

Then you have to run in the container shell: /opt/setup/scripts/db_upgrade.sh
ℹ I hope you can enjoy the "DB Upgrade" tool and let me know how it works for you, any feedback is welcome.
/cc @markdesilva @LandonStewart

Hi @Dexus,
Thank you! Will try it out as soon as I'm done coaching my son for his mid year exams.
Best Regards,
Mark

Here a working development build.
⚠ Please make sure you have shutdown/stopped the old GVM container from securecompliance or whatever your old image might be!!!!
Once you have done, please make sure you have a backup created before you running this following steps. We will not touch the old data, but you'll know it is better to have a backup, then sorry. We create a temp copy of the Database before we starting the upgrade process to postgresql version 13.
Also this step create the right permissions for the new database. So you don't need to have a eye on this. Right after all steps are done, you can use our image deineagenturug/gvm:latest with the new database of postgresql 13.
docker pull deineagenturug/pgdb-upgrade-develop:latest

docker run -ti --rm -v "/path/to/old/securecompliance/database:/mnt/pg_old/data" -v "/path/to/new/deineagenturug/database:/mnt/pg_new/data" deineagenturug/pgdb-upgrade-develop:latest bash

Then you have to run in the container shell: /opt/setup/scripts/db_upgrade.sh
ℹ I hope you can enjoy the "DB Upgrade" tool and let me know how it works for you, any feedback is welcome.
/cc @markdesilva @LandonStewart

Once it's tested a bit more and I get some feedback on it, it will be added to the gvm image as well. So there is no need for an extra image.

So here's what I did to test it with your instructions in mind:

docker-compose down
mv /data/gvm/database /data/gvm/database.OLD
$ docker run -ti --rm -v "/data/gvm/database.OLD:/mnt/pg_old/data" -v "/data/gvm/database:/mnt/pg_new/data" deineagenturug/pgdb-upgrade-develop:latest bash
Within the container shell executed:
# /opt/setup/scripts/db_upgrade.sh (answered 'y' when asked)
# exit
Modified my docker-compose.yml to use image: deineagenturug/gvm:latest-data-full
Executed: docker-compose up -d

It worked without a hitch.  Thank you!
I've attached the output of the docker container during the upgrade:
database_upgrade_output.txt

@LandonStewart
Thank you for sharing the path in more detailed steps.
Your log shows an identical output to mine. Perfect!

The conversion is successful but when the docker starts this error is thrown:
gvmdebian    | redis: started
gvmdebian    | Wait for redis socket to be created...
gvmdebian    | Testing redis status...
gvmdebian    | Redis ready.
gvmdebian    | Creating Database folder and rights...
gvmdebian    | Starting PostgreSQL...
gvmdebian    | 2022-04-23 12:47:48,993 INFO spawned: 'postgresql' with pid 590
gvmdebian    | 2022-04-23 12:47:59,063 INFO success: postgresql entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
gvmdebian    | postgresql: started
gvmdebian    | Generate SSH-HOST Keys
gvmdebian    | Creating Greenbone Vulnerability Manager database
gvmdebian    | createuser: error: creation of new role failed: ERROR:  role "gvm" already exists
gvmdebian    | 2022-04-23 12:47:59,277 INFO exited: init (exit status 1; not expected)

I think i found the problem.
in the new database folder these two files are missing, present in the old database folder:
-rw-r--r--  1 syslog input     0 Apr 23 14:13 .firstrun
and
-rw-r--r--  1 syslog input     0 Apr 23 14:13 .upgrade_to_21.4.0

Hi @LandonStewart, would it be alright to send me your docker-compose.yml please so I can take a look? I think I'm doing something wrong with the volumes.
Thank you.

So here's what I did to test it with your instructions in mind:
1. `docker-compose down`

2. `mv /data/gvm/database /data/gvm/database.OLD`

3. `$ docker run -ti --rm -v "/data/gvm/database.OLD:/mnt/pg_old/data" -v "/data/gvm/database:/mnt/pg_new/data" deineagenturug/pgdb-upgrade-develop:latest bash`

4. Within the container shell executed:
   `# /opt/setup/scripts/db_upgrade.sh` (answered 'y' when asked)
   `# exit`

5. Modified my docker-compose.yml to use `image: deineagenturug/gvm:latest-data-full`

6. Executed: `docker-compose up -d`

It worked without a hitch. Thank you!
I've attached the output of the docker container during the upgrade: database_upgrade_output.txt

@netbix you previous image/tag was which one?
Will look into it and fix it when I get the same result.

i migrated from:
securecompliance/gvm:debian-master-data TO deineagenturug/gvm:latest-data-full
I have change my config with:
COPY OR RENAME TO "local.env" AND CUSTOMIZE
Custom environment variables
USERNAME=admin
PASSWORD=admin
PASSWORD_FILE
DB_PASSWORD=xxxxxxxxxx
DB_PASSWORD_FILE
HTTPS=true
SSHD=true
AUTO_SYNC=YES
AUTO_SYNC_ON_START=YES
TZ=Europe/Rome
RELAYHOST=x.x.x.x
SMTPPORT=25
OPT_PDF=1
CERTIFICATE
CERTIFICATE_KEY
and compose:
version: '3.4'
services:
gvmdebian:
image: deineagenturug/gvm:latest-data-full
hostname: gvmdebian
container_name: gvmdebian
restart: always
ports:
- "8082:9392"
- "5432:5432"
- "2222:22"
env_file:
- ./config/local.env
volumes:
- ./storage/postgres-db:/opt/database
- ./storage/openvas-plugins:/var/lib/openvas/plugins
- ./storage/gvm:/var/lib/gvm
- ./storage/ssh:/etc/ssh
with those two files everything works

Yes I had not thought about the lock files. Will fix it in the evening, an release a new upgrade image.

what is this variable for?
export NO_AUTO_UPDATE=${NO_AUTO_UPDATE:-NO}

thank you !

what is this variable for?
export NO_AUTO_UPDATE=${NO_AUTO_UPDATE:-NO}

I hope I did not use it, had used it in a local test. It's the opposite of the AUTO_SYNC_ON_START=YES when I'm get it right from remembers.

further problem:
scanning does not work.
OpenVAS_scanner is not found

root@gvmdebian:/# gvmd --get-scanners
root@gvmdebian:/# gvmd --get-users
root@gvmdebian:/# gvmd --version
Greenbone Vulnerability Manager 21.4.5
Manager DB revision 242
Copyright (C) 2009-2021 Greenbone Networks GmbH
License: AGPL-3.0-or-later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

the process seems to work:

I was wrong:

but why is it not detected and the scans no longer work?

@netbix good catch, will fix it with the release 21.4.4 oder 21.4.5 the socket has changed with the merge of ospd and ospd-openvas.

@netbix
run
sudo -u postgres psql -d gvmd -c "UPDATE public.scanners SET host='/run/ospd/ospd-openvas.sock' WHERE name='OpenVAS Default' and (host='/var/run/ospd/ospd.sock' or host='/run/ospd/ospd.sock');"
within the gvm container should fix it.
Will be done later automatically in the db upgrade script and also on the start.sh with the next release.

When upgrading the db I get this error:
lc_collate values for database "postgres" do not match:  old "C.UTF-8", new "en_US.UTF-8"
If I use this db to startup the image, there are no errors, but then none of my reports, tasks, overrides, etc are there.
Another weird issue is that the CERTIFICATE and CERTIFICATE_KEY environment variables don't get recognized for some reason. The start script always executes gsad-https instead of gsad-https-owncert. I tested this by editing the /opt/setup/config/supevisord.conf for gsad-https and adding the certs into the command directly and when I restart the container then the certs loaded correctly.
Oh and on the wiki it says "Deprecated values: true,TRUE,false,FALSE" for SSHD and HTTPS. But if I use "YES", its not accepted.
Thank you.

When upgrading the db I get this error:
lc_collate values for database "postgres" do not match: old "C.UTF-8", new "en_US.UTF-8"
If I use this db to startup the image, there are no errors, but then none of my reports, tasks, overrides, etc are there.

This can't work, because the DB is not get upgraded with this error. Need to check how I get the correct lc_collate and reuse them. Thank you for the report, will check and create an update for the db_upgrade.sh

Another weird issue is that the CERTIFICATE and CERTIFICATE_KEY environment variables don't get recognized for some reason. The start script always executes gsad-https instead of gsad-https-owncert. I tested this by editing the /opt/setup/config/supevisord.conf for gsad-https and adding the certs into the command directly and when I restart the container then the certs loaded correctly.

Thanks, will look into it also.

Oh and on the wiki it says "Deprecated values: true,TRUE,false,FALSE" for SSHD and HTTPS. But if I use "YES", its not accepted.

Ups was to early with my changed to the wiki. release is not yet there where this will point to.

Thank you.

Thank you <3

Thank you @Dexus!

This can't work, because the DB is not get upgraded with this error. Need to check how I get the correct lc_collate and reuse them. Thank you for the report, will check and create an update for the db_upgrade.sh

For the gsad-https-owncert issue, I was looking at the start.sh and I think its running gsad-https because its not recognizing the "YES" in the env. It is also not recognizing "TRUE" (all caps) but "true" (small letters) works.
Thank you!

@Dexus, also is it ok to add "--hts-sts" to the supervisord,conf for the gsad-https and gsad-https-owncert commands to add HTTP Strict Transport Security? If not I can add it on my own, but it would be good to have.
Thank you!

A new version of the upgrade image is online: docker pull deineagenturug/pgdb-upgrade-develop:latest

fix the lock files, and reset them on the new DB version
stop if the old and the new DB have the same version
It will handle the ospd/openvas socket from older versions also the secure compliance solutions version. and fix it to the current used one.
Also it handles now the old LC_COLLATE and LC_CTYPE from the old DB and use it with the initdb command for the new version.

@netbix @markdesilva would nice if you can retry the upgrade - I have currently only mobile internet access and not able to check with different images and setups. Thank you.

sudo -u postgres psql -d gvmd -c "UPDATE public.scanners SET host='/run/ospd/ospd-openvas.sock' WHERE name='OpenVAS Default' and (host='/var/run/ospd/ospd.sock' or host='/run/ospd/ospd.sock');"

Thank you !
Perfect !

@Dexus, also is it ok to add "--http-sts" to the supervisord,conf for the gsad-https and gsad-https-owncert commands to add HTTP Strict Transport Security? If not I can add it on my own, but it would be good to have.
Thank you!

@markdesilva
To keep the thread here clean on the migration, can you open a issue for it? Thank you.

A new version of the upgrade image is online: docker pull deineagenturug/pgdb-upgrade-develop:latest
* fix the lock files, and reset them on the new DB version

* stop if the old and the new DB have the same version

* It will handle the ospd/openvas socket from older versions also the secure compliance solutions version. and fix it to the current used one.

* Also it handles now the old `LC_COLLATE` and `LC_CTYPE` from the old DB and use it with the `initdb` command for the new version.

@netbix @markdesilva would nice if you can retry the upgrade - I have currently only mobile internet access and not able to check with different images and setups. Thank you.

I have restore my backup DB, but ....

maybe this is the problem?

@Dexus thank you for the fast fix!
It’s 1.30am here now, will try when I wake up later and let you know if it works!

@netbix @markdesilva would nice if you can retry the upgrade - I have currently only mobile internet access and not able to check with different images and setups. Thank you.

I have restore my backup DB, but ....

@Dexus, also is it ok to add "--http-sts" to the supervisord,conf for the gsad-https and gsad-https-owncert commands to add HTTP Strict Transport Security? If not I can add it on my own, but it would be good to have.
Thank you!

@markdesilva

Will do, thank you.

To keep the thread here clean on the migration, can you open a issue for it? Thank you.

I have correct IF but ....

calmly it will be revised a bit

@netbix thank you and sorry that I was not double check it, a new image is uploaded with the fixes.
docker pull deineagenturug/pgdb-upgrade-develop:latest

many many thanks !!!

I'm sorry but it doesn't work!
calmly you will see tomorrow

Thank you! Damn... 😮💨 today I will not able to change this, but think tomorrow I can do it.

@netbix thank you and sorry that I was not double check it, a new image is uploaded with the fixes.
docker pull deineagenturug/pgdb-upgrade-develop:latest
Fixed:

copy of already edited configs to new DB -> should not copy the temp DB config -> copies now the old config to new DB

Perfect !!!
Now everything works! After update feed I'm running the first task with new engine.
Thank you so much thank you

Does the file for the first download exist in your work?

Does the file for the first download exist in your work?

local_multistep_build_v2.sh on devel branch line 227 is download it. So yes it's on my system and work :) or do you mean the lock file?

Getting this error in with the new db upgrade:
Checking for presence of required libraries                 fatal
Full error in "loadable_libraries.txt" is :
could not load library "/usr/local/lib/libgvm-pg-server": ERROR:  could not access file "/usr/local/lib/libgvm-pg-server": No such file or directory
In database: gvmd

Whole upgrade log:
Note, selecting 'postgresql-12' instead of 'postgresql-contrib-12'
dpkg is already the newest version (1.20.9).
libglib2.0-0 is already the newest version (2.66.8-1).
locales is already the newest version (2.31-13+deb11u3).
libgnutls30 is already the newest version (3.7.1-5).
libgpgme11 is already the newest version (1.14.0-1+b2).
libhiredis0.14 is already the newest version (0.14.1-1).
libical3 is already the newest version (3.0.9-2).
libnet1 is already the newest version (1.1.6+dfsg-3.1).
libpcap0.8 is already the newest version (1.10.0-2).
libssh-gcrypt-4 is already the newest version (0.9.5-1+deb11u1).
libxml2 is already the newest version (2.9.10+dfsg-6.7+deb11u1).
nano is already the newest version (5.4-2).
libldap-2.4-2 is already the newest version (2.4.57+dfsg-3).
libradcli4 is already the newest version (1.2.11-1+b2).
libuuid1 is already the newest version (2.36.1-8+deb11u1).
zip is already the newest version (3.0-12).
postgresql-common is already the newest version (238.pgdg110+1).
The following additional packages will be installed:
  binutils binutils-common binutils-x86-64-linux-gnu clang-11 lib32gcc-s1 lib32stdc++6 libasan6 libbinutils libc-dev-bin libc6-dev libc6-i386 libclang-common-11-dev libclang-cpp11 libclang1-11 libcrypt-dev libctf-nobfd0 libctf0
  libffi-dev libgc1 libgcc-10-dev libitm1 liblsan0 libncurses-dev libnsl-dev libobjc-10-dev libobjc4 libpfm4 libquadmath0 libssl-dev libstdc++-10-dev libtinfo-dev libtirpc-dev libtsan0 libubsan1 libyaml-0-2 libz3-dev linux-libc-dev
  llvm-11 llvm-11-dev llvm-11-runtime llvm-11-tools python3-pygments python3-yaml
Suggested packages:
  binutils-doc clang-11-doc glibc-doc manpages-dev ncurses-doc postgresql-doc-14 libssl-doc libstdc++-10-doc llvm-11-doc postgresql-doc-12 python-pygments-doc ttf-bitstream-vera
Recommended packages:
  libomp-11-dev manpages manpages-dev libc-devtools binfmt-support sysstat
The following NEW packages will be installed:
  binutils binutils-common binutils-x86-64-linux-gnu clang-11 lib32gcc-s1 lib32stdc++6 libasan6 libbinutils libc-dev-bin libc6-dev libc6-i386 libclang-common-11-dev libclang-cpp11 libclang1-11 libcrypt-dev libctf-nobfd0 libctf0
  libffi-dev libgc1 libgcc-10-dev libitm1 liblsan0 libncurses-dev libnsl-dev libobjc-10-dev libobjc4 libpfm4 libpq-dev libquadmath0 libssl-dev libstdc++-10-dev libtinfo-dev libtirpc-dev libtsan0 libubsan1 libyaml-0-2 libz3-dev
  linux-libc-dev llvm-11 llvm-11-dev llvm-11-runtime llvm-11-tools postgresql-12 postgresql-client-12 postgresql-server-dev-12 python3-pygments python3-yaml
The following packages will be upgraded:
  xz-utils
1 upgraded, 47 newly installed, 0 to remove and 3 not upgraded.
Need to get 101 MB of archives.
After this operation, 593 MB of additional disk space will be used.

Preconfiguring packages ...
(Reading database ...
Preparing to unpack .../00-xz-utils_5.2.5-2.1~deb11u1_amd64.deb ...
Unpacking xz-utils (5.2.5-2.1~deb11u1) over (5.2.5-2) ...
Selecting previously unselected package binutils-common:amd64.
Preparing to unpack .../01-binutils-common_2.35.2-2_amd64.deb ...
Unpacking binutils-common:amd64 (2.35.2-2) ...
Selecting previously unselected package libbinutils:amd64.
Preparing to unpack .../02-libbinutils_2.35.2-2_amd64.deb ...
Unpacking libbinutils:amd64 (2.35.2-2) ...
Selecting previously unselected package libctf-nobfd0:amd64.
Preparing to unpack .../03-libctf-nobfd0_2.35.2-2_amd64.deb ...
Unpacking libctf-nobfd0:amd64 (2.35.2-2) ...
Selecting previously unselected package libctf0:amd64.
Preparing to unpack .../04-libctf0_2.35.2-2_amd64.deb ...
Unpacking libctf0:amd64 (2.35.2-2) ...
Selecting previously unselected package binutils-x86-64-linux-gnu.
Preparing to unpack .../05-binutils-x86-64-linux-gnu_2.35.2-2_amd64.deb ...
Unpacking binutils-x86-64-linux-gnu (2.35.2-2) ...
Selecting previously unselected package binutils.
Preparing to unpack .../06-binutils_2.35.2-2_amd64.deb ...
Unpacking binutils (2.35.2-2) ...
Selecting previously unselected package libclang-cpp11.
Preparing to unpack .../07-libclang-cpp11_1%3a11.0.1-2_amd64.deb ...
Unpacking libclang-cpp11 (1:11.0.1-2) ...
Selecting previously unselected package libitm1:amd64.
Preparing to unpack .../08-libitm1_10.2.1-6_amd64.deb ...
Unpacking libitm1:amd64 (10.2.1-6) ...
Selecting previously unselected package libasan6:amd64.
Preparing to unpack .../09-libasan6_10.2.1-6_amd64.deb ...
Unpacking libasan6:amd64 (10.2.1-6) ...
Selecting previously unselected package liblsan0:amd64.
Preparing to unpack .../10-liblsan0_10.2.1-6_amd64.deb ...
Unpacking liblsan0:amd64 (10.2.1-6) ...
Selecting previously unselected package libtsan0:amd64.
Preparing to unpack .../11-libtsan0_10.2.1-6_amd64.deb ...
Unpacking libtsan0:amd64 (10.2.1-6) ...
Selecting previously unselected package libubsan1:amd64.
Preparing to unpack .../12-libubsan1_10.2.1-6_amd64.deb ...
Unpacking libubsan1:amd64 (10.2.1-6) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../13-libquadmath0_10.2.1-6_amd64.deb ...
Unpacking libquadmath0:amd64 (10.2.1-6) ...
Selecting previously unselected package libgcc-10-dev:amd64.
Preparing to unpack .../14-libgcc-10-dev_10.2.1-6_amd64.deb ...
Unpacking libgcc-10-dev:amd64 (10.2.1-6) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../15-libc-dev-bin_2.31-13+deb11u3_amd64.deb ...
Unpacking libc-dev-bin (2.31-13+deb11u3) ...
Selecting previously unselected package linux-libc-dev:amd64.
Preparing to unpack .../16-linux-libc-dev_5.10.106-1_amd64.deb ...
Unpacking linux-libc-dev:amd64 (5.10.106-1) ...
Selecting previously unselected package libcrypt-dev:amd64.
Preparing to unpack .../17-libcrypt-dev_1%3a4.4.18-4_amd64.deb ...
Unpacking libcrypt-dev:amd64 (1:4.4.18-4) ...
Selecting previously unselected package libtirpc-dev:amd64.
Preparing to unpack .../18-libtirpc-dev_1.3.1-1_amd64.deb ...
Unpacking libtirpc-dev:amd64 (1.3.1-1) ...
Selecting previously unselected package libnsl-dev:amd64.
Preparing to unpack .../19-libnsl-dev_1.3.0-2_amd64.deb ...
Unpacking libnsl-dev:amd64 (1.3.0-2) ...
Selecting previously unselected package libc6-dev:amd64.
Preparing to unpack .../20-libc6-dev_2.31-13+deb11u3_amd64.deb ...
Unpacking libc6-dev:amd64 (2.31-13+deb11u3) ...
Selecting previously unselected package libstdc++-10-dev:amd64.
Preparing to unpack .../21-libstdc++-10-dev_10.2.1-6_amd64.deb ...
Unpacking libstdc++-10-dev:amd64 (10.2.1-6) ...
Selecting previously unselected package libgc1:amd64.
Preparing to unpack .../22-libgc1_1%3a8.0.4-3_amd64.deb ...
Unpacking libgc1:amd64 (1:8.0.4-3) ...
Selecting previously unselected package libobjc4:amd64.
Preparing to unpack .../23-libobjc4_10.2.1-6_amd64.deb ...
Unpacking libobjc4:amd64 (10.2.1-6) ...
Selecting previously unselected package libobjc-10-dev:amd64.
Preparing to unpack .../24-libobjc-10-dev_10.2.1-6_amd64.deb ...
Unpacking libobjc-10-dev:amd64 (10.2.1-6) ...
Selecting previously unselected package libc6-i386.
Preparing to unpack .../25-libc6-i386_2.31-13+deb11u3_amd64.deb ...
Unpacking libc6-i386 (2.31-13+deb11u3) ...
Selecting previously unselected package lib32gcc-s1.
Preparing to unpack .../26-lib32gcc-s1_10.2.1-6_amd64.deb ...
Unpacking lib32gcc-s1 (10.2.1-6) ...
Selecting previously unselected package lib32stdc++6.
Preparing to unpack .../27-lib32stdc++6_10.2.1-6_amd64.deb ...
Unpacking lib32stdc++6 (10.2.1-6) ...
Selecting previously unselected package libclang-common-11-dev.
Preparing to unpack .../28-libclang-common-11-dev_1%3a11.0.1-2_amd64.deb ...
Unpacking libclang-common-11-dev (1:11.0.1-2) ...
Selecting previously unselected package libclang1-11.
Preparing to unpack .../29-libclang1-11_1%3a11.0.1-2_amd64.deb ...
Unpacking libclang1-11 (1:11.0.1-2) ...
Selecting previously unselected package clang-11.
Preparing to unpack .../30-clang-11_1%3a11.0.1-2_amd64.deb ...
Unpacking clang-11 (1:11.0.1-2) ...
Selecting previously unselected package libffi-dev:amd64.
Preparing to unpack .../31-libffi-dev_3.3-6_amd64.deb ...
Unpacking libffi-dev:amd64 (3.3-6) ...
Selecting previously unselected package libncurses-dev:amd64.
Preparing to unpack .../32-libncurses-dev_6.2+20201114-2_amd64.deb ...
Unpacking libncurses-dev:amd64 (6.2+20201114-2) ...
Selecting previously unselected package libpfm4:amd64.
Preparing to unpack .../33-libpfm4_4.11.1+git32-gd0b85fb-1_amd64.deb ...
Unpacking libpfm4:amd64 (4.11.1+git32-gd0b85fb-1) ...
Selecting previously unselected package libssl-dev:amd64.
Preparing to unpack .../34-libssl-dev_1.1.1n-0+deb11u1_amd64.deb ...
Unpacking libssl-dev:amd64 (1.1.1n-0+deb11u1) ...
Selecting previously unselected package libpq-dev.
Preparing to unpack .../35-libpq-dev_14.2-1.pgdg110+1_amd64.deb ...
Unpacking libpq-dev (14.2-1.pgdg110+1) ...
Selecting previously unselected package libtinfo-dev:amd64.
Preparing to unpack .../36-libtinfo-dev_6.2+20201114-2_amd64.deb ...
Unpacking libtinfo-dev:amd64 (6.2+20201114-2) ...
Selecting previously unselected package libyaml-0-2:amd64.
Preparing to unpack .../37-libyaml-0-2_0.2.2-1_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.2.2-1) ...
Selecting previously unselected package libz3-dev:amd64.
Preparing to unpack .../38-libz3-dev_4.8.10-1_amd64.deb ...
Unpacking libz3-dev:amd64 (4.8.10-1) ...
Selecting previously unselected package llvm-11-runtime.
Preparing to unpack .../39-llvm-11-runtime_1%3a11.0.1-2_amd64.deb ...
Unpacking llvm-11-runtime (1:11.0.1-2) ...
Selecting previously unselected package llvm-11.
Preparing to unpack .../40-llvm-11_1%3a11.0.1-2_amd64.deb ...
Unpacking llvm-11 (1:11.0.1-2) ...
Selecting previously unselected package python3-pygments.
Preparing to unpack .../41-python3-pygments_2.7.1+dfsg-2.1_all.deb ...
Unpacking python3-pygments (2.7.1+dfsg-2.1) ...
Selecting previously unselected package python3-yaml.
Preparing to unpack .../42-python3-yaml_5.3.1-5_amd64.deb ...
Unpacking python3-yaml (5.3.1-5) ...
Selecting previously unselected package llvm-11-tools.
Preparing to unpack .../43-llvm-11-tools_1%3a11.0.1-2_amd64.deb ...
Unpacking llvm-11-tools (1:11.0.1-2) ...
Selecting previously unselected package llvm-11-dev.
Preparing to unpack .../44-llvm-11-dev_1%3a11.0.1-2_amd64.deb ...
Unpacking llvm-11-dev (1:11.0.1-2) ...
Selecting previously unselected package postgresql-client-12.
Preparing to unpack .../45-postgresql-client-12_12.10-1.pgdg110+1_amd64.deb ...
Unpacking postgresql-client-12 (12.10-1.pgdg110+1) ...
Selecting previously unselected package postgresql-12.
Preparing to unpack .../46-postgresql-12_12.10-1.pgdg110+1_amd64.deb ...
Unpacking postgresql-12 (12.10-1.pgdg110+1) ...
Selecting previously unselected package postgresql-server-dev-12.
Preparing to unpack .../47-postgresql-server-dev-12_12.10-1.pgdg110+1_amd64.deb ...
Unpacking postgresql-server-dev-12 (12.10-1.pgdg110+1) ...
Setting up libz3-dev:amd64 (4.8.10-1) ...
Setting up llvm-11-runtime (1:11.0.1-2) ...
Setting up libyaml-0-2:amd64 (0.2.2-1) ...
Setting up binutils-common:amd64 (2.35.2-2) ...
Setting up linux-libc-dev:amd64 (5.10.106-1) ...
Setting up libctf-nobfd0:amd64 (2.35.2-2) ...
Setting up python3-yaml (5.3.1-5) ...
Setting up libffi-dev:amd64 (3.3-6) ...
Setting up libasan6:amd64 (10.2.1-6) ...
Setting up libclang-cpp11 (1:11.0.1-2) ...
Setting up python3-pygments (2.7.1+dfsg-2.1) ...
Setting up postgresql-client-12 (12.10-1.pgdg110+1) ...
Setting up libtirpc-dev:amd64 (1.3.1-1) ...
Setting up libpfm4:amd64 (4.11.1+git32-gd0b85fb-1) ...
Setting up xz-utils (5.2.5-2.1~deb11u1) ...
Setting up libquadmath0:amd64 (10.2.1-6) ...
Setting up libssl-dev:amd64 (1.1.1n-0+deb11u1) ...
Setting up libclang1-11 (1:11.0.1-2) ...
Setting up libgc1:amd64 (1:8.0.4-3) ...
Setting up libubsan1:amd64 (10.2.1-6) ...
Setting up libnsl-dev:amd64 (1.3.0-2) ...
Setting up libcrypt-dev:amd64 (1:4.4.18-4) ...
Setting up libc6-i386 (2.31-13+deb11u3) ...
Setting up libbinutils:amd64 (2.35.2-2) ...
Setting up postgresql-12 (12.10-1.pgdg110+1) ...
Creating new PostgreSQL cluster 12/main ...
/usr/lib/postgresql/12/bin/initdb -D /var/lib/postgresql/12/main --auth-local peer --auth-host md5
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "C.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/12/main ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

Success. You can now start the database server using:

    pg_ctlcluster 12 main start

invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of start.
Setting up libc-dev-bin (2.31-13+deb11u3) ...
Setting up liblsan0:amd64 (10.2.1-6) ...
Setting up libitm1:amd64 (10.2.1-6) ...
Setting up libtsan0:amd64 (10.2.1-6) ...
Setting up libctf0:amd64 (2.35.2-2) ...
Setting up llvm-11-tools (1:11.0.1-2) ...
Setting up libgcc-10-dev:amd64 (10.2.1-6) ...
Setting up llvm-11 (1:11.0.1-2) ...
Setting up libpq-dev (14.2-1.pgdg110+1) ...
Setting up libobjc4:amd64 (10.2.1-6) ...
Setting up lib32gcc-s1 (10.2.1-6) ...
Setting up lib32stdc++6 (10.2.1-6) ...
Setting up libobjc-10-dev:amd64 (10.2.1-6) ...
Setting up libclang-common-11-dev (1:11.0.1-2) ...
Setting up libc6-dev:amd64 (2.31-13+deb11u3) ...
Setting up binutils-x86-64-linux-gnu (2.35.2-2) ...
Setting up libncurses-dev:amd64 (6.2+20201114-2) ...
Setting up libstdc++-10-dev:amd64 (10.2.1-6) ...
Setting up llvm-11-dev (1:11.0.1-2) ...
Setting up binutils (2.35.2-2) ...
Setting up clang-11 (1:11.0.1-2) ...
Setting up postgresql-server-dev-12 (12.10-1.pgdg110+1) ...
Setting up libtinfo-dev:amd64 (6.2+20201114-2) ...
Processing triggers for postgresql-common (238.pgdg110+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
Processing triggers for libc-bin (2.31-13+deb11u3) ...
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.
removed '/var/lib/apt/lists/apt.postgresql.org_pub_repos_apt_dists_bullseye-pgdg_InRelease'
removed '/var/lib/apt/lists/apt.postgresql.org_pub_repos_apt_dists_bullseye-pgdg_main_binary-amd64_Packages.lz4'
removed directory '/var/lib/apt/lists/auxfiles'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-backports_InRelease'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-backports_main_binary-amd64_Packages.lz4'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_InRelease'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye-updates_main_binary-amd64_Packages.lz4'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease'
removed '/var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_binary-amd64_Packages.lz4'
removed '/var/lib/apt/lists/lock'
removed directory '/var/lib/apt/lists/partial'
removed '/var/lib/apt/lists/security.debian.org_debian-security_dists_bullseye-security_InRelease'
removed '/var/lib/apt/lists/security.debian.org_debian-security_dists_bullseye-security_main_binary-amd64_Packages.lz4'
Copy old PG_DATA and chown to process user
waiting for server to start...... done
server started
init new db version 13
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "C.UTF-8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /mnt/pg_new/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    /usr/lib/postgresql/13/bin/pg_ctl -D /mnt/pg_new/data/ -l logfile start

waiting for server to start.... done
server started
waiting for server to shut down.... done
server stopped
waiting for server to shut down.... done
server stopped
Start checking of Postgresql pg_upgrade from 12 to 13
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for system-defined composite types in user tables  ok
Checking for reg* data types in user tables                 ok
Checking for contrib/isn with bigint-passing mismatch       ok
Checking for presence of required libraries                 fatal

Your installation references loadable libraries that are missing from the
new installation.  You can add these libraries to the new installation,
or remove the functions using them from the old installation.  A list of
problem libraries is in the file:
    loadable_libraries.txt

Failure, exiting

Thank you.

@markdesilva did you pull the latest image version? It sounds like you did not. I had this error only in old versions and it should already fixed.

@markdesilva did you pull the latest image version? It sounds like you did not. I had this error only in old versions and it should already fixed.

Yes I removed all other images and pulled the latest:
REPOSITORY                            TAG       IMAGE ID       CREATED        SIZE
deineagenturug/pgdb-upgrade-develop   latest    c8c05a59b9c4   11 hours ago   676MB

EDIT: Also the path of the lib is different... Which image you used before from SCS?

Was using debian-master. If the path is wrong, maybe I try looking for the proper library path and soft link before running the script. I will try and report back.
Thank you!

If the path is wrong, maybe I try looking for the proper library path and soft link before running the script. I will try and report back.

Success! I copied the contents of /usr/local/lib to /usr/lib, then I soft linked /usr/lib in /usr/local
cd /usr/local/lib
cp -R * /usr/lib
cd /usr/local
mv lib lib.1
ln -s /usr/lib .

After running the db_upgrade script, it completes without errors!

THX @netbix @markdesilva you help a lot to improve the db_upgrade script. ❤
It only need /usr/lib/libgvm-pg-server symlinked, but I will look how I can find wrong locations and re-set them to be correct.
But I would like to prevent the symlinks, because it will make problems and need changes for the gvm container, which I will prevent.
I'm not so familiar with the postgres DB... I know that some functions that are created by gvmd have the location to /usr/lib/libgvm-pg-server or in your error the /usr/local/lib/libgvm-pg-server as path. To make sure that this will get fixed we have to run there a fix to set the correct path to the libgvm-pg-server else you will have problems with the gvm container, without modifications.

Here a what I found, that use the libgvm-pg-server in database gvmd
CREATE OR REPLACE FUNCTION public.hosts_contains(
	text,
	text)
    RETURNS boolean
    LANGUAGE 'c'
    COST 1
    IMMUTABLE PARALLEL UNSAFE
AS '/usr/lib/libgvm-pg-server', 'sql_hosts_contains'
;

ALTER FUNCTION public.hosts_contains(text, text)
    OWNER TO dba;
CREATE OR REPLACE FUNCTION public.max_hosts(
	text,
	text)
    RETURNS integer
    LANGUAGE 'c'
    COST 1
    VOLATILE PARALLEL UNSAFE
AS '/usr/lib/libgvm-pg-server', 'sql_max_hosts'
;

ALTER FUNCTION public.max_hosts(text, text)
    OWNER TO dba;
CREATE OR REPLACE FUNCTION public.next_time_ical(
	text,
	text)
    RETURNS integer
    LANGUAGE 'c'
    COST 1
    VOLATILE PARALLEL UNSAFE
AS '/usr/lib/libgvm-pg-server', 'sql_next_time_ical'
;

ALTER FUNCTION public.next_time_ical(text, text)
    OWNER TO dba;
CREATE OR REPLACE FUNCTION public.next_time_ical(
	text,
	text,
	integer)
    RETURNS integer
    LANGUAGE 'c'
    COST 1
    VOLATILE PARALLEL UNSAFE
AS '/usr/lib/libgvm-pg-server', 'sql_next_time_ical'
;

ALTER FUNCTION public.next_time_ical(text, text, integer)
    OWNER TO dba;

CREATE OR REPLACE FUNCTION public.regexp(
	text,
	text)
    RETURNS boolean
    LANGUAGE 'c'
    COST 1
    VOLATILE PARALLEL UNSAFE
AS '/usr/lib/libgvm-pg-server', 'sql_regexp'
;

ALTER FUNCTION public.regexp(text, text)
    OWNER TO dba;

@markdesilva @netbix Thanks for your support here and testing.
New Version is ready.
docker pull deineagenturug/pgdb-upgrade-develop:latest
Fixed:

correct old libgvm-pg-server path
fix rm to remove also DOT files from the new DB directory

THX @netbix @markdesilva you help a lot to improve the db_upgrade script. ❤

Happy to help with my limited knowledge!

I'm not so familiar with the postgres DB... I know that some functions that are created by gvmd have the location to /usr/lib/libgvm-pg-server or in your error the /usr/local/lib/libgvm-pg-server as path. To make sure that this will get fixed we have to run there a fix to set the correct path to the libgvm-pg-server else you will have problems with the gvm container, without modifications.

Yes, I had to do the same softlinking when I started the gvm container.
Also when I run the latest gvm container with this upgraded db, I'm getting the error that @netbix was encountering:
createuser: error: creation of new role failed: ERROR:  role "gvm" already exists
But I noticed that .firstrun and .upgrade_to_21.4.0 were not in the upgraded database folder. I touched the files in the database folder and it works from there.
Additionally I see this, which I'm not sure is normal:
2022-04-24 17:47:06,062 INFO spawned: 'rsyslogd' with pid 573
2022-04-24 17:47:06,070 INFO exited: rsyslogd (exit status 1; not expected)
2022-04-24 17:47:07,072 INFO gave up: rsyslogd entered FATAL state, too many start retries too quickly
Checking the processes, rsyslogd is not running.
For upgrading db from a previous gvm to a current one, I think we must have the dot files
/var/lib/gvm/.created_gvm_user (In host ./storage/gvm/.created_gvm_user)
/opt/database/.firstrun (In host ./storage/database/.firstrun)
/opt/database/.upgrade_to_21.4.0 (In host ./storage/database/.upgrade_to_21.4.0)
Then the gvm container runs smooth.
My gvm is now up and running, my reports, tagest, overrides, tasks, etc are all there!
GVMUpdate: started
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+     Greenbone Vulnerability Manager 21.4.5
Manager DB revision 242
Copyright (C) 2009-2021 Greenbone Networks GmbH
License: AGPL-3.0-or-later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
+ Your GVM container is now ready to use!                 +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Testing the scanning now.
Thank you @Dexus!

THX @netbix @markdesilva you help a lot to improve the db_upgrade script. ❤

Happy to help with my limited knowledge!

I'm not so familiar with the postgres DB... I know that some functions that are created by gvmd have the location to /usr/lib/libgvm-pg-server or in your error the /usr/local/lib/libgvm-pg-server as path. To make sure that this will get fixed we have to run there a fix to set the correct path to the libgvm-pg-server else you will have problems with the gvm container, without modifications.

Yes, I had to do the same softlinking when I started the gvm container.
Also when I run the latest gvm container with this upgraded db, I'm getting the error that @netbix was encountering:
createuser: error: creation of new role failed: ERROR: role "gvm" already exists
But I noticed that .firstrun and .upgrade_to_21.4.0 were not in the upgraded database folder. I touched the files in the database folder and it works from there.
Additionally I see this, which I'm not sure is normal:
2022-04-24 17:47:06,062 INFO spawned: 'rsyslogd' with pid 573 2022-04-24 17:47:06,070 INFO exited: rsyslogd (exit status 1; not expected) 2022-04-24 17:47:07,072 INFO gave up: rsyslogd entered FATAL state, too many start retries too quickly
Checking the processes, rsyslogd is not running.
For upgrading db from a previous gvm to a current one, I think we must have the dot files
/var/lib/gvm/.created_gvm_user (In host ./storage/gvm/.created_gvm_user) /opt/database/.firstrun (In host ./storage/database/.firstrun) /opt/database/.upgrade_to_21.4.0 (In host ./storage/database/.upgrade_to_21.4.0)
Then the gvm container runs smooth.
My gvm is now up and running, my reports, tagest, overrides, tasks, etc are all there!
GVMUpdate: started
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+     Greenbone Vulnerability Manager 21.4.5
Manager DB revision 242
Copyright (C) 2009-2021 Greenbone Networks GmbH
License: AGPL-3.0-or-later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
+ Your GVM container is now ready to use!                 +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Testing the scanning now.
Thank you @Dexus!

This should all gone when you run this again with the old db. Also the database should get the corrected path to the libs in the new db.
If you get then again errors let me know.
Maybe the gvmd.log in /var/log/gvm/ will print errors or the postgres logs if there after the db upgrade anything wrong that is not yet in line with the gvm container. Which I hope is not the thing.

One thing: rsyslog (#12) error is already in pipeline > deinegenturug/gvm-develop:latest

Hi @Dexus, I ran the latest deineagenturug/pgdb-upgrade-develop:latest on my old db and it fails with:
Start checking of Postgresql pg_upgrade from 12 to 13
Performing Consistency Checks
-----------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for system-defined composite types in user tables  ok
Checking for reg* data types in user tables                 ok
Checking for contrib/isn with bigint-passing mismatch       ok
Checking for presence of required libraries                 fatal

Your installation references loadable libraries that are missing from the
new installation.  You can add these libraries to the new installation,
or remove the functions using them from the old installation.  A list of
problem libraries is in the file:
    loadable_libraries.txt

Failure, exiting
root@dc2dd6914f3a:/work# more loadable_libraries.txt
could not load library "/usr/local/lib/libgvm-pg-server": ERROR:  could not access file "/usr/local/lib/libgvm-pg-server": No such file or directory
In database: gvmd

Have confirmed I'm running the latest deineagenturug/pgdb-upgrade-develop:
REPOSITORY                            TAG           IMAGE ID       CREATED       SIZE
deineagenturug/pgdb-upgrade-develop   latest        02275e667d97   6 hours ago   676MB

@markdesilva @netbix Thanks for your support here and testing.
New Version is ready.
docker pull deineagenturug/pgdb-upgrade-develop:latest
Fixed:
* correct old `libgvm-pg-server` path

* fix rm to remove also DOT files from the new DB directory

@markdesilva can you please send me a copy from your old DB as a .tar.gz/xz ? https://nc.josef-froehle.de/s/GmMW3txfAW8mCpY
I can so test it local and I would be a bit faster to fix problems.
And don't worry, I will work with it under data protection aspects.As soon as I have done my tests, I delete everything again.

@markdesilva can you please send me a copy from your old DB as a .tar.gz/xz ? https://nc.josef-froehle.de/s/GmMW3txfAW8mCpY I can so test it local and I would be a bit faster to fix problems. And don't worry, I will work with it under data protection aspects.As soon as I have done my tests, I delete everything again.

Sure, the whole thing is 4.3GB though, not sure if it'll go through. Let me try.

Sure, the whole thing is 4.3GB though, not sure if it'll go through. Let me try.

Should not be a problem for my Server, if you have an alternate storage where I can download it, I can do it. Then you can send me a link to github@josef-froehle.de

Sure, the whole thing is 4.3GB though, not sure if it'll go through. Let me try.

Should not be a problem for my Server, if you have an alternate storage where I can download it, I can do it. Then you can send me a link to github@josef-froehle.de

After compression its a few hundred MB. Uploading now.

After compression its a few hundred MB. Uploading now.

Upload is complete. Thanks!

After compression its a few hundred MB. Uploading now.

Upload is complete. Thanks!

Hmm, nothing there. But got an error in the logs. Forgot to set the Upload limit in one config file which now is fixed. Can you re-try?

Hmm, nothing there. But got an error in the logs. Forgot to set the Upload limit in one config file which now is fixed. Can you re-try?

Done! Thanks.

New Version is ready.
docker pull deineagenturug/pgdb-upgrade-develop:latest
Fixed:

correct path of the /usr/lib/libgvm-pg-server.so symlink to /usr/local/lib/libgvm-pg-server.so now with the extension

authors: Dexus LandonStewart markdesilva netbix


text:
Handle internet connection loss

Current behavior when internet is turned off during an upload : app crashes.

It now just displays a "Failed upload" error message.

repo: Deleplace/cool-maze


text:
🛑 cPanel is down

In 13e2de7, cPanel (https://charlie.delta-core.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cPanel is back up in ae0ee95.

repo: Delta-Core/status


text:
standardize reduction factor

          I made this plot of the smooth reduction factor:

how can I add it to equations.qmd? It has been added now.
Originally posted by @SouthEndMusic in https://github.com/Deltares/Ribasim/issues/549#issuecomment-1702971144
Bart made a nicer reduction factor. We should probably use this one for all the reduction_factors, which is now generally a linear reduction. Most are hardcoded to work until 10m3, for Manning it is 10cm waterdepth. Let's see if we can share this and/or make it configurable.

Probably any sigmoid function will work?

Probably. Sigmoid looks more expensive than this, and only approaches the right value, so it is not smooth at the threshold.

Sorry I should've checked #549 better first, it already moves all reduction factors over.

authors: evetion visr

repo: Deltares/Ribasim


text:
Well: Issues when importing steady-state from iMOD5

The GridAgnostic.from_imod5_data is currently is not able to import steady-state wells from a projectfile. I've found the following things which have to be changed:

For associated wells resample_timeseries creates problems in the final pd.merge, where an empty dataframe is generated
Unassociated wells shouldn't get a multi-index with a "time" index in case of steady-state.
_df_groups_to_da_rates shouldn't use a "time" dimension

Fixed in https://github.com/Deltares/imod-python/pull/1169

repo: Deltares/imod-python


text:
Normalize layout presentation from a single point

We should have, on lib/layout/layout.js a single file that takes care of the elements that are currently loaded on the Layout.
Instead of doing something like this on every page load:
  o('body').addClass('forum-new');
  var section = o('section.site-content').empty();
  var view = new View();
  view.appendTo(section[0]);

We should do something like:
import layout from `../lib/layout/layout`
import Sidebar from `../lib/sidebar/sidebar`
import View from `./view`

let sidebarView = new Sidebar({ template: sarasa })
let feedView = new View({ template: sarasa})

// Render the page.
layout.load({
  className: 'feed-page'
  sidebar: sidebarView, // If given `true` it will leave the currently instantiated sidebar (?)
  content: feedView // Will take care un removing the current content and put `feedView` instead
})

And the method load (or wathever) will take care of un-instantiating the current views (if exists) and removing the las className in favor of the new one (and emitting events maybe).

Let's wait until we start using React.js to see how we can rewrite this logic, instead of rewriting it twice

authors: mjlescano slifszyc

repo: DemocracyOS/app


text:
Update Geocoder-ca.rst

add auth parameter to geolytica provider doc (related to #164 and #165)

Thanks!

authors: DenisCarriere porn

repo: DenisCarriere/geocoder


text:
Stdweb 0.4.0

updates to released version of stdweb 0.4

Uh, it looks like you've already started to do this between when I did and got it pushed to github. Bummer :(
Close at will (not sure how to delete it myself)

repo: DenisKolodin/yew


text:
Is the cache not saved when there is a build failure?

When a failure occurs during a build, do the other store paths still get cached or not? I have the impression they're not. The runs I am doing require quite some building so it takes some time to get better insights.
name: "CI using nix"

on:
    push:
      branches:
        - develop
        - main

    pull_request:
      branches:
        - develop
        - main

jobs:
    check:
        runs-on: ubuntu-22.04
        steps:
        - uses: actions/checkout@v3
        - uses: DeterminateSystems/nix-installer-action@main
          with:
            extra-conf: |
              extra-experimental-features = nix-command flakes impure-derivations ca-derivations
        - uses: DeterminateSystems/magic-nix-cache-action@main
        - run: nix flake check

Yep, the completed builds are cached, even on failure.

authors: FRidh grahamc


text:
🛑 LUFi is down

In 267d619, LUFi (https://drop.deuchnord.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LUFi is back up in dce37ff.

repo: Deuchnord/uptime


text:
🛑 Privatebin is down

In 343e74e, Privatebin (https://paste.deuchnord.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Privatebin is back up in 72f5122.


text:
FIPS compliance with AjaxControlToolkit

The AJAX Control Toolkit 4.1.50927
I am looking for any information which could help me understand whether AjaxControlToolkit is FIPS compliant.

Relevant StackOverflow thread:
https://stackoverflow.com/a/33356819

The article is too general and deals with general functionality in the FIPS environment. My interest is more focused on the AjaxControlToolkit component and its FIPS compliance.
If I use the toolkit in my app in the FIPS environment can I claim my app FIPS compliant?

Two AJAX Control Toolkit components use System.Security.Cryptography:

https://github.com/DevExpress/AjaxControlToolkit/blob/02be68ae0dc71eade6d47b846f50a99ace1f7110/AjaxControlToolkit/Gravatar/Gravatar.cs#L130

https://github.com/DevExpress/AjaxControlToolkit/blob/dd212e9a4121be06fb9c8bb66c7b4a436de13476/AjaxControlToolkit/Twitter/TwitterAPI.cs#L113-L115

MD5CryptoServiceProvider is not FIPS compliant. The Gravatar component will throw in a FIPS-enabled environment. Other Toolkit code doesn't directly use any crypto algorithms.

authors: AlekseyMartynov swplok

repo: DevExpress/AjaxControlToolkit


text:
Update onBeforeSend d.ts and docs

Closes #463

Codecov Report
Base: 97.19% // Head: 94.61% // Decreases project coverage by -2.58% :warning:

Coverage data is based on head (56ba8db) compared to base (65af792).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #566      +/-   ##
==========================================
- Coverage   97.19%   94.61%   -2.59%
==========================================
  Files          55        1      -54
  Lines        2243      167    -2076
==========================================
- Hits         2180      158    -2022
+ Misses         63        9      -54

Impacted Files
Coverage Δ

net/DevExtreme.AspNet.Data/ResponseModel/Group.cs

net/DevExtreme.AspNet.Data/ExpressionExecutor.cs

...AspNet.Data/Helpers/DataSourceLoadOptionsParser.cs

...et/DevExtreme.AspNet.Data/DataSourceLoadContext.cs

net/DevExtreme.AspNet.Data/SelectHelper.cs

...DevExtreme.AspNet.Data/Types/AnonType.Generated.cs

...t/DevExtreme.AspNet.Data/Types/AnonTypeAccessor.cs

...t/DevExtreme.AspNet.Data/Aggregation/Aggregator.cs

...xtreme.AspNet.Data/Async/ReflectionAsyncAdapter.cs

net/DevExtreme.AspNet.Data/Aggregation/SumFix.cs

... and 44 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: AlekseyMartynov codecov-commenter


text:
Slow performance for heavy data crunching in a worker

What is your Test Scenario?
I'm trying to write testcafe e2e tests for a fairly data-intensive react/three.js application.
We use web workers heavily to smooth out data loading and crunching.
What is the Current behavior?
A certain step in loading our application takes 15s without testcafe/hammerhead. Running locally, it takes upwards of 10 minutes. Running in our CI environment where we record videos, this can run over an hour and eventually time out.
What is the Expected behavior?
Less overhead!
What is your web application and your TestCafe test code?
I've profiled this and most of the overhead seems to come from hammerhead instrumentation in one of our web workers.
In this worker, we run the marching cubes method from this library: https://github.com/gl-vis/gl-isosurface3d#readme reapeatedly. ~400 times.
As mentioned, in the worker this generally isn't a show stopper. I'm observing 50-80ms per geometry we create in plain chrome. In testcafe, this takes ~1000ms per iteration which adds up.
I can't share my application but the library has some public demos like this: https://gl-vis.github.io/gl-isosurface3d/surface_points.html
I've tested this example in the hammerhead playground and it is significantly slower than plain chrome, roughly in line with the ~10x slowdown I've observed in my application. Their public examples aren't as heavy as my use-case so hard to observe anything as drastic as what I'm reporting.
Reading through the instrumented code from hammerhead, the __get$ and __set$ shims seem like a likely source of the overhead? Not sure on this yet.
Is there a way to prevent hammerhead instrumentation for a single worker or resource in testcafe? Thanks in advance.

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):

Your complete configuration file (if any):

{
    "src": ["test-cafe/*e2e*.ts", "test-cafe/**/*e2e*.ts"],
    "reporter": [
        {
            "name": "spec"
        },
        {
            "name": "xunit",
            "output": "./dist/artifacts/reports/report.xml"
        }
    ],
    "videoPath": "./dist/artifacts/videos",
    "videoOptions": {
        "singleFile": false,
        "pathPattern": "XXX-${TEST_INDEX}-${FILE_INDEX}-${FIXTURE}-${TEST}-${BROWSER}.mp4"
    },
    "screenshots": {
        "path": "./dist/artifacts/screenshots",
        "takeOnFails": true
    }
}

Your complete test report:

Screenshots:

Steps to Reproduce:

Go to my website ...
Execute this command...
See the error...

Your Environment details:

testcafe version: 1.14.0
node.js version:  v12.18.4
command-line arguments:  N/A
browser name and version: Chrome  89.0.4389.114
platform and version: MacOs 10.15.7. Reproducable on debian.
other: WebWorkers are involved. Comlink is used as RPC but I didn't observe too much overhead in worker communication

Please let me know if it's more appropriate to open this ticket against hammerhead itself. Thanks in advance.

Thank you for reporting the issue. I have reproduced it on the example page you provided. We will investigate this case.

Sorry to bug you @VasilyStrelyaev but do you have any sense of where this issue stands in the backlog?

authors: VasilyStrelyaev jacobdr kmannislands

repo: DevExpress/testcafe


text:
Increase hex hex

Increase hex hex

Hi,
DevToysMac is now archived and deprecated. We just released DevToys 2.0 for Windows, Mac and Linux. This issue may or may have not been addressed in the new version. If the issue persist, we encourage to open a new issue on https://github.com/DevToys-app/DevToys or https://github.com/DevToys-app/DevToys.Tools
See more information about DevToys 2.0 here: https://devtoys.app/blog/announcing-devtoys-2.0-preview

authors: iseesec veler

repo: DevToys-app/DevToysMac


text:
Fixes issue #143

Made changes so that when website shifts to Dark-Mode Logo color of Github Changes from black to white in order to improve visibility of the logo.

Please add the screenshot here as well @Vedant-Manjrekar .

Before:

Great @Vedant-Manjrekar ,
Thanks for your contribution ♥.
Don't forget to join us on our Discord server for more Opportunities.

Great @Vedant-Manjrekar , Thanks for your contribution ♥.
Don't forget to join us on our Discord server for more Opportunities.

You are most Welcome @DeveloperAshish8 and it was great working with you.
Surely i will join the discord server.


text:
上传速度跟那些因素有关的，我想优化上传速度的

RT

I've already solved it! But thank you still!

repo: DeveloperLx/LxFTPRequest


text:
Include release notes on release builds

At the moment we link to releases (and their notes), but it's probably more helpful just to include them in the message.

Retiring as won't fix, as this library is coming out of support.

repo: DevicePilot/slack-monorepo-ci-post


text:
Fixed - Improve UI of greeting website

Description
Did some changes in the ui of the greeting web app

Fixes #11
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

Nice👍

Nice👍

Thanks


text:
no luarocks in

Whenever I start a new terminal session it writes
/usr/bin/which: no luarocks in (/home/jonathan/.luaver/lua/5.1.5/bin:/home/jonathan/.nvm/versions/node/v6.4.0/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/jonathan/.local/bin:/home/jonathan/bin)  at the top. My guess is that it can't find luarocks in path.

Does this happen 'just' as you start a new terminal session? Could you show me the contents of your ~/.bashrc or ~/.zshrc file?

I solved it by installing luarocks with my package manager too. It works now
On 5 September 2016 22:07:47 CEST, Dhaval Kapil notifications@github.com wrote:

Does this happen 'just' as you start a new terminal session? Could you
show me the contents of your ~/.bashrc or ~/.zshrc file?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/DhavalKapil/luaver/issues/14#issuecomment-244806043

Even if luarocks is not installed, this error should not come. Anyways, if you face the same error again, feel free to ping here.

repo: DhavalKapil/luaver


text:
Update formatting to match black

Fixes #1130
All developers will also need to re-run ./dls_dev_env.sh (or just confirm their black is up to date):

[x] @DominicOram
[x] @dperl-dls
[x] @olliesilvester
[x] @rtuck99
[x] @noemifrisina
[x] @stan-dot

To test:

Confirm no functional changes
With the latest version of black run black . and confirm nothing changes
Run the pre-commit run --all-files and confirm it passes

Thanks all!

repo: DiamondLightSource/hyperion


text:
Handle timeout localy

This will require the use of another lib. Maybe requests?

Will use requests

repo: Diaoul/subliminal


text:
LegendasTV: Add debug logs when discarding title

Today we discard title without logging anything
ping @ratoaq2

added requested changes

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

Coverage decreased (-0.05%) to 91.854% when pulling 486fa79b7f00fdf7eae3fa73a2bcb3e7ea6f163a on fernandog:feature/ltv_debug_logs into 461d33ce71c9117314e2e86455992e73c8e5aeae on Diaoul:develop.

@Diaoul this one is ready too. Added requested changes. If ok can you merge it too please?

authors: coveralls fernandog


text:
Can't working download at btorrent.xyz

Download can't work at site
https://btorrent.xyz/
Why?
Magnet for try download:
magnet:?xt=urn:btih:B9B757EE76B21E5FD960526E4ADEA81933370301&tr=http%3A%2F%2Fbt2.t-ru.org%2Fann%3Fmagnet&dn=%D0%A5%D0%BE%D1%88%D1%82%D0%B5%D0%B9%D0%BD%20%D0%9B%2C%20%D0%9C%D0%BE%D0%B7%D0%B5%D1%80%20%D0%A0.%20-%20%D0%97%D0%B0%D0%BF%D1%83%D1%81%D0%BA%D0%B0%D0%B5%D0%BC%20Ansible%20%2F%20Hochstain%20L.%20-%20Ansible%3A%20Up%20and%20Running%20%5B2018%2C%20PDF%2C%20RUS%5D

Maybe magnet is not seeded in webrtc network

authors: DiegoRBaquero xintrea

repo: DiegoRBaquero/BTorrent


text:
Feat/recipe details

Required Implementation:

[x] Should display a toggle button that allows for a recipe to be made public or private.
[x] If the recipe is public or the user is the owner of the recipe, should display the recipe details as in the wireframe.
[x] If the user is the owner of the recipe, should lead to the form that allows the user to add a new food.
[x] add bootstrap on the Login Page
[x] add bootstrap on the SignUp Page
[x] Made some additional UI changes on the pages

Hi Buddy! @henask12 ,
Status: required changes 🟠 🟠 🟠
Buddy you projec looks amazing, nice styling, :shipit: Congratulations! 🎉
Highlights

[x]  Amazing styling, great design!
[x]  Add foods if it does not exist
[x]  If food already exists, do not modify the food quantity which is great because we will generate a list in the other section

Pending changes:

[ ]  Toggle button should allow the user to switch a recipe between public or private

Additional notes: Thanks for implementing the design!
Cheers, and Happy coding!👏👏👏
Please, remember to tag me in your question so I can receive the notification._

@Diegogagan2587
Thank you For noticing that i have updated it now as below


text:
Check TensorArray chaining

Statements like tf.while_loop that use TensorArrays need to have chained operations for graph mode: https://github.com/tensorflow/tensorflow/issues/30409#issuecomment-508962873. Check the assignments and correct.

I think that we are already okay here.  For example, the result of the tiles.write(...) command in the following code is returned to the next iteration of the loop, and ultimately is assigned back to the tiles variable.  Similarly, for chunks.write(...) in the second code snippet.
https://github.com/DigitalSlideArchive/histomics_stream/blob/82a72143534a835f0bfa500a1047080a8006a198/histomics_stream/dsm/chunk.py#L79-L97
https://github.com/DigitalSlideArchive/histomics_stream/blob/82a72143534a835f0bfa500a1047080a8006a198/histomics_stream/dsm/wsi.py#L501-L519

authors: Leengit cooperlab


text:
Tiketin poistaminen

Lähettäjällä pitäisi olla mahdollisuus poistaa lähettämänsä tiketti.
Relevantti use-case on sellainen, että esimerkiksi opiskelija tuleekin kysymyksen lähettämisen jälkeen toisiin aatoksiin ja haluaa ettei kysymys päädy opettajille asti luettavaksi.

Backend on tästä jo tehty.

authors: JoniMatias erkkitervoOY

repo: Digivertaisverkko/UKK-tiketit


text:
Chrome Identified this as Malicious?

Why?
This work item was migrated from CodePlex
CodePlex work item ID: '9709'
Vote count: '1'

[Dijji@02/01/2017]
At the moment, Chrome appears to be reporting all downloads from CodePlex as malicious! I’ve picked a few at random, and there have been no exceptions.
Dijji

[Dijji@16/01/2017]
This has now been sorted out at the CodePlex level

[UnknownUser@16/01/2017]

repo: Dijji/FileMeta

license: MS-PL


text:
Apply Property Error message

I run Windows 7 Pro (64 bit) SP1. I have uses FileMeta for several years, and find it to be of great help. I just upgraded from 1.3 to 1.5, but I am sure that has nothing to do with my problem.
I use a backup program, Macrium Reflect, which, when a backup is made, creates  .mrimg files . I wanted to expand what Comments, Title, etc. they allow, so thought I would apply FileMeta.
FileMeta Association Manager lists the file extension and program correctly so I was able to set up a File Meta Handler, using a Simple profile. That portion went just fine.
When I open Properties for a specific .mrimg file, all of the items listed under Description (on the Details tab) can be modifed, so FileMeta seems to be working. But when I try to save that information, I get a 'Apply Property Error' screen, as shown on the attached file. I tried to accomplish this several times, and on 3 different .mrimg files, but always got the same Apply Property Error screen. I note that the icon on the screen is the same as Macrium uses, so the error message may be generated from them.
Have you ever seen anything like this, and if so, is there a workaround? I have not yet contacted Macrium; I thought I would start with you first.
Harry

I notice that the error message talks about a “password protected file”. So I’m guessing that the problem relates to file permissions. As the property store used by File Meta is provided by NTFS, file permissions will inhibit property updates just as they inhibit file updates.
Dijji

authors: Dijji githmw