Tell users where to place the application directory

Using "Extract All..." with the default options will extract the files to the Downloads folder. Many users will do exactly that and end up running Mattermost from there downloads folder. Not a good thing. These instructions tell users where to extract the files.
Perhaps in a future release these instructions can be reduced to run a batch script or installer.

Are you recommending installing to AppData instead of …Programs due to the fact that you don't need admin privileges?

I don't care, so no. The app should work at the desired directory.
btw, I usually create D:\Program Files\... for this kind of apps. Where is an appropriate directory for the app which has no installer?

@yuya-oc This commit is too master so I hadn't considered it specific to anyone version, which is why I continued using the pre-existing convention of dot-dot-dot (...). Providing an example folder name isn't a bad idea.
@GhostLyrics and @yuya-oc Since there is no installer at this time, the target audience I have in mind for these instructions are users who may not know where to place application files and likely have no idea why you might choose one folder over another. This is why I opted for \AppData\Local over Program Files or Program Files (x86). With Program Files and Program Files (x86) I would have to explain if you are on a 64-bit machine installing the 32-bit version then place it in Program Files (x86), if you are on a 64-bit machine installing the 64-bit version then use the Program Files folder, if you are installing the 32-bit version...blah blah blah. Too much info.  Install problems will be localized.
More advanced users or administrators will feel comfortable ignoring the advice here and use Program Files or Program Files (x86) when that makes sense, and take steps to add shortcuts to everyone's start menu, desktop, etc. which I believe does require admin privileges.

@jeremycook I see.


Duplicate entity_id

Hi,
All version up to date, on raspberry pi , HA OS.
Here is my configuration :
type: vertical-stack
cards:
  - type: vertical-stack
    cards:
      - type: custom:button-card
        color_type: label-card
        color: rgb(238, 233, 119)
        name: Lumieres Allumées
        aspect_ratio: 15
      - type: custom:battery-state-card
        color_gradient:
          - '#ff0000'
          - '#ffff00'
          - '#00ff00'
        icon: mdi:lightbulb-outline
        bulk_rename:
          - from: ZIG_relais_
            to: ''
          - from: ZIG_LED_Denis
            to: LED Bureau Denis
          - from: Yeelight Ceiling4 0x112f9312 Ambilight
            to: Plafonnier Salle a Manger Ambilight
          - from: ZIG-
            to: ''
        sort_by_level: asc
        collapse: 4
        filter:
          include:
            - name: entity_id
              value: switch.zig_relais*
            - name: entity_id
              value: light.*
          exclude:
            - name: state
              value: 'Off'
              operator: '='
            - name: state
              value: Unavailable
              operator: '='
            - name: entity_id
              value: '*p101*'
            - name: entity_id
              value: switch.zig_relais_denis

And here is the result :

Note 1 : Without the bulk_rename block, same result ( with different name of course ) ( capture is without to show the real name )
Note 2 : Strange behaviour, the state Off in exclude work, but state On in include doesn't.
Thanks for helping !

Can you please print the entity_id as a secondary info and take one more screenshot?

Ho ! Nice trick the secondary info, i have some duplicate entry, strange because don't know from where they are 👍
HA entity :

ZIIGBEE MQTT :

battery_state :

Problem solved after restarting ! Thanks for the tips !


As a player, I want to have the possibility to go back to the home screen in order to start  over.

Acceptance Criteria:

[x] If the user decides to finish the current game, they can click a button to go back to the home screen

Development Tasks:

[x] sopra-fs23-group-10/sopra-fs23-group-10-client#27
[x] sopra-fs23-group-10/sopra-fs23-group-10-server#73

All dev tasks are completed and acceptance criterias are met. Issue is therefore closed.


[FLINK-27299][Runtime/Configuration] flink parsing parameter bug fixed.

What is the purpose of the change
When I am running a flink job, I specify a running parameter with a "#" sign in it. The parsing fails.
e.g: flink run com.myJob --sink.password db@123#123
only parse the content in front of "#", after reading the source code It is found that the parameters are intercepted according to "#" in the loadYAMLResource method of GlobalConfiguration. This part needs to be improved
Brief change log

before: line.split("#", 2)  after: line.split("\\s+#", 2) Following yaml's parameter parsing rules, the content after " #" ( space + #) is the real comment part, which should be discarded when parsing parameters

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): don't know
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature?  no
If yes, how is the feature documented?  not applicable

@wolfboys , the change looks good to me. However, it would be better to add a test for it, e.g. in the GlobalConfigurationTest.

OK, I'll add testCases. 😁 thank you for your review.

@wolfboys , the change looks good to me. However, it would be better to add a test for it, e.g. in the GlobalConfigurationTest.

PTAL, thx

@wuchong PTAL, thx.


Inconsistent language flags

Given the subtitle configuration
[subtitles.languages]
"captions/vtt+de" = "Deutsch"
"captions/vtt+en" = "English"

you end up with a view like this:

Where does the German flag come from?
Why is there none for English?
Can we make this somewhat consistent?

The code at fault is this function here: https://github.com/opencast/opencast-editor/blob/1a63c95efa6a41cadc09663612c918ab08f40672/src/main/SubtitleSelect.tsx#L66

Where does the German flag come from?

It's unicode!

Why is there none for English?

The function extracts a substring from the subflavor in the vague hope that it's a valid unicode flag. "en" is not a valid unicode flag.

Can we make this somewhat consistent?

Probably not (without a lot of effort)! There's no standard way of telling which language a vtt file belongs to (or no language, or multiple languages...), so we would have to come up with one.

If it's only Unicode icons anyway, I've got an idea.
Why not let users configure them as well?
Something like this:
[subtitles.languages]
"captions/vtt+de" = "Deutsch"
"captions/vtt+en" = "English"

[subtitles.icons]
"captions/vtt+de" = "🇩🇪"
"captions/vtt+en" = "🇺🇸"

What do you think?

Not a bad idea? I guess you can trust a person who sets up the config to set reasonable values for the icons.

Well… if we can't trust the admin, we have already lost anyway ;-P

Although if we implement #826, your suggestion would not work for some subtitles, as we would then display subtitles that are not set in the config, right?

That's true. But that's true already, since those wouldn't necessary even have a +lang as part of the flavor. It's also more that I couldn't access a subtitle I knew was in the system and I wouldn't expect that to be common.


Can´t find the options button in Step 2

Can´t find the options button in Step 2 ...On the upper right, select Edit to edit the pipeline build, and then select Options.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6ad567ab-0513-570b-74dc-a0827815c6a1
Version Independent ID: 5e549605-cac8-98ea-ac5b-89f4a40a5f3c
Content: Create your first pipeline - Azure Pipelines
Content Source: docs/pipelines/create-first-pipeline.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

I found the badge section. Step 2 should be modified to say something like....On the upper right, select the 3 dot menu, and then select Status badge.


fix typo

Pull Request Test Coverage Report for Build 600267541

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.64%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/generator/method/method.go
0
1
0.0%

Totals

Change from base Build 591089476:
0.0%

Covered Lines:
609

Relevant Lines:
827

💛  - Coveralls


Feature: Support Basic authentication and Bearer Token authorization for a connection to Frigate server

Sometimes Frigate and frigate-notify may not be placed in the same non-auth segment, but both can access the MQTT bus. And then we can assume that the Frigate API is protected by some type of auth (e.g., behind a reverse proxy, or we can imagine that Auth! MR is already implemented).
Since frigate-notify uses the net/http package to handle HTTP requests, we can easily implement Basic authentication and authorization based on the static Bearer Token header (generated externally).
Basic Auth description: https://pkg.go.dev/net/http#Request.BasicAuth + https://pkg.go.dev/net/http#Request.SetBasicAuth
Bearer Token description:  https://swagger.io/docs/specification/authentication/bearer-authentication/
Thank you.

The implementation in the PR changed a bit. Port 5000 access will remain unauthenticated and is designed to be only exposed internally to other services in the compose file or selectively opened as needed. The new 8080 port is where auth will be enforced and where reverse proxies meant for external access will be pointed.

Port 5000 access will remain unauthenticated and is designed to be only exposed internally

Good point. Sounds like the frigate-notify might require separated Frigate endpoints configuration options:

Non-auth endpoint for m2m talks with Frigate, for example: https://github.com/0x2142/frigate-notify/blob/main/events/mqtt.go#L108
External auth-based endpoint, exposed in notifications towards the end user, for example: https://github.com/0x2142/frigate-notify/blob/main/events/events.go#L58-L62

Hey there @blakeblackshear - Thanks for sharing! That's great to know & will be helpful in addressing this.
So at the moment, I am working allowing the ability to configure additional arbitrary headers send to Frigate which should cover the initial request. And as suggested by @freefd, I'll go ahead and add a new config for an external/public URL to get ready for when that change is live in Frigate.


Attempt to implement embedded PDFs

Hello dear PDF-creating friends 👋
This is my attempt to allow embedding of PDF pages in other pages.
The good news is that it does not crash, the bad news is that it does
not work :) This is my first time playing with PDF internals, this project and typescript. I am pretty confident in that there are many things to improve :)
It is an attempt to solve https://github.com/Hopding/pdf-lib/issues/184 (@4rlekin if you read this, feel free to help, or, as you prefer, continue thinking about an alternative implementation).
Architecture-wise it was my idea was to follow the implementation of
how we embed PNGs:
Have an embedPdfDocument method  on PdfDocument which uses a
PdfPageEmbedder.
On PdfPage the returned object can be inserted using
drawEmbeddedPdfPage.
The PDF page to be embedded is wrapped into an XObject (8.10 FormXObjects from the PDF spec). This involved some heavy wrestling against contexts and copied pages.
I adapted the scratchpad to illustrate how this could be used. Sadly, it
just renders an empty, white page. I guess I need help debugging this.
Things to improve:

Is the general idea sound or total nonsense? @Hopding
I violated the PDFImage class by adding an EmbeddedPdfPage option to
the existing image types. To me it sounds like a PDFPage is not an
image and should either not be supported by this class or we should
rename/rework this class. Normally the pdf embedder would not need width and height, but I needed to implement it because PDFImage wants it.
XObjects seem to support transformation matrices and transparency. This
is great, but the normal PNG code scales/rotates their content
differently. We need to decide which is better.
My attempts to support better placement (rotation, skew, clipping, ...) is mostly commented out. I wanted to be able to insert something first, then make it better.
Add tests
Reset the scratchpad to have the original code before merging this to
master

I would appreciate reviews (to improve my TypeScript as well as the architecture, usage) and would love help in finding out why this does not work yet.

Hello @tessi!
Great work on this PR! You've done some impressive work here.
I was able to get this working after making a few changes to your PDFPageEmbedder.embedIntoContext method. I've copied the updated version of this method below:
import PDFDocument from 'src/api/PDFDocument';
import PDFPage from 'src/api/PDFPage';
import PDFRawStream from 'src/core/objects/PDFRawStream';
import PDFRef from 'src/core/objects/PDFRef';
import PDFStream from 'src/core/objects/PDFStream';
import PDFContext from 'src/core/PDFContext';
import PDFObjectCopier from 'src/core/PDFObjectCopier';
import { decodePDFRawStream } from 'src/core/streams/decode';
import PDFContentStream from 'src/core/structures/PDFContentStream';
import { mergeIntoTypedArray } from 'src/utils';

// ...

async embedIntoContext(context: PDFContext, ref?: PDFRef): Promise<PDFRef> {
  const { left, bottom, right, top } = this.boundingBox;
  const bbox = [left, bottom, right, top];

  const copier = PDFObjectCopier.for(this.page.doc.context, context);
  const copiedPage = copier.copy(this.page.node);
  const { Contents, Resources } = copiedPage.normalizedEntries();

  if (!Contents) throw new Error('Missing page.Contents!');

  const decodedContents: Uint8Array[] = new Array(Contents.size());
  for (let idx = 0, len = Contents.size(); idx < len; idx++) {
    const stream = Contents.lookup(idx, PDFStream);
    if (stream instanceof PDFRawStream) {
      decodedContents[idx] = decodePDFRawStream(stream).decode();
    } else if (stream instanceof PDFContentStream) {
      decodedContents[idx] = stream.getUnencodedContents();
    } else {
      throw new Error(`Unrecognized stream type: ${stream.constructor.name}`);
    }
  }

  // TODO: Should probably insert a newline in between each content array when
  // merging them, just to be safe
  const mergedContents = mergeIntoTypedArray(...decodedContents);

  const xObject = context.stream(mergedContents, {
    Type: 'XObject',
    Subtype: 'Form',
    FormType: 1,
    BBox: bbox,
    Matrix: this.transformationMatrix,
    // do we want to handle transparency?
    // https://github.com/galkahana/PDF-Writer/blob/edb7478dce955dfab61bbc2219a1ca7b85bed924/PDFWriter/DocumentContext.cpp#L992
    Resources,
  });

  if (ref) {
    context.assign(ref, xObject);
    return ref;
  } else {
    return context.register(xObject);
  }
}

Basically, the reason your code wasn't working is that you were copying an array of stream references as the content of the XObject stream. You can confirm that this is the case by saving your document without object streams: pdfDoc.save({ useObjectStreams: false }) (note that this format is generally very useful for debugging documents during development as it makes the output PDF human readable). If you open the resulting document in a text editor and search for the definition of indirect object 5 0, you'll find the following:
5 0 obj
<<
/Type /XObject
/Subtype /Form
/FormType 1
/BBox [ 0 0 595.28 841.89 ]
/Matrix [ 1 0 0 1 0 0 ]
/Resources <<
/Font <<
/Helvetica-7128 7 0 R
>>
/XObject <<
>>
>>
/Length 22
>>
stream
[ 9 0 R 8 0 R 10 0 R ]
endstream
endobj

Note the stream's content (the stuff between the stream and endstream keywords). It is an array of object references. This is because you grabbed the value of the source page's Contents entry and stuck it directly into the stream. Unfortunately, this won't work. The reason is that Contents is an array of stream references. But you want the XObject stream's content to be a sequence of content stream operators.
The solution I implemented in my refactored version of the  PDFPageEmbedder.embedIntoContext method is to lookup each stream and extract its contents. Once this is done, we can simply concatenate each content stream into a single stream of operators. And this single stream can be used as the content of the XObject stream.
After making these changes, indirect object 5 0 looks like the following:
5 0 obj
<<
/Type /XObject
/Subtype /Form
/FormType 1
/BBox [ 0 0 595.28 841.89 ]
/Matrix [ 1 0 0 1 0 0 ]
/Resources <<
/Font <<
/Helvetica-7128 7 0 R
>>
/XObject <<
>>
>>
/Length 110
>>
stream
q
BT
0 0 0 rg
/Helvetica-7128 24 Tf
24 TL
1 0 0 1 5 25 Tm
<7064662D6C696220697320617765736F6D6521> Tj
T*
ET
Q

And the resulting document contains the copied page!

@tessi I should also mention that your implementation concept is perfectly sound. In fact, it's exactly what I was thinking of when I wrote up https://github.com/Hopding/pdf-lib/issues/184#issuecomment-569120029.
As far as the PDFImage goes, perhaps we should create a new class to represent embedded PDF objects (it could potentially represent things besides embedded pages too)? Maybe something like PDFGraphic? PDFImage could then be made to subclass PDFGraphic... But I haven't fully thought through this, so it might have some holes. It just came to my mind as a potential solution. Thoughts?

@hopding thanks a torn for your feedback and even more for your refactored and working solution! You gave me a fish and helped me learn some fishing at the same time :)
Regarding PDFImage: I agree that extracting the embedded pdf page functionality into its own class is the way to go. I would say I'd like to decide later if and how that class connects to PDFImage.
My next step is to implement clipping/transformations on the embedded pdf. I'm not sure yet where exactly I should place the transformations: in the XObjects matrix or in the drawing code in PDFPage#drawEmveddedPdfPage. I will probably try both and stick with what's best.
Thanks again for your welcoming and extremely helpful comments. I'm hyped to continue working on this PR.

Thanks to your help @Hopding. PDF embedding works, even with slightly more complex source PDFs which include images \o/ Also scaling, rotation and skewing works:

For the implementation I decided to stick to the way the PNG/JPEG variants are implemented as I think its a more consistent user experience. Also, using transformation matrices on the XObject itself would probably (at least as far as I understand the spec) apply to all uses of the embedded PDF.
With my current solution it is still possible to apply a custom transformation matrix to the XObject (so we don't keep users from doing this). However, transforming during the draw step is much easier to use and should be the way we advertise in the documentation.
I implemented the TODO you left (insert newlines in between decoded streams) - it's probably not the most efficient code but seems to do the job.
In addition, I changed the draw options to use its own options object: PDFPageDrawEmbeddedPdfPageOptions. I renamed what used to be width/height in the image options to xScale and yScale since the underlying scale operation seems to scale relative (e.g. 0.5 for half the size) and not in absolute values (e.g. 200 to get 200 units).
I have not checked yet, but think that it's similar for PNGs/JPGs. Maybe we want to rename their width and height options too. At least to me width and height sounds like the user should give absolute numbers, but this may be because I'm not native English. What do you think?
Next, I will clean up the code (and rescue poor PDFImage from being misused) to make it properly reviewable. Then, I will add tests.

I have not checked yet, but think that it's similar for PNGs/JPGs. Maybe we want to rename their width and height options too. At least to me width and height sounds like the user should give absolute numbers, but this may be because I'm not native English. What do you think?

I just re-read the docs 🙈 width/height does in fact get relative sizes, but the code
   const jpgImage = await pdfDoc.embedJpg(jpgImageBytes)
   const jpgDims = jpgImage.scale(0.5)
   const page = pdfDoc.addPage()
   page.drawImage(jpgImage, {
     x: 25,
     y: 25,
     width: jpgDims.width,
     height: jpgDims.height,
     rotate: degrees(30)
   })

uses width and height from the jpgDims object. Still a little weird to me (why can't we directly give 0.5 into the imageOptions?). But it's not as weird as I first thought :)

Another Update:

The PDFImage class is restored to sanity again: Embeddable page stuff now lives in its own class EmbeddablePDFPage.
I slightly refactored PdfDocument.flush() to be more DRY and added another interface Embeddble to PDFImage, PDFFont, and the new EmbeddablePDFPage to make sure they all implement embed().
Added documentation to all the things
updated the scratchpad to showcase a more complex example of the new API - it is possible to embed a part of a PDF page, and rotate/place it however you want (note: I will restore the original scratchpad before merging)

the soure page
only a part of the source page embedded and rotated

Feature-wise I would say this PR is complete. We only miss some tests now. What do you think @Hopding ?

I added tests for the parts that were tested before (-> the embedder). The relevant other parts (page, document) had no existing tests for jpges/pngs. So I thought I may get away by also not testing them?!
Next steps:

[ ] get a review by @Hopding  and apply discussed changes
[ ] reset the scratchpad
[ ] prepare metadata. I found no CHANGELOG.md, is there other parts where I should document the changes?

@tessi Exciting progress! I'll review this as soon as I get a chance. I don't keep a changelog file. Instead I record the changes included in each release with GitHub's releases feature: https://github.com/Hopding/pdf-lib/releases. If you'd like to provide anything specific, just make a note in this thread and I'll include it in the release description.
One thing that we'll definitely need before merging this is some integration tests. If you're not familiar with them, here's a quick overview explaining how to run them. Please let me know if you have any questions about how to work with them. I think it would be good to update test1 to embed a document or two to test embedding pages in new documents. And then we'll want to add or update another one to test embedding pages in existing documents.

Thanks @Hopding :)
Adding integration tests, indeed, is crucial :) I added some pdf-embedding to test1 and test2. The pages now look like this:
test1.ts
Here, I added a 4th page which embeds page 3 (rotated by 90 degrees and stretched to cover most of the page).
In addition, normal.pdf is overlayed on top.

test2.ts
Here, we add part of page 74 of the PDF spec (a figure about PDF encryption) to the bottom-left of every page.

If you'd like to provide anything specific, just make a note in this thread and I'll include it in the release description.

I think I'm fine. Just wanted to take as much work off you for preparing a release (a fast release is in my interest, since I need the built package to use it in my project :))

@tessi Just wanted to check and see if you've had a chance to read over and consider all my comments?

Hey @Hopding I've seen your comments and as always they seem reasonable, well argued and nice :) I started working on them, but then came vacations and some family time. But I'm on it 🤞 (some of the easier changes are already commited and pushed)

Sounds good! Looking forward to merging this 👍

When will this PR be merged ?
This PR will help on a work around for #363, #202. Say svg-to-pdfkit -> pdfkit-to-pdf_lib -> embedPDF.

@ihmc3jn09hk I guess this will be merged when I find enough free time to work on this (which I am motivated to do, but without any promises) and Hopding finds enough free time to review again.
I guess we cannot promise a specific time

To my own surprise, I found some extended time to work on this PR today. @Hopding do you mind having another look? Changes are:

implemented width/height/scale for the embedded PDF pages
applied the renames you wished for
made embedDocument multi-page aware
fixed typos and copy&paste error you outlined
applied the code improvements you suggested
adapted the integration tests to use both, xScale/yScale and width/height when drawing pages
extended specs for PDFPageEmbedder to test that it uses not only the page dimensions, but those from the given boundingBox

@Hopding thanks for merging, and even more for your continuous support in that journey. It was fun working with you 🍻

@tessi It was great working with you as well! I really appreciate the work you did on this feature. I'm confident it will be a popular one.

Version 1.4.0 is now published. It contains PDF embedding support. (see this example). The full release notes are available here.
You can install this new version with npm:
npm install<EMAIL_ADDRESS>
It's also available on unpkg:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
As well as jsDelivr:

<EMAIL_ADDRESS><EMAIL_ADDRESS>


Metadata expansion

fix typo in AnnotationType enum
Add support for more annotation metadata other than just present or not.
Add glycogen to classNameDict

ready to merge if you are done making changes

Yeah go ahead and merge


Fix: Get constructor as Callable

Fixes https://github.com/godotengine/godot/issues/70319
Now constructors of Scripts and Native objects can be retrieved as a Callable.

Thanks!


[IOTDB-1396] Restructure logical query operator

The design doc is in https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=181306231

Coverage decreased (-0.003%) to 67.915% when pulling 8ec9cdf709a549bd4d34a664f061f3e557306bcc on RequeryV2 into 16167373d924b4f457ce380144a2564be76b65b2 on master.


Blog on zombie (defunct) processes with a Falco service

What would you like to be added:
There is concern around abandoned sub-processes with running Falco as a service. Can we write up a blog on this, explaining why it's happening.
Also can we open github issues for any work generated from this.
Why is this needed:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


[WIP] Update pion/ice to v0.5.x (new TURN client)

Relates to pion/turn#74
This updates pion/ice to v0.5.1, which include a refactoring of CandidateRelay and a TURN client overhaul which resolves the connectivity issue with relay-prflx (symmetric NAT) pair.

Hmm...
1.46s$ GOOS=js GOARCH=wasm go test -exec="./test-wasm/go_js_wasm_exec" -v .
# github.com/pion/turn/internal/ipnet
../../../gopath/pkg/mod/github.com/pion/turn@v1.3.1/internal/ipnet/ipv4.go:17:12: undefined: setControlMessage
../../../gopath/pkg/mod/github.com/pion/turn@v1.3.1/internal/ipnet/ipv4.go:32:8: undefined: createControlMessage
FAIL	github.com/pion/webrtc/v2 [build failed]
The command "GOOS=js GOARCH=wasm go test -exec="./test-wasm/go_js_wasm_exec" -v ." exited with 2.

@Sean-Der Any idea?  I wonder why this happens at webrtc level.  Actually, control message is no longer used in pion/turn. I may have to clearn that up, but wants to know exactly what this means.

Ah... ok. I am going to completely remove ipnet folder:
internal/ipnet/ipv4.go:17:      if err := setControlMessage(conn); err != nil {
internal/ipnet/ipv4_unix.go:10:func setControlMessage(conn *ipv4.PacketConn) error {
internal/ipnet/ipv4_windows.go:9:func setControlMessage(conn *ipv4.PacketConn) error {

Codecov Report

Merging #740 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #740      +/-   ##
==========================================
- Coverage   76.71%   76.66%   -0.05%
==========================================
  Files          58       59       +1
  Lines        4041     4050       +9
==========================================
+ Hits         3100     3105       +5
- Misses        686      690       +4
  Partials      255      255

Impacted Files
Coverage Δ

sctptransport.go
74.34% <0%> (-1.32%)
:arrow_down:

dtlstransport.go
66.66% <0%> (-1.17%)
:arrow_down:

configuration.go
100% <0%> (ø)

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 7243561...071d004. Read the comment docs.

Thanks! Let me tag it as v2.0.24.


To support Will Message Feature

Will Message is MQTT's ability to gracefully send wills to third parties for devices that may be unexpectedly disconnected. The Current version supports the MQTT 3.1.1 protocol, but the Will Message feature in this version is not yet supported. So we are discussing plans to support this feature.

I'd love to implement this feature, can you assign me？

I'd love to implement this feature, can you assign me？

welcome

I'd love to implement this feature, can you assign me？

ping @ShannonDing

it can be closed @ShannonDing


GEODE-6491: Fix signed/unsigned problem reading size field in handshake message

If memberId length grew longer than 127 characters, which happens in some environments, geode-native would overflow a signed byte and start looking for a negative-length array.  Bad things happened after that.
Co-Authored-By: Mike Martell<EMAIL_ADDRESS>Co-Authored-By: Jacob Barrett<EMAIL_ADDRESS>

Formatting is failing on Travis.


Allow configuration of background-color in marker styles for Android

@xming13 found some time for that? would love to merge this

@Hirbod iirc the last time I looked into it, in iOS it uses the images 'bubble_left' and 'bubble_right' for the marker styling. Changing the background color only affect the middle part. I am not very proficient in Objective-C so anyone is welcomed to implement for the iOS part.

Don't worry. I will check this and implement it in Objective-C if no problem when I have a time.
Thank you for sending this pull request.

Please use the HtmlInfoWindow in v2.0.
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/HtmlInfoWindow/README.md


Enabling ForkingClientServerIntegrationTestsSupport.java to support starting multiple servers

Enabling ForkingClientServerIntegrationTestsSupport.java to support the starting of multiple server processes without overwriting the gemfireServer
property with the last started server.
gh #11

Is there any thing left preventing this from being merged? Because it would be great to have this in a release so the WAN examples work correctly.


132 documentation for recompilation

switching branches added my two commits from hashing passwords to this branch. So I had to revert those.


Add disclaimer dialog

link to demo deployment of your smk based app is
https://smk-svt-rt-b16795-dev.apps.silver.devops.gov.bc.ca
Verify that it looks good, if so merge the pull request which will trigger a prod deployment, otherwise close the pull request without merging
mentions / notifications: @michaelpnelson

The Vanity URL for the dev deploy is https://smk-svt-api-gov-bc-ca.test.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @michaelpnelson

link to demo deployment of your smk based app is
https://smk-svt-rt-b16795-prod.apps.silver.devops.gov.bc.ca
Verify that it looks good, if so merge the pull request which will trigger a prod deployment, otherwise close the pull request without merging
mentions / notifications: @michaelpnelson

The Vanity URL for the prod deploy is https://smk-svt.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @michaelpnelson


HWY-65: Check more validity conditions in Highway Core

Check that every block belongs to a proposal vote, i.e. the timestamp matches the beginning of a round, the creator is the leader, and this is their first vote in that round.
Also check that the round exponent is not decreased further than 2 below the median, where faulty and mute validators are treated as having the initial round exponent. (For now, we set the initial to equal the minimal round exponent and we don't change it at all yet, but this will be relevant for adaptive round lengths in the future.)
https://casperlabs.atlassian.net/browse/HWY-65

I added comments and fixed the leader block check.


#1524 support null for image, svg and font properties

Added support for accepting null as value for image, font and svg properties.
This makes it possible to use a Skia Value as the property for the above types, and also helps developers using useFont, useImage and useSvg so that they don't need to null check their code all the time.

Updated types
Updated native implementation to support null values
Updated ts / web implementation
Updated documentation
Updated examples

fixes #1524

sorry for not catching this in the review but if the value becomes null after displaying an image, the image is still displayed.
The use case this example: https://shopify.github.io/react-native-skia/docs/snapshotviews where we cannot toggle based on the image state value.

sorry for not catching this in the review but if the value becomes null after displaying an image, the image is still displayed.
The use case this example: https://shopify.github.io/react-native-skia/docs/snapshotviews where we cannot toggle based on the image state value.


Homebridge and home Assistant support

I just found your project.  All I can say is awesome work!
I was thinking for the smart plug option that you have, if you create a plugin that would integrate with home assistant and home bridge, all smart plugs would be available. No extra work after initial plug-in development and you would reach a huge audience.
Again really great work!

Thanks for the feedback! For support of other smart plugs, I am actually a more generic way to call external APIs so one can configure a HomeBridge or Home Assistant API and trigger the smart plug that way. I will test and implement it as soon as I have some free time.


Multiarch support + updated base image

(I made the disk 50G instead of 150 as 150 is for most people not enough so you probably want a soft-RAID or SIS/other object storage)

Do not worry about the 50G, we are migrating our all images to 50GB and will develop a resize tool

LGTM

Oh the resize would be nice. I pay a lot for 150GB where not much is used.

:)


White square around elements

Description of the new feature/enhancement
Not sure if this is a future, but ... This white square pokes me out of myself when using a hotkey.
By the way, this is a problem with the windows 10 interface as a whole, I see this in office, in the calculator, and in many other places in modernUI applications.

Proposed technical implementation details (optional)

Yeah...I think this is out the scope of this repo.

In some programs, I have never noticed this, or it seems to me that this is also a windows 10 problem?

When you are using flat menus, a highlighted menu item is surrounded by a border with a different system colour.  This is not a Windows Terminal thing.

Indeed. This is the keyboard focus indicator, and it is going to be present anywhere you access ancillary UI by using the keyboard.


Keep renamed/removed experimental attributes as deprecated

When renaming/removing an attribute, we need to preserve the old name in the yaml.
Currently it disappears, meaning that:

codegen does not generate it from yaml
semconv lib maintainers need to manually copy them back to avoid breaking API changes

This creates a lot of work for  language SIGs

https://github.com/open-telemetry/semantic-conventions-java/issues/5
or here's how python list of manually defined deprecated attributes looks like

OR semconv libraries drop removed attributes from API surface

applications that don't have all the versions of instrumentation libraries perfectly aligned can fail in runtime because of missing attributes in newer versions.

Options:

Never remove an attribute, when renaming always add the old one to deprecated ones

we'd also need CI checks to validate

Add build-tools feature to compare list of attributes between semconv vOld and vNew and generate list of removed attributes.

My preference would be on Option 2 since we need to build validation tooling anyway, so why not automate the whole process.

@lmolkova For HTTP we have (at some of them) the deprecated attributes listed in a separate section in the registry: https://opentelemetry.io/docs/specs/semconv/attributes-registry/http/#deprecated-http-attributes
I like to have this documented not only in yaml files (and codegen) but also in the docs.

@AlexanderWert we've been inconsistent with marking them as deprecated.
So either we embrace it and pick option2 or add tooling to ensure we mark removed ones as deprecated (option1).
I agree that having them preserved in the spec (at least for a certain period of time) is great.

closing in favor of #740


feat(helm-chart): add initial Helm chart for OtterWiki

This Helm chart simplifies the deployment of An Otter Wiki on Kubernetes.
Supports Ingress, Loadbalancer and Nodeport.
Tested on k3s, passes helm lint.

Awesome. Thank you! Will test and review this PR this weekend.

Tooks more time than expected, sorry for that.
I have improved the chart somewhat.
Will be published on https://hub.docker.com/r/redimp/otterwiki/tags
Thanks again for pushing this!

Brilliant, thanks for the merge.
Super useful having the chart published makes deployment so easy.


Refactor the isFat flag, with backward compatibility

Also implement a temporary hack for the gunicorn file to be a pex, to unblock us.  We'll come back around later and fix this hard code.

We're closing this PR to open a new one over the force rebased master.


CLI interface updates

The current one looks kinda ugly:

Terminal Output
gtasks tasks view -c
Choose a Tasklist:
✔ To watch
Tasks in To watch:

[1] Notting hill
    Description: Movie
    Status: completed
    No Due Date

[2] The good place
    Description: Series
    Status: completed
    No Due Date

[3] Fresh off the boat
    Description: Sitcom
    Status: completed
    No Due Date

[4] Blade runner both
    Description: Movie
    Status: completed
    No Due Date

The CLI interface needs a more compact update. Perhaps a table format to utilise the width of the display. Something like this:

Image from Himalaya, an email client written in Rust

Fixed in #5


DNM - Create cephfs volume that can be consumed by Manila

This patch applies a cephfs volume and creates a ceph-nfs cluster that can be consumed by Manila.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:
[x] README in the role
[x] Content of the docs/source is reflecting the changes

Marking as draft because we need the new ceph container upstream version that includes the Aug backports (with the ganesha proxy-protocol support).
I'm going to unblock the patch as long as I have the new ceph bits in place.

+2

 -ceph -s[ceph: root@edpm-compute-0 /]# ceph -s
  cluster:
    id:     d6341b08-3ed2-5db8-b67a-5ed292687b5c
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum edpm-compute-0,edpm-compute-2,edpm-compute-1 (age 6h)
    mgr: edpm-compute-0.vddgga(active, since 6h), standbys: edpm-compute-2.pkcpwd, edpm-compute-1.rahmoc
    mds: 1/1 daemons up, 2 standby
    osd: 3 osds: 3 up (since 6h), 3 in (since 6h)
    rgw: 3 daemons active (3 hosts, 1 zones)

  data:
    volumes: 1/1 healthy
    pools:   12 pools, 337 pgs
    objects: 223 objects, 456 KiB
    usage:   214 MiB used, 21 GiB / 21 GiB avail
    pgs:     337 active+clean

  io:
    client:   255 B/s rd, 0 op/s rd, 0 op/s wr

[ceph: root@edpm-compute-0 /]# ceph orch ls
NAME                     PORTS                    RUNNING  REFRESHED  AGE  PLACEMENT
crash                                                 3/3  -          6h   *
ingress.nfs.cephfs       <IP_ADDRESS>:2049,9049      6/6  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
ingress.rgw.default      <IP_ADDRESS>:8080,8999      2/2  -          2m   count:1
mds.cephfs                                            3/3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
mgr                                                   3/3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
mon                                                   3/3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
nfs.cephfs               ?:12049                      3/3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
osd.default_drive_group                                 3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2
rgw.rgw                  ?:8082                       3/3  -          2m   edpm-compute-0;edpm-compute-1;edpm-compute-2

Marking as draft because we need the new ceph container upstream version that includes the Aug backports (with the ganesha proxy-protocol support). I'm going to unblock the patch as long as I have the new ceph bits in place.

i'm curious about how one can track this. The container tags seem to correspond to the upstream ceph tags; https://github.com/ceph/ceph/pull/53124 merged a couple of weeks ago... is there a cadence to the tagging?
https://bugzilla.redhat.com/show_bug.cgi?id=2176300 is verified.. so RHCS doesn't seem to be relying on upstream tags (much like RHOSP/RDO)

Marking as draft because we need the new ceph container upstream version that includes the Aug backports (with the ganesha proxy-protocol support). I'm going to unblock the patch as long as I have the new ceph bits in place.

i'm curious about how one can track this. The container tags seem to correspond to the upstream ceph tags; ceph/ceph#53124 merged a couple of weeks ago... is there a cadence to the tagging?
https://bugzilla.redhat.com/show_bug.cgi?id=2176300 is verified.. so RHCS doesn't seem to be relying on upstream tags (much like RHOSP/RDO)

There's no specific way to track this down apart getting notified on new builds happening in quay.io/ceph.
I see the downstream content is already there, and it helped speeding up the development on this, while
~1 week ago I didn't see the upstream backports in the 18 tag.
I'll retry this deploy with the new 18.2, built 6 days ago [1] and see if the cephadm options are there.
[1] https://quay.io/repository/ceph/ceph?tab=tags

Marking as draft because we need the new ceph container upstream version that includes the Aug backports (with the ganesha proxy-protocol support). I'm going to unblock the patch as long as I have the new ceph bits in place.

i'm curious about how one can track this. The container tags seem to correspond to the upstream ceph tags; ceph/ceph#53124 merged a couple of weeks ago... is there a cadence to the tagging?
https://bugzilla.redhat.com/show_bug.cgi?id=2176300 is verified.. so RHCS doesn't seem to be relying on upstream tags (much like RHOSP/RDO)

There's no specific way to track this down apart getting notified on new builds happening in quay.io/ceph. I see the downstream content is already there, and it helped speeding up the development on this, while ~1 week ago I didn't see the upstream backports in the 18 tag. I'll retry this deploy with the new 18.2, built 6 days ago [1] and see if the cephadm options are there. However, this requires the edpm nodes to get the latest reef cephadm package in the system, which is something that is going to be solved by [2]
[1] https://quay.io/repository/ceph/ceph?tab=tags [2] https://review.rdoproject.org/r/c/rdo-infra/ansible-role-dlrn/+/49997

After digging a bit on the way the Ceph container images are built, I can say that we're going to get this code when 18.3 is available.
We need to rebuild the whole Ceph code base on CentOS Storage SIG to be able to consume a version containing the proxy-procol fix, because containers are build using packages provided by CentOS [1], and you can see an example in [2].
The cbs build is Aug 4th, while the backports have been merged after that date (Aug 23rd), hence we should hold this change until 18.3 is out.
@adking @guits do we have a timeline for Ceph Reef 18.3 ?
[1] https://cbs.centos.org/koji/buildinfo?buildID=50233
[2] https://quay.io/repository/ceph/ceph/manifest/sha256:7836d32098927904b0ed8c59ad30c57201beb68e93f24693d3d8cde5afbd58bb

After digging a bit on the way the Ceph container images are built, I can say that we're going to get this code when 18.3 is available. We need to rebuild the whole Ceph code base on CentOS Storage SIG to be able to consume a version containing the proxy-procol fix, because containers are build using packages provided by CentOS [1], and you can see an example in [2]. The cbs build is Aug 4th, while the backports have been merged after that date (Aug 23rd), hence we should hold this change until 18.3 is out. @adk3798 @guits do we have a timeline for Ceph Reef 18.3 ?

The versioning scheme for ceph upstream releases tends to go 18.2.0, 18.2.1, 18.2.2, etc. The "y" part of the release was for tracking rc builds and such (rc builds were 18.1.z) so what you're going to be looking for is 18.1.1. That being said, I haven't heard any plans for 18.2.1 yet. The guy who handles the upstream release process is on PTO until the end of the month and I think we're planning to do 17.2.7 (next quincy release) at least before another reef release.

After digging a bit on the way the Ceph container images are built, I can say that we're going to get this code when 18.3 is available. We need to rebuild the whole Ceph code base on CentOS Storage SIG to be able to consume a version containing the proxy-procol fix, because containers are build using packages provided by CentOS [1], and you can see an example in [2]. The cbs build is Aug 4th, while the backports have been merged after that date (Aug 23rd), hence we should hold this change until 18.3 is out. @adk3798 @guits do we have a timeline for Ceph Reef 18.3 ?

The versioning scheme for ceph upstream releases tends to go 18.2.0, 18.2.1, 18.2.2, etc. The "y" part of the release was for tracking rc builds and such (rc builds were 18.1.z) so what you're going to be looking for is 18.2.1. That being said, I haven't heard any plans for 18.2.1 yet. The guy who handles the upstream release process is on PTO until the end of the month and I think we're planning to do 17.2.7 (next quincy release) at least before another reef release.

Thanks @adk3798 for clarifying that: I think at this point I'll move forward with this by skipping ceph-nfs for now, until we have the new container tag.
By doing this we can enable native cephFS until the nfs time comes.

Tested locally and we can see ceph-nfs is skipped as expected:
TASK [cifmw_cephadm : Apply cephfs volume _raw_params={{ cifmw_cephadm_ceph_cli }} fs volume create {{ cifmw_cephadm_cephfs_name }} '--placement={{ placement }}']
ok: [<IP_ADDRESS>]

TASK [cifmw_cephadm : Apply cephfs volume _raw_params={{ cifmw_cephadm_ceph_cli }} nfs cluster create {{ cifmw_cephadm_cephfs_name }} --ingress --virtual-ip={{ cifmw_cephadm_nfs_vip }} --ingress-mode=haproxy-protocol '--placement={{ placement }}'
skipping: [<IP_ADDRESS>]

recheck

@fmount we had some infra issues today, I'm gonna approve it to merge it
/approve


IfcElementAssembly - Missing in ifc2x3_element_type

Hello together,
I am missing the IfcElementAssembly as an IFC-Type.
If i get the ifc type from a container element it is none, although it is set as IfcElementAssembly.
When setting the name of a container with the attribute controller set_name() method the IFC Type goes missing,
and would need to be set again as IfcElementAssembly.
Which seems to be missing in the API as an IFC-Type.
Would be really much appreciated if this could be added.
Best Moritz

Hi @MoritzNiebler
That's right, we'll add that asap.

Done (will be available within the next minor version (live-update))


different date format

Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #9859
[ ] Requires deployment <worker/stick/speck>

Before submitting pull request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality

Optional

[ ] I've tested it at </ahp/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at Koda Ecosystem Telegram?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

thanks!
pay 20 usd

pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 8.32 USD/DOT ~ 2.404 $DOT
🧗 14dLrAvjDw7cFLaxM7VWR6YtHd7bGZY2QpzXDhAJJ4yv6oGw
🔗 0x59765a10f557cebe6b3ff7483ad80b10bea22e9799e0f7480f31606d06f1a216
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


{force: false} doesn't work if element is below the viewport

I believe the calculation of the viewport is wrong if container is body.
the statement in 380 will always be true while the element is below the viewport.
Lines: 375-385
if (!force) {
    var containerTop = initialY;
    var containerBottom = containerTop + container.offsetHeight;
    var elementTop = targetY;
    var elementBottom = elementTop + element.offsetHeight;
    if (elementTop >= containerTop && elementBottom <= containerBottom) {
        return;
    }
}

viewport calculation should be dependent on the window height (e.g. joshcarr/window-height-width.js)

I believe this has been fixed by https://github.com/rigor789/vue-scrollto/pull/150#issuecomment-529996487


Segmentation fault (core dumped)

I am currently using Opensuse Tumbleweed,
I used zypper to install lapce but when i try to run the program using the terminal, it throws a segmentation fault (core dumped

)
when i use journalctl -f it displays this

my system info is below

I could be wrong but I believe the only unsafe code is the FFI in the tree-sitter crates we depend on. They only really wrap around some C code. If you say what language you are working with then we could track down the bothersome crate and make an issue there. If it happens for multiple languages, then I am most likely wrong that that is the only place unsafe is.

I had just installed it,
Then tried to run it,
At first with through the graphical side but it didn't launch and then with the terminal and that's when I got the error.
Originally I had downloaded it to use it to code in rust,
And just generally try it out.
But it just failed to launch.
I tried downloading from the site as well as using zypper but both still gave the same error

I wouldn't be surprised if its a rendering bug (or bug in initializing rendering), since that tends to be the cause of some of these on-startup crashes.

I tried building it from source and it gave me a segfault as well. Me on pop-os. when compiling in debug target i get this output as well:
   Running `target/debug/lapce`
[2022-09-23][03:22:38][lapce_data::keypress][ERROR] Failed to load from "/home/ludm/.config/lapce-debug/keymaps.toml": no keymaps
Segmentation fault (core dumped)```
if i install it from flatpak it works fine, but building or downloading a release gives me a segfault.

On Fedora 37 Workstation aarch64 on RPi4.
I installed the package through copr, when I run "lapce"
"Segmentation fault (core dumped)"

I also experience this issue on Manjaro with the Manjaro package (0.2.0), the Arch package (0.2.1) and the Arch/Manjaro package built from scratch using this PKGBUILD with rustc/cargo version 1.64.0.

I think I also have this issue only I just get segmentation fault (without the core dumped)
I've built from source using the build instructions then ran ./target/release/lapce
for which I got Segmentation fault
After which I've tried the prebuilt version also and it also segfaults.
My system info:
$neofetch
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMMMM   monkeykong@mx
MMMMMMMMMMNs..yMMMMMMMMMMMMMm: +NMMMMMMM   -------------
MMMMMMMMMN+    :mMMMMMMMMMNo` -dMMMMMMMM   OS: MX x86_64
MMMMMMMMMMMs.   `oNMMMMMMh- `sNMMMMMMMMM   Host: GB-BXi7G3-760 1.x
MMMMMMMMMMMMN/    -hMMMN+  :dMMMMMMMMMMM   Kernel: 5.10.0-5mx-amd64
MMMMMMMMMMMMMMh-    +ms. .sMMMMMMMMMMMMM   Uptime: 2 mins
MMMMMMMMMMMMMMMN+`   `  +NMMMMMMMMMMMMMM   Shell: bash 5.0.3
MMMMMMMMMMMMMMNMMd:    .dMMMMMMMMMMMMMMM   Resolution: 1280x720
MMMMMMMMMMMMm/-hMd-     `sNMMMMMMMMMMMMM   DE: Xfce 4.14
MMMMMMMMMMNo`   -` :h/    -dMMMMMMMMMMMM   WM: Xfwm4
MMMMMMMMMd:       /NMMh-   `+NMMMMMMMMMM   WM Theme: Adapta
MMMMMMMNo`         :mMMN+`   `-hMMMMMMMM   Theme: Adapta [GTK2], Arc-Darker [GTK3]
MMMMMMh.            `oNMMd:    `/mMMMMMM   Icons: Papirus [GTK2], Moka [GTK3]
MMMMm/                -hMd-      `sNMMMM   Terminal: xfce4-terminal
MMNs`                   -          :dMMM   Terminal Font: Liberation Mono 11
Mm:                                 `oMM   CPU: Intel i7-4710HQ (8) @ 3.500GHz
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM   GPU: NVIDIA GeForce GTX 870M
                                           Memory: 2753MiB / 15950MiB

I guess your computer is too old to have an AVX instruction or something like that?


bosh aws create failure

i'm running bosh aws create command and getting the following output. i've re-run the command multiple times with the same outcome. Please investigate
Regards,
Aleksandr
aladyzhensky$ bosh aws create
Executing migration CreateVpc
creating internet gateway
creating security groups: open, bosh, bat, cf, web
creating subnets: bosh1, bosh_rds1, cf_elb1, cf_rds1, services_rds1,
cf1, services1, bosh_rds2, cf_elb2, cf_rds2, services_rds2
Making subnet bosh1 <IP_ADDRESS>/24:
Making subnet bosh_rds1 <IP_ADDRESS>/24:
Making subnet cf_elb1 <IP_ADDRESS>/24:
Making subnet cf_rds1 <IP_ADDRESS>/24:
Making subnet services_rds1 <IP_ADDRESS>/21:
Making subnet cf1 <IP_ADDRESS>/20:
Making subnet services1 <IP_ADDRESS>/20:
Making subnet bosh_rds2 <IP_ADDRESS>/24:
Making subnet cf_elb2 <IP_ADDRESS>/24:
Making subnet cf_rds2 <IP_ADDRESS>/24:
Making subnet services_rds2 <IP_ADDRESS>/21:
details in S3 receipt: aws_vpc_receipt and file: aws_vpc_receipt.yml
/Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/aws-sdk-1.44.0/lib/aws/core/client.rb:375:in
return_or_raise': The security group 'sg-0add0e60' does not exist in VPC 'vpc-d38f3ab6' (AWS::EC2::Errors::InvalidGroup::NotFound)     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/aws-sdk-1.44.0/lib/aws/core/client.rb:476:in client_request'
from (eval):3:in run_instances'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/aws-sdk-1.44.0/lib/aws/ec2/instance_collection.rb:303:in create'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/ec2.rb:71:in
create_instance'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/ec2.rb:88:in create_nat_instance'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/vpc.rb:133:in
block in create_nat_instances'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/vpc.rb:132:in each'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/vpc.rb:132:in
create_nat_instances'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/migrations/20130412004642_create_vpc.rb:27:in execute'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/migration.rb:21:in
run'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/migrator.rb:75:in block in run_migrations'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/migrator.rb:74:in
each'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/migrator.rb:74:in run_migrations'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh_cli_plugin_aws/migrator.rb:13:in
migrate'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli_plugin_aws-1.2697.0/lib/bosh/cli/commands/aws.rb:130:in create'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli-1.2697.0/lib/cli/command_handler.rb:57:in
run'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli-1.2697.0/lib/cli/runner.rb:56:in run'
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli-1.2697.0/lib/cli/runner.rb:16:in
run'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/gems/bosh_cli-1.2697.0/bin/bosh:7:in <top (required)>'
from /Users/aladyzhensky/.rvm/rubies/ruby-1.9.3-p484/bin/bosh:23:in load'     from /Users/aladyzhensky/.rvm/rubies/ruby-1.9.3-p484/bin/bosh:23:in '
from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/bin/ruby_executable_hooks:15:in
eval'     from /Users/aladyzhensky/.rvm/gems/ruby-1.9.3-p484@global/bin/ruby_executable_hooks:15:in '

bosh aws * commands were deprecated a few months ago and are not recommended for use.


Contravariant object parameters don't work well for optional object keys

Consider the following code https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgBiAlgE4DOGYAvGAN6phgBueFxcAdgFxicCuAWwBGbVAF8A3Omz4wAZTwBjLgBMa9RizbkOnAPy8BIsePRR+nJRj1gcpYpwwAKHAENSbwb0UrOqgEpNJmIoMGdZPDgw909BADpWdi4aaloAcmNRUnSghiYASD9yOBg8ePgAc1cPL0SdPQDpJnEwPBhyAnymMGLS8qrndNV+d1zmsDMzVGKqYRg3XhIKKlpupN0uXgBGAGZdgHYJdHtHF3m3JqA
What I expect is happening here is that version: number is not more general than version?: number so contravariance requirement breaks and Flow complains. However, any function that accepts version?: number can by definition accept versions that are non-optional.

You should make the property covariant to make this work:
type Second = {
  +version?: number
}

While this is a bypass, shouldn't flow do it by default? Function accepting version? can always handle version @vkurchatkin

@mkawalec If you don't make the object covariant your code can have a type error. Here's a demo:
/* @flow */

type First = {
  version: number
};

type Second = {
  version?: number
}

function print(param: Second) {
  if (typeof param.version === 'number') {
  	console.log(param.version);
  } else {
    console.log('dupa');
  }
  param.version = null; // allowed here as Second has version as nullable.
}

const bla: First = {
  version: 1337
}

print(bla);
// bla is no longer of type First, because print mutated it.
// Therefore type-error.

Since, objects can be mutated, you can assume sub-type relationship in places. Flow can't automatically figure out whether or not you are mutating an object in a function. So you have to make things as covariant to help Flow out.

It makes sense, thanks for the explanation. I guess I'm missing Haskell even more now :P


Add Dockerfile to Hydrate.

closes #27
This PR adds a Dockerfile to Hydrate, allowing Hydrate to be run in a container.
Merging into develop branch, the new home of devlopment work for the project.

This is great!
Just one thing, can you add the information about this in the README.md


Kitty open in single-instance mode ignores focused display and always opens on display where first instance is

I'm using yabai with two monitors and have bound Kitty to open with the --single-instance argument in skhd:
cmd - return : /Applications/kitty.app/Contents/MacOS/kitty --single-instance -d ~

This unfortunately leads to the new window always opening on the display where the initial (first) kitty instance currently resides (note: display, not space).
So e.g.:

Display 1 (focused): empty, Display 2: empty
Open the first Kitty instance
Display 1 (focused): [Kitty], Display 2: empty
Switch focus to Display 2
Display 1: [Kitty], Display 2 (focused): empty
Open Kitty with --single-instance argument
Display 1: [Kitty, Kitty], Display 2 (focused): empty

Is there any fix for this? Can I somehow specify to open a window at a specific (currently focused) display? I guess this should be the default behavior anyway but somehow the --single-instance argument leads to this being ignored.
Dotfiles for reference:

yabairc
skhdrc

I believe there is an error in your  config.
https://github.com/steven-lang/dotfiles/blob/master/configs/yabai/.config/yabai/yabairc#L20 should be yabai -m config window_origin_display        focused
That should in theory solve the issue, unless Kitty itself is stealing key-focus before spawning the new window.
If that is the case, you could set yabai -m config window_origin_display        cursor which will make newly created windows become tiled at the display that the cursor is placed at.

Oh wow, yes, the focus->focused fix resolved this issue. Thank you for your fast response and for taking the time to look at my config!
Since this went unnoticed to me, maybe a good idea would be to handle invalid configurations similar to i3wm which gives a notification (on config reload) that something went wrong.

yabai -m config window_origin_display cursor doesn't seem to be working for me, if there is a kitty window on another display when you close the focused kitty window, the focus goes there every time. It also happens with Alacritty and WezTerm.

Not sure I follow; that config option only takes place when creating a new window, not when windows are closed. I probably didn't understand what you meant.

Not sure I follow; that config option only takes place when creating a new window, not when windows are closed. I probably didn't understand what you meant.

My mistake, I got mixed up. The issue I'm describing happens when closing. Opening works as intended on my setup.


Accessibility : folds should be identified by sound, similar to how breakpoints identified

One of the use cases for me when considering vsCode is to have a folding editor. This makes reading someone else's code far easier when using a screen reader.
However, it is currently not possible to identify a fold when moving through the file. I can initiate folding and when viewing my own code, I obviously know that a function that looks empty is "folded".
SUggest playing a cound when entering (and possibly when exiting) a folded region when accessibility mode is enabled. I noticed that breakpoints play a sound when the line containing them is reached; similar thing could be done for folds.
Thanx.
-- Rich

Interestingly, I opened an old js file I had around and I got a couple of different sonic icons.

when I folded a function, it would tell me it was folded
when I unfolded it, it would make a sound as I executed the unfold
when I moved my cursor on a line with an object assignment ( object.foo = "something" ) it made a sound

THis was an old web project, so maybe things are different when operating on web projects; the previous comment was left in response to my examining a node.js project. I don't know why there should be such a difference; they are both clearly javascript...
How can I find a list of all earcons and their meanings?

Search for audio cues in the Settings to see the available cues.
There is
Audio Cues: Line has Folded Area
Play a sound when the active line has a folded area that can be unfolded.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


PVC can be deleted mistakenly when reading stale deletionTimestamp information

This issue was originally reported in datastax/cass-operator #412 by srteam2020
Description
We find that in a HA k8s cluster, cass-operator could mistakenly delete the PVC of the cassandra pod after cass-operator experiencing a restart. After diagnosis and inspection, we find it is caused by potential staleness in some of the apiserver.
More concretely, if cass-operator receives a stale update event from an apiserver saying "CassandraDatacenter has non-nil deletion timestamp", the controller will delete the PVCs returned by listPVCs, and listPVCs will list PVCs using the name(space) instead of the UID. Note that the stale event actually comes from the deletion of a previous CassandraDatacenter sharing the same name (but with a different UID) as the currently running one, so the PVC of the existing CassandraDatacenter will be listed and deleted mistakenly.
One potential approach to fix this is to label each PVC the UID of the CassandraDatacenter when creating them, and list the PVC using the UID of the CassandraDatacenter in listPVCs to ensure that we always delete the right PVC.
Reproduction
We list concrete reproduction steps in a HA cluster as below:

Create a CassandraDatacenter cdc. PVC will be created in the cluster.
Delete cdc. Apiserver1 will send the update events with a non-nil deletion timestamp to the controller and the controller will trigger deletePVCs() to delete related PVC. Meanwhile, apiserver2 is partitioned so its watch cache stops at the moment that cdc is tagged with a deletion timestamp.
Create the CassandraDatacenter with the same name cdc again. Now the CassandraDatacenter gets back with a different uid, so as its PVC. However, apiserver2 still holds the stale view that cdc has a non-nil deletion timestamp and is about to be deleted.
The controller restarts after a node failure and talks to the stale apiserver2. Reading the stale update events from apiserver2 that cdc has a deletion timestamp, the controller lists all the PVC belonging to the currently running cdc (as mentioned above) and deletes them all.

Fix
We are willing to help fix this bug by issuing a PR.
As mentioned above, the bug can be avoided by tagging each PVC with the UID of the CassandraDatacenter and listing PVC with UID. Each CassandraDatacenter will always have a different UID even with the same name. So in this case the PVCs belonging to the newly created CassandraDatacenter will not be deleted by the stale events of the old one.
┆Issue is synchronized with this Jira Bug by Unito

Hi @jdonenine I have issued a PR #122 (but it seems that there is some transient error in building?).
Besides the fix, I was asked about how to reproduce the bugs reliably in the original issue (in the old repo). Actually, we are recently building a tool https://github.com/sieve-project/sieve to reliably detect and reproduce bugs like the above one in various k8s controllers. This bug can be automatically reproduced by just a few commands using our tool. You can also use the tool to verify the patch.
To use the tool, please first run the environment check:
python3 check-env.py

If the checker passes, please build the Kubernetes and controller images using the commands below as our tool needs to set up a kind cluster to reproduce the bug:
python3 build.py -p kubernetes -m time-travel -d DOCKER_REPO_NAME
python3 build.py -p cass-operator -m time-travel -d DOCKER_REPO_NAME -s dbd4f7a10533bb2298aed0d40ea20bfd8c133da2

-d DOCKER_REPO_NAME should be the docker repo that you have write access to, -s dbd4f7a10533bb2298aed0d40ea20bfd8c133da2 is the commit where the bug is found.
Finally, run
python3 sieve.py -p cass-operator -t recreate -d DOCKER_REPO_NAME

and the bug is successfully reproduced if you can see the message below
[ERROR] persistentvolumeclaim TERMINATING inconsistency: 0 seen after learning run, but 1 seen after testing run

For more information please refer to https://github.com/sieve-project/sieve#sieve-testing-datacenter-infrastructures-using-partial-histories and https://github.com/sieve-project/sieve/blob/main/docs/reprod.md#k8ssandra-cass-operator-originally-datastax-cass-operator-412
Please let me know if you have interest in using or deploying our tool or encounter any problems when reproducing the bugs with the tool.


Since 1.19, AdvancedNBTTooltip 1.8.1 seems to interfere with ShulkerBox Preview mods

I normally use Tweakaroo for shulker box tooltips, which show all contents of a shulker box when using SHIFT key.  However after 1.19 upgrade, this no longer works.
I tried using the ShulkerBoxTooltips mod instead, thinking it was an issue with Tweakaroo, but that would hard-crash the game anytime I moused over a shulker-box.
Disabling AdvancedNBTTooltip got rid of the issues in both of the other two mods.

This is the same issue as #41

so as soon as I add AdvancedNBTTooltip 1.8.2 into my mod stack, I no longer get shulker tooltips.


Issue tracking?

I'm sorry if I've missed it and it was made clear inside the documentation somewhere, but is this repositry intended to also track known TC3 issues? I notice you have the "Issues" section at the top of the changes page.
I have a few issues and bugs I've experianced if so.

It is also to track known issues. You're more than welcome to add your bugs under the "Known Issues" section!

Wonderful, I'll add them to a fork, and PR it in at some point soonish. Thanks for the input!


Initial Multi-Robot Support

This PR adds initial multi-robot support, which required some rethinking of a lot of interfaces and visualization.
https://user-images.githubusercontent.com/4603398/192400839-ae07a18e-5611-46ae-9c0e-754a9839a63f.mp4
There is a new doc section outlining multirobot usage, but here are some basic things to test:
Regular Python examples (no ROS):
# Programmatic world buliding
cd /path/to/pyrobosim/pyrobosim
python3 examples/demo.py --multirobot

# From file
cd /path/to/pyrobosim/pyrobosim
python3 examples/demo.py --world-file test_world_multirobot.yaml

ROS example, with just GUI. Take a look at each individual robot's published state
ros2 run pyrobosim_ros demo.py --ros-args -p world_file:=test_world_multirobot.yaml

ROS example that shows multiple robots executing different plans.
# Run
ros2 run pyrobosim_ros demo.py --ros-args -p world_file:=test_world_multirobot.yaml
ros2 run pyrobosim_ros demo_commands.py --ros-args -p mode:=multirobot-plan

# Launch
ros2 launch pyrobosim_ros demo_commands_multirobot.launch.py

Some things to note:

The GUI now has an extra drop-down menu to select the active robot
Lots of display changes like per-robot colors, radius, paths, etc. And a lot of print statements now have a [robot name] prefix.
Only the latest published path / path planner overlay shows up right now. Wasn't sure how to do this better, though I see the argument for at least plotting all the robots' latest paths if enabled. Looking forward to input here.
The world still has a single inflation radius for collision checking and motion planning that right now uses just the max radius of all the robots. If you plan to use robots of all the same size, it won't affect you.
Task and motion planning is still done with a single robot, but nothing stops you from publishing actions/plans to multiple robots in the world.

Closes https://github.com/sea-bass/pyrobosim/issues/26.

Just that it seems that the robots are able to stand on top of each other, is it?

That's right, there is no collision checking between robots, except that the "randomize robot pose" button in the GUI will prevent robots from teleporting on each other.
As far as stopping robots from navigating to the same pose, or even crossing paths at runtime, that's not yet available. I was sort of hoping that would be handled at the algorithmic side when assigning plans to the robots.
Is there some minimal functionality you would expect to make your work feasible?

Just that it seems that the robots are able to stand on top of each other, is it?

That's right, there is no collision checking between robots, except that the "randomize robot pose" button in the GUI will prevent robots from teleporting on each other.
As far as stopping robots from navigating to the same pose, or even crossing paths at runtime, that's not yet available. I was sort of hoping that would be handled at the algorithmic side when assigning plans to the robots.
Is there some minimal functionality you would expect to make your work feasible?

I can make work with this, I think. Thank you again for creating this PR 👍 I don't have the authorization to approve it, but I think the assigned reviewers are satisfied and will approve the PR. 👍


[webview_flutter] add option to set the background to transparent

Regarding this issue:
https://github.com/flutter/flutter/issues/29300

@googlebot I signed it!

@real1900 Will this be merged soonly?

Hi, when will this PR merge?

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@rildexter what do you mean? i have done it and @googlebot said "CLAs look good".

Please this needs to be merged asap 🙏

Any plan on merging this one?

Any plan on merging this one?

@crizant can you resolve conflicts, please, maybe they finnaly will merge it

@crizant can you resolve conflicts, please, maybe they finnaly will merge it

@crizant can you resolve conflicts, please, maybe they finnaly will merge it

I'm tired of rebasing again and again, I have switched to another plugin, take a look at here for more:

@crizant can you resolve conflicts, please, maybe they finnaly will merge it

I'm tired of rebasing again and again, I have switched to another plugin, take a look at here for more:

Thanks for the submission! We’re currently working through a large backlog of PRs, and this will require non-trivial review, so it will take a little time before we’re able to review it. As explained in CONTRIBUTING.md, votes for the corresponding issue are the primary way we’re prioritizing non-trivial reviews; this is a fairly highly-rated issue, so we expect to get to this soon after completing the in-progress null-safety migrations.
This will need a test of the code in webview_flutter.dart (that it's sent to the interface); ideally there would native testing as well, but we need infrastructure plumbed up for that for webview_flutter still, and I don't think we need to gate this change on that.
We apologize for the long delay in triaging this PR. We’re in the process of overhauling our PR triage system to respond much more quickly, as well as working through the backlog.

Since #3431 is opened and somebody is handling it, it seems that I can take some rest.
I'm closing this merge request. Guys, please follow #3431 instead.


Bulk export to JDBC

Specify a cts.query to scope data in MarkLogic
Transform documents to rows (via Objects?)
Load into JDBC
Verify results

Migrated from marklogic/data-movement#11.

@sammefford , 4.0.3 release date is Oct 23rd , next Monday. Should this be assigned to to the right tester for ship ?

@arthi-ramachandran , yes, thanks for catching that.
@vivekmuniyandi, could you take a look at the docs (including the in-line comments) for src/main/java/com/marklogic/client/example/cookbook/datamovement/BulkExportToJdbc.java and see if you have any feedback to improve it?

@sammefford Looks good. Shipping it.


Add more metadata to content pages.

This adds the following metadata to content pages:

Channel name: og:video:series
Duration/Audio Duration: og:video:duration
Release time: og:video:release_time

Some notes:

og:video:series seemed like a reasonable place to put the channel name according to the opengraph model, but let me know if you have another suggestion!
I decided to put whichever of duration or audio_duration was available into the og:video:duration property. There is an og:music:duration, but it didn't seem right to use og:music:... for one property and og:video:... for all the rest. One question: are duration and audio_duration ever both specified on a claim?

Audio content example:

Video content example:

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number: Contributes to issue #3176
What is the current behavior?
lbry.tv is missing some useful metadata on content pages.
What is the new behavior?
lbry.tv includes metadata tags for the channel name, duration, release time.
Other information

Removed the twitter:creator tag. It seems that must correspond to an actual twitter username.. it's not just a generic "creator" tag.

Thank for the PR @bwkimmel , congrats on the first one to LBRY! We'll get this reviewed soon.
Can we show you some appreciation?

@tzarebczan do you know the answer to his question?

One question: are duration and audio_duration ever both specified on a claim?

@tzarebczan do you know the answer to his question?

One question: are duration and audio_duration ever both specified on a claim?

Actually, I think the answer is no, at least according the data currently available: select count(1) from claim where duration is not null and audio_duration is not null:
{
  "success": true,
  "error": null,
  "data": [
    {
      "count(1)": 0
    }
  ]
}

Rebased on master and resolved conflict with aa45a8f85c5d4a0298b4fbb7bc555c612bb60adf. I'm not sure what the CI failure is though, looking at the details it looks unrelated to this change.

Thank you! Looks great.


Error in "./App.tsx": Module parse failed: Unexpected token

Question
I successfully set up my React native app v0.69 with Repack v3 and pnpm. I executed all the necessary steps that are here: https://re-pack.netlify.app/docs/getting-started. I can install the app with npx react-native webpack-bundle command. Also I have node v16.14.2 and I use this default webpack config template: https://github.com/callstack/repack/blob/main/templates/webpack.config.mjs
But when I start webpack with this command npx react-native webpack-start I get this error message:

If you need more information feel free to ask.

hi @sleaper ! Thanks for posting your question.
I assume after initial setup that you've mentioned you still have Metro. Can you try to run the app using metro and see if that will work ?
If yes, you can also try use node 16.15.0.

@sleaper any luck with node 16.15.0?

Could not make it work even with node v.16.15.0. For now I will have to use pnpm without symlinks.


Issue with podman play kube on Ubuntu

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
On Ubuntu, the E2e test podman generate with user and reimport kube on pod (link) fails. We have temporarily disabled the test.
The error message is:
Error: container_linux.go:349: starting container process caused "error adding seccomp rule for syscall socket: requested action matches default action of filter": OCI runtime error

I believe this is related to the recent vendor of https://github.com/seccomp/containers-golang/pull/27 into Podman. The error message in question is generated by runc when trying to add a seccomp rule whose action matches the default action of the policy; my current theory is that the specific errno number in that PR is being dropped, causing the rule to just have ActErrno - which is exactly identical to the default action.
It is presently unclear why this only occurs on one test for podman play kube.
Steps to reproduce the issue:

Create an Ubuntu 20.04 VM

Clone Podman repository and install all dependencies

Run E2E tests

Describe the results you received:
Test fails
Describe the results you expected:
Test succeeds
Additional information you deem important (e.g. issue happens only occasionally):
Core difference here appears to be crun (Fedora) vs runc (Ubuntu)
Output of podman version:
Latest master

@rhatdan @giuseppe PTAL

I think we need an updated runc that has: https://github.com/opencontainers/runc/pull/2424

@lsm5 PTAL

/usr/bin/runc on Ubuntu is owned by the distro default runc. I have set dependencies to use distro runc by default since that seemed good enough for most cases. Would it be ok to let this be until Ubuntu updates its runc?

@giuseppe @lsm5 Is this still an issue, has the runc been  updated?  Should we switch to crun?

@mheon how's this looking now?

Still being skipped on Ubuntu. I'll make a PR to try reenabling and see if it still explodes.

https://github.com/containers/podman/pull/7024


Research data transfer to database: Research implementation of data transfer

Relates to #405
[x] Research implementation of data transfer to our MongoDB database after cleaning.

https://www.notion.so/Research-Paper-Comprehensive-Analysis-and-Implementation-of-Data-Transfer-to-MongoDB-After-Data-Cle-407afad73f514be785f3110a4b875e5e?pvs=4


Serialization works even if the MLP has not been trained

Useful for n_jobs=1 in randomised grid search from sklearn.
Closes #64.

Coverage remained the same at 100.0% when pulling 026c4cd17b385df4126bd8ef9e4ffaa4522ca329 on sklearn into 6f5cf118ea1377075a1e0eec3aaed5a1a473ca42 on master.


service_linux: Fix null dereference in findLBEndpointSandbox

In findLBEndpointSandbox, there are a number of checks which can return an error message. The final check will cause the program to crash if the sandbox doesn't return an endpoint, as the error message calls methods on the null pointer. This patch fixes this to use the previous (valid) pointer to get information for the error message.

PTAL @thaJeztah


Add serialization and deserialization features for codec and borsh to the host type in ics24

Summary

## this for codec
codec = { package = "parity-scale-codec", version = "3.0.0", default-features = false, features = ["derive"] }
scale-info = { version = "2.1.2", default-features = false, features = ["derive"] }
sp-runtime = {  version = "7.0.0", default-features = false }
## this for borsh
borsh = {version = "0.9.3", default-features = false }

example case ClientId:
use serde::{Deserialize, Serialize};

use codec::{Decode, Encode};
use scale_info::TypeInfo;
use sp_runtime::RuntimeDebug;
use borsh::{BorshSerialize, BorshDeserialize};

#[derive(Clone, Debug, PartialEq, Eq, PartialOrd, Ord, Hash, Serialize, Deserialize)]
pub struct ClientId(pub String);

#[cfg(feature = "codec")]
#[derive(Clone, Debug, PartialEq, Eq, PartialOrd, Ord, Hash, Serialize, Deserialize, Encode, Decode, RuntimeDebug, TypeInfo)]
pub struct ClientId(pub String);

#[cfg(feature = "borsh")]
#[derive(Clone, Debug, PartialEq, Eq, PartialOrd, Ord, Hash, Serialize, Deserialize, BorshSerialize, BorshDeserialize)]
pub struct ClientId(pub String);

Problem Definition

Proposal

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

I encountered some problems when implementing the Encode and Decode property macros for the timestamp codec, I found that the timestamp wrapper uses the time in the tendermint and this time the crate, can't add the property macros very well, do you have any good suggestions for implementation?

I found that the timestamp wrapper uses the time in the tendermint and this time the crate, can't add the property macros very well

I don't really understand the issue you're describing here. Could you provide some relevant links (e.g. link to the macro you're referring to), and perhaps rephrase as well?

This might not be the best place for this discussion, but I had previously tried serializing via borsh (by forking ibc-rs to add #[derive]s) but found that borsh doesn't have an easy way to override specific fields of a struct with a macro like serde so it ended up being somewhat of a dead end as some underlying types (I think the timestamps in Tendermint) don't derive borsh. This could definitely be solved if someone put some more work into supporting borsh but at this time it isn't widely derived, so using borsh often requires things like deriving on wrapper structs.
Around this time, I realized that most of IBC already had protobuf serializations so it was a lot easier to commit to protobuf representation for serialization/deserialization. Maybe some guidance around using impl Protobuf, defining protobuf files, etc. might be better to nudge people towards that direction?

I found that the timestamp wrapper uses the time in the tendermint and this time the crate, can't add the property macros very well

I don't really understand the issue you're describing here. Could you provide some relevant links (e.g. link to the macro you're referring to), and perhaps rephrase as well?

Error:    --> crates/ibc/src/core/ics04_channel/packet.rs:144:5
    |
144 |     codec::Encode,
    |     ^^^^^^^^^^^^^ the trait `WrapperTypeEncode` is not implemented for `timestamp::Timestamp`
    |
    = help: the following other types implement trait `WrapperTypeEncode`:
              &T
              &mut T
              Arc<T>
              Cow<'a, T>
              Rc<T>
              alloc::boxed::Box<T>
              alloc::string::String
              alloc::vec::Vec<T>
            and 3 others
    = note: required for `timestamp::Timestamp` to implement `Encode`
    = note: this error originates in the derive macro `codec::Encode` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `timestamp::Timestamp: WrapperTypeDecode` is not satisfied
Error:    --> crates/ibc/src/core/ics04_channel/packet.rs:157:5
    |
157 |     pub timeout_timestamp: Timestamp,
    |     ^^^ the trait `WrapperTypeDecode` is not implemented for `timestamp::Timestamp`
    |
    = help: the following other types implement trait `WrapperTypeDecode`:
              Arc<T>
              Rc<T>
              alloc::boxed::Box<T>
              sp_runtime::sp_application_crypto::sp_core::Bytes
    = note: required for `timestamp::Timestamp` to implement `Decode`

error[E0277]: the trait bound `timestamp::Timestamp: TypeInfo` is not satisfied
Error:    --> crates/ibc/src/core/ics04_channel/packet.rs:157:28
    |
157 |     pub timeout_timestamp: Timestamp,
    |                            ^^^^^^^^^ the trait `TypeInfo` is not implemented for `timestamp::Timestamp`
    |
    = help: the following other types implement trait `TypeInfo`:
              &T
              &mut T
              ()
              (A, B)
              (A, B, C)
              (A, B, C, D)
              (A, B, C, D, E)
              (A, B, C, D, E, F)
            and 139 others
note: required by a bound in `FieldBuilder::<MetaForm, N>::ty`
   --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/scale-info-2.3.0/src/build.rs:458:13
    |
458 |         TY: TypeInfo + 'static + ?Sized,
    |             ^^^^^^^^ required by this bound in `FieldBuilder::<MetaForm, N>::ty`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `ibc` due to 3 previous errors
Error: warning: build failed, waiting for other jobs to finish...
error: could not compile `ibc` due to 3 previous errors
Error: The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

yet, This error message is a good illustration of what I mean

This might not be the best place for this discussion, but I had previously tried serializing via borsh (by forking ibc-rs to add #[derive]s) but found that borsh doesn't have an easy way to override specific fields of a struct with a macro like serde so it ended up being somewhat of a dead end as some underlying types (I think the timestamps in Tendermint) don't derive borsh. This could definitely be solved if someone put some more work into supporting borsh but at this time it isn't widely derived, so using borsh often requires things like deriving on wrapper structs.
Around this time, I realized that most of IBC already had protobuf serializations so it was a lot easier to commit to protobuf representation for serialization/deserialization. Maybe some guidance around using impl Protobuf, defining protobuf files, etc. might be better to nudge people towards that direction?

Hey man do you have any idea, not only borsh but also codec is like this, can't serialize and deserialize types as well as serde

This might not be the best place for this discussion, but I had previously tried serializing via borsh (by forking ibc-rs to add #[derive]s) but found that borsh doesn't have an easy way to override specific fields of a struct with a macro like serde so it ended up being somewhat of a dead end as some underlying types (I think the timestamps in Tendermint) don't derive borsh. This could definitely be solved if someone put some more work into supporting borsh but at this time it isn't widely derived, so using borsh often requires things like deriving on wrapper structs.
Around this time, I realized that most of IBC already had protobuf serializations so it was a lot easier to commit to protobuf representation for serialization/deserialization. Maybe some guidance around using impl Protobuf, defining protobuf files, etc. might be better to nudge people towards that direction?

Very insightful. Seems to be what @DaviRain-Su is encountering as well. Supporting borsh does seem like it would take a decent commitment. While I think we want to end up supporting borsh, we don't have time to focus on that in the short term. However if this is a short-term requirement for you @DaviRain-Su then it does seem like the approach to take is to make sure that every type used by an ibc struct also derives borsh serialize/deserialize. And probably the same with parity-scale-codec.

Now I have implemented codec and borsh codec for the timestamp type separately


sc-11795 User Profile: Insert space between Full Name

Scope of changes
sc-11795 User Profile: Insert space between Full Name
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
https://app.shortcut.com/rotational/story/11795/user-profile-insert-space-between-full-name

Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 0.00% // Head: 37.96% // Increases project coverage by +37.96% :tada:

Coverage data is based on head (69e5929) compared to base (181831a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##           main     #945       +/-   ##
=========================================
+ Coverage      0   37.96%   +37.96%
=========================================
  Files         0      168      +168
  Lines         0     2568     +2568
  Branches      0      667      +667
=========================================
+ Hits          0      975      +975
- Misses        0     1409     +1409
- Partials      0      184      +184

Flag
Coverage Δ

unittests
37.96% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

 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.


Merge SPQR

SPQR is published recently, and it is impressively promising!!!
Will SPQR merge into bnb?? If yes, is there explicite schedule?
Best,

I plan to merge it eventually, but there is currently no timeline.


Connecting to localhost:4000/ causes headless dlv to exit

Please answer the following before submitting your issue:
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)?

Delve Debugger
Version: 1.1.0
Build: $Id: 1990ba12450cab9425a2ae62e6ab988725023d5c $

What version of Go are you using? (go version)?
go version go1.11 linux/amd64
What operating system and processor architecture are you using?
Linux/amd64, it is already in (2)
What did you do?
Start server with:

$ dlv --listen=:4000 --headless=true --api-version=2 exec myprogram

Then run:
$ curl http://localhost:4000/

What did you expect to see?
The service replying with 400.
What did you see instead?
Service returns empty reply and exits.

This is because by default the client will exit after the first connection closes. You must use --accept-multiclient to stay alive after a client closes the connection.


2 issues noted

Helper class - SettingsHelper.cs
Had to update "_appKey" value to use "ida:ClientSecret". There is no "ida:AppKey" reference in web.config
Had to re-create the a new mdf file instead of the one in package - existing was giving read-only error to the database while updating the token cache

Closing all issues since this repo is being archived and no longer maintained.