UnsupportedApiVersion error when giving some different content type

We are using 4.1.1 version of APiVersioning and 3.1 version of Asp.NetCore
I have a controller with an action which accepts only Content-Type "application/merge-patch+json"
[HttpPatch("{id}")]
[Consumes("application/merge-patch+json")]
public async Task<Object> CreateObjectAsync(
..
)
{
..
..
}

So while quering for the given api with  content type "application/merge-patch+json".. It works fine
but quering for some other valid content type for example "application/json" gives 400 bad request and
following output:
{
    "error": {
        "code": "UnsupportedApiVersion",
        "message": "The HTTP resource that matches the request URI 'https://bb-df-wus2-1.farmbeats-dogfood.azure.net/farmers/pra88888m?api-version=2021-03-31-preview' does not support the API version '2021-03-31-preview'."
    }
}

and on using APiVersioning version as "5.0.0"
I got the same response with different status code.
Can you please help me with this?

Are you able to show at least the skeleton of the rest of your controller and perhaps the configuration setup? Which route/action is giving you trouble? You seem to indicate that the one you've shown works. If no media types match, I would have expected HTTP 406 (Not Acceptable). A response will contain the same error, but may be HTTP 400 or 405 depending on whether the HTTP method is supported by any version.
Repros always the best, but with a little more information I can probably figure out what's happening here.

@commonsensesoftware
        [HttpPatch("{Id}")]
        [Consumes(CommonConstants.ApplicationMergePatchContentType)]
        [ProducesResponseType(typeof(Models.Entities.Object), StatusCodes.Status201Created)]
        [ProducesResponseType(typeof(Models.Entities.Object), StatusCodes.Status200OK)]
        [ProducesDefaultResponseType(typeof(ErrorResponse))]
        public async Task<ActionResult<Models.Entities.Object>> CreateOrUpdateObjectAsync(
            [Required][ValidateId(CommonConstants.MaxIdLength, MinIdLength = CommonConstants.MinIdLength)] string Id,
            [FromBody] Models.Entities.Object farmerUpdate,
            CancellationToken cancellationToken)
        {
        }

This is the structure of the controller . One of the headers "Content-Type" which is set in this attribute on the controller  [Consumes(CommonConstants.ApplicationMergePatchContentType)] and is made to accept value application/merge-patch+json ...but when we give some other value in content type header .. it gives error api version not supported (400 bad request).. let me know if you need any other information?
We want the api versioning library to not throw unsupported error so that we can error out properly.

This provides a little more about the action, but it doesn't provide any information about the controller or application setup. I still have a number of questions.

Are you versioning by media type?
a. The URL in error message suggests you're versioning by query string; it's possible you're using both methods
b. Your comments suggest you're versioning by media type, but perhaps you're not
I think you're saying that PATCH with application/merge-patch+json works, but not with application/json.
a. It appears you are trying implement RFC 7386
b. You've only mapped application/merge-patch+json with the ConsumesAttribute, so I would expect application/json to fail
c. I would expect HTTP 415 (Unsupported Media Type) if application/json is in the Content-Type header for this action
d. Like media types, the API version is a constraint used to filter down candidates. It's possible, things are short-circuit before other failures have a chance to execute. This could mean no candidates were found before HTTP 406 or 415 was evaluated.

"We want the api versioning library to not throw unsupported error so that we can error out properly."

I'm not 100% sure what that means. API Versioning has very few errors it throws. It will, however, return client errors - without exception - for invalid requests. There are ways to change the error response; for example, a different status code, message, or payload. It's unclear if that's what you mean by "...error out properly." I want to make sure I understand your scenario before I send you down that path.

Okay .. @commonsensesoftware  To simplify.. Let me give you the exact scenario ..I tried the same on one of your examples .. for the sample used for api-versioning (https://github.com/microsoft/aspnet-api-versioning/tree/master/samples/aspnetcore)..
I appended Consumes attribute over one of the post APis in OrdersController
/// <summary>
        /// Gets a single order.
        /// </summary>
        /// <param name="id">The requested order identifier.</param>
        /// <returns>The requested order.</returns>
        /// <response code="200">The order was successfully retrieved.</response>
        /// <response code="404">The order does not exist.</response>
        [HttpGet( "{id:int}" )]
        [Produces( "application/json" )]
        [Consumes( "application/merge-patch+json" )]
        [ProducesResponseType( typeof( Order ), 200 )]
        [ProducesResponseType( 404 )]
        public IActionResult Get( int id ) => Ok( new Order() { Id = id, Customer = "John Doe" } );

Now some of the answers to your questions:
1.There is versioning only on string and not on any mediaType/ContentType.
2. This should accept only "application/merge-patch+json" Content type and error out with HTTP 415 (Unsupported Media Type)with application/json is in the Content-Type header for this action.
Outputs:

On giving content type "application/merge-patch+json" and version "1.0" it works fine and gives the output
{
"id": 42,
"createdDate": "2021-03-05T00:00:00+00:00",
"customer": "kkk"
} with status code 201 Created

2. Issue : But on giving content type "application/json" and same version "1.0"
{
"error": {
"code": "UnsupportedApiVersion",
"message": "The HTTP resource that matches the request URI 'http://localhost:5000/api/Orders' with API version '1.0' does not support HTTP method 'POST'.",
"innerError": null
}
} with Status Code 405 Method Not Allowed.
It should not have errored out by api-versioning library as the version is correct and it should others contents types. I hope this examples gives you more context about controller and application-setup.

@commonsensesoftware I verified its working without versioning. It gives proper error 415 UnSupportedMediaType. You can verify it once on some sample controllers.
Yes, We want "application/merge-patch+json" according to some guidelines. I'll reconfirm on Patch + application/json thing. But We want to support "application/merge-patch+json" and we might need any other content type also for that matter for any scenario. We shall try to fix this to get unblocked early.

Thanks for confirming. I'll see what I can find.

@commonsensesoftware any updates?

My opinionated dogma aside 😉 , I'm not able to repro your scenario. I've tried against the latest 5.0.0 release and back to 4.1.1. I'm not sure if you have a particular reason to be back on 4.1.1, but 5.0.0 will have the latest features and fixes. 5.0.0 also multi-targets so you can still use .NET Core 3.1.
I tried following all the points from the discussion, but clearly our streams are crossed. You first mentioned putting [Consumes( "application/merge-patch+json" )] on a GET operation, which I would not expect to work because they don't (or shouldn't) accept any content. I'm not completely sure if that can be made to work. You also mentioned putting it on the OrdersController in a sample project. Based on what I saw, I assume the sample you are referring to is in the Swagger sample and you made the changes to the 1.0 version of the controller.
I saw things work as expected. If you want to support multiple media types, then you have to add them all:
/// <summary>
/// Places a new order.
/// </summary>
/// <param name="order">The order to place.</param>
/// <returns>The created order.</returns>
/// <response code="201">The order was successfully placed.</response>
/// <response code="400">The order is invalid.</response>
[HttpPost]
[MapToApiVersion( "1.0" )]
[Produces( "application/json" )]
[Consumes( "application/json", "application/merge-patch+json" )]  // ← list all supported media types
[ProducesResponseType( typeof( Order ), 201 )]
[ProducesResponseType( 400 )]
public IActionResult Post( [FromBody] Order order )
{
    order.Id = 42;
    return CreatedAtAction( nameof( Get ), new { id = order.Id }, order );
}

With this in place, the Swagger UI will show both media types and they both succeed with 201. These are the only changes I made in the sample project.

ASIDE: More dogma, but application/merge-patch+json - by spec - is only supposed to be used with PATCH, but it seems ASP.NET doesn't care. It worked with POST just fine. Something to consider in your final solution.

At this point, it's not clear to me how our two setups are different. If you're able to take a sample project, repro the issue, and drop a copy of it here, that will go a long way to making sure I'm on the same page as you.

Hiii, @commonsensesoftware I tried again and can still see the issue, let me help you repro the issue in OrdersController of https://github.com/microsoft/aspnet-api-versioning/tree/master/samples/aspnetcore

I tried on both versions 5.0.0 and 4.1.1
You can repro this issue by using SwaggerSample 1.0 version
a. Use Post API of OrdersControllers(correction: not get, that was a typo)
b. Add [Consumes( "application/merge-patch+json" )] to the api (not application/json, I want to support only 1)
c. Try hitting the API from postman with Content-Type header set as "application/json". (Swagger automatically handles this so you dont the see the issue there)

/// <summary>
        /// Places a new order.
        /// </summary>
        /// <param name="order">The order to place.</param>
        /// <returns>The created order.</returns>
        /// <response code="201">The order was successfully placed.</response>
        /// <response code="400">The order is invalid.</response>
        [HttpPost]
        [MapToApiVersion( "1.0" )]
        [Produces( "application/json" )]
        [Consumes( "application/merge-patch+json" )]
        [ProducesResponseType( typeof( Order ), 201 )]
        [ProducesResponseType( 400 )]
        public IActionResult Post( [FromBody] Order order )
        {
            order.Id = 42;
            return CreatedAtAction( nameof( Get ), new { id = order.Id }, order );
        }

Expected behaviour: It errors out saying media type is not correct(Unsupported media Type)
Reason : Only "application/merge-patch+json" is supported.
Actual Behaviour: It errored out with 405 Method not allowed saying api version is not correct(I didnot even change the api-version)
{
    "error": {
        "code": "UnsupportedApiVersion",
        "message": "The HTTP resource that matches the request URI 'http://localhost:5000/api/Orders' with API version '1.0' does not support HTTP method 'POST'.",
        "innerError": null
    }
}

You should be able to repro the issue with this. Let me know if you have any queries.
Thanks

I'll reiterate that application/merge-patch+json is only meant for the PATCH method. Here's what I added:
/// <summary>
/// Updates an existing order.
/// </summary>
/// <param name="order">The order to update.</param>
/// <returns>The created order.</returns>
/// <response code="204">The order was successfully updated.</response>
/// <response code="400">The order is invalid.</response>
/// <response code="404">The order does not exist.</response>
[MapToApiVersion( "1.0" )]
[HttpPatch( "{id:int}" )]
[Produces( "application/json" )]
[Consumes( "application/merge-patch+json" )]
[ProducesResponseType( 204 )]
[ProducesResponseType( 400 )]
[ProducesResponseType( 404 )]
public IActionResult Patch( int id, [FromBody] Order order ) => NoContent();

I then tested it with the HTTP REPL instead of the Swagger UI. These are from the default endpoint http://localhost:5000/api> in the REPL.
Defaulting to application/json
patch orders/42?api-version=1.0 -c "{"customer":"Bob Smith"}"
HTTP/1.1 415 Unsupported Media Type
Content-Length: 0
Date: Thu, 24 Jun 2021 15:45:43 GMT
Server: Kestrel

Specifying application/merge-patch+json
patch orders/42?api-version=1.0 -c "{"customer":"Bob Smith"}" -h "Content-Type:application/merge-patch+json"
HTTP/1.1 204 No Content
api-deprecated-versions: 0.9
api-supported-versions: 1.0, 2.0, 3.0
Date: Thu, 24 Jun 2021 15:46:12 GMT
Server: Kestrel

This is exactly what I would expect to have happen. Perhaps something is wrong in your PostMan setup?

@commonsensesoftware
I looked into this issue and I think it is either DotNet core routing issue or API versioning library issue.
So I have created 3 different PRs to see how API versioning lib  is behaving according to changes.
Setup-1

V1 Orders controller has PATCH method with attribute [Consumes("application/merge-patch+json")]
V2 Orders controller has PATCH method with attribute [Consumes("application/merge-patch+json")]

PR: https://github.com/BlackRider97/aspnet-api-versioning/pull/1
It is working correctly as expected.
Case-1 Correct content type -H "Content-Type: application/merge-patch+json"
Expected status code: 201
Found status code: 201
✅
Case-2 Incorrect content type -H "Content-Type: application/json"
Expected status code: 415 Unsupported Media Type
Found status code: 415 Unsupported Media Type
✅
Setup-2

V1 Orders controller has PATCH method with attribute [Consumes("application/merge-patch+json")]
V2 Orders controller has PATCH method with attribute [Consumes("application/json")]

PR: https://github.com/BlackRider97/aspnet-api-versioning/pull/2
It is NOT WORKING AT ALL as expected.
Case-1 Correct content type -H "Content-Type: application/merge-patch+json"
Expected status code: 201
Found status code: 405 Method Not Allowed
❌
Case-2 Incorrect content type  -H "Content-Type: application/json"
Expected status code: 415 Unsupported Media Type
Found status code: 405 Method Not Allowed
❌
Setup-3

V1 Orders controller has PATCH method with attribute [Consumes("application/merge-patch+json")]
V2 Orders controller has PATCH method without any Consumes attribute

PR: https://github.com/BlackRider97/aspnet-api-versioning/pull/3
It is NOT WORKING PARTIALLY as expected.
Case-1 Correct content type  -H "Content-Type: application/merge-patch+json"
Expected status code: 201
Found status code: 201
✅
Case-2 Incorrect content type -H "Content-Type: application/json"
Expected status code: 415 Unsupported Media Type
Found status code: 405 Method Not Allowed
❌
Now @PranjaliSoni  is talking about setup-3. For her it is not working as expected when wrong content type is passed.

@BlackRider97, @PranjaliSoni  thanks for the updated information; this is useful. This was a very deep investigation. Lucky you, you're the winner of two bugs!
The first bug is in API Versioning and will happen when:

There are multiple candidates for a route template
The actions specify different media types
The only reason for the lack of a match is media type

The reason you get 405 instead of 400 is because there is other matching candidates. It is possible that methods are added or removed between versions, which is the reason for 405 (e.g. PATCH isn't being found, when it should be).
It should be possible to properly report 415 instead of 405, but unfortunately I'm not currently able to fix it due to a bug I've discovered (and reported) in dotnet/aspnetcore#33865. Something in the routing system is filtering out possible candidates. The lack of all the candidate information is preventing me from properly detecting 415 across API versions (which is this special case).
The possible, temporary workaround is:

Use heterogenous media types across your controllers
Explicitly return 415 if a request reaches a controller that shouldn't support it; an action filter to help here
If you need OpenAPI/Swagger support, you'll need some type of filter to fix-up (e.g. remove) media types on APIs that don't actually support it

This is a yucky, lame solution, but I'm blocked up stream. I suspect it may take weeks or even months for the ASP.NET team to fix this issue. We'll have to see how much of a priority they make it. You might be able to flex your muscle on their repo. The linked issue illustrates how to repro the issue, even without API Versioning.

I just wanted to circle back around and provide a quick update on this issue. After a lot of researching, I can confirm that this is indeed a bug and a misunderstanding (on my part) about what extensions to the routing system are necessary. I've made the necessary changes, which you can now find in the new main branch. Expect the fix to be available in the next major release (6.0). I'm very hesitant to backport this change to 5.x patch because it results in a behavioral breaking change to routing; regardless, of the method that you use.
On a positive note, 415 will be properly reported without needing to change the error response status code. If you version by media type, and only by media type, then clients will receive 415 when there's no match.
The code should be ready if you want to play around with it. I'm actively working getting things setup to publish new packages.

The Preview 2 release available and you can pick up the changes from the new package Asp.Versioning.Mvc. While I could make the change in 5.1, I've decided not to because it results in a behavioral breaking change that will likely not be obvious.
I've lifted this use case into the test suite. I believe it will now do what you expect in a more consistent manner for 404, 405, and 415.  If you're able to confirm that would help close this issue out.
The latest examples can be found here.

6.0 has been officially released. It contains the official, final release of the changes discussed throughout this thread. You discovered a pretty big hole in the implementation, but a lot of good things came of it. Thanks for reporting it. If you continue to have any issues in 6.0, feel free to comment or we can reopen the issue. Thanks.


Remove package-lock.json

@flacatus Hi, we need to remove the package-lock.json, otherwise snyk scans do not have proper results and we are getting this: https://support.snyk.io/hc/en-us/articles/360000912457-Out-of-sync-manifest-lockfile-in-the-project?_gl=11w8czvo_gaMjA4OTA3NjQ0MS4xNjcyODE2MzMx_ga_X9SH3KP7B4*MTcxMjU2MDQ1MS4xNS4xLjE3MTI1NjA0NjkuMC4wLjA.


Update copyright comments

Within in the cmd/... packages you don't have a copyright email set up.
 // Copyright © 2018 NAME HERE <EMAIL ADDRESS>

Thanks. Fixed.


Flush cache on upgrade

Questions
Answers

Description?
We changed a logic of availability logic a bit (https://github.com/PrestaShop/ps_facetedsearch/pull/883#issuecomment-1648160837) and it would be good to flush block cache, users could see old values before their next CRON cleaning run.

Type?

BC breaks?

Deprecations?

Fixed ticket?

How to test?
Does not need QA - the same line of code is used when upgrading to previous version - https://github.com/PrestaShop/ps_facetedsearch/blob/dev/upgrade/upgrade-3.12.0.php.

This change is

Hi @Hlavtox
Thank you for your PR, it works on 8.0.5 and 8.1.1 :heavy_check_mark:
But when I put it in <IP_ADDRESS>, the availability order is inverted as you can see :
Untitled_ Jul 31, 2023 3_39 PM (1).webm
Do you know how to correct this ?
Waiting for your feedback

Discussed with @AureRita, merging. 👍


add new generic drivers

@ibuildthecloud

unrelated test failed.

@cjellick Rebased and Repushed. Once again unrelated test failure.

Where'd my LGTM go?
Anyway, LGTM. Ping @alena1108 or @sonchang to make it official.

LGTM


Ensure first blob is written to output file first (MP4 streaming issues)

The Issue
Per discussion with @jackrobison, it's possible that the 2nd (or others) blob is written to the output file before the first one, relevant code: https://github.com/lbryio/lbry/blob/e50ac69358bda507a7acd298ebe767cf7cba438e/lbrynet/daemon/Downloader.py#L64
This causes intermediate issues when streaming MP4s which have metadata required to start the stream in the first few bytes. If the 2nd blob is written first, it will get stuck on "waiting for metadata" until you leave the claim and come back (https://github.com/lbryio/lbry-desktop/issues/754).
Is there any downside to waiting for the first blob to download before writing the file?
Notes from chat:
jack
what it does now:
1. `get` request comes in
2. resolve the uri, throw error if it doesnt resolve to a stream
3. download sd blob, return sd timeout if fails
4. start downloading stream from many peers
5. as soon as a peer starts to send the first blob file to us, return the result from `get`
6. blob finishes (or maybe even fails before finishing) after we've returned from `get`. blob file on disk is removed on fail or saved and decrypted and added to the output file in the downloads folder

jack
just checked, there are edge cases the way it is that could break this
jack
it's _supposed_ to block on the first data blob being completed
jack
it actually blocks on _any_ data blob being completed
jack
if it blocks on the first one that should be very close to the time it's decrypted and written to the output file

Actual behaviour
Tell us what happens instead
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Repeat of partial notes from lbrio/lbry-desktop :

...

The media player begins reading from disk with no awareness of the completion of blobs. See https://github.com/lbryio/lbry-desktop/blob/e8aa67bf7eefeb778617403a89d593081cb62b2d/src/renderer/component/fileViewer/internal/player.jsx#L165
The current implementation of the daemon does not guarantee that the blobs are written in sequential order; detecting which ranges of data in the written file are available is difficult and not reliable. See https://github.com/lbryio/lbry/issues/1342
...

Here's an example of this in action with blob mirroring below. Blobl  05a5c9bc781c5310  (blob 3) is downloaded before blobs 1 and 2. Not sure if it was written to the output file before hand, but based on the anaylsis @jackrobison did before, it's possible.
blob data:
"blobs": [{"length": 2097152, "blob_num": 0, "blob_hash": "db03b8161a1aecd4d04b730891bd44ec4b56897f8add5d7409b8da2cb6ec758e56b21ca28214da83fbdb73bef5c30fd4", "iv": "838d37749d8a3cda38f9cc751ee08904"}, {"length": 2097152, "blob_num": 1, "blob_hash": "f4138a6d2e96eb21ba3ae2bfee803e8c28d13a58938f12872dc2096d137de4cfc149e580e883a0c1dc6221c3760402c5", "iv": "27d9f201f6708f0fc6809ee902a673a8"}, {"length": 2097152, "blob_num": 2, "blob_hash": "05a5c9bc781c53100027bf39fcfd7fd947bf29e1a6d70b5c97e0cc570162398683e8996f6f9edcfecedde15fa8951386", "iv": "29c66d18156a5b26220e08a9bc38ea6c"}, {"length": 2097152, "blob_num": 3, "blob_hash":
download:
2018-08-14 11:23:57,594 INFO     lbrynet.daemon.Downloader:96: Download lbry://bloodstained-curse-of-the-moon-review status changed to initializing
2018-08-14 11:23:57,595 INFO     lbrynet.daemon.Downloader:96: Download lbry://bloodstained-curse-of-the-moon-review status changed to downloading_metadata
2018-08-14 11:23:57,746 INFO     lbrynet.core.HTTPBlobDownloader:70: Mirror completed download for 6fc2cb3ac504fc9628157fc7d58c4437705420c76b79d91409b71628911d57eb22a1c7dac4ee6d680672219629d4276e
2018-08-14 11:23:58,851 INFO     lbrynet.daemon.Downloader:191: Downloading lbry://bloodstained-curse-of-the-moon-review (6fc2cb) --> C:\Users\SoloDolo\Downloads\lbry downloadstest\bloodstained-curse-of-the-moon.mp4
2018-08-14 11:23:58,852 INFO     lbrynet.daemon.Downloader:96: Download lbry://bloodstained-curse-of-the-moon-review status changed to running
2018-08-14 11:23:59,424 INFO     lbrynet.core.client.BlobRequester:417: Offered rate 0.000000/mb accepted by <IP_ADDRESS>
2018-08-14 11:23:59,427 INFO     lbrynet.core.client.BlobRequester:490: Requesting blob 05a5c9bc781c53100027bf39fcfd7fd947bf29e1a6d70b5c97e0cc570162398683e8996f6f9edcfecedde15fa8951386 from <IP_ADDRESS>:3333
2018-08-14 11:23:59,812 INFO     lbrynet.core.client.BlobRequester:566: Blob 05a5c9bc781c5310 has been successfully downloaded from <IP_ADDRESS>:3333
2018-08-14 11:24:00,739 INFO     lbrynet.core.client.BlobRequester:490: Requesting blob 4ac95ff9cbfe2975361bdd69c6939e7de35c77ba4bb39cfedea9b654ea7b4f79f0b32b330942bb63052ba37b144dab3e from <IP_ADDRESS>:3333
2018-08-14 11:24:00,801 INFO     lbrynet.daemon.Daemon:2348: Got unused wallet address: bKkaKq4Diu2kmykjZKJBZGnXiRHZXznR7i
2018-08-14 11:24:01,038 INFO     lbrynet.core.client.BlobRequester:566: Blob 4ac95ff9cbfe2975 has been successfully downloaded from <IP_ADDRESS>:3333
2018-08-14 11:24:01,043 INFO     lbrynet.core.client.BlobRequester:490: Requesting blob<PHONE_NUMBER>976fd2366fe0f9b37eb5642097616afc18c8a8225ca600308dc6ddf5927bc691f2a513a46060bc5caf0a89 from <IP_ADDRESS>:3333
2018-08-14 11:24:01,135 INFO     lbrynet.core.HTTPBlobDownloader:70: Mirror completed download for db03b8161a1aecd4d04b730891bd44ec4b56897f8add5d7409b8da2cb6ec758e56b21ca28214da83fbdb73bef5c30fd4

The proper resolution to this may simply be to expose in the API whether or not the first blob is written (or maybe just make daemon responsible for metadata being available?), rather than actually forcing blobs to be written in order.

This get call resulted in the "waiting for metadata scenario". Notice blobs completed is 1 but the written bytes are 0.
{
  "id":<PHONE_NUMBER>686,
  "jsonrpc": "2.0",
  "result": {
    "blobs_completed": 1,
    "blobs_in_stream": 179,
    "channel_claim_id": null,
    "channel_name": null,
    "claim_id": "8243646e853eeae4977b6fe055fc765f602b37ae",
    "claim_name": "what-cryptocurrency-to-buy-in-the-bear",
    "completed": false,
    "file_name": "what-cryptocurrency-to-buy-in.mp4",
    "total_bytes": 375178592,
    "txid": "9a32a1d190f195b7e40e3bef3b899a0d7171268e9043557bcf0d22f7a300257d",
    "written_bytes": 0
  }

Following file_list call (2 blobs completed, but only 2 MB written. hmm):
{
  "id":<PHONE_NUMBER>240,
  "jsonrpc": "2.0",
  "result": [
    {
      "blobs_completed": 2,
      "total_bytes": 375178592,
      "txid": "9a32a1d190f195b7e40e3bef3b899a0d7171268e9043557bcf0d22f7a300257d",
      "written_bytes": 2093056
    }
  ]
}


Live change still fired after maxLength reached

Hi SAP
I set on my input the maxLength property and the livechange event will still continue fired, even when the maxLength in the input field is reached.
Thanks

Hi @kostonstyle ,
Thank you for your findings. I have created an internal incident:<PHONE_NUMBER>
Regards,
Diana

Hi,
This issue has been found to be due to the following bug in Chrome browser: https://bugs.chromium.org/p/chromium/issues/detail?id=434631
We have closed the internal ticket as this is a browser bug and needs to be addressed by the browser vendor.
Thanks and regards,
Jordan


Speed resets on next video

When setting the playspeed it should stay that way for all future videos.
Nevertheless, when switching to the next or previous video it's back at 1.0.
Look into this -- why does it reset?

Fixed in the latest commit


Update your RocketChat Bug/Recommendation

Video displaying details about the bug and suggestion
https://youtu.be/CRGAu4wz2UI
My Setup

Operating System: Ubuntu running on docker
App Version:
Installation type:

[X] I have tested with the latest version
[X] I can simulate the issue easily

Description
You can see the version notification bar is suggesting we upgrade to is earlier than the version we are on.

Issue occurs in web browser and windows and mac app. This is while I filed here instead of the Electron as it pointed to a content issue from meteor or some other back end tech
Expected Behavior
I used inspect in Chrome to moc up how the solution could be worded. Of course in my situation, our RC server is on the latest version, and the notification bar should not even be showing.

Your issue is not about Electron application, but about server itself.
So right repo in your case is https://github.com/RocketChat/Rocket.Chat/issues

Closing this issue since I understand that it is a Rocket.Chat server issue.


Fix failing Cholesky decomposition

In same cases, the Cholesky decomposition in the Svärd-Kalisch simulation might fail due to non-positive-definiteness coming from too large time steps. This fixes this.

Just to be clear and for later reference: The change that rewrites hmD1betaD1 be using the periodic (upwind) SBP property is not directly related to the fix of the failing Cholesky decomposition. The fix comes from the check if the Cholesky factorization was successful and setting explicitly rejecting the time step if not. The other change was just in addition to avoid possible floating point errors in the symmetry of the matrix.


Recursive DFS implementations

Hi dagrejs team,
Like mentioned in this issue: dagrejs/dagre#327 I ran into some problems when using dagre on bigger graphs. Since dagre uses graphlib internally, some of the errors originated from graphlib.
In lib\alg\dfs.ts, the DFS function is implemented recursively which resulted in max call stack size errors when using it with big graphs (3000+ nodes).
It would be a good idea to rewrite the recursive DFS functions to iterative DFS functions to avoid max call stack size errors.

Implemented in https://github.com/dagrejs/graphlib/pull/174, which is a reimplementation of https://github.com/dagrejs/graphlib/pull/148.


[mwc-menu] not catching key events when opened upon a right mouse click

I am using the 0.25.3 version.
I have this logic on the main interface that implements a context menu on right click (very common thing in apps)
firstUpdated() {

  // Prevents Chrome context menu from opening on right click
  this.addEventListener('contextmenu', e=> e.preventDefault())

  // Opens menu on right click
  this.addEventListener('pointerdown', e => {
    if (e.button == 2) {
      document.body.click() // close all others menu
      // open menu at the pointer location (using e coords)
      // ...
    }
  })

  // Menu Hotkeys
  this.menu.addEventListener('keydown', e => {
    if (e.code == 'KeyS') {
      // execute command
    }
  })

}

When I right click on the interface the menu opens at the pointer location as expected. But when I try to press S to activate the hotkey, it doesn't work.
If I change e.button == 2 to e.button == 0 and try with the left click it works, which means the right click is not initiating focus.
Could that be an issue with the element? or is this behavior caused by the way the browser is built, independent from this element?

I can't find a temporary solution I tried this :
this.addEventListener('pointerdown', e =>{
  if (e.button === 2) {
    document.body.click() // close all others menu

    // Open menu at (e.x, e.y)

    // Virtual click on the menu to give keyboard focus?
    this.dispatchEvent(new MouseEvent('pointerdown', {button: 0}))

    // Trying different blur
    // this.menu.blur()
    // this.blur()

    // Clicking the non interactive list-item
    // setTimeout(()=>(this.shadowRoot!.querySelector('[noninteractive]') as ListItem).click(), 1000)
  }
}

Could you let me know a plausible solution if you think of one? (without binding event handler to the window object)
Thanks

NOTE : if I remove the property quick from the <mwc-menu> element, the hotkey works.
😕 ?

I  temporarily fixed this issue using
// @ts-ignore
setTimeout(()=>this.menu.listElement_.focus(), 0)

I also am not sure why I needed to use a timeout here (await on both the menu or the list didn't work).
Hope that helps to start investigating the problem.

Closing since this is old mwc, but let us know if this pattern still isn't working in M3


Virtual env creation failed

After created the venv by  conda env create -f environment.yml, checking conda env list, there is no venv named airflow-tutorial.
Any idea what may cause this?

After some trials, it may be due to some corruption in my conda environment. I will try to solve this, and keep this updated.


where can I find the 'kinetics_val.csv', 'kinetics_train.csv'

When I want to train the TSM model on kinetics, I do not find the file 'kinetics_val.csv', 'kinetics_train.csv'

Have you solved this issue?

you should create it yourself with below code
import os
import csv
Base directory containing class directories
base_dir = '/home/hbai/shukurullo/tsm/temporal-shift-module/data_frames/test'
CSV file path
csv_file_path = 'test_data.csv'
Open the CSV file for writing
with open(csv_file_path, mode='w', newline='') as file:
writer = csv.writer(file)
# Traverse through all class directories
for class_dir in os.listdir(base_dir):
    class_path = os.path.join(base_dir, class_dir)
    print(f'class_path: {class_path}')
    if os.path.isdir(class_path):
        # Traverse through all video files in the class directory
        for video_file in os.listdir(class_path):
            print(f'video_file: {video_file}')
            video_path = os.path.join(class_path, video_file)

            writer.writerow([class_dir, video_file])

print(f"CSV file '{csv_file_path}' created successfully.")


Invalid default-extensions break ob run in very confusing way

Adding a non-existent extension (e.g. typo) to default-extensions makes it so that only module extensions are active. For instance, starting with the obelisk skeleton
    , mtl
    , text
  default-extensions:
+   GeneralisedNewtypeDeriving
    TypeFamilies
    PolyKinds
   exposed-modules:

causes ob run to error with
common/src/Common/Route.hs:49:1: error:
    • Illegal family instance for ‘Data.Constraint.Extras.ConstraintsFor’
        (Use TypeFamilies to allow indexed type families)
    • In the type instance declaration for ‘Data.Constraint.Extras.ConstraintsFor’
      In the instance declaration for
        ‘Data.Constraint.Extras.ArgDict c_aaX5 FrontendRoute’
   |
49 | concat <$> mapM deriveRouteComponent
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
common/src/Common/Route.hs:49:1: error:
    • Illegal family instance for ‘Data.Constraint.Extras.ConstraintsFor’
        (Use TypeFamilies to allow indexed type families)
    • In the type instance declaration for ‘Data.Constraint.Extras.ConstraintsFor’
      In the instance declaration for
        ‘Data.Constraint.Extras.ArgDict c_aaX3 BackendRoute’
   |
49 | concat <$> mapM deriveRouteComponent
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...

The error only becomes apparent when nix-build -A ghc.common fails with
Setup: The package common-0.1 requires the following language extensions which
are not supported by ghc-8.4.3: GeneralisedNewtypeDeriving

because the British spelling is only available on 8.6.

Is ob run perhaps just not showing the Setup errors here? I would expect it actually hits them just as any cabal command would.

Seems like this now leads to an infinite reload cycle
    , mtl
    , text
+ default-extensions:
+  x
  exposed-modules:

(...)

Reloading...
  /run/user/1000/ghc24799_0/ghc_35.hspp

/run/user/1000/ghc24799_0/ghc_40.hspp:1:14: error:
    Cannot parse LANGUAGE pragma
    Expecting comma-separated list of language options,
    each starting with a capital letter
      E.g. {-# LANGUAGE TemplateHaskell, GADTs #-}
  |
1 | {-# LANGUAGE x #-}
  |              ^

Reloading...
  /run/user/1000/ghc24799_0/ghc_40.hspp

/run/user/1000/ghc24799_0/ghc_45.hspp:1:14: error:
    Cannot parse LANGUAGE pragma
    Expecting comma-separated list of language options,
    each starting with a capital letter
      E.g. {-# LANGUAGE TemplateHaskell, GADTs #-}
  |
1 | {-# LANGUAGE x #-}
  |              ^

Reloading...
  /run/user/1000/ghc24799_0/ghc_45.hspp

(...)

@alexfmpe Any idea how we can fix this issue? I can reproduce the issue as per your comment above, the infinite reload cycle still exists...

We inject cabal extensions in their package modules so that multiple packages can exist in ob run even though ghci itself doesn't distinguish packages and would just mash all extensions together.
It looks like we also do this with unknown extensions
https://github.com/obsidiansystems/obelisk/blob/master/lib/command/src/Obelisk/Command/Preprocessor.hs#L81 which is why the LANGUAGE x ends up in source.
I don't see why that would trigger an infinite cycle though. Looking at the weird .hspp filenames I wonder if there's some sanity checking happening after the preprocessor runs but before it's combined with normal source


Update for Laravel 5.2 and legacy compactibility

Changing bindShared as it's deprecated in 5.1 and removed from 5.2.

We're not going to be using 5.2, but as it's deprecated in 5.1, this might still be worthwhile.

I think it's worthwhile staying as close to the latest release as we can. 5.2 brings some nice new features. So long as it's still compatible with PHP 5.5.9, we can use it.

On 29 Dec 2015, at 08:57, Josh Harmon<EMAIL_ADDRESS>wrote:
We're not going to be using 5.2, but as it's deprecated in 5.1, this might still be worthwhile.
—
Reply to this email directly or view it on GitHub.

@euantorano I ninja-deleted my comment after I saw your commit. I thought the whole point of being on 5.1 though was to have as long of a framework short cycle as possible before people potentially have to update their environments for new Laravel versions.

Yeah, I noticed that ;)
IMO, so long as the versions still have the same server requirements, we should be OK to stick with them. The whole 5.x line should be following semantic versions and shouldn't change anything major like PHP requirements.

On 29 Dec 2015, at 09:14, Josh Harmon<EMAIL_ADDRESS>wrote:
@euantorano I ninja-deleted my comment after I saw your commit. I thought the whole point of being on 5.1 though was to have as long of a framework short cycle as possible before people potentially have to update their environments for new Laravel versions.
—
Reply to this email directly or view it on GitHub.

@JoshHarmon IMHO, whatever the Laravel version your team is going to stick to, bindShared has been  deprecated on 5.1 and removed from 5.2, however, Laravel has always introduced minor breaking change through differents minor release, see 5.1.0 and 5.1.11
I would rather suggest you, and your team, to stick to the newest release, or just set a 5.1 version as MyBB main Laravel version, it could be really tiresome to update all your dependencies for each new Laravel version, as the framework is constantly evolving.
@euantorano Laravel is not following semantic versionning as @GrahamCampbell specified on https://github.com/laravel/framework/issues/10625, also he said even 5.3 will keep compactibility with PHP 5

@Maxime-BHA I'm mostly in support of staying updated with the Laravel releases. However, I wasn't aware that we made the decision as a team to upgrade to 5.2 (or later, eventually?). If you saw my comment before I retracted it, I mentioned that I agree it's still worth changing because of bindShared being deprecated. Also, thenk you for the link I was looking for.

Alright, we'll merge this and keep my changes for the 5.2 upgrade. I'll open a topic discussing how we should track Laravel releases.


Fix memory leaks by using std::shared_ptr<>

This PL uses std::shared_ptr<> instead of classic pointers (which were never deleted). This is mostly in inverse-dynamics-formulation-base.cpp.
This should fix #110.
I think the "public" API should not have changed, but please double-check (our code worked out of the box). The python side seems to work (but I did not test in details).
We could consider a few API changes. For instance, the solver factory could return a shared_ptr instead of a pointer. There are also a few
We have to move to c++11 for std::shared_ptr (I also used a few auto, since we are in c++11...).

@jbmouret Many thanks. It looks good to me too.


Chef 12 ActiveDirectory keeps redirecting to "link-account"

Hi,
to reproduce the bug:

Configure Chef Server to support ActiveDirectory autentication
Login with your ActiveDirectory account the first time
Click the button on the left side for creating a new user
Let someone invite you and accept the invitation
Logout

Now this happens every time you login now:

Login
You'll be directed to Link an Existing Chef Account
If you now try to login with your password (as this is your account), you'll get a 500
9 If you call the "/" path of the installation (instead of producing the step which leads to 500), you're logged in

Hi @yves-vogl, thanks for reporting this.  We will take a look into it, but in the interim would you mind opening this issue at https://github.com/opscode/chef-server/issues?  We're tracking all server-related issues there, just because of the number of components involved in the fully packaged Chef Server makes it otherwise difficult to manage.


fail spending opret and tapret allocations together

I've added a test that tries to receive with a tapret wallet using opret as closing method. You can run it by checking out to https://github.com/zoedberg/rgb-integration-tests/tree/tapret_opret and running cargo +1.79 test --test transfers tapret_wlt_receiving_opret.
The transfer is succesful but when the wallet tries to spend the opret allocation together with a tapret one (the change from the 1st transfer) the pay method fails with:
Composition(Stock("the spent UTXOs contain too many seals which can't fit the state transition input limit."))

I recall this functionality (closing both an opret and a tapret seal in a single RGB transfer) was inteded to work, as discussed in Viareggio (because we discovered this wasn't working). A refactor should have then fixed this.

yes, there was a huge work done to make this work, and I had an impression that it was working before. Maybe I am wrong. Anyway this is a bug which I will work on

With https://github.com/RGB-WG/rgb-std/pull/252 the error changed from
Composition(Stock("the spent UTXOs contain too many seals which can't fit the state transition input limit."))

to
Composition(Stock("the invoice requirements can't be fulfilled using available assets or smart contract state."))

This is how it should work: the tapret wallet can't use opret funds; a manual hacking Is required. Since you lack tapret RGB funds you can't fulfill the invoice.
Spending opret would require creating a second transition bundle, since each transition bundle commits to the used closing method and can't spend both opret and tapret. But the second transition bundle can't pay to the seal defined in the first transition bundle - the receiver's wallet won't recognize that payment.
Thus, if you received invalid opret transfer into a tapret wallet, you need:

add some RGB tapret funds to the same UTXO which already has opret funds (you already have that in your case)
pay an invoice which can be covered by your existing tapret balance (you can create tiny self-invoice for that); with that opret funds will convert into tapret in your own change;
after that you will be able to spend funds which came through opret.

I actually was able to write logic allowing creating two different transition bundles spending from both opret and tapret inputs - and figuring out which ones have enough funds (or how to combine them). The logic is extremely complex, especially in part related to change etc. I am not sure whether that complexity (with all the risks for bugs) worth UX improvements.
https://github.com/RGB-WG/rgb-std/pull/256

I confirm that with https://github.com/RGB-WG/rgb-std/pull/256 the test wallet is able to spend both allocations.
The fix seems like a completion of the huge work that has been done to allow spending both tapret and opret allocations. In this context, the solution doesn't seem excessively complex and the added code looks reasonable.


New lines in tweet text concatenated. Can they be split by " " or \n instead?

I'm running the following:
import twint
c = twint.Config()
c.Since='2018-10-01'
c.Search= "#hashtag"
c.Store_csv = True
c.Custom = ["tweet"]
c.Output = "twitter.csv"
twint.run.Search(c)
###It works just fine. However, when my search finds tweets like this...
This tweet contains the following:
x
y
z
#hashtag
###My .csv files is formatted like so: "This tweet contains the following:xyz#hashtag"
###What would be great is more like this: "This tweet contains the following: x y z #hashtag" or "This tweet contains the following:\nx\ny\nz\n#hashtag"
Any ideas?
Cheers!!

twint/tweet.py

The new-line char is replace with whitespace-char, can you please update your local repo?
pip install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint


improved QNames

turtle QNames must not start with a number

Actually it is NCNames that cannot start with a number.
There is no prohibition on an element within a URI, including the final 'local-name' element, starting with a number. The Turtle spec is clear about this and includes examples where the local name starts with a number - https://www.w3.org/TR/turtle/#sec-iri
Some software (TopBraid) trips over where the local-name is not an NCName, but this is not an RDF problem.

Yes, not a pure RDF Issue, but unless there’s an issue with the PR negatively affecting others, I’d like to see it go through as I am using TB. Should be neutral for most.


tokens_str in Encoder

I have been trying to implement a "custom" encoder within this codebase, and I was wondering how to get access to the raw tokens (in string form).
What I have tried so far:

Setting up the tokens_str placeholder:

self.placeholders['tokens_str'] = \
            tf.placeholder(tf.string,
                           shape=[None, self.get_hyper('max_num_tokens')],
                           name='tokens_str')

Once I have those, I am trying to pipe the tokens into the tf_hub Elmo module, as follows:
seq_tokens = self.placeholders['tokens_str']
seq_tokens_lengths = self.placeholders['tokens_lengths']

# ## DEBUGGING: OUTPUT SHAPES
# print("Sequence Tokens Shape: %s" % seq_tokens.shape)
# print("Sequence Tokens Lengths: %s" % seq_tokens_lengths)

## pull elmo model from tensorflow hub
elmo = hub.Module("https://tfhub.dev/google/elmo/2", trainable=is_train)
token_embeddings = elmo(
     {
           "tokens": seq_tokens,
           "sequence_len": seq_tokens_lengths
      },
     signature='tokens',
    as_dict=True
)['elmo'] ## [batch_size, max_length, 1024 or 512]

I can see from my debugging statements, that seq_tokens shape is (?, 200), which is expected and seq_tokens_lengths shape is (?) which is also expected.
The error I get is len(seq_lens) != input.dims(0), (1000 vs. 0), which is coming from the ELMo model. But I'm guessing that this is coming from the seq_tokens not being pushed into the ELMo model.
Any help is appreciated!

HI @sjakati98,
The code doesn't support using the string representation of tokens as-is.
I believe that you need to create a new Encoder for your use-case. Specifically, load_data_from_sample is the function that's invoked for converting a raw sample (as it appears in the .jsonl) into a format that is "understood" by the network. Then extend_minibatch_by_sample takes care of the minibatching logic.
By implementing a custom Encoder, you should be able to use the pre-built ELMo model in an encoder; it'd be interesting to see the results :)


Proto file missing

Hello!
I tried to test the repository, but ran into the problem of missing protocol file audio2face.proto

You need to update the path in grpcClient.js with the path to the .proto file from your audio2face installation.
Eg:
const PROTO_PATH = "C:/Users/houar/AppData/Local/ov/pkg/audio2face-2023.2.0/exts/omni.audio2face.player/omni/audio2face/player/scripts/streaming_server/proto/audio2face.proto";


Android: Reading Progress Broken in Folders

The progress circle in Reading seems to not be tracking unread counts correctly while reading folders.  Individual feeds seem okay, though.

All fixed up in #662.  Feel free to re-open if I missed an edge case.


Notes on ConsLaborModel.py?

Are there any notes on this model and the solution method? @llorracc @mnwhite @Mv77

I'll dig up the document I wrote way back.
On Sun, Nov 14, 2021 at 6:27 PM alanlujan91 @.***>
wrote:

Are there any notes on this model and the solution method? @llorracc
https://github.com/llorracc @mnwhite https://github.com/mnwhite @Mv77
https://github.com/Mv77
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/HARK/issues/1083, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKRAFP7IRLEWLUQZQVLJXDUMBAXBANCNFSM5IAMZ7HQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Any luck? I'm interested in how to interpret the labor coefficient parameters LbrCostCoeffs and other details on the solution method.


upload_to_app_store not able to activate languages

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I am trying to upload metadata + screenshot in en-US and fr-FR. The failure comes when fastlane tries to activate languages. The app on itunesconnect currently has en-US, en-CA and fr-CA activated. I have used this Fastfile to upload metadata for other apps and it worked fine; on itunesconnect it activated only the given languages while deactivating rest. Not sure what's going on, all I know is after trying to activate language; fastlane uploads the rating.json, and then it again activates language and start uploading screenshots. But for this app, it fails on first try to activate languages.
The metadata and screenshots are in fastlane/metadata and fastlane/screenshots directory. The screenshots are valid, I have tested by uploading them manually.
I will appreciate if anyone can share alternate way to activate language on itunesconnect using spaceship.
Complete output when running fastlane, including the stack trace and command used

This I copied from reports.xml..  not sure how capture_output works neither found docs

/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/actions/actions_helper.rb:48:in `execute_action'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:236:in `block in execute_action'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:231:in `chdir'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:231:in `execute_action'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/fast_file.rb:149:in `method_missing'
Fastfile:108:in `block in parsing_binding'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/lane.rb:33:in `call'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:45:in `chdir'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/runner.rb:45:in `execute'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/lane_manager.rb:59:in `cruise_lane'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/commands_generator.rb:107:in `block (2 levels) in run'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:75:in `run!'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/commands_generator.rb:332:in `run'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/fastlane/lib/fastlane/cli_tools_distributor.rb:108:in `take_off'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.96.1/bin/fastlane:20:in `<top (required)>'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/bin/fastlane:23:in `load'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/bin/fastlane:23:in `<top (required)>'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `load'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `kernel_load'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:28:in `run'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli.rb:424:in `exec'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli.rb:27:in `dispatch'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/cli.rb:18:in `start'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/exe/bundle:30:in `block in <top (required)>'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/lib/bundler/friendly_errors.rb:122:in `with_friendly_errors'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/exe/bundle:22:in `<top (required)>'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/bin/bundle:23:in `load'
/Users/salmansiddiqui/.rbenv/versions/2.4.2/bin/bundle:23:in `<main>'

In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space.

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.4

Ruby
2.4.2

Bundler?
true

Git
git version 2.14.3 (Apple Git-98)

Installation Source
~/.rbenv/versions/2.4.2/bin/fastlane

Host
Mac OS X 10.13.4 (17E202)

Ruby Lib Dir
~/.rbenv/versions/2.4.2/lib

OpenSSL Version
OpenSSL 1.0.2l  25 May 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
fastlane_require 'spaceship'

DEFAULT_LOCALES = %w[en-US fr-FR].freeze

lane :publish_ipa_file do |options|
  upload_to_app_store(
    username: USERNAME,
    team_name: ios_tunes_team_name,
    dev_portal_team_id: ios_portal_team_id,
    app_identifier: IOS_APP_ID,
    skip_binary_upload: true,
    platform: 'ios',
    languages: DEFAULT_LOCALES,
    app_rating_config_path: 'fastlane/rating.json',
    price_tier: 0,
    reject_if_possible: true,
    automatic_release: true,
    force: true
  )
end

No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.96.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-appicon
0.13.0
✅ Up-To-Date

fastlane-plugin-brew
0.1.1
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.1.0

bundler
1.16.1

io-console
0.4.6

CFPropertyList
3.0.0

concurrent-ruby
1.0.5

i18n
0.9.5

minitest
5.11.3

thread_safe
0.3.6

tzinfo
1.2.5

activesupport
4.2.10

public_suffix
2.0.5

addressable
2.5.2

atomos
0.1.2

babosa
1.0.2

claide
1.0.2

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.5.0

cocoapods-deintegrate
1.0.2

cocoapods-downloader
1.2.0

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.0.0

netrc
0.11.0

cocoapods-trunk
1.3.0

cocoapods-try
1.1.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.0.1

gh_inspector
1.1.3

molinillo
0.6.5

ruby-macho
1.1.0

nanaimo
0.2.5

xcodeproj
1.5.9

cocoapods
1.5.0

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

dotenv
2.4.0

emoji_regex
0.1.1

excon
0.62.0

multipart-post
2.0.0

faraday
0.15.2

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

fastimage
2.1.3

jwt
2.1.0

little-plugger
1.1.4

multi_json
1.13.1

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

uber
0.1.0

representable
3.0.4

retriable
3.1.1

google-api-client
0.21.2

json
2.1.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.4.0

rubyzip
1.2.1

security
0.1.3

naturally
2.1.0

simctl
1.6.4

slack-notifier
2.3.2

terminal-notifier
1.8.0

unicode-display_width
1.3.2

terminal-table
1.8.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
1.0.0

fastlane-plugin-appicon
0.13.0

fastlane-plugin-brew
0.1.1

rest-client
2.0.2

generated on: 2018-05-26

After looking into spaceship codebase, I found create_languages function.. so I tried the following in bundle console:
require 'spaceship'
ss = Spaceship::Tunes.login(username, password)
ss.select_team #selected my team
app = Spaceship::Tunes::Application.find(app_identifier)
v = app.edit_version
v.create_languages('fr-FR')
v.save!

The above resulted in the same error I get when using upload_to_app_store action
😢

@salmanasiddiqui Heyyyy 👋 So I was able to run the exact code you posted above and it work 💯 for me 😬 Which I guess is good news and bad news. Good news because things work but bad news is that it makes it hard to debug your situation now.
Your error above says In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 5.5" displays must be a .jpeg, .jpg, or .png file that is 2208x1242 or 1242x2208 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 9.7" displays must be a .jpeg, .jpg, or .png file that is 1024x768, 1024x748, 768x1024, 768x1004, 2048x1536, 2048x1496, 1536x2048 or 1536x2008 pixels, at least 72 DPI, and in the RGB color space. In order to save your changes, all 12.9" displays must be a .jpeg, .jpg, or .png file that is 2732x2048 or 2048x2732 pixels, at least 72 DPI, and in the RGB color space. which makes it sound like that you might have some "bad" images already uploaded to your app.
Are you able to add fr-FR to your app via the iTunesConnect website directly? That might be the first place I would look to debug this. If that doesn't work I would maybe clear all the screenshots and then try to add a language.
Sorry for not being able to help more but I can't duplicate your issue on my end 😢

🙁 it was working for me aswell till May 24th, but not anymore.
I am able to add fr-FR to my apps via iTunesConnect website directly. Screenshot/metadata is all valid otherwise apple wouldn't let me upload it for already activated languages right? Something is wrong while activating/deactivating languages, but I am not really able to figure out what.
Also, before May 25th, for some apps which had en-US, en-CA and fr-CA locales activated, I updated metadata and changed locales to en-US and fr-FR using my lane publish_ipa_file. Now I have modified my Fastfile and changed the DEFAULT_LOCALES to en-US, en-CA, fr-CA. Running publish_ipa_file for the schools which were updated by my lane before May 25th now fails with the same error.

@salmanasiddiqui Do things work for you if you try downgrading to fastlane 2.95.0?

@joshdholtz I am not sure at all but this might be related https://github.com/fastlane/fastlane/pull/11555
As I have given up on modifying languages and currently just went with what was activated by default, I will need some time to reproduce the issue as the above PR suggest.


Calculate.activity : Fixing input reset when clicking on trigo functions, disable user selection of results

Strange: you're sending your pull request as "mikklfr" but you've commited using "ohayon_m". I guess it's the reason why you don't appear in the contributor list.


TIKA-2312 proposition of exposing ID3TagsAndAudio

[Issue Link]
https://issues.apache.org/jira/browse/TIKA-2312

There seems to be some unrelated whitespace changes in your commit - any chance you could remove those?
Otherwise, commit looks fine, but can I ask what you're trying to get at? Perhaps we might want to expose those id3 fields as well as standard through Tika is all!

@Gagravarr
Currently I am writing custom Mp3 Parser which allow user to import Metadata from Radio Automation System which name is AudioVault. This tool is used by professional broadcasters.
This system has custom metadata structure for all supported audio files. During the research I recognised that it add system specific metadata which depends on occurrence of ID3v2 tags in any version. To be straight if ID3v2 occurring this system add their specific metadata on top of file if not on the bottom


feat(GeoSearch): implement InstantSearch.css

Specs
https://instantsearch-css.netlify.com/widgets/geo-search/
Stories
https://deploy-preview-3138--algolia-instantsearch.netlify.com/v2/dev-novel/?selectedStory=GeoSearch.default

Is the spacing issue with the checkbox fixed by https://github.com/algolia/instantsearch.css/pull/81 ?

Nope but it's already fixed by https://github.com/algolia/instantsearch.css/pull/78 (it's not released yet though)

@francoischalifour @bobylito It's fixed.


Jumping on ramps causing movement weirdness

I have noticed using the vanilla script, whenever you jump whilst moving on a ramp, your upwards movement on the ramp is heavily dampened, nearly to a stop. This happens until you either stop moving at all, or jump again. I really enjoy this character controller but this issue has been bugging me a lot.

Have you tried the fix in Issue 21?
https://github.com/Olezen/UnitySourceMovement/issues/21


Peewee School model

Codecov Report

Merging #47 into master will decrease coverage by 0.21%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
- Coverage   35.98%   35.76%   -0.22%
==========================================
  Files          17       17
  Lines        1431     1423       -8
==========================================
- Hits          515      509       -6
+ Misses        916      914       -2

Impacted Files
Coverage Δ

backend/fixtures.py
100% <ø> (ø)
:arrow_up:

backend/database.py
41.33% <100%> (-2.07%)
:arrow_down:

frontend/frames/actualdata.py
85.71% <66.66%> (+0.13%)
:arrow_up:

frontend/mainwindow.py
39.57% <66.66%> (ø)
: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 9f01400...e525ed9. Read the comment docs.


build: include a docker-compose setup

Codecov Report

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

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
- Coverage   60.93%   56.64%   -4.30%
==========================================
  Files          16       16
  Lines        1792     1792
==========================================
- Hits         1092     1015      -77
- Misses        546      640      +94
+ Partials      154      137      -17

Codecov Report

Merging #76 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #76   +/-   ##
=======================================
  Coverage   60.93%   60.93%
=======================================
  Files          16       16
  Lines        1792     1792
=======================================
  Hits         1092     1092
  Misses        546      546
  Partials      154      154


RTF Editor in Web Components

Based on the Spike #2241

@ElishaSamPeterPrabhu Had worked on this and created a branch to show it currently only works with quill.js when not inside the shadowdom.  The holdup here is whether we accept that the RTF component is the only one that does not leverage the shadowdom.  Once we agree on that, we can proceed with a proper PR and code review.

@prashanth-offcl to review the POC and move to todo


pretty-print schema and examples for application/json mediatypes.

When RAML input contains schema or example contents in JSON-Schema, the results tend to come out like this:

Would be nice if they looked more like this:

Pull request #112 submitted to address this feature request :).

It's just shown however you input it in the raml file, for example:

Closing this issue since there's a PR for this as well. The designs for version 2 of raml2html are almost done, so once that is (finally) implemented there's room for more improvements again. Sorry for the delays.

Cool, thanks for the update and no worries on timing.


Better error handling

returning 1 instead of 0 when an error occurs
writing the whole exception to the STD ERR output

#4

Looks good. In the future, use the dev branch please. Thanks.

Sorry, I thought I did that, but somehow I failed...
On Mon, Aug 31, 2015 at 4:03 PM, Brock Allen<EMAIL_ADDRESS>wrote:

Looks good. In the future, use the dev branch please. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/IdentityServer/IdentityServer3.EntityFramework.Cli/pull/5#issuecomment-136380225
.


Limit number of pages shown

Ran into an issue while using this, and was wondering if there was any built in functionality to fix it. I have 50 pages worth of data being paginated, and by default it outputs all 50 of the page links. The issue is that since there are so many pages being output, they are scrolling off of the screen and skewing the site template.
Is there any way to limit the amount of pages being shown at a time? For example, on load it will only show pages 1-10, but as the user scrolls past 5 it will show 2-11, past 6 will show 3-12 and so on.

@BTW8892 I have the same problem,did you find any solution?

Any update on this? I am experiencing same issue...

I'm having the same problem, nice easy to use plugin but would definitely be nice to have an option for this particular situation.

any update on this？

It needs some cleaning up so you can use it in the options, but I've got a working fix and you can get the code here. I would have used the code feature but my code uses template literals so it messes with the code formatting.


Consider supporting virtualization with CSS Grid

https://github.com/Mikescops/vue-virtual-grid
https://github.com/vitorinoninja/react-virtual-css-grid
https://github.com/adazzle/react-data-grid

https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_grid_layout/Subgrid

Do you have any specific plans/goals with this? I'm just curious.
Would this be an internal implementation detail or are you planning on exposing things to the consumers of the grid as well?
I.e. set column count with repeat(auto-fit, ...)/ repeat(auto-fill, ...).

Would love to see this implemented, currently using TanStack Virtual for Vue 3 to get a virtualized masonry grid, but they only support vertical gap, not horizontal gap, which makes the designs ugly and impossible to use :/


Add XcodeBuildToolPlugin Support

Overview
This PR adds support for XcodeBuildToolPlugin support to the SPM plugin.
Motivation
The motivation for adding XcodeBuildToolPlugin support is to enable the SPM plugin to be added to the Xcode Run Build Tool Plugins build phase. This will allow users to generate Swift code from proto files automatically when building their projects. The XcodeBuildToolPlugin protocol defines the interface and behavior for plugins that can be invoked by Xcode during the build process.

This pull request contains the XcodeBuildToolPlugin part that we agreed to separate from the previous one. @FranzBusch , could you please review it and give your feedback?

The overview on the PR mention it still having directory support, is that still in or was that removed?  From the other PR, I thought that part was being removed?

Sorry, my bad. It was indeed removed. Corrected now.

Sorry, my bad. It was indeed removed. Corrected now.

No worries, just wanted to double check.
Added reviewers for you also.

Sure @FranzBusch , will add the changes there as well.

Looks like the grpc one has some follow up about docs tweaks, should those happen here also?

Yes, definitely. Best to make the changes here and then move changes there as well.

@FranzBusch have made some changes to the documentation. Let me know if something is amiss.

Done @FranzBusch

@thomasvl If you are happy then let's get this merged. @denil-ct Once this is merged, could you open a cherry pick PR to the 1_x_release_branch branch so that we can get it into the next release and also please update the gRPC PR. Thanks for your contribution!

https://github.com/apple/swift-protobuf/pull/1389 is missing from release branch hence causing conflicts for me. Should I cherrypick that PR as well or should I resolve conflicts for my changes alone?
@FranzBusch @thomasvl

I believe you'll have to patch things up to work around it, otherwise it would be breaking change on the 1.0 branch. ☹
@FranzBusch Thoughts?


Apply pipeline to db api endpoint

refs #5508

adds pipeline to export, import and delete all methods

I think that it should be possible to further refactor this to use utils.handlePermissions(docName, methodName) rather than having your own version?

@ErisDS updated. Thanks for the guide.


GEOMESA-1300 Data jar with just converter and sft definitions

Available as artifactId 'geomesa-tools_${scala.binary.version}' with classifier 'data'

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

you can, you just have to import it in the geomesa-tools/conf/reference.conf. Is that ok?

Is there anyway to avoid the two step process to add sft confs?

yeah, you can just put the file at the top-level of the conf dir. I wanted to keep the classloading in the tools in sync with the jar - otherwise I figured that someone would add a new sft but forget to add it to the jar. But we can also roll back to just searching for sft folders in the conf file.

I wonder if anyone is using the ability to add SFTs, etc.
Could we split the difference?  Load up the jar and search the conf directory structures?

yeah, i kept the existing ones in conf instead of a jar to make it easier to edit them if desired. but I could include the jar instead

Ok, do we already have a tutorial/other documentation on what the GeoMesa converters do?  Maybe we should update that and explain how things change?  @mdzimmerman thoughts?

There is not a tutorial. There is, however, a chapter on the converters library in docs/user/convert.rst (http://www.geomesa.org/documentation/current/user/convert.html) which I think would be the appropriate place to describe the changes.

I'll update the docs - @jahhulbert-ccri @jnh5y are we satisfied with the current behavior?

In the final section ("Loading Converters and SFTs at Runtime"), there's a reference to gm-data that should probably be removed.

@elahrvivaz I think the behavior in this PR is sensible.  My main push is to document it.

updated docs


lor error message: may lead to race conditions between concurrent requests

2020/05/04 21:56:32 [warn] 73071#0: *3 [lua] _G write guard:12: __newindex(): writing a global lua variable ('LOR_FRAMEWORK_DEBUG') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
stack traceback:
	/usr/local/openresty/site/lualib/lor/index.lua:11: in main chunk
	[C]: in function 'require'
	/usr/local/openresty/nginx//app/server.lua:2: in main chunk
	[C]: in function 'require'
	/usr/local/openresty/nginx//lor_demo/app/main.lua:1: in main chunk
	[C]: in function 'require'
	content_by_lua(test.conf:23):2: in main chunk, client: <IP_ADDRESS>, server: , request: "GET /cc/hello HTTP/1.1", host: "<IP_ADDRESS>:7700"
2020/05/04 21:56:32 [warn] 73071#0: *3 [lua] _G write guard:12: __newindex(): writing a global lua variable ('node_id') which may lead to race conditions between concurrent requests, so prefer the use of 'local' variables
stack traceback:
	/usr/local/openresty/site/lualib/lor/lib/node.lua:26: in function 'gen_node_id'
	/usr/local/openresty/site/lualib/lor/lib/node.lua:50: in function 'new'
	/usr/local/openresty/site/lualib/lor/lib/trie.lua:172: in function 'new'
	/usr/local/openresty/site/lualib/lor/lib/router/router.lua:108: in function 'new'
	/usr/local/openresty/site/lualib/lor/lib/application.lua:25: in function 'new'
	/usr/local/openresty/site/lualib/lor/index.lua:18: in function 'fn'
	/usr/local/openresty/site/lualib/lor/lib/wrap.lua:24: in function 'lor'
	/usr/local/openresty/nginx//app/server.lua:4: in main chunk
	[C]: in function 'require'
	/usr/local/openresty/nginx//lor_demo/app/main.lua:1: in main chunk
	[C]: in function 'require'
	content_by_lua(test.conf:23):2: in main chunk, client: <IP_ADDRESS>, server: , request: "GET /cc/hello HTTP/1.1", host: "<IP_ADDRESS>:7700"

sumory/lor : 0.3.3

@hongli-my, The issue has been fixed on the master branch.


SD Card IO Pins

If there is no SD card inserted, can the  SD card IO pins be used for other purposes?

The pin of the SD card is not extended

Thanks for your reply. I may not be understanding the pinout correctly, on the A7670SA pin diagram it shows GPIO 13, 14, 15 on the board edge pins, are these different to the 13, 14 and 15 listed as used by the SD card?

It can be used

Excellent,  thanks.


change validate signature with hmac validation

based on this
https://docs.shopify.com/api/authentication/oauth#verification
MD5 Signature Validation will be removed after June 1st, 2016

Oh wow, is the file already updated. Or do we need to update that
individually?
On Monday, February 8, 2016, Ahmad Hajar<EMAIL_ADDRESS>wrote:

based on this
https://docs.shopify.com/api/authentication/oauth#verification
MD5 Signature Validation will be removed after June 1st, 2016
You can view, comment on, or merge this pull request online at:
https://github.com/cmcdonaldca/ohShopify.php/pull/13
Commit Summary

change validate signature with hmac validation

File Changes

M shopify.php
https://github.com/cmcdonaldca/ohShopify.php/pull/13/files#diff-0
(27)

Patch Links:

https://github.com/cmcdonaldca/ohShopify.php/pull/13.patch
https://github.com/cmcdonaldca/ohShopify.php/pull/13.diff

—
Reply to this email directly or view it on GitHub
https://github.com/cmcdonaldca/ohShopify.php/pull/13.

not yet, you can check my update on validate signature function on my repo.

I'll trust that this works ;-)

Just tried it. It authenticates properly for me.
Only thing is I noticed some syntax errors pointed out by my text editor, but couldn't

pin point the issue.

@omarel1 hmm, do you know what's wrong?
or maybe it because I use short array syntax [] instead of array()? (php >= 5.4)
I just noticed that minimum requirement of this script is php 4
@omarel1 please update your script with this
$dataString = array();
		foreach ($query as $key => $value) {
			if(!in_array($key, array('shop', 'timestamp', 'code'))) continue;

and let me know if the error still exists or not? if the error is gone, I'll update my remo and make another pull request.
how do you think @cmcdonaldca ?

Yes that removed the syntax error and the validation still worked. Thank
you.

@omarel1 check my pull request #14
I change hash_hmac function too because hash_hmac need php >= 5.1.2
    public function validateSignature($query)
	{
		if(!is_array($query) || empty($query['hmac']) || !is_string($query['hmac']))
			return false;

		$dataString = array();
		foreach ($query as $key => $value) {
			if(!in_array($key, array('shop', 'timestamp', 'code'))) continue;

			$key = str_replace('=', '%3D', $key);
			$key = str_replace('&', '%26', $key);
			$key = str_replace('%', '%25', $key);

			$value = str_replace('&', '%26', $value);
			$value = str_replace('%', '%25', $value);

			$dataString[] = $key . '=' . $value;
		}
		sort($dataString);

		$string = implode("&", $dataString);

		$signatureBin = mhash(MHASH_SHA256, $string, $this->secret);
		$signature = bin2hex($signatureBin);

		return $query['hmac'] == $signature;
	}


fix(amqplib): use extracted context for message consuming

fixes #1351 baggage propagation

Which problem is this PR solving?
the baggage is lost while consuming messages since the extracted context isn't passed in
Short description of the changes
we pass in the extracted context to the context.with(....)

Thanks for the fix. Can you please add a test for that?

Thanks for the fix. Can you please add a test for that?

I can't make the repository work on my machine (node-gyp native build problems). The scoped bootstrap is also failing. It's taking too much time for me, I can't continue here :(
I pushed the untested/incomplete test

so, got it running in WSL. and funny, the test I wrote worked on the first try 🎉

/__w/opentelemetry-js-contrib/opentelemetry-js-contrib/plugins/node/instrumentation-amqplib/test/amqplib-callbacks.test.ts
   17:9   error  Replace `expect` with `·expect·`                                                                                prettier/prettier
   18:9   error  Replace `AmqplibInstrumentation` with `·AmqplibInstrumentation·`                                                                                prettier/prettier
   31:9   error  Replace `Baggage,·context,·propagation,·SpanKind` with `·Baggage,·context,·propagation,·SpanKind·`                                                                                prettier/prettier
   32:9   error  Replace `asyncConfirmSend,·asyncConsume,·shouldTest` with `·asyncConfirmSend,·asyncConsume,·shouldTest·`                                                                                prettier/prettier
   39:9   error  Replace `CompositePropagator,·W3CBaggagePropagator,·W3CTraceContextPropagator` with `⏎··CompositePropagator,⏎··W3CBaggagePropagator,⏎··W3CTraceContextPropagator,⏎`                                    prettier/prettier
   47:37  error  Insert `⏎······`                                                                                prettier/prettier
   48:7   error  Replace `propagators:·[new·W3CBaggagePropagator(),·new·W3CTraceContextPropagator()` with `··propagators:·[⏎··········new·W3CBaggagePropagator(),⏎··········new·W3CTraceContextPropagator(),⏎········`  prettier/prettier
   49:1   error  Replace `····})` with `······})⏎····`                                                                                prettier/prettier
   77:38  error  Delete `⏎··········`                                                                                prettier/prettier
   81:14  error  Replace `durable:·false` with `·durable:·false·`                                                                                prettier/prettier
  100:16  error  Delete `⏎······`                                                                                prettier/prettier
  135:1   error  Delete `··`                                                                                prettier/prettier
  167:11  error  Delete `··`                                                                                prettier/prettier
  198:53  error  Replace `context.active(),` with `⏎········context.active(),⏎·······`                                                                                prettier/prettier
  199:9   error  Replace `key1:·{value:·'value1'` with `··key1:·{·value:·'value1'·`                                                                                prettier/prettier
  200:7   error  Replace `})` with `··})⏎······`                                                                                prettier/prettier
  202:29  error  Replace `⏎··········queueName,⏎··········Buffer.from(msgPayload)⏎········` with `queueName,·Buffer.from(msgPayload)`                                                                                prettier/prettier
  210:12  error  Insert `⏎············`                                                                                prettier/prettier
  211:1   error  Insert `··`                                                                                prettier/prettier
  212:11  error  Replace `}` with `··},⏎··········`                                                                                prettier/prettier
  256:45  error  Delete `⏎··········`                                                                                prettier/prettier
  260:14  error  Replace `durable:·false` with `·durable:·false·`                                                                                prettier/prettier
  279:16  error  Delete `⏎······`                                                                                prettier/prettier
  306:13  error  Delete `··`                                                                                prettier/prettier
  311:1   error  Delete `··`                                                                                prettier/prettier
  319:1   error  Delete `··`                                                                                prettier/prettier
  342:13  error  Delete `··`                                                                                prettier/prettier
  347:1   error  Delete `··`                                                                                prettier/prettier
  355:1   error  Delete `··`                                                                                prettier/prettier

it's in amqplib tests

ah, I see. I fixed it, thank you for the other changes.

CI fails for node 18. Not sure why nor if it is caused by this PR as CI logs don't show any useful hint.


generate-helper-types causes System.IO.IOException

In case if I add --config generate-helper-types key to the command line, I get an exception:
Unhandled exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.IO.IOException: Cannot create '...\PInvoke' because a file or directory with the same name already exists.
   at System.IO.FileSystem.CreateDirectory(String fullPath, Byte[] securityDescriptor)
   at System.IO.Directory.CreateDirectory(String path)
   at ClangSharp.PInvokeGenerator.Close() in /_/sources/ClangSharp.PInvokeGenerator/PInvokeGenerator.cs:line 270
   at ClangSharp.PInvokeGenerator.Dispose(Boolean isDisposing) in /_/sources/ClangSharp.PInvokeGenerator/PInvokeGenerator.cs:line 1689
   at ClangSharp.Program.Run(InvocationContext context) in /_/sources/ClangSharpPInvokeGenerator/Program.cs:line 648
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Span`1& arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
   at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass23_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass25_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__24_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass11_0.<<UseDebugDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__10_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass14_0.<<UseExceptionHandler>b__0>d.MoveNext()

Attached test.zip is set of files to reproduce the issue
 $ ClangSharpPInvokeGenerator --version
ClangSharp P/Invoke Binding Generator version 14.0.0
  clang version 14.0.0
  clangsharp version 14.0.0

This was the same issue as https://github.com/dotnet/ClangSharp/issues/339. It has now been resolved


Remove related org unit section

Doesn't seem to be used (section id: 50)

Actually used by RoadmapView.  Aborting!


Creating a user with roles

Assume the default design docs for the users database. Let's say I have an admin user with username myuser and password mypassword. When I execute:
var db = new PouchDB('http://myuser:mypassword@localhost:5984/mydb');

db.signup('batman', 'brucewayne', { roles: 'myrole' }, function (err, response) {
  if (err) {
    console.log('err=', err);
  }
});

I get the error:
{ [forbidden: Forbidden by design doc validate_doc_update function]
  status: 403,
  name: 'forbidden',
  message: 'Forbidden by design doc validate_doc_update function',
  error: true,
  reason: 'Only _admin may set roles' }

I can issue the following via curl and it works just fine:
curl -HContent-Type:application/json -vXPUT myuser:mypassword@localhost:5984/_users/org.couchdb.user:batman --data-binary '{"_id": "org.couchdb.user:batman","name": "batman","roles": ["myrole"],"type": "user","brucewayne": "mypassword"}'

I just wanted to make sure that I'm not doing something wrong before I start poking around more at the pouchdb and pouchdb-authentication code.

Interesting, the issue only appears to occur when running this code in node--it works fine in the browser. I'm investigating...

For now, I sidestepped this problem by using nano instead. I think there may be a bug somewhere in pouchdb/pouchdb-authentication.

Yes, pouchdb-authentication does not really work properly in Node, although that hasn't stopped people from trying. ;)

I'm having this problem in the browser.
Actually the only reason I was able to add users at all (without roles) was that I didn't have any user/role settings in the _users database's security object (so I guess any old guest was free to add users). Now that I've added restrictions on the security object, I can't do anything on the _users database from my web app.
I think it has something to do with CORS. The preflight OPTIONS for the PUT doesn't include 'authorization' in Access-Control-Request-Headers, and so the PUT never includes any auth information. The preflight only requests 'accept' and 'content-type'.
I do have CORS set up in my CouchDB config and didn't have any issues with PouchDB in general until this.

Same problem in the browser(Chrome) here too .
This is my env.:  PouchDB 5.4.4, pouchdb-authentication v0.5.1, CouchDB 1.6.1.
Is this fixed? why the issue is closed? Where can I get more info on how to create default roles for new users if this is not the way to do it?  Thanks a lot!.

@delkant @nolanlawson Also having this issue when calling db.getUser() for a user that's already logged in. Any thoughts?


Changing provider = "sqlite" to provider = "postgres" does not crash any more.

I used to be able to crash Lift by following these steps from https://github.com/prisma/prisma2/issues/617#issuecomment-536478218:

Create project with prisma2 init foo: Blank project > SQLite > Confirm > Javascript > Demo script
Open prisma/schema.prisma and replace provider = "sqlite" with provider = "postgres"
Run prisma2 dev

Now the replacement of sqlite with postgres in the provider is just ignored and the sqlite file is migrated anyway.

I can confirm this. Looks like we are ignoring the provider and just using the protocol from the URL as the parser.

Yes it's a change in quaint I was afraid would leak through the public API, and it did indeed. I'll fix this.

https://github.com/prisma/prisma-engine/pull/346 gives an error. Do we want to create a specific user facing error for this, to make the end-user experience nicer?

Can you please see how this works now @pantharshit00 and if this is indeed a good way to trigger the Lift error reporting again?


Updated Readme

If the default version of python is 3, it gives an error "ModuleNotFoundError: No module named 'globals'
". Hence python2 should be used with web2py

@earora97 : Closing due to inactivity. Please reopen with the required updates.


Python version upper limit

When trying to install Spelunker with Python 3.12.1, I got the following error:
> pip install spelunker
Collecting spelunker
  Downloading spelunker-1.1.0-py3-none-any.whl.metadata (5.0 kB)
Collecting numpy (from spelunker)
  Downloading numpy-1.26.3-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.2/61.2 kB 2.8 MB/s eta 0:00:00
Collecting scipy (from spelunker)
  Downloading scipy-1.12.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.4/60.4 kB 6.4 MB/s eta 0:00:00
Collecting pandas (from spelunker)
  Downloading pandas-2.2.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (19 kB)
Collecting jwst (from spelunker)
  Downloading jwst-1.12.5.tar.gz (18.5 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.5/18.5 MB 11.0 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting astroquery (from spelunker)
  Using cached astroquery-0.4.6-py3-none-any.whl (4.5 MB)
Collecting astropy (from spelunker)
  Downloading astropy-6.0.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (9.8 kB)
Collecting astroplan (from spelunker)
  Downloading astroplan-0.9.1.tar.gz (140 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 141.0/141.0 kB 9.7 MB/s eta 0:00:00
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting matplotlib (from spelunker)
  Downloading matplotlib-3.8.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (5.8 kB)
INFO: pip is looking at multiple versions of spelunker to determine which version is compatible with other requirements. This could take a while.
Collecting spelunker
  Downloading spelunker-1.0.4-py3-none-any.whl.metadata (5.0 kB)
  Downloading spelunker-1.0.3-py3-none-any.whl.metadata (5.0 kB)
  Downloading spelunker-1.0.2-py3-none-any.whl.metadata (4.9 kB)
  Downloading spelunker-1.0.1-py3-none-any.whl.metadata (4.9 kB)
  Downloading spelunker-1.0.0-py3-none-any.whl.metadata (4.8 kB)
  Downloading spelunker-0.5.5-py3-none-any.whl.metadata (4.4 kB)
  Downloading spelunker-0.5.4-py3-none-any.whl.metadata (4.3 kB)
INFO: pip is still looking at multiple versions of spelunker to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install spelunker==0.5.4, spelunker==0.5.5, spelunker==1.0.0, spelunker==1.0.1, spelunker==1.0.2, spelunker==1.0.3, spelunker==1.0.4 and spelunker==1.1.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    spelunker 1.1.0 depends on ray
    spelunker 1.0.4 depends on ray
    spelunker 1.0.3 depends on ray
    spelunker 1.0.2 depends on ray
    spelunker 1.0.1 depends on ray
    spelunker 1.0.0 depends on ray
    spelunker 0.5.5 depends on ray
    spelunker 0.5.4 depends on ray

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

It appears your ray dependency is incompatible with Python 3.12.1. However, when I downgraded to Python 3.11.0, the package installed successfully. I recommend you note this upper-limit on the Python version in your documentation and potentially in your setup.py file.
This issue was made as part of the review for https://github.com/openjournals/joss-reviews/issues/6202

Okay, I have updated the installation documentation to account for this, as well as setting the python version in the setup.py file to Python 3.10!

Note that you've set a lower-limit of 3.10, but you haven't set an upper limit. The line should instead be python_requires='>=3.10,<3.12', and assuming that Python 3.9 or lower would work (which I suspect it may but haven't tested) you could simply just do python_requires='<3.12'


Fillmurry = error

Gem version (1.7.2)
expected
Faker::Fillmurray.image #=> "http://fillmurray.com/300/300"
what I'm getting
\Faker::Fillmurray.image
NoMethodError: undefined method `match' for 200:Fixnum
Did you mean?  catch

Hey @ChrisCPO, Error message is correct
The function defination of Fillmurray  image is
def image(grayscale = false, width = 200, height = 200)
 raise ArgumentError, "Width should be a number" unless width.match(/^\d+$/)
 raise ArgumentError, "Height should be a number" unless height.match(/^\d+$/)
 raise ArgumentError, "Grayscale should be a boolean" unless [true, false].include?(grayscale)
grayscale == true ? "https://fillmurray.com/g/#{width}/#{height}" : "https://fillmurray.com/#{width}/#{height}"
end
And error present at first two lines
width and height are Fixnum type, and match function dosen't work with Fixnum
Thats why it gives
NoMethodError: undefined method `match' for 200:Fixnum


browser: v1.6

Version bump to 1.6
Added a success screen when chat is sent, rather than just closing the window.
Fancier copypasta link for when nudging is needed but not available
Nasty workaround for popup size glitch https://github.com/keybase/client/pull/6852/commits/f23902aa13e7178ba10093a512c41339994a2e42
Support for keybase.{io,pub} profiles
Tightened up the page matching expressions

@keybase/react-hackers Ready for review at your leisure.