Ignore certain warning/error

I am using the clang linter for C and would like to ignore the warning "foo.h not found" as it is not affecting my code. Is there a setting that allows me to do this?

Yes.

hmmmm I added this to my settings file and it doesn't seem to be working.
"ignore_match": [
"file not found",
],

Is the exact text "file not found" part of the error message? Where did you add the setting? It's a linter-level setting, so it should be in your settings for clang, e.g.
{
  "linters": {
    "clang": {
      "ignore_match": [
        "file not found"
      ]
    }
  }
}

I did add the setting there. The exact error I get in sublime is “Error: ‘foo.h’ file not found"
Ryan Rudzitis
On Mon, Apr 6, 2015 at 11:24 PM, Josh Hagins<EMAIL_ADDRESS>wrote:

Is the exact text "file not found" part of the error message? Where did you add the setting? It's a linter-level setting, so it should be in your settings for clang, e.g.
{
  "linters": {
    "clang": {
      "ignore_match": [
        "file not found"
      ]
    }
  }
}

Reply to this email directly or view it on GitHub:
https://github.com/SublimeLinter/SublimeLinter3/issues/236#issuecomment-90337079

Do you get the same error when running the linter from the command line?

How do I do that?

Enable debug mode in the SublimeLinter settings and check the Sublime console log for the command the clang linter executes. Then execute that command from your terminal.

Yes I get the same error on the command line.
Ryan Rudzitis
On Mon, Apr 6, 2015 at 11:43 PM, Josh Hagins<EMAIL_ADDRESS>wrote:

Enable debug mode in the SublimeLinter settings and check the Sublime console log for the command the clang linter executes. Then execute that command from your terminal.
Reply to this email directly or view it on GitHub:
https://github.com/SublimeLinter/SublimeLinter3/issues/236#issuecomment-90347403

Can you post your full Sublime Text log, from startup through the linter run?
Hint: use a fenced code block to make it easier to read here.

reloading Packages/User/SublimeLinter.sublime-settings
SublimeLinter: clang: input.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang output:
<stdin>:1:10: fatal error: 'input.h' file not found
SublimeLinter: clang: input.h ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-x', 'c++', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang: dbg.h ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-x', 'c++', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang: dbgtest.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang: main.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang output:
<stdin>:1:10: fatal error: 'filein.h' file not found
SublimeLinter: clang: make_game.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang output:
<stdin>:1:10: fatal error: 'make_game.h' file not found
SublimeLinter: clang: make_game.h ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang: filein.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']
SublimeLinter: clang output:
<stdin>:1:10: fatal error: 'filein.h' file not found
SublimeLinter: clang: filein.h ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-x', 'c++', '-isysroot/Applications/Xcode 2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk', '-I', '/Users/ryanrudzitis/Documents/cis2500/A1/include', '-I', '/Users/ryanrudzitis/Documents/University/First Year/cis2500/A2/include', '-I', '/Users/ryanrudzitis/Documents/University/First_Year/cis2500/A4/include']

Ah, seems this is either a bug or a deliberate design decision on the part of @aparajita. Patterns in ignore_match are matched against error messages using re.match() instead of re.search(), which means that the pattern must occur at the beginning of the message.
I'll create a separate issue for this and link back here.

Thanks, can you post that link here?

something like '[a-zA-Z0-9_\-]+.h' file not found should cover you in the meantime

I am just going to put in the full path of the header file until this issue (hopefully) gets fixed.

The following should work without hardcoding any paths:
"ignore_match": "'[a-zA-Z0-9_-]+.h' file not found"

No dice. It seems like the linter ignores any other errors or warnings in the c file if an ignore_match entry is not "found".

How do you mean? From your console output, it seems that the only clang errors present are file not found.

If I introduce errors into my file, they don’t get reported by the linter if:

The .h file is not found (presumably because it’s a fatal error)

The situation I described in my previous post

Ryan Rudzitis
On Tue, Apr 7, 2015 at 12:50 AM, Josh Hagins<EMAIL_ADDRESS>wrote:

How do you mean? From your console output, it seems that the only clang errors present are file not found.
Reply to this email directly or view it on GitHub:
https://github.com/SublimeLinter/SublimeLinter3/issues/236#issuecomment-90357237

So without "ignore_match": "'.+\\.h' file not found", errors other than file not found are reported, but with that setting they are not? I'm not able to reproduce this.

My bad, it is getting late. If I have "ignore_match": "'.+\\.h' file not found" and include the full path to the header file, other errors are reported. Without the full path, no errors AT ALL are reported. (With "ignore_match": "'.+\\.h' file not found")

Again, I'm unable to reproduce. Given this code snippet:
void f() {
   printf("%.*d");
}

And this setting:
"ignore_match": "'.+\\.h' file not found"

I get this console output:
SublimeLinter: clang: hello.c ['clang', '-cc1', '-fsyntax-only', '-fno-caret-diagnostics', '-fcxx-exceptions', '-Wall', '-x', 'c++']
SublimeLinter: clang output:
<stdin>:2:4: error: use of undeclared identifier 'printf'

I get the same warning, however if you add at the top of your program include "foo.h" then no errors at all will be reported.

Right, that's expected since clang treats file not found as a fatal error, as you said above.

Which means I am stuck putting in the full path to the header file until the clang linter issue is fixed.

But it has nothing to do with the SublimeLinter plugin. clang itself doesn't report any other warnings after it encounters a fatal error.

Closing issue until further issue is discovered.


.Net core WebAPI with OAuth on IIS

Hello,
I am testing OAuth2 with .Net Core WebAPI. Scenario is like that:

I have ListService with some simple access to SQL Database.

I have AuthService with GetToken methods. Controller looks like this
public class AuthorizationController : Controller
{
 private readonly Logger _errorLogger = LogManager.GetLogger("ErrorLogger");
 private static Logger _auditLogger = LogManager.GetLogger("AuditLogger");

 private readonly SignInManager<User> _signInManager;
 private readonly UserManager<User> _userManager;
 private readonly RoleManager<Role> _roleManager;

 public AuthorizationController(
    SignInManager<User> signInManager,
    UserManager<User> userManager,
    RoleManager<Role> roleManager)
 {
         _signInManager = signInManager;
         _userManager = userManager;
         _roleManager = roleManager;

 }

 [HttpPost("~/connect/token")]//, Produces("application/json")]
 public async Task<IActionResult> Token(OpenIdConnectRequest request)
 {
     // Stuff
 }

 [HttpGet]
 [Route("api/[controller]")]
 public IEnumerable<string> Get()
 {
     // Test Action
     return new string[] { "Token", "XXXXX-XXXXX-XXXXX-XXXXX" };
 }

 [HttpPost]
 [Route("api/[controller]")]
 public IEnumerable<string> Post()
 {
    // Test Action
     return new string[] { "Token", "XXXXX-XXXXX-XXXXX-XXXXX" };
 }

`
And my DI Container Configuration:
   public void ConfigureServices(IServiceCollection services)
    {
        // Add framework services.
        services.AddMvc();

        services.AddEntityFrameworkSqlServer()
    .AddDbContext<AuthSampleContext>(options =>
        options.UseSqlServer(Configuration["Data:DefaultConnection:ConnectionString"]));

        services.AddScoped<UserManager<User>, CustomUserManager>();
        services.AddScoped<SignInManager<User>, CustomSignInManager>();

        services.AddIdentity<User, Role>(o =>
                {
                    o.Password.RequireDigit = false;
                    o.Password.RequireLowercase = false;
                    o.Password.RequireUppercase = false;
                    o.Password.RequireNonAlphanumeric = false;
                    o.Password.RequiredLength = 6;
                }
            )
            .AddEntityFrameworkStores<AuthSampleContext>()
            .AddDefaultTokenProviders();

        services.AddOpenIddict<AuthSampleContext>()
          .AddMvcBinders()
          .EnableTokenEndpoint("/connect/token")
          .AllowPasswordFlow()
          .AllowRefreshTokenFlow()
          .DisableHttpsRequirement()
          .UseJsonWebTokens()
          .AddEphemeralSigningKey();
    }

I am using POSTMAN to see if my controller is working properly. If i run my AuthService on IIS Express form Visual Studio 2015 everything is fine, I got my token. I Published it on IIS via this command:

dotnet publish -c release -r win10-x64
Now when I try to get token I get 500 Internal Server Error. In the same time this service contains sample Values Controler and it works perfectly. I was debugging and logging a lot and what I know for sure that it is something wrong with Dependency Injection. When I commented code like this:
      public AuthorizationController()
       //SignInManager<User> signInManager)
       //UserManager<User> userManager)
       //,RoleManager<Role> roleManager)
       {
            // _signInManager = signInManager;
            //_userManager = userManager;
            //_roleManager = roleManager;
       }

My controller is working fine. Of course only my "dummy"/test actions are working (due to lack of dependencies).
What can be de Issue ? DI Configuration should be different for other IIS version than Express? Maybe there is some kind of bug? I am lack of ideas, I spend 3 days on this. Maybe it is something very easy and I just don't see it.

What was the DI error?
/cc: @HaoK

Can you try using the AddSignInManager/UserManager helpers instead to see if that works?
https://github.com/aspnet/Identity/blob/dev/src/Microsoft.AspNetCore.Identity/IdentityBuilder.cs#L220

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


Add caution to behavior of --from-env-file

Resolves #16729
When creating ConfigMaps using --from-env-file command, the documentation provides a cautionary note and example about unexpected behavior when passing multiple files to the --from-env-file command. However, it it not signaled as a caution in the documentation which is confusing to readers who would otherwise gloss over this important detail, or think of it as a feature.

/lgtm
/approve


Update 'Back up Secret Key' screen

This screen needs to be updated with new design / illustrations:
https://www.figma.com/file/VupGh90FJtT0dcBj2Sh7bb/📏Spec?node-id=80%3A3287
https://www.figma.com/file/VupGh90FJtT0dcBj2Sh7bb/📏Spec?node-id=80%3A3317

This is just a proposal, but I think it'd be better if we'd give more air/clarity to each word:

+1 to boxing each word. Much easier to match order when writing down on paper.

oh this is much better! ❤

@fbwoolf The screen looks awesome, just curious why the 'back up later 'isn't visible on the screen. Attaching the actual implementation vs the Figma draft design below.

@Eshwari007 we have decided to remove that option from the user for now bc the flow for back it up later was never completed.


Adding repository field to pubspec.yaml

This issue was originally filed by @financeCoding

One part of metadata that would be nice for projects to expose outside of their homepage would be repository where the code exits.

This issue has been moved to dart-lang/pub#1108.


[docs][a11y] Add link underlining guidance to UX dot

Now that we've gotten approval to add underlines to all inline links in text blocks on RHDC, let's make this more explicit in our accessibility section--and anywhere else this info needs to be.

Also, the phrase "from assistive tech" needs to be added here on the development page:


updating node version for GH action

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

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Update README.md

Copy paste should just simply work instead of pasting and then removing $ everytime after pasting.

This is needed for the console code block to be formatted correctly


(docs) Update run_* function calls in 'Writing plans' docs

This updates several run_* function calls in the example plans of the
'Writing plans' doc to use a consistent format for specifying plan,
task, and parameter names. Previously, the doc was inconsistent in how
it showed specifying plan, task, and parameter names, switching between
quoted and unquoted names.
This also fixes a run_plan function call that was specifying the
**puppetdb_fact** plan, instead of puppetdb_fact.
!no-release-note

CLA signed by all contributors.


Refactor the implementation of Flow and TypeScript on the BabelConfig

What does this PR do?
Tiny change that will only affect someone extending the BabelConfiguration class: I was doing the TypeScript and Flow checks for plugins on presets on the same method and it was increasing the complexity of the method to the point were extending the class and supporting both of them required copying a lot of stuff, so... refactor.
How should it be tested manually?
This just moves two big if blocks to a different method, it doesn't change anything else, so...
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 241

24 of 24 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 239:
0.0%

Covered Lines:
2132

Relevant Lines:
2132

💛  - Coveralls


Particles angle speed in editor different than in running game [3D]

Godot 3.1.2 and master branch
Operating system: Linux 64 bits
Graphics card: Nvidia GeForce GTX 1050
Description:
In the attached video you can see that the particle rotation on the game screen (right) is faster than in the editor (left). I had to reduce the speed x10 to make it look like the editor.
video.zip
minimal_project.zip
Expected behaviour:
Particle rotation should be the same in the editor and when running the game.

My bad people. This is fixed setting Particles > Time > Fixed FPS


[Issue] : Adding functionality suggestion

Issue Description
Hi, your site looks awesome, but the "Explore More" button is not working. I suggest that this button should point to another component of the site with many articles in the same categories. You can tag me to do this. I would love to help you with this
Are you a Hacktoberfest'21 contributor

[X] Yes, I'am Hacktoberfest'21 contributor

ya sure @kamarel


Preprocessor improvements

Depends on the new solution to #28, so not to be merged until that is.
Introduces an improvement to the preprocessor and instrumentation in
general. The preprocessor improvement is the fix to #32.
The instrumentation improvement derived from how I saw SolCover behaving
with statements immediately following comments.
Previously, we traversed the whole AST, and when we encountered a
statement we checked if we could instrument it i.e. if it was
standalone. This introduced a bunch of cases that we wanted to check
(is it in a block? it is immediately after a block? etc.) and some edge
cases that didn’t work properly (comments).
Instead, we now stop traversing the AST in situations where we know we
can’t instrument, and assume that if we find a statement that we can
instrument it. We can’t instrument f(x) easily (see below) in
these situations, so we don’t traverse them:

if (f(x))
arr[f(x)
var x = f(x)
g(f(x))

Of course, going forward we might ‘decide’ that we can in fact
instrument these. e.g. arr[f(x)] could be replaced by
var _some_unique_id = f(x);
arr[_some_unique_id];

and then instrumented as appropriate.

Those tests all pass locally for me, so I'm not sure what's going on here....

@area the failing tests on CI are because of this PR was just merged at solidity-parser. I pegged SP to master because it had bug fixes that weren't published to npm but that's obviously a bad idea. I think just getting SP off master in the package will run everything clear for this PR. And i'll open another branch right now that makes the changes necessary for SP #57 to work with solcover.

Ah, okay. I'm fine with pinning to master on solidity-parser, but it should probably be a specific commit / tag.

@area Sorry - missed that last comment. I just opened a PR for solcover master that is a temporary patch for the SP problem. I just used the result of npm install solidity-parser which is ^0.2.0. I'll push a change here now but pinned to 0.2.0.

Highlighting is perfect from what I can see. 👍  Really good. I'm looking at  instanbul and solcover reports side by side for a bunch of  if / else / loop code and solcover is actually slightly more accurate.

Rebased, so you'll need to git pull --rebase if you want to work on this branch.

@area  I have nothing to add here. I'll happily write some unit tests for any instrumentSolidity.js lines that aren't getting codecov coverage when you merge this though. Looks really good.


Remove graphql.rebuild_schema() from public API

Instead of rebuilding in a ddl event listener, increment a sequence tracking the schemas version.
Check the current value of the sequence inside the resolve function and, if it differs from the cached schema version, call graphql.rebuild_schema before executing the query.

May be relevant:
On a newly created project, pg_graphql seems to be enabled by default, however it only creates the graphql_public schema.
When toggling the pg_graphql extension off for the first time, an error message is presented saying that the extension could not be found.
Works as expected once the extension is toggled back on.

Thank you
This issue is to remove the need for users to call rebuild_schema. It's an enhancement goal rather than a bug

So is the expected behaviour that the "old" / original schema returns after toggling off than on?

You should not need to toggle the extension off or on
As of last week, pg_graphql is enabled on new projects by default and you can call graphql.rebuild_schema() to rebuild the schema as needed (the permissions issue you previously faced was fixed)

There's a chance I created the project in some interim state, but perhaps have a look at the behaviour of a fresh project on live Supabase platform and inspect the live database with a direct postgres connection to see the issue above.
The UI "extension not found" error popup is triggered only once when disabling the extension for the first time, but still caused an error.

For the first few days of pg_graphql general availability on the supabaes platform the extension was disabled by default. Now it is enabled by default and you can see the public_graphql + graphql schemas immediately after creating a project.
I just confirmed on a new project, but if you see something else, please let me know

@olirice
When running migrations as postgres user on a fresh project (just created minutes ago) I am still getting:

[2022-04-23 20:22:17] 0 row(s) affected in 100 ms
SELECT graphql.rebuild_schema( )
[2022-04-23 20:22:17] [3F000] ERROR: schema "graphql" does not exist
[2022-04-23 20:22:17] Position: 8
[2022-04-23 20:22:17] Undetect Dev: 2 of 1 statements executed, 1 failed in 210 ms

Additionally, this is the UI error presented when turning off the pg_graphql extension for the first time (does not occur after the first time, meaning there is some issue with the setup triggered by new project creation):

When running migrations as postgres user on a fresh project (just created minutes ago) I am still getting:
[2022-04-23 20:22:17] 0 row(s) affected in 100 ms
SELECT graphql.rebuild_schema( )
[2022-04-23 20:22:17] [3F000] ERROR: schema "graphql" does not exist
[2022-04-23 20:22:17] Position: 8
[2022-04-23 20:22:17] Undetect Dev: 2 of 1 statements executed, 1 failed in 210 ms
After toggling the pg_graphql extension off then back on, it behaves normally.

this looks like you're running locally via the CLI. Is that correct?

Migrations are via IDE connected to hosted Supabase instance.
The error is via the supabase.com GUI if that helps?

I can not reproduce that error. As far as I can see, new projects have pg_graphql created by default, the graphql schema exists, and the default graphql request is served without issue
If you're having trouble with initial project setup, please create a new issue so we can keep this issue single purpose.
In that issue please attempt to reproduce the state you're seeing in a new project and send me the project ref so I can investigate
thanks

Not sure if this is related - but I think since this PR dropped, I can no longer access GraphQL requests in Supbase outside of the .resolve() method in SQL (i.e via an IDE like Postman or Altair).
All I get when I run an introspection query is heartbeat - whereas I can query multiple entities using resolve()...  any ideas>

Some debugging:
Via SQL:
select graphql.resolve($$
    {
      usersCollection(first: 1) {
        edges {
          node {
            id
            email
          }
        }
      }
    }
$$);

<EMAIL_ADDRESS>
VIA API:
{
  usersCollection(first: 1) {
    edges {
      node {
        id
        email
      }
    }
  }
}

{
  "data": null,
  "errors": [
    {
      "message": "Unknown field 'usersCollection' on type 'Query'"
    }
  ]
}

@joesaunderson could you please send your project reference? That does sound like a schema rebuilding issue


Issue 242: Update Third Party Library Versions

Signed-off-by: Shashwat Sharma<EMAIL_ADDRESS>Change log description
Few libraries version identified with possible vulnerabilities, this needs to be updated
Purpose of the change
Fixes #242
What the code does
Update the library version with possible vulnerabilities
How to verify it
All test cases should pass, Schema-Registry samples should work with Pravega Samples

@shshashwat could you please provide kind of tests performed on this ?

building and running Schema Registry samples with latest Pravega master is working fine in local

ObjectMapper.Configure is deprecated and as per the JavaDoc new way is to use JsonMapper.builder().configure(...).
Ref:- [https://javadoc.io/doc/com.fasterxml.jackson.core/jackson-databind/latest/com/fasterxml/jackson/databind/ObjectMapper.html](The Javadoc)

Can you give the CVE number for the avro version upgrade and check if version 1.10.0 also works for you. Thanks.

@crazyzhou The changes made here was as per the issue ticket created by Security scan. The suggested version in the ticket is 1.11.0 and hence it's changes here. If there is some backward compatibility related issue you're facing the way I faced here, that should be manageable.


Agents can get into a bad state and not recover

Summary
It would appear agents can get into a bad state and continue to run in that state, stopping traffic from reaching the receiving controller.
When agents get into a bad state, they either need to recover or stop processing traffic. If it's possible to implement a health check on the agents that monitors such conditions we could wire it up in OpenShift and have the pods taken out of service.
We can monitor:

readiness; the pod is ready to receive traffic. OpenShift will only route traffic to the pod when this check passes.
liveness; health condition of the pod (running, etc). OpenShift will kill the pod if this check fails a number of times (all configurable).

Details
Using bcgovimages/aries-cloudagent:py36-1.11-1_0.4.0-alpha
Pod Configuration:

1 - ICIA (Indy Catalyst Issuer Agent) Controller
21 - ICIA Agents
17 - ICOB (Indy Catalyst OrgBook) Agents
16 - ICOB Controllers
This configuration has been confirmed to support a maximum issuance rate of ~2100 credentials per minute.
Data set is 2,090,092 credentials.

The following issues appear after several hours of sustained load.
Seeing a lot of these errors in the ICIA (Indy Catalyst Issuer Agent) Agents;
ModuleNotFoundError: No module named 'aries_cloudagent.protocols.problem_report.messages'
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/transport/inbound/http.py", line 98, in inbound_message_handler
    await self.message_router(body, self._scheme, single_response=response)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/conductor.py", line 318, in inbound_message_router
    parsed_msg, delivery, connection, self.outbound_message_router
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/dispatcher.py", line 65, in dispatch
    message = await self.make_message(parsed_msg)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/dispatcher.py", line 132, in make_message
    message_cls = registry.resolve_message_class(message_type)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/messaging/protocol_registry.py", line 91, in resolve_message_class
    msg_cls = ClassLoader.load_class(msg_cls)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/classloader.py", line 141, in load_class
    raise ModuleLoadError(f"Unable to import module: {mod_path}")
aries_cloudagent.classloader.ModuleLoadError: Unable to import module: aries_cloudagent.protocols.problem_report.messages
2019-11-27 13:56:22,762 aries_cloudagent.transport.inbound.http ERROR Error handling message
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/classloader.py", line 139, in load_class
    mod = import_module(mod_path)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked

Seeing a lot of these errors in the ICOB (Indy Catalyst OrgBook) Agents;
2019-11-27 14:03:15,210 asyncio ERROR Task exception was never retrieved
future: <Task finished coro=<Conductor.complete_dispatch() done, defined at /home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/conductor.py:322> exception=StorageDuplicateError('Multiple records located',)>
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/conductor.py", line 324, in complete_dispatch
    await dispatch
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/handlers/credential_issue_handler.py", line 35, in handle
    context.message
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/manager.py", line 302, in receive_credential
    self.context, credential_message._thread_id, "external"
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/models/credential_exchange.py", line 115, in retrieve_by_thread_and_initiator
    context, {"thread_id": thread_id}, {"initiator": initiator}
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/messaging/models/base_record.py", line 236, in retrieve_by_tag_filter
    raise StorageDuplicateError("Multiple records located")
aries_cloudagent.storage.error.StorageDuplicateError: Multiple records located
2019-11-27 14:03:15,666 aries_cloudagent.task_processor WARNING Task failed: <aries_cloudagent.task_processor.PendingTask object at 0x7f9108579ba8>
2019-11-27 14:03:15,666 asyncio ERROR Future exception was never retrieved
future: <Future finished exception=Exception('Unexpected response status',)>
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/task_processor.py", line 14, in delay_task
    return await task
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/transport/outbound/manager.py", line 224, in dispatch_message
    await transport.handle_message(message)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/transport/outbound/http.py", line 55, in handle_message
    raise Exception("Unexpected response status")
Exception: Unexpected response status
2019-11-27 14:03:31,124 aiohttp.server ERROR Unhandled exception
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 447, in start
    await resp.prepare(request)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_response.py", line 353, in prepare
    return await self._start(request)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_response.py", line 667, in _start
    return await super()._start(request)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/web_response.py", line 410, in _start
    await writer.write_headers(status_line, headers)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/http_writer.py", line 112, in write_headers
    self._write(buf)
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/http_writer.py", line 67, in _write
    raise ConnectionResetError('Cannot write to closing transport')
ConnectionResetError: Cannot write to closing transport
2019-11-27 14:03:39,327 asyncio ERROR Task exception was never retrieved
future: <Task finished coro=<Conductor.complete_dispatch() done, defined at /home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/conductor.py:322> exception=StorageDuplicateError('Multiple records located',)>
Traceback (most recent call last):
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/conductor.py", line 324, in complete_dispatch
    await dispatch
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/handlers/credential_issue_handler.py", line 35, in handle
    context.message
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/manager.py", line 302, in receive_credential
    self.context, credential_message._thread_id, "external"
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/protocols/credentials/models/credential_exchange.py", line 115, in retrieve_by_thread_and_initiator
    context, {"thread_id": thread_id}, {"initiator": initiator}
  File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aries_cloudagent/messaging/models/base_record.py", line 236, in retrieve_by_tag_filter
    raise StorageDuplicateError("Multiple records located")
aries_cloudagent.storage.error.StorageDuplicateError: Multiple records located

This issue was initial discovered yesterday.  Overnight, under load, the agents (21 Issuers, 17 receivers) got into the same state which all but stopped credential processing.

@WadeBarnes The first error is fixed in the refactoring branch (bad path for the problem report module). The second one is odd, when ICIA doesn't get a response to a credential offer does it send a message with the same thread ID?

@andrewwhitehead, @ianco may be able to confirm.


Invalid syntax for untyped backend

Hi!
When generating code for parametrized functions with the untyped backend, the generated syntax contains what seems to be a type annotation that cause a syntax error when bundling the code.
For the given function:
[@genType]
let column = (name: string, render: 'a => React.element): column('a) => {
  name,
  render,
};

The generated code is:
export const column = function <a>(Arg1, Arg2) {
  const result = Curry._2(TableBS.column, Arg1, Arg2);
  return {name:result[0], render:result[1]}
};

Which yields the following error:
    Module parse failed: Unexpected token (9:31)
    You may need an appropriate loader to handle this file type.
    | import * as TableBS from './Table.bs';
    |
    > export const column = function <a>(Arg1, Arg2) {
    |   const result = Curry._2(TableBS.column, Arg1, Arg2);
    |   return {name:result[0], render:result[1]}

Do I need a specific configuration to bundle the output of genType in this case? I checked the demos and can't see a difference with my config.
Thanks :)

@tmattio thanks for the report!
Indeed that should not be generated for the untyped back-end.
Fix coming.

Thanks!


Small changes to Cloudfront settings

Closes #68 and closes #69
Restricts the methods that can access the Cloudfront distribution to GET and HEAD, which are the two methods that are compressed. Should the retrieval server ever need other methods opened up, we can adjust it later.
Also enabled compression for Cloudfront.

This only affects the retrieval server, not the submission server


Workspace contents

Summary: Updates the methods of WorkspaceContents.
Goal: Pair down to reflect former concept as well as required function.
Specifically Includes:

Removal of methods which are unnecessary
-Implementation of remaining methods

This change is

Review status: 0 of 1 files reviewed at latest revision, 4 unresolved discussions.

src/model/workspace_contents.js, line 28 at r1 (raw file):

/**
 * @class Workspacecontents contains a set of positioned blocks

Nit: WorkspaceContents (capital).
Also "and used to initialize an app's workspace" => "to load onto a Blockly workspace upon initialization" ?

src/model/workspace_contents.js, line 49 at r1 (raw file):

    /**
     * Block types in the project's libraries.
     * @type {Array.<string>}

Would it be more useful to have an array of BlockDefinitions instead, since a BlockDefinition would give more information (e.g. the XML)? That way, if we need the XML of an individual block within this WorkspaceContents class we don't need an additional reference to project or something in order to access the XML?
(Not entirely sure myself--or even if there is access to the BlockDefinitions when libBlockTypes is set.

src/model/workspace_contents.js, line 51 at r1 (raw file):

     * @type {Array.<string>}
     */
    this.libBlockTypes = [];

Also, when would this.libBlockTypes be used? I am wondering if having a has() function or other access functions might be useful in this case.

src/model/workspace_contents.js, line 97 at r1 (raw file):

    const workspaceContentsJson = $.extend(true, super.getJson(),
      {'id': PREFIXES.WORKSPACE_CONTENTS});
    return workspaceContentsJson;

I think that there may be worth in having the JSON be a field in this class. We can have a this.json field that executes the $.extend() function within the constructor, so that the jQuery function does not have to be executed every time getTreeJson() is called. That way, this function can just be one like that just does return this.json;.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 4 unresolved discussions.

src/model/workspace_contents.js, line 28 at r1 (raw file):
Previously, chynu (celine choo) wrote…
Nit: WorkspaceContents (capital).
Also "and used to initialize an app's workspace" => "to load onto a Blockly workspace upon initialization" ?

Done.

src/model/workspace_contents.js, line 49 at r1 (raw file):
Previously, chynu (celine choo) wrote…
Would it be more useful to have an array of BlockDefinitions instead, since a BlockDefinition would give more information (e.g. the XML)? That way, if we need the XML of an individual block within this WorkspaceContents class we don't need an additional reference to project or something in order to access the XML?
(Not entirely sure myself--or even if there is access to the BlockDefinitions when libBlockTypes is set.

I didn't think so, since then you'd have to deal with updating definitions as they changed, etc. and it felt a little messy

src/model/workspace_contents.js, line 51 at r1 (raw file):
Previously, chynu (celine choo) wrote…
Also, when would this.libBlockTypes be used? I am wondering if having a has() function or other access functions might be useful in this case.

Scrapped because it had only been used in the (former) isDefinedBlockType(blockType) method

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 3 unresolved discussions.

src/model/workspace_contents.js, line 97 at r1 (raw file):
Previously, chynu (celine choo) wrote…
I think that there may be worth in having the JSON be a field in this class. We can have a this.json field that executes the $.extend() function within the constructor, so that the jQuery function does not have to be executed every time getTreeJson() is called. That way, this function can just be one like that just does return this.json;.

(Discussed) leaving it for now//can add field if the need arises

Comments from Reviewable

 after Very Minor nit.

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

src/model/workspace_contents.js, line 28 at r1 (raw file):
Previously, svouse wrote…
Done.

0: I think reviewable isn't updating correctly or maybe you missed a commit q.q

Comments from Reviewable

No references to the deleted methods in other files? If so,

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


Switch Protobuf library dependency to 3.6.0

PiperOrigin-RevId: 202356935

Closing this... there are more things need to be able to build this old code at head. The build script depends on pip install that ends up having newer things that break the old build environment.


Restart the app if environment variables change

Could be confusing why your changes aren’t having any effect.
Someone should probably test this before merging it 😬
cc @edwardhorsford

I tested this locally, when I make changes to the .env file and save them, nodemon doesn't restart the app.

Thanks for the testing.
I’ve changed it so that it actually works in b7bf675:

Doing this using the existing file-extension-based config doesn’t work because nodemon doesn’t undestand that .env is a file with no name, and an extension of env. So I’ve removed the file-extension-based stuff entirely and rewritten it to use globbing.
Tested locally that:

changing server.js or .env causes the app to restart
changing a file inside node_modules doesn’t cause the app to restart

I have pulled Chris' change locally and confirmed that changing a file ending with .js, .json and .env triggers nodemon to restart the application.

I think all we need is an addition to the CHANGELOG under 'features'

@nickcolley done and squashed into aaf531c

Quick thought, does this affect very first start up after install? The kit creates empty .env at that point, wonder if that triggers restart and if that's a problem

@joelanman no problems from my testing.

Rebased against master.

👍 to merge

Thanks, @quis!


Add sound to notification

Is there anyway to add a sound to the notification?  Ive tried to add through the optional actions, but without success.
Thank you in advance

It depends of your device type and of what you want to do : https://companion.home-assistant.io/docs/notifications/notification-sounds/
so edit the blueprint to what you want

I’m using iOS.  I have plenty of notifications that have sound, but I have not been successful in adding a sound to the blueprint.
Are you suggesting that the Optional Action should work?  If so, it breaks the entire blueprint.
if you’re suggesting to add the appropriate code, which line of the blueprint should it be added?….because I’ve tried everything I can think of.
thank you.

it's a normal notify call : https://github.com/Aohzan/hass-blueprints/blob/main/blueprints/medication_reminder_ios.yaml#L175
you can try it on dev tools

Hello again,Ive tried everything under the sun to add a Home Assistant preloaded sound to the notification…all without success.If you’ve been able to do so, would you please share the code?Thank youSent from my iPadOn Aug 13, 2024, at 9:06 AM, Matthieu Bourgain @.***> wrote:
it's a normal notify call : https://github.com/Aohzan/hass-blueprints/blob/main/blueprints/medication_reminder_ios.yaml#L175
you can try it on dev tools
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

show me what you tried in dev tools


崩溃了

                indirect_symbol_bindings[i] = cur->rebindings[j].replacement;

我也是在这里崩溃的 iOS13 Xcode 11.3


Loading TF Hub modules in tensorflow.js

Hi,
Any chance of supporting loading TF Hub modules in tensorflow.js?
Thanks

Please go through the following link where you can find how to convert tensorflow graph def based models which include [1. TensorFlow SavedModel 2. Frozen Model 3. Session Bundle 4. Tensorflow Hub module] into Tensorflow.js and let me know if it helps!

Hi @kenjitoyama, you are right, it's not a great user experience.
We are currently hosting some TF.js models on TF-Hub, although this is very poorly documented.
For example https://tfhub.dev/google/imagenet/mobilenet_v1_025_128/classification/1 is available as a TF.js model and there is a public API on the TF.js side to load it, see https://github.com/tensorflow/tfjs/blob/f94df0f384130940ba1343900a049f8319f7f51e/tfjs-converter/src/executor/graph_model.ts#L286.
It is clear that the messaging of this feature is very poor and we are currently rethinking about how to improve those.
+@dsmilkov from TF.js.

Please take a look at the new UI, you can find the converted TF.js models for many original models now, for example: https://tfhub.dev/google/imagenet/mobilenet_v1_025_128/classification/1
You should be able to load this (as described on the TF.js tabs) by doing:
tf.loadGraphModel("https://tfhub.dev/google/tfjs-model/imagenet/mobilenet_v1_025_128/classification/1/default/1", { fromTFHub: true })

Cool, that's exactly what I wanted. Thanks, Vojtech!


[App Service]: .NET SDK generated for API version "2021-03-01"

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run

@fengzhou-msft can you please help to succeed the build. We need to use this SDK to work on the breaking changes release.

@dingmeng-xue who can help us get some traction on this PR please? So we can update websites extension in PS to use the latest SDK as part of upcoming release? Thanks!

Hi @ArthurMa1978 , could you help to assign team member to review it.

@ArthurMa1978 Any help is appreciated here.

@fengzhou-msft  and @HarveyLink please help on this PR.

@Kotasudhakarreddy 2 comments and please fix the ci issue

@Kotasudhakarreddy 2 comments and please fix the ci issue

@ArthurMa1978 I looking for help to fix CI issue. I am not sure what is causing the problem.

The pipeline shows there is a extra metadata folder exists, you should remove that folder.
src/SDKs/_metadata/web_resource-manager.txt

The pipeline shows there is a extra metadata folder exists, you should remove that folder. src/SDKs/_metadata/web_resource-manager.txt

@HarveyLink Thanks for the guidance! CI is passed now.

@ArthurMa1978 / @HarveyLink can you please review it.


Another attempt at getting project name from git.

I didn't realize that #14 already existed before I started working on this, so it duplicates a lot of work already done in that PR.
Although it also uses <<LAST_PROJECT>> as opposed to putting all unknown Terminal information in the Terminal project this should I think resolve #17 as well and will better associate time.

Thanks for your contributing.  It's a nice and clean change.
I don't want to break current user behavior (always use Terminal project).  Instead,  can introduce an new environment  like $WAKATIME_ENABLE_PROJECT_DECTION if anyone want to enable this feature.
Let me know if you wanna add this support. Otherwise, I can merge your PR and add this env support.

@wbingli I have added the ability to set ZSH_WAKATIME_PROJECT_DETECTION to enable project detection, also added some documentation in the README file about the new flag.

Awesome job!  Merged, THANKS!


Using Sass with Roots results in "TypeError: Object.keys called on non-object"

This is due to using 0.14.x with the main Roots runtime; updating it to 0.15.x allows Sass to be used.

Whups, wrong queue. Sorry!


Auto-export locks up Zotero during large exports

[x] I have verified in the Zotero addons screen that I have the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero installed
[x] I am posting a single question, bug or feature request
[x] I have included a descriptive subject of the problem
[x] I am available for follow-up questions and testing
[x] If I am posting an export or key-generation related bug report, I have included an error-report by selecting the problematic reference(s), right-clicking, and submitting an BBT error report from that popup menu

Bug classification
Non-export problems with BBT
When the BBT add-on is enabled in Zotero for Mac, most interactions with items in collections result in the app freezing -- 15+ seconds of spinning beachball. When the add-on is disabled, this stops.
In addition, the BBT report error function fails when uploading the report (see screencaps attached). I've copied the text from the report here:
https://www.dropbox.com/s/gaa31oadvay69tn/BBT error report.rtf?dl=0
Mac OS is High Sierra 10.13.5, Zotero is up-to-date, BBT is version 5.0.196.
A couple of possible contributing issues: my BBT library is saved in my Dropbox; and my Zotero storage was locked because I'd forgotten to renew. But I've paused syncing on Dropbox and paid my renewal for Zotero storage and the problem persists after multiple restarts.

There are some macos-specific fixes in the version posted in #863 - can you see if that at least makes the wizard.advance error go away? How many references do you have in your library?

Thanks for getting back to me so quickly. I have a bit over 3,500
references in my library.
Also, it's just the BBT auto-export that I save in my Dropbox -- the Zotero
library is local, and syncs to the Zotero server.
I gave the version posted in #863 a go. I still get the beachball when I
interact with BBT, e.g. it occurs every time I ask it to refresh a citekey.
And the error reporting wizard still does not work. Sorry the Mac is giving
you so much trouble.
Many thanks,
Daniel
On 5 September 2018 at 16:18, Emiliano Heyns<EMAIL_ADDRESS>wrote:

There are some macos-specific fixes in the version posted in #863
https://github.com/retorquere/zotero-better-bibtex/issues/863 - can you
see if that at least makes the wizard.advance error go away? How many
references do you have in your library?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-418612187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZOYH4-4Axmz8vZatVv9UDwXrdpBt2mjks5uX2y_gaJpZM4WaJuq
.

Wait, the error report did complete, after about 3 minutes!
My report id is: C9MS5WAG-euc
Cheers,
Daniel
On 5 September 2018 at 20:37, Daniel Reeders<EMAIL_ADDRESS>wrote:

Thanks for getting back to me so quickly. I have a bit over 3,500
references in my library.
Also, it's just the BBT auto-export that I save in my Dropbox -- the
Zotero library is local, and syncs to the Zotero server.
I gave the version posted in #863 a go. I still get the beachball when I
interact with BBT, e.g. it occurs every time I ask it to refresh a citekey.
And the error reporting wizard still does not work. Sorry the Mac is giving
you so much trouble.
Many thanks,
Daniel
On 5 September 2018 at 16:18, Emiliano Heyns<EMAIL_ADDRESS>wrote:

There are some macos-specific fixes in the version posted in #863
https://github.com/retorquere/zotero-better-bibtex/issues/863 - can
you see if that at least makes the wizard.advance error go away? How many
references do you have in your library?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-418612187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZOYH4-4Axmz8vZatVv9UDwXrdpBt2mjks5uX2y_gaJpZM4WaJuq
.

3.5k isn't so much. I will have to enable tracing to see what's going on.
First. can you tell me which of these regions is fastest for you?

https://www.cloudping.info/

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>45 ("faster s3 ping")
Install in Zotero by downloading test build <IP_ADDRESS>45, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>46 ("set autosave to an hour")
Install in Zotero by downloading test build <IP_ADDRESS>46, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

2746 should make log submission slightly faster and spaces out autosave more. Can you see if it helps?

How big the the better-bibtex.sqlite file when Zotero is closed (with cmd-Q)?

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>52 ("Merge branch 'master' into 1061")
Install in Zotero by downloading test build <IP_ADDRESS>52, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Okay, my closest region is Asia Pacific (Sydney), and my BBT sqlite file is
1.7mB.
With that 2746 build, the error reporting wizard completes a lot faster.
Report ID: M4YVEK6M-apse
Also, I hit 'reset cache' in BBT settings, and I'm not sure if it was that
or the new build but I'm not getting anymore beachball!
Cheers,
Daniel
On 6 September 2018 at 06:14, Emiliano Heyns<EMAIL_ADDRESS>wrote:

How big the the better-bibtex.sqlite file when Zotero is closed (with
cmd-Q)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-418866182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZOYH21D2MAGOPLmJyLo0NfmYBVvO_36ks5uYDCcgaJpZM4WaJuq
.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>54 ("reset autosave to 5s")
Install in Zotero by downloading test build <IP_ADDRESS>54, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

The new build resets the save timer to what it was before, see how that works.
If you do see the problem again, please close zotero (cmd-Q) and take note of the file sizes in the better-bibtex directory in the zotero directory before resetting the cache. If the size of the cache is involved it'd be good to know how much data we're dealing with. But I'm seeing some really large save times for the main database (which is separate from the cache), I'm looking into changing the way the database is saved.

Ok, I think I've found the problem.
The file sizes in the better-bibtex directory are all <2mb.
I'm using the Bibtex auto-export function to support a workflow for
inserting citekeys into markdown texts in Ulysses, and pandoc gets called
to replace the citekeys when I generate RTF output. Zotero freezes up when
auto-export is set to 'on change', and it doesn't freeze up when
auto-export is 'when idle'. I watched the settings window and the
freeze-ups occur when the auto-export status changes to 'scheduled' and end
when it changes to 'done'. And it's triggered by changing something that
affects the citekey, e.g. tweaking the publication date field.
Cheers,
Daniel
On 6 September 2018 at 15:55, Emiliano Heyns<EMAIL_ADDRESS>wrote:

The new build resets the save timer to what it was before, see how that
works.
If you do see the problem again, please close zotero (cmd-Q) and take note
of the file sizes in the better-bibtex directory in the zotero directory
before resetting the cache. If the size of the cache is involved it'd be
good to know how much data we're dealing with. But I'm seeing some really
large save times for the main database (which is separate from the cache),
I'm looking into changing the way the database is saved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-418973484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZOYHyth-E2Vq2i8WBuCnjXfoFpUYoDBks5uYLjOgaJpZM4WaJuq
.

Right -- fixing this requires changes in Zotero, sorry.
Still, 15 seconds is still a lot for 3.5k references, assuming the cache is in order. Can you check that your auto-export caches are at or near 100% in the BBT preferences?

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>56 ("save to json")
Install in Zotero by downloading test build <IP_ADDRESS>56, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

2757 will, o.a., log how long the export actually takes. From this I could tell whether the cache is being used - -the cache makes a huge difference, I have a test that does 12k item which takes 194 seconds on a cold cache but 21 on a hot cache.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>94 ("add typings")
Install in Zotero by downloading test build <IP_ADDRESS>94, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

2794 adds a trick to partially prevent lockups during export. The actual fix requires a planned change in Zotero, but there's no timeline for the fix. While any single export runs, Zotero just locks up, there's nothing I can do about that; BBT is an odd duck because it makes people do large exports, which is not customary for Zotero users. So what happens now is:

Start a large export on an empty cache
While the export runs, pre-cached items are picked from the cache (which will be none if 1. is true), the cache is populated for each item in the export
Subsequent exports will find a pre-filled cache for all or most of the exported items, so it should (hopefully) be fast enough to lock up Zotero for an imperceptibly small time

Problem is, if you change anything in the BBT prefs, the cache is cleared, so any time you do this you start from 1. and not from 2.
2794 adds a configurable cheat -- before BBT kicks off 1., it looks at how many uncached items will be exported, and if there are too many (with "too many" being configurable) it will pre-fill the cache for those items before the actual import starts, with individual pre-fills again locking up the UI, but because they're just single items, that should per-item be unnoticeable. This pre-fill does take time, so exporting an unfilled cache will take a lot more time, but during the pre-fill it will not lock the UI, and during the actual following export, it will be as fast as technically possible because everything comes from the cache.
This behavior is off by default but can be turned on by setting the hidden preference primeExportCache to a non-zero number; the number is how many non-cached items there have to be to trigger the behavior.
The change in Zotero will make this unnecessary, but in the meantime, it may help.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>04 ("configurable prime threshold/batch")
Install in Zotero by downloading test build <IP_ADDRESS>04, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Hi Emiliano,
I think this problem might have recurred — I have on-update set to 'idle' but I'm still getting Zotero lock-ups and this message appears from BetterBibtex.

Cheers,
Daniel

Did Zotero freeze while you were using it (which means the idle detection would be wrong), or did it freeze after it went idle but would then not respond until the export was done?

Do you have primeExportCache set BTW?

Really can't do anything without more information.

Apologies, having a busy week. These are my settings for primeExportCache, I haven't changed them:
Cheers,
Daniel
On Apr 17 2019, at 1:34 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

Really can't do anything without more information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-484188566), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH2YWR55OXWAWRYZLLTPQ5NSVANCNFSM4FTITOVA).

I was mistaken, it should have been autoExportPrimeExportCacheThreshold, but I think you mailed in response with an attachment; github discards attachments. If you send a BBT error report I als get your BBT settings. Be sure to update first, a new version has just been released.

Hi again,
Sorry for the slow response — I'm in PhD write-up.
I haven't changed any of the preset values for Zotero/BBT.
I've submitted an error report: REQV743G-euc
It was running the April 19 update of BBT.
Many thanks,
Daniel
On Apr 17 2019, at 3:10 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

I was mistaken, it should have been autoExportPrimeExportCacheThreshold, but I think you mailed in response with an attachment; github discards attachments. If you send a BBT error report I als get your BBT settings. Be sure to update first, a new version has just been released.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-484222765), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH2FCFZZ6JRPA2O6OWLPQ5Y2LANCNFSM4FTITOVA).

You have it on, probably because BBT automatically turned it on when it saw the large auto-export. Looks like the cache priming isn't always working though because I see some 5k uncached items entering the export twice.
I know how busy a PhD can be, but if I'm going to tackle this one I'll need your help. Is this something you can do right now?

Yep, happy to help — if I go quiet please don't hesitate to remind me though!
Cheers,
Daniel
On Apr 22 2019, at 3:20 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

You have it on, probably because BBT automatically turned it on when it saw the large auto-export. Looks like the cache priming isn't always working though because I see some 5k uncached items entering the export twice.
I know how busy a PhD can be, but if I'm going to tackle this one I'll need your help. Is this something you can do right now?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-485520599), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH5RE2MXVSX4NRCSO6DPRYFWJANCNFSM4FTITOVA).

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>14 ("more logging for cache priming")
Install in Zotero by downloading test build <IP_ADDRESS>14, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Can you try triggering an auto-export with 3814 and post a new debug log?

Maybe I can help- I'm having the same problem. I submitted an error report: HBEIQ5YI-euc
Thanks,
Katie

I need a debug log specifically from 3814, you're on 5.1.68 (release).

Okay no problem, just installed 3814 and was able to reproduce the error. Report: HMF9FVKR-euc

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>23 ("log uncached query")
Install in Zotero by downloading test build <IP_ADDRESS>23, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

OK, that does indeed reproduce the problem. I can see the cache being filled, and I have some idea of why this may be happening -- it may be the preference overrides in the auto-export. Please generate a new debug log with 3823.

Okay here it is: I5574CD3-euc
Hopefully the main problem is fixed soon!

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>24 ("prefs override cache search")
Install in Zotero by downloading test build <IP_ADDRESS>24, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Right, prefs overrides were at least part of the problem. I'd appreciate a new debug log with 3824.

Hi all,
I've installed 3824 and I haven't noticed any slowdowns while using Zotero itself — doing the kinds of things that previously caused slowdowns (e.g. adding a new item, changing an author name so that the BBTX key changed as well). In fact, Zotero felt a lot quicker to respond.
However, I did get a massive slowdown when I did the error report — trying to highlight and copy the report ID, the interface reacted about 15 seconds after I clicked it.
Debug id: R4Z4JJYR-euc
Cheers,
Daniel
On Apr 23 2019, at 3:06 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

Right, prefs overrides were at least part of the problem. I'd appreciate a new debug log with 3824.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-485934686), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH624U3YLT267VF7F4LPR5M2BANCNFSM4FTITOVA).

I can't really tell whether it helped -- I can find no auto-exports triggered in R4Z4JJYR, but that may be explained by the fact that auto-export is set to "idle" on your system, and it likely didn't fall idle. Did you manually trigger the auto-export in I5574CD3? You also had auto-export set to on-idle there, and while I don't see the system falling idle, I do see an auto-export there.
Not sure where the slowdown in the debug submission comes from, but fixing the auto-export slowdowns takes priority.

Okay I was able to trigger an auto-export error with 3824. ID is F6ARW6VN-euc. Interestingly, I didn't experience a slowdown in the error reporting interface.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>40 ("Merge branch 'master' into gh-1061")
Install in Zotero by downloading test build <IP_ADDRESS>40, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Can you get me a new debug log using 3840? I haven't been able to replicate the problem.

Hi again,
I've downloaded the new update, no slowdowns visible when adding new items, moving items, renaming authors etc, but Zotero has crashed completely (spinning beachball) when I've gone to do the error report.
Cheers,
Daniel
On Apr 24 2019, at 3:06 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

Can you get me a new debug log using 3840? I haven't been able to replicate the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-486385527), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH4CDTJW6HJNBNB5WC3PSCVUDANCNFSM4FTITOVA).

Is that reproducible? I can't make that happen on my end.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>41 ("cleanup")
Install in Zotero by downloading test build <IP_ADDRESS>41, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>43 ("Merge branch 'master' into gh-1061")
Install in Zotero by downloading test build <IP_ADDRESS>43, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Man I'll be happy when I can ditch the cache when Zotero implements async exporters. Give 3843 a go, if possible triggering an auto-export after clearing the cache in BBTs advanced prefs. If possible, tick the send cache box in the debug log screen. It will be slower, but between the logs and the actual cache contents, maybe I can figure out what's happening.

I downloaded 3843, cleared the cache, and triggered an auto-export. Hopefully this is helpful! FXW6SMYU-euc. My error reporting is still fine- no crashing

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>49 ("more logging")
Install in Zotero by downloading test build <IP_ADDRESS>49, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

I still see it filling the cache and then at the end claiming that it hasn't. Can you do it again with 3849? That adds more logging still.

Sure! Here it is: JQ8UKF4K-euc

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>53 ("does sqlite give me string IDs? That would be nasty")
Install in Zotero by downloading test build <IP_ADDRESS>53, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

You know the spiel by now 🙄 . More logging.

Yep, here it is: 3XW7Y33S-euc
Thank you for your work on this :)

Hi again,
With 3840 I got the BBTX popup noting a 140-second export: EJ2PCEAZ-euc
With 3853 I could see Zotero doing a sync, running incredibly slowly, and after maybe 4 minutes it froze altogether.
Cheers,
Daniel
On Apr 25 2019, at 12:12 pm, Katherine Wolfert<EMAIL_ADDRESS>wrote:

Yep, here it is: 3XW7Y33S-euc
Thank you for your work on this :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-486738621), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH7BBLXVCMLQJC2HHJDPSHJ6FANCNFSM4FTITOVA).

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>59 ("not all items are cachable?")
Install in Zotero by downloading test build <IP_ADDRESS>59, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Unfortunately I really need logs from the latest build posted here. I'll need a new one from 3859 -- it looks like the priming results are not always offered to the cache, but I don't yet know why.

Okay here it is: VPGKYFPZ-euc

It's not the exports not being offered to the cache... some items are offered to the primer but they don't seem to make it to the exporter. A new build has been scheduled with more logging which will be announced here in a few minutes.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>65 ("why this can't just be static build info... never changes at runtime")
Install in Zotero by downloading test build <IP_ADDRESS>65, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Can you go into Preferences - Advanced - Files and Folders - Show data directory, quit Zotero (so that'd be cmd-Q if you're on a Mac) to make sure it is not running, and then get me a zip of the zotero folder of the folder that just opened? I need to get this reproducible locally.

Ok, doing that now. I just noticed the Zotero folder is 10gb and the better-bibtex folder is about 21mb — is that a possible cause of the issue? I'll e-mail through a Dropbox link as soon as the zip is done.
Cheers,
Daniel
On Apr 26 2019, at 1:38 am, Emiliano Heyns<EMAIL_ADDRESS>wrote:

Can you go into Preferences - Advanced - Files and Folders - Show data directory, quit Zotero (so that'd be cmd-Q if you're on a Mac) to make sure it is not running, and then get me a zip of the zotero folder of the folder that just opened? I need to get this reproducible locally.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-486932293), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH6SV4RZN2LBV6WVGD3PSKILXANCNFSM4FTITOVA).

That's big, but cache priming is supposed to ameliorate the problems that it would bring. To be clear -- Zotero just always locks up when doing any kind of export, that's nothing I can fix, it's just that in most uses of Zotero, exports are so small and infrequent as to not matter. The problem here is that

BBT users are more likely to do frequent exports
BBT users are more likely to do larger exports

The way I try to work around this is to detect potentially large exports before they happen, export them in very small chunks (which will individually lock up Zotero, but for hopefully unnoticeably short periods each), grab the output and cache it, and then kick off the actual export, using the cached output. This will still lock up Zotero, but as BBT doesn't have to do any "work" during that export, it would be as short as is possible in current Zotero.
For some reasons, even when I request the batch export (of size 10 currently), only 3 or for are actually exported, so not even half of the priming is effective... but when I request during the prime whether that batch is in the cache, I'm getting "yes". No idea what's going on there yet.
The proper solution is just for Zotero to allow me to say inside the export "it's OK to pause the export here, you can do something else" like it is possible in the imports. That will entirely solve this problem, and I could do away with the cache entirely. This change to Zotero is planned, but there's no ETA.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>84 ("Merge branch 'master' into gh-1061")
Install in Zotero by downloading test build <IP_ADDRESS>84, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>90 ("Merge branch 'master' into gh-1061")
Install in Zotero by downloading test build <IP_ADDRESS>90, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

I have a bit of time today, so if the zip is ready, I'm really keen to get to the bottom of this.

Hey Emiliano,
Thanks for the explanation in your earlier e-mail — makes sense.
Here is the zip: https://www.dropbox.com/s/if05g6chg7wn4ig/Zotero.zip?dl=0
Warm regards,
Daniel
On Apr 27 2019, at 6:29 am, Emiliano Heyns<EMAIL_ADDRESS>wrote:

I have a bit of time today, so if the zip is ready, I'm really keen to get to the bottom of this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-487274381), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQH4LZLT5Z32NUMUD573PSQTHTANCNFSM4FTITOVA).

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>92 ("so bottom line: we need async export. For real.")
Install in Zotero by downloading test build <IP_ADDRESS>92, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Thanks for that - that got me a little further. I have added a small delay between priming batches and have made the priming batches smaller, and this makes the zotero ui more responsive.
The downside to all this is that the delays mean that the priming takes longer (you can see the cache filling in the preferences auto export tab), and the smaller batches also make it take longer, as each individual export action incurs overhead.
There's hidden preferences you can tweak this with, but it's really just choosing one downside over the other (slower priming vs longer freezes). The true fix is async export.

Can you try 3892 to see if it (sufficiently) solves the problem for you? And if not, submit a new debug log?

Sorry I was away from my work computer over the weekend! The newest build is working well for me- less freezing. Thank you again your work on this

Superb. I'm going to strip some of the logging, and then I'll put out a new release with this.

I'm going to leave this issue open because to really solve it, I need (planned) changes in Zotero

Hi Emiliano,
I tried 3892 and didn't spot any noticeable slowdowns with it!
Debug: Q4SXYM2Z-euc
Let me know if there's anything I can do to help make the case for raising the priority of async export in the Zotero roadmap.
Many thanks for your time and energy, Emiliano.
Best,
Daniel
On Apr 29 2019, at 3:17 pm, Emiliano Heyns<EMAIL_ADDRESS>wrote:

I'm going to leave this issue open because to really solve it, I need (planned) changes in Zotero
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/retorquere/zotero-better-bibtex/issues/1061#issuecomment-487708370), or mute the thread (https://github.com/notifications/unsubscribe-auth/AGJZQHYRLPEIMCMYI3E4BULPS5CWHANCNFSM4FTITOVA).

5.1.76 has been released that has the changes from 3892. It's still far from idea because the responsiveness comes at the cost of substantially slower auto-exports.
I'm not entirely sure what the best way is to let Zotero know that the async change is useful to others. It's being discussed on their github, on the Zotero forums and the Zotero development discussion group, but they know I need this, it's planned, and I don't want it to come across like I'm sending people over to harass them...

I'm going to look into splitting it off to a worker thread. This is going to be a major undertaking but should solve the problem once and for all.

Hi Emiliano,
Thank you so much for your work on this. I'd be happy to continue as a beta
tester — do you want to add me on an IM platform to make communication
easier?
Cheers
Daniel
On Mon., 11 Nov. 2019, 9:48 am Emiliano Heyns<EMAIL_ADDRESS>wrote:

I'm going to look into splitting it off to a worker thread. This is going
to be a major undertaking but should solve the problem once and for all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/1061?email_source=notifications&email_token=AGJZQHYKRYCF2KQ6TWG2WT3QTCFSBA5CNFSM4FTITOVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDVJBSY#issuecomment-552243403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGJZQH2CYF2KEMGUFLQRWDLQTCFSBANCNFSM4FTITOVA
.

Nah, github works good for me. And it will take a while to get this working, probably something for the xmas holiday.

If you ever want testing on this, I'm happy to help too

That will become relevant in the very near future. I'm putting the last touches on an overhaul that will do BBT exports in a separate thread, which should make these exports entirely painless.
Gitter works well for chat for me.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>87 ("BOOYAH!")
Install in Zotero by downloading test build <IP_ADDRESS>87, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

5487 does half the job currently. Regular exports will be blocking, but auto-export should be smooth. I'm still looking whether I can do the same for regular exports.

Just tried it. Seems to work great!

I very nearly have it working for all bbt exports.

Note to self:

[ ] test attachment exports
[ ] keep registry of running threads so I can check whether they've been properly closed

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>95 ("add worker stats to error log")
Install in Zotero by downloading test build <IP_ADDRESS>95, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

@anjiro, @lyndondrake, @danmeek, @kwolfert: I'd really love to hear from you guys how 5495 does for you. This should fix the problems of BBT blocking Zotero once and for all -- all exports*, regular and auto-exports, are now background exports so should not affect Zotero at all. I'm really keen to get this into a formal release, but it'd be good to have confirmation that this indeed does remove the lockup problem for you guys. No more cache priming! In fact the preferences for cache priming are gone in 5945. I'm super stoked about this, I've been brewing on this idea for a long time, and after a few insights it turned out to be a lot less work than I had initially thought.

* except drag-and-drop, which is mostly for citations, but which I can't fix this way because of limitations imposed by the Firefox platform

Works for me!

This is so freaking AWESOME. BBT exports now run on their own thread. This is not supposed to be possible under the current Zotero architecture -- I mean, BBT does a lot of things that shouldn't be possible, but this one is the most out-there of them all. I am pretty proud of myself for this one -- this should be a game-changer for large libraries. Auto-exports of thousands of entries won't be faster than it was, but it should be almost unnoticeable while it runs in terms of how usable Zotero stays. And multiple auto-exports will just run simultaneously (actually simultaniously, not just async-interleaved) on different cores if you have a multi-core PC (and who doesn't these days).
WOOHOO!

Yes! This seems to work for me as well. I tried removing a couple thousand items from a collection and Zotero continues to respond. Watching the auto-export preference window, it looks like it runs multiple times ("status" changes from "running" to "done" several times) and Zotero's CPU usage hits 600+%, but things are still usable! 🎉

The CPU could also be Zotero sync running, but I don't have time to check that at the moment…

Yeah how often the auto-export is actually kicked off depends on the timing with which Zotero notifies BBT of deletes. When a notification comes in I delay the start of auto-exports to see if more notifications come in to limit unnecessary exports, and every time a new notification does come in within the delay window, the delay starts anew. The delay is set to 1s by default, but you can set it to a larger value by changing extensions.zotero.translators.better-bibtex.autoExportDelay (which is a number in seconds). With thousands of entries being changed at once, 5s wouldn't be unreasonable I think. If the delay is not sufficient to cover the time Zotero takes to actually delete a large batch of items, you'll have multiple export running targeting the same file, but since the writes to the output file are atomic, the last one should win (generally, come to think of it... I don't control the CPU time slicing, and if it's a tight race, n-1 might finish before n).
It's entirely likely that the CPU would show 600% if overlapping exports are running -- you can see in the Advanced pane of BBT how many workers are currently running and how many have been running (including the currently active ones) since Zotero started, but exports are entirely CPU-bound, so they'll spike the CPU, and (at least if you're checking the load with top on a unixoid) 600% means "600% of 1 CPU", so on an 8-core machine, that could mean 2 cores are very bored (see here). So under that interpretation, 600% wouldn't be worrying.
Man I'm so very stoked that this works so well. Much to my amazement I by and large got it to work in one large activity -- the first test that actually ran simply worked as planned, which was a bit of a surprise, I'll tell you, for this significant a change. Don't worry, if any single test in my suite fails (and I have some 250 or upwards test), no new version will be announced on an issue, because the build tool chain automatically posts builds after the tests clear. One test fails => no build is published (test builds or prod builds).

For completeness sake: with this change (which I'm going to roll out to a new release when I have a few other minor issues closed) it should be safe to have auto-export set to on change even for large libraries.

Seems to be working for me too!


comma three stuck on loading screen and bootlooping

https://github.com/commaai/openpilot/assets/85845724/a9059c29-8b4e-49cf-9ee0-cd4f89a0b068
Describe the bug
Sat in my car this morning to find out my comma three was bootlooping. After I unplugged the power cable then plugged it back in, the device booted up normally and I was able to use openpilot with no issues. I had a similar occurrence on the same device a few days ago, except the screen was completely black while the fan was running, which was resolved the same way.
I’m on my second warranty replacement, and I’d rather not send it in for a third time if it turns out to be a hardware issue.
Provide a route where the issue occurs
N/A
openpilot version
ead064e981d928ffd51d6a8bd7153e90244b694d
Additional info
No response

https://cdn.discordapp.com/attachments/1005992883452649483/1136317228657164379/IMG_6754.mov
Attached is a Discord link to the video of the comma three bootlooping as it won’t upload to GitHub for some reason.

Need a dongle ID to look into this.

Need a dongle ID to look into this.

5c49984c8efb9c9c

It just hapoene

It just happened again this morning. This time I noticed the light on the back of my device was red, and fading in and out.

The LED on the back isn't relevant here - that's just the panda.
Unfortunately, this is pretty early in the startup, so there's not much logging. Can you provide any more details?

Does it always reboot while in the spinner?
How many loops have you let it go for? I suspect it'll just keep going indefinitely, but good to confirm

Does it always reboot while in the spinner?

Doesn't look like it.  From the video I recorded this morning, the large comma logo blinked at least three times before it got to the spinner, which is the first time I've seen this specific occurence happen.
https://github.com/commaai/openpilot/assets/85845724/57f425ba-2c6a-49f3-a278-154ad7709416

How many loops have you let it go for? I suspect it'll just keep going indefinitely, but good to confirm

I assume this loops indefinitely as well. The longest I've let it go was for about a couple minutes.

Is it fine once it's booted? Fortunately, it's repeatable, so I can add some new logging to figure out what's going on.

Is it fine once it's booted? Fortunately, it's repeatable, so I can add some new logging to figure out what's going on.

Yes, once I unplug the device then plug it back in, I'm able to use openpilot with no issues. It seems like this happens every two days.

https://github.com/commaai/openpilot/assets/85845724/ec5eb5e9-7916-4520-b527-e2f4e8ba0859
It just happened again this morning. The car is running and I can hear the fan, but the screen is completely blank.

Once again I unplugged the device and plugged it back in and was able to boot as usual, except this time I’m unable to use openpilot due to this error message. Rebooting does not resolve this issue.
Regardless, I am now convinced my device is on its last legs and thus no longer comfortable with using it anymore.

I understand the latest master-ci build resolves this error message. When I have the time I will factory reset and reinstall master-ci.

I was able to factory reset and then re-install master-ci shortly after posting my previous comment. So far, I have yet to encounter any bootlooping or black screens, and have had no issues while using openpilot as well. However, I just realized I forgot to connect to my home Wi-Fi network since then. Could a problem with the Wi-Fi be a possible reason?

Unlikely, but possible. Since you can't repro anymore, I'm gonna leave this open until we add some logging. Let us know if you hit it again.

Need a dongle ID to look into this.

This happened to me too, yesterday. I was really scared, thought it's bricked. Dongle ID 44379c05b64fd7e3. I turned it off and tried after a couple of hours, then it started normally.
It happened in this scenario:

C3X is connected to a 5V USB power supply
In the settings choose to make a reset to factory settings (wipe it)
Low voltage warning appears (choice Power off or proceed at own risk)
Choose Power off
Not sure if I waited long enough for a clean power off
Unplug, and within a few minutes connect it to the OBD-C in the car
stuck in logo screen forever

Unlikely, but possible. Since you can't repro anymore, I'm gonna leave this open until we add some logging. Let us know if you hit it again.

Just encountered the black screen for the first time in weeks. This time I was on the optimus_prime branch 9d17fca4616bccf142657c57e9e4490d42190f97

Encountered another instance of bootlooping after attempting to switch branches from nlp-driving to dummy_b4_model:
https://github.com/commaai/openpilot/assets/85845724/751fe2e1-55e3-4fee-98cf-e2c4237a27b8
Then, after unplugging the device and plugging it back in, openpilot failed to build:

I was able to factory reset and reinstall openpilot on the master-ci branch, but this took much longer than expected. The progress bar was slow to move and got stuck several times in the process. It took about half an hour to download and install with the SIM card’s LTE connection.

I just got back from a month long trip overseas, the comma three unplugged and stored neatly inside its box during that time. When I plugged in my comma three I was once again greeted with the openpilot failed to build error. I performed the usual factory reset then attempted to install the nlp-driving branch.
Everything seemed to go fine until the installer froze  at 91%. After waiting several minutes to no avail I unplugged the device, plugged it back in, and tried again. This time the loading bar went crazy for a few seconds, but openpilot successfully installed after a couple of minutes.
openpilot is up and running right now but at this point I am concerned I am dealing with a possible hardware issue.

It seems like you're experiencing issues with your Comma Three device bootlooping. Here are some general steps you can take to troubleshoot and potentially resolve the issue:

Check for Software Updates:
Ensure that your openpilot software is up to date. Sometimes, bugs are fixed in newer software releases.

Reinstall openpilot:
Reinstalling the openpilot software might help if there are any corrupted files causing the bootloop. Follow the recommended procedure for reinstalling openpilot on your Comma Three device.

Review Logs:
Check the logs generated by openpilot for any error messages or warnings. This information can provide insights into what might be causing the bootloop.

Community Forums:
Visit the Comma Three community forums or support channels. Other users might have faced similar issues and could provide valuable insights or solutions.

Contact Support:
If the issue persists, reach out to Comma AI's official support channels. They might have specific troubleshooting steps or be aware of any common issues related to bootlooping on the Comma Three.

Hardware Inspection:
Since you've already had a warranty replacement, it's essential to consider the possibility of a hardware issue. Check for any physical damage or loose connections that might be contributing to the problem.

Factory Reset:
If possible, perform a factory reset on your Comma Three device. This will revert the device to its default settings, eliminating any potential software glitches.

Documentation:
Refer to the official documentation for your Comma Three device. There might be specific instructions or troubleshooting steps provided by Comma AI that can help resolve bootloop issues.

Remember that these are general suggestions, and the specific solution might depend on the details of your situation. If the problem persists, reaching out to Comma AI support is crucial, especially considering that your device is still under warranty. They can provide personalized assistance and guide you through the troubleshooting process.


DirectLine works intermittently (502 / 503 error codes)

Hi there,
Can you please tell me if DirectLine is experiencing some problems right now? We have lots of 502/503 errors in requests

Request URL:https://directline.botframework.com/v3/directline/conversations/8eM0OdqP3Z3IZ7smB7w1Ym-h/upload?userId=c83d1d8d-9463-4c8a-af23-a00db7606598
Request method:POST
Remote address:<IP_ADDRESS>:8080
Status code: 502
Version:HTTP/2.0
Referrer Policy:no-referrer-when-downgrade
APP ID: a6c8bf7d-1cba-47af-a470-d6b8247dadd8

We are experiencing the same issues!

Another example
Request URL:https://directline.botframework.com/v3/directline/conversations/C46gOO3jIbO4QZl4E0cp51-h/upload?userId=1ac40575-3df6-4bc3-9474-46a83d67ee1a
Request method:POST
Remote address:<IP_ADDRESS>:8080
Status code: 503 Service Unavailable
Version:HTTP/2.0
Referrer Policy:no-referrer-when-downgrade

Thank you for reporting. I can confirm that there was a period where Direct Line in West Europe was returning 503s and 502 gateway timeouts intermittently. Our live site team engaged on the issue and it is resolved now. Please let us know if you continue to see issues with these API calls.


PR: Enable running renamed files and .ipy files

Description of Changes

Removes first_execution so there is no need to confirm every time a new file is run.
adds a test for running files with quotes in their names (see https://github.com/spyder-ide/spyder/pull/20633)
Support running ".ipy" files as well as ".py" files
Removes sig_switch_run_configuration_focus whih was unused

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #20701
Fixes #20715
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

@impact27, I disabled running IPython files in the Code Analysis and External Console plugins because those plugins can't handle them.
I also pushed a fix for a bug I found while testing this locally: if you renamed a Python file to an IPython one in the editor, then it was registered twice, which caused a bug.


Demo asparagus.html not working under IE

Tested under IE11
It is because you use window.scrollY instead of window.pageYOffset
scrollY and pageYOffset are identical except pageYOffset is supported by all browsers including IE.

@tkrotoff Ah, good catch, fixed now!
:+1:

Your demo site still uses the old code, so not working in IE. You can update it or link directly to the repo:
http://htmlpreview.github.io/?https://raw.githubusercontent.com/Form5/parallax/master/demo3/asparagus.html


Update pytorch.py

refactoring code with var unpack which is more pythonic, concise, readable and efficient; how do think this change which has practical value？
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

Thanks for the suggestion, I prefer the existing code.