text:
Test failure: AppOfflineDroppedWhileSiteRunning_SiteShutsDown_InProcess

This test fails occasionally with the following error:
System.AggregateException : One or more errors occurred. (dotnet publish exited with exit code : 1) (Operation did not succeed after 44 retries (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path))
---- System.Exception : dotnet publish exited with exit code : 1
---- System.AggregateException : Operation did not succeed after 44 retries (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path) (Value cannot be null.
Parameter name: path)
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value cannot be null.
Parameter name: path
-------- System.ArgumentNullException : Value ca
...

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on 2.2.
CC @muratg
This issue was made automatically. If there is a problem contact ryanbrandenburg.

Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

Is there any logging or extra information that we could add to make this more diagnosable when it happens again?

Yes?

[ ] Add the logging (TODO: Link to PR/commit)

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact ryanbrandenburg.

AppOfflineDroppedWhileSiteRunning_SiteShutsDown_InProcess failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

AppOfflineDroppedWhileSiteRunning_SiteShutsDown_InProcess failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

AppOfflineDroppedWhileSiteRunning_SiteShutsDown_InProcess failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

AppOfflineDroppedWhileSiteRunning_SiteShutsDown_InProcess failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.

repo: aspnet/IISIntegration


text:
Broken test: ConnectionResetLoggedWithActiveStreams

A lot of tests seem to have been broken by our move to Http2. I'm Skipping them for now, but we need to triage and fix them.
Non-exhaustive list of failures here.
The collection contained 0 matching element(s) instead of 1.
   at Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.<ConnectionResetLoggedWithActiveStreams>d__127.MoveNext() in /_/test/Kestrel.Core.Tests/Http2ConnectionTests.cs:line 1974
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Affected tests:

ConnectionResetLoggedWithActiveStreams

Duplicate of https://github.com/aspnet/KestrelHttpServer/issues/2359?

source: gharchive/issue

authors: Tratcher ryanbrandenburg

repo: aspnet/KestrelHttpServer

license_type: permissive

license_source: github-api


text:
Improve reliability of MaxRequestBufferSizeTests.LargeUpload

Increase _dataLength from 20MB to 40MB to improve reliability of Sockets on Windows
Addresses https://github.com/aspnet/KestrelHttpServer/issues/2225

@dotnet-bot test Ubuntu 16.04 Release Build

@halter73, @Tratcher: Added pause data for MaxRequestBufferSize=1MB (the default).  I don't understand why, but the Libuv and Sockets behaviors are much closer compared to MaxRequestBufferSize=5MB.

@halter73, @Tratcher: OK to merge?  I could file an issue to investigate why Sockets gets paused so much later than Libuv when MaxRequestBufferSize=5MB, but since the two transports have similar behavior for the default MaxRequestBufferSize=1MB, I don't think it's worth the time.

source: gharchive/pull-request


text:
Add API baseline for Microsoft.AspNetCore

https://github.com/aspnet/MetaPackages/issues/37
cc @ryanbrandenburg, apparently you are doing this for all the repos? Should I make this change or wait for yours?

Got an offline :shipit: from @ryanbrandenburg.

repo: aspnet/MetaPackages


text:
In Mono, Controller cannot have the name "ActionFilterController"

If there is a controller created with the name ActionFilterController, on calling http://localhost/ActionFilter/SomeAction, InternalServerError is thrown. The same is not the case for ResultFilterController.

This does not happen up to mono 4.0.2.5 alpha bits / 4.0.4 beta bits. It fails in 4.3.0. Filed a bug on mono and is tracked here - aspnet/External#32. Closing this.

repo: aspnet/Mvc


text:
Using PrecompiledViewsCompilerCacheProvider with Multiple Dynamically Invoked Modules

How do we use PrecompiledViewsCompilerCacheProvider with multiple nuget packages ( each nuget package assembly type has it's own source of precompiled views )?

Once the PrecompiledViewsCompilerCacheProvider has been activated/created with a set of assemblies containing precompiled razor views there is no method to add additional assemblies with additional precompiled razor views.
I would like to add component class library packages with controllers and precompiled views to my application. Each component then adds its precompiled views to the overall application.

OK. I've looked through the MVC source and I can use the StaticAssemblyProvider class in my app startup sequence. Each application module ( class library package ) can then add to the provider if it supports precompiled views.
Although I've always had DI in MVC, MVC6 with ASP.NET 5 DI has allowed me to cut my code base substantially - thanks!

@pranavkm @rynowak any thoughts on this? How much will this change with CLI? Still unknown?

We might change how compile modules work in CLI, but this is more about the runtime discovery of precompiled views. The current model should work - you have to know at Startup what assemblies contain views and register these. Auto discovering views from random dependencies has never been the goal.

@pranavkm ok, so then would there be any further work for this issue?

@ToddThomson seems to have figured a work around. So I guess not

@pranavkm I've written my own provider to cover my needs, so I'm fine.

@pranavkm I now add an EmbeddedFileProvider using razor view engine options for each discovered "Plugin" in my solution ( each plugin is an asp.net core class library ).
My plugins are complete "areas" or subsets of a modular asp.net core MVC application.
Within each plugin I would also like to include "immutable" js and less/sass content files. I would like to be able to use the EmbeddedFileProvider for this purpose and have a Nuget command line extension to "manage" these embedded resources. I understand the troubles that are involved with adding content to projects, but I just cannot come to terms with have a self contained component be shipped with nuget bits and and bower/npm bits.
Can you please point me in the right direction to get started.

It's not a first class feature, all we have are building blocks and it hasn't been a scenario. If you don't get specific details to do exactly what you're trying to do it's because we haven't thought it through either. There's no out of the box solution for having a all facets of a component shipped as a nuget package and  consumed as part of your MVC application.

authors: Eilon ToddThomson davidfowl pranavkm


text:
Cache-Control Immutable HTTP Header

There is a new immutable extension to the Cache-Control HTTP header which has been adopted into the IETF on the Standards Track. It's currently implemented in Firefox 49. The documentation states:

Indicates that the response body will not change over time. The resource, if unexpired, is unchanged on the server and therefore the client should not send a conditional revalidation for it (e.g. If-None-Match or If-Modified-Since) to check for updates. Clients that aren't aware of this extension must ignore them as per the HTTP specification. In Firefox, immutable is only honored on https:// transactions.

Read More here:

IETF Draft Spec
Using Immutable Caching To Speed Up The Web
Cache-Control
Cache-Control: immutable
This browser tweak saved 60% of requests to Facebook

Facebook and the BBC have implemented this extension with significant performance wins. Since this is a draft spec, ASP.NET Core should probably not implement it just yet but raising this issue to put it on the radar. If another browser should implement this feature, perhaps it should be considered even as a draft.

This issue was moved to aspnet/HttpAbstractions#763

authors: Eilon RehanSaeed


text:
[BindProperty][BUG] How ModelState validation is calculated?

I have a few BindProperty in my Page:
 [BindProperty]
public string CurrencyId { get; set; }

[BindProperty]
public Currency SelectedCurrency { get; set; }

[BindProperty]
public WithdrawalInput WithdrawalInput { get; set; }

[BindProperty]
public DepositBankInput DepositBankInput { get; set; }

[BindProperty]
public UserWallet UserWallet { get; set; }

[BindProperty]
public UserTransaction WaitingBankDeposit { get; set; }

[BindProperty]
public List<SystemBankAccount> SystemBankAccounts { get; set; }

Only DepositBankInput & and WithdrawalInput have validation attributes(Required and Range). I used them for "asp-for" attributes. I also have two form in that page with following handler signatures:

OnPostWithdrawAsync()
OnPostDepositBankAsync()

When I post to OnPostDepositBankAsync(), it validates WithdrawalInput too, which I don't want (it should only validate DepositBankInput). But when I OnPostWithdrawAsync(), it only validates WithdrawalInput, which is correct.
Forms in that page:
<form method="post" asp-page-handler="DepositBank">
    <input type="hidden" asp-for="@currencyId">

        Miktar

            <input type="number" class="form-control" id="amount-input" placeholder="10" asp-for="DepositBankInput.Amount" autocomplete="off">

        Bitfil Banka hesabı

            <select id="bank-account-input" class="form-control" asp-for="DepositBankInput.SelectedSystemBankAccountId">
                @foreach (var item in Model.SystemBankAccounts)
                {
                    <option value="@item.Id">@item.BankName</option>
                }
            </select>

    <button type="submit" class="btn btn-primary">Yatırma emri ver</button>
</form>

<form method="post" asp-page-handler="Withdraw">
    <input type="hidden" asp-for="@currencyId">

        IBAN
        <input class="form-control" id="address-input" placeholder="TR" asp-for="WithdrawalInput.Address" autocomplete="off">

        Miktar

            <input type="number" class="form-control" id="withdraw-amount-input" placeholder="" asp-for="WithdrawalInput.Amount" autocomplete="off">

                @currencyId

        <button type="submit" class="btn btn-primary">Çekim emri ver</button>

</form>

Related handler methods:
public async Task<IActionResult> OnPostWithdrawAsync()
{
    if (!ModelState.IsValid)
    {
        await InitData();
        return Page();
    }

    return RedirectToPage(new {
        currencyId = CurrencyId
    });
}

public async Task<IActionResult> OnPostDepositBankAsync()
{
    if (!ModelState.IsValid)
    {
        await InitData();
        return Page();
    }

    return RedirectToPage(new {
        currencyId = CurrencyId
    });
}

I'm using .NET Core 2.0.0. I'd like to know what I'm doing wrong.

Hi @lugrugzo. Can you please share the project (or even a simplified version of it) using which we can repro the issue? That'll help us with investigation. Thanks!

I've created it here: https://github.com/lugrugzo/RazorPagesValidationIssue
That problem still occurs for me with that configuration.

Any updates on this?

@dougbu, can you please look into this? Thanks!

One issue here is your use of [Required] on properties with value types (decimal and int). Those will never lead to a validation error because value types can't be null. So the [Required] attribute on WithdrawalInput.Address is the only one that matters when no values are submitted. That's right, your form could be completely empty and validation errors would occur for WithdrawalInput.Address.
The root cause here is the same as #7360: MVC binds top-level nodes with default objects before doing validation. When you submit the WithdrawalInput form, MVC validates the information you submit. When you submit the DepositBankInput form, MVC validates the default i.e. empty WithdrawalInput instance. (MVC validates an DepositBankInput instance in both cases too. But, the default instance is valid.)

Thanks for explanation.

authors: dougbu lugrugzo mkArtakMSFT


text:
Prototype MVC changes for current authorize design

cc @yishaigalatzer @rynowak @loudej @blowdart
Here's my take on what MVC changes would look like with the proposed auth changes so far:

Replaced Permission claim concept with 2 policies: CanViewPage and CanViewAnything
There was one test checking that NullPolicy would succeed, I don't fully grok what that was testing since we repurposed the policy name, so I just skipped it for now (my instinct was to flip that test around to ensure that UnknownPolicy FAILS instead)

Question:

Do we still want Authorize to support effectively what would be an auto policy where its asking for a specific claim in the attribute?  The design currently doesn't support that, but I don't think its that bad requiring all authorize checks to go through a policy configured in startup...

@HaoK where does this PR stand?

My mvc build was broken for a while, I'll update the PR with the new MVC changes in the next day or two

Replaced by https://github.com/aspnet/Mvc/pull/1804

authors: HaoK yishaigalatzer


text:
Consider putting Connection ID back in the log messages

Today we log the connection ID as a "scope" parameter, which tags it on every log throughout the application that is written in the scope of a specific connection. This is goodness. However, some loggers (lookin at you Azure App Service Logger) don't include Scope information in the log messages and don't have a way to do so. For these, it would be useful if the SignalR log messages included the connection ID. We should consider putting the connection ID back into the individual log messages (in the actual message) so we can get that data.
Similarly, we should expose scopes in Azure App Service, but that's a separate issue.

https://github.com/aspnet/Logging/issues/818

repo: aspnet/SignalR


text:
Versioning query

I have added in the nuget package ...
https://dotnet.myget.org/feed/aspnetcore-dev/package/nuget/Microsoft.AspNetCore.WebHooks.Receivers/1.1.0-preview1-34007
... into my project however it says it depends on ...
Microsoft.AspNetCore.Mvc.Core (>= 2.2.0-preview1-34007)

Does this mean they are not going to be part of the aspnetcore 2.1 release? I thought it was due to be released as part of 2.1?

On further investigation, am I to assume the aspnetcore 2.1 release will correspond to the https://dotnet.myget.org/feed/aspnetcore-dev/package/nuget/Microsoft.AspNetCore.WebHooks.Receivers/1.0.0-rc1-30611 ?

… am I to assume …

Yes, that's how the versions align.

authors: WestDiscGolf dougbu

repo: aspnet/WebHooks

license_source: bigquery


text:
Set useBrowserLink to false for VS host file

See #394

I spoke to @Eilon about that. The decision was to turn it off by default for VS. For CLI the default is false already

repo: aspnet/templating


text:
How to access jsdom instance?

Hey,
Is there a way to access the underlying jsdom instance? I'm trying to bridge cucumber js/zombie/enzyme.
I'm not entirely sure if zombie/enzyme would use the same instance of jsdom through normal require mechanics as theres some very specific setup for enzyme/jsdom:
/* setup.js */

var jsdom = require('jsdom').jsdom;

global.document = jsdom('');
global.window = document.defaultView;
Object.keys(document.defaultView).forEach((property) => {
  if (typeof global[property] === 'undefined') {
    global[property] = document.defaultView[property];
  }
});

global.navigator = {
  userAgent: 'node.js'
};

Whilst not related to zombie, im trying to mount a react/redux app into jsdom to perform some BDD style tests using .feature files (gherkin syntax).
Not got alot of experience with Zombie so I may be able to cut out enzyme completely!

It would be a bit of a hack, but you could try require('zombie/dom') and see if that gives you the access you want.

@mdlavin I went with this instead and it appears to be working:
this.browser.visit('http://localhost', function(){
      var jsdom = require('jsdom').jsdom;
      var exposedProperties = ['window', 'navigator', 'document'];

      global.document = b.document;
      global.window = b.document.defaultView
      Object.keys(document.defaultView).forEach((property) => {
        if (typeof global[property] === 'undefined') {
          exposedProperties.push(property);
          global[property] = document.defaultView[property];
        }
      });

     // Able to mount react app now
})

authors: deyceg mdlavin

repo: assaf/zombie

license: mit


text:
ACE Medical rewrite

ACE medical rewrite was released yesterday, atropine was removed and various medical functions were renamed. Please make sure this thing still works.

Welp

I was looking into this a little bit while at work, seems like most things should work as is. The atropine removal is the biggest issue.
Actually it was only hidden and is automatically converted to adenosine in old missions.
Defining a new item that inherits the ACE_atropine and ACE_atropineItem, adding the treatment values and actions it should work again.
However I would probably recommend creating your own item entirely as replacement on the long run.

as reference
https://github.com/acemod/ACE3/pull/7212
https://github.com/acemod/ACE3/commit/aec7a78a58a6a70c99e5b707cc670b5a182f5507

authors: assaultboy zharf

repo: assaultboy/ChemicalWarfare

license: MIT


text:
harmoniser et centraliser les procedures de migrations de donné

Tension
Lors d'un changement de version, d'un changement de gestion des utilisateurs, d'un changement de gestion des droits ou d'autres opération de ce type, des opérations sont nécessaires sur les données existantes. Ces opérations sont dispersé et leur usage est assez peu documenté.
https://github.com/assemblee-virtuelle/archipelago/blob/master/middleware/services/migration.service.js
https://github.com/assemblee-virtuelle/semapps/blob/next/src/middleware/packages/auth/services/migration.js
Proposition
Centraliser et documenter l'usage de ces procédures.

Off topic for SemApps but it was implemented in Archipelago https://github.com/assemblee-virtuelle/archipelago/blob/master/middleware/dbMigrate.js

repo: assemblee-virtuelle/semapps


text:
Clean, consistent LDP get results

Je ne sais pas si je m'y suis pris de la bonne manière, mais au niveau front (et notamment react-admin), cela me pose un problème que les résultats retournés par le serveur LDP ne soient pas toujours les mêmes.
En l'occurence quand on fait un GET en JSON-LD sur une ressource, on obtient des résultats comme ceux-ci:
{
  "@id": "http://localhost:3000/ldp/pair:Project/005ef2d0",
  "@type": "pair:Project",
  "description": "Test",
  "label": "Les chemins de la Transition",
  "webPage": "sdcscd",
  "@context": {
    "description": {
      "@id": "http://virtual-assembly.org/ontologies/pair#description"
    },
    "webPage": {
      "@id": "http://virtual-assembly.org/ontologies/pair#webPage"
    },
    "label": {
      "@id": "http://virtual-assembly.org/ontologies/pair#label"
    },
    "schema": "http://schema.org/",
    "as": "https://www.w3.org/ns/activitystreams#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "ldp": "http://www.w3.org/ns/ldp#",
    "foaf": "http://xmlns.com/foaf/0.1/",
    "pair": "http://virtual-assembly.org/ontologies/pair#"
  }
}

Le formattage du JSON est fait directement par Fuseki.
En l'occurence ce serait plus simple si les résultats étaient compactés comme pour les autres appels à LDP. On obtiendrait alors quelque chose de plus clean comme ça:
{
  "@context": {
    "as": "https://www.w3.org/ns/activitystreams#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "ldp": "http://www.w3.org/ns/ldp#",
    "schema": "http://schema.org/",
    "foaf": "http://xmlns.com/foaf/0.1/",
    "pair": "http://virtual-assembly.org/ontologies/pair#"
  },
  "@id": "http://localhost:3000/ldp/pair:Project/005ef2d0",
  "@type": "pair:Project",
  "pair:description": "Test",
  "pair:label": "Les chemins de la Transition",
  "pair:webPage": "sdcscd"
}

C'est ce que cette PR fait.
J'ai mis le code de "compactage" du côté du service LDP car c'est à ce niveau qu'on a les ontologies. Mais ce n'est peut-être pas juste ?

OK pour moi, on reviendra dessus si nécessaire mais c'est ce qui parait le plus cohérent


text:
Using with administrate gem

I have a products class and using attachinary/cloudinary for images. Decided to try out the administrate gem and this is what I am getting: _uninitialized constant Attachinary::FileDashboard
Extracted source (around line #263):           constant.const_get(name)             else               candidate = constant.const_get(name)               next candidate if constant.const_defined?(name, false)               next candidate unless Object.const_defined?(name)
Any idea on how to solve this? Thank you

I am unaware of where you are getting this error, however I have successfully used attachinary with administrate. You have to do something link this.
rails generate administrate:field attachinary
# app/fields/attachinary_field.rb
require "administrate/field/base"

class AttachinaryField < Administrate::Field::Base
  def path_for_image
    data.path
  end

  def to_s
    data
  end
end

# app/views/attachinary_field/_form.html.erb

  <%= f.label field.attribute %>

  <%= f.attachinary_file_field field.attribute %>

# app/views/attachinary_field/_show.html.erb

<%= cl_image_tag(field.path_for_image, { size: '200x200', crop: :fit }) %>

In your actual dashboard file, you will declare the field like this
ATTRIBUTE_TYPES = {
    id: Field::Number,
    date: Field::DateTime,
    alternative_picture: Field::AttachinaryField,
  }.freeze

Then you can just use :alternative_picture in your FORM_ATTRIBUTES, etc

authors: estiens samwebgit

repo: assembler/attachinary


text:
Mascara CPF Android 4.2

Boa noite senhores ...
Testei o plugin à partir do Android 4.4 e o mesmo funcionou 100%.
Quanto fui fazer o teste no Android 4.2 na digitação do 4º digito para frente a mascara se perde e o usuário não consegue informar o CPF de forma correta, tendo que toda hora posicionar o cursor na última posição para continuar digitando.
Alguém já enfrentou esse problema ?
Obrigado
Ronaldo Araujo

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38710735-mascara-cpf-android-4-2?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1022469&utm_medium=issues&utm_source=github).

Relacionado https://github.com/assisrafael/angular-input-masks/issues/242

Não conseguimos reproduzir no iPhone.
Percebemos que o comportamento ocorre exatamente quando um caracter estático da máscara é inserido, então suspeitamos da lib de máscara, mais especificamente algo próximo dessa função:
https://github.com/the-darc/string-mask/blob/master/src/string-mask.js#L73

O problema não é relacionado a biblioteca, é mais um problema do Angular com certos navegadores.
Segue um issue do StackOverflow relacionado: http://stackoverflow.com/questions/22940346/preserving-cursor-position-with-angularjs
A sugestão do pessoal é usar a API HTMLInputElement.setSelectionRange() embora o suporte dele ainda não seja difundido.

Já existe um pull request com a solução: https://github.com/assisrafael/angular-input-masks/pull/211
Ajuda aí @assisrafael 😄

Eu estava com o mesmo problema ao inserir cpf ou cnpj o cursor pulava para depois do ponto e antes do número digitado.
RESOLVI dessa forma:
<input name="nome_campo" value="seu_valor" onkeydown="this.selectionStart = this.value.length; this.selectionEnd = this.value.length;">

@LauroRafael Sua solução funcionou aqui. Valeu

@LauroRafael utilizando a sua solução estou conseguindo digitar os 6 primeiros dígitos do cpf, depois apaga o que havia digitado, sabe o que pode ser?

@marcosvc84 Opa, blz...
Não consegui emular esse problema que está acorrendo aí no seu caso.
Essa solução que eu havia postado, eu estava usando em um app onde o input aceita CPF ou CNPJ no mesmo campo.
Você colocando apenas o que está em negrito no seu input, não resolveu??

onkeydown="this.selectionStart = this.value.length; this.selectionEnd = this.value.length;"

@LauroRafael o problema é que eu estava utilizando o type="number" e ocorria este problema. O que fiz e resolveu foi usar essa directive que segue e, para forçar o uso do teclado numérico coloquei no html desta forma: type="text" onfocus="(this.type='tel')"    . Tive que usar o tel pois com o number não funcionou
app.directive('input', input);
function input($timeout) {
return {
restrict: 'E',
link: function ($scope, $element, $attrs) {
$element.bind('keydown', function ($event) {
$timeout(function () {
$event.target.selectionStart = $event.target.value.length;
$event.target.selectionEnd = $event.target.value.length;
});
});
}
};
}

Duplicate of #104

authors: LauroRafael assisrafael jayrmotta marcoshmendes marcosvc84 ronaldogaraujo

repo: assisrafael/angular-input-masks


text:
Mask is not working in Android Chrome

Hi,
We're using your mask in production, and noticed that this module have a cursor error. In your own page you can test it, when you try to input a value in a CEP mask in an Android Device, when you fill a value after the "-" the cursor go back to the value that was inputed. And you can't fill the field correctly.
Can you help me?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

+1

+1

+1

+1

authors: leonardodavila lucasmartins mrpvsilva recs182 shirazz


text:
HyperEnclave and AMD SEV、Intel SGX

Hai.
According to my understanding，HyperEnclave is more similar to AMD SEV,not Intel SGX，right？
HyperEnclave include VMM（RustMonitor）和Guest（Occlum and applications in enclave）as AMD SEV does.
I can't figure out the similarities between HyperEnclave and  Intel SGX except the fact that they are all process-based TEE.
Can you offer some guidance？

@Ariel08081214 ,

HyperEnclave is more similar to AMD SEV, not Intel SGX，right？

The TEE instance provided by HyperEnclave is similar to Intel SGX(Process-based Enclave).
The TEE instance provided by AMD SEV is a CVM(Confidential Virtual Machine).
It should be mentioned that we are now working on extending HyperEnclave to provide CVM instance for users, and we plan to publish the related source code in the future.

@Bonjourz
According to my understanding, HyperEnclave create a unique VM for host OS and the untrusted part of applications, the trusted part of the applications run in enclave as a secure VM created by RustMonitor. If the application runs in encalve with Occlum,then the whole application is in the encalve,right？ I think Hyperenclave's enclave is similar to Intel SGX(Process-based Enclave) but the VMM named RustMonitor is similar AMD SEV.

Hi @Ariel08081214

According to my understanding, HyperEnclave create a unique VM for host OS and the untrusted part of applications, the trusted part of the applications run in enclave as a secure VM created by RustMonitor. If the application runs in encalve with Occlum,then the whole application is in the encalve,right？

Yes.

I think Hyperenclave's enclave is similar to Intel SGX(Process-based Enclave)

Yes. The interface to manage enclave on HyperEnclave is similar to SGX.

but the VMM named RustMonitor is similar AMD SEV.

In all the TEE's design, there is a secure monitor who has the most privilege and is able to manage all the security-related resource(memory, CPU status) on the platform. For SGX, the monitor is the microcode in the CPU. For AMD SEV, the monitor is integrated into the AMD Platform Security Processor.
HyperEnclave targets on the common platform, it only relies the common technology like virtualization. So on HyperEnclave, our RustMonitor runs in the VM Root mode(most privilege), and other parts runs in VM-non Root mode.

Thank you very much,your reply helps a lot to me

@Bonjourz  Hai.Here is another question.
The trusted part of a application run in enclave,which is inside a secure VM. So, is there only one secure VM or is one-to-one with application？

Hi @Ariel08081214,
A virtual machine's state comprises the state within the VMCS (Virtual Machine Control Structure), general-purpose registers, and various other CPU states.
From this perspective, each enclave corresponds to a VM on HyperEnclave.

repo: asterinas/hyperenclave


text:
Faster loading folders

Hello.
I have noticed that the first time you enter the mounted folder it takes a while to load.
Consecutive loads of the same folder (while metadata is still valid, are performed really fast) but after some time, it needs to reload it again.
This behavior is the same for every folder and subfolder in the mounted directory.
While understandable, I find it really slow and it gives the whole application a feeling really unresponsive while loading the metadata
Is there any way to improve the metadata retrieval so the application doesn't feel so unresponsive, specially for simple operations such as ls and navigation of folders?

No, sorry, there is no way to make the metadata fetching faster.

I am just trying to understand the behavior of why sometimes it's really slow and other times really faster.
Could the metadata be fetched in the background when the folder is mounted and then be ready for when any operation is performed?

I am just trying to understand the behavior of why sometimes it's really slow and other times really faster.

I think it depends on the access pattern. Sometimes the OS issues a stat call to a dir or a file (maybe to get completion arguments), so when you actually need the metadata it's already there.

Could the metadata be fetched in the background when the folder is mounted and then be ready for when any operation is performed?

At the moment it isn't so. But it can be an enhancement.

In version 0.7.21 (that I'm publishing right now), I've added background_folder_fetching config option to start a background thread that fetches folder data. Let me know is this solve your issue.

Is it possible to cache this metadata somehow?
Each time you access a folder in which there have not even been changes, a rescan takes place, if the folder is large, it takes a long time.
It may be possible to add options with different scenarios such as:
Download a list of all files when mounting - it would be convenient to wait once, and know that the folders will open quickly.
Download lazily (it’s already possible now)
Use cache past scan? (Is this possible?

authors: astrada jorpilo shpinog

repo: astrada/google-drive-ocamlfuse


text:
[red-knot] Panics on generic type alias

Red knot currently panics when encountering PEP-695 generic type aliases:
type ListOrSet[T] = list[T] | set[T]

Backtrace:
thread '<unnamed>' panicked at crates/red_knot_python_semantic/src/types/infer.rs:872:37:
no entry found for key
stack backtrace:
[…]
   6: red_knot_python_semantic::semantic_index::SemanticIndex::definition
             at ./crates/red_knot_python_semantic/src/semantic_index.rs:210:33
   7: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_definition
             at ./crates/red_knot_python_semantic/src/types/infer.rs:872:26
   8: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_type_parameters
             at ./crates/red_knot_python_semantic/src/types/infer.rs:4036:50
   9: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_type_alias_statement
             at ./crates/red_knot_python_semantic/src/types/infer.rs:1805:13
  10: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_statement
             at ./crates/red_knot_python_semantic/src/types/infer.rs:851:53
  11: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_body
             at ./crates/red_knot_python_semantic/src/types/infer.rs:831:13
  12: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_module
             at ./crates/red_knot_python_semantic/src/types/infer.rs:793:9
  13: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_region_scope
             at ./crates/red_knot_python_semantic/src/types/infer.rs:417:17
  14: red_knot_python_semantic::types::infer::TypeInferenceBuilder::infer_region
             at ./crates/red_knot_python_semantic/src/types/infer.rs:405:46
  15: red_knot_python_semantic::types::infer::TypeInferenceBuilder::finish
             at ./crates/red_knot_python_semantic/src/types/infer.rs:4044:9

Fixing this probably involves understanding type … = … statements as having their own annotation scope (https://docs.python.org/3/reference/simple_stmts.html#the-type-statement).

repo: astral-sh/ruff


text:
Add Implementation for Pylint E1132: Repeated Keyword

Summary
Adds the Pylint rule E1132 to check for repeated keyword arguments in a function call.
Test Plan
Tested via the included unit tests and manual spot checking.

Awesome, thanks for this PR and for getting involved!
There's some overlap here with https://github.com/astral-sh/ruff/pull/8450, I'm almost wondering if they should one rule since they both only deal with static dictionary spreads, but I think I need to take a closer look at the code before I have a clear answer to that.

Oh yeah! I totally did not see that other PR. I'm happy to help merge stuff if we go down that route.
I also should have mentioned this in the summary, but this is my first meaningful Rust code besides random side projects, so feel free to be extra nit-picky with your comments 😄

Okay, it's probably fine to just proceed with this rule on its own. Left a few comments!

@charliermarsh Okay this is ready for another pass. All of your comments should be addressed. I also updated some of my destructuring statements to use .. so that unused values weren't just destructured into _ variables. I think it made it easier to read, but happy to change it back if it's not the preferred style.

authors: AlexBieg charliermarsh


text:
Does uv provide package handling for multiple code locations?

I would like to switch to uv, however Im running dagster that have multiple code locations with some common dependencies but some are only there for one project some only the other, they are now listed in 2 req.txt files:
Location A:
dagster==1.7
dagster-dbt==0.23
pandas==2.1.4

Location B:
dagster==1.7
dagster-dbt==0.23
pyarrow==16.0.0

Is it possible to set this with only one pyproject.toml file?
Something like this:
Common:
dagster==1.7
dagster-dbt==0.23

Location A:
pandas==2.1.4

Location B:
pyarrow==16.0.0

Im open to suggestions if this looks completly wrong.
Also i dont necessarily want to have multiple .python_version files as python is always the same for all locations

By code locations, do you mean indexes, like PyPI?

No, sorry. This is a dagster concept, basically they are just different folders, with seperate requirements as seen above but still in one project

Sounds like https://docs.astral.sh/uv/concepts/workspaces/

We don't let you define the common dependencies in the workspace root yet though

I looked at this, but we have conflicting dependencies, so i see that i should use path dependencies. However its not super clear for me how to use it based on the example in the documentation. Do you have any more examples?

authors: GellertPalfi charliermarsh zanieb

repo: astral-sh/uv


text:
Adding documentation for handling LSP import error when using packages from workspaces

Consider the following directory structure, in this example, I have a llm package in the workspace.
.
├── README.md
├── hello.py
├── packages
│   ├── llm
│   │   ├── README.md
│   │   ├── pyproject.toml
│   │   └── src
│   │       └── llm
│   │           └── __init__.py
├── pyproject.toml
├── src
│   └── saral_backend
│       ├── main.py
│       ├── routes
│       │   ├── __init__.py
│       │   └── notes
│       │       ├── __init__.py
│       │       ├── models.py
│       │       └── route.py
├── tests
└── uv.lock

When I try to import this package in my src/saral_backend/main.py I get the reportMissingImports Error from basedpyright (or other LSPs). This error is correct as the package llm is not yet installed and once I install the package in the same virtual environment the error goes away.
It would be nice to have this documented along the lines of "packages in the workspace needs to be installed in the same virtual environment for the LSPs to correctly resolve them".
Also I couldn't find any mention of installing local packages. Currently what I do is cd into the package directory and run uv run (without any argument), this seems to build the package and install it but it also generates a message "Provide a command or script .....". Not sure if using uv run is the right way to install local packages in the virtual environment.
(I can take a stab at the documentation, if you can point me in the right direction)

yes, using the hatchling build system. I think this gets added automatically when I do uv init --package
Following is my main pyproject.toml (in the root directory)
[project]
name = "saral-backend"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.13"
dependencies = [
    "asyncpg>=0.30.0",
    "fastapi[standard]>=0.115.5",
    "psycopg2>=2.9.10",
    "pydantic[email]>=2.10.2",
    "sqlmodel>=0.0.22",
    "uvicorn>=0.32.1",
]

[project.scripts]
app = "saral_backend.main:main"

[dependency-groups]
dev = [
    "pytest>=8.3.3",
]

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[tool.hatch.build.targets.wheel]
packages=["src/saral_backend"]

[tool.uv.workspace]
members = ["packages/saral-utils", "packages/llm"]

And this is my toml file from llm package
[project]
name = "llm"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
authors = [
    { name = "mohit sharma", email = "mohitlakshya@gmail.com" }
]
requires-python = ">=3.13"
dependencies = []

[project.scripts]
llm = "llm:main"

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

I don't think hatchling will use the packages directory by default, so maybe you need
[tool.hatch.build.targets.wheel]
sources = ["src", "packages"]

I'm not really sure on the specifics of how to configure hatchling's editable installations though.

Thanks @zanieb , I tried your suggestion, but it didn't help. I made the changes to main pyproject.toml  (file in the root directory). I get the following error, when I attempt to build my main package.
ValueError: Unable to determine which files to ship inside the wheel using the following heuristics: https://hatch.pypa.io/latest/plugins/builder/wheel/#default-file-selection

The most likely cause of this is that there is no directory that matches the name of your project (saral_backend).

At least one file selection option must be defined in the `tool.hatch.build.targets.wheel` table, see: https://hatch.pypa.io/latest/config/build/

As an example, if you intend to ship a directory named `foo` that resides within a `src` directory located at the root of your project, you can define the following:

[tool.hatch.build.targets.wheel]
packages = ["src/foo"]
error: Build backend failed to build wheel through `build_wheel` (exit status: 1)

Then I tried with the suggestions suggested by error message, I used the full path as in:
[tool.hatch.build.targets.wheel]
# packages=["src/saral_backend"]
# sources = ["src", "packages"]
packages = ["src/saral_backend", "packages/llm/src/llm", "packages/saral-utils/src/saral_utils"]

With this I am able to build my main package. I can see that the entire packages directory is included in the tar file (in the dist folder). However, when I do uv pip list to see the packages installed in the virtual environment, I don't see the two packages in the list. When I do uv run --all-packages, it installs all the packages in virtual environment from the workspaces.


text:
Add astria-merkle to specs

Right now our merkle tree implementation is thoroughly documented through doc strings. It might make sense to also add it to our specs.

This issue is stale because it has been open 45 days with no activity. Remove stale label or this issue
be closed in 7 days.

This issue was closed because it was stale

authors: SuperFluffy joroshiba

repo: astriaorg/astria


text:
Fix example_batch  DAG to check for job queue status.

In example_batch.py was failing at certain times because disable_job_queue_func was not waiting for the job queue to be disabled.  This PR adds a check for the job queue to be disabled before it moves to the next task.
closes #413

https://github.com/astronomer/astronomer-providers/pull/500

PR title needs to summarize the change you are doing. Can you please correct it?

PR title needs to summarize the change you are doing. Can you please correct it?

Updated the PR title.

not there yet. It needs to be concise.

PR title needs to summarize the change you are doing. Can you please correct it?

Updated the PR title.

not there yet. It needs to be concise.

Changed it again.

repo: astronomer/astronomer-providers


text:
Generate polygon region using MOCpy

We are using HEALPy's query_polygon because it validates that the polygon is convex, and fine filtering using lsst.sphgeom requires it. Trying to migrate away from HEALPy, we should check if we can replace it with MOCpy's implementation - from_polygon - and handle the validation differently.

Closed by https://github.com/astronomy-commons/hats/pull/415.

repo: astronomy-commons/hats


text:
isolation criteria

is there any other point within a given sphere?
is there any other point within a given cylinder?
Is there any point passing a boolean criteria (logM1 < logM2 + 0.5) within a given sphere? cylinder? (Riff on Duncan’s wfunc MCF structure)

Very closely related to #238
CC @duncandc

simple isolation determination is done--to be included in next pull request.  The marked version has yet to be coded up.

authors: aphearin duncandc

repo: astropy/halotools


text:
Add Future::join and Future::try_join

Addresses #470 .
@yoshuawuyts Regarding the module level documentation changes, is the plan to replace join! and try_join! in the documentation with join and try_join ?

I like this change. 👍
To be honest, I don't find join! and try_join! all that useful nor expect those macros to pop up in practice. It seems a lot of people are confused by future joining in general (see here).
Instead, I expect people will spawn futures to make them run in paralle/concurrently rather than joining futures.
wdyt, @yoshuawuyts?

@stjepang you might be right actually. Agree we can probably remove them without much loss.

I have changed the reference to join! and try_join! in the module documentation to refer to 'join' and 'try_join` functions instead.

@yoshuawuyts @portgasd666 In that case, let's also remove macros join! and try_join!? :)

authors: portgasd666 stjepang yoshuawuyts

repo: async-rs/async-std


text:
fix: fixing caching on windows machines

Description
The build process passes the entire Test NodeJS PR pipeline.
Related issue(s)

Fixes #1349

Maintainers, as mentioned in the issue, I tried fixing the caching issue on Windows machines by conditionally checking the npm cache. But a certain substep is failing which passes on other machines. It would be great if someone could point me in the right direction about what is going wrong.
Fix till now:

Failed subprocess

Link to the workflow: https://github.com/helios2003/cli/actions/runs/8624914219/job/23640659229?pr=1

I think it is fixed @helios2003 with https://github.com/asyncapi/cli/pull/1340

I tried running the earlier workflow and apparently, it doesn't pass the same subprocess and also it fails the macOS workflow.
Link: https://github.com/helios2003/cli/actions/runs/8626561222/job/23644917594?pr=2

Hi @Souvikns, thanks for the quick reply. I tried running the earlier workflow and apparently, it doesn't pass the same subprocess and also it fails the macOS workflow. Link: https://github.com/helios2003/cli/actions/runs/8626561222/job/23644917594?pr=2

Yeah, I saw this in other PRs as well, does not look like it is occurring due to cache though.

Oh okay, so can I try to fix the errors in this https://github.com/helios2003/cli/actions/runs/8626561222/job/23644917594?pr=2

@helios2003 it is not caching
it is because one script is still not modified to support windows
just revert your change and update https://github.com/asyncapi/cli/blob/master/package.json#L143 script from printf command to below node script
node -e \"const fs = require('fs'); fs.writeFileSync('scripts/README.md', '# Usage\\n\\n<!-- usage -->\\n\\n# Commands\\n\\n<!-- commands -->\\n');\"

/rtm

authors: Souvikns derberg helios2003

repo: asyncapi/cli


text:
Broken links to customization

I dont know where the links were supposed to lead so I cant fix it.
BTW is there a tool to check all the links in the documentation? Would be a neat thing (Issue in .github).
https://github.com/asyncapi/modelina/blob/d72f11fda764b4eeaa0fe83f2c25279ed37b0da8/docs/generators.md?plain=1#L36
https://github.com/asyncapi/modelina/blob/d72f11fda764b4eeaa0fe83f2c25279ed37b0da8/docs/generators.md?plain=1#L37

@jonaslagoni  Is this issue still valid?
I would take this issue,

repo: asyncapi/modelina


text:
chore: merge master into next-major-spec + fix bug in bundler

Description
This PR, besides merging master into next-major-spec, does the following:

Fixes a bug in the bundler to -without-$id where $ref pointing to definitions without .json extension fail. For example, "$ref": "http://asyncapi.com/definitions/3.0.0/operation.json#/properties/title" like the OperationTrait in v3 has now
It adds support for bindings $id to without-$id transformation. For example http://asyncapi.com/bindings/mqtt/0.1.0/operation.json to bindings/mqtt/operation.

Both matching are now done through regex, since there is no easy silver bullet solution without doing tons of hacks.
Pinging @derberg who made the changes in the bundler for creating schemas without $id. So I expect you can review my last commits where the fix is done.

Warning
Manually merge and not rebase!

@derberg @jonaslagoni  I need some help debugging what's the issue with the produced 3.0.0-without-$id.json.
Here you can find the validator error: https://www.jsonschemavalidator.net/s/3OO3lvSb

Could not resolve schema reference '#/operation#/properties/title'. Path 'definitions.operationTrait.properties.title', line 4675, position 26.

Interesting, it is only with operationTrait, not a serious stuff imho
the oryginal schema has http://asyncapi.com/definitions/3.0.0/operation.json#/properties/title and the no-id bundler is dummy and replace http://asyncapi.com/definitions/3.0.0/operation.json with a local reference. So simple fix is just have an if that if there is a url with anchors, then not only http://asyncapi.com/definitions/3.0.0/operation.json but http://asyncapi.com/definitions/3.0.0/operation.json# should be replaced new local reference so it looks like "$ref": "#/definitions/operation/properties/title"

"$ref": "#/definitions/operation/properties/title"

@derberg The issue is with JSON pointer here and the fact we should scape / characters with ~1, which doesn't look pretty good from DX perspective.
I decided to use - instead now (See the last commit I pushed). For example,http://asyncapi.com/bindings/http/0.1.0/message.json in regular file is bindings-http-0.1.0-message in -without-$id file.
I also added support for testing and validating the schemas without $id which was not added before.

@smoya I don't get why you need ~1? we use it in parser-js only if we need to handle encoding of / in the channel names that may have it. But in case of stuff like "#/definitions/operation/properties/title" there is no need to do any tilde encoding really 🤔

@smoya I don't get why you need ~1? we use it in parser-js only if we need to handle encoding of / in the channel names that may have it. But in case of stuff like "#/definitions/operation/properties/title" there is no need to do any tilde encoding really 🤔

My bad for the confusing explanation. Gonna try again.
1. Bug with #/operation#/properties/title
The issue was that the extra # was not required. That's fixed, and now it is #/operation/properties/title.
2. Bug with definition ids with / characters
Ids can have extra / characters. That's the case for the bindings, for example, where you can find things like http://asyncapi.com/bindings/mqtt/0.1.0/operation.json.
If we convert that to bindings/mqtt/0.1.0/operation, then references will need to use ~, such as "#/definitions/bindings~1mqtt~10.1.0~1operation". Otherwise, the JSON Pointer will try to find in the path definitions.bindings.mqtt.0.1.0.operation. Meaning it will only work if a definition like the following is in the file (which is not our case):
 "bindings": {
            "mqtt": {
                "0.1.0": {
                    "operation": {
                        "type": "object"
                    }
                }
            }
        },

"0.1.0

ah yeah, makes a lot of sense

authors: derberg smoya

repo: asyncapi/spec-json-schemas


text:
[BUG] Improper alignment of case study cards in case studies page

Describe the bug.
The cards are not aligned at the center of the screen.
Expected behavior
All cards should take up equal space, maintaining consistent vertical alignment for a balanced layout.
Screenshots

How to Reproduce

Go to the case studies page
Check the adeo And HDI cards, these are not aligned properly within the grid

🥦 Browser
Google Chrome
👀 Have you checked for similar open issues?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

can i fix the bug

@Kalprajsinh I appreciate your contribution, but I noticed you've resolved the issue I created and was already working on. I kindly request you to delete your pull request. In the future, please consider raising your own issues and working on those instead.

Each individual card is actually taking up 1/3rd of the horizontal available space. Since there are only 2 cards, the alignment looks like it isn't proper, even though it is technically.
Closing this as this is a design choice to include 3 cards in each row.

repo: asyncapi/website


text:
Create multiple web driver instance in same process

It's difficult to handle multiple tab/window in one web driver instance in Selenium/Atata. I have an idea to create each web driver instance for each window/url and process in parallel. Is that possible for Atata? Do you have an example to implement that idea?

A late response, but anyway here is the sample: Atata Samples / Multiple Browsers in Test.

authors: YevgeniyShunevych siquylee

repo: atata-framework/atata


text:
🛑 Wedding HTTPS is down

In 2aa542a, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 7616773.

repo: atatkin/milos-uptime


text:
🛑 Wedding HTTPS is down

In 4c54974, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 54aa8a2.


text:
🛑 Wedding HTTPS is down

In ad2f126, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in e816713.


text:
🛑 Wedding HTTPS is down

In b014076, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 658c8f2.


text:
🛑 Wedding HTTPS is down

In df1958b, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 976ffc4.


text:
interceptor.request calls twice for one interceptor

Hi there,
I am not really familiar with a topic of how angular handles interceptors however maybe someone met a similar issue and may help. I have a couple of interceptors pushed into $httpProvider. One of them runs an application spinner which increments a counter of requests per each request and deducts the counter after response. What the protractor-http-mock plugin intends to do is to call interceptor.request per each interceptor it finds. But does that mean that spinner interceptor should trigger its request callback twice after overrides of the plugin?
Thank you!

Hi @Mishurin , just recently I published a new version of the package that includes some changes on how stateful interceptors should work. Please try it out. Hopefully that solves your problem.

authors: Mishurin atecarlos

repo: atecarlos/protractor-http-mock


text:
Issue with knob slider in Ionic Meteor

I have loaded this plugin on my Meteor Ionic project through the normal instructions. The plugin registers the knob but the input area is showing off screen for some reason. It appears the CSS styling for margin-left is pushing it off the screen. I have attached 2 screenshots and if I remove the margin it shows on the screen. My JS code for initializing the knob dial is
Template.knob.rendered = function () {
	// initialise the knob slider
	$(".deposit-dial").knob({
		stopper: false,
		min: -50,
		max: 50,
	  	format: function (value) {
	     return '$' + value;
	 	}
	});
};

Is there a way to override the generated CSS somehow. Bit puzzled as to why its adding a margin-left to the input though

Having a similar problem... Did you find any solution @akhatri ?

Not sure if it helps, but I added a callback to override styles.
In jquery.knob.js, add:
this.o = $.extend({
    ...
    style: function(el, d) {}     // <- new

and
this.init = function () {
    ...
    this.o.style(this.i, this);    // <- new
};

Then in your app:
element.knob({
    'style': function(el, d) {
        el.css({
            'top': 'inherit',
            'left': 0,
            'right': 0,
            'margin-left': 'auto',
            'margin-right': 'auto',
            'margin-top' : -(d.w / 1.5) + 'px',
        });
    }
});

authors: akhatri dunksmith jhedev

repo: aterrien/jQuery-Knob


text:
make files contain html5 doctype

replaced outerHTML en jsDOM with serialize() as outerHTML strips the <!DOCTYPE>.

Very noice

authors: atjn gustavcorpas

repo: atjn/easy-web-app-builder


text:
connection handler is sending the breakdown twice for the SDX LC

Hi,
I believe this error was introduced by PR #226 , which ended up sending the breakdown connections twice for the SDX LC:
https://github.com/atlanticwave-sdx/sdx-controller/blob/main/sdx_controller/handlers/connection_handler.py#L159-L160

@congwang09 would you please take a look on this and #229 when you get a chance.
That PR for refactoring probably created the bug.

authors: YufengXin italovalcy

repo: atlanticwave-sdx/sdx-controller


text:
Add autoStart feature

These changes introduce a global autoStart configuration option, that when enabled, will schedule and manage lazy component loaders automatically. This ultimately removes the need to have useLazyPhase and will close https://github.com/atlassian-labs/react-loosely-lazy/issues/67.
Changes

Add autoStart global configuration, and associated documentation
Add an internal useScheduler hook and associated tests, which is used in the client lazy component
Introduce @testing-library/react-hooks to test the scheduler
Handle autoStart configuration in the client lazy component, by scheduling the deferred task inside of a useLayoutEffect (more discussion and rationale here: https://github.com/facebook/react/issues/20090#issuecomment-716652603), and add corresponding tests
Add more lazy client unit tests, which captured an issue with the preload deferred logic with retry (fixed in the PR)
Move client fallback logic to a custom hook, with the existing placeholders
Test autoStart in root and LazyWait integration tests

Notes

autoStart handling is performed in the component render, which ensures that the behaviour is consistent in the case where a lazy* factory is imported and evaluated before init. So long as the init is called before React render, this should be obey the rule of hooks and work as expected.

Sorry this never got merged... Anyway this behaviour plays well with React 18 Suspense + concurrent mode, as deferred components should not remain dead for long as might cause hydration to break, so we should hydrate them asap (but still makes sense to have some priorities).
Also, I think we should make autoStart work without a configuration. Basically we enable it by default, but if somewhere we use useLazyPhase, we turn it off. Should be doable as the component with useLazyPhase should run before afterPaint components are scheduled to load, what do you think?

authors: MonicaOlejniczak albertogasparin

repo: atlassian-labs/react-loosely-lazy


text:
CLIP-1567: Make synchrony pod and service annotations configurable

This PR makes it possible to redefine:

pod annotations for synchrony. If undefined, .Values.podAnnotations is used
service annotations for synchrony. If undefined, .Values.confluence.service.annotations is used

Fixes https://github.com/atlassian/data-center-helm-charts/issues/398
Checklist

[x] I have added unit tests
[x] I have applied the change to all applicable products
[x] I have added the change description to the changelog.md and Chart.yaml files
[ ] (Atlassian only) I have run the E2E test (if applicable)
[ ] (Atlassian only) Internal Bamboo CI is passing

Approved but left some comments to consider before merging.

repo: atlassian/data-center-helm-charts


text:
Compile an end-to-end tutorial to deploy to Xen

There should be a tutorial for building a hello world program and deploying it to Xen.

There's now a "Running locally with Vagrant" tutorial which covers this!
https://github.com/atmanos/atmanos/blob/master/doc/running-locally-with-vagrant.md

repo: atmanos/atmanos


text:
Some linter changes

To be consistent with core I am proposing two things:

Requires not wrapped in parens fs = require('fs') -> fs = require 'fs'
Only allow double quotes on strings in spec describe and it methods. They often contain contractions and generally '. We have taken to using double quotes in this case. Also the coffee de and i snippets generate specs with double quotes.

The following should be prefaced by my general desire to get to a coffeelint.json which enforces core standards. In this, I defer entirely to you.

Requires not wrapped in parens fs = require('fs') -> fs = require 'fs'

What's your opinion on ( ) for function invocations? We could have a custom rule that allows require 'fs' but doesn't allow myPack.doThis withThat. I find the latter (while idiomatic CoffeeScript) poor from a readability perspective.

Only allow double quotes on strings in spec describe and it methods. They often contain contractions and generally '. We have taken to using double quotes in this case. Also the coffee de and i snippets generate specs with double quotes.

It's easy to '' or use cannot in place of can't, etc. Wouldn't it be better to change the de and i snippets to generate specs with single quotes? (I realize the absurdity of that suggestion, fwiw).

Per the prior statement, please feel free to update coffeelint.json to match the core standards - they are what matter, in particular for this project. It currently reflects my standards, which are not yours, and consequently lower in priority :smile:.

Interestingly, coffeelint is smart enough on the double quote rule to allow double quotes when you use ' (to avoid escaping). So yeah, the issue is the snippets generate " by default. Should they?

See also: https://github.com/atom/language-coffee-script/pull/49

What's your opinion on ( ) for function invocations?

In most cases, I agree with you. There are a couple cases where we use naked function calls:

requires
spec matchers. So expect('a').toBe 'a'
when there is a function or object at the end of the call

On the quote front, I totally agree with nathan's comment: https://github.com/atom/language-coffee-script/pull/49#issuecomment-72698786

I toned down the coffeelint.json config, and have it warning now. I need to write a few custom rules to allow naked requires, naked spec matchers, and double quotes in specs. It already permits when there is a function or object at the end of the call.
Once the rules are there, I will ignore implicit parens and double quotes, and use the custom rules instead.

authors: benogle joefitzgerald

repo: atom-community/autocomplete-plus


text:
アップデートが必要とマックは言っている

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Steps to Reproduce

Expected behavior:

Actual behavior:

Reproduces how often:

Versions

Additional Information

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:

repo: atom/atom


text:
Arrow Key Behaviour over tabs & spaces

I’m not sure how to categorize this issue, or whether there’s a setting or a fix for it.
Personally I prefer to use tabs instead of spaces for my own reasons, and have set that in the options.
When I edit an existing document with spaces, I find that left & right arrow keys skip over 4 spaces at a time. This gives me the false impression that the document uses spaces. It also means that I end up mixing tabs and spaces.
I know that I can view invisibles to see what is happening.
Is it possible to set the arrow key to move one space at a time?

@darangi Why?


text:
Error checking for updates immediately after updating Atom

After Atom updates (and restarts), immediately attempt another update. The error message is displayed.
After waiting a few minutes, the update check succeeds.

Could be related? https://github.com/atom/atom/issues/8265

I also saw this today, was at version 1.0.5, a few minutes later I checked again and it downloaded 1.0.6 successfully.

Updated from 1.7.4 to 1.8.0 and attempted to immediately update again. I did not receive the "There was an error checking for updates." message, and instead received an accurate "No update available" message. I believe this issue can be closed.

@parasyte @rick Are you still experiencing this?

I have not seen this recently.

Ok, in that case I'm going to close this issue until it can be reproduced again.

I got this today after updating last week (either to 1.17.0 or 1.17.1), but mine didn't have the "(null)" at the end of the message.  This only appeared once, then didn't see it again. However, Atom kept telling me there was an update available (blue circle icon), but on the About screen, clicking Check for Updates told me 1.17.0 was the latest.
I then manually downloaded Atom 1.17.2 today, opened it, and got this message again ("There was an error checking for updates...").
A few minutes later (as I'm typing this), I get "Editor is not responding" (from MacOS I assume).  After I clicked, "wait for response" (or whatever the button was), clicking any of my open panels have no response. Menus open, but do no response on any action I click.  I had to request a Quit via Activity Monitor, then got the "not responding" message again and closed it.
After restarting, all my previously open panels/files are cleared, and checking for updates says 1.17.2 is the latest (which it is).  I do wonder though if I'll have the same issue when a new version of Atom comes out.  Unfortunately, reinstalling the application (copying Atom.app into Applications) didn't fix the issue this last time, so there must be something corrupted elsewhere. Thoughts?

I am having the same experience as @pydolan, except when updating from 1.17.2 to 1.18.0.

:wave: @pydolan or @tjkohli would you mind opening a new issue?  It sounds like what you're experiencing is slightly different from what was reported in this one.

@50Wliu No, it was the same exact error and steps. But I want to note that once you click "Restart to Update" or something similar on 1.17.2, it quits Atom for a long time. If you manually launch Atom again, you get the error described above. But if you wait a minute or so, 1.18.0 launches and updates successfully. That's how I resolved it.

@tjkohli sounds like you're running into https://github.com/Squirrel/Squirrel.Mac/issues/124?

I'm running to the same error now on 18.

yep, just downloaded linter and updated all packages and got same thing (el capitan)

Apparently Atom has an installer which runs in background without any user feedback. When I tried to start Atom before it was finished - the "Error checking for updates" came up. My solution was to punch the "Restart and Install Update" and wait patiently for a minute or so while watching my empty desktop. Eventually an updated Atom came up automatically.
In my opinion this is an UX error. Atom should have some sort of an update progress notification.

@mdanetzky Yep - this is mostly out of our hands.  See Squirrel/Squirrel.Mac#124.

@mdanetzky I agree. I think the easiest solution would be to warn the user that it may take up to a minute before the application is restarted. I initially thought the installation failed or the updated application was unable to launch for some reason.

I saw this issue pop up today when trying to update.
Atom Version: 1.18.0
MacOS Version: 10.12.6

As Azazw as d xx zezea<<¢a,a,aa
As atssazdzdz
On Aug 9, 2017 10:05, "Ryan French" notifications@github.com wrote:
I saw this issue pop up today when trying to update.
Atom Version: 1.18.0
MacOS Version: 10.12.6
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/7854#issuecomment-321150252, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPB8dfHJODcvdoqsEaW8aWqGLXpbau_ks5sWTcQgaJpZM4FW3I3
.

I experienced this issue today, as well, when re-opening Atom:
Atom: v1.18.0
MacOS: v10.11.6

@d3r1v3d @vilaskumkar @ryanlloydfrench You guys realize there is no "bug" here, right? It's just a usability issue. Atom takes a while to reopen after installing update and there is no way to know what it's doing. If you open it manually during that period, it will fail. Just be patient, and it will load up. Takes about 90 seconds.

@tjkohli I let it run for an hour and it hung. That qualifies as a bug to me... Comes back up every time I reopen Atom.

@d3r1v3d But did you attempt to launch Atom at any point while it was updating?

@tjkohli This is a bug as the "update" progress has no kind of visibility to the user. The user has no way of knowing. The application will boot up and work just fine (though it will show that error message in the process). What you call a "usability" issue makes the application function weirdly, so in other words, this becomes a "bug." The error message is unclear. To me, it looks like a permissions issue. I didn't even know an update was in progress.

@50Wliu Please reopen this. This is a valid issue and can be reproduced every time.

To everyone who has commented on this ticket in regard to manually restarting Atom during an update; please file another ticket. This one is related to checking for updates after an automatic restart completes successfully.

@tjkohli Can you give a set of steps to reproduce the problem here?

@lee-dohm Although I need an Atom update for it to happen, and I've learned to avoid it, basically the steps are:

macOS (happened in 10.12, I haven't triggered it in 10.13 yet)
Check for updates on Atom, install them.
Atom quits
Atom takes a long time to restart
In the meantime, it seems as if Atom has crashed
Attempt to relaunch Atom (clicking Dock icon, Spotlight, whatever)
Receive update error, and you notice the update install also failed

On the contrary, if you don't do anything around steps 4-5, and just wait a solid 30 seconds, Atom comes back up no problem. This is somewhat of a usability issue more than an actual bug. There should be some sort of communication to the user telling them that the update may take a while. You could also disable relaunching of Atom while it is updating.

@tjkohli So if I understand correctly, at a high level you have to:

Have an update available
Check for updates and immediately install and relaunch
Launch Atom while it is still updating
Check for updates again and get the error?

@lee-dohm That is what triggered it last time I reported it. I'll report back next time there is an Atom update.

authors: 50Wliu F1ks3r Stanzilla arrygoo d3r1v3d erchen ikari7789 lee-dohm mdanetzky parasyte pydolan rick ryanlloydfrench tjkohli vilaskumkar


text:
Provided and Consumed services out of order?

Today I upgraded Atom to 1.0.3. Immediately, I found out that packages that I wrote, that provides and consumes services, were breaking.
I found out that in Atom 1.0.0 (or maybe I've been lucky), when I added package dependencies, all my "providedServices" were being fired BEFORE the package that consumes them is activated. I still think this is the "correct" behaviour, but in 1.0.3, this changed - so, the consumer was activated, commands were ran, and only then the packages that provided that service were being fired.
Is this expected? Or is this somehow a bug? Is it changed on Atom 1.0.3? If so, can we update the package documentation, or add an entry on changelog?

Just to add more info, I've added some console.log to check what's happening.
On Atom 1.0:
provide Object {name: "dependencies", onStart: function, function: function, shouldRun: function}
provide Object {name: "rails-i18n", function: function, shouldRun: function, onStart: function}
provide Object {name: "redmine", onStart: function, shouldRun: function, onQuery: function, onStop: function}
Consumer Activated

On Atom 1.0.4
Consumer Activated
provide Object {name: "dependencies", onStart: function, function: function, shouldRun: function}
provide Object {name: "rails-i18n", function: function, shouldRun: function, onStart: function}
provide Object {name: "redmine", onStart: function, shouldRun: function, onQuery: function, onStop:

It's exactly the oposite...
Tested on Ubuntu 14.04, Same machine on both tests (just downgraded Atom, tested, then upgraded Atom and tested again).

In 1.0.3 services were made async. Can you paste a link to your code? cc @maxbrunsfeld

This where the code: https://github.com/mauricioszabo/atom-everything/blob/master/lib/everything-view.coffee
The problem was on line 162 - it called onStart to initialize providers, and then called, on line 139, it called another function on the provider. So, previously, everything worked as expected - when my consumer was initialized, all the providers where already fired. Now, it doesn't work like this.
This is not really a problem - the real problem is that, in 1.0.3, services were made async, but this was not informed on release notes. As a plugin creator, it's kinda frustrating to update Atom and then discover that things that were not suposed to break are breaking - without any warning, deprecation info, or such.
Also, this does not follow semantic versioning - Atom have updated a patch information, but added features that broke backwards compatibility. Plus, there is no info that this would even happen - in the docs, there's no information that services are async, or even they were suposed to be one day....

You're right, we should have mentioned this in the release notes.
The order of operations via services was never guaranteed, and in the docs we should have been explicit about this. It is admittedly a bit of an awkward dance to make sure things work independent of order of operations, but it is necessary. In your case, you can collect providers if things arent active yet, or just call  @evr.registerProvider(provider) if the view has been created.

I'm going to close this out. We should make the docs more clear and give some examples of how to deal with the indeterminate order of operations. I have opened an issue over at https://github.com/atom/docs/issues/106 to improve the docs.

I'm already working on a fix, thanks. It's just that Atom is one of the best editors to create plugins/packages, but it loses to almost all other editors in speed, memory consumption, and big file/lines handling. With the 1.0.0 release, I though it would become more stable an feel less like an experiment, but this isn't happening - and that's the reason I wanted to discuss this in this issue.
For me, a simple "changelog" entry would be enough to close this ticket, for now. But I think the core team should be aware that we, package developers, are not expecting things to break in patch updates...

Apologies for the behavior change. Though, I want to be clear that the order of operations was never guaranteed or stated as one way or the other. I think properly documenting this behavior will help future users of services avoid this pitfall.
We are currently working on quality and polish, and will be tacking the performance issues soon.

I know this is already closed, but I've come into an edge-case that raised a flag for me. Sorry for coming back into this issue, but is it really a good idea to make it async?
The edge-case I found is the following: in my Everything plugin, I bind a searcher to a group of providers. So, the user types a query, the searcher fires this query to registered providers, then it awaits for providers to return. I'm trying to implement a "find symbols", like Sublime's, when you type @, it finds the symbols in the current file.
What I wanted to do, thought, is to this "find symbols" to be a consumer of another kind of providers - for now, let's call then "Parsers". This would be incredible for spec files, for instance, when there are no method definitions, but you could navigate through every testcase and every method - you would only need to register a new provider.
Ok, but now, the "Symbols" provider depends on "Parsers", but it cannot know previously how many, and who they are. He will pass to Everything just what he knows it exists, and Everything will show just that - but, of course, a moment later a new Parser is registered, but the provider already sent information to its consumer...
I think this could become a big problem when there are consumers that depends on providers that are consumers too... it breaks a kind of "principle of less surprise", that a user thinks that if his package depends on another, the other will already be loaded. I know it wasn't written anywere, and until now I only thought it would be an ankward dance on my package, but for this new case, I really think it could be a problem.
WDYT? Is is desirable to keep the API as it is, or is it important to discuss this issue a little more? I know there are ways of solving this problem, but I do really think this could become a problem in the future...

@mauricioszabo I'm not sure I'm understanding your use case, but it sounds like in your 'find symbols' package, you want a way to retrieve all the providers of your 'parser' service, on demand. Is that right?
I don't think that services being consumed async should affect this use case at all. I would recommend doing this:
parserServices = null

module.exports =
  activate: ->
    parserServices = new Set

  # This is the `consumedServices` hook for the 'everything.parser' service
  consumeParsers: (parserService) ->
    parserServices.add(parserService)
    new Disposable -> parserServices.delete(parserService)

This way, inside of your onQuery method for the everything.search service, you can use the parserServices set to parse the file using all of the registered parsers.

That's not exactly what I want. What I'm saying is that, with services becoming async, some cases may become impossible to work in the first call. I've opened a discussion on https://discuss.atom.io/t/provided-and-consumed-services-are-now-async-is-it-a-good-idea/19788/2, but I'll explain here too:
The idea is that I have a package, Everything, that have multiple providers. One of them, Symbols is a consumer of other providers too (in this case, I call the providers of Symbols Parsers, because they'll parse the current file and try to find additional symbols that the default Atom parser does not recognize).
What's happening is that Symbols have no way of knowing if it is "already loaded" or not - what's happening is the following case:

I hit a keystroke and Everything opens -> in this moment, Everything is activated too. There are no providers registered.

Some miliseconds later, Symbols activate, and fire the providedServices -> then, Everything catches this fire, registers this provider, and ask for this provider to bring results to the query.

Another miliseconds later, one of the Parsers fire -> then, Symbols register the parser, but it already sent to Everything its results.

Everything has an API to know when a provider sent all the results. I could relax this restriction and permit to a provider to send the results again - but I'll need to invalidate previous results from that provider an re-add them (and it is a lot of work for something that will only bring wrong results the first way that is fired). This was not a problem in version 1.0.0, because these services worked the way we expect - if I depend on some other service, I imagine (and I know this word can be misused) that my dependencies are solved previously.
I really understand the idea that we shouldn't imagine these things, like, that providers will be loaded previously, and in the discussion forum I already talked a little about "Law of Demeter" and such, but what I thing - sincerely - is that this decision to make services async will lead to a lot of work in packages that depends on others by the services API, lots of unpredicted behaviour on packages that have a chain of dependencies - like A -> B -> C -> D, and it's one thing to worry that'll only happen when the package is activated.
What I find most strange in this async behaviour is that we have no way of knowing if all providers of some service that I consume are loaded. In my Everything case, it'll be much simpler if the Symbols provider could wait until all Parsers are loaded before sending the results.
I don't know if this decision to make things async is something that's still open to discussion or not. I really think this could be a problem to package development, and it'll complicate a lot packages that uses services in the first run - after the activation of every provider and consumer, things will be ok (and that's what I find most strange - this complication just for the first time it is toggled). What I'm trying to do is open this to discussion. I'm trying not to be too zealous about this, just showing some other point of view in this case...

What I find most strange in this async behaviour is that we have no way of knowing if all providers of some service that I consume are loaded.

In general, that has always been the case. It is part of the nature of services: there may be multiple providers and consumers at any time, and providers and consumers may appear and disappear at any time, because the user activates or deactivates a package.

Some miliseconds later, Symbols activate, and fire the providedServices -> then

I'm not understanding this part. I get that Everything has an activationCommand, so it is activated lazily when running that command. Why would Symbols activate after running the command?

authors: benogle mauricioszabo maxbrunsfeld


text:
Uncaught BufferedProcessError: Failed to Spawn Command

This only happens when I open up the preferences window. (Or open Atom with the tab from last session actie).
This did not happen until I installed 1.0.5.
Window load time: 1753ms
/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:260 Uncaught BufferedProcessError: Failed to spawn command /Applications/Atom.app/Contents/Frameworks/Atom Helper.app/Contents/MacOS/Atom Helper. Make sure /Applications/Atom.app/Contents/Frameworks/Atom Helper.app/Contents/MacOS/Atom Helper is installed and on your PATH

Duplicate of #7594, please subscribe there for updates.


text:
Add TextEditors to the registry only when opting in

This PR makes it so TextEditors are added to the registry only when they explicitly opt in.
This was mentioned in atom/atom#10851 (where I forgot to include it) to avoid leaking memory due to package authors not calling destroy.
/cc @nathansobo

Maintaining registration across serialization/deserialization is a good idea, but I'd prefer not to add a parameter to buildTextEditor when someone can just call register and get a disposable back that would unregister.

Makes sense, I removed the parameter to buildTextEditor.

:cherry_blossom: :arrow_right: :cherries:

authors: nathansobo wvanlint


text:
Add Microstockr

Microstockr built on Electron

Great, thanks for adding this :ship:

And that app looks awesome, congrats :+1:

Thanks, we appreciate you adding us


text:
Allow synthetic clicks

Hi,
when trying to open a file picker by doing inputElement.click(), nothing happens.
similarly, a API can only be initiated by a user gesture error happens when doing element.requestFullScreen()
it would be nice if there were a way to run javascript in a “user interaction” context.
i found out that we have to basically call UserGestureIndicator gestureIndicator(DefinitelyProcessingNewUserGesture); before executing the code. here is a Qt bug about it

wow, what a pleasant surprise!
i didn’t expect this to be added since no discussion happened at all.
thank you! :bow:

repo: atom/electron


text:
Chrome switches clarification

This page suggests that only a small number of chrome switches are usable with electron (I assumed it was some kind of switch whitelist).  However, I've found that ones not on the list also seem to work (e.g. --in-process-gpu).  Please could you clarify what this list of switches is?  Perhaps it's switches that have been tested to work well with electron?  Are all chrome switches usable in theory?

You may view all chrome switches in https://code.google.com/p/chromium/codesearch#chromium/src/content/public/common/content_switches.cc. However, electron doesn't guarantee all the switches make sense since it's hard to test all these switches. The switches listed in electron's document are well tested and meet most of user requirements.
I think you can try the switch you needed, and see whether it works. If it won't, report back to the community.

authors: bgSosh hokein


text:
OS X: dialog.showSaveDialog: callback not being called when a browser window is passed

dialog.showSaveDialog(BrowserWindow, {
    title: 'A title',
    defaultPath: '/Users/',
    filters: []
  }, function(filePath){
    log(filePath);
  });

log just calls console.log via ipc.
Works with:
dialog.showSaveDialog({
    title: 'A title',
    defaultPath: '/Users/',
    filters: []
  }, function(filePath){
    log(filePath);
  });

From your code you are passing the BrowserWindow class instead of an instance of it?

UGGGGH...... sorry, last night coding. Thanks. Sorry for wasting your time

authors: adam-lynch zcbenz


text:
Provide option to ignore EOL whitespace

Repository.getLineDiffs provides an option to ignoreEOLWhitespace, however it is not passed in the code. Could you please add it as an option?

Yeah I was about to submit an issue for ignoring whitespace. When I go to check in files, I see bogus differences that should not exist. I think the Atom editor is mucking up lines I am not even editing. OK that's a separate problem, but I would like to ignore whitespace changes. For example
git diff -b app/models/plan.rb

Shows exactly the differences that I made, and more specifically,
git diff --ignore-space-at-eol app/models/plan.rb

Also does the same thing.

This issue was moved to atom/atom#17998

authors: lijunle maxbrunsfeld starrychloe

repo: atom/git-diff


text:
Hide tooltips behind panels

Before

After

Fixes https://github.com/AtomLinter/linter-ui-default/issues/51

Going to ping a few theme authors so they can fix this bug in their themes as well,
@silvestreh @jesseweed @ignism @JesseLeite @burntime

I could be wrong on "how things supposed to be", but I prefer the Before screen. And I intend to leave it that way in Nucleus.

At first glance I thought the before and after screenshots were mixed up. In short, these PRs will cause a GUI regression.
I understand that you're attempting to fix a problem in linter related to "stuck" tooltips, but this is not the way to go about it. I can provide some assistance/guidance on alternate, and better, ways of fixing your root problem if you want. But as it stands, I am strongly against these tooltip PRs being merged.

I'm actually curious on this as well, what's the benefit of hiding the tooltip behind the panel?

In this case (I mean the screenshot) I can see how it looks better in the Before screen. But once you scroll up past the limit of the panel you'd have a linter tooltip pointing at something in the panel instead the code.
Here, I made a mockup to better illustrate what I'm trying to explain:

hmm, ok I can see that use case...

You opened my eyes.

Thanks @silvestreh :+1:
That's exactly the problem I intended to fix with this

But the solution is not to implement a hack that causes a regression in the core GUI, because of what is essentially a problem in a community package. This feels backwards, and this would have to be applied to every single (affected) theme.

@thomasjo We could of course patch the themes from our package but this seemed like the best way to go. Currently this is a bug for all tooltip users who use a panel. Doing this in all the themes is gonna be a lot of work I agree but I believe it's the way forward :) Therefore I opened the PRs to the core packages and pinged authors of famous themes
I personally wouldn't call this a regression but a bug fix. This isn't something specific to the linter package, it happens to every single package who uses a panel and tooltips, in other words, every IDE package out there :)

it happens to every single package who uses a panel and tooltips

From what I can tell this is only applicable to persistent tooltips. A tooltip shown on e.g. mouse hover, will not be affected by this. I might be wrong, so feel free to correct me.

The screenshot was taken in the latest linter-ui-default that creates tooltips on mouse hover :)
Even if this wasn't the case, mouse overing the last line would cover at least two messages from the panel which is not the most comfortable experience. Just so you would know, almost all of the IDE packages use persistent tooltips, the mouse hover tooltips in linter-ui-default are unreleased.

@thomasjo the problem here might be wording: the issue is actually with overlays, not tooltips. Essentially, atom-overlay has a higher z-index value than atom-panel-container. Though I'm not sure atom-panel-container has a defined z-index value at all.

almost all of the IDE packages use persistent tooltips

@steelbrain Just because "everyone" does something, doesn't necessarily mean it's a good idea :wink:

the problem here might be wording: the issue is actually with overlays, not tooltips

@silvestreh OK, interesting! But I'm still not convinced it makes sense to hide a GUI element such as a tooltip (which is an actively triggered element), behind a passive element such as a panel or similar.

@thomasjo In this case the "tooltip" (overlay?) is part of the editor content, the panel is meant to be part of the UI. Shouldn't the UI be above the editor content? If you have a better way to accomplish this  the UI is still being rebuilt, so now is the the ideal time to fix it.

@thomasjo I agree with you once more, yet I believe some tooltips (or overlays, in this case) should probably be confined to certain "UI scopes" (I just probably made that up).
Here, I made yet another graphic to compensate for my lack of vocabulary

It seems to me that linter has some information that is tied to a particular segment of code. And this information should not be displayed if the relevant code is not visible. So, we have a few options:

The tooltips can be fixed so that they don't extend outside the boundaries of the TextEditor. While this is uncommon in the case of tooltips, one approach I have seen is that a tooltip can reverse direction when it can't be displayed within the boundaries of the TextEditor. So instead of being displayed below the relevant line, it can be displayed above the relevant line ... but only when showing below would overlap other UI.
The content from the tooltips can be changed to block decorations that expand on hover of the relevant content
The relevant content can be scrolled so that the "tooltip" can be displayed within the borders of the TextEditor

I agree with @thomasjo. If these "tooltips" look like a duck, walk like a duck, quack like a duck, etc ... well, whether you call them "overlays" or not is immaterial. These appear to be tooltips to me and should either work like other tooltips (i.e. always be on top, be small bits of information and most importantly go away reasonably quickly)  ... or the method of conveying the information should be changed to something more appropriate.

Would it be possible to detect if the "anchored/affected line" (in case of Linter, the line that has the error) is scrolled "out of sight" and not visible anymore? If so, we could do this:

Keep atom-overlay overlapping if the anchored line is still visible.
Hide atom-overlay as soon the anchored line is not visible anymore.

Here an example with autocomplete:

This probably should be part of core, so all atom-overlays would behave like that and packages don't have to worry about it.

There is now a new issue in core: https://github.com/atom/atom/issues/11249
@steelbrain thanks for trying to fix it, but I'll close this as wontfix since it would make some packages less usable. Hopefully the "auto-hide when scrolled out of sight" can be added to atom-overlay. Or you could already try to add it to Linter. Not sure how hard it is, tough.

Thanks @simurai! :tada:

authors: Arcanemagus ignism jesseweed lee-dohm silvestreh simurai steelbrain thomasjo

repo: atom/one-dark-ui