Allow to disable pinning for subdomains

Hey,
I want to enable pinning for all our domain, but disable it for a specific subdomain. So I tried it with something like that:
<network-security-config>
  <!-- Pin the domain www.datatheorem.com -->
  <!-- Official Android N API -->
  <domain-config>
    <domain includeSubdomains="true">www.mydomain.com</domain>
    <pin-set>
      <pin digest="SHA-256">....</pin> <!-- production -->
      <pin digest="SHA-256">...</pin> <!-- backup -->
    </pin-set>
    <!-- TrustKit Android API -->
    <!-- Do not enforce pinning validation -->
    <trustkit-config enforcePinning="true" disableDefaultReportUri="true">
      <!-- Add a reporting URL for pin validation reports-->
      <report-uri>https://report-uri</report-uri>
    </trustkit-config>
    <domain-config>
      <domain>unsecure.mydomain.com</domain>
      <pin-set></pin-set>
      <trustkit-config enforcePinning="false" disableDefaultReportUri="true">
        <!-- Add a reporting URL for pin validation reports-->
        <report-uri>https://report-uri</report-uri>
      </trustkit-config>
    </domain-config>
  </domain-config>
</network-security-config>

Notice the empty pin set in the child domain configuration - this is required, otherwise Android will use the pin from the parent domain cofing. The problem is - TrustKit not allow declaring empty pinset. Maybe this is something possible to change?
I have similar issue with ios - datatheorem/TrustKit#88 - and I suggested similar change there too.
Thanks,
Omer

Hey,
Can you try this config on Android N without initializing TrustKit (you can comment the line out) ? I'd like to know what is Android N's behavior in this case. TrustKit should 100% mirror it.
Thanks!

I checked that by debugging Android N TrustManager - it seems that if the pin list is empty, it does not do certificate pinning (from NetworkSecurityTrustManager):
PinSet pinSet = mNetworkSecurityConfig.getPins();
        if (pinSet.pins.isEmpty()
                || System.currentTimeMillis() > pinSet.expirationTime
                || !isPinningEnforced(chain)) {
            return;
        }

private boolean isPinningEnforced(List<X509Certificate> chain) throws CertificateException {
        if (chain.isEmpty()) {
            return false;
        }
        X509Certificate anchorCert = chain.get(chain.size() - 1);
        TrustAnchor chainAnchor =
                mNetworkSecurityConfig.findTrustAnchorBySubjectAndPublicKey(anchorCert);
        if (chainAnchor == null) {
            throw new CertificateException("Trusted chain does not end in a TrustAnchor");
        }
        return !chainAnchor.overridesPins;
    }

Thanks for checking - then this is definitely a bug in TrustKit. Will fix it for the next release.

Ok, thank you! If that help, I can create a PR.

Sure, that would definitely help! Two things I would ask tho:

Please make sure that an empty  will be accepted as a valid policy by Android N (as in your previous reply you said "it seems that if"). For a quick check, you can use the TrustKit Demo App, remove the line of code that initializes TrustKit, add an empty  and make sure that it is accepted.
In your implementation, we will need an extra check which is that if enforcePinning is set to true and the  is empty, TrustKit should crash on initialization (because this config wouldn't make sense).

So yeah feel free to create a PR, or otherwise we will eventually fix this for the next release.
Thanks!

I opened the issue only after we had issue (e.g. subdomain that should be excluded does not exclude) on Android 7. I just looked in the code to make sure I am not missing something.


Router - Base path

is It possible to set a base path for the router?
instead of handling endpoints likedomain.com/v1/auth as/v1/auth, it should handles it as /auth
Thanks!

Hi @yassinrais !
You can use app.route().
https://hono.dev/api/routing#grouping

does it support url format ?
ex: app.route('http://domain.com/v1')

No. Treating a domain is not Hono matter.

Okey, thanks you 🙏🏻


Update CODEOWNERS

Added a code owner in a Indian time zone
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66fe34de2515e41ccc2ba4bd--harness-developer.netlify.app

Since Abhijeet has left, closing this PR


add neo4j (d3) visualization for nodes of task to show contrasts, etc.

added VERY simple graph view - will need customization depending on styling decisions


overlay another layer in get_image_collection_gif function, solve #1993

This PR is raised for #1993. I tried to add the overlay layer to the output gif.

Looks great! Thank you for your contribution.


Bug: spacing in math align environment is incorrect for equal sign and minus sign

Issue Summary
In LaTeX align math environment and some other similar environments, space after equal sign and spaces around minus sign are set incorrectly.
Steps to Reproduce

In MathJax demo https://www.mathjax.org/#demo, enter this example:

We have incorrect spacing here when we use align:
\begin{align}
a = & b \\
c = & -d \\
\end{align}

Compare to correct spacing when we use eqalign in plain math
\[ \eqalign{
a = & b \\
c = & -d \\
} \]

This is a bug for align because (1) there is no proper space between = and b in the first line, and (2) there is too much space between - and d in the second line.  The correct behavior is demonstrated with eqalign in plain math mode.
Technical details

MathJax Version: 3.2.2 (latest commit:  600692ad9d3552cc25f85510d5797bc942ecc9f7)
Client OS: Linux 5.15.0-58-generic
Browser: Firefox 109.0.1 (64-bit)

The rendering you are seeing for your first example is actually correct.  Here is the output from actual LaTeX for your `align environment:

which is what MathJax is rendering as well.  Here is MathJax's output for the same expression:

The reason is that you are not putting the ampersands in the correct place.  The proper expression would be
\begin{align}
a &=  b \\
c &= -d
\end{align}

which renders as

On the other hand, MathJax's rendering of your second expression is actually incorrect, at is should render like the first one.  Again, this is because the ampersands should precede the equal signs.

Thanks very much for your reply.  I agree with your conclusion.  When the right-hand side of equation is very long and I want to split it into multiple lines, I do want to put the ampersand to the right of equal sign so that all lines of the right-hand side are displayed to the right of the equal sign.  After some searching online, I find that I can achieve the correct spacing with ampersand to the right of equal sign by adding dummy tokens:
\begin{align}
a = {} & b \\
c = {} & {-d} \\
f = {} & 1 + 2 + 3 + 4 \\
& + 5 + 6 + 7 + 8 \\
& + 9 + 10
\end{align}

This achieves the spacing that I want.  Thanks for your help!

I'm glad you found something that works for you.  The usual approach to this is to still use the & before the =, but to add an explicit space at the beginning of the continuation lines.  E.g.,
\begin{align}
a &= b \\
c &= -d \\
f &= 1 + 2 + 3 + 4 \\
&\hspace{1em} + 5 + 6 + 7 + 8 \\
&\hspace{1em} + 9 + 10
\end{align}

or
\begin{align}
a &= b \\
c &= -d \\
f &= 1 + 2 + 3 + 4 \\
&\phantom{={}} + 5 + 6 + 7 + 8 \\
&\phantom{={}} + 9 + 10
\end{align}

if you want exactly the amount of space for the equal sign.  If course, you can define a macro that makes these easier:
\newcommand{\=}{\hspace{1em}}
\begin{align}
a &= b \\
c &= -d \\
f &= 1 + 2 + 3 + 4 \\
&\= + 5 + 6 + 7 + 8 \\
&\= + 9 + 10
\end{align}

or use \newcommand{\=}{\phantom{={}}} or use whatever spacing works best for you.  This is less complicated that adding the extra braces on all the lines that aren't broken, and around leading minus signs.  Just use &\= for the beginning of any continuation line and that is it.
The macro only has to be defined once, and you can add it to the macros list in the tex block of your Mathjax configuration.  See the configmacros documentation.

Thank you!  These are great suggestions.


Problem with icons not displaying

Describe the bug
I'm trying to add the file-user icon to the sidebar, but it isn't displaying.
To Reproduce
Add the following to config.toml and go to the home page.
[[params.socialIcons]]
icon = "fas fa-file-user"
title = "Foo"
url = "/posts/"

Expected behavior
Expect the file-user icon to be present in the sidebar.
Desktop (please complete the following information):

OS: Linux
Browser Firefox
v1.12.0
hugo v0.108.0+extended linux/amd64 BuildDate=unknown

Additional context
Other icons, such as the social icons described here, display fine.

@joe-mann This is a pro icon, unfortunatley we do not include these.

@lxndrblz Ah ok I didn't realise that. Thanks for the info.


Data table rows can not have custom height after beta.7

Before beta.7 Data-Table row can be of any height. For example, if I set ng-template for a row
<ng-template tdDataTableTemplate="name" >
  <div [style.height.px]="200"></div>
</ng-template>

When all data table rows will have 200px height.
It is not he case after this PR https://github.com/Teradata/covalent/pull/859. It is no longer possible because height of td-data-table-cell-content-wrapper have been explicitly set to 48px in this file https://github.com/Teradata/covalent/blob/530d8a14db3a7abf67cf63548208d0f5ce485d30/src/platform/core/data-table/data-table-cell/data-table-cell.component.scss
How to allow custom height of data table rows now if I don't need virtual scroll?

I recently ran into this issue. I've got a custom data table, but in some cases the content overflows one line. The fixed height causes the content to be compressed in an ugly way.
Please switch this to a min-height, or provide a good way to override the values set in ~@covalent/core/theming/all-theme.

@clarkebishop Do you mean something like this?

I've managed to "fix" this by overriding the css and applying text-overflow: ellipsis

Although this fixes the ugly compression, I would like the row height to be dynamically determined so the whole text becomes visible, like in the older versions.
My suggestion would be to introduce a boolean property on td-data-table so one can choose to apply fixed height or not.

For my use case, I'm displaying a file name, and have some long names. I like your ellipsis trick, but it won't work for me.
The boolean or some other method seems like the right answer.

My table rows have thumbnail images.  48px height restriction is really getting in the way.

There is a PR opened to address this this https://github.com/Teradata/covalent/pull/898, but it still requires lots of testing


Expose id as sequence value

Expose id as sequence value for records with dynamic attributes
that depend on the id -- like the links hash:
export default Mirage.Factory.extend({
  links(id) {
    return {
      posts: `/api/users/${id}/posts`,
    };
  }
});

Previously, the sequence value was an auto-incrementing value starting
from 0. ID generation behaved exactly the same, but started from 1.
This commit changes the sequence to generated exactly the same as the
id.
Additionally, in the case of the consumer overriding the id, the
sequence value defer to the overriding value:
const author = server.create('user', { id: 100 });

assert.equal(author.links.posts, '/api/users/100/posts');

Interesting... there are enhancements planned for the factory layer that will allow you to access attrs inside a function via this
export default Mirage.Factory.extend({
  links() {
    return {
      posts: `/api/users/${this.id}/posts`
    }
  }
});

or perhaps more explicitly, where you specify the dependent attrs you need:
export default Mirage.Factory.extend({
  links: Factory.lazy('id', function(id) {
    return {
      posts: `/api/users/${id}/posts`
    }
  }
});

So the only reason I'm hesitant to merge this is because it would be two api changes in relatively short time. Also, some people explicitly use string ids for their DB, and they may still want a simple sequence number in their dynamic factory attributes.

@samselikoff I would prefer your first approach, making this.id accessible (and non-null/undefined).
However, id attributes aren't assigned until DB-insert-time, so it's impossible to use this.id unless your factory explicitly defined { id: 1 }, which is workable, but tedious.
In this PR, id and sequence are separate variables. I could modify the code to only ever pass in the number version (whether that's the auto-incrementing id, or the sequence when a String id is specified).
Would that change make this mergible?

This change would definitely remove a lot of boilerplate setup in our current tests.

Good point, can't access id until the object is created. factory_girl gets around this with an after_create. We could do something similar:
export default Factory.extend({
  afterCreate(obj) {
    obj.links = {posts: `/api/users/${obj.id}/posts`};
    obj.save();
    // or use object.update('link', ...) to do in one line
  }
});

Another thought, there's been discussion about storing ids as strings, so that might eventually interfere with this.
I can look at this more a bit later, I definitely want to make your lives easier and since sequence is arbitrary this shouldn't make much of a difference for now.

@samselikoff I'm pretty opposed to adding an afterCreate hook.
I'd prefer a simpler solution where this exposes everything you'd need, whatever that ends up being.

Interesting, but then this couldn't expose id, as you pointed out. Why opposed to afterCreate? Do you also oppose this in factory_girl? (genuinely curious, I haven't done tons with factory_girl).

@samselikoff I'm a big fan of mirage's simplicity.
Push hash in, get hash out. Introducing hooks would complicate an otherwise simple and minimal interface

I see. I'm not sure if you've been following recent development but I just wanted to mention that there are some "opinions" coming down the line. The db will remain agnostic about its hashes, but models will hold opinions on (and take care of storing) foreign keys.
You'll be able to continue using mirage with just the unopinionated db if you so choose, but you'll end up rewriting a lot of the serialization logic we hope to include (which is totally fine).
Anyways, I only mention this bc I don't know if the simplicity argument will hold forever. But I appreciate your input. I'll check this soon.

Sounds good. Thanks for the hard work :facepunch:

Thank you :)
So, my concern here is that we're anticipating what the id will be, instead of waiting to find out what it actually is. It's true that right now the algorithm used to generate ids and sequences is the same. But that just happens to be the case. Sequence is still just a proxy for id, not the actual thing, so calling it id worries me a bit.
We have an app where id < 1000 is meaningful for the domain object (not the best data modeling, but bear with me). So, developers in this app have a reason to create models with overridden ids. But then, they don't get a sequence number anymore. I think sequence is useful. If they create users with ids of 2000, 2001, then 50, they should still be able to have a position attribute with something like 1, 2 and 3.
Also, I know the mirage server is tied to a single test right now, but if down the road there's ever a situation where there's multiple reads/writes to the db, you can easily imagine sequence no longer tracking id.
I just don't see a way around using afterCreate to get at the id. You have to wait until the db assigns the id. I do understand that this would be convenient for y'all, but it just feels too slippery.
Btw I generally think afterCreate is a great escape hatch since it's general purpose + people can use it to create related models or what have you. We already have it on the roadmap and since it solves your problem here, I'm inclined to stick with it.
Curious, could I see some of the boilerplate code you mentioned in your current factories?

@samselikoff I've given this more thought, and I'm ok with an afterCreate so long as it plays nice with both the factory definition and test server.create call.
Maybe something like:
// app/mirage/factories/author.js
export default Mirage.Factory.create({
  afterCreate() {
    this.links = {
      posts: `/api/authors/${this.id}/posts`,
    };
  }
});

// tests/acceptance/some-test.js

const author = server.create('author', {
  name: 'Ernest Hemmingway',
  afterCreate(db) {
    db.posts.insert({ author_id: this.id });
  }
});

Does that sound unreasonable or difficult to implement?

Closing in favor of https://github.com/samselikoff/ember-cli-mirage/pull/385


Pull out a deprecation message.

It was breaking cluster turn up.

#9540 ... but how?

We use that script when we generate the bearer token for kubectl on the master:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cluster/common.sh#L90
So that deprecation message got kicked into the tokens file.
Obviously we should stop using that script in our cluster turn-up scripts...


Implement AccountsJS, TypeGraphQL and TypeORM

I've been playing with accounts.js, typeorm and type-graphql (also gqltype).
Looks like a killer combo and I am thinking if I can slowly replace the internal graphql server with it.
Thoughts...

Database models would have type-graphql decorators implemented for internal schema use only
External schema would stick with vanilla graphql or a separate schema class
AccountsJS would require a TypeORM driver, which I've made a PR and has been merged and released (https://github.com/accounts-js/accounts/pull/555)
TypeORM has a very easy way of writing custom queries compared to sequelize, so all the custom versioning behavior would be trivial to port
We could implement ACL driver for type-graphql by using the Authorization decorator
Looks like migrations are easy and almost maintenance free
TypeORM has experimental mongodb support so https://github.com/birkir/prime/issues/37 may be a possibility

Links:

https://github.com/19majkel94/type-graphql
https://github.com/typeorm/typeorm
https://github.com/accounts-js/accounts

Closed with https://github.com/birkir/prime/pull/57


[labs] Initial commit of eleventy plugin

A plugin for Eleventy for pre-rendering pages that include Lit web components. The components can then be (optionally) hydrated on the client for interactivity.
Note, this plugin is primarily focused on rendering standalone widgets which can be configured with attributes in HTML into an 11ty site (there currently no facility for passing 11ty data into components via Javascript).
TODO: add tests (the included demo is working).

do you have any progress?


Selectively enable/disable plugins

Right now the plugins need to be imported into the server.py file explicitly (e.g. import plugins.miniapps.routes). Plugins may vary from instance to instance. Some instances may have privately developed plugins that are not available on other instances.
There should be a way to include arbitrary plugins through configuration in such a way that the application code (e.g. server.py file) does not need to be touched. One possibility is to do this through environment variables.

Plugins can now be selectively enabled through an environment variable called PLUGINS. A comma separated list of active plugins can be supplied as its value.


Documentation from handoff sessions

Added a few items of documentation based on our handoff sessions last week:

Links to infrastructure components
How authentication and authorization happens, with links to where to modify settings
Instructions on how to contribute to the site, with links to the CMS

Going to merge since this shouldn't impact the code you're working on @bloom-hondo , but tagging you for awareness and if you spot any mistakes, feel free to update.


[Core] Optimize block_manager_v2 vs block_manager_v1 (to make V2 default)

This PR optimizes block_manager_v2 python logic to make it comparable to block_manager_v1. The goal is to enable block_manager_v2 by default as part of the spec decode project.
The issues optimized are:

Python Block object allocations/deallocations are expensive on the hot-path of iterative batching, so a block pool is used to cache block objects.
Any string/list duplication should be avoided, especially for token id lists
Modified Prefix Caching Block/Allocator to avoid any full traversals of block_ids by using dynamic/incremental style computations
Redid the way access all blocks updates timestamps by deferring the actual updates to free(..) of sequences

Here is initial performance comparison for both standard and prefix-cache enabled runs:

TODO:

Cleanup code
Address all review comments from Cade

Great work btw! thanks!

Updated the PR with performance fixes for prefix-caching block_manager_v2. The table above is updated with new numbers for both standard run and prefix-cache enabled run.

Will start addressing review comments and cleaning up the PR

As the PR touches prefix caching and preparing v2-block-manager to be default, I was curious to see if the PR might resolve this correctness issue: https://github.com/vllm-project/vllm/issues/5543#issuecomment-2173004110.
and you might be interested to know that when running with this branch (commit c1f650fa7f162eb48763d8eeb70081986379f7e1) with  --enable-prefix-caching --use-v2-block-manager, the snippet in the linked issue crashes the server with:
ERROR 06-19 07:45:58 async_llm_engine.py:45] Engine background task failed
ERROR 06-19 07:45:58 async_llm_engine.py:45] Traceback (most recent call last):
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 40, in _raise_exception_on_finish
ERROR 06-19 07:45:58 async_llm_engine.py:45]     task.result()
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 521, in run_engine_loop
ERROR 06-19 07:45:58 async_llm_engine.py:45]     has_requests_in_progress = await asyncio.wait_for(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return fut.result()
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 495, in engine_step
ERROR 06-19 07:45:58 async_llm_engine.py:45]     request_outputs = await self.engine.step_async()
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 226, in step_async
ERROR 06-19 07:45:58 async_llm_engine.py:45]     output = await self.model_executor.execute_model_async(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/executor/gpu_executor.py", line 117, in execute_model_async
ERROR 06-19 07:45:58 async_llm_engine.py:45]     output = await make_async(self.driver_worker.execute_model
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
ERROR 06-19 07:45:58 async_llm_engine.py:45]     result = self.fn(*self.args, **self.kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return func(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/worker/worker.py", line 272, in execute_model
ERROR 06-19 07:45:58 async_llm_engine.py:45]     output = self.model_runner.execute_model(seq_group_metadata_list,
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return func(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/worker/model_runner.py", line 736, in execute_model
ERROR 06-19 07:45:58 async_llm_engine.py:45]     hidden_states = model_executable(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self._call_impl(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return forward_call(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 371, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     hidden_states = self.model(input_ids, positions, kv_caches,
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self._call_impl(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return forward_call(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 288, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     hidden_states, residual = layer(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self._call_impl(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return forward_call(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 227, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     hidden_states = self.self_attn(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self._call_impl(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return forward_call(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 161, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     attn_output = self.attn(q, k, v, kv_cache, attn_metadata)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self._call_impl(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return forward_call(*args, **kwargs)
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/attention/layer.py", line 89, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return self.impl.forward(query, key, value, kv_cache, attn_metadata,
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/workspace/nm-vllm/vllm/attention/backends/flash_attn.py", line 338, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     flash_attn_varlen_func(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 1099, in flash_attn_varlen_func
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return FlashAttnVarlenFunc.apply(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/torch/autograd/function.py", line 598, in apply
ERROR 06-19 07:45:58 async_llm_engine.py:45]     return super().apply(*args, **kwargs)  # type: ignore[misc]
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 596, in forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     out, q, k, v, out_padded, softmax_lse, S_dmask, rng_state = _flash_attn_varlen_forward(
ERROR 06-19 07:45:58 async_llm_engine.py:45]   File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 88, in _flash_attn_varlen_forward
ERROR 06-19 07:45:58 async_llm_engine.py:45]     out, q, k, v, out_padded, softmax_lse, S_dmask, rng_state = flash_attn_cuda.varlen_fwd(
ERROR 06-19 07:45:58 async_llm_engine.py:45] RuntimeError: out must have shape (total_q, num_heads, head_size_og)
Exception in callback functools.partial(<function _raise_exception_on_finish at 0x7f2bc22f4160>, error_callback=<bound method AsyncLLMEngine._error_callback of <vllm.engine.async_llm_engine.AsyncLLMEngine object at 0x7f2bb73e0910>>)
handle: <Handle functools.partial(<function _raise_exception_on_finish at 0x7f2bc22f4160>, error_callback=<bound method AsyncLLMEngine._error_callback of <vllm.engine.async_llm_engine.AsyncLLMEngine object at 0x7f2bb73e0910>>)>
Traceback (most recent call last):
  File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 40, in _raise_exception_on_finish
    task.result()
  File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 521, in run_engine_loop
    has_requests_in_progress = await asyncio.wait_for(
  File "/usr/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
    return fut.result()
  File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 495, in engine_step
    request_outputs = await self.engine.step_async()
  File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 226, in step_async
    output = await self.model_executor.execute_model_async(
  File "/workspace/nm-vllm/vllm/executor/gpu_executor.py", line 117, in execute_model_async
    output = await make_async(self.driver_worker.execute_model
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/worker/worker.py", line 272, in execute_model
    output = self.model_runner.execute_model(seq_group_metadata_list,
  File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/worker/model_runner.py", line 736, in execute_model
    hidden_states = model_executable(
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 371, in forward
    hidden_states = self.model(input_ids, positions, kv_caches,
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 288, in forward
    hidden_states, residual = layer(
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 227, in forward
    hidden_states = self.self_attn(
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/model_executor/models/llama.py", line 161, in forward
    attn_output = self.attn(q, k, v, kv_cache, attn_metadata)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1541, in _call_impl
    return forward_call(*args, **kwargs)
  File "/workspace/nm-vllm/vllm/attention/layer.py", line 89, in forward
    return self.impl.forward(query, key, value, kv_cache, attn_metadata,
  File "/workspace/nm-vllm/vllm/attention/backends/flash_attn.py", line 338, in forward
    flash_attn_varlen_func(
  File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 1099, in flash_attn_varlen_func
    return FlashAttnVarlenFunc.apply(
  File "/usr/local/lib/python3.10/dist-packages/torch/autograd/function.py", line 598, in apply
    return super().apply(*args, **kwargs)  # type: ignore[misc]
  File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 596, in forward
    out, q, k, v, out_padded, softmax_lse, S_dmask, rng_state = _flash_attn_varlen_forward(
  File "/usr/local/lib/python3.10/dist-packages/vllm_flash_attn/flash_attn_interface.py", line 88, in _flash_attn_varlen_forward
    out, q, k, v, out_padded, softmax_lse, S_dmask, rng_state = flash_attn_cuda.varlen_fwd(
RuntimeError: out must have shape (total_q, num_heads, head_size_og)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 63, in uvloop.loop.Handle._run
  File "/workspace/nm-vllm/vllm/engine/async_llm_engine.py", line 47, in _raise_exception_on_finish
    raise AsyncEngineDeadError(
vllm.engine.async_llm_engine.AsyncEngineDeadError: Task finished unexpectedly. This should never happen! Please open an issue on Github. See stack trace above for the actual cause.
INFO 06-19 07:45:58 async_llm_engine.py:158] Aborted request cmpl-4ce91102896f49d598ec6313f9629a10-0.
INFO:     <IP_ADDRESS>:47640 - "POST /v1/completions HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application

@hibukipanim thanks for pointing this issue, I will check

ok looking

To speed up the CI queue for #5905, I've cancelled the distributed tests for the latest CI run in this PR since they won't pass anyway until #5905 has been merged. Please merge main into your branch after that happens so that the CI can pass once again.

@cadedaniel @Yard1 I have addressed the review comments, the PR is ready for a pass.

@cadedaniel fixed the nits, thanks for catching these issues!


[SPARK-17105][CORE] App name will be random UUID while creating spark context if it will …

What changes were proposed in this pull request?
App name will be random UUID while creating spark context if it will not set as configuration as same as spark session.
How was this patch tested?
run all test cases

Test build #63914 has started for PR 14684 at commit c05fc3e.

This is a duplicate of SPARK-16966, pretty much. I don't think this behavior here should be changed. See the fix for SPARK-16966 and discussion for more about the intended behavior.

@srowen Yes you are right but SPARK-16966 is only for spark session but while user creating the spark context then they must be give app name. i think for both spark session and spark context the behaviour should be same so i make changes for spark context also.

@srowen ok so i close this PR as you suggested.

Test build #63914 has finished for PR 14684 at commit c05fc3e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63914/
Test FAILed.


building from source vis.h

Hi!
I tried to build hyperdex from source, but didn't find vis.h. On ubuntu, you need to install libbsd-dev to have this file. Imo, you should include it as a configure dependency.

You also call your main executable 'daemon', but it intersects with a common package 'daemon'. Why don't call it 'hyperdex'?

Good catch on the vis.h issue.  I may be removing that tool in a future version (or at least the use of vis.h)
I've changed the default program prefix in HEAD to be "hyperdex-", so every release after 0.2b6 (non-inclusive) will default to hyperdex-daemon.

I've made trace-player optional.  vis.h will not be used by default, and configure should fail when it needs to be used and the library is unavailable.


SWDEV-327563 - Win:skip mempool and getUuid failing tests

SWDEV-327563 - Win:skip mempool and getUuid failing tests
Windows skipping the failing mempool and getUuid tests

@mangupta  - This skips the latest failing windows tests.


Update MVCS blog post

As 2.0 has a few changes compared to the original version, it might be a good idea to update the older MVCS blog post sometime for newcomers.

Apologies about not updating this, I simply forgot! The blog post was updated the latest APIs a few months ago, hope that helps people coming from the blog.


Remove irrelevant configuration step

Why:
Closes #22143

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@kovaacs Thanks for opening an issue and submitting a PR! 🎉
I've edited your post slightly to link it to your issue.
I'll get this triaged for review ⚡


Update method names in readme and code

Classes should be renamed. Suggestion:
Best -> DirectAccum_ClassifNflashes
InferBlock -> BayesAccum_ClassifNflashes
InferContinuous -> BayesAccum_ClassifEarly


Fixed unqualified class "string"

The unqualified "string" class created class not found error when compiling with OpenCV

Using std::string does not comply with Google's coding conventions. The current git master compiles for me (Linux, Windows, macOS). Which problem do you have?

I do have the same issue when trying to compile the latest OpenCV. Below are the relevant lines from make's log:
[ 21%] Linking CXX static library ../../lib/libopencv_saliency_pch_dephelp.a
In file included from /usr/include/tesseract/ltrresultiterator.h:26:0,
                 from /usr/include/tesseract/resultiterator.h:26,
                 from /usr/include/tesseract/baseapi.h:31,
                 from /home/middleware/opencv_contrib/modules/text/src/precomp.hpp:51,
                 from /home/middleware/opencv/build/modules/text/opencv_text_pch_dephelp.cxx:1:
/usr/include/tesseract/unichar.h:164:10: error: ‘string’ does not name a type
   static string UTF32ToUTF8(const std::vector<char32>& str32);
          ^

The proposed fix allow make to proceed correctly.

I got the same error including <baseapi.h> into a new Visual Studio 2017 project. A simple
#include <string>
using std::string;

before including <baseapi.h> helped, but i think that's not the right way....

From https://github.com/tesseract-ocr/tesseract/issues/1045:
theraysmith commented

The problem is that -DUSING_STD_NAMESPACE is now needed  for all of the tesseract library, not just for training.

Belval commented

theraysmith Is it? Because I had that problem about 3 hours ago on Ubuntu. Tesseract does build, it's the modules built with its header files that doesn't.
I'll try adding -DUSING_STD_NAMESPACE and report back.

theraysmith commented

The same define will be required for anything that uses the library too, as the define causes a using std::string to be declared in platform.h, which is exactly what you are missing. …

stweil commented

The correct macro which must be defined is USE_STD_NAMESPACE.

so I should build OpenCV with USE_STD_NAMESPACE?

It's not necessary to build the whole project with that macro. Just define it in your code (with a comment why it is needed) before including any Tesseract header file.

@zdenop, I suggest to close this PR.

Made a pull-request to the opencv_contrib repo

why the code uses, for example, std::vector but not std::string?

Why the code uses, for example, std::vector but not std::string?

Tesseract is being developed mainly by Google employees.
As said before,  that's part of Google's coding conventions.

If what you asking is 'Why is Google use that particular convention', I don't think you'll get an answer from Ray to this question here. He is just following the internal rules.

I maintain the tesseract bindings for the R language. Currently we cannot build against tesseract 4 on MacOS because we get:
clang++ -std=gnu++11 -I/Library/Frameworks/R.framework/Resources/include -DNDEBUG -I/usr/local/Cellar/tesseract/HEAD-1b0379c/include/tesseract -I/usr/local/Cellar/leptonica/1.74.4_1/include/leptonica -I"/Library/Frameworks/R.framework/Versions/3.4/Resources/library/Rcpp/include" -I/usr/local/include   -fPIC  -Wall -g -O2 -c RcppExports.cpp -o RcppExports.o
** libs
In file included from RcppExports.cpp:4:
In file included from ./tesseract_types.h:1:
In file included from /usr/local/Cellar/tesseract/HEAD-1b0379c/include/tesseract/baseapi.h:31:
In file included from /usr/local/Cellar/tesseract/HEAD-1b0379c/include/tesseract/resultiterator.h:26:
In file included from /usr/local/Cellar/tesseract/HEAD-1b0379c/include/tesseract/ltrresultiterator.h:26:
/usr/local/Cellar/tesseract/HEAD-1b0379c/include/tesseract/unichar.h:164:10: error: unknown type name 'string'; did you mean 'std::string'?
  static string UTF32ToUTF8(const std::vector<char32>& str32);
         ^~~~~~
         std::string
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/iosfwd:194:65: note: 'std::string' declared here
typedef basic_string<char, char_traits<char>, allocator<char> > string;
                                                                ^
1 error generated.

It would be really great if this can be fixed. This PR fixes my immediate problems: https://github.com/tesseract-ocr/tesseract/pull/1164

@jeroen, a #define USE_STD_NAMESPACE (with a good comment) in tesseract_types.h (before including baseapi.h) should fix the build problem.

@zdenop , please reopen this PR and merge it.

@zdenop note the problem appears in a few more places: https://github.com/tesseract-ocr/tesseract/pull/1164/files

Can you please PR that fix it all?
I am just able to merge PR quite easily, but I am not able to work source code...

I just pointed you at the pr.

So now all issues related to class "string" should be fixed?

Let me rebuild and test if it works without #define USE_STD_NAMESPACE now. One sec....

@zdenop yes the problems are fixed. We can now compile libtesseract bindings with -std=gnu++11 without requiring -DUSE_STD_NAMESPACE. 🎉

So we could remove all USE_STD_NAMESPACE from the code, too ... if there were not some strange code lines in training/util.h. Obviously Google uses a class HeapLeakChecker for heap checks if the macro is undefined. @zdenop, do you know whether that heap checking is still needed?

I am not sure if you still need USE_STD_NAMESPACE internally for building tesseract itself. This issue is mostly about the header files which are needed for building clients that link against lib tesseract. What you use in libtesseract internally doesn't matter to the outside world.


empty mod

using mod manager and launching this through it, i get an error for merging, says empty file no matter which ones i analyze and merge

Please run version 1.0.2 or later. It will generate logs in logs/zonepaq.log. Share the logs here.

I'm glad you resolved your issue, though running from uncompiled version should work too, and it's also faster with calls to repak.


First draft of SIG Cluster Lifecycle related relnotes.

These are mostly populated from the issues labeled for sig/cluster-lifecycle and 1.8. I have reworded them in places to change from future to past tense and have more consistent verbiage.
CC @timothysc @luxas @justinsb @jbeda @mkumatag @ixdy @wlan0 @aaronlevy @diegs
Could everyone on the above CC list please take a look at the feature(s) you own and sign off on their representation here?
Also, if there is anything that is definitely going to slip the 1.8 release, now is a good time to pull it out of the release notes and update its issue.

/assign @timothysc @luxas @justinsb @jbeda @mkumatag @ixdy @wlan0 @aaronlevy @diegs

I've updated a few things based on feedback in a new commit so it's easy to see what changed. I'll squash into one commit before merging (after an LGTM).

I've stripped out the reference to s390x per @mkumatag and rebased. I'll still squash all the commits before merging.
If there isn't any other immediate feedback, I'd prefer to just merge as-is and let people tweak as necessary after commit. Does that sound okay, @jdumars?
/assign @jdumars


"Pool" or "Pooling" ?!

Currently, we are using a mix of both "Pool" and "Pooling" words in naming the variables, functions, classes and the files, as well as in constant string values. I think this might bring confusion and inconsistency. It would be a good idea to choose only one of these and use it all over the codebase. Of course, we can choose the other one only as required (e.g. for compatibility with Keras when loading models).
For comparison, this was also used to be the case in Keras/TF (and indeed it creates confusion as some users thought "pool" and "pooling" are different!); however, to mitigate it to some degree TF developers now use "pool", and the "pooling" would be considered as an alias of "pool" (even in documentation links); although, with the exception of "average pooling" which still uses "pooling" (probably because they have used "average" instead of "avg" for clarity and therefore in this case decided to chose the longer version, i.e. "pooling" instead of "pool", for consistency).
Personally, I suggest to always use "MaxPool" and "AvgPool" in naming everything, from variables to files to values of string constants. And only use "Pooling" as necessary (e.g. for compatibility reasons).

An update on this about compatibility: I just checked this and Keras is using "pooling" (instead of "pool") in the output of layer.get_config() and model.get_config() (for both fields of name and class_name) which in turn is used by model.to_json() to export model config as JSON. This is true for all layers.

Great, I dislike the long AveragePooling and prefer AvgPool too, so it could be renamed in the same manner, then all tickets related to pooling for 1d/3d will be merged.
We use Conv instead Convolution, Pool instead Pooling, Max instead Maximum.
PyTorch has the same short names: https://pytorch.org/docs/stable/generated/torch.nn.MaxPool2d.html
Regarding Keras compatibility: we will keep it on configuration saving level and could add notes about that in comments about layer serialization.

I suppose that you could use short versions in tickets assigned to you, final renaming could be performed later

I suppose that you could use short versions in tickets assigned to you, final renaming could be performed later

Yeah, I have already used the short version in all the related PRs.


New version: Malwarebytes.Privacy version <IP_ADDRESS>7

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Resolves #27887
Microsoft Reviewers: Open in CodeFlow

The Hash actually matched in both PRs for me


Generate snippets with Attributes instead of Annotations

Behat has full support for PHP 8 Attributes since version 3.10.0.
For example, this means that instead of
/**
 * @Given something
 */
public function something() {}

it is now possible to write
#[Given('something')]
public function something() {}

and the same goes for When, Then and all hooks (BeforeScenario et al).
However, when generating snippets1 Behat will use Annotations instead of Attributes.
Behat should be able to generate snippets using Attributes instead of Annotions when applicable (ie on PHP >= 8). Note that when generating a snippet with an Attribute that Attribute should also be used in the class where it's added, otherwise it won't work.
Since Behat supports PHP7.2+ at the time of writing it still needs to support generating snippets with Annotations, but it could default to Attributes when PHP >=8 is detected for example. This could also be an option, but I'm unsure if that is worth it. It feels like something that would be OK te enforce, since the entire ecosystem is moving away from Annotations to Attributes anyway. Curently features/snippets.feature tests for output with Annotations. Those scenarios could be run with a new tag @php7 similar to the already existing @php8 to prevent them from being checked on PHP8. And then the same scenarios but updated using attributes could be added with @php8 tags.
1 A snippet can be generated when at the end of a run Behat has detected undefined steps. It can add a skeleton of the step to a feature context.

There is an existing --snippets-type CLI option that hints what type of snippets to generate. We could easily add Annotations as a supported type, the question would be how to handle defaulting

I looked into that. --snippets-type is for regex vs turnip. Annotations and attributes seem orthogonal to those options.
Maybe --snippets-syntax with options annotations and attributes? And when not supplied, default depends on PHP version, i.e. attributes for PHP >= 8 and annotations for PHP < 8?

I think the smart thing for now would be to hold off on implementing this until PHPStorm supports Attributes for Behat.
Right now the DX is absolutely terrible, all the nice things you could do with Behat (find usages, ctrl+click to jump to definition from gherkin, etc) don't work with Attributes.
I did create an issue for this in Youtrack: https://youtrack.jetbrains.com/issue/WI-63963

This mostly works in later versions of PHPStorm (still falls over a bit at times), so we might want to add this snippet generation in.

Now that we have dropped support for PHP<8, my vote would be that instead of adding a new option we just change the default snippet to use attributes. People can manually change to annotations if they really want them (or tbh create the steps direct from their IDE without using behat's snippet generator at all...).

I think we could change the default for sure
Bear in mind that we could possibly adopt a third type of annotation in future (Cucumber Expressions)

Closed via https://github.com/Behat/Behat/pull/1549


Fixed typo in docs/internals/contributing/writing-code/coding-style.txt

Before:

After:

Thanks

Thanks


ldap trust map cleanup on domain delete

Description
This PR...

Fixes: #6752

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@blueorangutan package

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan package

@blueorangutan package

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

verified OK
before domain removal (some mock data)
MariaDB [cloud]> select * from ldap_trust_map;
+----+-----------+------+----------------------+--------------+------------+
| id | domain_id | type | name                 | account_type | account_id |
+----+-----------+------+----------------------+--------------+------------+
|  1 |         3 | OU   | DC=CloudStack,DC=com |            2 |          0 |
|  2 |         4 | OU   | DC=CloudStack,DC=com |            2 |          0 |
|  3 |         5 | OU   | DC=CloudStack,DC=com |            2 |          0 |
+----+-----------+------+----------------------+--------------+------------+
3 rows in set (0.00 sec)

after domain removal
MariaDB [cloud]> select * from ldap_trust_map;
+----+-----------+------+----------------------+--------------+------------+
| id | domain_id | type | name                 | account_type | account_id |
+----+-----------+------+----------------------+--------------+------------+
|  1 |         3 | OU   | DC=CloudStack,DC=com |            2 |          0 |
|  2 |         4 | OU   | DC=CloudStack,DC=com |            2 |          0 |
+----+-----------+------+----------------------+--------------+------------+
2 rows in set (0.01 sec)

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6918

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6919

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6921

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6922

@blueorangutan package

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6923

@blueorangutan test

@weizhouapache a [SF] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-7593)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42969 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7593-kvm-centos7.zip
Smoke tests completed. 105 look OK, 3 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

ContextSuite context=TestNetworkACL>:teardown
Error
89.77
test_network_acl.py

test_02_upgrade_kubernetes_cluster
Failure
532.23
test_kubernetes_clusters.py

ContextSuite context=TestNestedVirtualization>:teardown
Error
2.14
test_nested_virtualization.py

[SF] Trillian test result (tid-7594)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 39231 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7594-kvm-centos7.zip
Smoke tests completed. 106 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

ContextSuite context=TestNetworkACL>:teardown
Error
86.85
test_network_acl.py

ContextSuite context=TestNestedVirtualization>:teardown
Error
2.15
test_nested_virtualization.py

@blueorangutan package

@DaanHoogland a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@DaanHoogland a [SF] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-7618)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 39688 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7618-kvm-centos7.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@blueorangutan package

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 7050

@blueorangutan test matrix

@blueorangutan test matrix

[SF] Trillian test result (tid-7682)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 41775 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7682-kvm-centos7.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

[SF] Trillian test result (tid-7680)
Environment: xenserver-71 (x2), Advanced Networking with Mgmt server 7
Total time taken: 45661 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7680-xenserver-71.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

[SF] Trillian test result (tid-7681)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server r8
Total time taken: 51122 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7915-t7681-vmware-67u3.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File


Tox tests don't run out of the box

(coming back several hours later)
There was a space in the real path.
Seriously, like, seriously?

Fresh install, Python 2.7 either in virtualenv or in no virtualenv, installed only tox (and dependencies, obviously).
# tox
GLOB sdist-make: /Users/ssteiner/path with space/swagger-tester/setup.py
py27 create: /Users/ssteiner/path with space/swagger-tester/.tox/py27
py27 inst: /Users/ssteiner/path with space/swagger-tester/.tox/dist/swagger_tester-0.2.7.zip
ERROR: invocation failed (errno 2), args: ...<the traceback>

So, tox can't find the distribution to install.
Thinking that maybe there was an assumption that the distribution files would be there, I tried:
# python setup.py develop
# tox

That failed the same way, so I tried # make dist prior to the tox call with identical results.
Even tried adding setup.py develop to [testenv] commands section, but it's failing before it even gets there.
# make test works, # make test-all fails as above.
 NOTE: YES, tox fails with space in path, really?

Sigh.


Document search should allow a way to see all the documents matching search terms

Description
The document search should allow showing more documents than the fixed limit of 200. This should be done so that it is only possible if you are searching for one group of documents, as otherwise the ordering and paging is hard from the ui perspective (do I need to scroll past all drafts before I get to RFCs)..
But if you have only one type of documents visible (for example either active internet-drafts, or only RFCs), then at the end of the page there should next page button, and perhaps even quick jump buttons to specific pages. If the search is returning thousands of items we do not want to show them all in one huge page, as that would be again hard from the ui perspective.
Best would have page numbers and some way of showing which page contains what as first item (If the document list is sorted by draft name, the page 33 could say first draft on this page is draft-xxx on the tooltip, if the document list is sorted by the date, the page 33 would say the first item is 2020-03-13 etc).
This is bigger change as we need do sorting also on the python code, where currently I think it is done in javascript in browser.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

@kivinen could we give this issue a better title?

This could go the route of using the django paging framework, or, more likely, a better front-end/back-end separation and results via graphql that lets the front-end do efficient paging.


Visual problems on mobile with link issue

Steps to reproduce

Login to Zafira (Admin) from Mobile
Open test runs tab
Open test run
Click on 3 dots on failed test
Select Link issue

Actual behavior
Link/unlink function is not visible with one long word in summary in Safari

Unexpected stripe above the save button In Chrome

Environment
ui v.1.27.RC4 | server v.4.1.81.RC1 | client v.4.1.65
iOS 13.1.3

Verified in ui v.1.24-SNAPSHOT | server v.1.489-SNAPSHOT | client v.1.0-SNAPSHOT.


git commit -m"changed css for form layout and added 6th post"

first pull request

added new blog page font and style need sorting out though


Unable to get/set data in onremove callback

Is it possible to GET/SET values inside onremove callback?
import(
  "github.com/allegro/bigcache"
)

var cache *bigcache.BigCache
onRemove := func(key string, entry []byte) {
  // THIS DOESNT WORK
  f, err := cache.Get("test")
}

config := bigcache.Config{
  // number of shards (must be a power of 2)
  Shards: 5,
  // time after which entry can be evicted
  LifeWindow: 5 * time.Second,
  // Interval between removing expired entries (clean up).
  // If set to <= 0 then no action is performed. Setting to < 1 second is counterproductive — bigcache has a one second resolution.
  CleanWindow: 6 * time.Second,
  // max entry size in bytes, used only in initial memory allocation
  MaxEntrySize: 5000,
  // prints information about additional memory allocation
  Verbose: false,
  // callback fired when the oldest entry is removed because of its expiration time or no space left
  // for the new entry, or because delete was called. A bitmask representing the reason will be returned.
  // Default value is nil which means no callback and it prevents from unwrapping the oldest entry.
  OnRemove: onRemove,
}
cache, err = bigcache.NewBigCache(config)

Nice solution, thanks for sharing 😉


Implement protocol tunneling

I want to be able to tunnel connections - either arbitrary port/ip pairs or socks4/5 - out of a client. The idea is, you compromise a service, install the client on it, and tunnel other connections through the client. They'll be exposed "out of the box", and will also be able to be created through 'command mode'.
How it'll actually look on the client and server remains to be seen. I'll likely imitate the ssh options (-L/-R/-D), but if anybody is invested in this then please let me know!

Subscribing, I can't wait! :+1:

Oh noes, now I'm committed! :)
I'm finishing up a major refactor right now, just a few little things left.
Then I want to add a couple features, this being one of them. I don't think
it'll be super hard, but I didn't want to start before I cleaned up the
codebase.
If you have any special requests / scenarios you want to make sure I
handle, let me know!
On Thu, Sep 17, 2015 at 12:48 PM, Brandon Chalk<EMAIL_ADDRESS>wrote:

Subscribing, I can't wait! [image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/39#issuecomment-141205993.

Well, if you're asking, I definitely would like compatibility with Powercat and the ability to tunnel ports, specifically both ways (-L/R) would be ideal!
Ideally I see a a compromised host running some control program and talking to a TCP localhost:port and having Powercat/Dnscat2 handling all the middle work and having the communication end up on my HTTPS or similar C2 port listening on my same Dnscat2 server.

Cool! That's sort of what I was imagining - having the equivalent of
-R/-L/-D:

Being able to listen on a specific ip:port on the server and connect to
a specific ip:port on the other side of the tunnel

Being able to listen on a specific ip:port on the client and have
connections go to a specific ip:port on the server's network

Open a proxy on the server that would come out through the client, so
you can proxy anything into the target network

I think that covers what you said. :)
Ron
On Thu, Sep 17, 2015 at 1:04 PM, Brandon Chalk<EMAIL_ADDRESS>wrote:

Well, if you're asking, I definitely would like compatibility with
Powercat and the ability to tunnel ports, specifically both ways (-L/R)
would be ideal!
Ideally I see a a compromised host running some control program and
talking to a TCP localhost:port and having Powercat/Dnscat2 handling all
the middle work and having the communication end up on my HTTPS or similar
C2 port listening on my same Dnscat2 server.
—
Reply to this email directly or view it on GitHub
https://github.com/iagox86/dnscat2/issues/39#issuecomment-141210122.

Any updates?

+1


Anyway to override or add env tag for logging?

I have multiple Kubernetes clusters for different environments and I would like to tag env or environment depending on the environment. I used to do this using _meta but not sure if this still works.
Currently I see pre-populated value env=172 (not sure what this means or where from) on Splunk and I wonder if I can override this value to something like env=stage, env=prod, etc, or create a new tag something like environment=stage

Has anyone got an answer for this?? We are looking to do the same...

you can use the clusterName field for eg. https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-kubernetes-logging/values.yaml#L316
Closing this for now, create a new issue if this work for you. Thanks.

I am not sure if this is a known issue but, yes we are using cluster_name on production.
However search with the field is not always populated. I need to dig further but it only works for some specific sourcetypes, and some of the containers are not working with cluster_name at all.

You can have a look at the following PR https://github.com/splunk/splunk-connect-for-kubernetes/pull/185 and the commit merged to develop https://github.com/splunk/splunk-connect-for-kubernetes/commit/2addba7458d9e30a31f7bb861f9cdc71cb155dca
If you find more issues, please file a new issue letting us know which metrics/events are missing the cluster name field. Thanks.


Uncaught TypeError: $(...).pickatime is not a function

It seems there is something broken with a few components.
I've got this error using
<script type="text/javascript" src="https://code.jquery.com/jquery-3.2.1.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/materialize/0.100.2/js/materialize.min.js"></script>.
At first I thought I messed up but it seems to affect https://react-materialize.github.io/#/forms as well. You can see it by looking into the console.
scrollspy also does this.

http://materializecss.com/ and https://react-materialize.github.io/#/forms are not the same thing. You ca see that the time picker at http://materializecss.com/forms.html is working correctly.
Can you post your code? I am confident the issue is on your end.

Please search closed issues first

Thank. I'll try to solve this issue with react-materialize since we both use react.


Typos in Chapter on Auto-regressive Models [version 2022-03-14]

(Findings due to Aalto Seminar students)
Comments are formatted via LaTeX.
Given the old version some of them are probably outdated.

p838, l43: However, at at test" $\to$ However, at test"
p839, l24: This is decoder-only" $\to$ This is a decoder-only"
p839, l36: tasks that is has never" $\to$ tasks that it has never"

fixed, thanks


exp/lighthorizon: enforce the limit from request on the reponse size of tx list

check the page limit parameter on tx and ops listing requests, it should determine the response results size.
Closes #4430
Confirmed by live testing, exported and indexed small ledger range,
START_LEDGER= 1538223
STOP_LEDGER= 1538323
/transactions processes the cursor and limit query string parameters, if no limit defaults to 10
request by cursor: l=1538223, t=1, o=1
GET localhost:8080/transactions?cursor=6606617478959105&limit=2
{
  "_links": {
    "self": {
      "href": "http://localhost:8080/transactions?cursor=\u0026limit=0\u0026order="
    },
    "next": {
      "href": "http://localhost:8080/transactions?cursor=6606621773930497\u0026limit=0\u0026order="
    },
    "prev": {
      "href": "http://localhost:8080/transactions?cursor=6606621773926401\u0026limit=0\u0026order=asc"
    }
  },
  "_embedded": {
    "records": [
      {
        "memo": "xdr.Memo{Type: xdr.MemoTypeMemoNone}",
        "_links": {
          "self": {
            "href": "http://localhost:8080/transactions/544469b76cd90978345a4734a0ce69a9d0ddb4a6595a7afc503225a77826722a"
          },
          "account": {
            "href": ""
          },
          "ledger": {
            "href": ""
          },
          "operations": {
            "href": ""
          },
          "effects": {
            "href": "http://localhost:8080/transactions/544469b76cd90978345a4734a0ce69a9d0ddb4a6595a7afc503225a77826722a/effects"
          },
          "precedes": {
            "href": "http://localhost:8080/effects?order=asc\u0026cursor=6606621773926401"
          },
          "succeeds": {
            "href": "http://localhost:8080/effects?order=desc\u0026cursor=6606621773926401"
          },
          "transaction": {
            "href": ""
          }
        },
        "id": "544469b76cd90978345a4734a0ce69a9d0ddb4a6595a7afc503225a77826722a",
        "paging_token": "6606621773926401",
        "successful": true,
        "hash": "544469b76cd90978345a4734a0ce69a9d0ddb4a6595a7afc503225a77826722a",
        "ledger": 1538224,
        "created_at": "2022-06-17T23:29:42Z",
        "source_account": "GBGTCH47BOEEKLPHHMR2GOK6KQFGL3O7Q53FIZTJ7S7YEDWYJ5IUDJDJ",
        "source_account_sequence": "",
        "fee_account": "",
        "fee_charged": "84000",
        "max_fee": "0",
        "operation_count": 28,
        "envelope_xdr": "[encoded data, 4672 characters]",
        "result_xdr": "AAAAAAABSCAAAAAAAAAAHAAAAAAAAAADAAAAAAAAAAAAAAACAAAAAAAAAAMAAAAAAAAAAAAAAAIAAAAAAAAAAwAAAAAAAAAAAAAAAgAAAAAAAAADAAAAAAAAAAAAAAACAAAAAAAAAAMAAAAAAAAAAAAAAAIAAAAAAAAAAwAAAAAAAAAAAAAAAgAAAAAAAAADAAAAAAAAAAAAAAACAAAAAAAAAAwAAAAAAAAAAAAAAAIAAAAAAAAADAAAAAAAAAAAAAAAAgAAAAAAAAAMAAAAAAAAAAAAAAACAAAAAAAAAAwAAAAAAAAAAAAAAAIAAAAAAAAADAAAAAAAAAAAAAAAAgAAAAAAAAAMAAAAAAAAAAAAAAACAAAAAAAAAAwAAAAAAAAAAAAAAAIAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAABNMR-fC4hFLec7I6M5XlQKZe3fh3ZUZmn8v4IO2E9RQQAAAAAABn5GAAAAAUVVUlYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAAEDnlMQh53yD1RDVAAAAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAAE0xH58LiEUt5zsjozleVApl7d-HdlRmafy_gg7YT1FBAAAAAAAGfkcAAAABRVVSVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAFVU0RWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAAgc8nAvTYRUK-j7zAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAATTEfnwuIRS3nOyOjOV5UCmXt34d2VGZp_L-CDthPUUEAAAAAAAZ-SAAAAAFFVVJWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAVVTRFYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAAADCtrqEpeNUBFGhBAAAAAAAAAAAAAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAABNMR-fC4hFLec7I6M5XlQKZe3fh3ZUZmn8v4IO2E9RQQAAAAAABn5JAAAAAUVVUlYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAAQOeVELled8CsaWcAAAAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAAE0xH58LiEUt5zsjozleVApl7d-HdlRmafy_gg7YT1FBAAAAAAAGfkoAAAABRVVSVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAFVU0RWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAABRIXnwoFlrkJVJmkAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAATTEfnwuIRS3nOyOjOV5UCmXt34d2VGZp_L-CDthPUUEAAAAAAAZ-SwAAAAFFVVJWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAVVTRFYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAAAGFbXtAt3hogKr7UEAAAAAAAAAAAAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAABNMR-fC4hFLec7I6M5XlQKZe3fh3ZUZmn8v4IO2E9RQQAAAAAABn5MAAAAAUVVUlYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAAcZVDsOkaLRDZcvfAAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAAE0xH58LiEUt5zsjozleVApl7d-HdlRmafy_gg7YT1FBAAAAAAAGfk0AAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAFFVVJWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAB2FvShg76SwZMg_SAAAAAAAAAAAAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAATTEfnwuIRS3nOyOjOV5UCmXt34d2VGZp_L-CDthPUUEAAAAAAAZ-TgAAAAFVU0RWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAUVVUlYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAAAGUd8mxnYMCQa17b8AAAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAABNMR-fC4hFLec7I6M5XlQKZe3fh3ZUZmn8v4IO2E9RQQAAAAAABn5PAAAAAVVTRFYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAABRVVSVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAAVC2xdMqQx_DSLM9AAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAAE0xH58LiEUt5zsjozleVApl7d-HdlRmafy_gg7YT1FBAAAAAAAGflAAAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAFFVVJWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAABDRjn1rIN2gbwopqAAAAAAAAAAAAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAATTEfnwuIRS3nOyOjOV5UCmXt34d2VGZp_L-CDthPUUEAAAAAAAZ-UQAAAAFVU0RWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAUVVUlYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAAADJnfsXe4OVB79tFIAAAAAAAAAAAAAAAAAAAADAAAAAAAAAAAAAAAAAAAAABNMR-fC4hFLec7I6M5XlQKZe3fh3ZUZmn8v4IO2E9RQQAAAAAABn5SAAAAAVVTRFYAAAAAL3ZBkx0hzBH3SxRQmbsxJvS0lyUOUUEqMkdUbvATQ00AAAABRVVSVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAAIZGP3ZhFNkGmUG1AAAAAAAAAAAAAAAAAAAAAMAAAAAAAAAAAAAAAAAAAAAE0xH58LiEUt5zsjozleVApl7d-HdlRmafy_gg7YT1FBAAAAAAAGflMAAAABVVNEVgAAAAAvdkGTHSHMEfdLFFCZuzEm9LSXJQ5RQSoyR1Ru8BNDTQAAAAFFVVJWAAAAAC92QZMdIcwR90sUUJm7MSb0tJclDlFBKjJHVG7wE0NNAAAAAAQxGOcJAfp4CU7cgAAAAAAAAAAAAAAAAA==",
        "result_meta_xdr": "",
        "fee_meta_xdr": "",
        "memo_type": "MemoTypeMemoNone",
        "signatures": [
          "2E9RQQAAAEDOHy2IQJTNEz9kgUbHYolo_qjWo5s1ZkHOo70AQM2DRVWSNb4Py043HLbgZ6B5WdgkAs3gzoQ9sYk77KVZ5CsG"
        ]
      },
      {
        "memo": "xdr.MemoText(\"psp:1405\")",
        "_links": {
          "self": {
            "href": "http://localhost:8080/transactions/5fef21d5ef75ecf18d65a160cfab17dca8dbf6dbc4e2fd66a510719ad8dddb09"
          },
          "account": {
            "href": ""
          },
          "ledger": {
            "href": ""
          },
          "operations": {
            "href": ""
          },
          "effects": {
            "href": "http://localhost:8080/transactions/5fef21d5ef75ecf18d65a160cfab17dca8dbf6dbc4e2fd66a510719ad8dddb09/effects"
          },
          "precedes": {
            "href": "http://localhost:8080/effects?order=asc\u0026cursor=6606621773930497"
          },
          "succeeds": {
            "href": "http://localhost:8080/effects?order=desc\u0026cursor=6606621773930497"
          },
          "transaction": {
            "href": ""
          }
        },
        "id": "5fef21d5ef75ecf18d65a160cfab17dca8dbf6dbc4e2fd66a510719ad8dddb09",
        "paging_token": "6606621773930497",
        "successful": false,
        "hash": "5fef21d5ef75ecf18d65a160cfab17dca8dbf6dbc4e2fd66a510719ad8dddb09",
        "ledger": 1538224,
        "created_at": "2022-06-17T23:29:42Z",
        "source_account": "GCFJN22UG6IZHXKDVAJWAVEQ3NERGCRCURR2FHARNRBNLYFEQZGML4PW",
        "source_account_sequence": "",
        "fee_account": "",
        "fee_charged": "3000",
        "max_fee": "0",
        "operation_count": 1,
        "envelope_xdr": "AAAAAgAAAACKlutUN5GT3UOoE2BUkNtJEwoipGOinBFsQtXgpIZMxQAAJxAAE05oAAHUKAAAAAEAAAAAAAAAAAAAAABirQ6AAAAAAQAAAAhwc3A6MTQwNQAAAAEAAAAAAAAAAQAAAADpPdN37FA9KVcJfmMBuD8pPcaT5jqlrMeYEOTP36Zo2AAAAAJBVE1ZUgAAAAAAAAAAAAAAZ8rWY3iaDnWNtfpvLpNaCEbKdDjrd2gQODOuKpmj1vMAAAAAGHAagAAAAAAAAAABpIZMxQAAAEDNJwYToiBR6bzElRL4ORJdXXZYO9cE3-ishQLC_fWGrPGhWrW7_UkPJWvxWdQDJBjVOHuA1Jjc94NSe91hSwEL",
        "result_xdr": "AAAAAAAAC7j_____AAAAAQAAAAAAAAAB____-gAAAAA=",
        "result_meta_xdr": "",
        "fee_meta_xdr": "",
        "memo_type": "MemoTypeMemoText",
        "signatures": [
          "pIZMxQAAAEDNJwYToiBR6bzElRL4ORJdXXZYO9cE3-ishQLC_fWGrPGhWrW7_UkPJWvxWdQDJBjVOHuA1Jjc94NSe91hSwEL"
        ]
      }
    ]
  }
}

Just getting around to reviewing this - sorry for the delay. Are you sure the noted test actually respects the limit? I see
        "ledger": 1538224

in both records, meaning it never had to look up or ingest another.

Just getting around to reviewing this - sorry for the delay. Are you sure the noted test actually respects the limit? I see
        "ledger": 1538224

in both records, meaning it never had to look up or ingest another. So it may be that it works w/ multiple transactions w/in the same ledger, but not for multiple.

great catch, I think have fixed with this commit. archive.GetTransactions wasn't incrementing tx order num all the time, resulted in skipping all tx's in the first ledger encoded in cursor.


defect/1

http request fails:

URL did not resolve to an image resource, status code %1$s

no longer applicable


ergo: 5.0.6 -> 5.0.7

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ergoplatform/ergo/releases.
meta.description for ergo is: Open protocol that implements modern scientific ideas in the blockchain area
meta.homepage for ergo is: https://ergoplatform.org/en/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.0.7 with grep in /nix/store/1d05n1rx9sxrf8h148f75ii13claxzmd-ergo-5.0.7
found 5.0.7 in filename of file in /nix/store/1d05n1rx9sxrf8h148f75ii13claxzmd-ergo-5.0.7

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
ergo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1d05n1rx9sxrf8h148f75ii13claxzmd-ergo-5.0.7 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ergo https://github.com/r-ryantm/nixpkgs/archive/cb0581d6608bf251cb08c3915caf3d48a89e10af.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1d05n1rx9sxrf8h148f75ii13claxzmd-ergo-5.0.7
ls -la /nix/store/1d05n1rx9sxrf8h148f75ii13claxzmd-ergo-5.0.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

ergo

Maintainer pings
cc @mmahut for testing.

Result of nixpkgs-review pr 217525 run on aarch64-darwin 1

1 package built:

ergo


Add margin-top to tabs

Fix for #6

Thanks! did this manually, works like a charm :)

Bump. I find that I need 15px or icons are clipped. Here's what I get with 15px:

and with 10px:

So like, it goes up to another 10px every atom update 😄

Closing in regards to #22


[Draft] Add test network agent for ncproxy dev work

This draft PR contains a test version of a vnetagent that we can use locally when doing dev work with ncproxy. This is not meant to be used outside of a testing environment.
Adding as draft right now since this depends on recent changes to ncproxy that are still in PR. CI will currently fail for this.
Please let me know if you have any suggestions on useful tests for this.
Signed-off-by: Kathryn Baldauf<EMAIL_ADDRESS>

@dcantah in particular :)

One note: I would probably put this under internal/tools since it's a test binary.

Thanks for making this btw ❤ I'll keep the review up on Monday

I'm wondering how we could make some useful tests here.. We need to launch ncproxy and the test agent and make calls between them to have anything of value

re-lgtm


versions: bump kata ref

Bumping kata to include a fix for image layer ordering

The CI e2e tests have passed here now too :)


Make graphs nice and pretty

@dylwhich mentioned pulling this into a seperate plugin.

While developing 00296a7 I spent quite a while working trying to get the Materialbox plugin to work, but had no luck. I think it is perfect for this use-case, but has strange errors when used with AngularJS.
In order to initialize it for dynamically-added content (such as the graphs in cards that are loaded on-the-fly), AngularJS must be in charge of running the JQuery code. However, when the image gets clicked afterward, the overlay winds up in the wrong place in the DOM, obscuring the image.
I have no idea how to fix this.


1.1.0 broke Dialog component

Hi there,
I am having an issue with the Dialog component in version 1.1.0. When I try to import it in my pages/index.vue and build the project, I get the following error:
 ERROR  'Dialog' is not exported by node_modules/.pnpm/nuxt<EMAIL_ADDRESS>imported by pages/index.vue?vue&type=script&setup=true&lang.ts                                                                                02:19:33
file: /home/dreamingcodes/Desktop/event-scheduler/pages/index.vue?vue&type=script&setup=true&lang.ts:9:9
 7: import { default as __nuxt_component_6 } from "/home/dreamingcodes/Desktop/event-scheduler/node_modules/.pnpm/nuxt<EMAIL_ADDRESS> 8: import { TransitionRoot as __nuxt_component_7 } from "/home/dreamingcodes/Desktop/event-scheduler/node_modules/.pnpm/@headlessui+vue<EMAIL_ADDRESS> 9: import { Dialog as __nuxt_component_8 } from "/home/dreamingcodes/Desktop/event-scheduler/node_modules/.pnpm/nuxt<EMAIL_ADDRESS>             ^
10: import { TransitionChild as __nuxt_component_9 } from "/home/dreamingcodes/Desktop/event-scheduler/node_modules/.pnpm/@headlessui+vue<EMAIL_ADDRESS>11: import { DialogPanel as __nuxt_component_10 } from "/home/dreamingcodes/Desktop/event-scheduler/node_modules/.pnpm/nuxt<EMAIL_ADDRESS>

 ERROR  'Dialog' is not exported by node_modules/.pnpm/nuxt<EMAIL_ADDRESS>imported by pages/index.vue?vue&type=script&setup=true&lang.ts                                                                                02:19:33

  at error (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:1858:30)
  at Module.error (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:12429:16)
  at Module.traceVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:12788:29)
  at ModuleScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:11440:39)
  at FunctionScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
  at ChildScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
  at ReturnValueScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
  at ChildScope.findVariable (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:6372:38)
  at Identifier.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:7439:40)
  at VariableDeclarator.bind (node_modules/.pnpm/rollup@2.79.1/node_modules/rollup/dist/es/shared/rollup.js:5269:23)

My project deps:
  "devDependencies": {
    "@morev/vue-transitions": "^2.3.5",
    "@nuxt/image-edge": "1.0.0-27840416.dc1ed65",
    "@nuxtjs/color-mode": "^3.2.0",
    "@nuxtjs/robots": "^3.0.0",
    "@nuxtjs/tailwindcss": "^6.2.0",
    "@prisma/client": "^4.8.1",
    "@sidebase/nuxt-auth": "^0.3.3",
    "@types/animejs": "^3.1.6",
    "animejs": "^3.2.1",
    "nuxt": "3.0.0",
    "nuxt-headlessui": "^1.1.0",
    "prisma": "^4.8.1",
    "sass": "^1.57.1"
  }

This error did not occur in previous versions.

Does it work in development mode but only fail during build?

Does it work in development mode but only fail during build?

Exactly


CoreText note: Client requested name ".SFUI-Regular" 如何解决

CoreText note: Client requested name ".SFUI-Regular", it will get TimesNewRomanPSMT rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[UIFont systemFontOfSize:].
出现该问题的时候会有明显的UI 卡顿

同样遇到这个问题。


Improved the type checking for uses of scan.

Previous way of checking was done after flattening and got
easily confused by tuples of different shapes, or None.
Relates to https://github.com/google/jax/issues/1534.

does this actually fix the error reporting problem from #1534, or is it just related?

I have changed the implementation to compare pytreedefs instead of pytrees themselves. It was a good opportunity to learn more about how pytrees work.
I have also expanded the tests to show the complete actual error message.

does this actually fix the error reporting problem from #1534, or is it just related?

It does fix it; one of the test cases directly targets this bug


how to initialize the instance decoder query

Does the paper initialize human query and object query to different values,then self-attention together?
I think instance decoder focus on parts feature, so human query and object query should go to self-attention separately as it in [Reference Paper 5], i cannot find description about this in paper.
waiting for your reply,Thank you!

Hi, the human and object queries are both with random initialization and add the same position embedding in the same position.


VSCode doesn't display Markdown images in Jupyter Notebook

Issue Type: Bug
Loaded a Jupyter notebook from https://github.com/lukepolson/youtube_channel/blob/main/Python Tutorial Series/image_processing1.ipynb
(also downloaded associated '../Data/CT_scan.npy' and '../images/HU.png').
There is a Markdown cell (I believe it is #5 from the top) that displays the HU.PNG image inline.  This works on the 'jupyter lab' command line running in Chrome, but doesn't display properly in VSCode (I instead get a broken image link icon with the alternative text displayed).
I also tried the direct Markdown code of
![Table of typical HU Values](../images/HU.png)
and that renders perfectly in Jupyterlab running on Chrome, but not in VSCode.
VS Code version: Code 1.69.0 (Universal) (92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9, 2022-07-07T05:28:41.511Z)
OS version: Darwin arm64 21.5.0
Restricted Mode: No

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
10, 9, 9

Memory (System)
16.00GB (0.10GB free)

Process Argv
--crash-reporter-id e7f6bfec-c4a0-49d2-98c4-5b5c48019475

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

code-gnu-global
aus
0.2.2

vscode-open-in-typora
cyb
1.2.0

vscode-mac-color-picker
dae
1.0.2

vscode-markdownlint
Dav
0.47.0

vscode-dash
dee
2.4.0

gitlens
eam
12.1.1

theme-macos-classic
hua
1.4.2

latex-workshop
Jam
8.27.2

vscode-ksdiff
kal
1.0.0

vsc-python-indent
Kev
1.17.0

rainbow-csv
mec
2.4.0

python
ms-
2022.10.0

vscode-pylance
ms-
2022.7.20

jupyter
ms-
2022.6.1001902341

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.8

cpptools
ms-
1.10.8

autodocstring
njp
0.6.1

printcode
nob
3.0.0

indent-rainbow
ode
8.3.1

vscode-css-peek
pra
4.2.0

code-settings-sync
Sha
3.4.3

python
tht
0.2.3

vscodeintellicode
Vis
1.2.22

change-case
wma
1.0.0

material-theme
zhu
3.15.2

(10 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdf:30486550

Works fine for me when you open that project as a workspace:

If you just open the single file (without opening any workspace) we don't allow the image to be accessed  for security reasons since it uses .. to travers up to a parent folder

That makes sense, I so rarely open notebooks directly instead of in a workspace I didn't catch it.  Thanks!


Held item in mirror rendering inside-out with sodium

Issue happens with shaders on or off

My bad, the issue only happens with sodium + iris


Updated Session / App Lifecycle logic

More accurately replicated Amplitude's Session logic.
Added support for amplitude lifecycle events.
Amplitude specific events are blocked from all destinations other than Amplitude.
Added privacy manifest.

Hi @skydivedan, yeah sure!  Those application opened events are what the amplitude SDK would do to properly track mobile sessions.  I would've preferred that the Action Destination did this on the segment.com side, but that team wasn't going to have any time opening up in the near future to fix it.  I'm not entirely sure how amplitude uses those events internally, but we received reports from customers that their stats on amplitude weren't correct because of these missing events.


Support GoToAction in composer

Is your feature request related to a problem? Please describe.
I want to create looping logic similar to a while loop based on a condition to repeat a number of steps in a dialog until the user is done. GoToAction allows me to create this logic simply and fills the feature gap.
Describe the solution you'd like
Support GoToAction node, and include a dropdown with the actions in the current dialog so I do not have to explicitly create a new id for the node I want to goto.
Describe alternatives you've considered
I copied the current gotoaction into my custom actions library and verified it works for me, but it does not have a full UI to make the scenario easy to use.
Additional context

refs #2375


Visiting :8000 on Mac doesn't work.

File: get-started/part2.md

Thanks for sharing the issue. The topic has been updated.
If you're still experiencing issues, please try to find support in the Docker Community Slack or Forums:

https://forums.docker.com/
https://dockercommunity.slack.com/


Create a report with all benchmarks results

The report should address the batched verification time concerns and also list optimizations we could add to the protocol.

Given that the main issue concerning this turn out to not be directly related to batch verification this report is no longer very relevant.
An optimization was found in the process, in a new issue https://github.com/o1-labs/proof-systems/issues/1061.


Change the text highlighting color

Is your feature request related to a problem? Please describe.
When I select text it hides the text it is because I think the text highlighting color is black and the background color is also black so the text hides
Describe the solution you'd like
Change the text highlighting color the appropriative one i.e. light,blue,light cyan, etc

hey @UG-SEP please be specific where this problem is occurring or share some screen shots or videos

before

After i selected the written text

ok @UG-SEP go ahead :)
Dead line 2 july


proofs+tarodb: stop storing proofs files in the DB switch to mmap access to on disk files everywhere

Today we store proofs in the DB, mainly for simplicity and to ensure we can atomically update proofs when we modify assets. IMO what we really want to do is only store them on disk, them use memory-mapping to access the proofs over contained memory regions. This means we minimize copying, and can pass around pointers in memory to the relevant mmap'd region. On top of this, we'll either want to maintain an external file w/ an index, or maintain the index within the database itself.

"memory mapping the subdirectory"
would enable the path be an S3 bucket


Incorrect Time is displayed when check the Submit time

Gitea version (or commit ref): 1.9.0 docker
Git version:
Operating system: Centos
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
The submit time is about 1 o'clock.
The Check time is about 2 o'clock.
The submit time description is right which is an hour ago,
but the Exact moment should be about 1 o'clock on the morning of August 3, but now is about 15:21 of August 3 . . .
But where the wrong submit time come from?
I noticed that issue #7239 maybe the same problem or a very similar problem  ...
Screenshots

I hv checked the time in the docker and the server time, there are the same.

Should be closed by #7792


Add Loadable Components to Code Splitting doc

Since React Loadable is not a standard and does not provide any support (issues are disabled), I think it is good to give users an alternative: Loadable Components.

This can probably be closed, since on latest loadable-components is the recommendation for server-side code splitting.

🎉


Uncaught Error: Cannot call function 'isFocused' on missing remote object 22Error: Cannot call f...

[Enter steps to reproduce:]

...
...

Atom: 1.39.1 x64
Electron: 3.1.10
OS: Unknown Windows version
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot call function 'isFocused' on missing remote object 22
Error: Cannot call function 'isFocused' on missing remote object 22
at throwRPCError (C:\ProgramData\home\atom\app-1.39.1\resources\electron.asar\browser\rpc-server.js:145:17)
at EventEmitter. (C:\ProgramData\home\atom\app-1.39.1\resources\electron.asar\browser\rpc-server.js:367:7)
at EventEmitter.emit (events.js:182:13)
at WebContents. (C:\ProgramData\home\atom\app-1.39.1\resources\electron.asar\browser\api\web-contents.js:294:13)
at WebContents.emit (events.js:182:13)
At C:\ProgramData\home\atom\app-1.39.1\resources\electron.asar\renderer\api\remote.js:219

Error: Cannot call function 'isFocused' on missing remote object 22
Error: Cannot call function 'isFocused' on missing remote object 22
    at throwRPCError (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/browser/rpc-server.js:145:17)
    at EventEmitter.<anonymous> (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/browser/rpc-server.js:367:7)
    at EventEmitter.emit (events.js:182:13)
    at WebContents.<anonymous> (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/browser/api/web-contents.js:294:13)
    at WebContents.emit (events.js:182:13)

    at metaToException (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/renderer/api/remote.js:271:17)
    at Object.exception (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/renderer/api/remote.js:219:30)
    at metaToValue (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/renderer/api/remote.js:223:28)
    at Object.remoteMemberFunction (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/renderer/api/remote.js:123:16)
    at BackgroundTipsElement.shouldBeAttached (C:/ProgramData/home/atom/app-1.39.1/resources/app/static/<embedded>:11:664921)
    at BackgroundTipsElement.updateVisibility (C:/ProgramData/home/atom/app-1.39.1/resources/app/static/<embedded>:11:664735)
    at e (C:/ProgramData/home/atom/app-1.39.1/resources/app/static/<embedded>:11:663700)
    at CallbacksRegistry.apply (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/common/api/callbacks-registry.js:47:25)
    at EventEmitter.ipcRenderer.on (C:/ProgramData/home/atom/app-1.39.1/resources/electron.asar/renderer/api/remote.js:285:21)
    at EventEmitter.emit (events.js:182:13)

Commands
     -2:33.8.0 application:open-file (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -2:11.5.0 application:open-folder (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)

Non-Core Packages
atom-live-server 2.3.0
clean-wrap-guide 0.1.4
emmet 2.4.3
minimap 4.29.9

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/16630 so you can subscribe there for updates if you'd like (we believe that this will be fixed in a future Electron upgrade).

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.