How to install Kong on Fedora 21? Requires: lua = 5.1.4 , but already 5.2.2

Hi,  When I install Kong, I met below issues, please advise: Thanks!
--> Finished Dependency Resolution
Error: Package: kong-0.2.0_2-1.noarch (/kong-0.2.0_2.el7.noarch)
Requires: lua = 5.1.4
Installed: compat-lua-5.1.5-2.fc21.x86_64 (@fedora)
lua = 5.1
Installed: lua-5.2.2-8.fc21.x86_64 (@anaconda)
lua = 5.2.2-8.fc21
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@ip-172-30-0-136 ~]# yum install lua
Failed to set locale, defaulting to C
Package lua-5.2.2-8.fc21.x86_64 already installed and latest version
Nothing to do

Kong needs lua 5.1, so you'll have to remove 5.2 and use 5.1.

Ok. thanks.
On Fri, May 8, 2015 at 8:27 PM, Thibault Charbonnier <
<EMAIL_ADDRESS>wrote:

Kong needs lua 5.1, so you'll have to remove 5.2 and use 5.1.
—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/kong/issues/212#issuecomment-100217657.


Add license information

Hello!
I found link to this project from https://hackaday.com/2020/09/25/hacking-a-cheap-action-cam-into-a-dashcam-with-a-microcontroller/
Could you please add information about license of this repository — is it allowed to copy, change and use code in any purpose?
It would be great to see any popular open source license.

License added, thank you for the reminder
On Fri, Sep 25, 2020 at 9:28 AM Alexey Vazhnov<EMAIL_ADDRESS>wrote:

Hello!
I found link to this project from
https://hackaday.com/2020/09/25/hacking-a-cheap-action-cam-into-a-dashcam-with-a-microcontroller/
Could you please add information about license of this repository — is it
allowed to copy, change and use code in any purpose?
It would be great to see any popular open source license.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tterev3/dash-cam-controller/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFBZ7Z4YRFETFG6BE4GDS3SHSLHHANCNFSM4RZRPY2Q
.

@tterev3 , thank you for fast answer and for the MIT license!


Published version out of sync with repo?

Hi,
I see the latest published version is 0.24.0 but this repo only has 0.23.0.  Has it been published from another repo?
Thanks!

No it was published from this repo. The 0.24.0 npm package was published from a checkout of tag 0.24.0.
What might have have caused confusion is the repo's releases page has the 0.24.0 tag listed, but it is displayed less prominently than 0.23.0 and isn't labelled as a "release" because it lacks release notes.


HV-1023 Prevent resource aggregation to occur in an Google App Enviro…

…nment

This works, but I am not sure whether I like the GAE-specific coding. I feel I'd prefer just an example in the ref guide showing how to configure a custom locator / interpolator with the aggregation feature disabled. Any thoughts?

This works, but I am not sure whether I like the GAE-specific coding.

I am also a bit torn, but in the end I thought for the ease of use it is better this way. And really we are not importing any App Engine specific classes. I think it makes it works much smoother for people using Validator on App Engine. And we know that it is being used. We had several issues over time related to App Engine.

I feel I'd prefer just an example in the ref guide showing how to configure a custom locator / interpolator with the aggregation feature disabled.

The problem is that atm you can  only configure a custom ResourceBundleLocataor via the programmatic bootstrap. We would either need to add a custom MessageInterpolator for use in App Engine which can already be configured via validation.xml or we need some provider specific option to configure PlatformResourceBundleLocator accordingly. I would assume that in most cases Validator is used as part of another framework in which case it is easiest/best if things keep working out of the box.
This is maybe not perfect, but in the end I find it the lesser evil.
Btw, I think it is a oversight that the ResourceBundle.Context class is not white listed. Not quite sure how one would report this or how one would get more detailed information on why it should not be whitelisted.

We would either need to add a custom MessageInterpolator

I would just add an example showing a custom MessageInterpolator using a non-aggregating RBL in the docs and not add any code at all. That way there is no reliance on GAE code on the HV side at all, as a bonus the approach will continue to work also if e.g. that class is renamed in GAE. Sure, we don't import GAE-classes, but we rely on it some specifics of it now.
Anyways, if you feel the usability advantages out-weigh that concern, let's merge it.

if you feel the usability advantages out-weigh that concern, let's merge it

I think so. I think we should merge this. One "improvement" we could make is to not try a Google App Engine specific class, but rather directly ResourceBundle.Control. This won't have any effect on normal JVM runtimes and in the case of App Engine we catch the exception and skip aggregation. So it becomes really a generic check with no reliance to App Engine classes at all. The added benefit would be that bundle aggregation would magically work on App Engine in case they decide to whitelist ResourceBundle.Control. The only reference to App Engine would be in a comment explaining why we do the class loading check at all. Thoughts?

Yes, that seems a bit better.

Yes, that seems a bit better.

Ok then. We go for that. I'll update the pull request.

pushed an update

Applied, thanks, @hferentschik. Note that I've added one more commit for moving the presence check into a static method invoked once at class load time. The not safely published Boolean made me feel a bit uneasy ;)

Thanks.

The not safely published Boolean made me feel a bit uneasy ;)

Do you think this could really lead to a problem?

The only thing that really could happen is that the check is done several times on different threads. It's more that such not safely published field looks wrong and makes one (well, me) wonder each time whether there is actually a problem or not. Plus, that way the null check during each instantiation is avoided.

The only thing that really could happen is that the check is done several times on different threads

Ok, then we agree :-)


Add a internal Aggregator to fix overestimate thetaSketch,quantilesDoublesSketch in  ingestion task

Fixes #6743 .
When the data source has one or more thetasketch,quantilesDoublesSketch,ingestion task(when maxBytesInMemory not -1) will generate a lot of small files and  will trigger off heap OOM when merge this spill files.

Description
Add a internal Aggregator to fix overestimate thetaSketch,quantilesDoublesSketch.   This PR add a new internal countAdjustmentAggregator, it is used to aggregate count and judge complex metric(for now  thetaSketch,quantilesDoublesSketch) whether reached expansion capacity threshold, and append bytes to bytesInMemory when reached.
This is a better way than #10241 on aggregation performance. The following are the aggregation test results:

Benchmark                                     (adjustFlag)  (maxBytesInMemory)  (rollup)  (rollupOpportunity)  (rowsPerSegment)  (schema)  Mode  Cnt      Score      Error  Units
ComplexMetricAdjustStrategyBenchmark.addRows          true<PHONE_NUMBER>0      true                  low             75000   complex  avgt   10  75030.753 ±  485.785  us/op
ComplexMetricAdjustStrategyBenchmark.addRows          true<PHONE_NUMBER>0      true             moderate             75000   complex  avgt   10  74210.326 ±  404.810  us/op
ComplexMetricAdjustStrategyBenchmark.addRows          true<PHONE_NUMBER>0      true                 high             75000   complex  avgt   10  74502.573 ±  230.314  us/op
ComplexMetricAdjustStrategyBenchmark.addRows         false<PHONE_NUMBER>0      true                  low             75000   complex  avgt   10  73830.057 ±  758.054  us/op
ComplexMetricAdjustStrategyBenchmark.addRows         false<PHONE_NUMBER>0      true             moderate             75000   complex  avgt   10  72092.055 ±  210.018  us/op
ComplexMetricAdjustStrategyBenchmark.addRows         false<PHONE_NUMBER>0      true                 high             75000   complex  avgt   10  72549.061 ± 1107.324  us/op

This PR has:

[x] been self-reviewed.
[x] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

Key changed/added classes in this PR

MaxIntermediateSizeAdjustStrategy
ThetaSketchSizeAdjustStrategy
DoublesSketchSizeAdjustStrategy
InternalCountAdjustmentAggregator
OnheapIncrementalIndex
AggregatorFactory
......

Consuming time will increase the effect by about 15% in our test druid cluster.

I can't find reason for thisTravis-ci: https://travis-ci.org/github/apache/druid/jobs/742105278 https://travis-ci.org/github/apache/druid/jobs/742105297

I've been trying to solve this same problem recently and came across this PR! I'll take a look soon @liuxiaohui1221.

Ok,no problem,Thank you @gianm .


k8s deployment with WGAccess failed with could not list node interfaces

Describe the bug
this integration test fails when WGAcess is required and for some reason it reports failed to get node 11 endpoint within the error message even when the deployment is not run using node 11 at all
Network
devnet
Screenshots

Verification steps:

Deploy a Kubernetes cluster using a network with a WireGuard access
Deployed 2 VMs using a network with a WireGuard access

It worked fine after the fix:

https://github.com/threefoldtech/tfgrid-sdk-go/pull/537


Issue getting littr and fedbox to communicate with each other correctly

Here is what is in my .env for littr
# HOSTNAME is used as the base for the absolute URLs in the site
HOSTNAME=littr.local
# LISTEN_PORT is the port number that the application will listen on for connections
LISTEN_PORT=3000
# LISTEN_HOST is the host/ip that the application will listen on for connections
LISTEN_HOST=localhost
# ENV the environment type sets different configuration settings, valid are: DEV, QA, STAGING, PROD
ENV=dev
# API_URL is the url of the fedbox instance that provides our C2S ActivityPub API
API_URL=http://fedbox.local
# SESS_AUTH_KEY is used for encrypting the session data
SESS_AUTH_KEY=16_chars_enc_key=
# SESS_ENC_KEY
SESS_ENC_KEY=16_chars_enc_key+
# OAUTH2_KEY the default OAuth2 key used by the frontend to connect to the C2S ActivityPub end-points
OAUTH2_KEY=1e2ba133-f4a5-4182-8540-309646e9ea59
# OAUTH2_SECRET the default OAuth2 secret used by the frontend
OAUTH2_SECRET=littr
# SESSIONS_BACKEND the backend to use for session storage, valid: cookie, fs
SESSIONS_BACKEND=fs
# DISABLE_SESSIONS setting this to true, makes the instance essentially read only, by disallowing user logins
DISABLE_SESSIONS=false
# DISABLE_DOWNVOTING disables allowing Dislike activities
DISABLE_DOWNVOTING=false
# DISABLE_VOTING disables all Like/Dislike activities
DISABLE_VOTING=false

Here is what is in my fedbox .env
HOSTNAME=fedbox.local
LISTEN=localhost:4000
ENV=dev
STORAGE=fs
STORAGE_PATH=.

I have littr.local and fedbox.local setup in /etc/hosts. I also have both littr and fedbox running behind a reverse proxy using nginx.
I ran these commands for setting up fedbox:
./bin/ctl bootstrap
./bin/ctl ap actor add admin
./bin/ctl oauth client add --redirectUri http://littr.local/auth/fedbox/callback

This is what I get when I go to littr.local

In the littr log I get this:
ERRO[0000] http://fedbox.local/actors/1e2ba133-f4a5-4182-8540-309646e9ea59: Unable to load from the AP end point: invalid status 404
ERRO[0000] Failed to load actor: Unable to load Actor: http://fedbox.local/actors/1e2ba133-f4a5-4182-8540-309646e9ea59
ERRO[0000] oauth2: cannot fetch token: 403 Forbidden

OK, I see. From what I can see you have two issues.

The session can not be saved - if you're on a linux machine /tmp/fedbox.local should be writable by the user that runs the application - this is the error in the screenshot "Failed to save session". I guess I'll add a followup task to make session path more configurable, or use the STORAGE_PATH.
The second issue, is that the application can't load the generated OAuth2 application that you configured in the settings. Can you please access the url from the error: http://fedbox.local/actors/1e2ba133-f4a5-4182-8540-309646e9ea59 and paste the log from fedbox, with maybe a screenshot of the result?

On the vm running littr I have /tmp/littr.local folder and the user running littr can write to it.
Log from fedbox:
ERRO[0003] Not Found addr="<IP_ADDRESS>:36538" elapsed=1.47849ms id=fedbox/sxsPfDPG0z-000001 len=6640 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 17:00:30 UTC" ua="Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0" uri="http://localhost:4000/actors/1e2ba133-f4a5-4182-8540-309646e9ea59"

Error from going to that url:
{
  "@context": "http://localhost:4000/ns#errors",
  "errors": [
    {
      "status": 404,
      "message": "1e2ba133-f4a5-4182-8540-309646e9ea59 not found in actors",
      "trace": [
        {
          "file"<EMAIL_ADDRESS>          "line": 79,
          "calee": "github.com/go-ap/errors.wrap(0x0, 0x0, 0xc4a318, 0xd, 0xc0000cf7e0, 0x2, 0x2, 0x0, 0x0, 0x0, ...)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 42,
          "calee": "github.com/go-ap/errors.Annotatef(...)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 54,
          "calee": "github.com/go-ap/errors.wrapErr(0x0, 0x0, 0xc4a318, 0xd, 0xc0000cf7e0, 0x2, 0x2, 0x0, 0x0, 0x0, ...)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 109,
          "calee": "github.com/go-ap/errors.NotFoundf(...)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 238,
          "calee": "github.com/go-ap/fedbox/app.HandleItem.func1(0xc0000c2c00, 0x7f1d22af7368, 0xc000137f20, 0xc000137f20, 0x0, 0x0, 0xc000186960)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 225,
          "calee": "github.com/go-ap/handlers.ItemHandlerFn.ServeHTTP(0xc78f48, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 431,
          "calee": "github.com/go-chi/chi.(*Mux).routeHTTP(0xc000057ec0, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015c660, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 70,
          "calee": "github.com/go-chi/chi.(*Mux).ServeHTTP(0xc000057ec0, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 298,
          "calee": "github.com/go-chi/chi.(*Mux).Mount.func1(0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b360, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 31,
          "calee": "github.com/go-chi/chi.(*ChainHandler).ServeHTTP(0xc000191100, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 431,
          "calee": "github.com/go-chi/chi.(*Mux).routeHTTP(0xc000057da0, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015c630, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 70,
          "calee": "github.com/go-chi/chi.(*Mux).ServeHTTP(0xc000057da0, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 298,
          "calee": "github.com/go-chi/chi.(*Mux).Mount.func1(0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b400, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 431,
          "calee": "github.com/go-chi/chi.(*Mux).routeHTTP(0xc000057d40, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015c620, 0x7f1d22af7338, 0xc000195400, 0xc0000c2c00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 61,
          "calee": "github.com/go-ap/fedbox/app.ActorFromAuthHeader.func1.1(0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc000061cc0, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 37,
          "calee": "github.com/go-chi/chi/middleware.GetHead.func1(0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b040, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 34,
          "calee": "github.com/go-chi/chi/middleware.RealIP.func1(0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b060, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 70,
          "calee": "github.com/go-chi/chi.(*Mux).ServeHTTP(0xc000057d40, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 298,
          "calee": "github.com/go-chi/chi.(*Mux).Mount.func1(0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b640, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 431,
          "calee": "github.com/go-chi/chi.(*Mux).routeHTTP(0xc000057740, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015c910, 0x7f1d22af7338, 0xc000195400, 0xc0000c2b00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 46,
          "calee": "github.com/go-chi/chi/middleware.RequestLogger.func1.1(0xd67ca0, 0xc0001a20e0, 0xc0000c2a00)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00018d320, 0xd67ca0, 0xc0001a20e0, 0xc0000c2a00)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 76,
          "calee": "github.com/go-chi/chi/middleware.RequestID.func1(0xd67ca0, 0xc0001a20e0, 0xc0000c2900)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00015b660, 0xd67ca0, 0xc0001a20e0, 0xc0000c2900)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 21,
          "calee": "github.com/go-ap/fedbox/app.Repo.func1.1(0xd67ca0, 0xc0001a20e0, 0xc0000c2800)"
        },
        {
          "file": "net/http/server.go",
          "line": 2007,
          "calee": "net/http.HandlerFunc.ServeHTTP(0xc00018d350, 0xd67ca0, 0xc0001a20e0, 0xc0000c2800)"
        },
        {
          "file"<EMAIL_ADDRESS>          "line": 86,
          "calee": "github.com/go-chi/chi.(*Mux).ServeHTTP(0xc000057740, 0xd67ca0, 0xc0001a20e0, 0xc0000c2700)"
        },
        {
          "file": "net/http/server.go",
          "line": 2802,
          "calee": "net/http.serverHandler.ServeHTTP(0xc0001a2000, 0xd67ca0, 0xc0001a20e0, 0xc0000c2700)"
        },
        {
          "file": "net/http/server.go",
          "line": 1890,
          "calee": "net/http.(*conn).serve(0xc000187ea0, 0xd6c260, 0xc000195240)"
        },
        {
          "file": "net/http/server.go",
          "line": 2928,
          "calee": "created by net/http.(*Server).Serve"
        }
      ],
      "location": "github.com/go-ap/errors@v0.0.0-20200610194301-39b7d0cbba26/http.go:54"
    }
  ]
}

I suspect that this issue might be related to #38. I'll come back with a followup when I find a fix for it.

Hey @endoffile78 I think I fixed the issue by fixing the bootstrap command for fedbox. Can you please give it a spin and let me know if it fixes this issue too?

On the homepage I now get this:

I get the same error as before on the other pages.
My littr .env is
# HOSTNAME is used as the base for the absolute URLs in the site
HOSTNAME=littr.local
# LISTEN_PORT is the port number that the application will listen on for connections
LISTEN_PORT=3000
# LISTEN_HOSTNAME is the host/ip that the application will listen on for connections
LISTEN_HOSTNAME=localhost
# ENV the environment type sets different configuration settings, valid are: DEV, QA, STAGING, PROD
ENV=dev
# API_URL is the url of the fedbox instance that provides our C2S ActivityPub API
API_URL=http://fedbox.local
# SESS_AUTH_KEY is used for encrypting the session data
SESS_AUTH_KEY=16_chars_enc_key=
# SESS_ENC_KEY
SESS_ENC_KEY=16_chars_enc_key+
# OAUTH2_KEY the default OAuth2 key used by the frontend to connect to the C2S ActivityPub end-points
OAUTH2_KEY=e13d5e23-1c62-4c92-b248-23aa8d213423
# OAUTH2_SECRET the default OAuth2 secret used by the frontend
OAUTH2_SECRET=littr
# SESSIONS_BACKEND the backend to use for session storage, valid: cookie, fs
SESSIONS_BACKEND=fs
# DISABLE_SESSIONS setting this to true, makes the instance essentially read only, by disallowing user logins
DISABLE_SESSIONS=false
# DISABLE_DOWNVOTING disables allowing Dislike activities
DISABLE_DOWNVOTING=false
# DISABLE_VOTING disables all Like/Dislike activities
DISABLE_VOTING=false

My fedbox .env is
HOSTNAME=fedbox.local
LISTEN=localhost:4000
ENV=dev
STORAGE=fs
STORAGE_PATH=.

In the fedbox log I get:
RRO[0008] Not Found addr="<IP_ADDRESS>:38116" elapsed=1.410219ms id=fedbox/dssr5P9R44-000001 len=6640 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=littr.local-b1a72a7 uri="http://localhost:4000/actors/e13d5e23-1c62-4c92-b248-23aa8d213423"ERRO[0008] Invalid username or password
ERRO[0008] Unauthorized addr="<IP_ADDRESS>:38120" elapsed=1.07406ms id=fedbox/dssr5P9R44-000002 len=1005 method=POST proto=HTTP/1.0 scheme=http status=401 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=Go-http-client/1.1 uri="http://localhost:4000/oauth/token"
ERRO[0008] Forbidden addr="<IP_ADDRESS>:38122" elapsed="782.275_s" id=fedbox/dssr5P9R44-000003 len=6155 method=POST proto=HTTP/1.0 scheme=http status=403 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=Go-http-client/1.1 uri="http://localhost:4000/oauth/token"
ERRO[0008] Not Found addr="<IP_ADDRESS>:38124" elapsed="873.234_s" id=fedbox/dssr5P9R44-000004 len=6613 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=littr.local-b1a72a7 uri="http://localhost:4000/actors?type=Person&type=Service&type=Group&type=Application&type=Organization"
ERRO[0008] Not Found addr="<IP_ADDRESS>:38128" elapsed="888.457_s" id=fedbox/dssr5P9R44-000005 len=6614 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=littr.local-b1a72a7 uri="http://localhost:4000/objects?context=-&type=Article&type=Note&type=Link&type=Page&type=Document&type=Video&type=Audio"
ERRO[0008] Not Found addr="<IP_ADDRESS>:38132" elapsed="890.822_s" id=fedbox/dssr5P9R44-000006 len=6614 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 18:09:44 UTC" ua=littr.local-b1a72a7 uri="http://localhost:4000/objects?type=Article&type=Note&type=Link&type=Page&type=Document&type=Video&type=Audio"
ERRO[0017] Not Found   addr="<IP_ADDRESS>:38146" elapsed=1.057821ms id=fedbox/dssr5P9R44-000007 len=6612 method=GET proto=HTTP/1.0 scheme=http status=404 ts="Tue, 14 Jul 2020 18:09:53 UTC" ua=littr.local-b1a72a7 uri="http://localhost:4000/inbox?maxItems=25&object.context=-&object.type=Article&object.type=Note&object.type=Link&object.type=Page&object.type=Document&object.type=Video&object.type=Audio&type=Create"

Using thunder this what I get for the client information
{"Id":"e13d5e23-1c62-4c92-b248-23aa8d213423","Secret":"littr","RedirectUri":"http://littr.local/auth/fedbox/callback","Extra":"bnVsbA=="}

Hey @endoffile78 can you test again ? I did some improvements to bootstrapping/initial run in for issue #38, and I want to know if it fixes your problem too. Let me know please. :)

No, I'm still having some problems, the one I described in https://github.com/go-ap/fedbox/issues/6 seems to be fixed.
When starting littr I get:
ERRO[0000] http://fedbox.local/objects?context=-&type=Article&type=Note&type=Link&type=Page&type=Document&type=Video&type=Audio: Unable to load from the AP end point: invalid status 404
ERRO[0000] http://fedbox.local/objects?type=Article&type=Note&type=Link&type=Page&type=Document&type=Video&type=Audio: Unable to load from the AP end point: invalid status 404

I get this on the littr homepage:

Those are not fatal issues.
The error in the screenshot is related to the browser sending a session cookie to go-littr, but no session exists for it.
The 404 errors from fedbox are there just because the fedbox.local/objects collection doesn't exist until you save something in it.  As soon as you add a submission they will be gone.


iOS11 hangs on VR prompt

When running an example on https://poly.google.com on iOS11, when entering VR, the VR prompt "place your phone into your cardboard viewer" hangs.
edit: removing iPhone 7+ distinction, was due to orientation lock :cry:  (but still exists in other iPhone models)

Confirmed on iOS 11.1.2, iPhone 6s, screen orientation unlocked

I haven't dug into this yet, but if you've given this some thought, what's your best guess on the easiest workaround (and hopefully a viable long-term solution)? I can experiment, but I figured I'd ask first. Thanks, @jsantell!

@cvan I haven't been able to recreate this again on any version of iOS11 over the last few months with screen orientation unlocked, and suspect either something changed in a later iOS11 build, or screen orientation was ultimately locked

Haven't seen this in a few months; closing.


[Feature]: Run tests directly without spinning up a test server, in an Angular and Jest.

Feature description
Run E2E tests in angular ,
ng e2e
This command invariably necessitates running ng serve beforehand, which typically consumes around 2 minutes.
It would be highly convenient for developers if tests could be run directly against an already running service.

This seems to be an issue pertaining to Angular.

This issue is related to @puppeteer/ng-schematics:puppeteer
async function executeE2ETest(   options: PuppeteerBuilderOptions,   context: BuilderContext ): Promise<BuilderOutput> {   let server: BuilderRun | null = null;   try {     message('\n Building tests 🛠 ... \n', context);     await executeCommand(context, [tsc`, '-p', 'e2e/tsconfig.json']);
server = await startServer(options, context);
const result = await server.result;

message('\n Running tests 🧪 ... \n', context);
const testRunnerCommand = getCommandForRunner(options.testRunner);
await executeCommand(context, testRunnerCommand, {
  baseUrl: result['baseUrl'],
});

message('\n 🚀 Test ran successfully! 🚀 ', context, 'success');
return {success: true};

} catch (error) {
message('\n 🛑 Test failed! 🛑 ', context, 'error');
if (error instanceof Error) {
return {success: false, error: error.message};
}
return {success: false, error: error as string};
} finally {
if (server) {
await server.stop();
}
}
} ng e2e` must start a server, this is a waste of time.
If ng e2e can test a exist server, that would be great.

Imho this is a duplicate of https://github.com/puppeteer/puppeteer/issues/12222.


DBZ-8501 Support for JDBC offset and schema history stores

https://issues.redhat.com/browse/DBZ-8501

LGMT. Just a minor nitpick

@mfvitale  can we merge this?

@jcechace Applied, thanks!


chore(scancode): Print JSON raw results non-pretty

ScanCode's raw JSON results are not exposed by ORT and thus not looked at by humans. So disable pretty-printing for the chance of a tad quicker result generation.

FYI @Etsija and @lamppu, as this aligns with DOS.


Provide easy parser of Received headers

It would be nice if there was a built in parser for the Received headers, like there is for Address and Date

Looking further into this, parsing "Received" seems like a huge headache -- I was looking at the tests written for a python script and am baffled by the variety... just looking at the "from" part gives me a number of variations for where 'name', 'ip' and 'hostname' could show up: https://github.com/Te-k/pyreceived/blob/master/test.py
It would be much easier of course if I was only parsing the main parts, so the parsed header class provided a "from", a "by", an "id", etc... rather than "fromName", "fromIp", "fromHostname", but I guess it all depends on how this information is used.
Could you perhaps expand on your use-case and tell me what parts you're interested in?  I've noticed sometimes "cipher", "server", "envelope-from", "envelope-for", "protocol" are some example additional fields as well... how useful is all this given that it's all possibly missing, or could be tampered with or faked entirely?

My first use-case what to use it to verify TLS delivery through the Received chain. So "fromName", "fromIp" is not needed, that would in any case be over-the-top

Even that's pretty difficult to determine as there are no standards to follow.  I'm inclining towards not accepting this as part of the library at this point, because:

I'd be in a constant race to correctly parse headers from an infinite number of new possible servers or versions, always losing out at some point when a new "Received" header is discovered, or some random server somewhere decides to be clever
The library in its current form tries to be standards-compliant rather than all-encompassing... I'd rather build confidence in that what the library claims to parse from a message is true considering 1) standards, and 2) common practice (e.g. commonly ignored parts of a standard or mistakes in implementation).

I think parsing the Received header belongs outside of this library for that reason -- a library that is specifically designed to be constantly chasing new Received header formats discovered, not one looking for reliability.
I'd be happy to consider doing that with some help if anyone's interested in a joint effort.

That makes sense, I'm however puzzled there is no RFC in regards to Received:
Received: From X by Y [with Z]; DATE seems to be as close as one can get

I found it defined here: https://tools.ietf.org/html/rfc5321#section-4.4
It gives some defined structure but it's pretty loose as far as values go.  I could consider providing the basic parts: From, By, Via, With, For, ID and Timestamp if that helps... for any field that exists, provide a string for its value?
I haven't seen an example use of Via though looking at the pyreceived tests.

That would be a helpful start

Happy to add that, but I'm not sure you'll particularly love it.
When/if servers add TLS connection info, it's usually in a comment... so you'd have to look through parsed comments (I'll clarify with an example when I've uploaded some code).  Figuring out if a message was transmitted via TLS from point-to-point is just not possible looking at a Received header for many reasons.
Having said that, I can at least parse the standardized parts -- maybe parts of it are useful for other use cases.

I realise that, but it would still be helpful :)

I've pushed some commits to master.  You should be able to:

$message->getAllHeadersByName('Received') and get an array of ReceivedHeader objects
call $header->getFromName, getFromHostname, getFromAddress (and getByName, etc...)
call $header->getValueFor('with') (or 'via', 'id', 'for', 'from' or 'by' -- 'from' and 'by' would return full value of the header, e.g. 'name (host.tld [<IP_ADDRESS>])'
call $header->getDateTime() to get a DateTime for the date/time stamp in the header.

Please have a look and let me know what you think.  I'll probably release a 1.1 for it and a few other changes over the weekend if all is well.

Excellent job :)

Released in 1.1 :)

Closing this as it seems resolved and no further comments, if you find any issues please open a separate ticket.


Need logging in Space Cloud

Currently space cloud doesn't provide any logging. We need a proper logging mechanism with configurable levels.

Do you have any thoughts on what this might look like?  Should the log level be configurable via the config.yaml or as a CLI parameter?

Here is a sample Dockerfile
FROM alpine:3.9
WORKDIR /space-cloud
RUN set -ex  \
  && apk add --no-cache ca-certificates unzip libc6-compat

RUN wget https://spaceuptech.com/downloads/linux/space-cloud.zip -O space-cloud.zip
RUN unzip space-cloud.zip \
    && rm space-cloud.zip \
    && chmod +x space-cloud

COPY config.yaml .

 Then when running in a container it would be easy to change on the fly without having to rebuild a container.

@speshak and @MichaelLeeHobbs this is a tricky piece. The questions which comes to my mind is, whats the logging level? Where are the logs being published? In a file? Something like statsd or Prometheus?
Maybe we can start with simply logging to a file. Here we'll need the following inputs:

Enable and disable logging
Logging level
File to flush the logs to

When doing something look for precedent, it will greatly increase the odds of being compatible with what already exists.
For levels: https://www.tutorialspoint.com/log4j/log4j_logging_levels.htm I always use these with one exception. I add an audit/security level to log anything that auditors or security related will need.
Where to send the logs? stdout. Then you can take advantage of Dockers logging.

@MichaelLeeHobbs I think we can use the logrus library. Let's give the user the option to decide where to send the logs (to a file or stdout). We can default to stdout for docker.

Enable and disable logging
Logging level
File to flush the logs to
Pluggable Logging endpoints: ElasticSearch, Syslog, etc

A note on ES per discord discussion. There are a few different ways ES can be auth'ed and they vary by the environment. Below is an AWS example as configured in fluentd.
<endpoint>
    url https://vpc-production-blue-ubj6n...xxi.us-gov-west-1.es.amazonaws.com
    region us-west-1
    access_key_id "AKIALB6.....MLSCJHQ"
    secret_access_key "hNvzshI.....sUf0oPG3EsvUdRc"
  </endpoint>

Agreed. Lets break this issue down into smaller chucks. Maybe one ticket per module / package we have? Will make it easier to track and contribute. What say?

Even though this issue is pretty old I want to get started implementing the standardized logging for space-cloud. I would recommend using logrus.
This looks good on a first view and the logs are generated in JSON and can, therefore, be streamed easily to a centralized logging-and-monitoring-platform. What do you say @YourTechBud?

Sounds perfect. @ledex i was thinking of making this as a module under the utils folder. The idea is to implement our own logger. This would be an interface. This will let us add something like elasticsearch in the future without having to change any SC code. Makes sense?

I see. Yeah, we should definitely do that, but I would still base this on the aforementioned logrus. Reimplementing the functionality of logrus doesn't make sense in my eyes.
I would suggest, that I make a proposal in the next few days and then we can improve it from there.

Oh i guess i wasn't clear enough. Lets build it in a way to add implementations in the future. The first implementation will be logrus

We have finally decided to use https://github.com/uber-go/zap. @sharadregoti is working on this right now.

Coming in v0.19.2


Blendshape Documentation

Eideren edit: This new documentation is related to the blendshape pr over here https://github.com/stride3d/stride/pull/2136

This file is missing a simple overview of how one would import and use blendshapes, likely because https://github.com/stride3d/stride/pull/2136 still needs some work. Changed it to draft for now :)


passmanager fails when called a second time on different circuit

Environment

Qiskit version: 1.0.2
Python version:
Operating system:

What is happening?

N = 14

qc = QuantumCircuit(N)
qc.h(0)
qc.cx(0, range(1,N))
qc.measure_all()

eagle_pm = generate_preset_pass_manager(3, backend=eagle_backend)
trans_qc = eagle_pm.run(qc)

qc2 = QuantumCircuit(N)
qc2.h(N//2)
qc2.cx(range(N//2, 0, -1), range(N//2-1, -1, -1))
qc2.cx(range(N//2, N-1), range(N//2+1, N))
qc2.measure_all()

trans_qc2 = eagle_pm.run(qc2)

fails on the second call with
TranspilerError: "The 'layout' must be full (with ancilla)."
If I make a new PM instance it works, so I am assuming there is some state being held.
How can we reproduce the issue?
run above
What should happen?
it should work
Any suggestions?
No response

Are you sure you're using Qiskit 1.0.2?  I can't reproduce with 1.0.2 nor current main, and I think I already fixed this issue after you raised it before: #11784, #11787.
For what it's worth, here's my complete reproducer script, guessing at your undefined variables, in case they're material:
from qiskit import QuantumCircuit
from qiskit.transpiler.preset_passmanagers import generate_preset_pass_manager
from qiskit_ibm_runtime import QiskitRuntimeService

prov = QiskitRuntimeService()
eagle_backend = prov.get_backend("ibm_sherbrooke")

N = 14

qc = QuantumCircuit(N)
qc.h(0)
qc.cx(0, range(1,N))
qc.measure_all()

eagle_pm = generate_preset_pass_manager(3, backend=eagle_backend)
trans_qc = eagle_pm.run(qc)

qc2 = QuantumCircuit(N)
qc2.h(N//2)
qc2.cx(range(N//2, 0, -1), range(N//2-1, -1, -1))
qc2.cx(range(N//2, N-1), range(N//2+1, N))
qc2.measure_all()

trans_qc2 = eagle_pm.run(qc2)

Ahh no your right.  The AI transpiler install downgraded me to 1.0.0.  Thanks!


packagist off version

Just noticed that ss4 updates is not available at packagist.

Made a PR who might fix the issue.
https://github.com/isaacrankin/silverstripe-social-feed/pull/12


i18n(ko-KR): update 0-introduction/1.mdx

Description (required)

update 0-introduction/1.mdx
#8239

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
tutorial/0-introduction/1.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Feature request: get info about unpaid invoices

sdk_services.payment_by_hash only returns a result for invoices that were paid. It would be nice if I could check the state of an invoice that is still outstanding. Right now I have to infer that from the lack of response.

Technically we can. Can you elaborate on the use case?

It would be much more explicit, this way I need to guess whether the invoice I'm looking up doesn't exist, or exists but isn't paid. It's a standard thing most frontend would want to do: Pass the payment_hash to the backend, receive the state of the invoice.
The same goes for payments! Frontends need to be able to check all states explicitly.


Add new exercise wordy

As described in #125

I would ask the same question about this as for the linked-list: does it make sense to do this as part of porting the exercise, or as its own PR?  What do you think?

These kind of PR are special ones, because we're taking code from another track and adapting it to this track.
During the process, if I see some code that I can improve, I improve it. I do this because the code in this track can be considered as independent of the code in xjavascript. These improvements can be a detail that ES2015 makes easier to do, better variable names,...
From my point of view, if there are small improvements that don't change dramatically the code of the tests or the solution while adding the new exercise, I would include them in the first PR. If there is something I want to discuss, I'll first add the exercise, and then, I'll open a issue on the subject.

I'll change this one and resubmit.

I would consider each track to be independent and fix anything about an exercise in the first PR.

Fantastic! A new exercise!


fix for Doorkeeper incompatibility

Fixes issue #265
When secondary authorization request is made to the token url, OAuth2 appends the status code the to redirect URI. This is incompatible with Doorkeeper which then refuses to recognize the registered callback url. I made a minor change to client.rb at LOC 92-98--by checking to see if the request being made was the secondary request to the token URL, and changing the redirect URI to remove the appended authorization code and status if so.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Coverage decreased (-0.9%) to 95.313% when pulling c12444d74aa0df7972714b3cbab26d339e197601 on flatiron-school:master into fb502c755ed8801aa5d4575f18b86a9b7ecf9f5e on intridea:master.

Looks like this pull request will depend on https://github.com/intridea/oauth2/pull/263 to be merged in order for the build to run successfully.

I think the problem you are referring to is in the omniauth-oauth2 gem.
See: https://github.com/intridea/omniauth-oauth2/issues/93
A workaround is given at: https://github.com/intridea/omniauth-oauth2/issues/93#issuecomment-227247801
The PR that causes the issue: See https://github.com/intridea/omniauth-oauth2/pull/70/files

Any way we could push this fix over the finish line?

@neerfri is correct. this isn't an issue with this gem, but rather with omniauth-oauth2. I've used the fix mentioned above in many omniauth strategies.

Thanks for the fix @neerfri & for the analysis and bump @johaywood .
Any interest in taking on a broader maintenance role in this project?

@pboling I'd be interested in helping out with maintenance. I've certainly relied on this project heavily, and continue to, so I definitely don't want to see it fall by the wayside. Let me know where the priorities are and I'll see where I can jump in.


Refactor Sequence and Regimen pages

Coverage increased (+0.02%) to 91.526% when pulling 099d0c25cfd2969b04f1c5eb0bd8026f7950cab3 on gabrielburnworth:staging into 8d379044ab619dd486c1d81cc80be80a9c97fa49 on FarmBot:staging.


listenip bug

Found a typo, probably relating to atleast agent.pp listenip.
The following code block has its comparison backwards:
Find if listenip is set. If not, we can set to specific ip or
to network name. If more than 1 interfaces are available, we
can find the ipaddress of this specific interface if listenip
is set to for example "eth1" or "bond0.73".
if $listenip == undefined {
if ($listenip =~ /^(eth|bond|lxc).*/) {
$int_name = "ipaddress_${listenip}"
$listen_ip = inline_template('<%= scope.lookupvar(int_name) %>')
} elsif is_ip_address($listenip) {
$listen_ip = $listenip
} else {
$listen_ip = $::ipaddress
}
} else {
$listen_ip = $::ipaddress
}
It should be:
Find if listenip is set. If not, we can set to specific ip or
to network name. If more than 1 interfaces are available, we
can find the ipaddress of this specific interface if listenip
is set to for example "eth1" or "bond0.73".
if $listenip != undefined {
if ($listenip =~ /^(eth|bond|lxc).*/) {
$int_name = "ipaddress_${listenip}"
$listen_ip = inline_template('<%= scope.lookupvar(int_name) %>')
} elsif is_ip_address($listenip) {
$listen_ip = $listenip
} else {
$listen_ip = $::ipaddress
}
} else {
$listen_ip = $::ipaddress
}

Hi JvdW,
Thank you for making time to create this issue.
I'll take a look at it. This was recently changed with pull request #46
Kind regards,
Werner

Hi JvdW,
I'll close this ticket, because you provided the pull request.
Thanks again!
Kind regards,
Werner


Get proposal metrics on dashboard look incorrect

The get proposal times on the dashboard look incorrect relative to 99th percentile.

The average metric is correct, the histogram buckets cap out on 5s, so it is unable to estimate higher than that.

Thanks Kuba in which case we need explicit bucket config


Bowser boiler doesnt compile.

What's going on?
Following the guide listed in the Readme.md then doing yarn compile I get the following errors:
src/navigation/example-navigator.ts:1:10 - error TS2305: Module '"/Users/mike.cann/dev/bam/experiments/PizzaApp/node_modules/@types/react-navigation/index"' has no exported member 'createStackNavigator'.

1 import { createStackNavigator } from "react-navigation"
           ~~~~~~~~~~~~~~~~~~~~

src/navigation/root-navigator.ts:1:10 - error TS2305: Module '"/Users/mike.cann/dev/bam/experiments/PizzaApp/node_modules/@types/react-navigation/index"' has no exported member 'createStackNavigator'.

1 import { createStackNavigator } from "react-navigation"
           ~~~~~~~~~~~~~~~~~~~~

src/navigation/stateful-navigator.tsx:5:1 - error TS6133: 'throttle' is declared but its value is never read.

5 import throttle from "lodash.throttle"
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Steps to reproduce

ignite new PizzaApp
( Choose Bowser (alpha) when prompted )
cd PizzaApp
yarn compile

ignite doctor results:
System
  platform           darwin
  arch               x64
  cpu                8 cores                                         Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  directory          /Users/mike.cann/dev/bam/experiments/PizzaApp

JavaScript
  node               8.11.1       /Users/mike.cann/.nvm/versions/node/v8.11.1/bin/node
  npm                5.6.0        /Users/mike.cann/.nvm/versions/node/v8.11.1/bin/npm
  yarn               1.7.0        /usr/local/bin/yarn

React Native
  react-native-cli   2.0.1
  app rn version     0.55.4

Ignite
  ignite             2.1.0        /Users/mike.cann/.nvm/versions/node/v8.11.1/bin/ignite
vvv -----[ DEBUG ]----- vvv
{ Error: Command failed: java -version 2>&1

    at ChildProcess.exithandler (child_process.js:275:12)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
  killed: false,
  code: 1,
  signal: null,
  cmd: 'java -version 2>&1',
  stderr: '' }
^^^ -----[ DEBUG ]----- ^^^

@mikecann what version of @types/react-navigation is installed ?

@fadeojo We decided not to go with Ignite in the end but to help you debug. This is the package.json, its basically just the Pizza app taken from your guide:
{
  "name": "PizzaApp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest",
    "compile": "tsc --noEmit -p . --pretty",
    "format": "npm-run-all format:*",
    "format:js": "prettier --write {.,**}/*.js",
    "format:json": "prettier --write {.,**}/*.json",
    "format:md": "prettier --write {.,**}/*.md",
    "format:ts": "prettier --write {.,**}/*.{ts,tsx} && tslint --fix -p .",
    "lint": "npm-run-all lint:*",
    "lint:ts": "tslint -p .",
    "postinstall": "solidarity",
    "hack:types-react-navigation": "rimraf node_modules/@types/react-navigation/node_modules/@types",
    "hack:types-react-native": "rimraf node_modules/@types/react-native/node_modules/@types",
    "hack:types-react-test-renderer": "rimraf node_modules/@types/react-test-renderer/node_modules/@types",
    "patch": "patch-package",
    "prepare": "npm-run-all patch hack:*",
    "storybook": "storybook start -p 9001 --skip-packager",
    "ios": "react-native run-ios"
  },
  "dependencies": {
    "apisauce": "0.14.3",
    "lodash.throttle": "4.1.1",
    "mobx": "4.2.1",
    "mobx-react": "5.1.2",
    "mobx-state-tree": "2.0.5",
    "ramda": "0.25.0",
    "react": "16.3.1",
    "react-native": "0.55.4",
    "react-native-i18n": "2.0.12",
    "react-native-keychain": "3.0.0-rc.3",
    "react-native-splash-screen": "3.0.6",
    "react-navigation": "2.0.4",
    "reactotron-mst": "2.0.0-beta.2",
    "reactotron-react-native": "2.0.0-beta.2",
    "validate.js": "0.12.0"
  },
  "devDependencies": {
    "@storybook/addon-storyshots": "github:infinitered/addon-storyshots",
    "@storybook/react-native": "3.4.3",
    "@types/jest": "22.2.3",
    "@types/ramda": "0.25.28",
    "@types/react": "16.0.40",
    "@types/react-native": "0.55.12",
    "@types/react-navigation": "1.5.2",
    "@types/react-test-renderer": "16.0.1",
<EMAIL_ADDRESS>"0.11.0",
    "babel-jest": "23.2.0",
    "babel-plugin-transform-inline-environment-variables": "0.4.1",
    "babel-preset-react-native": "4.0.0",
    "ignite-ir-boilerplate-bowser": "^1.0.0-alpha.8",
    "jest": "23.2.0",
    "jest-preset-ignite": "0.5.0",
    "npm-run-all": "4.1.3",
    "patch-package": "5.1.1",
    "postinstall-prepare": "1.0.1",
    "prettier": "1.12.1",
    "react-dom": "16.2.0",
    "react-native-typescript-transformer": "1.2.5",
    "react-powerplug": "0.1.5",
    "react-test-renderer": "16.3.1",
    "rimraf": "2.6.2",
    "solidarity": "2.1.0",
    "tslint": "5.10.0",
    "tslint-config-prettier": "1.12.0",
    "typescript": "2.8.3"
  },
  "jest": {
    "preset": "jest-preset-ignite"
  },
  "rnpm": {
    "assets": [
      "./src/theme/fonts/"
    ]
  }
}

@mikecann you need to upgrade "@types/react-navigation": "1.5.2" to v2. I think you should reconsider ignite. The infinite-red team are very solid OSS maintainers and I can vouch for their design decisions. You should re-consider ignite. You can find me as @fadeojo on the infinite-red Slack.

thanks @fadeojo but its too late for us, we have already gone too far down the ejected CRA route now but we may reconsider for a future project. Thanks again.


Import path seems to be ambiguous

Hi!
import "github.com/sethvargo/go-envconfig/pkg/envconfig"
Such import contains almost duplicated parts - go-envconfig and envconfig at the end.
Have you thought about moving go code to the project root?
We will have more elegant and meaningful import path then.

Hey @mwf
Some folks brought this up on Twitter. I'm happy to move it, but I think that will break existing imports.

I think it's fine to do as long we assign a long lived version to the way it currently is (0.1?)

Done

Thanks!
It's great you decided to fix the import path :)
0.1 version is indeed young enough for such changes.


Add missing semicolon

Fixes lint error
Ironically the lint.ts file was failing when linted due to a missing semicolon 😄

/cc @RyanCavanaugh @DanielRosenwasser


Mad invalid password reconnects

I have this problem for a few days right now. So basicaly, when I start asf bots are entering steam with no problem, but after about 50 bots some accounts just go berserk and try to reconnect every second with Invalid password. Manual stop does not help. I guess it has something to do with captcha but this bot just won't stop.
Maybe it's kinda related to #46 ?
23.12.2015 11:54:33 [] INFO: OnConnected()  Connected to Steam!
23.12.2015 11:54:34 [!] WARNING: OnLoggedOn()  Unable to login to Steam: InvalidPassword
23.12.2015 11:54:34 [] INFO: OnLoggedOn()  Will retry after 25 minutes...
23.12.2015 11:54:34 [] INFO: OnDisconnected()  Disconnected from Steam!
23.12.2015 11:54:34 [] INFO: OnDisconnected()  Reconnecting...
23.12.2015 11:54:34 [] INFO: OnConnected()  Connected to Steam!
23.12.2015 11:54:35 [!] WARNING: OnLoggedOn()  Unable to login to Steam: InvalidPassword
23.12.2015 11:54:35 [] INFO: OnLoggedOn()  Will retry after 25 minutes...
23.12.2015 11:54:35 [] INFO: OnDisconnected()  Disconnected from Steam!
23.12.2015 11:54:35 [] INFO: OnDisconnected()  Reconnecting...
23.12.2015 11:54:35 [] INFO: OnConnected()  Connected to Steam!
23.12.2015 11:54:35 [] INFO: OnConnected()  Connected to Steam!
23.12.2015 11:54:35 [!] WARNING: OnLoggedOn()  Unable to login to Steam: InvalidPassword
23.12.2015 11:54:35 [] INFO: OnLoggedOn()  Will retry after 25 minutes...
23.12.2015 11:54:35 [] INFO: OnDisconnected()  Disconnected from Steam!
23.12.2015 11:54:35 [] INFO: OnDisconnected()  Reconnecting...
23.12.2015 11:54:36 [!] WARNING: OnLoggedOn()  Unable to login to Steam: InvalidPassword
23.12.2015 11:54:36 [] INFO: OnLoggedOn()  Will retry after 25 minutes...
23.12.2015 11:54:36 [] INFO: OnDisconnected()  Disconnected from Steam!
23.12.2015 11:54:36 [] INFO: OnDisconnected()  Reconnecting...
23.12.2015 11:54:37 [] INFO: OnConnected()  Connected to Steam!
23.12.2015 11:54:37 [!] WARNING: OnLoggedOn()  Unable to login to Steam: InvalidPassword
23.12.2015 11:54:37 [] INFO: OnLoggedOn()  Will retry after 25 minutes...
23.12.2015 11:54:37 [] INFO: OnDisconnected()  Disconnected from Steam!
23.12.2015 11:54:37 [] INFO: OnDisconnected()  Reconnecting...
23.12.2015 11:54:38 [*] INFO: OnConnected()  Connected to Steam!

#46 + most likely fixed already in 1.2.

23.12.2015 11:47:37 [] INFO: Main()  Archi's Steam Farm, version <IP_ADDRESS>
23.12.2015 11:47:38 [] NOTICE: CheckForUpdate() <> Local version: <IP_ADDRESS>
23.12.2015 11:47:38 [*] NOTICE: CheckForUpdate() <> Remote version: <IP_ADDRESS>

You didn't include bots name, so your log is pointless, also it's most likely Valve throttling connections.

Name was hidden by git, I guess. It's the same bot trying to reconnect. I don't understand why it doesn't wait for 25 minutes as it says.

Apparently steam sends extra OnDisconnected callback in addition to OnLoggedOn, that needs to be handled in special way.

Reproduced, fix pending.

Bot connected without fix! It took about an hout and ten minutes to log in. And madness in console have stopped. I wonder how it was able to connect after so many attempts.

It will eventually connect because Valve will eventually stop throttling, but it doesn't justify ASF trying to connect without waiting.
Fixed and released in 1.2.1

Should we switch to testing 1.2.1 then?

The fix doesn't matter for ASF reconneting loop issue which is #46, as it's totally other issue (actually 1.2 regression), but yeah always better to test on latest release (or pre-release).


Fix Windows symlink time information

On Windows, symlink does not work like on Unix, the OS think it is a real file like another. So for time operations, it only see changes on the symlink file and not the original one. That mean fileXtime functions get info about the symlink file too.
So if you make some changes in the original file, Puli will not seen anything if this file is register in the repository as a symlink. It work as espected for files in a symlink directory.

Thanks a lot @WedgeSama! :) Looks good!

Done.

Thanks, merged! :)

Done.

That's not what you removed...

You removed the entire line, instead of the single whitespace character on the end.

@GrahamCampbell I fixed the StyleCI issue in a separate commit.

Oh, that just that. I did not seen the whitespace.

Note that in future, you can just download and apply the diff styleci gives you.

Thank for the tips.


Add curator info to GET /collection/{collection_uuid} endpoint

@Bento007 commented on Mon Nov 15 2021
In order to support the new curator row displayed in the collection info, additional information will need to be return in in the GET /collection/{collection_uuid} endpoint. The information that needs to be added to the endpoint response are the curators email, first name, and last name. These fields are not stored in the data portal database. They are found in Auth0 using the foreign key Owner in the collections table. The owner of the collection is also the curator of the collection.
Approach

Retrieve the curator's information from auth0 using [Auth0's API(https://auth0.com/docs/api/management/v2#!/Users/get_users_by_id).
Add the following JSON into the return response from GET /collection/{collection_uuid} response.

{
  "curator_email": "string",
  "curator_name": "string"
}

Definition of Done

GET /collection/{collection_uuid} returns the collection curators email, last name, and first name.

@brianraymor  RE: https://github.com/chanzuckerberg/single-cell/issues/259#issuecomment-969694847
changed the response to be
{
  "curator_email": "string",
  "curator_name": "string"
}


[Spi_host/doc] updated documentation to reach V1 ready

This PR includes 3 commits.

Update test plan with test points for both V1 and V2
Update Coverage plan with functional coverage points
several test points were added - and the original ones are cleaned up.
I also removed the list of tests that were mentioned in each test point as none of these exist and therefore should not be listed
update dv plan so that should now be ready for V1 review
updated checklist to track the status of the documentation.

I also added the test plan to the hardware dashboard.
A PR will follow this with the Spi host environment and smoke test.
with approval of this document, I will consider the SPI_HOST documentation reviewed and approved for V1.
IP will stay at V0 until the checklist is complete and reviewed.

@weicaiyang thank you for your feedback I have updated to follow your comments.
@sriyerg do we need a formal doc review or is it ok to update the checklist for doc_reviewed?

All testplan reviews (meeting) so far have proven to be useful. Recently, the SW team has also requested to have more visibility into testplan reviews so that they have a better idea of what functionality is planned to be tested and what is expected to be working at the full chip at each stage. Please do schedule one, thanks!

All testplan reviews (meeting) so far have proven to be useful. Recently, the SW team has also requested to have more visibility into testplan reviews so that they have a better idea of what functionality is planned to be tested and what is expected to be working at the full chip at each stage. Please do schedule one, thanks!

@sriyerg I was never trying to avoid a review - just to get the doc V1 approved.
but as per agreement with @weicaiyang this was also reset to not started.
so I think we are all in sync!

All testplan reviews (meeting) so far have proven to be useful. Recently, the SW team has also requested to have more visibility into testplan reviews so that they have a better idea of what functionality is planned to be tested and what is expected to be working at the full chip at each stage. Please do schedule one, thanks!

@sriyerg I was never trying to avoid a review - just to get the doc V1 approved.
but as per agreement with @weicaiyang this was also reset to not started.
so I think we are all in sync!

Great, thanks!


Add bolna Voice AI support

Title
Bolna https://github.com/bolna-ai/bolna provides open source end to end Voice AI orchestration.
Description
Thinking of having this integration for multimodal voice capabilities

@prateeksachan if you would like to create a PR for this we can help you move it along. We may not get to voice for some time.


Enhance DX of plugin authors

To improve the DX of plugin author's we should provide a couple of changes to the current data structure.
Adoption of RunnerConfig

[x] ~#227 => https://github.com/flowup/quality-metrics-cli/issues/227#issuecomment-1806756227~

This will make it easier to work with different cwd and config location settings.
npx ../../dist/packages/cli collect --config=../../packages/cli/test/plugin-progress-bar.config.mock.ts --outputDir=../../tmp
Adoption of RunnerConfig

[x] #228.
clodes by #229

If a transform function is provided,
the output of a plugin is piped through the provided transform function after we read the plugin-output.josn.
{
  plugins: [
    {
      outputPath: "out.json",
      transform: (data: Record<string, any>): PluginOutput => {
          return {
            //...
          }
      }
    }
  ]
}

Adoption of runner type

[x] #230

Would get executed inside the cli and its return value is directly used int the report.
{
  plugins: [
    {
      runner: async (): void => {
         return // audit outputs
      }
    }
  ]
}

Implementation should be in different PRs.

@BioPhoton Can this be closed? All the referenced issues are done.


Fix opening named-pipe on Windows

Thanks for this useful crate.
Unfortunately opening the FIFO named-pipe stopped working for me on Windows after Rust 1.75 - this is a fix.

Thanks for the fix!


Feat/DBnewAnnotation2

Main improvements in this PR:
Continuation of #140, addressing issue #38:

This PR is mainly for adding new reactions and metabolites and GPR rules according to database new annotation.
We chose those new reactions based on new gene annotation. reactions are from different databases, for further information, please check: /ComplementaryData/databases/DBnewGeneAnnotation.tsv
addDBnewRxns.m is the function that we used to adding new rxns/mets/GPRs, in this function, it would call for quality control for each new reactions. Quality control includes: Mass/charge balance check and energy/redox production check.

Below are summary for each commit.

fix-data:changingGPR rules. We changed several GPR rules of existing rxns according to new gene annotation. We found several new rxns are already exist in the model, so we updated the GPR rules instead of adding them as new rxns (following the PR: #124)

feat-data:DB new annotated rxns/mets/genes. We added new mets/rxns/genes which are associated with database new annotated genes. In this commit, model was not updated.

fix-data:correct comps. Based on gene annotation for compartment in SGD and uniprot, we corrected compartments. DBnewGeneAnnotation.tsv was also updated to include compartment information.

feat-met:add new mets. In this commit, we added all new mets into the model. addDBnewMets.m was used to add new mets which are associated with database annotated new reactions.

fix:function name. Function name was changed from addDBnewMets to addDBnewRxn for latter use.

feat-rxn:add new rxns. New reactions were added into model using addDBnewRxn.m. In this function, it would generate a quality check for each reaction, including energy and redox production check and mass/charge balance check.

fix-met.prop:change met formulas and charges. Metabolites formulas and charges were corrected according to the energy/redox production results  and mass/charge balance results which were generated during adding new reaction function:addDBnewRxn.m. (No model change)

fix:rxns remove bad reactions. For those rxns which are unbalanced in database or contain metabolites which are too general and has no information related, we remove those rxns. (This commit is the first step of updating model). model = removeRxns(model,{'r_4213','r_4257','r_4259','r_4289','r_4290', ‘r_4182’}); and model = removeUnusedGenes(model) were used in this commit. Rxn ID mapping were based on the massbalance result.

feat:update model with new met formulas and charges. This commit is the second step.  We updated the model with formulas and charges. CheckBalanceforSce.m and CheckEnergyProduction.m were also modified for UpdateDBnewRxn.m.

feat:rxnprop. KEGG IDs for new rxns were added to model.

I hereby confirm that I have:

[X] Tested my code with all requirements for running the model
[X] Selected devel as a target branch (top left drop-down menu)
[X] If needed, asked first in the Gitter chat room about this PR

looks all good from my side (just added some formatting in the functions + corrected a grRule)
@hongzhonglu are all the changes from the old PR now integrated?


[Breaking change]: Graphics.GetContextInfo() is obsolete and marked as Windows only.

Description
Graphics.GetContextInfo() is a very costly API, so instead we added 2 GetContextInfo() overrides:
https://docs.microsoft.com/dotnet/api/system.drawing.graphics.getcontextinfo?view=dotnet-plat-ext-6.0#System_Drawing_Graphics_GetContextInfo_System_Drawing_PointF__
https://docs.microsoft.com/dotnet/api/system.drawing.graphics.getcontextinfo?view=dotnet-plat-ext-6.0#System_Drawing_Graphics_GetContextInfo_System_Drawing_PointF__System_Drawing_Region__
These new overrides calculate just the information needed based on what was requested by the caller depending on the override used, making it lower in allocations and time. Also, instead of returning an object (that represents an array of object containing the data) we are returning the structs needed to represent this data, making it easier for the consumer to access that data.
Version
6.0.0-preview4
Version
Other (please put exact version in description textbox)
Previous behavior
No warnings when compiling.
New behavior
When compiling on Windows:
warning SYSLIB0016: 'Graphics.GetContextInfo()' is obsolete: 'Use the Graphics.GetContextInfo overloads that accept arguments for better performance and fewer allocations.'

When compiling on non-Windows:
warning CA1416: This call site is reachable on all platforms. 'Graphics.GetContextInfo()' is only supported on: 'windows'.

Type of breaking change

[ ] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
[X] Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change
Graphics.GetContextInfo exists to allow WinForms to apply cumulative Graphics transform translation and clipping to the underlying HDC so that rendering via GDI has similar output. This method currently returns an object array of [ Region, Matrix ].  (Note that the Matrix is the current Transform with only the cumulative offset applied.)
This API is called many times during rendering of WinForms applications. Avoiding the array allocation would make a significant difference in rendering allocations. A much greater allocation reduction would be obtained if Graphics tracked if the .Clip and .Transform setters are ever accessed to allow an early out in the method logic.
WinForms also don't always need both values. System.Drawing can't calculate the clipping region without the offset, but it can calculate the offset without the Region. Making the Region optional will save significant overhead.
Recommended action
Use the overload that is most appropriate for the scenario from the new overloads replacing the obsolete API.
Feature area
Extensions
Affected APIs

System.Drawing.Graphics.GetContextInfo()

@safern Between these two breaking change articles, I think we can consider this to be documented already:

https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/system-drawing-common-windows-only
https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/obsolete-apis-with-custom-diagnostics

Thanks @gewarren didn't know we had an entry for the obsoleted type 😄


remove the misleading n_class information

Fix #15800
tf.estimator.DNNClassifier expects a [D0] or [D0, 1] labels, where expected_labels_dimension is not equal to n_classes.  Hence the error information below is totally misleading.

Classifier configured with n_classes=1. Received 4.

@ispirmustafa Hi, could you take a look. I think it is a trivial modification, however the information is really misleading.

What do I do if I'm getting this error?!


Update SimpleTcpServer.cs

applied a fix for my own issue; https://github.com/jchristn/SimpleTcp/issues/83

Thanks @sector13371 - merging now.  I'll also amend to include the other dictionaries where the entry may reside.

The server DataReceiver method should have been responsible for removing from the dictionaries.  I think what might have been happening is DisconnectClient disposed the client object before the DataReceiver was able to complete.
Would you mind giving v<IP_ADDRESS> a try and letting me know if this still works as expected on your side?  It looks good on mine.
NuGet: https://www.nuget.org/packages/SuperSimpleTcp/<IP_ADDRESS>
Commit: https://github.com/jchristn/SimpleTcp/commit/c1bd23e737c9e1379c91d75d40efb3c6dfc923fd

I've tryed it, now it works as expected now i'm having no issues with latest version. Thanks for that great library again.

Glad to hear. Thanks for finding the issue and letting me know, and also for your kind words!


The action 'Delete' is enabled for soft deleted blobs in new blob explorer

Storage Explorer Version: 1.31.0-dev
Build Number: 20230731.1
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 20.04/MacOS Ventura 13.5 (Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: From running test cases
Regression From: Previous release (1.30.2)
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Right click the blob container -> Click 'Open in React'.
Upload one blob -> Soft delete the blob.
Switch to 'Active and soft deleted blobs' -> Right click the soft deleted blob.
Check whether the action 'Delete' is disabled.

Expected Experience
The action 'Delete' is disabled.

Actual Experience
The action 'Delete' is enabled.

Verified this issue on the main build 20230801.4. Fixed. So we are going to close it.


Deploy to Github Pages

This PR creates a quarto website for the apl-study repo with a custom font that works with APL glyphs.  This is using Jeremy's latest APL notebook as of now.  cc @jph00
See page for website:  https://isaac-flath.github.io/apl-study/
You will need to go to settings -> pages -> and deploy to github pages using the docs folder after PR is accepted.
As @hamelsmu  is going to be working on making nbprocess work with other languages I thought getting particular challenges I ran into out there quickly would be helpful to be aware of.
Stuff maybe nbprocess or Quarto developments can help with:

I believe (please test) that in order to properly build the site you will have to install the APL font on your machine SAX2.ttf.  Ideally we could reference the ttf file and have nbprocess install automatically if needed rather than a separate step.  This is specified in the _quarto.yml file.
Quarto flags do not work well because #| is not seen as a comment in APL and other languages Quarto Fixed this.

Related to APL Font:

We used a specific font for APL (SAX2) as APL glyphs are unusual and don't work well with many fonts.
I changed the default theme in the _quarto.yml file.  When using the SAX2 font - headers do not stand out and it makes the posts hard to read.  I chose a similar theme where headers are a different color for readability.
The APL font doesn't look great with code blocks - future improvement could be to customize a theme to make code blocks look better.

I was able to improve a lot of the font issues that was having by setting only the code font to the APL compliant font as opposed to the full site font.  Didn't know that was an option, but is much better aesthetically!
That allowed the default theme headers to be clear and look better, so I reverted to the default theme with a minimal code background color.

I don't see any webfont embedding here - did I miss it, or is it not there? If it's not, then folks would need the font installed locally.
I think we should use CI to build the docs. People cloning the repo aren't going to want to have the whole Web site too!

Web font should be there now and is working - I didn't know what webfont meant and assumed it just meant a font downloaded from the web.  I used the styles.css for this since I do not think there is a Quarto configuration for this.
Working on CI to build the docs and hope to complete soon.  I have not used github actions before so it may take a couple of days, but I do want to figure this out!

@jph00 Done!

Web font is implemented via styles.css, putting it on code cells only.
CI builds docs now via deploy.yaml

That was quick!

Luckily I had good reference material due to fastkaggle and nbprocess :)
As a reminder you will have to go to settings -> Pages -> and set to gh-pages branch for the deploy.


Remove markdown images from appearing in description text

Markdown images and italics and stuff are showing up as plain text in the collection description.

These regex added removes markdown images from text before it's processed

Here is an example of italics sneaking through:

Printing image's description is a feature of strip markdown https://github.com/wooorm/strip-markdown/blob/77cc294226fe09ada6cee761a01b5d6839ba54a5/test.js#L104
The italic text looks like a bug. But I prefer sending a PR/open an issue to strip-markdown

@thangngoc89 just double checked. The italics was actually my fault =P
But the image thing is something I think we should remove. The left-over image text makes the snippet read incorrectly

@moox @thangngoc89 does this need to be done upstream at the strip-markdown dependancy?
I can't really think of a reason why someone would want "image description text" mixed in with actual text.

You see?

@DavidWells well, create a loader plugin that run the regex before description plugin. You can totally do this.

Will be in core. But we should add a test for this.

Now that I look at the tests. I'm wondering if "plain-texting" the description is ideal.
https://github.com/DavidWells/phenomic/blob/master/src/loader-plugin-markdown-init-head.description-property-from-content/__tests__/index.js#L50
# Why I love apples

Oranges are great but apples are better... This is my paragraph that says awesome stuff.

Turns into: "Why I love apples Oranges are great but apples are better... This is my paragraph that says awesome stuff." (bad grammar, improper english)
Aside from this example blog post being ridiculous... Do you think we should perhaps exclude headings/lists/tables etc from automatic descriptions?
Proposal:

strip some default tags (headings/lists/tables) from automated description but add option for people to include them?

Then again. This would be solved if people do their job of adding the 'description' frontmatter =P
I'm conflicted

Automatic description is a nice feature imo. At lease for meta tags.
Stripping eveything that is not a paragraph make sense to me.
If people need a custom behavior -> custom plugins.

If you want to remove heading, lists, tables, go with remark plugin, add a new remark plugin that strip all of those nodes before strip markdown.
@MoOx I see that we are parsing markdown twice with remark. Is it a good idea to merge generate body and description into 1?

Does strip-markdown need to change for this, and if so, how?

I haven’t touched that for a while. I should really clean that codebase.

Maybe this should be an option in strip-markdown indeed! Something like an "agressive" flag?

Images
Why is there image alt text if you don’t want people seeing/hearing/reading it?
Headings
The fact that
# Why I love apples

Oranges are great but apples are better... This is my paragraph that says awesome stuff.

Turns into...
Why I love apples  Oranges are great but apples are better... This is my paragraph that says awesome stuff.

Is not done by strip-markdown, I’m guessing it’s handled in phenomic somewhere?

@wooorm we rely on strip markdown for generating description from main content. See https://github.com/MoOx/phenomic/blob/2f46be51f1fdab5bc2d07323ce427faf1398cb46/src/loader-plugin-markdown-init-head.description-property-from-content/index.js#L26-L32
We don't have any custom behaviours here.

This behaviour is what I’m talking about, that’s done here.

Indeed, the lines replacing \n are a custom behavior weird enough to make the output weird.

But since the description is intended to be used in meta tag, having multiple lines doesn't make any sense.

Yeah, but this is causing issue in this case. Pretty tricky right?
Not sure what is the best to do. Probably stripping some elements like we discussed which will make sense in some context but not when inlined.

This is a matter of opinion and use cases. You may need both in the same project.

I don't see how someone will need an inlined text like this: "Title alt_image Hi there this is a new post..."

I don't see how someone will need an inlined text like this: "Title alt_image Hi there this is a new post..."

On that I agree

Up here. Should we remove everything that is not just normal text for the desc?

I am closing this PR as for now

transform markdown plugin (in master) does not create a description by default as many people where not happy with it (and even confused)
the current PR is doing a change in a file that does not exist.

We will revisit this later if we reimplement this, but I guess for now this should be handled in user land.


BaseOAuth::sendRequest  - Can't send raw content

Problem is with BaseOAuth and it's methods api() and sendRequest().
Everything was ok until I tried to send clean raw PATCH request with json in it.
sendRequest() allows only array as input params and my content can't be passed.
Also I can't override CURLOPT_POSTFIELDS with setCurlOptions().
If I set

curl_setopt( $curlResource, CURLOPT_POSTFIELDS, '{"message":"raw json"}' );

inside BaseOAuth::sendRequest with other curl_cetopt -  it works.

Same as #6961

This is solved with this pull request https://github.com/yiisoft/yii2-authclient/pull/33


Instead of going to the Discogs search results scene when tapping an iTunes library artist, pop up a disambiguation list

I should also keep track of which Discogs artist the user selected so that the disambiguation doesn't have to be displayed the next time.

Done.


Clean up request validations

Current problem: When POST request is sent, kangal first runs httpValidator method which uses govalidator. But after this we validate all the fields one more time with custom validation methods.
This PR is an attempt to remove duplicated validations in order to reduce dependencies and have error messages in the same format for all the request fields.

Codecov Report

Merging #172 (90142f9) into master (aab6339) will increase coverage by 0.26%.
The diff coverage is 64.28%.

@@            Coverage Diff             @@
##           master     #172      +/-   ##
==========================================
+ Coverage   59.80%   60.06%   +0.26%
==========================================
  Files          35       35
  Lines        2458     2454       -4
==========================================
+ Hits         1470     1474       +4
+ Misses        883      878       -5
+ Partials      105      102       -3

Impacted Files
Coverage Δ

pkg/proxy/request.go
80.54% <64.28%> (+3.82%)
: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 aab6339...90142f9. Read the comment docs.


Simple overlay

Merging this to pivot.
Working through supporting multi-channel signed distance fields made it clear that I need to evolve the existing rendering pipeline before layering on additional complexity.

Chose the wrong branch...


fix(CI): prevent the e2e test from running on  0.XX-stable branches

Summary
Because of the usual ✨dark magic✨ that we do 'cause RN is not a proper monorepo (usual link https://github.com/react-native-community/discussions-and-proposals/pull/480), one of the side effects is that test_js and test_js_prev_lts  insta-crash whenever they run in a -stable branch because of the run_e2e job, that runs verdaccio and verdaccio needs the workspace, but the workspace is not there because of the aforementioned ✨dark magic✨
This PR fixes that by not allowing said command to be run when we are in 0.XX-stable branches. (TIL that under the hood CircleCI wants Java regex)
Once merged, we can cherry-pick in 0.71-stable.
Changelog

[INTERNAL] [FIXED] -  prevent the e2e test from running on  0.XX-stable branches
Test Plan

I used this PR for testing: https://github.com/facebook/react-native/pull/35665
here's a screenshot of when things work (no E2E command run):

here's how it looks when they don't (E2E runs and crashes):

You can also verify that the condition is correct by throwing this sample code in an online Java ide:
import java.util.regex.*;

public class Main
{
    public static void main(String[] args) {
        System.out.println(Pattern.matches("0.[0-9]{2}-stable", "main"));//false
        System.out.println(Pattern.matches("0.[0-9]{2}-stable", "0.71-stable"));//true
        System.out.println(Pattern.matches("0.[0-9]{2}-stable", "just-a-test-with-stable"));//false
        System.out.println(Pattern.matches("0.[0-9]{2}-stable", "just-a-test-with-stable-test"));//false
    }
}

Doesn't this mean that we don't run JS tests at all in the stable branch? 🤔
If that's the case, what about changing the e2e script so that, if there is a workspace entry in the package.json, we use that. Otherwise we can pass the path to the packages folder and the script can consider all the folder in that path as packages to try and publish.
By doing that, Verdaccio will work as if it was a workspace and we could retain JS test on stable as well.
WDYT?

Doesn't this mean that we don't run JS tests at all in the stable branch? 🤔

No, it's only a logical condition for run_e2e which is here https://github.com/facebook/react-native/blob/main/.circleci/config.yml#L259 and that corresponds to https://github.com/facebook/react-native/blob/main/scripts/run-ci-e2e-tests.js which is a script that we should completely rework since the "E2E" part of it is some old smelly code that basically doesn't do anything useful. But for some reason the Verdaccio part was added here so we can't just entirely remove this script and CircleCI command.

Ok, so we skip only the e2e test which are not providing value, right now.
Then, that's fine.

that runs verdaccio and verdaccio needs the workspace, but the workspace is not there because of the aforementioned ✨dark magic✨

😢

So, the e2e part is kind of misleading, but the unique bit about this script is that it runs tests against a newly initialized app. E.g. it is where we test that a new app typechecks.

The reason Verdaccio is used here is so that tests can be run simulating a real installation from an npm registry. There is a seprate bit using file copies, but it does some surprising stuff which can cause some tests to hang because of differences compared to a real app init.

TLDR: The script does provide some unique coverage. So, I am a little weary of removing this, unless it is needed to unblock the release (then maybe we could just disable in the stable branch)?

Update on all of this - I've spent a bit more time and I wanted to share the learnings:

in main branch, we don't need this change because of @hoxyq's work. Great stuff there. I'm going to close this PR then.
For 0.71, we have 3 alternatives:

we don't do anything (good enough, but some small JS/typing issues might go undetected)
we merge a variation of this PR, I've made that PR here: https://github.com/facebook/react-native/pull/35681
we figure out a way to port @hoxyq's work in 0.71-stable. I did a rough attempt to see what would happen here: https://github.com/facebook/react-native/pull/35680 the main issue is that we can't cherry-pick cleanly https://github.com/facebook/react-native/commit/7f29357c7c7dcbf4b59bb072db613169944ba2cf but it needs the other commits from him, and in particular https://github.com/facebook/react-native/commit/83afdafae4d465ab2949439ca261bf00bae44f3f which I'm pretty sure we don't want/can't have in the 0.71 branch since it's pre-all the refactorings and renaming happening in main. So it'd basically have to be a proper PR for 0.71 only, so might not be worth pursuing.

We can pick this up in Jan btw, and fix for 0.71.1, no rush.


Removed ClusterImageSet from BootstrapIgnition

ClusterImageSet is redundant in BootstrapIgnition as it's already available as part of the unconfigured.ign.
Also, adding our custom ClusterImageSet causes a version mismtach error when using the latest config-image API (which is used in dev-scripts).

/cc @filanov


Backport "Fix Closure span assignment in makeClosure" to LTS

Backports #15841 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-20295.
Reference


Error: cannot check server release: cannot find neither /etc/uyuni-release nor /etc/susemanagere-release

mgradm upgrade podman command ends in an error Error: cannot check server release: cannot find neither /etc/uyuni-release nor /etc/susemanagere-release
The server can be revived by going in to the container and running commands to start postgresql and spacewalk-service.
The upgrade seems to have worked but this isn't the correct outcome.
Upgrade was from 2024.05 to 2024.07 on podman
Container tools are up to date, from EL_9 repo.
mgradm upgrade podman
12:23PM INF Welcome to mgradm
12:23PM INF Executing command: podman
12:23PM INF Cannot find RPM image for registry.opensuse.org/uyuni/server:latest
12:23PM INF Running podman pull registry.opensuse.org/uyuni/server:latest
Trying to pull registry.opensuse.org/uyuni/server:latest...
Getting image source signatures
Copying blob 82f4a02bb4a5 done   |
Copying blob e29629bb36a2 done   |
Copying blob 490ea0c3696a done   |
Copying config 1ec7fabb91 done   |
Writing manifest to image destination
1ec7fabb91d83438fa8c6750abffbfe752fa30a6fd0fb811491edd8bcb09a1b9
Error: cannot check server release: cannot find neither /etc/uyuni-release nor /etc/susemanagere-release

This seems to me a timing issue. I checked released container image and /etc/uyuni-release is present. So this seems like check for it is happening too soon and container is not yet completely started. This should be fixed by https://github.com/uyuni-project/uyuni-tools/pull/386
This fix is not yet included in your version (head 311105e I see in another issue), but will be in next released uyuni-tools.


Dependency: html-minifier REDoS vulnerability

Describe the bug
31 high severity vulnerabilities
html-minifier  *
Severity: high
kangax html-minifier REDoS vulnerability - https://github.com/advisories/GHSA-pfq8-rq6v-vf5m
To Reproduce
Steps to reproduce the behavior:

Init new project and install npm i mjml
check npm audit
result will be 31 high severity vulnerabilities

Expected behavior
found 0 vulnerabilities
Environment:
nodejs v20.11.1 + mjml 4.15.3

Confirmed.
This needs a dependency cleanup asap. I work with mjml on most of my projects and this vulnerabilities are not good to keep.
Maybe html-minifier will patch the vulnerability on their end and MJML can follow up with it and patch it here.

html-minifier seems to be unmaintained. https://github.com/kangax/html-minifier/issues/1135

Closing as duplicate of #2589
For what it's worth : this vulnerability isn't anything new. We started to check alternatives as html-minifier doesn't seem to be updated anymore :

switch to a different package html-minifier-terser is way too big as a dependency to be worth considering, htmlnano seem to be the best candidate
forking html-minifier as mjml-html-minifier and patch it ourself : I think that could work too as we can just remove unused feature for MJML. I'm nowhere near an expert level in tokenizer so I don't know how to properly patch out the reDos vulnerability that html-minifier has.
removing completely minifying as an option and let users pipe the result in w/e library: not ideal IMO as some email doesn't work in some email clients when not properly minified.

You can check https://www.npmjs.com/package/mjml/v/5.0.0-alpha.1 this version remove html-minifier and js-beautify. It relies on htmlnano and prettier instead.
➜  mjml-5 yarn audit
yarn audit v1.22.22
0 vulnerabilities found - Packages audited: 224
➜  mjml-5 npm audit
found 0 vulnerabilities

this vulnerability isn't anything new

Ok, great but the current version 4-15-3 explodes the terminal 💥

Is there feature parity between mjml-5 and mjml@4-15-3?


TypedArray.copyWithin polyfill

copywithin seems really fast, but apparently some TypedArray features, and especially copyWithin isn't currently supported on essentially any mobile browsers: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray/copyWithin
Is this automatically transpiled? Or should you provide a polyfill?
https://github.com/zloirock/core-js#ecmascript-typed-arrays

Or just use babel with rollup and distribute that?
https://github.com/rollup/rollup-plugin-babel

Instead of using copyWithin, just fill the array from the start, without gaps, and take a contiguous view up to the last index
e.g. tiny example:
x = [[1, 2], [3, 4], [0, 0], [5, 6]]
var line = new Float32Array(8)
var coordLength = 2;
var index = 0
for (var segment of x) {
  if (segment[0] === segment[1]) {
    continue
  }
  line.set(segment, index * coordLength)
  index++
}
line.subarray(0, index * coordLength)


convert functional to class components

It is a bit hard to understand what it has been changed in the UI, if all parts are there, but I guess there is no feature change here, just a refactoring.

Well nothing changed in the ui, and nothing changed in general, just instead of functions we use classes for the components.


Fix #1256: AuthCode w/ PKCE not supported for popups

An attempt to fix #1256. See the issue for context, especially https://github.com/IdentityModel/oidc-client-js/issues/1256#issuecomment-737196107

Closing for now, since it seems to be working. If it's not, please let me know.

Closing for now, since it seems to be working. If it's not, please let me know.

It's NOT working! Please revisit this.

It's NOT working! Please revisit this.


Missing entry in /etc/hosts

When running any sudo command, there's this line in the output:
user@fc1574dff44b:~$ sudo ls
> sudo: unable to resolve host fc1574dff44b: Name or service not known

This was caused by network config during image building — for now we changed this here https://github.com/e2b-dev/infra/blob/main/packages/env-build-task-driver/internal/env/rootfs.go#L293