MIME encoded syntax (=?UTF-8?Q??=) shown in subject

I just recently got

Original subject line Subject: =?UTF-8?Q??=  =?UTF-8?Q?=D0=9F=D0=BE=D0=B4=D1=82=D0=B2=D0=B5=D1=80=D0=B6=D0=B4=D0=B5=D0=BD=D0=B8=D0=B5=20?=  =?UTF-8?Q?=D1=80=D0=B5=D0=B3=D0=B8=D1=81=D1=82=D1=80=D0=B0=D1=86=D0=B8=D0=B8=20?=  =?UTF-8?Q?=20=D0=BD=D0=B0=20Bookland.com?=
you can see that the encoded text part of the first encoded-word-thingy is empty, maybe that's an issue.

=?UTF-8?Q??= is not a valid encoded word and hence not decoded. See RFC 2047, section 2.
I'm hesitant to add support for this particular case. It doesn't feel like something that happens when 'encoded word' encoding is implemented naively. This seems like a more serious bug that should be fixed rather than worked around.
That being said, both Thunderbird and Gmail's web interface don't show =?UTF-8?Q??= for the provided subject. Thunderbird does display =?UTF-8?Q??= when it's the sole value of the Subject header, it doesn't if that part is followed by anything else (encoded word or regular text). Gmail always ignores it.

Similar thing in the To:  field:

To: =?utf-8?Q??=<EMAIL_ADDRESS>


External contract

We have really nice hooks (on top of wagmi's) for interacting with contracts deployed from SE-2 (leveraging on the hardhat_contracts.ts file).
Let's find the best way to do something similar with external contracts. E.g.  SE1 use a external_contracts.js file.
Ideally, as a builder, I'd like to use it the same way we use our custom hooks (same autocomplete / types magic).
  const { writeAsync } = useScaffoldContractWrite({
    contractName: "DaiContract",
    functionName: "transfer",
    args: [address, amount],
  });

I guess we could do that right now if we make the builder paste (in the right format) the contract info in hardhats_contracts.ts. But that's not very friendly.
So maybe a external_contracts.ts with a more clear format? Using wagmi's cli?
Check out this comment from @technophile-04 https://github.com/scaffold-eth/se-2/pull/200#issuecomment-1485414504.

the hook should accepts the ABI and address of the contract right?

I have made some progress on this (https://github.com/sverps/se-2/tree/feature/271-external-contracts) before my holidays. I'll see if I can find some time to pick this up again.


Still Uses Phong Shading and Not GGX

It appears that the lighting model in the shaders is based off of the phong lighting that Unity had at the time The Lab Renderer was created. Unity now has the more physically correct GGX lighting which is crucial when working with PBR in things like Substance Painter, as a lack of consistency makes it impossible to make things look right. Is there any way to use GGX with this renderer?

That's intentional, Phong shading is much cheaper than GGX. GGX would not be optimal for VR. However it wouldn't take much to switch from Phong to GGXto test for your self. As for consistency issues, they should be fairly minimal as this is still a pbr based renderer.

I know it was intentional, especially since that's what Unity used at the time, but the consistency issues are too much unless the assets are designed specifically for it. I've been trying to switch from Phong to GGX, but still haven't been able to find exactly where in the code to do that. It seems that the functions that affect the lighting are quite spread out.


Task: Enable responsive sizing_modes

Currently setting layout.responsive=True will result in the plot being responsively sized on initial load. However resizing the JLab Panel (either by dragging the edge or moving the panel) doesn't cause the plot to resize. Presumably the window size change events aren't being triggered by the panels natively.

tested with 1.2 and scale_wdth, seems to work fine now


geom_density: The "..count.." variable is not computed correctly

import numpy as np
from lets_plot import *

dat = dict(
    xs = np.random.normal(0, 10, 1000)
)

(ggplot(dat, aes(x="xs", y="..count..")) +
 geom_histogram(bins=10) +
 geom_density(n=10, color="red")).show()

The density "count" estimate is not even close to what the histogram is showing.
At the same time the "..density.." variable seem computed correctly.

What about to remove bins parameter from geom_histogram() and add stat='bin' into geom_density()? Now it is different statistics as I understand.

Yes, it seems the "..count.." computed by density stat is fine.
What I need is to adjust these values to match the histogram values. (see https://stackoverflow.com/questions/37404002/geom-density-to-match-geom-histogram-binwitdh)


For typescript, "dom" has to be added to your tsconfig.json under "compilerOptions.lib", but this isn't mentioned anywhere in the docs

Describe the bug
The dom lib is necessary for the Request type in the default context to be evaluated correctly. Request is part of the Fetch API, which is not something that node projects will have by default.
Add this enabled my project to resolve Request under YogaInitialContext:
{
   "compilerOptions": {
      "lib": [
         "dom"
      ],
   }
}

Your Example Website or App
n/a
Steps to Reproduce the Bug or Issue

Use Yoga in any TypeScript application where "dom" is not a lib under tsconfig

Expected behavior
I should expect this dependency mentioned somewhere. If it is, I missed it.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
NodeJS: [e.g. 18.1.0]
@graphql-yoga/* version(s): [e.g. 2.5.1]

Additional context
No response

It's been fixed in the Fetch ponyfill we are using. So it should be fixed. If it still continues, please share a reproduction on CodeSandbox or StackBlitz.
Thanks for reporting the issue.


Create Amazon test

Description

Created different tests for amazon scraper

Resolves: 888
Checklist

Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?
[ ] Have you updated the 'documentation.md' file with the method/function documentation?
[ ] Have you sent a message along with the result or response?
[ ] Have you used the try-catch technique?
[ ] Has the method/class been added to the documentation (md file)?

Screenshots

Uploading a screenshot illustrating the approach you developed for validation is required.

Additional Notes/Comments

I have created amazon_test.py file but the code of amazon.py sometimes gives 503 error due to which the tests are failing.
The Tests themselves are correct.

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.
I appreciate your contribution.

@nikhil25803 Please review PR

Great work @TrijoySinha  !!
Do not forget to

Share your contribution on socials and tag Clueless 🫂
Give this repository a star ✨
Follow Clueless Community on GitHub ✅


ProgressBar::WithProgress use #size when available

Since #count iterates the enumerable, it can be quite slow. #size is not always available but when it is, it can be much faster than #count.
For some large enumerables I work with, iterating the whole thing takes minutes, so doing it once for count and once for the actual iteration is terribly slow. These use an Enumerator with a block specifying size, and that is computed in relatively insignificant time, so using than when it is available is much better.

I think this used count over size originally because when it was written, ActiveRecord::Relation#size would load the entire query, but #count would execute the COUNT SQL query. It doesn't look like that's the case any more: ActiveRecord::Relation#size
Is there any reason to use #count at all? Should it just be switched it #size in every case?

#size is not always defined - the Enumerable module defines #count but not #size; most classes that include Enumerable do define #size, but not all. And the Enumerator class does define #size but it returns nil unless the Enumerator is initialized with a block indicating the size.


[R] Add binding to stringr::str_replace_na()

Describe the enhancement requested
It's just coalesce(), right?
cc @thisisnic
Component(s)
R

That function doesn't do what either of us thinks it does 😅
Apparently replaces NA with "NA"
https://stringr.tidyverse.org/reference/str_replace_na.html

Looks like you have to check that replacement is a scalar string but then coalesce() does the job.
arrow_table(x = c("a", NA, NA, NA, "b")) |>
  mutate(x = coalesce(x, "Missing data")) |>
  collect()

# A tibble: 5 × 1
  x
  <chr>
1 a
2 Missing data
3 Missing data
4 Missing data
5 b


Fieldsets + Relationships

When making a request to the following endpoint - GET /users?fields[users]=title,first_name,last_name&fields[organisations]=name&include=organisations
This is the outcome of the serialisation, there is no relationships object on the user data to link it to the organisation.
{
  "data": [
    {
      "type": "users",
      "id": "20c48f50-97b3-4712-9b0c-f5436c6185b5",
      "attributes": {
        "title": "Mr",
        "first_name": "New",
        "last_name": "User"
      },
      "links": {
        "self": "http://localhost/users/20c48f50-97b3-4712-9b0c-f5436c6185b5"
      }
    },
    {
      "type": "users",
      "id": "e0c473f1-82b1-449a-80a1-5800ada52a93",
      "attributes": {
        "title": "Mr",
        "first_name": "Test",
        "last_name": "Test"
      },
      "links": {
        "self": "http://localhost/users/e0c473f1-82b1-449a-80a1-5800ada52a93"
      }
    },
    {
      "type": "users",
      "id": "dbc9a064-bb59-4e33-8181-d6949100c0e2",
      "attributes": {
        "title": "Mr",
        "first_name": "Broker",
        "last_name": "Broker"
      },
      "links": {
        "self": "http://localhost/users/dbc9a064-bb59-4e33-8181-d6949100c0e2"
      }
    }
  ],
  "included": [
    {
      "type": "organisations",
      "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638",
      "attributes": {
        "name": "Test Underwriter"
      }
    },
    {
      "type": "organisations",
      "id": "7e3d5395-c433-4c0d-bc8a-1da8dad1b6d7",
      "attributes": {
        "name": "Test Broker"
      }
    }
  ]
}

Ff we don't include the fieldset parameters, the following is the outcome:
{
  "data": [
    {
      "type": "users",
      "id": "20c48f50-97b3-4712-9b0c-f5436c6185b5",
      "attributes": {
        "title": "Mr",
        "first_name": "New",
        "last_name": "User",
        "username": "NewUser",
        "name": "Mr New User",
        "email"<EMAIL_ADDRESS>        "phone1": "1234567890",
        "phone2": null,
        "position": null,
        "address": {
          "line1": "",
          "line2": "",
          "line3": "",
          "postal_town": "",
          "county": "",
          "postcode": "",
          "country": ""
        },
        "address_string": ".",
        "status": "pending",
        "created_at": "2016-04-29T10:59:37+0000",
        "updated_at": "2016-04-29T10:59:37+0000"
      },
      "relationships": {
        "organisation": {
          "data": {
            "type": "organisations",
            "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638"
          }
        }
      },
      "links": {
        "self": "http://localhost/users/20c48f50-97b3-4712-9b0c-f5436c6185b5"
      }
    },
    {
      "type": "users",
      "id": "e0c473f1-82b1-449a-80a1-5800ada52a93",
      "attributes": {
        "title": "Mr",
        "first_name": "Test",
        "last_name": "Test",
        "username": "test",
        "name": "Mr Test Test",
        "email"<EMAIL_ADDRESS>        "phone1": "09762522699",
        "phone2": "(437)079-3236",
        "position": null,
        "address": {
          "line1": "Line 1",
          "line2": "Line 2",
          "line3": "",
          "postal_town": "Town",
          "county": "County",
          "postcode": "Postal Code",
          "country": "United Kingdom"
        },
        "status": "active",
        "created_at": "2016-04-24T15:34:19+0000",
        "updated_at": "2016-04-24T15:34:19+0000"
      },
      "relationships": {
        "organisation": {
          "data": {
            "type": "organisations",
            "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638"
          }
        }
      },
      "links": {
        "self": "http://localhost/users/e0c473f1-82b1-449a-80a1-5800ada52a93"
      }
    },
    {
      "type": "users",
      "id": "dbc9a064-bb59-4e33-8181-d6949100c0e2",
      "attributes": {
        "title": "Mr",
        "first_name": "Broker",
        "last_name": "Broker",
        "username": "broker",
        "name": "Mr Broker Broker",
        "email"<EMAIL_ADDRESS>        "phone1": "409-267-7733x8233",
        "phone2": "(247)919-6106x2426",
        "position": null,
        "address": {
          "line1": "Line 1",
          "line2": "Line 2",
          "line3": "",
          "postal_town": "Town",
          "county": "County",
          "postcode": "Postal Code",
          "country": "United Kingdom"
        },
        "status": "active",
        "created_at": "2016-04-24T15:34:19+0000",
        "updated_at": "2016-04-24T15:34:19+0000"
      },
      "relationships": {
        "organisation": {
          "data": {
            "type": "organisations",
            "id": "7e3d5395-c433-4c0d-bc8a-1da8dad1b6d7"
          }
        }
      },
      "links": {
        "self": "http://localhost/users/dbc9a064-bb59-4e33-8181-d6949100c0e2"
      }
    }
  ],
  "included": [
    {
      "type": "organisations",
      "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638",
      "attributes": {
        "name": "Test Underwriter",
        "created_at": "2016-04-24T15:34:19+0000",
        "updated_at": "2016-04-24T15:34:19+0000"
      }
    },
    {
      "type": "organisations",
      "id": "7e3d5395-c433-4c0d-bc8a-1da8dad1b6d7",
      "attributes": {
        "name": "Test Broker",
        "created_at": "2016-04-24T15:34:19+0000",
        "updated_at": "2016-04-24T15:34:19+0000"
      }
    }
  ]
}

Should the relationships object and on the resource be hidden when a fieldset is requested?
I know the package hides relationships if they aren't specified in the fieldset, but is desired behaviour? What if you want to have the entire fieldset for a relationship but filter the "primary" resource.

Should the relationships object and on the resource be hidden when a fieldset is requested? I know the package hides relationships if they aren't specified in the fieldset, but is desired behaviour?

I tend to think that in such cases lib should not try to outsmart the developer. I he/she says 'I want to filter some fields but receive included data' let it be so.

What if you want to have the entire fieldset for a relationship but filter the "primary" resource.

That's what you got in your example. You filtered 'primary' resource and got entire field set for relationship.

I'm closing the question. Don't hesitate to contact if you have any further questions.

@neomerx Actually I specified the filtered name on the organisation. I suppose I should have demo'd the fact that if you include a relationship but don't filter it, it returns nothing.

Aha
So if you GET /users?fields[users]=title,first_name,last_name&include=organisations it won't include organization, will it? If so the following request might be helpful GET /users?fields[users]=title,first_name,last_name&fields[organisations]=&include=organisations though it doesn't look consistent to me. If I understand you correctly we should define 'proper' behavior for the lib, write the test and update the code base.

@neomerx I apologise, see my edit, I tried it again after I posted that comment, but it returned, I must have had something wrong when I saw it initially.
What I was trying to communicate is that the relationships object is missing from the users resource making it impossible to determine the how the relationship is linked.

'full linkage' requirement was cancelled. So it's not necessary to have all links in the document now.

So how do I work out what organisation these users belong to?
{
  "data": [
    {
      "type": "users",
      "id": "20c48f50-97b3-4712-9b0c-f5436c6185b5",
      "attributes": {
        "title": "Mr",
        "first_name": "New",
        "last_name": "User"
      },
      "links": {
        "self": "http://localhost/users/20c48f50-97b3-4712-9b0c-f5436c6185b5"
      }
    },
    {
      "type": "users",
      "id": "e0c473f1-82b1-449a-80a1-5800ada52a93",
      "attributes": {
        "title": "Mr",
        "first_name": "Test",
        "last_name": "Test"
      },
      "links": {
        "self": "http://localhost/users/e0c473f1-82b1-449a-80a1-5800ada52a93"
      }
    },
    {
      "type": "users",
      "id": "dbc9a064-bb59-4e33-8181-d6949100c0e2",
      "attributes": {
        "title": "Mr",
        "first_name": "Broker",
        "last_name": "Broker"
      },
      "links": {
        "self": "http://localhost/users/dbc9a064-bb59-4e33-8181-d6949100c0e2"
      }
    }
  ],
  "included": [
    {
      "type": "organisations",
      "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638",
      "attributes": {
        "name": "Test Underwriter"
      }
    },
    {
      "type": "organisations",
      "id": "7e3d5395-c433-4c0d-bc8a-1da8dad1b6d7",
      "attributes": {
        "name": "Test Broker"
      }
    }
  ]
}

if you filter out such link it's assumed you already know it somehow.
Can you please post what you get for
GET /users?fields[users]=title,first_name,last_name&fields[organisations]=&include=organisations

and
GET /users?fields[users]=title,first_name,last_name&include=organisations

  "data": [
    {
      "type": "users",
      "id": "20c48f50-97b3-4712-9b0c-f5436c6185b5",
      "attributes": {
        "title": "Mr",
        "first_name": "New",
        "last_name": "User"
      },
      "links": {
        "self": "http://api.alpha.soc/users/20c48f50-97b3-4712-9b0c-f5436c6185b5"
      }
    },
    {
      "type": "users",
      "id": "e0c473f1-82b1-449a-80a1-5800ada52a93",
      "attributes": {
        "title": "Mr",
        "first_name": "Test",
        "last_name": "Test"
      },
      "links": {
        "self": "http://api.alpha.soc/users/e0c473f1-82b1-449a-80a1-5800ada52a93"
      }
    },
    {
      "type": "users",
      "id": "dbc9a064-bb59-4e33-8181-d6949100c0e2",
      "attributes": {
        "title": "Mr",
        "first_name": "Broker",
        "last_name": "Broker"
      },
      "links": {
        "self": "http://api.alpha.soc/users/dbc9a064-bb59-4e33-8181-d6949100c0e2"
      }
    }
  ]
}```

{
"data": [
{
"type": "users",
"id": "20c48f50-97b3-4712-9b0c-f5436c6185b5",
"attributes": {
"title": "Mr",
"first_name": "New",
"last_name": "User"
},
"links": {
"self": "http://localhost/users/20c48f50-97b3-4712-9b0c-f5436c6185b5"
}
},
{
"type": "users",
"id": "e0c473f1-82b1-449a-80a1-5800ada52a93",
"attributes": {
"title": "Mr",
"first_name": "Test",
"last_name": "Test"
},
"links": {
"self": "http://localhost/users/e0c473f1-82b1-449a-80a1-5800ada52a93"
}
},
{
"type": "users",
"id": "dbc9a064-bb59-4e33-8181-d6949100c0e2",
"attributes": {
"title": "Mr",
"first_name": "Broker",
"last_name": "Broker"
},
"links": {
"self": "http://localhost/users/dbc9a064-bb59-4e33-8181-d6949100c0e2"
}
}
],
"included": [
{
"type": "organisations",
"id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638",
"attributes": {
"name": "Test Underwriter",
"created_at": "2016-04-24T15:34:19+0000",
"updated_at": "2016-04-24T15:34:19+0000"
}
},
{
"type": "organisations",
"id": "7e3d5395-c433-4c0d-bc8a-1da8dad1b6d7",
"attributes": {
"name": "Test Broker",
"created_at": "2016-04-24T15:34:19+0000",
"updated_at": "2016-04-24T15:34:19+0000"
}
}
]
}

This is the object I'm talking about that is missing, not the `links`:

  "relationships": {
    "organisation": {
      "data": {
        "type": "organisations",
        "id": "7ebb2b15-bafb-4d98-83b2-e8600fbfe638"
      }
    }
  },

When you filter `users` it removes the `relationships` resource, when you **only** filter `organisations` it is still present.

I apologise for my poor wording here.

I understand you say 'look I set filter for users (no organisation relationship) but request organisation to be included'. And it does what you request: only attributes for user and organisation included. And you say 'but there is no relationship between them in response!'. Yes, that's right. So called 'full linkage' is not necessary now by spec

... compound documents require full linkage (except when relationship linkage is excluded by sparse fieldsets) ...

Do you want relationship to be included? Try this request
GET /users?fields[users]=title,first_name,last_name,organisation&fields[organisations]=name&include=organisations

Note organisation field was added

@neomerx Huh, I never realised the term fields also applied to the relationship keys.
Thanks for clarifying that.

field = attribute || relationship spec

A resource object’s attributes and its relationships are collectively called its “fields”.

Yeah, after reading that part of the spec now it's obvious.


Guidance on adding private CA certificates?

Corporate users may require a private CA certificate to be installed in the final container. ko doesn't have some kind of native approach to passing in a private CA certificate as a parameter.
I believe the correct approach here is to use a base image which has the private CA certificate baked-in, but then there's a bootstrapping issue requiring another method (e.g. with a Dockerfile) to build the new base image with the private CA certificate.
I'd appreciate guidance / documentation on strategies to approach this; if I need to use a Dockerfile to bundle in the private CA certificate then I'm not sure what additional value ko is bringing to this use-case.

My recommendation would be to either bake the certs into the base image as you suggest, or possibly use a tool like https://github.com/dlorenc/incert to append a layer before or after ko to add the corp certs.
Hope this helps

Even if the base image is built with a dockerfile, IMO ko still adds value since each app on top of it doesn't need to use docker to build, and can be faster and more secure as a result.
One team can periodically build the base with custom certs once, and dozens of app teams can independently build on that base without having to care about certs or docker.

Nice, I wasn't aware of incert.
I guess we can close this, unless someone wants to add this to the docs website.


haskell: add the linkWithGold function to link packages with ld.gold

This was inspired by https://www.reddit.com/r/haskell/comments/63shj7/link_with_the_gold_linker_for_faster_build_times/.

@peti it would be interesting turning on linkWithGold by default (for GHC >= 7.8) and let hydra build the package set and see how much will break. I would expect that we need to add a few --ghc-option=-optl-lm here and there.

I would expect that we need to add a few --ghc-option=-optl-lm here and there.

@basvandijk I think those -lms should then be integrated into the upstream cabal packages, as that is the clean way to do it.

@nh2 agreed.
I forced-pushed a commit to this PR that adds a reference to a PR for double-conversion to explicitly link with libm.

BTW I initially used the following implementation but abandoned it because the current implementation is simpler and doesn't require rebuilding all Haskell packages. But it might be interesting to compare the two...

@nh2 it would be great to also have your linkWithLLD available. Are you working on a PR for that BTW?

it would be great to also have your linkWithLLD available. Are you working on a PR for that BTW?

@basvandijk do you mean to add this example as a nixpkgs package?

@nh2 no, I mean I would like to have a function like my linkWithGold but then for linking with lld. It could be called linkWithLLD and work something like:
linkWithLLD = drv : appendConfigureFlag drv
    "--with-gcc=clang --with-ld=clang";

What is probably missing is that clang should be brought in scope.

@basvandijk Yes; and pkgs.lld would also be needed, and flags to build to pass ld-option, cc-option, ghc-option etc.
I'm not currently working on that, so if you'd like to do it please go ahead, it would be awesome!
Also, if you come across a problem involving linking functions from libstc++, ping me.

Ok this sounds like a nice weekend project. I'll see if I have some time for it. Thanks for the info!

Great! Any thoughts on making it the default where possible? We pass --split-sections by default for GHC > 8.0.1, which apparently requires the gold linker to take effect and thus I assume doesn't do anything currently.

@basvandijk I found that Haskell executables built with lld in nix that also link -l system shared libraries don't link correctly, with entries in lld in resulting executbles being not found (rpaths are missing). That's because ld and gold have wrappers that do the following:
https://github.com/NixOS/nixpkgs/blob/593b46fd1dcbbd0e963e9aee13d738ae6bdb3d08/pkgs/build-support/cc-wrapper/ld-wrapper.sh#L133
 # First, find all -L... switches.

    # Second, for each directory in the library search path (-L...),
    # see if it contains a dynamic library used by a -l... flag.  If
    # so, add the directory to the rpath.

lld currently doesn't have such a wrapper.

Also this type of patch or setting to --enable-new-dtags will likely be needed.

@aristidb thanks for the merge. Could this also be cherry-picked on release-17.03? I would like to use this in production.

I've created a separate issue https://github.com/NixOS/nixpkgs/issues/24744 for the problem that lld doesn't work correctly with nix.

I wonder if linkWithGold should also pass --ghc-option=-optl-lm to the package it's compiling. Maybe also `-pthread.

I wonder if linkWithGold should also pass --ghc-option=-optl-lm to the package it's compiling. Maybe also --ghc-option=-optl-pthread.

@domenkozar Personally I think it shouldn't, unless it's a temporary hack. It should be fixed upstream, as ld happily accepts these flags and that's better than implicitly linking those anyway.

Every package that uses Prelude.sqrt would need that flag added to cabal file. That sounds unfeasible to me :)

Every package that uses Prelude.sqrt would need that flag added to cabal file.

@domenkozar With "upstream" I mean the package that declares the function, not the one that uses it (that would be infeasible, users shouldn't have to rely on the implementation detail with what C function a Haskell function is implemented).
So in that case I think base should have that extra-libraries: m.
Do you think this will make any problem?

If we can get base fixed, I'm all for it.

There's a bug when you depend on a library that is linked with gold: https://ghc.haskell.org/trac/ghc/ticket/13810#comment:3

I would expect that we need to add a few --ghc-option=-optl-lm here and there.

@basvandijk I think those -lms should then be integrated into the upstream cabal packages, as that is the clean way to do it.

I have now confirmed that --ghc-option=-optl-lm should not be used.
It wil pass it also to those linker invocations that create the individual Haskell module .o files, which will then fail with e.g.
/nix/store/iz98xp5p48jayn034wq89y30plpx5xns-binutils-2.27/bin/ld.gold: fatal error: cannot mix -r with dynamic object /nix/store/7crrmih8c52r8fbnqb933dxrsp44md93-glibc-2.25/lib/libm.so.6

in some cases.
Putting extra-libraries: m into the executable section of the .cabal file is the only working solution (or more precisely, any library that uses functions from libm, but note that is hard to determine because nothing in the toolchain will complain when you forget it on a library that uses function from libm, so you'll only get missing symbols at the link of the final executable).

Anyone remembers why we didn't enable gold by default?

@domenkozar No, I don't know.

@domenkozar, @nh2: I think #80466 is the missing piece for gold as the default linker.


Separate etherlime into two packages; add lerna configs; configure tests

Codecov Report

Merging #214 into master will decrease coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #214      +/-   ##
==========================================
- Coverage   98.55%   98.48%   -0.07%
==========================================
  Files          73       74       +1
  Lines        2901     2902       +1
==========================================
- Hits         2859     2858       -1
- Misses         42       44       +2

Impacted Files
Coverage Δ

packages/etherlime-utils/utils/signer-utils.js
100% <ø> (ø)

.../etherlime/cli-commands/zk-proof/generate-proof.js
100% <ø> (ø)

...etherlime-utils/utils/global-exception-handling.js
100% <ø> (ø)

packages/etherlime/cli-commands/shape/urlConfig.js
100% <ø> (ø)

...ckages/etherlime/cli-commands/flattener/flatten.js
100% <ø> (ø)

...me/cli-commands/compiler/etherlime-resolver/npm.js
100% <ø> (ø)

packages/etherlime/cli-commands/shape/shape.js
100% <ø> (ø)

...erlime/cli-commands/etherlime-test/evm-commands.js
100% <ø> (ø)

...ckages/etherlime/logs-store/blocking-json-store.js
100% <ø> (ø)

...lime/cli-commands/etherlime-test/etherlime-test.js
100% <ø> (ø)

... and 66 more

Continue to review full report at Codecov.

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


clusterctl

/kind feature
Describe the solution you'd like
clusterctl does not work. This is logged to trace issues for clusterctl

it works now after #72 merged


easy way to customize the diagnostic severity of all lint rules

i originally raised https://github.com/Dart-Code/Dart-Code/issues/5058, @DanTup suggested that i raise it here instead:

Is your feature request related to a problem? Please describe. i have my CI set up to fail on all analyzer diagnostics, but many of them are displayed in vscode as "information":

"information" implies that it's not a problem, but since the CI will fail if this code is committed, i want it to show as a warning or an error.
also, information diagnostics do not show up on the file name, but warnings and errors do:

Describe the solution you'd like an option to change the severity of diagnostics

as discussed there, the solution ended up being to duplicate the list of rules i have enabled in my project, like so:
analysis_options.yaml
linter:
  rules:
    prefer_single_quotes: true
    avoid_unused_constructor_parameters: true
    avoid_dynamic_calls: true
    avoid_annotating_with_dynamic: false
    literal_only_boolean_expressions: true
    prefer_final_locals: true
    prefer_final_parameters: true
    prefer_foreach: true
    prefer_if_elements_to_conditional_expressions: true
    prefer_interpolation_to_compose_strings: true
    prefer_mixin: true
    public_member_api_docs: false
    require_trailing_commas: true
    sized_box_shrink_expand: true
    sort_child_properties_last: true
    sort_constructors_first: false
    sort_unnamed_constructors_first: true
    tighten_type_of_initializing_formals: true
    unawaited_futures: true
    unnecessary_await_in_return: true
    unnecessary_constructor_name: true
    unnecessary_lambdas: true
    unnecessary_late: true
    unnecessary_null_aware_assignments: true
    unnecessary_null_checks: true
    unnecessary_nullable_for_final_variable_declarations: true
    unnecessary_parenthesis: true
    unnecessary_raw_strings: true
    use_colored_box: true
    use_decorated_box: true
    use_enums: true
    use_if_null_to_convert_nulls_to_bools: true
    use_is_even_rather_than_modulo: true
    use_late_for_private_fields_and_variables: true
    use_named_constants: true
    use_raw_strings: true
    use_setters_to_change_properties: true
    use_string_buffers: true
    use_super_parameters: true
    use_test_throws_matchers: true
    use_to_and_as_if_applicable: true
    depend_on_referenced_packages: true
    secure_pubspec_urls: true
    sort_pub_dependencies: true
    avoid_void_async: true

analyzer:
  errors:
    prefer_single_quotes: warning
    avoid_unused_constructor_parameters: warning
    avoid_dynamic_calls: warning
    literal_only_boolean_expressions: warning
    prefer_final_locals: warning
    prefer_final_parameters: warning
    prefer_foreach: warning
    prefer_if_elements_to_conditional_expressions: warning
    prefer_interpolation_to_compose_strings: warning
    prefer_mixin: warning
    require_trailing_commas: warning
    sized_box_shrink_expand: warning
    sort_child_properties_last: warning
    sort_constructors_first: false
    sort_unnamed_constructors_first: warning
    tighten_type_of_initializing_formals: warning
    unawaited_futures: warning
    unnecessary_await_in_return: warning
    unnecessary_constructor_name: warning
    unnecessary_lambdas: warning
    unnecessary_late: warning
    unnecessary_null_aware_assignments: warning
    unnecessary_null_checks: warning
    unnecessary_nullable_for_final_variable_declarations: warning
    unnecessary_parenthesis: warning
    unnecessary_raw_strings: warning
    use_colored_box: warning
    use_decorated_box: warning
    use_enums: warning
    use_if_null_to_convert_nulls_to_bools: warning
    use_is_even_rather_than_modulo: warning
    use_late_for_private_fields_and_variables: warning
    use_named_constants: warning
    use_raw_strings: warning
    use_setters_to_change_properties: warning
    use_string_buffers: warning
    use_super_parameters: warning
    use_test_throws_matchers: warning
    use_to_and_as_if_applicable: warning
    depend_on_referenced_packages: warning
    secure_pubspec_urls: warning
    sort_pub_dependencies: warning
    avoid_void_async: warning

this isn't ideal because enabling a new rule requires specifying it twice. it would be nice if there was an option to set the diagnostic severity for all lint rules.

While this would be a useful feature to add, it's fairly low on our priority list at the moment so I don't know whether we'll be able to get to it.


feat(cmd_all): add in-memory mode to single-node mode

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Part of unifying single node mode and playground. https://github.com/risingwavelabs/risingwave/issues/14997
Just provide this first, then @mikechesterwang can try to migrate our web playground to use this config. We can deprecate playground mode once we are sure this satisfies all requirements.
You can do the following to run it:
./risingwave --in-memory --max-idle-secs=1800

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Further changes not in scope for this PR. They will be done subsequently.

Deprecate playground internal implementation.
./risingwave playground will just be an alias for ./risingwave --in-memory --max-idle-secs=1800.

Will keep deprecation changes separate, in case roll back is needed.


How do I configure grunt-mocha to report global leaks?

I asked this question on StackOverflow but got no answers.
I'm trying to us grunt-mocha 0.1.7 with grunt 0.3.17 and mocha 1.8.1.  I have some intentional global leaks in my code.  When I use mocha through a browser, I see these leaks reported.  However, no leaks are reported when I run mocha via grunt.
I tried several grunt configuration variations similar to
mocha: {
   all: {
     src: ['test/**/*.html'],
     options: {
       ignoreLeaks: false
    }
  }

based on information on the GitHub project page, samples I found on the web, and by looking through the source.  I also tried to compare the source to the "spec" test reporter in the mocha source to see if there was something obvious that suggested that it wouldn't work.  I didn't see anything, although I must admit I'm still fairly new to JavaScript so I may have missed something.
Could you provide guidance on how to properly configure grunt-mocha to report global leaks?  Browser testing is fine for now, but I'd like to ultimately use a continuous integration server.
Thanks in advance.
Trevor

Closing due to age, please reopen if this is still important.


mouse without borders: cannot uninstall the service

Microsoft PowerToys version
0.73.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
Run PowerToys as admin, and click 'Uninstall the service', the service cannot be uninstalled.
✔ Expected Behavior
The service of PowerToys.MouseWithoutBorders <IP_ADDRESS> - Settings should be uninstalled

❌ Actual Behavior
The service of PowerToys.MouseWithoutBorders <IP_ADDRESS> - Settings still running in my PC.
Other Software
No response

You should be using the powertoys setting system and uncheck the service that way.

I'm also experiencing this issue.  I've tried using the PT UI to remove the service... I've even tried uninstalling PowerToys.    If I tried to terminate the process, it gives me Access Denied, even when running as Admin.
Process Explorer is reporting the process to be running out of the PowerToys folder in my user directory, but that folder was removed when I uninstalled, so I have no idea where this EXE actually is.
But it is extremely problematic because I'm trying to switch back to the regular MWB, but now I can't even do that because this rogue process takes the port so the other install can't use it.
Is there a manual way to remove the process?

I re-installed PT and tried to reconfigure the MWB service (so it could remove it) and I got this unhandled exception:
Access to the path is denied:
Global\PowerToys.MouseWithoutBorders-<IP_ADDRESS>-Default-6.

Wondering are you installing PowerToys under a different user? /needinfo

No, I've only ever used one user account on that system.
In order to revert to the non-PT version of MWB, I had to boot into safe mode and then delete the C:\Config.Msi folder.  After that, I rebooted and the PT version of MWB was not running and the other version was able to start.


Segmentation faults

On Debian when I run dvtm it just segfaults...

To produce a  more useful bug report, please includes versions.  Which version of Debian are you using?  Which version of dvtm are you using?
Have you tried it with different terminals (e.g. xterm, konsole) or different shells (e.g. fish, bash, zsh)?  Trying different terminals and shells would be useful, I think, assuming you have the time, inclination, and knowledge to do so.
Note that I am not a dvtm developer, just a busybody trying to contribute, so feel free to ignore me. :>

I am experiencing seemingly random, non reproducible segfaults.
I am using dvtm-0.15 from Void Linux packages, running on Linux 5.11.22_1 x86_64 using in st 0.8.4 and bash 5.1.8 from Void binary packages.
The same setup, apart the continuous package updates has been working without issues for at least 18 months.
The issue is non reproducible at will, but it happens when I hit enter for running a command, it happened twice with git and once with a pipe of walk | ag, see walk and the silver searcher. This does not seems tied to a specific command being run.
In dmesg I see:
[12386.128678] dvtm[11466]: segfault at<PHONE_NUMBER>58 ip<PHONE_NUMBER>96c9a9 sp 00007ffcac00f070 error 6 in dvtm[558068966000+9000]
[12386.128702] Code: c2 0f 8e c2 01 00 00 49 8b 54 24 08 48 63 f0 48 8d 34 76 4c 8b 1a 49 8d 34 b3 f6 83 e8 00 00 00 02 0f 85 32 01 00 00 8d 78 01 <89> 4e 04 66 44 89 56 08 66 44 89 4e 0a 41 89 7c 24 54 44 89 2e 80

Any info on what further detail I can provide is appreciated.

I have exactly the same issue. i'm using

void
dwm and st
abduco and dvtm

abduco/dvtm crashes from time to time (more than once within one workday)
2022-05-31T06:33:43.51240 kern.info: [660470.620935] dvtm[15454]: segfault at 55acb7311022 ip 000055a9ebaab9a9 sp 00007ffc07021410 error 6 in dvtm[55a9
ebaa5000+9000]

maybe important: Jetbrains font nerdfont and patched libxft to be able to use emojis

Then this clears out the libxft issue. I think I have noticed this happening when using copy mode (history) in dvtm and the issue seems to be the underlying editor (I use vis for copy mode as well).
When my session collapses I remember being able to still see the stuck process, as soon as I kill the copy mode process (a vis instance child of dvtm) the session exits.
 I'll enable trace dump collection and try to save the next one. Any other useful info I should collect?

i start my abduco session with
abduco -A hacking dvtm -M -m \^a

and my session terminates with
abduco: hacking: session terminated with exit status 0

but the log file contains the info msg about the segfault in dvtm

It looks like the segfaults are not related to abduco.
I'm using

dvtm
zsh
st
void

the logs gave me
2023-02-09T07:15:02.00975 kern.info: [252742.293789] dvtm[14386]: segfault at ffffffff00000004 ip 000055cc81457bd7 sp 00007ffeeb445250 error 7 in dvtm[
55cc81451000+9000] likely on CPU 7 (core 1, socket 0)
2023-02-09T07:15:02.00977 kern.info: [252742.293798] Code: 39 d0 0f 8d eb 01 00 00 49 8b 55 08 48 63 f0 48 8d 34 76 4c 8b 1a 49 8d 34 b3 f6 83 e8 00 00
 00 02 0f 85 0c 02 00 00 8d 78 01 <89> 4e 04 66 44 89 56 08 66 44 89 4e 0a 41 89 7d 54 44 89 26 80 4a
2023-02-09T07:15:02.03260 kern.info: [252742.317157] zsh[383]: segfault at 6471 ip 000055d909e83511 sp 00007ffd34964910 error 4 in zsh[55d909e43000+970
00] likely on CPU 1 (core 1, socket 0)
2023-02-09T07:15:02.03266 kern.info: [252742.317167] Code: 89 f3 eb 16 0f 1f 44 00 00 85 db 74 3c be 10 00 00 00 48 89 ef e8 1f 15 01 00 4c 89 e7 e8 c7
 99 00 00 48 89 c5 48 85 c0 74 3f <8b> 45 08 85 c0 75 d8 48 8b 7d 00 85 db 74 20 e8 0b 15 01 00 eb cd

any advice how to get more debug infos?


Inconsistancy in Inclusive ranges

Why is it that when using a match expression you have to use "..."
let a = 0;

match a {
    1...4 => println!("{}", a),
    _ => {}
}

but when using ranges you have to specifiy "..=":
for i in 1..=4 {
    println!("{}", i);
}

To me "..=" looks quite ugly in an otherwise very well designed language, is there any hope of addressing this inconsistancy?

..= can be used in patterns as well
match a {
    1 ..= 4 => println!("{}", a), // OK
    _ => {}
}

It's not available on stable channel though, but it's being stabilized right now - https://github.com/rust-lang/rust/pull/47813.
..= being ugly by itself is an orthogonal question, the syntax was ... originally, but the lang team preferred stronger visual difference between exclusive and inclusive ranges to aesthetics (see long discussion in https://github.com/rust-lang/rust/issues/28237).

I see, thanks for the quick response! I gonna check that issue now.


Renamed packages to follow a new convention

Pull Request Test Coverage Report for Build 326

957 of 961 (99.58%)  changed or added relevant lines in 29 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.4%) to 99.392%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

source/Cosmos-Data/DataStreamIsEmpty.class.st
6
10
60.0%

Totals

Change from base Build 324:
2.4%

Covered Lines:
3598

Relevant Lines:
3620

💛  - Coveralls


github actions failure

Looks like a typo in our rust.yml introduced by #71. To fix this we'll have to open a PR and keep checking the "Actions" tab (which I should've done on 71 itself, sorry) until it passes. I think.
https://github.com/rust-bitcoin/rust-bech32/actions/runs/4298692799

Fixed by #87, please close this.


Allow import in paras & res

Resources and paragraphs should allow importing from other files.

Or force to split the files.


feat(torii): integrate long poll getTransactions

closes DOJ-269
closes #1363
use the toriI_getTransactions long poll api when using katana and fallback to getEvents

Will close this for now. We will re-open if necessary. Interesting to keep torii using standard json rpc which is for now well optimized with the recent events.


Creates LNURLw image folks can embed

The image is generated from the LNURL id, so unique LNURLws are compatible.
Makes sense to add the same function to LNURLp

Codecov Report

Merging #152 (97e519d) into master (32a3dbb) will increase coverage by 1.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   29.35%   30.47%   +1.11%
==========================================
  Files          26       29       +3
  Lines        1785     1969     +184
==========================================
+ Hits          524      600      +76
- Misses       1261     1369     +108

Impacted Files
Coverage Δ

lnbits/helpers.py
28.75% <0.00%> (ø)

lnbits/tasks.py
50.00% <0.00%> (ø)

lnbits/decorators.py
51.61% <0.00%> (ø)

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 32a3dbb...97e519d. Read the comment docs.

Sorry, need to format with prettier etc. Will also add lnurlw API wndpoint

Is this ready to merge?

Ready or not, I'm merging.


Add new var for tracking if camera preview has been initiated

Issue:

We're getting errors like camera already started and camera already stopped very frequently
Previously, we used to track camera preview using a flag called isCameraShown, but the problem here is that we used to set this flag only when the camera started or stopped, and not when we initiated the request to start/stop the camera
The camera plugin takes some time to start/stop the camera preview, and hence we may get the above errors if the user tries to open the camera in between
Also, we cannot change isCameraShown to track when the camera start/stop request was initiated, as we use it hide the parent components, and if we do so, the the user would see a weird UI till the camera preview actually starts

Solution

Created a new flag isCameraPreviewInitiated to track whether the user has intitiated a camera preview - if yes, we wont intitiated it again. Same goes for stopping the preview
The existing flag isCameraShown is renamed to isCameraPreviewStarted which aptly signifies the purpose of this flag.

Sentry bugs:

Uncaught (in promise): Error: camera already started
Uncaught (in promise): Error: camera already stopped

looks good, lets test this on multiple devices,


Allow arbitrary byte-array for secret

The current implementation does not allow using an arbitrary secret (such as a random generated secret that is base64-encoded).
The changes I have added allow using an arbitrary array of bytes as the secret.

@zerodivide1 Thanks for your contribution! In a couple of minutes it will be published in the 2.1.0 version.

@pose Thank you for taking the merge!


drivers: i2c_nrfx_twi: Make use of NRFX_TWI_FLAG_SUSPEND

Make use of the new flag introduced in nrfx v1.7.2 that suspends
transfers, in order to properly handle scattered I2C transactions,
especially to perform i2c_burst_write() in the way expected by
display drivers, i.e. as a continuous transaction on the bus,
without the repeated START between its two parts.
Fixes #15116 (although the issue mentions the TWIM peripheral, on which the hardware limitation prevents the issue from being solved, on all SoCs of nRF52 Series TWI can be used instead of TWIM).

@pabigot please, take a look at this bug-fix PR


[suggestion] In-house implementation of Binary-coded decimal fixed point

Feature request
Implement a Binary coded decimal fixed point rational type and use it throughout the code-base.
Motivation
We do not need a general purpose Fixed point operation library. Given that we are responsible for the logic of addition and subtraction and exponentiation it makes sense to cut down on the dependencies and do an in-house implementation with the appropriate assumptions and little to no extra overhead. Given that we have a new NumericalValue type, the choice of using i64 as the backing type is thoroughly misguided too.
Who can help?
@appetrosyan

Superseded by Arbitrary precision arithmetic


Utils truncation api update

Would appreciate help with frame_skip tests, I can't quite figure out why env.env.steps isn't incrementing.


update review-add validation for review comments.

Fixes https://github.com/eclipse-xpanse/xpanse/issues/2202
backend updated:

make comments required:

alert show above buttons and when alert failure, buttons can open modal:

The title of the PR is not current.

LGTM

LGTM

LGTM

The title of the PR is not correct.

updated.

LGTM

LGTM


SilverStripe 4.1.x and Silverstripe-S3 module - TinyMCE WYSIWYG doesn't load on initial CMS Load

From @obj63mc on May 29, 2018 21:32
Currently testing using v4.1.x and dev/master of silverstripe-s3.
I wasn't sure where the best place to log this issue but assuming it will probably need to be moved to a fix in silverstripe/framework as it is an issue with the HTMLEditorField, or possibly needs to go to the silverstripe-s3 repo.
Steps to reproduce

Create a clean install of SS4.x using the composer command -
     composer create-project silverstripe/installer /path/to/project 4.1.1

Configure the site as normal and require silverstripe-s3
     composer require silverstripe/silverstripe-s3

Complete configuration of S3

Go to your site/admin and login

Edit the Home Page-  I get the following JS error -
 bundle.js?m=1520903238:1 Uncaught ReferenceError: tinymce is not defined
     at Object.create (bundle.js?m=1520903238:1)
     at Object.init (bundle.js?m=1520903238:1)
     at init.onadd (bundle.js?m=1520903238:1)
     at o (vendor.js?m=1520903238:1)
     at Array.<anonymous> (vendor.js?m=1520903238:1)
     at HTMLDocument.<anonymous> (vendor.js?m=1520903238:1)
     at HTMLDocument.dispatch (eval at t.exports (vendor.js?m=1520903238:1), <anonymous>:3332:9)
     at HTMLDocument.eventHandle (eval at t.exports (vendor.js?m=1520903238:1), <anonymous>:2941:28)
     at Object.trigger (eval at t.exports (vendor.js?m=1520903238:1), <anonymous>:3210:12)
     at init.triggerHandler (eval at t.exports (vendor.js?m=1520903238:1), <anonymous>:3874:24)

Screen shot -

I notice though that in my network console it is trying to load the tinymce script from the amazon public directory, not the local server address - example :
    ....s3.amazonaws.com/public/_tinymce/tinymce-cms-92563982d3.js?_=1527628916905

vs
/assets/tinymce/tinymce-cms-92563982d3.js?=1527628916905
Since this is loading the tinymce script file from S3 not sure if that is the cause of a race condition, cross domain origin issue or ?
If I refresh the page in the browser (eg /admin/pages/edit/show/1), the CMS loads normally and the WYSIWYG loads normally.  If I go to a different section of the CMS besides pages though such as say 'Settings' and then back to pages I get the same issue until I reload the site.
Is this possibly an issue as the file is being generated into the /public/assets directory instead of the /public/resources directory?  If there is a way to exclude this file from loading on S3 or a way to change the write path for the tinymce js I can test this some more to try and confirm what exactly is causing the issue.
Copied from original issue: silverstripe/silverstripe-cms#2177

From @maxime-rainville on July 13, 2018 3:18
The silverstripe/s3 module is experimental. It's not something we're actively working on at this time.

From @obj63mc on July 13, 2018 16:12
As a note, I turned off and removed the S3 module and still have the same issue.  So not 100% sure it is caused by that module.
When trying to determine the cause of this.  My site is setup with the following -

the 'mysite' code lives in the 'app' folder in the root.  I have a structure that is based off of - https://github.com/a2nt/silverstripe-webpack

The following modules are installed -
     aws/aws-sdk-php                            3.62.11
     colymba/gridfield-bulk-editing-tools       3.0.0-beta4
     composer/ca-bundle                         1.1.1
     composer/installers                        v1.5.0
     dnadesign/silverstripe-elemental           2.1.0
     dnadesign/silverstripe-elemental-list      1.0.0
     dnadesign/silverstripe-elemental-userforms 1.0.0
     dnadesign/silverstripe-elemental-virtual   dev-master 3867957
     doctrine/instantiator                      1.1.0
     embed/embed                                v3.3.5
     guzzlehttp/guzzle                          6.3.3
     guzzlehttp/promises                        v1.3.1
     guzzlehttp/psr7                            1.4.2
     intervention/image                         2.4.2
     jonom/silverstripe-betternavigator         4.1.1
     league/flysystem                           1.0.45
     league/flysystem-aws-s3-v3                 1.0.19
     m1/env                                     2.1.2
     marcj/topsort                              1.1.0
     monolog/monolog                            1.23.0
     moosylvania/silverstripe-age-gate          2.1.0
     mtdowling/jmespath.php                     2.4.0
     myclabs/deep-copy                          1.8.1
     nikic/php-parser                           v3.1.5
     paragonie/random_compat                    v2.0.17
     phpdocumentor/reflection-common            1.0.1
     phpdocumentor/reflection-docblock          4.3.0
     phpdocumentor/type-resolver                0.4.0
     phpspec/prophecy                           1.7.6
     phpunit/php-code-coverage                  4.0.8
     phpunit/php-file-iterator                  1.4.5
     phpunit/php-text-template                  1.2.1
     phpunit/php-timer                          1.0.9
     phpunit/php-token-stream                   2.0.2
     phpunit/phpunit                            5.7.27
     phpunit/phpunit-mock-objects               3.4.4
     psr/cache                                  1.0.1
     psr/container                              1.0.0
     psr/http-message                           1.0.1
     psr/log                                    1.0.2
     psr/simple-cache                           1.0.1
     sebastian/code-unit-reverse-lookup         1.0.1
     sebastian/comparator                       1.2.4
     sebastian/diff                             1.4.3
     sebastian/environment                      2.0.0
     sebastian/exporter                         2.0.0
     sebastian/global-state                     1.1.1
     sebastian/object-enumerator                2.0.1
     sebastian/recursion-context                2.0.0
     sebastian/resource-operations              1.0.0
     sebastian/version                          2.0.1
     sheadawson/silverstripe-linkable           2.0.0
     silverstripe/admin                         1.1.2
     silverstripe/asset-admin                   1.1.2
     silverstripe/assets                        1.1.2
     silverstripe/blog                          3.2.0
     silverstripe/campaign-admin                1.1.2
     silverstripe/cms                           4.1.2
     silverstripe/comment-notifications         2.0.1
     silverstripe/comments                      3.1.2
     silverstripe/config                        1.0.4
     silverstripe/elemental-blocks              1.0.0
     silverstripe/errorpage                     1.1.2
     silverstripe/externallinks                 2.0.2
     silverstripe/framework                     4.1.2
     silverstripe/graphql                       1.1.2
     silverstripe/html5                         2.0.1
     silverstripe/lumberjack                    2.0.0
     silverstripe/recaptcha                     dev-master 6c839da
     silverstripe/recipe-cms                    1.1.2
     silverstripe/recipe-core                   1.1.2
     silverstripe/recipe-plugin                 1.3.0
     silverstripe/redirectedurls                2.0.0
     silverstripe/reports                       4.1.2
     silverstripe/segment-field                 2.2.1
     silverstripe/siteconfig                    4.1.2
     silverstripe/spamprotection                3.0.0
     silverstripe/tagfield                      2.1.0
     silverstripe/userforms                     5.2.0
     silverstripe/vendor-plugin                 1.3.3
     silverstripe/versioned                     1.1.2
     swiftmailer/swiftmailer                    v5.4.9
     symbiote/silverstripe-gridfieldextensions  3.2.0
     symfony/cache                              v3.4.12
     symfony/config                             v3.4.12
     symfony/filesystem                         v4.1.1
     symfony/finder                             v3.4.12
     symfony/polyfill-apcu                      v1.8.0
     symfony/polyfill-ctype                     v1.8.0
     symfony/polyfill-mbstring                  v1.8.0
     symfony/translation                        v2.8.42
     symfony/yaml                               v3.4.12
     unclecheese/display-logic                  2.0.1
     undefinedoffset/sortablegridfield          2.0.6
     webmozart/assert                           1.3.0
     webonyx/graphql-php                        v0.8.0
     wilr/silverstripe-googlesitemaps           2.1.2

When referencing https://github.com/silverstripe/silverstripe-framework/issues/8228 it seems like it may be because we are both using webpack for our front end code, but can't say if that is the cause or not either.  I am in the process of doing a clean install and changing each step to replicate my previous site to see where it breaks.

From @anishpixel on July 19, 2018 9:47
I am having the same issue, I am using webpack for my web build too so think something is conflicting.

From @spark-green on July 31, 2018 0:15
Hi guys,
I am having the same issue,
I am not using  S3 module. but using webpack to run foundation on front-end.
And surprising it is happening only with one single page in CMS.
screenshot

Console error as below

For reference I am using below version of silver-stripe and other modules

"php": ">=5.6.0",
"silverstripe/cms": "4.1.1",
"silverstripe/framework": "4.1.1",
"silverstripe/recipe-plugin": "^1",
"silverstripe/recipe-cms": "1.",
"silverstripe/versioned": "1.",
"silverstripe/blog": "3.",
"silverstripe/widgets": "2.",
"ryanpotter/silverstripe-cms-theme": "2.",
"undefinedoffset/sortablegridfield": "2.",
"silverstripe/staticpublishqueue": "4.",
"jonom/focuspoint": "dev-master",
"unclecheese/display-logic": "2.",
"sheadawson/silverstripe-linkable": "2.",
"silverware/validator": "1.",
"jonom/silverstripe-text-target-length": "2.",
"axllent/silverstripe-cms-tweaks": "2.",
"symbiote/silverstripe-gridfieldextensions": "^3.0"

Any help on this is much appreciated.

From @jpmcc on August 8, 2018 14:19
Also experiencing similar issue. However, I am using the S3 module, and not using Webpack. The TinyMCE script is being loaded from S3.
Just currently trying to work out why that is placed into assets when all other admin JS isn't

From @anishpixel on August 8, 2018 14:54
No reply from SS mods or contributors? Seems odd to avoid this as various people are having this issue...

From @jpmcc on August 8, 2018 15:26
When reloading, the requirements system places the call for the script into the page source, as you would expect, therefore I assume everything blocks until all the scripts have loaded, and everything works.
Navigating within the CMS, when you move to an area that requires the TinyMCE editor, the JavaScript requirements are pulled in via Ajax and anx-include-js header. I assume there is some timing issue here between the script being requested and the editor trying to load, but before the script has loaded in, hence the tinymce is not defined error.
Is there any way of forcing the request for the TinyMCE script earlier, or delaying the editor from trying to initialise for a bit longer?

From @jpmcc on August 8, 2018 15:2
It looks to be a timing thing. The script tinymce-cms-<unique-string>.js is  actually loaded from S3, but I am guessing it is after it is actually called. I assume that is why if the page is reloaded, it appears to work as it is now already in the cache. However going back some time later, it is requested again but with a cache busting parameter.
I can see why it is generated as it references the site domain to setup a baseUrl var, also based on a specific configuration of the editor.
Just wondering what can be done about that.
Not totally sure if this fits in with everyone else's experience if not using the S3 module.

@jpmcc The behaviour of x-include-js is the same without the S3 module installed, so provided the request to the tinymce-cms.js is returning a valid response I can’t see why it would result in a race condition or anything. It’s not being blocked by CORS headers or something is it?

From @jpmcc on August 8, 2018 15:45
Is there a way to configure the Requirements system to place the TinyMCE generated file to a local folder? There is some information on requirements about changing where combined assets are placed, but so far not making any headway with that.

You might be able to override the asset handler for TinyMCE generated files. Totally untested code below, but it might provide a starting point:
SilverStripe\Core\Injector\Injector:
  League\Flysystem\Filesystem.localpublic:
    class: League\Flysystem\Filesystem
    constructor:
      FilesystemAdapter: '%$SilverStripe\Assets\Flysystem\PublicAssetAdapter'
      FilesystemConfig:
        visibility: public
  LocalGeneratedAssetHandler:
    class: SilverStripe\Assets\Flysystem\GeneratedAssets
    properties:
      Filesystem: '%$League\Flysystem\Filesystem.localpublic'
  SilverStripe\Forms\HTMLEditor\TinyMCECombinedGenerator:
    properties:
      AssetHandler: '%$LocalGeneratedAssetHandler'

From @jpmcc on August 9, 2018 8:4
Thanks Loz, I think I was going down the same path based on the docs, but I think I'm still missing something. The GeneratedAssetHandler being injected into the TinyMCE generator still uses the SilverStripe\S3\Adapter\PublicCacheAdapter as the Adaptor.

Maybe you need a YAML header to ensure it’s loaded last
---
After:
  - '#corehtml'
---
SilverStripe\Core\Injector\Injector:
  League\Flysystem\Filesystem.localpublic:
# ...

From @jpmcc on August 9, 2018 8:29
Not sure the configuration is even being picked up :-(. Created a yml file in the _config folder. I would expect to see an instance of League\Flysystem\Filesystem being created. The only one that triggers the constructor is for the S3 adapter.
Therefore I'm assuming I am missing something pretty fundamental. All my other yml files appear to be processed (multiple builds and flushes).

From @jpmcc on August 9, 2018 8:33
yup, using
---
Name: tinymce_override
After:
  - '#silverstripes3-flysystem'
---

I'll try #corehtml

From @jpmcc on August 9, 2018 8:36
No luck.
Really appreciate the help :). I may have to come back to this later.

The following does seem to work in my testing - App\TestAssetAdapter is the adapter used in TinyMCECombinedGenerator:
---
After:
  - '#corehtml'
---
SilverStripe\Core\Injector\Injector:
  League\Flysystem\Filesystem.localpublic:
    class: 'League\Flysystem\Filesystem'
    constructor:
      FilesystemAdapter: '%$App\TestAssetAdapter'
      FilesystemConfig:
        visibility: public
  LocalGeneratedAssetHandler:
    class: 'SilverStripe\Assets\Flysystem\GeneratedAssets'
    properties:
      Filesystem: '%$League\Flysystem\Filesystem.localpublic'
  SilverStripe\Forms\HTMLEditor\TinyMCECombinedGenerator:
    properties:
      AssetHandler: '%$LocalGeneratedAssetHandler'

namespace App;

use SilverStripe\Assets\Flysystem\PublicAssetAdapter;

class TestAssetAdapter extends PublicAssetAdapter
{
}

Probably best at this point to hop on the forums or Slack to save adding any more to this issue 😄

@jpmcc has confirmed that the above will allow the TinyMCE JS to be written to the local filesystem rather than S3, which offers a workaround for the issue for now.
As this definitely occurs with the S3 module installed, I’m going to move this issue to that repo. Even if it requires a fix in framework, it’s best to track the issue there as that module seems to be the only definite cause.
For those experiencing this issue without S3 installed (@spark-green, @anishpixel?) I’m going to re-open https://github.com/silverstripe/silverstripe-framework/issues/8228 as there’s less S3-related noise there. If you’re still experiencing this issue, please paste the output of composer show into that issue so we know which exact versions of each module you’re using. Thanks!

Migrated from https://github.com/silverstripe/silverstripe-cms/issues/2177. There’s a workaround available here https://github.com/silverstripe/silverstripe-cms/issues/2177#issuecomment-411688248

Hi @kinglozzer , thanks for opening this.
It is happening consistently for me as well on any given SS4 project.
This is a sample composer extract
    "require": {         "php": ">=5.6.0",         "silverstripe/cms": "^4.2",         "silverstripe/framework": "^4.2",         "silverstripe/recipe-plugin": "*",         "silverstripe/recipe-cms": "*",         "silverstripe/versioned": "1.*",         "silverstripe/blog": "3.*",         "silverstripe/widgets": "2.*",         "silverstripe/userforms": "5.*",         "silverstripe/redirectedurls": "2.*",         "ryanpotter/silverstripe-cms-theme": "2.*",         "undefinedoffset/sortablegridfield": "2.*",         "silverstripe/staticpublishqueue": "4.*",         "silverware/validator": "1.*",         "unclecheese/display-logic": "2.*",         "sheadawson/silverstripe-linkable": "2.*",         "jonom/silverstripe-text-target-length": "2.*",         "jonom/focuspoint": "3.*",         "dnadesign/silverstripe-elemental": "3.0.x-dev",         "axllent/silverstripe-cms-tweaks": "2.*",         "heyday/silverstripe-menumanager": "~3.0.0",         "heyday/silverstripe-colorpalette": "2.*"     }
Unfortunately your proposed solution does not seem to fix the issue at all for me.

@eehondas It doesn't look like you have the s3 module installed. If you’re experiencing that issue without using the s3 module, can you please post here instead: https://github.com/silverstripe/silverstripe-framework/issues/8228? Thanks :)

@kinglozzer Yes.
Done thank you. I just posted here because I followed from the other thread.

Bump for great justice.

Hey @JoshuaCarter, sorry for the delay - there's not a lot of support for this module as I'm not actively using it in production, and it was only ever meant as a proof-of-concept to test the new SS4 filesystem layer (I'm not entirely sure of the reasons why it was picked up under the silverstripe GitHub org :))
Anyway - have you been able to try the workaround that was posted by @kinglozzer here: https://github.com/silverstripe/silverstripe-cms/issues/2177#issuecomment-411688248? I'm keen to know if that still works for you or not, as it might help us assess where the problem lies.
I have a feeling it could be a race condition (TinyMCE file is written to S3 -> attempts to read immediately -> file can't be read -> file gets rewritten next request -> etc) but I haven't been able to confirm that as the cause yet. Theoretically the module shouldn't return an S3 URL unless the file was successfully replicated to S3 and exists in the S3 bucket (e.g. it should wait until the file is replicated within S3 before returning the URL) but perhaps we're missing something there.

@JoshuaCarter - I submitted a PR that has the workaround for this bug auto included (force tinymce files to write to the local filesystem).  If you checkout the TinyMCEAdapter as well as the .yml file.  If you implement that on your project you should have no issues.

Hey @JoshuaCarter, I've just merged this in, so using the latest dev-master should resolve this for you now. Either @obj63mc or I will probably release a new version once #23 is merged.

I've just released 0.4.0 that should hopefully resolve this for you!
Please let us know if you continue to have issues with this.


respondent validation

Before creating a pull request make sure that:

[X] commit messages are meaningful and follow good commit message guidelines
[X] README and other documentation has been updated / added (if needed)
[X] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-2002
Change description
Make changes to civil-general-applications and civil-general-app-ccd-definition for respondent details
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

merging this through to allow passing GA master pipeline


New Private cloud portal release: 7.7.0

release scope: https://mendix.atlassian.net/projects/DES/versions/23346/tab/release-report-all-issues

Reviewed and waiting for the go ahead to publish.


Better complexity for measures of presortedness

According to Computing and ranking measures of presortedness by J. Chen, the complexity of some of our measures of presortedness simply outrightly suck. With better algorithms, we could change them as follows, (quotes are from the paper):

[ ] « Exc(X) is  also linear computable (see , The Art of Computer Programming, Vol. 3: Sorting and Searching, Ex.  5.2.2-2) and we cannot do better. »
[x] « Altman and Chlebus [Sorting roughly sorted sequences in parallel] proved that Par(X) can be computed with O(n log Par(X)) comparisons », which means that Par(X) can be computed with a O(n log n) algorithm since 0 <= Par(X) <= n - 1.
[ ] « Osc(X) can be computed in O(n log(Osc(X)/n)) time [Adaptive Sorting by O. Pertersson]. », which is roughly equivalent to O(n log n) considering that 0 <= Osc(X) <= (n * (n - 2) - 1) / 2. However Adaptive Sorting mentions that computing Osc(X) is an open problem, but that it is easy to compute it in O(n log n).
[x] Our implementation of Enc is O(n ²) while it could be reduced to O(n log n) by using a binary search during the construction of the encroaching lists.
[ ] T. M. Chan and M. Pătraşcu give a O(n sqrt log n) algorithm to compite Inv(X) in Counting Inversions, Offline Orthogonal Range Counting, and Related Problems.

Also, some of the comments make me doubt the implementation of the of the measures of presortedness. Did I really understand every definition, or did I take some mental shortcuts? It's left to investigate... I'll gladly accept any help if anyone knows how to implement these algorithms with the complexities above.

As explained in this lengthy comment, the measure of presortedness Radius(X) described in by T. Altman and Y. Igarashi Roughly Sorting: Sequential and Parallel Approach is pretty much the same as Par(X) described by V. Estivill-Castro and D. Wood in A New Measure of Presortedness, which means that we won't implement a probe::radius in cpp-sort.
However the good news is that the Roughly Sorting papers gives a linear method to compute Radius(X), which means that we can surely change our Par(X) implementation. The described method has the following properties:

O(n) time instead of O(n² log n)
O(n) space instead of O(1)
Works on bidirectional iterators instead of random-access

Having an O(n² log n) algorithm is kind of unsightly, but as can be seen in the benchmarks, the current implementation of Par(X) is a sneaky beast with a high enough short-circuiting power that it manages to run faster than O(n) algorithms when it doesn't encounter an adverse pattern. It would be nice if we could take advantage of the short-circuits while running in O(n) time, but I fear that it isn't possible.

Commit 77c4c756d1cff0ce3f2566b4a942fa10fbad9270 changes probe::osc to run in O(n log n) time and O(n) space. Thanks a lot to @Control55 from @The-Studio-Discord for coming up with the new algorithm.


Reference Line - text label when using data

At the moment, if you pass a dataset to the ReferenceLine component, your label prop must be the name of a column rather than a string.
This makes sense when there are multiple entries, but if you are using a query to create a single line, we should have an option to pass a text label as well.
Not sure how this would best be implemented since the prop is a string and could be either a text label or a column name.
One approach is: check if the column name exists, and if not use it as a text label.

Done
https://docs.evidence.dev/components/annotations/#reference-line


Integrate TLC SI Summer Session II Schedule

When TLC SI information is available for Summer Session II, update and deploy TLC_SI_DATA.json
Due Date: July 29, 2019
Deployment Deadline: Aug 2, 2019

@a6wu TLC SI for SSII is not available online and the deployment deadline is almost upon us - please advise

Closing for the following reasons:

Deployment deadline missed
TLC SI SSII 2019 data is not available as of 08/12/2019


add new properties to the swagger spec

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

Adding new properties requires a new api-version. So, if needs to be done in the same api-version for some reason , it will need approval from Azure API review board ( Adrian Hall, Jeffery Richter, Johan Stenberg etc.)

/azp run automation - sdk

I have created a new version for this change

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk


Please don't use chromium as webengine

Hi,
please dont use chromium as webengine because of this two things:
1- binary size
2- don't became second electron :D

Please read README before opening issues

@behdanisohrab I think our Discord would have been a better place for this.
But just to clarify here for others that look for this info via github issue and would like a more detailed explanation:

We plan to always have Electrobun use the system webview by default
It doesn't really matter for binary size since Electrobun's smart bsdiff-based update mechanism means your app's updates are as small as 4KB regardless of the initial binary size, and our zstd-based self-extracting mechanism means your initial binary sizes are squeezed as small as possible.
MANY people want the option to use a consistent renderer including pinning the version to mitigate the amount of work they need to do to make advanced web-apps cross platform. Even when I explain the security tradeoffs they are insistent and fine making that tradeoff and really want this option. Most of these cases exist today as webapps that only support chromium because startups tend not to have infinite resources and that's the most widely used renderer. And they'd really love to be able to extend into desktop apps without having to deal with a ton of cross-browser issues. So we do still intend to support this option.
on Windows the system webview is Edge, which is Chromium. So I'm not sure I even understand your actual request.

I do appreciate your contribution though so thank you for taking the time to raise your concerns.


Error compression level

When trying to export with a compression level of the following error:
The path specified in the error is not my pc

Ah, looks like a regression. I'll take a look at it when I get a chance. In the meantime, does no compression still work?

Yes, it works uncompressed
I wanted to ask you something.
It would be possible to add some protection in app.exe? because when you rename it to app.zip is possible to extract all files. It would be interesting that the zip stay with password protection for example.
The HTML Compiler software works the same way but the zip is password protected.

Cool. By the way, the issue is with the new way permissions work in Windows 10. I'm going to update Web2Exe to handle this situation soon :)
In regards to your question about security, as far as I know, there's not a good way to do this. The problem is that NW.js needs to extract the source files onto the hard drive when you run the exe. It extracts the files into a temp directory, and then runs itself with that directory as an argument. There's an issue about security on the NW.js repo that basically says "it's not yet possible to protect the files"
The best security that I can think of would be to minify your javascript code so that it is obfuscated and basically unreadable by a human. Even then, there are probably ways to get at your original code. Such is the life of web technologies.

@hitaloramon This should be fixed now in the latest release. Let me know if it works :)

Thanks @jyapayne, I will test this version and warn you if it worked.
Congratulations, web2executable is amazing and his work too!
Sorry my English


Update Sparkle framework for security vulnerabilities

https://vulnsec.com/2016/osx-apps-vulnerabilities/
Hermes is vulnerable to this, so would be good to get Sparkle updated.

😨😭🔫

This vulnerability has now been easily weaponized. https://www.evilsocket.net/2016/01/30/osx-mass-pwning-using-bettercap-and-the-sparkle-updater-vulnerability/

Hello, unfortunately I can no longer contribute tested changes to Hermes, and have since moved on, so somebody else will have to address this. Please contact me or @nriley if you have interest in maintaining and actively developing Hermes.
As for the risk factor of this vulnerability, it isn't very significant when one considers Sparkle uses DSA signatures to sign and verify updates; and there is no network of trust associated with the key pair.
Regardless this is still a vulnerability, so it should be fixed, if anybody is up to taking over.

As for the risk factor of this vulnerability, it isn't very significant when one considers Sparkle uses DSA signatures to sign and verify updates; and there is no network of trust associated with the key pair.

See the link in the OP, the DSA stuff doesn't matter.

My mistake -- I had only read the second link :). Yes looks like the weak app signing via DSA is irrelevant. At any rate, I don't have the resources to fix this issue, which would require:

Add a SSL/TLS cert to hermesapp.org
Push a fix for Hermes that has the HTTPS Sparkle URL.

One could get a letsencrypt cert, however I don't have a Mac to do (2).
Somebody needs to take over the project if they want to see this fixed.

@winny- all that's needed is an updated version of sparkle. you don't need to do any HTTPS stuff.

Sparkle 1.13.1 specifically

Unfortunately to push a new version of Sparkle in Hermes, one needs to have XCode and friends. In addition they will need two keys which I can hand over, provided you're trust worthy.
https://github.com/HermesApp/Hermes/blob/master/Documentation/ReleaseEngineering.md

Just an fyi: 1.13.1 on website might still be vulnerable

For the SSL/TLS option, you could use CloudFlare to front the domain and
then just pass through to https://HermesApp.github.io transparently. That
is a free option and doesn't require you to do anything on your end to host
the website or proxy the SSL/TLS cert.
In any case, you don't even need to get HTTPS on hermesapp.org to solve
this particular issue. If you see in my diff, I swapped it to use
https://raw.githubusercontent.com/... which takes the domain out of it
entirely and goes directly to GitHub.
Also, it's best to get things on HTTPS and upgrade Sparkle. Only doing
the latter just means that any more Sparkle vulns could cause another
security issue.
On Saturday, January 30, 2016, Greg Slepak<EMAIL_ADDRESS>wrote:

Just an fyi: 1.13.1 on website might still be vulnerable
https://github.com/sparkle-project/Sparkle/issues/726
—
Reply to this email directly or view it on GitHub
https://github.com/HermesApp/Hermes/issues/254#issuecomment-177403026.

@taoeffect check the last comment in
https://trac.videolan.org/vlc/ticket/11987#comment:29 -- perhaps you want
to try with something besides VLC?
On Saturday, January 30, 2016, Reed Loden<EMAIL_ADDRESS>wrote:

For the SSL/TLS option, you could use CloudFlare to front the domain and
then just pass through to https://HermesApp.github.io transparently. That
is a free option and doesn't require you to do anything on your end to host
the website or proxy the SSL/TLS cert.
In any case, you don't even need to get HTTPS on hermesapp.org to solve
this particular issue. If you see in my diff, I swapped it to use
https://raw.githubusercontent.com/... which takes the domain out of it
entirely and goes directly to GitHub.
Also, it's best to get things on HTTPS and upgrade Sparkle. Only doing
the latter just means that any more Sparkle vulns could cause another
security issue.
On Saturday, January 30, 2016, Greg Slepak<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Just an fyi: 1.13.1 on website might still be vulnerable
https://github.com/sparkle-project/Sparkle/issues/726
—
Reply to this email directly or view it on GitHub
https://github.com/HermesApp/Hermes/issues/254#issuecomment-177403026.

@reedloden did you mean to send that reply to this thread or here? Either way, I can't get even the most basic of modules working (like hack_title.rb).

@taoeffect The other thread, sorry. I'm watching all your threads right now as you investigate this, and doing it from mobile while I'm out with friends isn't helping with keeping track of stuff. Hah.

Sorry, I can't address this either — too many other projects contending with my time and resources, and I don't even use Hermes as a user any more.  If someone (or more than one person) wants to take over Hermes maintenance, I'm happy to facilitate this in any way possible, but they need to be actually committed to it.  I've had enough experiences where people asked to contribute to one of my projects, I spent a bunch of time trying to help and then never heard from them again.

Good news folks!
There are ways to mitigate against this and it's also not as bad as reported.
Just published details:
Sky Not Falling: Sparklegate Not As Bad As It Could Be

Apologies! Sky Kinda Falling + Protecting Yourself From Sparklegate
It turns out that I was mistaken, in some situations Gatekeeper does get bypassed. I just published a post with details + mitigations. Thanks to @radekk for insisting that I was missing something!
https://www.taoeffect.com/blog/2016/02/apologies-sky-kinda-falling-protecting-yourself-from-sparklegate/


Hook for asyncpg Postgres Connector

Is your feature request related to a problem? Please describe.
By default, hooks are available for different Postgres connectors, such as psycopg2. But for the async frameworks, it's common to use async Postgres connector, for instance asyncpg.
Feature Description
It would have been nice to have a hook for asyncpg connector implemented in the hooks.
Describe Alternatives
An alternative solution to this is to use 3rd party instruments available, such as this one, which is lacking some of the useful features (i.e. what queries have been executed).
Priority
This is a Must-Have for us at the moment.

Thanks for the feature @a-feld . That's nice.
Will there be a release anytime soon?

Yup! We're working on getting it out either today or tomorrow! 🎉

Yup! We're working on getting it out either today or tomorrow! 🎉

Fantastic! Thanks


flaw and bugfix

Detected a flaw which results in a port left open and detected a bug when data=b'' error occured. Improved readme also and added version info in it. Please review and merge.

Thanks for the PR, looks good