[Proposal] IGAPP-664: Only build after checks succeeded

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.
This should be discussed.
Builds will take even longer with this change (7.30mins on average), but we would probably reduce our credit usage significantly (especially iOS builds are very expensive) if we only build our apps once tests succeeded. I would not merge this if anyone thinks even longer builds are really annoying and not worth the reduced credit usage because it makes it more tedious and time intensive for us. I am not really sure about this either.
Possible alternative: Only run iOS builds on main. However, whenever "native" dependencies are upgraded and the Podfile is out of date, this will lead to failing builds on main, so probably not really an option either.
Another possible alternative: Research why our iOS builds take over 34mins on average...
Some numbers (last 90 days):
Total credits used: 1,100,000, with 990,000 (90%) for the commit workflow.
Of these 990,000 credits of the commit workflow the build_e2e_ios job is using 805,000 (81%) and the build_e2e_android job 95,000 (9.6%) credits. The success rate of commit workflows is 43%, average duration are 42mins. 200,000 credits are 120$, so 660$ in last three months.
Some more numbers and insights:
https://app.circleci.com/insights/github/Integreat/integreat-app/workflows/commit/jobs?reporting-window=last-90-days&branch=b1d8acd4-8701-4c76-8a87-7ff2320aa95f

I personally don't have any issues with slightly longer build time, as most of us now use the auto-merge feature.
Apparently it seems to be a known issue that react-native build times are somewhere between 20-45 minutes.
On a quick search I found that you can disable flipper in the ci, which apparently should reduce the build time by about 10 minutes. I think that could be worth trying.

Fine for me! Also running our tests should not take 8 minutes to be honest :D so there is also optimization possibilities.
In general I think we should not need to care about 100-200€ per month. Thats peanuts compared to the effort we have to do here.

Fine for me! Also running our tests should not take 8 minutes to be honest :D so there is also optimization possibilities.
In general I think we should not need to care about 100-200€ per month. Thats peanuts compared to the effort we have to do here.

What do you mean by the effort we have to do here? This PR? Or the general work we put into this project?
I think we should care about money spent a tiny little bit, but I agree with you in general. However, a little bit more important to me is small resource usage/environmental impact and if we can reduce that a little bit I am all in. Sure, it's just a very tiny factor but it is something :man_shrugging:
Also agreeing with the point that test should not run for 8 minutes :astonished: I think 4 mins are yarn alone...

What do you mean by the effort we have to do here? This PR? Or the general work we put into this project?

The discussions and this PR, I think investing time into saving money/resources here is lost time.

I think we should care about money spent a tiny little bit, but I agree with you in general. However, a little bit more important to me is small resource usage/environmental impact and if we can reduce that a little bit I am all in. Sure, it's just a very tiny factor but it is something

Sure, every tiny bit helps, but as Digitalfabrik we haven't invested in "green computing" at all, so if we want to do it, then we should do it seriously.


Implement a way to write object dumps to a file

We should implement a way to write current heap dump to a file when process receives a special SIGNAL.
Such a thing can slow down the ruby process (not altogether unexpected), for first iteration we can keep it in same thread/process as main application but later on perhaps worth exploring forking a process for writing the dump file.

https://samsaffron.com/archive/2015/03/31/debugging-memory-leaks-in-ruby


Quote all fields in exported CSV files

Fields in our exported CSV files may contain commas, for example,
strings that represent functions with arguments. To ensure that these
CSV files can be correctly imported in spreadsheet applications, values
for these fields need to be quoted.
Tested: Exported CSV file from sampled callstack, imported in Google
Sheets.
Bug: http://b/181847321

I've addressed your comment that quotes need to be escaped (with another quote) when quoting the fields. I added a unit test for the CSV formatting function. The CSV formatting code and test could be moved to OrbitBase, but since they are not used anywhere else I figured it would be better to keep it local in DataView. But happy to address any additional comments if you don't agree with the choices here.


Fix: Correct the spelling of repository within the NRI plugin documentation.

These changes fix a spelling error found within the NRI plugin documentation (NRI.md) kept within the docs project directory.
In docs/NRI.md, the following spelling mistake was resolved:

a misspelled word respository has been corrected to repository, following Merriam-Webster's spelling of the word.

/retest


Not working as should

WaterBot version:
1.2.1
Steps to reproduce
Just trying to use it....
Expected behavior
Water all the plants not more then once
Actual behavior
Waters several plants more then once and others not at all. Aim seems to be off on others watering to high or low to hit the plant.

I am also having this issue.


Come up with a better way of storing Alonzo language cost models

Currently these are just stored serialized as Text. which is rather suboptimal as can be seen in this comment.
We should come up with a better way.

I asked ledger and plutus teams and it seems these parameters like if_then_else-cpu-arguments, eq_integer-memory-arguments are not stable at all (not the values, but the fields themshelves). So probably we want to avoid creating tables with columns that will change all the time.
Maybe we can store in a json format, that someone could parse if necessary?

Yes, converting to JSON makes sense. We should also put it in a separate table to make sure we are not storing multiple copies of exactly the same thing.

Currently there is a cost_model column which looks like:
fromList [(PlutusV1,"fromList [( ...

which is just the text serialized Haskell data structure.
Instead we should convert it to JSON and store it in its own table (to prevent any possible duplication)


Allow for larger range for universal offset setting

I've now had two requests to increase the range to ~200ms. I don't know how well this will work from a gameplay perspective, but am not against the change being made if we do push out updates for this .

This is probably due to Android having latency issues, which in Lazer isn't a problem anymore (hit judgements are better in Lazer). Every single time I play osu!stream, there always is this issue where I get a lot of 100s instead of 300s, especially in Expert Mode maps.


Few fixes to HTML file

Added DOCTYPE
Added alt tags to the images
Cleaned up the code(more tidy)

@Speculator101 Thanks for the contribution, good additions.


Bump slimmer for rendering app meta tag

Yo @edds. Can you add some more information about why we need this change, and whether it needs to be merged by a certain date (e.g. because the old version will stop working) please?

The only change this has is an extra meta tag will be added to the page. This will be read by the analytics JavaScript if it is there (and give us the ablity to segment performance metrics per rendering application amongst other things), it doesn't matter if it isn't present though so nothing will break with/without this. There is no dependancy or urgency on merging or deploying.

I imagine the same change should be made to the calculators app.

@floehopper indeed it will, I current making my way through our 17 frontend applications.

You beat me to it, @tadast. I was planning to rewrite the commit to include @edds comment before merging.

Oh sorry. This would have been a good thing to do. I'll be more careful next time :)

I notice that this branch (along with a number of other branches) have been merged into master without rebasing first. I think this makes the git history really hard to follow. I thought the plan was to always rebase against master before merging - have I got the wrong end of the stick?

We have no policy on rebasing on master before merging that I am aware of. Only that you should rebase to make sure your commits make logical sense.

@edds: Thanks. That's helpful to know. My comment was really addressed to @tadas who pushed the merge button. Sorry for the confusion.

I only tend to rebase when I need to tweak commits. I'm fine with rebasing before merging, but then we should write it up in the README and submit a PR where we can discuss merging practices. I'm also not a big fan of committing directly to master, so we could discuss it there too :)

Individual projects shouldn't have special instructions for PRs and merging unless there's a very good reason, because that makes it harder for people to start working on the project.  The styleguides (in particular https://github.com/alphagov/styleguides/blob/master/git.md#branchingmerging-conventions) are the place for documenting our practices.

One good reason for not rebasing before merging is that if comments have been made in github on the individual commits, rebasing will stop those comments being shown on the pull request (because the commit will no longer be part of the pull request).

Is there a better forum for this discussion? This PR doesn't seem appropriate.


Providing app/api uri should prevent the emulator from starting its own

Let's say I want to run the APP and/or API myself (maybe they run a compiler like TypeScript), I would run the emulator like so:
$> swa --app-uri=http://localhost:3000 --api-uri=http://localhost:7071

But when it starts up, it'll attempt to run its own proxies for those, and in particular the API will fail as the port is already in use.
Since there's no need for these proxies to be run by the emulator, it should skip trying to start them if you provide the uri.

I've included this in #19 Now you would do:
$> swa --use-app=http://localhost:3000 --use-api=http://localhost:7071

Would this would for you?
FYI, --app-uri and --api-uri are used to set the URI for the built-in proxies.


feat: pinning

Ref.: #518
Pin a new hash

Search

Animation while pinning

https://gyazo.com/50a063449199a3992a23bec940273ce4

I think this is working! I'd like you to that a look: @flyingzumwalt @diasdavid

I think it's done @diasdavid! 🎉 🎉 🎉 Let's merge this?

Sweeeet!! Awesome work @hacdias :)


Add Search in CWE list while selecting in template Findings

Since a few weeks I'm following this project and I've tried a few things now.
In the current version it is not possible to search in CWE list while adding a new template finding.
It would be helpful if the functionality to search in the CWE list, which is present while adding a new finding is available for adding a finding template as well.
I've attached two screenshots.
Adding a finding template without search functionality within the CWE list.

Adding a finding with functionality to search in the CWE list

@mvdvaart thank you for that I forgot the templates, fixed in 0.3 :)

Tested - Solved


How do test without Nimble

Hi
Need help in writing test cases for my project which uses RxMoyaProvider and Object mapper. Currently the calls to the n/w or using stub behaviour works fine in my code. However when I tried to do unit test cases test cases are failing and even there is no call to endpoint closure. This I obesrved with debug statement in endpoint closure.
Below is the code snippet for the test case
// initialises the oauthclient which holds variable of moyaProvider and is initialized with stub behavier
 let  ccApiOAuthClient = CCApiOAuthClient(apiKey: CC_CLIENT_API_KEY, apiSecreteToken: CC_CLIENT_SECRET_TOKEN, stubCloser: MoyaProvider.immediatelyStub, response: (200, CCStubbedResponse.stubbedResponseFromJSON(filename: "authResponse")))

        let expect = expectation(description: "subscribeNext called")

// rx_getAuthToken is the function defined in the oAthClient which in turn send the request

              _ = ccApiOAuthClient.rx_getAuthToken(username: "XYZ", password: "XYZ")
            .observeOn(MainScheduler.instance)
            .do(onNext: { oAuth2ResponseObject in
                print(oAuth2ResponseObject)
                XCTAssert(true)
               // expect.fulfill()
            })

        waitForExpectations(timeout: 2) { error in
            if let error = error {
                XCTFail("waitForExpectationsWithTimeout errored: \(error)")
            }
        }

Do next is never executed. Advice me .
Thanks in Advance
Shivayogi

Can some one help me on how to test without Nimble?

@shivayogic, in the code you posted, it doesn't look like there are any subscriptions to rx_getAuthToken, so the request won't be made. The do operator only specifies a side-effect to be performed. Try replacing the do operator with subscribe. Then uncomment the expect.fulfill() and see if this test passes.

@scottrhoyt
Thank you for the reply. I have solved the issue myself. It was a mistake on using do operator. After replacing with subscribe it is working fine.


TypeError: r.readFileSync is not a function - Shim issue with pdfkit

The addFonts functionality does not work. I went ahead and debugged your library, and seems the fs library is not shimmed correctly for the pdfkit.standalone.js as instead of returning the fs-virtual.js it returns an empty object due to the other shim libraries you have used.

https://github.com/betterwrite/pdfeasy/issues/15
I'll look into some alternatives for this, I've only tested this functionality on the server-side.

Thank you @Novout if you have any idea how to fix it let me know, maybe I can try sending a PR

Did you test it this way?
$pdf.addFonts([{
  name: 'Roboto',
  normal: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  bold: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  italic: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  bolditalic: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
}])

I put it in the playground and it worked normally.

not yet, I'll check it, but I'm pretty sure its not related to how the endpoints are declared, but mainly because the polyfill doesn't work correctly.

@Novout To replicate my issue use the following snippet of code:
  const { $pdf } = useNuxtApp();
  console.log($pdf);
  $pdf.addFonts([
    {
      name: "Roboto",
      normal:
        "https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf",
      bold: "https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf",
      italic:
        "https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf",
      bolditalic:
        "https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf",
    },
  ]);

  $pdf.new();

  $pdf.add([
    { raw: "Hello PDFEasy!", text: { font: "Roboto" } }, // text with custom font,
    { raw: "https://i.imgur.com/path.png", image: {} }, // external image
    {
      stack: [
        // stack for paragraph's
        { raw: "A ", text: {} },
        { raw: "Simple", text: { bold: true, italic: true } },
        { raw: " Stack!", text: {} },
      ],
    },
    { pageBreak: {} }, // page break
    { lineBreak: {} }, // line break
    { raw: "A checkbox!", checkbox: {} }, // checkbox
    { raw: "A list!", list: { style: "circle" } }, // list
    { raw: "https://link", qrcode: {} }, // use qrcode.js lib
    {
      table: {
        // table. Check pdfkit-table package for more explanations
        body: {
          title: "Title",
          subtitle: "subtitle",
          headers: ["Item 1", "Item 2"],
          rows: [
            ["A", "100%"],
            ["B", "50%"],
          ],
        },
        options: {},
      },
    },
    {
      form: [
        // dynamic forms
        {
          name: "button-field",
          type: "button",
          options: { label: "Click here!" },
        },
        { name: "text-field", type: "text", options: { value: "" } },
      ],
    },
  ]);

  $pdf
    .run({
      type: "client",
      // 'blob' | 'save' | 'open-link' | 'none'
      clientEmit: "save",
    })
    .then(() => {})
    .catch((err) => {
      console.error(err);
    });
});

@Novout FYI I'm also trying to generate the PDF on the server side using Nuxt API Endpoints, but also that does not work. I tried changing the cwd
 pdfeasy
    .run({
      type: "server",
      serverPath: "/public",
      cwd: process.cwd(),
    })
    .then((res) => {
      console.log(res);
    })
    .catch((err) => {
      console.log(err);
    });

but does not work.

Try to call $pdf.new() before addFonts or other content:
const { $pdf } = useNuxtApp()

$pdf.new()

$pdf.addFonts([{
  name: 'Roboto',
  normal: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  bold: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  italic: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
  bolditalic: 'https://fonts.gstatic.com/s/roboto/v19/KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf',
}])

$pdf.add([
  //...
])

// ...


Add BinaryReadable trait, implementations and endianness conversion functions

This is a prerequisite for #100.
@jemc @tonchis Do you think we really need all these read_{le,be}_u{16,32,64} functions when we could just use read_native_u16!(offset).native_to_be instead? IMHO, the latter can be quite a bit confusing, as you want to read for instance a "big endian u16 from disk" and then convert it into a native integer, but the sequence says "read a native u16 from disk and then convert it to big endian".

I just realized I didn't explicitly answer this question:

Do you think we really need all these read_{le,be}_u{16,32,64} functions when we could just use read_native_u16!(offset).native_to_be instead? IMHO, the latter can be quite a bit confusing, as you want to read for instance a "big endian u16 from disk" and then convert it into a native integer, but the sequence says "read a native u16 from disk and then convert it to big endian".

Yes, I agree with you that having the methods that are more intuitively and directly named is helpful and convenient to the developer. And they don't impose much extra maintenance burden on the standard library because they are simple. So I'm :+1: on including them as you did here.


chore: code clean up for samples are migrated to python-docs-samples

This is a repo-cleanup request.
All manually written code samples are at https://github.com/GoogleCloudPlatform/python-docs-samples/tree/main/datacatalog
For more details @ http://b/257073082
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

As identified by snippet bot, working on cl/493602812 to update docs pages

Update cl/493624574 is merged! Clearing do not merge flag.


added gym website

🛠 Fixes Issue (#555)
✅ Check List (Check all the applicable boxes)

[x] My code doesn't break any part of the project (Zero Octave-Javascript-Projects).
[x] This PR does not contain plagiarized content.
[x] My Addition/Changes works properly and matches the overall repo pattern.
[x] The title of my pull request is a short description of the requested changes.

📷 Screenshots

@Astrodevil please review

@NOiR-07 Done


Update piratebay extension

Description

Screencast

Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

Hey, thanks for first contribution! Unfortunately, we decided to not publish the Piratebay extensions. While Piratebay can be used to share files, it provides provides easy access to copyrighted content without permission. Additionally, the extension contains references to explicit adult content in the searchbar dropdown filter. Both points are against our guidelines.
I noticed that you have another extension (#5754) in review, which seems a better fit for our users. Thanks for understanding.


feature: opentelemetry 针对get请求添加 mock

Codecov Report

Merging #383 (f7a95d9) into v2.6.x_develop (9f251d3) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head f7a95d9 differs from pull request most recent head 99ed22a. Consider uploading reports for the commit 99ed22a to get more accurate results

@@               Coverage Diff               @@
##           v2.6.x_develop     #383   +/-   ##
===============================================
  Coverage           62.63%   62.63%
===============================================
  Files                 441      441
  Lines               26999    26999
===============================================
  Hits                16911    16911
  Misses              10088    10088

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 9f251d3...99ed22a. Read the comment docs.


Start Azurite if already installed

Is your feature request related to a problem? Please describe.
One of the things I forget to do when working with Storage, Queues, and Tables is starting the emulator. Most of the time I have to wait for the connection in the Storage Account > Emulator - Default Ports - Queues or Blobs to timeout before I realize that I did not start the emulator.
Describe the solution you'd like
I would like that if I am in the "Local & Attached\Storage Accounts" tree of the Explorer and the Explorer can not connect to the local emulator to either prompt me to start it, or better yet start it for me.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@jguadagno some questions for you:

How many emulators do you usually have running at once? If more than one, please be specific about how many.
Do you use Azurite?
If you do, where do you keep your Azurite data?
If you don't, what emulator are you using?

@MRayermannMSFT

How many emulators do you usually have running at once? If more than one, please be specific about how many.
Usually, one, but it depends.  On a Windows machine, I typically had the AzureStorageEmulator and Azurite (in Docker) running

Do you use Azurite?
Now I do. I have it running in Docker, plus JetBrains Rider has the ability to start an instance of Azurite

If you do, where do you keep your Azurite data?
I try to keep my data in one location for Azure c:\Projects\Data

@jguadagno thanks for answering my questions. Taking a look at JetBrains Rider definitely expanded my thoughts on what we would want to do for a "start the emulator for you" feature. For now, in 1.22, we're simply going to prompt:

We'll keep watching this issue for additional feedback from people on wanting to "start" instead of "prompt". For future people, some things we'd like to know about are (and some of these are repeat questions from above):

Would you want Storage Explorer to support starting multiple instances of Azurite for you?
Do you want started Azurite instances to keep running after Storage Explorer is closed?
Do you want to be able to stop/restart started Azurite instances while Storage Explorer is running?
Do you want to be able to see Azurite's output?
If you wanted multiple Azurite instances to be started, how would you want to configure the data locations for each instance? For a single instance, we think just having a single setting should be sufficient, but once we start thinking about multiple instances it isn't quite clear.

@MRayermannMSFT

Would you want Storage Explorer to support starting multiple instances of Azurite for you?

I could the possibility of wanting to start multiple instances if you are trying to replicate different storage regions with the same names for queues/containers or acting like different clients with the same name queues/containers

Do you want started Azurite instances to keep running after Storage Explorer is closed?

Probably not.  I typically only have it running when I start the solution and close it when the solution close (a feature of Jetbrains Rider)

Do you want to be able to stop/restart started Azurite instances while Storage Explorer is running?

For me, probably not

Do you want to be able to see Azurite's output?

The output would be helpful to ensure connection and validating content is being sent/received

If you wanted multiple Azurite instances to be started, how would you want to configure the data locations for each instance? For a single instance, we think just having a single setting should be sufficient, but once we start thinking about m
multiple instances it isn't quite clear.

I think if you have multiple instance you would want a configuration with the data location unless you have a default.  If a configuration, may like a configuration for port or port range along with storage location, Example
[
 {
  name: "Client 1",
 queuePort: 10001,
queueStorage: `/client1/queues',
storagePort: 10002,
storageStorage: `/client1/storage'
], etc...

or
[
 {
  name: 'Client 1'
 portRangeStart: 10000,
storageRoot: '/client1'
]

from the second you could infer the ports based on the standard default ports and infer the storage based on the default storage paths.

I would propose that a 4th button be added that would open command prompt with default azurite start command

Run Azurite could replace the Install Azurite button, if you do a check for it in the commonly installed places, specifically when installed along side VS 2022
https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio#run-azurite
Install Azurite should be a link and not a button, as it doesn't do the action.
Getting started developing with Azure is not smooth, tooling is spread between a number of teams, there a lot of overly verbose documents which loop link to each other and it can be frustrating and time consuming.
There needs to be a concise way to get going, and running Azurite for most users would be great.
Thank you


Problem detecting supported signature algorithms

Using TLS-Attacker (and the BSI policy test script) I found a problem in Botan where even if SHA1 was disabled in the policy, we would negotiate it in the case that the client sends no signature_algorithms due to the implicit fallback hardcoded into the TLS v1.2 spec. (Thanks!)
But now that I've fixed it (in https://github.com/randombit/botan/pull/1173), the test is still failing and I am confused by the output:
ProtocolVersionTest
 Supported protocols: TLS12
CryptoTest
 Supported cipher suites:
  TLS12: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 Supported ciphers: AES_128_GCM, AES_128_CBC, AES_256_GCM, AES_256_CBC,
 Supported key exchange algorithms: DHE_RSA, EC_DIFFIE_HELLMAN,
 Supported MAC algorithms: HMAC_SHA384, AEAD, HMAC_SHA256,
 Supported PRF algorithms: TLS_PRF_SHA256, TLS_PRF_SHA384,
 Key sizes  (0 if not provided):
  Minimum RSA key size: 2048
  Minimum EC key size: 0
  Minimum DH group size: 2048
NamedCurvesTest
 Supported named curves: BRAINPOOLP256R1 SECP384R1 BRAINPOOLP512R1 BRAINPOOLP384R1 SECP256R1
 Minimum ECDH group size: 256
SignatureAndHashAlgorithmsTest
 Supported signature and hash algorithms: RSA-SHA384 RSA-SHA256 RSA-SHA256 RSA-SHA384
CipherSuiteOrderTest
 Server cipher suite selection cannot be recognized (lees than 2 cipher suites compatible)
19:12:24.577 [main] INFO  de.rub.nds.tlsattacker.testtls.policy.BotanPolicyParser - Currently cannot handle rule allow_dtls10
...
19:12:24.578 [main] ERROR de.rub.nds.tlsattacker.testtls.policy.TlsPeerProperties - The list of signature and hash algorithms is different from the configured signature and hash algorithms
\n\nPolicy tests failed. See the recent error and the server log output.

Several strange things here. First (and most important) it rejects the configuration, even though now we correctly reject all but the policy-allowed hashes. I wondered if perhaps this was because the Botan BSI policy also allows DSA+ECDSA, but the server only has an RSA key. But I tried editing the policy to only allow RSA and that didn't seem to have any effect. Second, RSA-SHA256 and RSA-SHA384 are repeated in the  Supported signature and hash algorithms line.  And thirdly it claims that "Server cipher suite selection cannot be recognized (lees than 2 cipher suites compatible)" after telling me 8 ciphersuites are supported.

I am sorry Jack, I completely missed this issue (worked on the internal repo for a longer time). I think you can safely ignore this. This appeared to be a bug in our code. We have now released a new TLS-Attacker version and are going to work on that one in the future.
I can still look into it. Can you tell me how to run the new tls_attacker script in botan? More precisely, what is the botan_ci_tools parameter to the script?
Thanks

The idea is that points to a checkout of https://github.com/randombit/botan-ci-tools (the eventual goal of the script is to run the whole test suite as part of CI, so that repo includes a prebuild version of the TLS-Attacker jar).
It basically expects the following dir layout:
<specified dir>/TLS-Attacker
<specified dir>/TLS-Attacker/TLS-Attacker-1.2.jar
<specified dir>/TLS-Attacker/resources/testsuite
<specified dir>/TLS-Attacker/resources/fuzzing/workflows

So it almost (but does not quite) work to point it at a standard TLS-Attacker checkout. I think if you copied Runnable/target/TLS-Attacker-xxx.jar to the top level of the checkout directory, then passed the parent directory to run_tls_attacker.py, it would work.
This is kind of a mess, I should change the botan-ci-tools directory layout so it is equivalent to a standard TLS-Attacker checkout, and then have the script scan Runnable/target for anything matching TLS-Attacker-*.jar instead of hardcoding the version.

We just had a look on this and it seems that there are some bugs in the older TLS-Attacker 1.2 release. For example, the signature and hash algorithms were repeated because no hash values were computed for these enums in Java. I am sorry for the confusion.
We are currently developing a new TLS-Attacker version and do not support the older one anymore. We are also developing new tests and perform fuzzing, and give you more information once this is ready. Please do not invest your time currently to patch the TLS-Attacker scripts.
I hope this helps.

OK, thanks for letting me know. Looking forward to the new release.


✨ disable colors when log format is plain and dagger is not attached to console (or provide a switch to disable colors in logs)

What are you trying to do?
I try to get logs with no colors so it is easy to read dagger logs collected by some CI system.
Why is this important to you?
It is hard to read when ANSI color codes are displayed in a log when coloring is not available.
How are you currently working around this?
no workaround, getting json is not an option as it is totally not human readable

Hey! If it's alright I can try to take a look at this.

Actually this is a lot more than I originally thought. If someone else wants to take a look into this, please feel free.

Close this one. Logs has been revamped.


Show top comment on threads in full view.

similar to how in Feed it shows you the most recent comment by a user you follow, you should be able to see, and then reply to, the top comment on a thread without having to open the post or the post dialog.

for a compact view, we can have both the thread and the comment collapsed.

Very computational expensive, in other words, long load time


Beachmark for RSA circuit

@vuvoth is the intention here to benchmark different implementations of RSA circuit?

Thank FYI! I think I will benchmark all of them.

I finished benchmark here.


Gamespy 2 support.

I can take this issue on, there doesn't seem to be a PR for it now but I will open once I start.

I would be glad if you'll be up to take this.
I think there will be a need to synchronize and standardize some stuff, but having the implementation done is a greater priority.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_41ce26b0-3909-43d1-8ea6-b6ddbdc3b1be/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_41ce26b0-3909-43d1-8ea6-b6ddbdc3b1be.git

Docs Build status updates of commit 280eda4:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 280eda4:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 280eda4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/VSC-Service-Account/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 280eda4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/VSC-Service-Account/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Deprecate/Remove PayPal adaptive

Related to https://github.com/opencollective/opencollective/issues/4210
Motivation

PayPal adaptive has been deprecated by PayPal for at least 3 years now
They are publishing breaking changes on this API with notices (e.g. https://github.com/opencollective/opencollective/issues/6074, https://github.com/opencollective/opencollective/issues/4021)
We have a replacement solution that is more stable, cheaper & better tested (PayPal Payouts)
Overall, we want to distance ourselves as much as possible from PayPal given its history of obscure business practices & low security.

Proposed plan

[ ] Make sure it's not possible to connect PayPal adaptive anymore
[ ] Send a notice to hosts still using it to warn them that the feature will be removed in 3 months
[ ] In 3 months, disable the feature
[ ] In 4 months, remove it entirely

Yet another adaptive breaking change: https://github.com/opencollective/opencollective/issues/6581. I'm discussing with OCEU about moving them to PayPal payouts.

This issue is making it more complex to optimize the host admin page, because we need to refetch the balance for adaptive in multiple occasions. I'm willing to iterate on it.
Some data first:

slug
total expenses
total expenses in the last 6 months

wwcodeinc
37
37

europe
12
12

dosecrets
8
3

nfsc
7
7

allforclimate
7
1

platform6-coop
6
6

out4s
5
3

barcamp-events-llc
3
0

wandelbuendnis
3
0

tilde
2
0

our-sci
2
2

daarpr
2
0

osgeo-foundation
1
1

cscicorg
1
0

kanium-host
1
0

islah-reparations-project
1
0

mariposasrebeldes
1
1

opensource
1
0

shivamgoyal
0
0

popsolutions
0
0

sylvain-viste
0
0

the-schumacher-institute
0
0

numfocus
0
0

priyanshu
0
0

reculture
0
0

the-advocacy-academy
0
0

biowoborders
0
0

cesakparis
0
0

scambi
0
0

lorax
0
0

3mdeb_com
0
0

drake-connally
0
0

lucy-parsons-labs
0
0

bcc-tucson
0
0

mentoralia-a-c
0
0

morevnaproject-ru
0
0

monachelle
0
0

ebnull-org
0
0

ussen
0
0

openworm
0
0

transition-network
0
0

treeoflight
0
0

silicon-valley-robotics
0
0

b3log
0
0

felinn
0
0

adminforumlumiar
0
0

the-radical-bus-ny
0
0

p0ly186
0
0

wisdomenigma
0
0

guilded-lca
0
0

2b2tjb-o
0
0

fig-tree
0
0

gradsflow
0
0

fya
0
0

thenewoilmedia
0
0

foodandsolidarity
0
0

vigilfordemocracyllc
0
0

pentakly
0
0

navel
0
0

playzinhoagro
0
0

higenku
0
0

bria
0
0

fun4cash
0
0

gurm-studios
0
0

warriors
0
0

island-17
0
0

living-era
0
0

alexa777
0
0

homin-org
0
0

ppy
0
0

zenbu-ui
0
0

arcaelas
0
0

idevdata
0
0

black-trans-texas-connection
0
0

sitt-community-group
0
0

eastg-a-better-future
0
0

nobodyfilm
0
0

e_foundation
0
0

traderz
0
0

estraperlo-scoop
0
0

eref
0
0

codewithvladperchi
0
0

kerygmadigital
0
0

projectanomalydev
0
0

paramitalab
0
0

casual-simulation
0
0

yottabitconsultingllc
0
0

hilfe-fur-die-ukraine
0
0

open-business-collective
0
0

luninuxos
0
0

baby-lion-2
0
0

student-co-op-homes1
0
0

heimdall-intranet
0
0

developer-noon
0
0

bkind-family-services
0
0

nexopia
0
0

dreamsee
0
0

ipare
0
0

celendibot
0
0

centurymine
0
0

justjazzfoundation
0
0

sikh-community1
0
0

nexuscity
0
0

ua
0
0

materialize
0
0

scriptkkiddie-org
0
0

baliz-orphanage-foundation
0
0

libhv
0
0

fertiles
0
0

cwc-digital-commune
0
0

barkayma
0
0

the-valiant-sailor
0
0

earth-arts
0
0

opendreamnet
0
0

edlibnetwork
0
0

tminiilasold
0
0

anonymous1182
0
0

huddlecraft
0
0

brown-university-aaup
0
0

chua-benh
0
0

cb-intelligence
0
0

muslimbc
0
0

good-phone-foundation
0
0

stroud-district-community-hubs
0
0

odroe
0
0

risk-of-thunder
0
0

sea-turtle-express
0
0

foss-gmbh
0
0

leosac
0
0

kikdoubt
0
0

dreamvillagegh
0
0

weather-ranch
0
0

mphimla23
0
0

efa
0
0

sir-amimo-media
0
0

teamfund
0
0

neurodiversityfoundation
0
0

jamarcus-miller1
0
0

buckners-place
0
0

belovedcommune
0
0

greengold
0
0

netty_project
0
0

cct
0
0

the-4th-hokage
0
0

tbd
0
0

constantine-millan11111
0
0

indigigenius-org
0
0

codecrumbs-io-org
0
0

dp-network1
0
0

devsblue
0
0

goodancestor
0
0

savannabits-ltd
0
0

playfullearning
0
0

c8786
0
0

nuclear-electrical-engineers
0
0

curse-brand702
0
0

osusume
0
0

business-platform-srf15-74
0
0

opendesert
0
0

d17
0
0

chingo-tribe
0
0

ukrainian-culture-series1
0
0

gowanusdredgerscanoeclub
0
0

connect
0
0

azzuradigitaldonate
0
0

onelitefeather-host
0
0

crossdb
0
0

dystopian-arts-llc
0
0

for-the-better-of-humanity
0
0

jco72
0
0

amtv
0
0

jco721
0
0

treasurer2
0
0

openmiami-host
0
0

opencollective
0
0

calderbootstrap-org
0
0

knightslca
0
0

paris
0
0

joke2k
0
0

hodierne-ventures
0
0

luandro
0
0

scicommxyz
0
0

wpf
0
0

general-intellect-sl
0
0

matthias-wilke
0
0

recaptimesquad
0
0

kent-food-hubs-cic
0
0

sentrium
0
0

joshua-casey
0
0

Query

select C.slug, COUNT(t.id) AS total_transactions,
    COUNT(t.id) FILTER (WHERE t."createdAt" > NOW() - INTERVAL '6 month') AS total_transactions_last_6_months
from "PaymentMethods" pm
INNER JOIN "Collectives" C on pm."CollectiveId" = C.id
LEFT JOIN "Transactions" t ON t."PaymentMethodId" = pm.id AND t.kind = 'EXPENSE' AND t.type ='DEBIT'
WHERE pm.service = 'paypal' AND pm.type ='adaptive'
AND pm."deletedAt" IS NULL
AND pm."expiryDate" > NOW() - INTERVAL '6 month'
GROUP BY C.id
ORDER BY COUNT(t.id) DESC

Actions

Prevent new hosts that don't have adaptive set up already from connecting it
Remove adaptive for all hosts that are not using it

I just disabled adaptive for all hosts that never used it (deletedAt = '2023-06-27 10:05:28.682000 +00:00').
Details

'amtv',
'treasurer2',
'openmiami-host',
'calderbootstrap-org',
'knightslca',
'paris',
'joke2k',
'hodierne-ventures',
'luandro',
'scicommxyz',
'wpf',
'platform6-coop',
'general-intellect-sl',
'aissat-abdelwahab',
'matthias-wilke',
'kent-food-hubs-cic',
'shivamgoyal',
'popsolutions',
'sylvain-viste',
'the-schumacher-institute',
'numfocus',
'wandelbuendnis',
'reculture',
'the-advocacy-academy',
'biowoborders',
'cesakparis',
'lorax',
'3mdeb_com',
'drake-connally',
'lucy-parsons-labs',
'bcc-tucson',
'mentoralia-a-c',
'monachelle',
'ebnull-org',
'ussen',
'openworm',
'treeoflight',
'silicon-valley-robotics',
'b3log',
'felinn',
'adminforumlumiar',
'the-radical-bus-ny',
'p0ly186',
'wisdomenigma',
'2b2tjb-o',
'fig-tree',
'fya',
'thenewoilmedia',
'foodandsolidarity',
'pentakly',
'navel',
'playzinhoagro',
'bria',
'island-17',
'alexa777',
'ppy',
'zenbu-ui',
'arcaelas',
'black-trans-texas-connection',
'sitt-community-group',
'e_foundation',
'traderz',
'estraperlo-scoop',
'eref',
'codewithvladperchi',
'kerygmadigital',
'projectanomalydev',
'paramitalab',
'casual-simulation',
'yottabitconsultingllc',
'hilfe-fur-die-ukraine',
'open-business-collective',
'luninuxos',
'baby-lion-2',
'student-co-op-homes1',
'heimdall-intranet',
'developer-noon',
'bkind-family-services',
'nexopia',
'dreamsee',
'ipare',
'celendibot',
'centurymine',
'justjazzfoundation',
'sikh-community1',
'nexuscity',
'ua',
'materialize',
'hackers-collective',
'baliz-orphanage-foundation',
'libhv',
'fertiles',
'cwc-digital-commune',
'barkayma',
'the-valiant-sailor',
'earth-arts',
'opendreamnet',
'edlibnetwork',
'tminiilasold',
'huddlecraft',
'brown-university-aaup',
'chua-benh',
'cb-intelligence',
'muslimbc',
'good-phone-foundation',
'stroud-district-community-hubs',
'odroe',
'risk-of-thunder',
'sea-turtle-express',
'foss-gmbh',
'leosac',
'kikdoubt',
'dreamvillagegh',
'weather-ranch',
'mphimla23',
'efa',
'sir-amimo-media',
'teamfund',
'neurodiversityfoundation',
'jamarcus-miller1',
'buckners-place',
'belovedcommune',
'greengold',
'netty_project',
'cct',
'the-4th-hokage',
'tbd',
'constantine-millan11111',
'indigigenius-org',
'codecrumbs-io-org',
'dp-network1',
'devsblue',
'goodancestor',
'savannabits-ltd',
'playfullearning',
'c8786',
'nuclear-electrical-engineers',
'curse-brand702',
'osusume',
'business-platform-srf15-74',
'opendesert',
'd17',
'chingo-tribe',
'ukrainian-culture-series1',
'gowanusdredgerscanoeclub',
'connect',
'azzuradigitaldonate',
'onelitefeather-host',
'crossdb',
'dystopian-arts-llc',
'for-the-better-of-humanity'

We're now down to a list of 15 hosts

slug
total expenses
total expenses in the last 6 months

wwcodeinc
48
43

allforclimate
7
0

europe
6
6

out4s
5
3

dosecrets
5
5

barcamp-events-llc
3
0

our-sci
2
1

tilde
2
0

mariposasrebeldes
1
1

islah-reparations-project
1
0

cscicorg
1
0

nfsc
1
1

transition-network
1
1

osgeo-foundation
1
0

opensource
1
0

OCEU's request for PayPal payouts got rejected. Seems like we'll be stuck with adaptive for some time.


Mining Speed / ETA is not Accurate

How To Fix:
File: resmon.lua
Line: 641
Fix: Change "if delta_ore_since_last_update > 0 then " to "if delta_ore_since_last_update ~= 0 then"
"delta_ore_since_last_update" is always 0 or a negative number, thus this condition is never true.

While changing this to ~= would have an effect, it wouldn't really be the desired one. In order to actually fix this, we really need to keep a few snapshots, over time, of how many changes happen to the field and how long each change took from the last change. I haven't run a long test yet, but so far, in my own game, my linked change is now showing accurate field rates (the 34m field drained in 34m wall clock time, the 1h15m field drained in 1h15m, etc.) My patch isn't perfect, it needs at least two snapshots of data to produce valid results, so fields that are idle when the new code is rolled out will end up showing nonsense data for their mining rate until they spin up and mine again (the first data snapshot is grabbed automatically from existing variables).
I'll continue to test it in my personal game, but so far, it's working great for me.

While changing this to ~= would have an effect, it wouldn't really be the desired one. In order to actually fix this, we really need to keep a few snapshots, over time, of how many changes happen to the field and how long each change took from the last change. I haven't run a long test yet, but so far, in my own game, my linked change is now showing accurate field rates (the 34m field drained in 34m wall clock time, the 1h15m field drained in 1h15m, etc.) My patch isn't perfect, it needs at least two snapshots of data to produce valid results, so fields that are idle when the new code is rolled out will end up showing nonsense data for their mining rate until they spin up and mine again (the first data snapshot is grabbed automatically from existing variables).
I'll continue to test it in my personal game, but so far, it's working great for me.


Can't install on Rails 5

I want to use Refile for AJAX file upload in app based on Rails 5.0.0.beta3. I added this to Gemfile as mentioned in docs:
gem 'refile', require: 'refile/rails'
gem 'refile-mini_magick'

Then after running bundle install I get the following error:
Fetching gem metadata from https://rubygems.org/.............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies.......
Bundler could not find compatible versions for gem "rack":
  In snapshot (Gemfile.lock):
    rack (= 2.0.0.alpha)

  In Gemfile:
    unicorn (>= 0) ruby depends on
      rack (>= 0) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack (~> 2.x) ruby

    sass-rails (>= 3.2) ruby depends on
      sprockets (< 4.0, >= 2.8) ruby depends on
        rack (< 3, > 1) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack-test (~> 0.6.3) ruby depends on
            rack (>= 1.0) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack-test (~> 0.6.3) ruby depends on
            rack (>= 1.0) ruby

    refile-mini_magick (>= 0) ruby depends on
      refile (~> 0.5) ruby depends on
        sinatra (~> 1.4.5) ruby depends on
          rack (~> 1.4) ruby

    unicorn (>= 0) ruby depends on
      rack (>= 0) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

bundle update didn't help. I also tried to delete Gemfile.lock and run bundle install again, didn't help also.
It's important to mention that I included latest version of rack in my Gemfile, because of this error - https://github.com/activeadmin/activeadmin/issues/4327:
gem 'rack', github: 'rack/rack'

I guess Sinatra is causing this problem.
I tried to remove gem 'refile-mini_magick' because I don't need to do any image processing. The gem was successfully installed with version 0.3.0. This is kind of old (14 Dec 2014) so I decided to switch to master. No luck:
Updating git://github.com/refile/refile.git
warning: expected SRV RR, found RR type 1
Fetching gem metadata from https://rubygems.org/.............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Resolving dependencies.....
Bundler could not find compatible versions for gem "rack":
  In snapshot (Gemfile.lock):
    rack (= 2.0.0.alpha)

  In Gemfile:
    unicorn (>= 0) ruby depends on
      rack (>= 0) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack (~> 2.x) ruby

    sass-rails (>= 3.2) ruby depends on
      sprockets (< 4.0, >= 2.8) ruby depends on
        rack (< 3, > 1) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack-test (~> 0.6.3) ruby depends on
            rack (>= 1.0) ruby

    rails (< 5.1, >= 5.0.0.beta1) ruby depends on
      railties (= 5.0.0.beta3) ruby depends on
        actionpack (= 5.0.0.beta3) ruby depends on
          rack-test (~> 0.6.3) ruby depends on
            rack (>= 1.0) ruby

    refile (>= 0) ruby depends on
      sinatra (>= 1.4.5) ruby depends on
        rack (~> 1.4) ruby

    unicorn (>= 0) ruby depends on
      rack (>= 0) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Then during problem investigating I saw separate Gemfile for Rails 5 master, but I haven't found a way to specify it instead of one that's in the repo root.

I added the latest version of Sinatra:
gem 'sinatra', github: 'sinatra/sinatra'

And gems were installed successfully.

Adding sinatra explicitly does not work for me, same error. (Rails 5.0.0rc1)

I removed the version dependency as sinatra needs to release a new version( the requirement for rack 2.x is in the master branch gemspec file. A temporary solution that I would not recommend in the long run is:
´gem 'refile´, require: ´refile/rails', github: 'pgericson/refile', branch: 'stupid-hack-sinatra-version'
the commit

I removed the version dependency as sinatra needs to release a new version. The requirement for rack 2.x of sinatra is in the master branch gemspec file . A temporary solution that I would not recommend in the long run is:
gem 'sinatra', github: 'sinatra' #require master to get the rack >= 2.0
gem 'refile', require: 'refile/rails', github: 'pgericson/refile', branch: 'stupid-hack-sinatra-version'` # remove version on gem dependency to use sinatra master branch
gem 'refile-mini_magick'

the commit

thanks so much! @pgericson

Here's a solution that's a bit easier than maintaining a fork: specify that you want to use the github repo for refile, refile-mini_magick, and sinatra:
gem 'refile', github: 'refile/refile', require: 'refile/rails'
gem 'refile-mini_magick', github: 'refile/refile-mini_magick'
gem 'sinatra', github: 'sinatra/sinatra', branch: 'master'

/cc @pgericson @dongennl

Thanks @mculp. Looks like some commits to master broke your solution: https://github.com/sinatra/sinatra/commit/13fec9cf160946ee7d044b7728b2b56cb38f6059
  gem 'refile', github: 'refile/refile', require: 'refile/rails'
  gem 'refile-mini_magick', github: 'refile/refile-mini_magick'
  gem 'sinatra', github: 'sinatra/sinatra', ref: "88a1ba7bfb2262b68391d2490dbb440184b9f838"

got me working again.

Looks like in rails <IP_ADDRESS> refile has a pendency with old version of rest-client:
refile was resolved to 0.6.2, which depends on
      mime-types

    refile was resolved to 0.6.2, which depends on
      rest-client (~> 1.8) was resolved to 1.8.0, which depends on
        mime-types (< 3.0, >= 1.16)

I was trying to do what was listed here, but since I am using refile-s3 it's was breaking anyway.
I was using refile-s3 with  0.1.0 version and the dependency was refile ~> 0.5.0.
gem "refile", require: "refile/rails"
gem "refile-mini_magick"
gem "refile-s3", '~> 0.1.0'

Using this refile-s3 version was causing this error:
Bundler could not find compatible versions for gem "mime-types":
  In snapshot (Gemfile.lock):
    mime-types (= 3.1)

  In Gemfile:
    capybara (~> 2.7.1) was resolved to 2.7.1, which depends on
      mime-types (>= 1.16)

    rails (>= <IP_ADDRESS>, ~> 5.0.0) was resolved to <IP_ADDRESS>, which depends on
      actionmailer (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
        mail (>= 2.5.4, ~> 2.5) was resolved to 2.6.4, which depends on
          mime-types (< 4, >= 1.16)

    refile-s3 (~> 0.1.0) was resolved to 0.1.0, which depends on
      refile (~> 0.5.0) was resolved to 0.5.4, which depends on
        mime-types

    refile-s3 (~> 0.1.0) was resolved to 0.1.0, which depends on
      refile (~> 0.5.0) was resolved to 0.5.4, which depends on
        rest-client (~> 1.7.2) was resolved to 1.7.2, which depends on
          mime-types (< 3.0, >= 1.16)

Bundler could not find compatible versions for gem "rack":
  In snapshot (Gemfile.lock):
    rack (= 2.0.1)
  In Gemfile:
    rails (>= <IP_ADDRESS>, ~> 5.0.0) was resolved to <IP_ADDRESS>, which depends on
      railties (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
        actionpack (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
          rack (~> 2.0)

    refile-s3 (~> 0.1.0) was resolved to 0.1.0, which depends on
      refile (~> 0.5.0) was resolved to 0.5.0, which depends on
        sinatra (~> 1.4.5) was resolved to 1.4.5, which depends on
          rack (~> 1.4)

    sass-rails (~> 5.0) was resolved to 5.0.6, which depends on
      sprockets (< 4.0, >= 2.8) was resolved to 3.7.0, which depends on
        rack (< 3, > 1)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

Looking into this, I noticed that the problem was the rest-client that was using a mime-type with older version and rails 5 need rack version ~> 2.0.
Updating gem file to use `refile-s3 ~> 0.2.0` `rack` problem did not happen again.
Bundler could not find compatible versions for gem "mime-types":
  In snapshot (Gemfile.lock):
    mime-types (= 3.1)

  In Gemfile:
    capybara (~> 2.7.1) was resolved to 2.7.1, which depends on
      mime-types (>= 1.16)

    rails (>= <IP_ADDRESS>, ~> 5.0.0) was resolved to <IP_ADDRESS>, which depends on
      actionmailer (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
        mail (>= 2.5.4, ~> 2.5) was resolved to 2.6.4, which depends on
          mime-types (< 4, >= 1.16)

    refile-s3 (~> 0.2.0) was resolved to 0.2.0, which depends on
      refile (~> 0.6.0) was resolved to 0.6.0, which depends on
        mime-types

    refile-s3 (~> 0.2.0) was resolved to 0.2.0, which depends on
      refile (~> 0.6.0) was resolved to 0.6.0, which depends on
        rest-client (~> 1.8) was resolved to 1.8.0, which depends on
          mime-types (< 3.0, >= 1.16)

The problem is that rest-client ~> 1.8 needs mime-types between version 1.16 and 3.0 and refile is not defining the mime-type version which is getting the 3.1 version.
Looking into rest-client changelog, the version 2.0 is not going to support ruby 1.9.x anymore and Refile ruby version dependency is >= 2.1.0. Which means we can set the rest-client version to newer version without breaking anything.
So I make a fork and fixed this: https://github.com/manfe/refile/commit/6005d0d7df3d9a84529093ca47b8d91e1ff93c07
Also I am going to create a PR for this. Tried to explain eveything.
For now I am using this, without need to explicity set in Gemfile rack and sinatra.
gem "refile", require: "refile/rails", github: 'manfe/refile'
gem "refile-mini_magick"
gem "refile-s3", '~> 0.2.0'

This one got me working, but there has to be a better solution:
  gem 'refile', github: 'refile/refile', require: 'refile/rails'
  gem 'refile-mini_magick', github: 'refile/refile-mini_magick'
  gem 'sinatra', github: 'sinatra/sinatra', ref: "88a1ba7bfb2262b68391d2490dbb440184b9f838"

@mculp solutions works on Rails <IP_ADDRESS>. Thanks.

I got the same problem. Is there an official solution for this? Or whats the most recommended solution for production?
I'm in Rails <IP_ADDRESS>

As the error message says, the error is on the mime-types dependency.
Can anyone fix that in a pull request?
I would be glad to merge it.

Better saying, bundle update refile mime-types would do the job.
Seems like the mime-types is pinned at your Gemfile.lock for some reason, refile should be compatible with rails 5 on master these days.
Thanks.


Reorganized and cleaned up dircon_utils.

-Moved to solvers/ directory as optimization_utils, since it is not dircon specific.
-Added documentation.
-Made use of new MathematicalProgram.GetAllConstraints().
-Changed all APIs to use better naming schemes and appropriate use of const references and pointers.

No hurry on this one either. It's an API change, which will definitely effect your code.
I'd appreciate a review of the API and documentation.


Documentation issue

The code in README is wrong. The part where we get the Host from the config doesn't work.
This doesn't work
server.Config.Host()

This works
server.URL().Host

Fixed!


Requests appear aborted before handler over HTTP/1.1

Describe the bug
The signal request.signal on a UniversalServerRequest is aborted as soon as the request body has been read, at least over HTTP/1.1.  As a result, for most rpc handlers the request appears aborted before the handler begins (since the request has already been read).  Ideally the signal would not be aborted until the underlying connection closes.
To Reproduce
Create an rpc handler using node HTTP/1.1, hit the endpoint with a POST request, and read request.signal.aborted at the top of the handler.  It will appear aborted (i.e. take the value true) even though the client and server maintain a connection, and the client will be able to receive the response.
Environment (please complete the following information):

@connectrpc/connect-node version: on latest 1.3.0, likely going back further as well.
Node.js version: v16+

Additional context
The issue most likely goes back to this change in node v16 https://github.com/nodejs/node/issues/40775, where the 'close' event on an IncomingMessage indicates that you've read the whole message, whereas in the past it represented the resource underlying the request (i.e. would not close until the request/response flow ended, either due to actions taken by the server or client).  I believe the more straightforward fix may be to use the node response object's 'close' event rather than the request object's here: https://github.com/connectrpc/connect-es/blob/fa7726b598391b8dfd0e9f14e27dcc87aca74146/packages/connect-node/src/node-universal-handler.ts#L120-L121

Thank you for reporting and for finding the node issue! I can reproduce. Not sure if relying on the response is the solution here.

I also just ran into this issue when switching a service from http2 to http. My logger includes whether or not a response was aborted. It was very confusing and concerning to see that all of our requests were now being aborted. It also broke logic in our code that uses the abort signal.
This is quite a significant bug. It effectively eliminates http1 as an option for any moderately complex Connect server.

Thank you for reporting and for finding the node issue! I can reproduce. Not sure if relying on the response is the solution here.

@srikrsna-buf, can you still reproduce this after https://github.com/connectrpc/connect-es/pull/1206?

I still can, the fix in #1181 seems to work, but I am trying to see if we can do this in a backward compatible way.

I still can, the fix in #1181 seems to work,

Thanks 😞

but I am trying to see if we can do this in a backward compatible way.

The function has a comment basically marking it as private, but I agree it would be good to not break.


Enable Scratch containers

As of now images need at least cp and sh (even though they don't need job-shim anymore).  We should figure out a way to rid these last dependencies so users can use FROM scratch.

I believe we now support whatever containers the user wants because the sh and cp are present in the worker's init container.


merge from arlac77/template-arlac77-github,arlac77/template-esm-only,arlac77/template-node-component

package.json

chore(package): add ^17.0.8 remove ^17.0.7 (devDependencies.semantic-release)

:tada: This PR is included in version 3.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Where I can take an APK file?

Hi! I want to test Your Android app AR Cut & Paste. But I can't compile repo to APK. Please, drop me a file.

Sorry, this is a prototype that requires building from a terminal. Please follow the instructions in the /app folder.


[QST]  'Tibble' object has no attribute 'to_clipbaord'

Question about datar
I want to copy a dataframe to clipboard()
`
from datar.all import *
(df >> mutate(test = 1) ).to_clipboard()
#'Tibble' object has no attribute 'to_clipbaord'
`
Sometimes the function 'to_clipboard()' works,but sometimes does not.

Could you point out when it works and when it doesn't, and provide a reproducible and runnable code?


Don't enforce existence of X-Forward-For on non-websocket requests

This was breaking healthchecks coming directly over the UNIX socket.
:eyeglasses: @bsimpson63 @dellis23

🐟

🐟


refactor: revamp project

Pull Request Test Coverage Report for Build 19

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 15:
0.0%

Covered Lines:
19

Relevant Lines:
19

💛  - Coveralls


New component: Popover (formerly Toggletip)

Need to research a new component that is visually similar to a tooltip, but perhaps is better for containing interactive elements.
https://carbondesignsystem.com/components/toggletip/usage/

Figma: https://www.figma.com/file/z2H2qv9iYQX942LqToCuQE/Components---Data-Display?type=design&node-id=625%3A21846&t=O0EUkNbsDC83olKU-1
Inspiration:

https://mantine.dev/core/popover
https://carbondesignsystem.com/components/toggletip/usage/
https://getbootstrap.com/docs/5.3/components/popovers/

AC

1.0 Popover is triggered by clicking on a focusable element (button, input, etc.).
-- 1.1 you can set popover to be triggered on hover if necessary.
2.0 Positioning
-- 2.1 Default positioning is centered below the trigger
-- 2.2 Use popper.js to adjust the position
3.0 Keyboard
-- 3.1 Pressing Tab or Enter also opens and closes the popover
-- 3.2 When focus is inside the popover then you can press Escape to close, and focus goes back to the triggering element.
-- 3.3 If there aren't any focusable elements inside the popover and focus is still on the triggering element, Escape does not close the popover.
-- 3.4 If there are focusable elements inside the popover, you should be able to set focus automatically to the first item and trap focus inside the popover.

4.0 Popover width
-- 4.1 Width can be manually set to any pixel value

-- 4.2 Width can also be set to automatically match the width of the triggering element

5.0 Disabled or unfocusable elements
-- 5.1 (per Bootstrap) Elements with the disabled attribute aren’t interactive, meaning users cannot hover or click them to trigger a popover. As a workaround, you’ll want to trigger the popover from a wrapper  or , ideally made keyboard-focusable using tabindex="0".
6.0 Popover anatomy and contents
-- You can put just about anything inside a popover, although putting something like a dropdown or tooltip is probably not advised.
-- Popover has a main content area, and optional header and footer

7.0 Accessibility
-- Popover element has role="dialog" and aria-labelledby="target-id" attributes
-- Target element has aria-haspopup="dialog", aria-expanded, aria-controls="popover-id" attributes
8.0 Dark mode inverse available.

Sarah has presented a use case that would like Popovers to support the ability of being open by default without click or hover


Make the default test-app an Embroider app

I mean it would make sense for the test-app to be an Embroider app instead of a classic one?

I mean it would make sense for the test-app to be an Embroider app instead of a classic one?

Maybe, but that would mean we would also have to modify the ember-try setup (which we currenty don't have touch, as that comes from the official app blueprint), since it assumes a classic app, and only "converts" (by means of @embroider/test-setup) it to Embroider for the two Embroider specific scenarios. So with that change it would effectively only have test coverage for Embroider, not for a classic app... 🤔

I think right now the test-app runs as both embroider and classic, using @embroider/test-setup. It's important for addon authors to test under both.
(If I'm wrong about that we can definitely reopen.)


page.setRequestInterception(true); always throw exception " UnhandledPromiseRejectionWarning: Error: Protocol error (Fetch.enable): 'Fetch.enable' wasn't found"

Steps to reproduce
Tell us about your environment:

Puppeteer version:
1.17.0

Platform / OS version:
Windows 7 Enterprise 64
Chrome Version 71.0.3578.98 (Official Build) (64-bit)

Node.js version:
v12.1.0

What steps will reproduce the problem?
While using local Chrome with path specified not able to intercept request and it throws error as
(node:56332) UnhandledPromiseRejectionWarning: Error: Protocol error (Fetch.enable): 'Fetch.enable' wasn't found
at ..\node_modules\puppeteer\lib\Connection.js:183:56
at new Promise ()
at CDPSession.send (..\node_modules\puppeteer\lib\Connection.js:182:12)
at NetworkManager._updateProtocolRequestInterception (..\node_modules\puppeteer\lib\NetworkManager.js:145:22)
at NetworkManager.setRequestInterception (..\node_modules\puppeteer\lib\NetworkManager.js:134:16)
at Page.setRequestInterception (..\node_modules\puppeteer\lib\Page.js:244:48)
at Page. ..\node_modules\puppeteer\lib\helper.js:111:23)
at processTicksAndRejections (internal/process/task_queues.js:89:5)

(node:56332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:56332) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I have removed local path reference from above trace but that is the error
Please include code that reproduces the issue.
configuration for browser
headless: true,
executablePath: 'chrome.exe',
devtools: true,
ignoreHTTPSErrors: true,
args: ['--enable-features=NetworkService']
What is the expected result?
To intercept the request which works on Chromium properly
What happens instead?
It throws this error and the script stops.

@faiyazshk if you use custom chrome executable, please use version of Puppeteer that matches chromium version.
Please check out our FAQ Entry: Q: Why doesn’t Puppeteer v.XXX work with Chromium v.YYY?

I went back to the version for chrome 71
"puppeteer-core": {
"version": "1.9.0",
"resolved": "https://registry.npmjs.org/puppeteer-core/-/puppeteer-core-1.9.0.tgz"
but still I am not able to intercept the request only response interception works when used in isolation but if used alongwith with request inception that also fails.

@faiyazshk at least the "Protocol error (Fetch.enable): 'Fetch.enable' wasn't found" shouldn't happen any more. For the other problem you have, please file a separate issue with a repro script that we can use to debug your problem.

fetch.enable is still an issue I found out it goes away when I disable devtools. The real problem is request interception it just does not work with chrome 71 with devtools enable it give fetch.enable error and without it, it goes straight without doing anything.

Puppeteer 1.9.0 doesn't use fetch domain at all. I'm not sure what errors are you seeing there.
Do you have a script that I can try running and reproduce it locally?

Here is the script
const puppeteer = require('puppeteer-core');
async function main() {
const browser = await puppeteer.launch({
headless: false,
executablePath: 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe',
devtools: false,
});
const page = await browser.newPage();
await page.setUserAgent('Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36');
await page.goto('https://www.google.com',{'networkIdleTimeout0': 5000, waitUntil: 'networkidle0', timeout: 3000000});
await page.waitForSelector('#tsf');
await page.type('input[name=q]', "Quantum Mechanics", {delay: 20});
//await page.setRequestInterception(true);
/*page.on('request', async request => {
    console.log('INTERCEPTED Request: ' + request.url());
    console.log(await response.method());
});*/
page.on('response', async response => {
    console.log('INTERCEPTED Response: ' + response.url());
    console.log(await response.status());
});
await page.click('input[name=btnK]');

}
main()

Run as is and see response
Run uncommenting just line 15
Run uncommenting everything.

I'm getting this exact same error with puppeteer 1.20.0 with 69.0.3497.81. I found that the error goes away if I stick with puppeteer 1.8.0 with 69.0.3497.81.
Seems like a regression?
const makePage = async (_browser, pageHTML, width, height) => {
    const page = await _browser.newPage();
    await page.setViewport({ width, height });

    await page.setRequestInterception(true);
    page.once('request', (request) => {
        request.respond({
            body: pageHTML.toString('utf8'),
            contentType: 'text/html; charset=utf-8',
        });
        page.on('request', (_request) => _request.continue());
    });
    return page;
};

{ Error: Protocol error (Fetch.enable): 'Fetch.enable' wasn't found
    at Promise (/var/task/node_modules/puppeteer/lib/Connection.js:183:56)
    at new Promise (<anonymous>)
    at CDPSession.send (/var/task/node_modules/puppeteer/lib/Connection.js:182:12)
    at NetworkManager._updateProtocolRequestInterception (/var/task/node_modules/puppeteer/lib/NetworkManager.js:139:22)
    at NetworkManager.setRequestInterception (/var/task/node_modules/puppeteer/lib/NetworkManager.js:128:16)
    at Page.setRequestInterception (/var/task/node_modules/puppeteer/lib/Page.js:289:48)
    at Page.<anonymous> (/var/task/node_modules/puppeteer/lib/helper.js:112:23)
    at makePage (/var/task/robots/capture.js:29:16)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  message: 'Protocol error (Fetch.enable): \'Fetch.enable\' wasn\'t found' }

interceptors work fine locally for me but when executing under docker I get the protocol error mentioned in the bug.
The referenced doc that closed this bug basically says to use the chromium downloaded in node_modules/puppeteer/.local-chromium/linux-xxxxxx/chrome-linux/chrome
https://github.com/GoogleChrome/puppeteer#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy
However, the alpine docs https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-on-alpine
say to use the distribution chromium.  These instructions cause the exception.
I moved my docker image to use:
https://github.com/GoogleChrome/puppeteer/blob/a582c11b1befb2e0059bcfad7488ff84761c78f5/.ci/node12/Dockerfile.linux
and the problems went away.


Cannot use Preview Webhook URL with Gatsby Refresh Endpoint on Gatsby 3.7.1

Description
According to https://github.com/gatsbyjs/gatsby/issues/10328, setting an env var ENABLE_GATSBY_REFRESH_ENDPOINT=true while running gatsby develop will configure the develop server to re-source data when it receives a POST request to /__refresh.
Based on your documentation on setting up LivePreview in local development, this endpoint needs to be added to the Preview Webhook URL of this Helper.  However, this triggers a Get Request which will 404 on the development server, since Gatsby will only accepts a Post request.
Steps to reproduce

Install Gatsby 3.7.1 and gatsby-source-graphql 3.8.0
Follow all the steps to setup livePreview
Make changes in livePreview and see all of the /__refresh calls produce 404 errors because they are not Post requests

Additional info

Craft version: 3.6.17
PHP version: 7.4
Database driver & version: mariadb:10.3
Plugins & versions: Gatsby Helper 1.0.4

Can you share your Gatsby Helper settings? The updates are definitely leaving Craft as a POST request (https://github.com/craftcms/gatsby-helper/blob/eeca60fbcd2973390ed57539ecd6ce0638081c5b/src/Plugin.php#L233)


Store / save published stream on server

Which version are you using?
v0.14.1
Question
Is there a way to store/ record all publishing streams on server?

Yes, you can use runOnPublish and ffmpeg to do so
paths:
  all:
    runOnPublish: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -c copy -f mpegts $(date +'%s').ts
    runOnPublishRestart: yes


POV: Make test structure more test runner friendly

Currently, the structure of the tests differs from our usual patterns and is not very good for the test runner.
We should investigate, whether we can bring it more into this format: https://github.com/exercism/go-test-runner#subtest-format-specification (This might mean that this causes some duplication which is ok.)
Even if we can't reach that ideal structure, we should make sure that the cases_test.go file only contains the test case slices, not also parts of the test code. Currently, test code being in that helper file leads to issues where the error in the test output is not properly associated with the actual test case that caused it.

I'd be happy to have a go at this.


Decide on final names for plugins

BlockStore might be overly specific. I think something with "Volume" instead of "Block" in the name would make more sense.
Also decide if we want to rename any of the others.

I'm ok with BackupItemAction, RestoreItemAction, and ObjectStore. I'd like to rename BlockStore. Some options:

VolumeSnapshotter
VolumeSnapshotProvider
VolumeStore
VolumeStorage

Any other ideas?


adding Hungarian

Hello everybody,
I'm working with Hungarian etymological data in my research, and came to realise that it would make sense to standardise them first. I first went for a cldf-wordlist, but as it turned out, a dictionary would be more fitting. So now I was wondering: Would there be interest in adding this data set to dictionaria?

As the person who introduced you to dictionaria, I should maybe tell you that Dictionaria has some specific focus: they need glossed examples (IGT to illustrate how words are used for many of the entries), and they only publish original new dictionaries, not resources digitized by others.

Ah, I wasn't aware of that, sorry. I think I can close the issue then.


Add Manish Bhatt to Contributors list

@manishbhatt94, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?


feat: presentations

What

create a new layout template to render slides using revealjs
add revealjs as a dependency

Why

we can publish our own slide decks

Refs

task

Go go go!

 I send you a dm with the ones I can publish.


Fixed docstrings of OptimizationProblemToQubo

Summary
fixed docstrings of OptimizationProblemToQubo to meet its actual implementation

I fixed English as the above suggestion. Could you check it?


Remove CallerIdPolicy

OPS Build status updates of commit 17a924d:
:clock10: Preparing: average preparing time is 1 min(s) 13 sec(s)

OPS Build status updates of commit 17a924d:
:clock10: Incremental building: average incremental building time is 12 min(s) 29 sec(s)

OPS Build status updates of commit 17a924d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Grant-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/New-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Remove-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Set-CsCallerIdPolicy.md
:white_check_mark:Succeeded

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

@kelqi can you provide more information on why you are trying to remove these?

OPS Build status updates of commit a07d92d:
:clock10: Preparing: average preparing time is 1 min(s) 13 sec(s)

OPS Build status updates of commit a07d92d:
:clock10: Incremental building: average incremental building time is 12 min(s) 30 sec(s)

@islubin @tomkau - OK to remove these and merge this?

OPS Build status updates of commit a07d92d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Grant-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/New-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Remove-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Set-CsCallerIdPolicy.md
:white_check_mark:Succeeded

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

@kelqi can you provide more information on why you are trying to remove these?

It's because these were deprecated in favor of CallingLineIdentity.

@kelqi - were these removed from the code though? If not, they will just show up as 'new' cmdlets next time the reflection tool is run. If they are still in code it is better to add to top of description "Deprecated in favor of CallingLineIdentity" or something to that affect. If these were removed from code then it is OK to remove them here too. @islubin or @tomkau - can you provide guidance?

@kelqi - were these removed from the code though? If not, they will just show up as 'new' cmdlets next time the reflection tool is run. If they are still in code it is better to add to top of description "Deprecated in favor of CallingLineIdentity" or something to that affect. If these were removed from code then it is OK to remove them here too. @islubin or @tomkau - can you provide guidance?

@venkat

OPS Build status updates of commit eada18b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Grant-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/New-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Remove-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Set-CsCallerIdPolicy.md
:white_check_mark:Succeeded

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

@kelqi - were these removed from the code though? If not, they will just show up as 'new' cmdlets next time the reflection tool is run. If they are still in code it is better to add to top of description "Deprecated in favor of CallingLineIdentity" or something to that affect. If these were removed from code then it is OK to remove them here too. @islubin or @tomkau - can you provide guidance?

Venkat is working on removing this from the code, but right now it's still there.

OPS Build status updates of commit eada18b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Grant-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/New-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Remove-CsCallerIdPolicy.md
:white_check_mark:Succeeded

skype/skype-ps/skype/Set-CsCallerIdPolicy.md
:white_check_mark:Succeeded

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

This is OK to merge.


include awesome badge

No.

Pull requests with useful links and references about TypeScript are highly welcome and appreciated. Everything else is wasting of time.


"Show posts from my feed" won't stay on

Describe the bug
The "Show posts from my feed" option occasionally turns off on its own. Every once in a while, I'll notice that I'm not seeing posts from other feeds. When I check the settings, it's off. But I never turned it off.
When I fix it, it'll be fine for a week or two, and then it'll turn off again.
To Reproduce
I cannot reproduce it reliably. It just happens every couple weeks.
Expected behavior
It should stay on if I turn it on.
Screenshots

Details

Platform: Web - Windows 11, Chrome
Platform version:
App version: 1.67.0

Would it be helpful to document when notice that it has flipped? I turned it again when I posted this issue 3 days ago. Now it's off again.

Feb 13. It happened again. The setting was definitely on earlier today. Now it's off.
And this happens for the "Threaded Mode" setting too.
I wonder if the problem is with my using other clients, specifically skyfeed and deck.blue?

March 1. It happened either today or yesterday. It was definitely on two days ago.
Both "Show posts from my feed" and "Threaded mode" are off.

I haven't looked at how this currently works, but I have a theory that if we try to do the syncing between clients, then the client whose settings are most recently updated can overwrite the previous settings — and that would overwrite the parts that haven't been synced to it.

Besides the main website, I also use skyfeed (for updating custom feeds) and deck.blue, so maybe jumping between clients plays a role?

Happened again at some point in the last couple days.

@steveharoz Thanks. I've reached out to a few devs with which this might be related. We'll do some work to prevent this from happening too. Thanks for the heads up though!

@steveharoz Hey, just heard word that this should have been fixed in deck.blue. Keep an eye out and see if it happens again, but it should be good. Going to close this for now but (I think) those issues should go to their repo is there's another issue in the future (assuming you're still using deck.blue).
Thanks!

@haileyok Thank you for tracking this weird bug down!


Delete unused tola modules

Purpose
Deletes unused tola module code.
Related ticket: #898

Coverage decreased (-7.5%) to 50.292% when pulling 43f175265b4eddc888a299f884b4aa7aa0e457c5 on Menda:cleanup-tola into 1f0a22a98f8e845a879fef5a351512406ddb2d72 on toladata:dev-v2.


LazyLoad + Swiper not loading cloned/duplicate slides for looping slider/swiper

Howdy, I love this plugin and I've been using it a lot lately. I recently came across a case where I'm using Swiper (https://github.com/nolimits4web/Swiper) in an infinite loop and can't manage to get the cloned slides to load lazily. You'll see (1) initial images load, but (2) cloned images (used to accomplish Swiper's loop parameter only load after you click to advance the slider.
I was hoping someone else has encountered this issue and could shed some light on the best way to ensure all the slides load correctly.
I've setup a fiddle that contains the essential elements of my use case and that displays the problem behavior:
https://jsfiddle.net/silb3r/oxb2ztu5/

Actually this is still an issue on iOS devices. If anyone has some feedback it would be much appreciated!

Turns out that if I add this to Swiper's init param before I update LazyLoad then all is well on Safari:
$(this.$el).find('img').removeAttr('data-was-processed');
See here: https://jsfiddle.net/silb3r/oxb2ztu5/37/ (JS line 18)
Should I be doing that?

Hi @cfxd
which version of lazyload you use on Safari?

10.17.0

Sorry I tried but I couldn’t spot the version used in the fiddle from my mobile (I’m on vacations!).
So version 10.x on Safari immediately loads all images instead of loading them lazily, are you sure you want to keep using that version for all browsers?
The best way to do it would be to do a conditional loading like recommended in the readme.
About the problem you’re having, that you solved removing the data-was-processed attribute, we can discuss later.

About lazy load of images inside a carousel slider like Swiper, Slick and others, since they don’t always actually scroll but the are moved by the sliders using CSS, you should definitely use the API provided by those scripts and avoid using lazyload there.
See how to do it for Swiper here
Thanks

Also, about using the IntersectionObserver polyfill, are you using the polyfill only because of LazyLoad? It would be better to use LazyLoad 8.x in this case, for a number of reasons resulting in better performance.

@cfxd ?

Assuming is solved for not receiving replies.
Feel free to reopen.

Thank you @cfxd!

By the way @cfxd, since LazyLoad v. 10.x and v. 8.x share the same API, and v. 10 is much better for performance, you should seriously think about conditionally loading v. 8 or v. 10 depending on the browser support of IntersectionObserver.
Find how to do this in the docs (README.md file).

Yes I've been looking into that. Not sure it will be easy with my current gulp config but I'll see what I can come up with.

I am using swiper js with lazy loading and loop.
Last clonned slide does not change its data-src to src even when it is in view. Can you please suggest

@VineetKumarKushwaha I think the solution to this issue has been found already. Please read the discussion, particularly the latest 5-6 comments.


Add optional style to column

The allows inline react styles to be applied to all td elements in the column.

This is similar to #12, but with less code change. I'm currently using this change to keep style definitions close to the tables.

FYI it looks like this repo is not maintained anymore so I've forked this project as easy-json-table and plan on keeping it well maintained. You may wish to look at the contribution protocol and send a PR here: https://github.com/gazhayes/easy-json-table


scrollbar styling issues

Yanel on a mac running chrome gets this:

I get a lighter scrollbar on categories as opposed to the scrollbar far right:

They should ideally be the dark style like the scrollbar on the far right of the page

Not certain if this is still an issue, removing from epic so it can be closed, scheduling w/ proper labels.


Remove #[derive(Debug)]

Followup issue for https://github.com/ChunMinChang/cubeb-coreaudio-rs/pull/55#discussion_r395089676
The reason is smiliar to https://github.com/servo/servo/pull/19756

It seems this causes trouble since other related crates still requires Debug trait.
#75 reverts the changes for now.


Ucx+data handling

@mrocklin
https://github.com/TomAugspurger/distributed/pull/2/commits/8bc2dbb9ae495bc231d3d572ecdd89f7bb2c67ea implements your suggestion of included a couple header frames with descriptions of what's coming. I was able to remove all the peeking / deserialization code.
Do you have thoughts on whether it looks cleaner? It puts a bit tighter restriction on the "protocol" we're using to communication. Now the pattern is

message with the number of frames
message with whether each frame is a GPU frame
message with whether each frame is a sized frame
messages with all the "real" frames.

I may look into re-using distributed.utils.nbytes. I worry that the fallback of sys.getsizeof(frame) is not appropriate for this use case. We would rather fall back to recv_future if we aren't sure of the object's size.

I don't understand what a sized frame is.  We should know the size in bytes of every bytes-like object that we're sending through.  For Python objects like Pandas dataframes or cupy arrays there may be some ambiguity yes, but at the comms level we should be past all of that, and only hold onto bytes-like objects, for which I would expect the number of bytes of that object is very clear.  Is this not the case?

Hmm, that may be the case. Let me try it out on some workloads.


Can't open Camunda Modeler from VSCode plugins

Describe the Bug
When trying to open a BPMN or DMN file from VSCode in Camunda Modeler none of the existing plugins to open a file in the system's default application seem to work. Typora seems to have a similar problem, where one can see the application being started if it's not yet running and then seems to get killed again.
This is particularly problematic because drag & drop also does not work as reported in #2299.
Environment

OS: Ubuntu 20.04.2 LTS using KDE
Camunda Modeler Version: 1.10.0-nightly.20210721
Execution Platform: Camunda Cloud
Installed plug-ins: Generate Technical IDs, BPMN Lint, Cloud Sync, TX Boundaries, Property Info, Camunda Cloud Model Migration

I submitted a plugin similar to Open in Typora as a project idea for this year's Summer Hackdays.

Thanks for reporting!

Works as expected on Windows. I used the 'open' plugin by sandcastle to test this.


🌐 feat: add Tamil i18n

This PR adds Tamil translation for the available strings.

Thanks for the project, I like the overall ease of use and experience (planning to port my website to your project soon).

Thanks for this translation, @kbdharun! I'm happy to merge this in.


Add logging example and some readme fix ups

Just getting my feet wet, so some typo fixes and a logging env example.

Thanks for fixing the typo. :+1:

Thanks @lukehinds, this looks good!  Don't worry about the Travis failure; rustfmt seems to have changed under us.  Will merge shortly.

Thanks @leonjia0112 , so the lint errors have crossed over from the master branch.
I can fix these by just running with --check, may as well do this in this branch and we can look at the diffs.

Hah, that works too :)

Sorry @frozencemetery missed your previous comment somehow (comment race condition!). All looks good now.


Code 2406 skill id invalid

How to solve:
TuyaOpenAPI response: {"code":2406,"msg":"skill id invalid","success":false,"t":1622204992541} path = /v1.0/iot-01/associated-users/actions/authorized-login
(node:28565) UnhandledPromiseRejectionWarning: TypeError: Cannot destructure property 'access_token' of 'res.result' as it is undefined.
at TuyaSHOpenAPI._refreshAccessTokenIfNeed (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:45:10)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at TuyaSHOpenAPI.request (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:128:5)
at TuyaSHOpenAPI.getDevices (/usr/local/lib/node_modules/homebridge-tuya-platform/lib/tuyashopenapi.js:58:15)
at TuyaPlatform.initTuyaSDK (/usr/local/lib/node_modules/homebridge-tuya-platform/index.js:76:17)
(Use node --trace-warnings ... to show where the warning was created)
(node:28565) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:28565) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
using:
tuyaSmart
europe

@jackwburger Sorry for the bad experience, the server problem has been fixed, please try again

@Hanh94 same here. I'm trying to contribute but I couldn't use my account now after the recent update. Getting "skill is invalid" error -- although this error is now the same with the API explorer when I tried. Could be a timezone issue? I'm in Asia/Manila and using America as the data center.
Please advise. thanks

Hi，@lodev09  Your cloud project on the Tuya IoT Platform was created after May 25, 2021.  For more information, Please see Tuya IoT Platform Configuration Guide Using Smart Home PaaS.

@Hanh94 hmmm, I'm not sure if that's the right documentation. First, that project was created weeks ago already -- I just modified it to match the instructions given to link to homebridge. 2nd, there's no way to delete an existing home paas project and I couldn't create new one as well.

Hi @lodev09 , as the new update for Tuya Homebridge plugin only works for new projects created after 25th May, 2021. If your project is created weeks ago, then please recreate a new cloud project of "Smart Home PaaS" type by following the documentation above. If you have exceeded the limit of creating cloud project for free account (Only two projects), please create a new Tuya IoT Platform account and create the cloud project again. Hope this helps!

Yeah I guess I can do that. Anyway, is there a way you can change the country of my other account? I wanted to use an official email of mine for my integration. The email
Is<EMAIL_ADDRESS>I can't find a way to change the region.

Hi @lodev09 , You can make this request through the tickets

@jackwburger Sorry for the bad experience, the server problem has been fixed, please try again

@Hanh94 I tried again but still the same problem. I created the cloud project a couple of months ago so it seems I need to recreate one. Unfortunately the old project cannot be deleted (Why does it take so long to implement this feature?). Now I need to create a new account which is rather dump. Anyway thanks for the help.

I ended up creating my own plugin lol
https://github.com/lodev09/homebridge-tuya-smarthome

Hi @lodev09, We already support Lightbulb Dynamic dp

Hi @lodev09 , as the new update for Tuya Homebridge plugin only works for new projects created after 25th May, 2021. If your project is created weeks ago, then please recreate a new cloud project of "Smart Home PaaS" type by following the documentation above. If you have exceeded the limit of creating cloud project for free account (Only two projects), please create a new Tuya IoT Platform account and create the cloud project again. Hope this helps!

This seems like the most difficult possible way to do things. Is there no other way?

Hi @codyc1515 sorry for the inconvenience, please create a Tuya technical support ticket , we will assistant you to resolve the issue.

@zlinoliver can't I delete my existing project? Or my current account? This way I'd have two accounts.

Hi guys, Since we haven't received your reply for a long time, we think our latest version should have solved your problem. We will close this issue first. If there is any problem, you can contact us at any time.


More details on 'Crashing pod' Slack message

I have amount of containers inside the pod, and when the pod crashed I want to see in the Slack message which container exactly caused it. For example, my workflow is to launch some init containers before the pod starts (fetch secrets, internal dependencies, flyway), and for now I get the same message 'Crashing pod  in namespace ', and I need to describe the pod to understand which container failed. I want to look ah the message and immediately know - ah, it's flyway problem, no panic.

Hi @shfisher ,
We display the container name in the message body.
Would adding it to the description as well help? (This way you can see it when hovering on the timeline in the UI)

I actually think it might be useful for others as well, so I'm going to add it anyway

@arikalon1 I think you have already done it ? can you close this?

@RoiGlinik yes, closing


repair compile error

repair compile error

Codecov Report

Merging #2575 into 1.2.x will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##            1.2.x    #2575      +/-   ##
==========================================
+ Coverage   75.32%   75.35%   +0.03%
==========================================
  Files         193      193
  Lines        6043     6043
  Branches      760      760
==========================================
+ Hits         4552     4554       +2
+ Misses       1164     1162       -2
  Partials      327      327

Impacted Files
Coverage Δ

...d/netflix/eureka/server/EurekaServerBootstrap.java
55.38% <100%> (ø)
:arrow_up:

...a/server/EurekaServerInitializerConfiguration.java
79.31% <0%> (+6.89%)
:arrow_up:

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 3f1b372...25941b3. Read the comment docs.