Expose dns server on tcp as well as udp

Issue was discovered when testing scope with master vs 1.0 branches.
@inercia, Any reason not to do this? AFAICT it initializes the same thing on tcp and udp, but just doesn't expose the tcp.

@paulbellamy This is odd. We should definitively expose both ports.

LGTM.

@paulbellamy please describe what problem this is solving. Presumably something to do with using weavedns outside of weave.

The new scope script uses the open tcp port 53 to detect weave DNS, as we can't use the presence of the weavedns container anymore.

The new scope script uses the open tcp port 53 to detect weave DNS

That seems like it would be rather fragile.

The new scope script uses the open tcp port 53 to detect weave DNS

That seems like it would be rather fragile.

Checking that something is listening on port 53 may give you false positives. If the next thing you do is to attempt a WeaveDNS operation -- e.g., adding an entry -- with the expectation that it could fail if WeaveDNS is not actually running, then why don't you just attempt that operation in the first place?

Surely there is a real bug here, affecting weave. I would expect DNS resolution to be unable to retrieve large answers. Alas we have a test for that - 295_dns_large_response.sh - which succeeds. Something doesn't add up here.

The port mapping was missing from the 1.0 branch, but present on master, where the 295_dns_large_responses.sh test exists.  So the presence of the test doesn't imply there is definitely a bug.
Also, 1.0 only ever gave 'small' answers, so its unlikely anyone ever hit this.

Also, 1.0 only ever gave 'small' answers, so its unlikely anyone ever hit this.

Except for recursive queries.

#1333.
The change lgtm. We could add a test, along the lines of #1333, but that is superfluous on master, so let's not bother.


error on init repo for google cloud storage on restic 11 but works in restic 10

restic version
restic 0.11.0 compiled with go1.15.3 on linux/amd64
How did you run restic exactly?
restic -r gs:bucket/folder init
Expected behavior
repo is initialized on restic 11.0 and 10.0
Actual behavior
Fatal: create repository at gs:bucket:/folder failed: service.Buckets.Get: googleapi: Error 403<EMAIL_ADDRESS>does not have storage.buckets.get access to the Google Cloud Storage bucket., forbidden
but on 10.0 it works

Hm, that's odd. We have updated the library to access GCS between 0.10.0 and 0.11.0, so that could be it (in PR #2974). Can you spot any differences which may explain what you're seeing?
From what I can see nothing interesting has changed. Are you able to run a git bisect between 0.10.0 and 0.11.0?

yup, i think i found in https://github.com/restic/restic/pull/2974 what could be causing it. i'll debug next chance i get and try and confirm the resolution.

Nice, looking forward to what you find!

for some context, the service account i'm using has storage.objects.* permissions but does not have storage.buckets.get permission. the reason being that i don't want the service account to be able to create new buckets, just to create objects in an existing bucket (including initializing new restic repositories in the bucket).
in restic 11.0 there is new behavior in how bucket lookup failures are handled. if a bucket can not be looked up (which happens for service accounts that do not have storage.buckets.get permission), then it fails to create the repository.
however, in restic 10.0, when a bucket could not be looked up, it would continue ambiguously forward and attempt to create an object in the bucket. if that works, all is well.
if you wanted to preserve the behavior of restic 10.0, we can modify Create() in internal/backend/gs/gs.go to the following
  func Create(cfg Config, rt http.RoundTripper) (restic.Backend, error) {
    be, err := open(cfg, rt)
    if err != nil {
      return nil, errors.Wrap(err, "open")
    }

    // Try to determine if the bucket exists. If it does not, try to create it.
    ctx := context.Background()
    exists, err := be.bucketExists(ctx, be.bucket)
    if err != nil {
      // return nil, errors.Wrap(err, "service.Buckets.Get")

      /*------------------------------------------------------------------
      +  the service account might still have object permissions
      + just continue forward ambiguously till the next storage call
      ----------------------------------------------------------------------*/

      return be, nil
    }

    if !exists {
      // Bucket doesn't exist, try to create it.
      if err := be.bucket.Create(ctx, be.projectID, nil); err != nil {
        // Always an error, as the bucket definitely doesn't exist.
        return nil, errors.Wrap(err, "service.Buckets.Insert")
      }

    }

    return be, nil
  }

so in conclusion, there was a behavior change. either the behavior is desired and the documentation could be updated, or the above function could be modified to preserve the behavior.
which would you prefer @fd0 ?
i wouldn't mind putting together a small PR for this given my current investigation.

Cool, thanks for debugging! Would you mind finding out which error is returned by be.bucketExists()? You can add the following code within the if err != nil:
    exists, err := be.bucketExists(ctx, be.bucket)
    if err != nil {
        fmt.Fprintf(os.Stderr, "bucketExists() returned error %T %#v\n", err, err)
    }

This will print the error's type (via %T) and the Go representation of it. Maybe we can check for a specific error instead of just ignoring the error.

It's probably a googleapi.Error which has a field Code containing the HTTP status. The ErrBucketNotExist return value is created in the gcs library by checking that status code against http.StatusNotFound. With missing permissions I'd assume the status code to be http.StatusForbidden (which was also returned prior to merging #2974)

type: googleapi.Error
code: 403
i'll put together a PR catching for this specific error and not blocking. this way, a service account need only object permissions to be able to initialize a repository.
i've also tested trying to create a repository in a new bucket and restic appropriately errors with a message informing the user that the service account needs the service.Bucket.create permissions.

i have a PR out for this, but i could use some guidance if i were to write a unit test for one specific backend. the test suite seems set up to run a barrage of tests against all the backends, ensuring a basic contract.


MB-6917 Add PaymentServiceItemParams to GHC API

Description
A TIO needs to see how weights factor into the pricing of service items
so that they can understand how the price was determined.
This information comes from the payment_service_item_params and
service_item_param_keys tables.
The GHC YAML file already included the necessary fields in the
definition of the getPaymentRequestsForMove endpoint via the
definitions for
PaymentRequest->PaymentServiceItem->PaymentServiceItemParam
To add these to the payload, I copied the functions from the Prime API,
and then I updated the FetchPaymentRequestListByMove function to
perform the necessary joins and eager loading to fetch the data from the
DB.
I used TDD to write a failing test first, and converted the existing
TestGetPaymentRequestsForMoveHandler test to an integration test that
hits the DB, as opposed to using mocks. To figure out how to properly
set up the DB with all the necessary data, I looked up existing usage of
paymentServiceItemParams in our codebase, and found one in the Prime
API's pkg/handlers/primeapi/move_task_order_test.go. I copied that
over and added tests for the Key and Value fields in the payload.
It's not clear from the JIRA issue what the payload needs to contain for
the client to display the information to the TIO. If it needs the full
paylod as defined in the PaymentServiceItemParam section of the YAML,
then I'll add more tests for the rest of the payload.
Reviewer Notes
Note that this PR only implements the backend portion of this feature. There is a separate unscheduled story (in TTV's March Slice) for the frontend portion.
Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - Regular Expression Denial of Service
Package three
Patched in >=0.125.0
Dependency of @trussworks/react-file-viewer
Path @trussworks/react-file-viewer > three
More info https://npmjs.com/advisories/1639
1 high vulnerabilities and 0 critical vulnerabilities found

Messages

:book:
:link: MB-6917

  Generated by :no_entry_sign: dangerJS against 9a5dcc0ab419c4e08bbe691fa7e55b48cb417fdc

This is looking good. I think for this to show up on the request we're making on the payment request overview that we'll also need to reference the PaymentServiceItems that you've updated in the PaymentRequest payload.

@Ryan-Koch I think this is the only Move so far in Devseed that has a payment request with service item params: Move ID "7cbe57ba-fd3a-45a7-aa9a-1970f1908ae7"

@Ryan-Koch I think this is the only Move so far in Devseed that has a payment request with service item params: Move ID "7cbe57ba-fd3a-45a7-aa9a-1970f1908ae7"

Thanks for the ID! I see the things included in the payload now for that move.


Added new errors for dealing with closing stdin

This adds errors ErrComputeSystemDoesNotExist and ErrElementNotFound. They are needed to handle the error cases when closing stdin.
/cc @swernli
Signed-off-by: Darren Stahl<EMAIL_ADDRESS>

Closing this PR in favour of a new PR that has much larger changes to errors which will help with future extensions.


Add gifs for Genuary 15 & 16 and resize images to 500x500

I have replaced the images for day 15 & 16 with GIFs and resized everything to have a width of 500px.  I am not sure if others would be better as GIFS but I think  these 2 are  better animated.

I think the custom image styles are ignored by the GitHub renderer since it applies its own styles to all markdown images.
Also, just in case, the GIFs can also be added in <img /> tags like other images to have uniform width.

Redoing with grid.


cri: remove v1alpha1 codebase

Signed-off-by: Wei Fu<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
time to remove v1alpha1 cri
Ⅱ. Does this pull request fix one issue?

fix #2689
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
none
Ⅳ. Describe how to verify it
CI
Ⅴ. Special notes for reviews

please also remove cri alphav1 related code here
@fuweid  https://github.com/alibaba/pouch/blob/master/travis_ci.sh#L63

Could we kick the ball? @fuweid @zhuangqh

@allencloud @zhuangqh
sorry for the late reply. please take a look. If it is good to go, we can move it on.

I would like to invite @zhuangqh to review and merge if reasonable.


Create travis build + deploy to dev instance

https://github.com/ZGIS/smart-csw-ingester/commit/2f11c6a3260ef06cb8207766844855108137bd67

Travis Build is done. The deploy to dev instance requirement is a whole other can of worms.

admin app receives webhook and issues gke container builder with the prepared source package from the the travis build. the deployment is currently requiring manual activation (click in the web gui) through the admin app, but could also be automated . the process is now complete pipeline from github to travis to gce/gke


OLED 0.96

hi all,
I try with to run Helloworld program and it’s not work well

i have only warning :

and in TERMINAL ;

Hi, a few things you can try:

Set the SSD1306_I2C_COMMAND_MODE to 0;
I2CDisplayWidth = 128
I2CDisplayHeight = 64

@JayEnaR
that not solve problem


how do you get all the potential processed transcripts

Hello,
I'm trying to find novel transcripts so I don't use the -e option. Using the verbose option, I see in the output that it says
[10/07 16:20:42]^bundle NC_001538:1-5153 done (16 processed potential transcripts).
but it only outputs 7 transcripts in the GTF file.  How do I get it to output all 16 potential transcripts?  Thank you,

There is no option in StringTie to output those extra potential "transcripts". Those 16 potential transcripts are just paths in the splicing graph that StringTie considers. In this case, once the reads are allocated to the top 7 transcripts there are not enough remaining reads to support the 9 other paths, and StringTie discards them.


installing RLC-510WA

hi after installing the integration I get this error in logs
Logger: homeassistant.config_entries
Source: helpers/network.py:123
First occurred: 11:20:20 AM (1 occurrences)
Last logged: 11:20:20 AM

Error setting up entry Backyard for reolink_dev
Traceback (most recent call last):
  File "/config/custom_components/reolink_dev/__init__.py", line 77, in async_setup_entry
    push = hass.data[DOMAIN][base.push_manager]
KeyError: 'push_manager-ec71db731679'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 248, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/config/custom_components/reolink_dev/__init__.py", line 86, in async_setup_entry
    await push.subscribe(base.event_id)
  File "/config/custom_components/reolink_dev/base.py", line 302, in subscribe
    get_url(self._hass, prefer_external=False),
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 83, in get_url
    request_host = _get_request_host()
  File "/usr/src/homeassistant/homeassistant/helpers/network.py", line 123, in _get_request_host
    raise NoURLAvailableError
homeassistant.helpers.network.NoURLAvailableError

what should I do? I don't have the device or entity after the installation

I've had the same problem. Try setting "Internal URL" in "Configuration" -> "General". I've also set "External URL", but I think this is not needed.

WORKED LIKE A  CHARM
@mateuszkielar


Create etu.u-bordeaux-montaigne.fr

@bastienrobert Could you please answer this comment with an actual domain name of the institution which you wish to add to this repository? The file path in your request is in wrong format. Please read instructions at the bottom of this page and modify the request accordingly. Thank you for the understanding!

Hey, #2703 take the relay.
I close the Issue.


Rebuild starting web project with the latest Next.js build

Rebuild the honeypots web project from scratch with the latest Next.js release.

Issue resolved with new default branch


Add Codes for the editorials

Some editorials doesn't show the code, since they are hidden inside scrolling. Without editorial code, solutions doesn't help that much.
maybe you can hit the copy button using selenium, and copy those codes, and provide along with the screenshot for each problem to refer to.

@akhilkammila  if you still have the leetcode premium account, can you run this python script ?
This I created by reverse engineering the API calls made in the editorial page to get the editorial solution codes, this gets those codes, and puts them in separate files, for all the approaches, and for all the languages..
Let me know if you face any issues, since some file paths and other things might needs to be changed.

@raghavrambo007
Nice script, it seems to work decently well. Appreciate it.
For some problems it doesn't work. Problem 3, for example, throws an exception because response1.text is just {"data":{"question":{"solution":{"content":null}}}}.
I'll run the script for now though and push the files. Thx man

Hey @akhilkammila , thanks a lot!
Maybe some problems use some other json response structure.
if we can write those problems which doesnt work in the except section to some csv, could look into them.
Also, looking forward to integrate this with your project, with all those docker, and proper foldering out the output and stuff.
I am not much familiar with docker, let me know how we can go about that.

Hm yeah. The foldering isn't that hard, I just made a quick change to the script and it should put it into folders. The main point of the folders is just because github doesn't display more than 1000 subitems per folder.
I think the main thing to do for integration is create something that formats the files into the ReadMe (like whats under the readme-formatter folder). So people can just go to the ReadMe and click links and it'll open the link to the problem. It'd be great if you could help with that, if not its aight
Also don't worry about Docker. It runs fine locally, Docker is just for containerization (so you can run it on AWS EC2 or something). I don't really use the docker container most of the time.
I'll push the editorial code once the script finishes running. Lmk if u need anything, I'm a bit too busy for like big stuff right now cuz of school and recruiting, but I can help. Thx!

Speaking on this, the editorials sometimes have video solutions. Is it possible to scrap those videos?

@akhilkammila , sure would do the readme formatter thing, thats just simple string concatenation it seems.
Once you push the codes data, would create that based on the forder structure.
Thanks

@raghavrambo007 Pushed it, thx. Unfortunately it looks like a good amount failed, but it got a lot of the editorial code.
@unable8759 Its probably not feasible. Even if we could get them, would have to store it somewhere. Tbh the videos aren't that useful though, its the same content plus some examples and stuff. I don't watch them I just use the editorials.

@akhilkammila , there was a bug in the script. Basically there was no default return statement for the getExt method in the previous one. so if there is some code language which I didnt mentioned, it would fail with exception.
I fixed it, can you merge this PR ( #3 )?
Also when you get time can you rerun this to check if there is any reduction in number of errors this time?

@raghavrambo007 does this also fix the editorials that didn't work? Or is it too hard to debug why some fail?

@raghavrambo007 Hey! I just ran the new script. It seems to have fixed the issue for a few editorials, but a lot of them still don't work (like #3 for example). I pushed the new changes tho, thx. Appreciate ur help
@unable8759 Nah this is unrelated to the screenshots. To get screenshots for the missing problems I need to rescrape the problems and rerun my screenshotter. I'll do that in a few weeks when I have more time, sry.

@akhilkammila do you have neetcode by any chance? There are courses in there which have articles similar to this leetcode screenshotter.

Hi @akhilkammila  @raghavrambo007 , please can you add remaining Editorial Codes please. Like i am solving interview 150 questions for those i don't think codes are there..i didn't find many..
like house robber etc..

I think the API in the script is correct, but the login session header is missing
However, I don't have a premium account. so it's hard to fix the error.


CVE-2024-27280

The AWS CPI seems to be affected by https://www.ruby-lang.org/en/news/2024/03/21/buffer-overread-cve-2024-27280
Even though the issue doesn't seem to be critical we should update the used Ruby version to 3.2.3

fixed with https://github.com/cloudfoundry/bosh-aws-cpi-release/pull/159


Detect and use yadm when makes sense

Is your feature request related to a problem? Please describe.
I was planning to move to gitsigns, but coming from mhinz/vim-signify, I noticed that it misses yadm support.
Describe the solution you'd like
I know that gitsigns is more tied to git than signify, but yadm is only a git wrapper, so it's enough to:

Detect when the current file is being managed by yadm .
Call git with the GIT_DIR set as the output of yadm enter 'echo $GIT_DIR' in that case.

I've never used yadm so I have s couple of questions.

How can you detect if a file is managed by yadm?
What does yadm support specifically mean? If it is just a git wrapper then why isn't the current git support enough? All my dotfiles are symlinks to a dotfile git workspace and I specifically made gitsigns resolve symlinks so signs work. How is yadm different?

If there isn't too much collateral then I'm happy to add support but I'll need precise details so I know what need to implement.

Please try #84

@lewis6991  #84  works well, but I'm losing the new fixes and features, when will it get merged?

Sorry, this has been on my todo list for a while. The PR needs quite a bit of work still. I'll try and work on it soon.

Once #137 goes in, adding yadm support will be trivial. I basically needed to refactor so every git command has the gitdir and toplevel passed in but done in a way that doesn't cause bloated function arguments on every git command.


Gh 306 spark operations

The travis fix I put doesn't return the error code properly so the build is failing but it isn't getting reported correctly. I'll have a look at this now.
The errors are due to the new Closable Iterables being merged in (gh-235). Either we need to change your operation handlers to return closable iterables or implement gh-396 first.


Build pipeline

Created build pipeline.

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

This was an accident.


Viewer docs for viewing Gists are incomplete.

The Gist URL template here seems to be incomplete -- I can't get this to work without adding an extra filename= parameter
Compare:
      http://viewer.gorilla-repl.org/view.html?source=gist&id=3bdede1df8232d255e35&filename=biodatoms-demo

with:
     http://viewer.gorilla-repl.org/view.html?source=gist&id=3bdede1df8232d255e35

In the latter case, there's also an error in the JS console:
   Uncaught TypeError: Cannot read property 'content' of undefined

I'm also wondering if it might be worth defaulting the filename for gists containing only one file.

Have updated the docs, and made single-file gists default to the only file, as suggested. Thanks for the report :-)
BTW, that worksheet you posted a link to looks neat :-)


[BUG] - Node startup takes too long even with mostly-up-to-date ledger database

cardano-node 1.13.0 - darwin-x86_64 - ghc-8.6
git rev a1dd8ebb7b0a959619abceb34ef1044b9ea696b0
Private network (guild-operators, using settings referenced here - https://github.com/cardano-community/guild-operators/tree/master/files/ptn0/files)
Correctly stopped passive node that was exited from LiveView via 'Q' button press earlier in the day subsequently took about 50 minutes after launch to show non-zero epoch/slot/block number information.
Majority of this time was supposedly spent incrementally replaying blocks, e.g. starting with
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceLedgerReplayEvent.ReplayedBlock","slot":20,"tip":265848},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Info","thread":"32"}
right until
{"at":"2020-06-20T06:52:10.47Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceLedgerReplayEvent.ReplayedBlock","slot":265848,"tip":265848},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Info","thread":"32"}
after which the ledger DB opening commenced (which itself took about 4 minutes):
{"at":"2020-06-20T06:52:10.47Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceOpenEvent.OpenedLgrDB"},"app":[],"msg":"","pid":"94674","loc":null,"host":"YARRISMA","sev":"Info","thread":"32"}
Can you please shed some light on how to prevent this from happening and have node start in timely fashion?
Worth noting that the log file started with the following:
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceOpenEvent.OpenedVolDB"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Info","thread":"32"}
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"snapshot":{"snapshot":"DiskSnapshot 70","kind":"snapshot"},"kind":"TraceLedgerEvent.InvalidSnapshot","failure":"InitFailureRead (ReadFailed (DeserialiseFailure 261 "An error occured while decoding Negative Coin.\nError: -2800202946253107677"))"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Error","thread":"32"}
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"snapshot":{"snapshot":"DiskSnapshot 69","kind":"snapshot"},"kind":"TraceLedgerEvent.InvalidSnapshot","failure":"InitFailureRead (ReadFailed (DeserialiseFailure 262 "An error occured while decoding Negative Coin.\nError: -2797174925787671926"))"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Error","thread":"32"}
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceLedgerReplayEvent.ReplayFromGenesis"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Info","thread":"32"}

Solved. Had to update the config files. It is in all probability due to the wrong version of ff-genesis.json file. Works now ...

Solved. Had to update the config files. It is in all probability due to the wrong version of ff-genesis.json file. Works now ...

Please don't muddy up the waters, there's nothing solved about this issue that I reported...

Solved. Had to update the config files. It is in all probability due to the wrong version of ff-genesis.json file. Works now ...

Please don't muddy up the waters, there's nothing solved about this issue that I reported...

Sorry...my fault. Mixed it up with my issues...

{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"snapshot":{"snapshot":"DiskSnapshot 70","kind":"snapshot"},"kind":"TraceLedgerEvent.InvalidSnapshot","failure":"InitFailureRead (ReadFailed (DeserialiseFailure 261 "An error occured while decoding Negative Coin.\nError: -2800202946253107677"))"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Error","thread":"32"}
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"snapshot":{"snapshot":"DiskSnapshot 69","kind":"snapshot"},"kind":"TraceLedgerEvent.InvalidSnapshot","failure":"InitFailureRead (ReadFailed (DeserialiseFailure 262 "An error occured while decoding Negative Coin.\nError: -2797174925787671926"))"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Error","thread":"32"}
{"at":"2020-06-20T06:03:18.43Z","env":"1.13.0:a1dd8","ns":["cardano.node.ChainDB"],"data":{"kind":"TraceLedgerReplayEvent.ReplayFromGenesis"},"app":[],"msg":"","pid":"94674","loc":null,"host":"MYHOST","sev":"Info","thread":"32"}

This indicates the following happened: when you shut down the node the last time, its ledger contained a negative Coin somewhere. This should not happen, and is something for the ledger-specs team should look into, cc: @JaredCorduan (or maybe it has been fixed recently?).
A snapshot of the ledger (the UTxO and other state) is written to disk so that the next time you start the node, it can just read it and quickly continue working (with a little replay of blocks). That negative Coin was serialised to disk without causing errors (no validation should be needed, as it should be impossible to have a negative Coin), but when it is deserialised, it is rejected, as it should not be negative. That's what the trace messages above say: the ledger snapshots on disk (we take multiple) are both invalid because they can't be deserialised because of a negative Coin value. This means we have no choice but to reconstruct the ledger state by replaying all blocks in the database against the genesis UTxO. As this requires reading and validating all blocks in the database, this takes a while.

This is not really a performance issue - the node is correctly validating the chain, as it should when it discovers an inconsistency (here a negative Coin value).  We should make sure we understand why we have this inconsistency.

Thank you for reporting this @bergr01 ! I can't tell from the errors below where a negative coin is appearing, but I have a good guess. There is one place in the ledger state where negative coins are used, namely in reward updates (we record, for instance, that the reserves will be reduced by X lovelace when the update is applied, etc). We had not originally planned on this state ever being serialized.
I think that the correct thing to do is to create a new "coin difference" type to be used for this situation, which has a different serialization and allows for negatives.

would y'all be willing to try to recreate this issue using the 1.15.0 tag? the logs from cardano-cli shelley query ledger-state will now give us some very helpful new information.

We have been unable to reproduce this issue.  It may be related to some specific configuration settings?  I am closing it for now.


Take upstream java fixes and put them here

Got some advice from some Puppetlabs people on how to do facts better! :)

@dgoodlad this should fix the facts and it adds in a fact for major number (ie. 7 or 8), so we can do some work toward #33 :smile:

Moved to #52


fixed typo and amended wrong page reference text

Changes in this PR:

Fixed a typo tet instead of text.
Fixed where a wrong page was references near a link

Trello card / Rollbar error (etc)
https://trello.com/c/dFWyXZKK/972-pui-how-to-search-content-refresh
Screenshots of UI changes:
Before

After

[ ] Requires env variable(s) to be updated

Codecov Report

Merging #781 (261a90a) into main (269f661) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #781   +/-   ##
=======================================
  Coverage   93.06%   93.06%
=======================================
  Files          30       30
  Lines        1226     1226
  Branches       62       62
=======================================
  Hits         1141     1141
  Misses         68       68
  Partials       17       17

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
13 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
57 seconds
clamav-scan

✅ Succeeded
14 seconds
sanity-inspect-image

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
7 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary


A new hope.

Restarts the development of robotic avatar with some new goals:

Simple just works code.
The robot should host its own webapp.
Implement one device at the time both in code and in hardware.
Try to reduce dependencies and complexity.

Main tasks:

[x] #139
[ ] #146
[ ] Robot arm without ROS.
[ ] Drive controller.
[ ] Clean up the repo.

The hope was killed by AI.


add LICENSE

The design is amazing, congratulations on publishing it.
I only missed a license in the project. What do you think about this?

@gutierri - I haven't made any updates in a long time but feel free to put through a PR! Less restrictive the better.


⚠ Bofrost.fr has degraded performance

In ab1a63d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1271 ms

Resolved: Bofrost.fr performance has improved in e821bd1 after 13 minutes.


Fix link

closes https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/issues/2810

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@scanum Can you ask for merge? Thank you!

@kaarins PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@kaarins Can you kindly review and merge, please? Thanks

@kaarins Can this be merged? thank you

Already fixed!


Configuration testing suggestion

I'm one many users who use Hakari in anger, because it's shipped with other frameworks. I sympathise with the developers who put in a lot of hardwork and are consistently met with a never-ending barrage of non-buggy, configuration related issues being raised on your github issues board amongst other places. Unfortunately Hakari seems to be very configuration dependant, possibly a side-effect of Hakari's goal to be super fast. It's inclusion by other frameworks aim to pass on that hard work to casual end users. DB connection limits, authorisation issues, general network issues are hairy for everyone to debug but certainly many appear to be overflowing here.
For your own sake (aka to reduce bug reports), have you considered writing any new tools? For example a command line app packaged as a jar file that might present valid options, test the network connection, simulate some moderate usage, warn about connection limits, print supporting diagnostics and generate sample code or config?
If it helps your users save time, make fewer mistakes, doesn't require rewriting libraries or error messages and reduces the number of issues raised on your board, it could be a worthwhile investment.
Anyway just a thought. Do you have anything like this already?

I'm frankly surprised by the negativity that some users have shown toward HikariCP in the issue tracker. For basic use cases it shouldn't be hard to set up. Just use the default  static pool size of 10 and set the maxLifetime to something value that isn't longer than the database's and infrastructure's connection time limit. And even for the maxLifetime, if you don't know what the infrastructure's account connection time limit really is, you can just leave this setting at the default of 30 minutes and wait for a timeout to happen. When the timeout happens just reduce the time a little and repeat until you no longer get timeouts.
Doing just this should handle 95% of use cases. Most people's issues come from trying to configure more than this when they don't have to. In the case that the environment requires more than this, the assumption is that the developer configuring it would absolutely know better than HikariCP could know.
In the case that the default pool size of 10 causes problems, it is likely that the application is not releasing connections back to the pool in a timely manner as expected. Or if the database is running out of connections it is likely that the maximumPoolSize was increased beyond what it should have been. In the case that more than 10 are needed, then it is likely a fairly large scale deployment, and I would expect whoever is managing the system to have the expertise to do the investigation to see what settings would work best.
As far as I can tell HikariCP has the least amount of configuration technically possible. The only properties that are really necessary are the datasource specific properties (datasource class, host, username, password, etc). I challenge you to find another connection pool that requires fewer properties to do the same thing.
The vast majority of issues reported to this project are from people who have simply failed to call close() in a finally or are doing something strange like calling getConnection() once and then reusing it for multiple separate operations over a long period of time. These mistakes are guaranteed to result in what looks like timeouts, because the system times out waiting on a new connection which is waiting on the application to release the previous one. No command line tool would be able to provide a configuration to protect against this kind of mistake (unless such a tool was a code linter on the user's application's code).
Another large bulk of the issues are issues specific to data source implementations that would be more appropriately opened against those specific projects. The configuration properties for a specific data source are not HikariCP's concern, they're just passed through.
Additionally, one more class of issues that I've seen on here are non-standard setups where one application uses multiple connection pools. This kind of thing, while being relatively straightforward to set up, does require slightly more in-depth knowledge. But it certainly shouldn't be needed in the vast majority of systems.
I don't think any command line tool could possible make HikariCP configuration any simpler. In the simple cases, just use the defaults and don't change anything. In the case that that is not sufficient, then the developer would need to know specifically why it isn't sufficient anyway, and a tool isn't going to be able to determine what that is.
I would wonder if maybe these frameworks you mention that ship with HikariCP have set some unreasonable defaults that are what are actually causing the pain. If you have specific examples of a framework and configurations that aren't working, it would be nice to hear them so that we could address a specific configuration problem. Maybe there really is some common configuration mistake that causes confusing errors and wastes user's time. If there is then we should address those specific issues.
One last thing to note. HikariCP is used by a very very large number of systems. So a single issue opened in github probably only represents a very small fraction of users. It is probable that 99.99% of users haven't run into any problem at all. Those users don't open tickets saying "It works fine for me!".

I think hikaricp is simplistic enough. Using the framework doesn't mean nothing to understand.

@lfbayer, It works fine for me!
There I said it. ;)


Create Celestial

celestial - webapp that analyzes events for display to user

Currently waiting for logo design to come back from third-party. Celestial web UI design will be based off of that, and mockup can begin once we have it.


Grammatical changes to Sign-a-package

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@MariusVolkhart thank you for catching that!