Time necessary for BibTeX QuickCopy around 4 seconds

I am using Zutilo to get a Quick Copy of the BibTeX of an item in Zotero (Better BibTeX.js in quickCopy_alt1), either from the main pane, or from the PDF Viewer.
In the Debug Output, I can see the time taken for the basic Quick Copy options: it typically takes less than 1 second to "Copy Selected Item Citations to Clipboard" (Ctrl+Shift+A) or "Copy Selected Items to Clipboard" (Ctrl+Shift+C). So, by the time I want to paste, I usually get it correctly. For example:
"Copied bibliography to clipboard in 518 ms"
However, for a BibTeX Quick Copy, the typical time is around 4 s (3 to 5 s, rough from the Debug Output).
I use this shortcut to get my references in LaTeX. My copy-paste speed is probably around 2 seconds. So I thought for some time that there was a problem in Zutilo, with the Quick Copy not working, and changed different keyboard shortcut. I realized recently that if I wait long enough, the BibTeX text is actually correctly copied.
Is this time normal, or is there something wrong in my Zotero?
Would it be possible to reduce the time of Quick Copy for BibTeX? Or is there a fundamental limitation behind, and I should get used to wait these 5 seconds before pasting the BibTeX in LaTeX?
On a side note, would it be possible to get the time estimate of the BibTeX QuickCopy, in the same way as shown above? Or is this a Zutilo or Zotero feature request?
Debug log ID: HK8ZU6U8-refs-apse
Thank you very much for the plugin and its maintenance.

I don't see any BBT or export activity in the HK8ZU6U8-refs-apse. I don't know whether zutilo uses foreground or background exports; background exports have a relatively long ramp-up time so I could see that using close to two seconds, but cold or hot cache behavior for background exports for 1-10 items was consistently below 2 secs for my, and only cold-cache on 12 items git me 2.1 seconds. Foreground export took approx 12 milliseconds for me (12 items, hot cache).
With BBT or export activity I might be able to tell, but as it is, I cannot replicate the behavior, and I'd need to know whether Zutilo is doing foreground or background exports.

I have tried to generate the Debug log ID again from an item: 8568DP9K-refs-euc
And from the Help menu: TUR83BJW-euc
Hopefully this is the correct process to make the Debug log ID.
I see something like this in the Zotero Debug Output:
(3)(+0011932): Preloading ca65189f-8815-4afe-8c8b-8c7c15f0edca for Quick Copy
(3)(+0000029): {better-bibtex} +11969 worker export skipped, user has chosen foreground export for Better BibTeX
(4)(+0000001): Translate: Binding sandbox to http://www.example.com/
(4)(+0000003): Translate: Parsing code for Better BibTeX (ca65189f-8815-4afe-8c8b-8c7c15f0edca, 2022-09-03)
(3)(+0002866): Translate: Beginning translation with Better BibTeX
(3)(+0000012): Translate: Translation successful
(5)(+0000001): Translate: Running handler 0 for done
(5)(+0000002): Translate: Running handler 1 for done
But no time information.

Zotero takes 2 seconds to parse the translator. The parse result should be kept in memory for quick re-use but it doesn't, and it's a long-standing problem I have gotten no response to when I asked. I have re-raised the issue here.

I have an idea for a fix but it won't be a quick fix, this will take a while.

That would be great. Thank you very much.

New builds will drop here occasionally, you can ignore them for the time being.

Can you try build 3259?

It is working perfectly now. I could not notice any latency anymore.
The copy paste is always successful now, even with 200 items!
I do not get anything in the way anymore for my writing workflow in LaTeX.
Very impressive. Thank you very much!

Thanks for driving this change. I have a few more cleanup tasks but will then release a new version. You will be upgraded to that automatically.


Allow git node land with full PR urls

https://github.com/nodejs/node-core-utils/issues/206#issuecomment-371827740

Just to add, it looks like you can't currently do git node land https://github.com/nodejs/node/pull/19130.

@cPhost

@gibfahn can you please assign it to me? I'll take a look in free time


Chore: Expose sns proposal action types

Motivation
Expose the action types of SNS proposals.
They will be used to convert the optional parameters into T | undefined instead of [T] | [].
Changes

Export action types in index.ts for sns-js.

Tests
Not applicable.

@mstrasinskis @peterpeterparker please review

@lmuntaner we still need this PR?

No, I don't think we need this here. @mstrasinskis what do you think?

Given the lack of activity in this PR since months I guess we do not need it.
@lmuntaner @mstrasinskis feel free to reopen it if I misunderstand the status.


Add the ability to use RequireAuthorization when using MapPost to add authentication policies to the graphql endpoint

#304 Add the ability to pass authorization policies that should be applied to the Post Endpoint.  By passing in the authorization policies and using RequireAuthorization, the entire graphql endpoint can be easily secured with an authorization policy.
I added an additional optional string array parameter to the MapGraphQL extension and passed it to the RequireAuthorization() method for the MapPost call.
This allows using .net asp.net core authorization policies on the endpoint to enable ensuring users are authenticated

Thanks for this! Any chance you could update the docs with an example of how to use please?

I will work on getting the documentation updated if the coding changes will be accepted with the updated documentation.
Thanks
Jessica
Get Outlook for iOShttps://aka.ms/o0ukef

From: Luke Murray @.>
Sent: Tuesday, May 9, 2023 2:23:57 AM
To: EntityGraphQL/EntityGraphQL @.>
Cc: Jessica @.>; Author @.>
Subject: Re: [EntityGraphQL/EntityGraphQL] Add the ability to use RequireAuthorization when using MapPost to add authentication policies to the graphql endpoint (PR #305)
Thanks for this! Any chance you could update the docs with an example of how to use please?
—
Reply to this email directly, view it on GitHubhttps://github.com/EntityGraphQL/EntityGraphQL/pull/305#issuecomment-1539630623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXFKBQ6EEOUBBOLND64CV3XFIEK3ANCNFSM6AAAAAAXUQSAGQ.
You are receiving this because you authored the thread.Message ID: @.***>

Yes, the code changes look good. Thank you!

@lukemurray Documentation updated.  I put it in the Quick Start guide since security on the endpoint should be a universal requirement for most applications that want to restrict access.


Fixes an issue where Chromecast audio groups were not properly discovered

The issue is described at #2909
The fix is working on my setup, but I can't seem to prepare the test environment in order to successfully run tox (I get some InvocationError and a keychain issue somehow), even before my change.
Can somebody either help me reliably run the tests (so that I can adapt them for my modification), or take over this change and make it good enough to be merged? Thanks!

Travis will run your CI and give you feedback, so there is that.
Can you elaborate on how this change works ? The only difference I see is that instead of host + port, you only pass host now to the Cast constructor.

Hi @balloob, the change consists in using the Chromecast object returned by the get_chromecasts() call rather than building one just using port and host.
This way we get correct friendly names for Chromecast Audio groups too. Using only host and port results in duplicate names instead.

@hcooper I'm not sure how to fix the tests as I'm really a noob when it comes to Python (in particular I've never seen the mocking logic/library used here).
How do you recommend to proceed here?

Here's an example fix for the test:
https://gist.github.com/hcooper/4b3ed0425e1e1537aa29f23ad560d29f
It adds a mock for the response of get_chromecasts(). This means some_host (which in the first test is being passed-in as if it was hardcoded in the config file) gets matched in your "found" logic.
There may be a better alternative to creating the FakeChromeCast() object, but this works for now. I'm not too brilliant at python testing either, and these aren't the easiest tests to decipher, but this should work for now :-)

Looks like there's 2 minor lint errors to fix, see the bottom of https://travis-ci.org/home-assistant/home-assistant/jobs/165585595
I'm not that familiar with the coverage test, it seems to be mentioning file that haven't changed in this PR (maybe rebase your checkout at a guess?).
For the comment, I was thinking it should describe why there's another call to pychromecast, e.g. "get_chromecasts() returns Chromecast objects with the correct friendly name for grouped devices"
Thanks for all the fixes :-)

The coverage test can be ignored.

@hcooper I would like to fix the last lint warnings and to improve the comment as you suggested, but can't see how to do both at the same time. This line length rule is strange for me, if I solve the lint issues I'll break the line length rule, for instance.

Can you not just split the line onto two? And the line length rule is currently broken by a comment, which can also be fixed easily, either by rewording it or just putting half of it on a second comment line

Sure, I basically restored that line as it was originally. Now it will complain because it's too long (that's why I had to split it).
I rephrased the comment and put it in multiple lines

@hcooper any chance you could help us out with some additional detail about fixing those lint errors?

Sure.
Before:
~/code/home-assistant: pylint homeassistant/components/media_player/cast.py
************* Module homeassistant.components.media_player.cast
C: 66, 0: Line too long (116/100) (line-too-long)
C: 76, 0: Wrong continued indentation (add 1 space).
                if (device.host, device.port) == host]
                ^| (bad-continuation)

After applying: https://gist.github.com/hcooper/d31958353dc5a1f2732fbb73dd8ca207 (it just breaks line 66 so it's less than 100 characters long, and bumps line 76 one space in so the contents of the square brackets align)
~/code/home-assistant: pylint homeassistant/components/media_player/cast.py
Hope that helps :-)

Ahh, viewing it on mobile made the "bad continuation" message show up in the wrong place and had me confused. Thanks!
@vittoriom if you want to make these changes that would be great, otherwise I'll try to set up a dev environment tomorrow to implement it.

Thanks a lot @hcooper! I'll surely do that this evening so that maybe this PR will finally be merged :)

This change broke docker support for google cast. See #4469.


 don't work when contents is valid html tag

Failing input:(note use of <dir>)
General options:

  * `-d`, `--output-directory` <dir>:
    Some text.

  * `-j`, `--max-jobs` <jobs>:
    More text.

Failing output: "dir" and "Some text." is missing.
       General options:

       -d, --output-directory

       -j, --max-jobs jobs
              More text.

So, I think this is expected: because Markdown allows you to mix in HTML markup, it expects any <foo> tags to be valid HTML tags.
If you want to render a literal <, you should use the < HTML entity:
General options:

  * `-d`, `--output-directory` <dir>:
    Some text.

  * `-j`, `--max-jobs` <jobs>:
    More text.

Sorry about the inconvenience here, but it seems (to me) to be the only way to resolve the format specifications.


Document the Baby Dragons

Try to figure out the code and add helpful documentation for the various files!
The better the documentation, the more the points!

type_content.h: 5 Bounty Points
client.c: 5 Bounty Points
tc.c: 5 Bounty Points
tc.h: 5 Bounty Points

Can I work on this, please? There is a problem with my python compiler and I need to work on C only. Pleaseee give it to me

@Geeker357 You may work on this! You have been assigned!

Can I work on this bro? Also come to Seminar Hall 1 for treasure hunt

Ill be reassigning this to @TejasB02!

dude give me 15 more min , please

I got started already. Can I please submit it

Sorry you didnt give us an update :/
let's wait for a while

Can I work on this?

Go ahead Varuni! @varuni7

hey can i work on this

@siddarthpai go for it !

can I work on this?

Open access, go ahead!


Cannot get all notes from a post

There is a limit of 50 and there is no offset like in getting all post to traverse. I would like to make a suggestion to add options where you can put limit and offset to traverse all notes.

You should likely use pagination
https://github.com/tumblr/jumblr#pagination

You can only use pagination when getting posts not in notes. For example
how will you use the options to get all notes when there is no api for that?
On Sep 12, 2017 9:31 PM, "Kirill Suslov"<EMAIL_ADDRESS>wrote:
You should likely use pagination
https://github.com/tumblr/jumblr#pagination
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tumblr/jumblr/issues/111#issuecomment-328850933, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJyhQpA5PGkpVIqPKJsrLP-hGIH9n3g_ks5shoUVgaJpZM4PUJCT
.

Sorry, you were right
Seems like post type doesn't support note pagination
https://github.com/tumblr/jumblr/blob/master/src/main/java/com/tumblr/jumblr/types/Post.java


CR00026 Updated comments

Signed-off-by: Kenny Smith<EMAIL_ADDRESS>

Accepted CR00026 branch changes.


Run

How do i run tool after  installation is complete  ?

After installation, you should be able to just type osintui in your terminal, and run the the tool.

After installing rust and attempting installation of osintui using cargo i receive the follow error:
( For reference i am using linux os)
installation code entered:
cargo install osintui
Error received:
warning: build failed, waiting for other jobs to finish...
error: failed to compile osintui v0.1.1, intermediate artifacts can be found at /tmp/cargo-installKX3U8e


Make test_suites.sh run multiple iterations of the tests.

The default is to run 20 times (which takes ~3 seconds on a Mac
laptop), but it's configurable via the first command-line arg.
The changes to the actual loop body over test_array are:

Removing all the sleeps.

Problem
Intermittent failures are only caught by some test runs.
Change overview
Have each test run run the tests 20 of times, making it more likely to catch intermittent problems.
Testing
Ran the script locally to make sure that the new setup does not fail.  Verified via the log that the tests did indeed get run 20 times.

@andy31415 @saurabhst @jelderton @msandstedt @Damian-Nordic @LuDuda ?


cypress tests for Repositories

https://issues.redhat.com/browse/AAH-2245

replaced by https://github.com/ansible/ansible-hub-ui/pull/3714


Make fetch() zone-aware without triggering extra requests or uncatchable errors.

Previous implementation called fetch() during setup in order to obtain a result promise from it so its constructor could be patched to make it zone-aware.
This had two problems:

Calling fetch() would trigger an unwanted (and unnecessary) HTTP-request.
Chrome threw an uncatchable error, which means with open dev tools will halt execution and enter the debugger (which is hugely annoying, as it happens on every page load).

This change replaces fetch() with a wrapper function that lazily ensures the result returned by fetch() is zone-aware.

CLA signed.

#446

@MichaelBuerge , please read DEVELOPER.md, before commit part, so you can check your commit. Currently it seems you build failed with tslint part.

@JiaLiPassion Apologies for missing the linter. Everything should be fine now (npm run ci goes through).

@MichaelBuerge , you are welcome, could you check my review comment? especially whether the first promise is patched or not one.

@JiaLiPassion I can't find your review comment. As of now, the pull request page still says "no reviews". (Am I looking in the wrong place?)
However, guessing from your comment here, your question seems to be whether the first time the patched fetch() function is called its result promise is properly patched.
That is indeed the case, as the constructor's prototype is modified before any caller can get a hold of the returned promise. Also, the fetch tests (in test/common/Promise.spec.ts) would not pass with an unpatched result promise.
Does this address your concern?

@MichaelBuerge, sorry I forget to push submit review button...

That is indeed the case, as the constructor's prototype is modified before any caller can get a hold of the returned promise. Also, the fetch tests (in test/common/Promise.spec.ts) would not pass with an unpatched result promise.
Does this address your concern?

yeah, you are right! thank you for explaining this, I didn't realize that.

My pleasure!
I assume there's a process in place, but if there's anything left do so this gets merged eventually and the associated issue (https://github.com/angular/zone.js/issues/446) closed please let me know.

Also addresses #476


Fix UX issues.

Related issues are #1917, #1754.

Coverage remained the same at 54.995% when pulling 503a33293737456d378cc6c3e9c4f4b84de1d54b on wknet123:master-new into b7a196f7aa6400c9bf5a6484c1b0ce06726c330b on vmware:master.

Coverage increased (+0.05%) to 55.042% when pulling 7510a136da0589512fb17eae91e65b1c28de713a on wknet123:master-new into 85b8b496be542e3dae3b2fca3d6057040f5def59 on vmware:master.

Coverage remained the same at 54.995% when pulling 782caa69bb17908f0f5177df40a909499a114a4b on wknet123:master-new into 85b8b496be542e3dae3b2fca3d6057040f5def59 on vmware:master.


Latex: a line break should be added at the end of an adjacent ANSI cell

Hi,
Thank you for this useful project. But when I built latex from a notebook, I found that adjacent ANSI cell wouldn't start a new line, so it would make something like this:
\begin{OriginalVerbatim}[commandchars=\\\{\}]
 some code
\end{OriginalVerbatim}\begin{itemize}
 some other code
\end{itemize}

In this example, the itemize  cell won't be compiled correctly.

Fixed in #107.


label:bug BC Gcode Not Generating in bed_tint Bug

In nozzle_tint, the AB axis appears normal, but in bed_tint, the BC alphabet and value are not output at all.

BC add


Documentation page doesn't seem to work

Documentation page doesn't seem to work.
https://www.typescriptlang.org/docs/home.html throws The resource you are looking for has been removed, had its name changed, or is temporarily unavailable..

Thanks, looks like a bad deploy - fixed!


Create releases

Now users can download nydus-snapshotter from image-service, but nydus-snapshotter repo has not any release yet.
Related to https://github.com/kata-containers/tests/issues/4446

Nydus-snapshotter now has function of  automatic releasing when a tag pushed. I guess it should meet current requirement.

I just release v0.1.0 as the initial released version. Hope it will be helpful to you.

Thank you.


Add CMakeLists.txt

Hi,
Thanks for leaving your project open. I need an allocator for a research project in C++, I would be interested in contributing, let me know if you are ok. I'm using Visual Studio 2019 / clang / gcc.

Hey @AlexisMotet. I am open to contributions, but what kind of change did you have in mind? I'll look at this PR a bit later when I'm free

I'd like to code it in C++ and make some changes to make it more efficient for small allocations, for example. I don't know if that's possible. But I think I'll code it in C++ on my own to understand the algorithm properly because I'm a bit lost.

Getting this code to work with a C++ compiler would be nice! Introducing C++ specific features may be too much though. If you decide to write your own allocator let me know if the comments help or if there are any mistakes.
If you're still interested in contributing here are a few notes:
The cmake version is a bit high. You require 2.23 but the package manager on my WSL install only goes up to 2.22. I did change the version in CMakeLists.txt and it appeared to work fine, so maybe you can lower it?
The comment is slightly wrong here. Since MIN_BLOCK_LOG2 must be greater than 3, the minimum size is 16 and not 8
_Static_assert(BUDDY_ALLOC_MIN_BLOCK_LOG2 > 3, "the min block must be at least 8 bytes long");

Yes, I can lower the CMake version, but this pull request was just to create a chat you can ignore it.
I've pushed a “buddy.hpp” https://github.com/AlexisMotet/buddy/tree/main to show you the interface I'd need in C++, let me know what you think.

I realize the buddy_startup interface could be simplified quite a bit. Basically, for each block of size BUDDY_MAX_BLOCK_SIZE of the memory pool, you need to provide a struct page_info. Here is an example:
int main()
{
    #define N 10

    char mem[BUDDY_MAX_BLOCK_SIZE * N];

    struct page_info pinfo[N];
    struct buddy_alloc alloc = buddy_startup(mem, sizeof(mem), pinfo, N);

    // ...

    buddy_cleanup(&alloc);
    return 0;
}

I realize now that the better API would handle everything internally using the memory provided by the user

For the pages:  I understand, but for me they were non-contiguous pages in memory, and in your API they are part of the same buffer, so yes I think it would be enough to take a single pointer as an argument and a size.
For the exception: Ok then it can just return nullptr.
Also, in C++ 20 there are several functions that could be used for dealing with bits:
https://en.cppreference.com/w/cpp/header/bits

Each page has its own tree (and by page I actually mean an aligned block of size BUDDY_MAX_BLOCK_SIZE). If you only provide it one bit tree, the allocator will only consider the first aligned page of the pool. I think I will change the API.
It's important to me that the actual buddy.c and buddy.h can be compiled with a C compiler. I don't mind adding a new header file for C++ or doing compatibility fixes (eg avoid implicit void conversions), but adding C++ features to the main code I would avoid.
You could always make the code C++20 in your own fork. I'd be curious to see how it turns out.

I simplified the API quite a bit. You may want to rebase now

ok :)

I've added this file to compare performance.
https://github.com/AlexisMotet/BuddyAllocator/blob/main/perf.cpp
I think your code has a problem for now because it's below C++, but it can't be anything serious. But I think that in the end, C++ should be barely slower than C. And the buddy allocator C++ is just below malloc, as it doesn't have to deal with concurrency I guess ?

(Release + O2 flags, Windows, Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz, 32Go)
I've tried to compare with another implementation https://github.com/red-rocket-computing/buddy-alloc.
... But I've got bugs for now. I was trying on Windows but I'll test with gcc tonight (I don't have WSL). They embed the allocator so it seems more prone to bugs.
For the next I'll take a look at this paper I think, to see if it can be improved:
Fast Allocation and Deallocation with an Improved Buddy System
https://cs.au.dk/~gerth/papers/actainformatica05.pdf

Hey, thanks for the feedback! I'll try timing the code to see what's going on.
The paper looks interesting. If you're going to work on this feel free to ping me in pvt. I'm always interested in talking about this kind of stuff


Classic UI  multifield does not save values on reloading/editing in dialog but is stored in CRX as JSON

Classic UI multifield does not save values on reloading/editing in dialog but is stored in CRX as JSON.
We are in AEM 6.2 and ACS Commons version is 3.3, Please help us with the fix. This was working fine when we have this in AEM 6.0

@Sandeep18051990 any chance you could package up the component that is having this problem?

@davidjgonzalez  thanks for the reply.
Attached is the dialog where we have issues
dialog.zip

@davidjgonzalez  Below is the issue in brief
|- MultiField (ootb multifield )
|-fieldConfig - xtype : multifieldpanel
|- field A (xtype:textfield example textfield)
|- field B (xtype:pathfield example pathfield)
|- field C (xtype:tags example tags field)
Where tag field is not a mandatory field but when a tagfield doesn't contain any values/no values selected all the pre entered values below that multifield set are getting disappeared from the dialog.
On Save it's saving in CRX after reloading Dialog for edit field A2,field B2 and field C2 are disappearing from dialog.
Thanks for any suggestions to overcome this issue.

@Sandeep18051990 i tried your dialog on AEM 6.2 and AEM 6.3 instances w ACS Commons 3.9.0 and it works fine.. see attached. Have you tried checking your dialog on a a vanilla instance without your code installed to make sure you dont have something that is causing issues (tbh, doesnt sound likely but it works fine for me on a vanilla...)
1018-aem62-acscommone3.9.0.mp4.zip
1018-aem63-acscommons3.9.0.mp4.zip

@davidjgonzalez  This seems strange but It's not working for me on AEM 6.2 vanilla instance with ACS Commons 3.9.0
Below is the url and attached is the packaged I used to verify in vanilla instance.
🔢 https://youtu.be/MagRFeeVj_A

header-1.0.zip

header-1.0.zip

I'm using windows 10 and Chrome browser to test this

It will be great help if you provide the package of component you created and the test page from AEM 6.2,I'll cross verify on my end.
Thanks for the help

here's the simple component i made to test: acs-commons-issue-1018-1.0.0.zip

@Sandeep18051990 hopefully this isnt a Windows thing since i cant help you with that. Can you:

verify there are no JS errors when you POST the data back (save the dialog)
verify in the network request headers on the POST that all the data is present (A2, B2, C2)
verify that all the data is present in the JCR post the post (check the JSON obj persisted to the node)
when opening the dialog, verify that the HTTP GET for the data is sending all the data (A2, B2, C2)

You might have to roll up your sleeves and debug this one yourself in Windows though :(

I tried various options .. even tried listener options loadContent
function(){
var valu=this.findParentByType('dialog').getField('./navitems').getValue();
alert("find it"+valu);
}
It's giving a stripped value even though JCR node has a correct json values this is happening only when tag field is empty.
:(

@davidjgonzalez

Is there anyway I can set default value to tags pro-grammatically or by some property settings

@Sandeep18051990 so the issue if confirmed as the dialog can't repopulate the fields on reload (the correct data is persisted and read from jcr). Right?

Yes you are correct

https://github.com/davidjgonzalez

@davidjgonzalez If the tag field is selected than dialog is repopulated with correct field,It will fail to populate the values one below where tag field is empty/not selected

@davidjgonzalez Data in JCR {"linktitle":"one","linkurl":"","privatelinkurl":"","eserviceRole":["forum:topic","forum:topic/answered"]},
{"linktitle":"three","linkurl":"","privatelinkurl":"","eserviceRole":[]},
{"linktitle":"twi","linkurl":"","privatelinkurl":"","eserviceRole":["forum:topic","forum:topic/answered"]};
listener
function(){
var valu=this.findParentByType('dialog').getField('./navitems').getValue();
alert("find it"+valu);
}
alert in above listener is giving only 2 values
{"linktitle":"one","linkurl":"","privatelinkurl":"","eserviceRole":["forum:topic","forum:topic/answered"]},
{"linktitle":"three","linkurl":"","privatelinkurl":"","eserviceRole":[]};

@davidjgonzalez So to conclude correct data is persisted but while reading it has an issue .. it's excluding values below where tag is not selected

@Sandeep18051990 if you look at the HTTP request that GETS the JSON from the JCR; do you see the 3 items coming back OR are you seeing only those last 2?
If the HTTP requests the sends the content back only contains the 2, then there is a problem w the serialization of the data (server-side), if the HTTP request HAS the 3 entries, then its something in the JS.

@davidjgonzalez I have observed HTTP requests and the request contain only 2 items. Do you have any leads which component in acs-commons I need to verify in order to fix this.
Thanks for your help here

I had the same issue, I created a component called "blog" and apparently other component called called "blog" was called in the load process. To solve the issue I just change the name of my component /apps/myproject/components/blog -> /apps/myproject/components/other-blog
and everything worked fine.


The pull-down bar can't be dragged sometimes

Repro Steps:
•   Navigate to https://makecode.microbit.org/beta
•   Zoom out the window then drag the pull-down bar on content pane
Expect Result:
The pull-down bar should be dragged smoothly
Actual Result:
The pull-down bar can't be dragged sometimes

Can't repro. What OS / Browser is this on?

It repros on every browser and it needs to zoom out the browser firstly.

Closed as not repro


After upgrade from 10.3.1 to 10.4 the non-data based geocode services do not start

After upgrading the production server from 10.3.1 to 10.4, the MGRS and Longitude/Latitude geocode services fail to start with the following error:
Service failed to start
"ServiceName".GeocodeServer:
"ServerName"
the input is not a geographic or projected coordinate system

I extracted the MGRS.loc and latitude/longitude .loc files from the .sd files we released with the Fall 2015 Ops Server and when I attempt to publishing these from ArcMap 10.4 I receive the error 00096 "Locator is invalid". The MGRS.loc that is installed with ArcMap 10.4 does publish to our development 10.4 ArcGIS Server.

The issue is that the .loc.xml file has an extra "" character at the beginning of the GEOGCS definition. At 10.4 the geometry object parser is more stringent and does not accept this as a valid definition. Removing this extra character allows the service to be started.

I've created new .sd files contained edited versions of the .loc.xml files for both MGRS and LongitudeLatitude geocode services and have placed these in the arcgisserver\directories\arcgissystem\arcgisuploads\admin folder on the production server so when the .sd files are extracted the corrected .sd files for these services will be extracted as well.


Collection count is float instead of integer

Is this an API change? or an error?
the 5.0 beta
User.count => 128.0

the 4.0
User.count => 128

Moped explicitly cast the results of count to an integer, where the core driver just gives back the result. Which version of MongoDB are you running on?

Thanks :) I use MongoDB 2.6, Rails 4.1.2


Question: animated icons????????????????

Hello i need to know how to make animated icons on andromeda engine??

you add them through the source code


Handlers should not be required

get.js and request.js should not be requires in /app folder

No bug found, all tests shows that handlers is not requires now


feat(test): Added e2e test simulating a consumer of JSON RPC

:tada: This PR is included in version 1.7.0 :tada:
Your semantic-release bot :package::rocket:


Maven deployment

Hi @imagejan,
Could you please help me by having a look why this artifact was not deployed to our maven repository. I feel I am missing some step but I don't know which one...

I guess the enforcer would have told you if you didn't always disable it 😉
As far as I can quickly grasp, your pom.xml is lacking several required fields, in particular <ciManagement>.
Did you run github-actionify.sh on this repository yet? From https://github.com/embl-cba/metaimage-io/commit/c179b58d445f6f8f05db64eb08e0ee725d7b144b it seems you tried to add/copy these files manually?
Some recommendations:

Never have <enforcer.skip>true</enforcer.skip> in your pom.xml. Better fix the issues that make the enforcer fail.
Never have <scijava.app.directory>[...]</scijava.app.directory> in your pom.xml. Define the directory in your local .m2/settings.xml so that maven picks them up, but they have nothing to do in your public source code.
Use the tooling provided by SciJava (i.e. github-actionify.sh and release-version.sh) instead of copying boilerplate from existing repos.

Thanks a lot @imagejan ❤
Thanks to your suggestions it works now!


Username Validation

During the registration of a new user, a prompt for a username is given (for the user to be referred by in the application).
This prompt currently accepts any input, but should instead limit the user with the following constraints:

[x] character length in the range of 3 to 18 characters
[x] allowing only alphanumeric characters
[x] allowing only unique usernames*

*unique usernames may not be necessary

[x] This prompt should also inform the user of the constraints if the first input is not valid.

User profile name validation now implemented, with adjusted constraints:

length in range of 4 to 32 characters
letters, numbers, dashes, and underscores allowed


error while testing u2net_test.py

Hello,
I tried to launch u2net_test.py with the unetp model. It shows no pratical error but still doesn't iterate trough test_salobj_dataloader(line 96).
It shows some warning:
[W ParallelNative.cpp:212] Warning: Cannot set number of intraop threads after parallel work has started or after set_num_threads call when using native parallel backend (function set_num_threads)
[W ParallelNative.cpp:212] Warning: Cannot set number of intraop threads after parallel work has started or after set_num_threads call when using native parallel backend (function set_num_threads)
/Users/user/opt/miniconda3/envs/unet/lib/python3.6/site-packages/skimage/transform/_warps.py:110: UserWarning: Anti-aliasing will be enabled by default in skimage 0.15 to avoid aliasing artifacts when down-sampling images.
  warn("Anti-aliasing will be enabled by default in skimage 0.15 to "

But the CPU doesn't compute at all.
Tried the code on Mac OS 10.15 with miniconda 4.10 and torch 1.9.0
Thanks in advance

line no 78 on u2net_test.py try changing num_workers to 0.

Thanks @tiwari93 it resolved the issue !


skytemple: 1.3.10 -> 1.3.11.post1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for skytemple is: "ROM hacking tool for Pokémon Mystery Dungeon Explorers of Sky"
meta.homepage for skytemple is: "https://github.com/SkyTemple/skytemple"
meta.changelog for skytemple is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.11.post1 with grep in /nix/store/98iv7dkgazsay7ygx2yq8jb5q6jyjzqw-skytemple-1.3.11.post1
found 1.3.11.post1 in filename of file in /nix/store/98iv7dkgazsay7ygx2yq8jb5q6jyjzqw-skytemple-1.3.11.post1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
skytemple

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/98iv7dkgazsay7ygx2yq8jb5q6jyjzqw-skytemple-1.3.11.post1 \
  --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 skytemple https://github.com/r-ryantm/nixpkgs/archive/1b111060e3e519c25d26c68892d5f865088f942a.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/98iv7dkgazsay7ygx2yq8jb5q6jyjzqw-skytemple-1.3.11.post1
ls -la /nix/store/98iv7dkgazsay7ygx2yq8jb5q6jyjzqw-skytemple-1.3.11.post1/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:

skytemple

Maintainer pings
cc @xfix @marius851000 for testing.

Tested some of the complex function (applying patches, displaying graph, running the ROM). They work.

Shall we also switch to gtksourceview4 in this update?

@bobby285271

Shall we also switch to gtksourceview4 in this update?

It is possible, but would require a new PR (I think?). This is an automatically generated one. But the few stuff I tested which use gtksourceview worked well.

Actually, I’ll make a new PR

(a, yes 1.4.0 was published too)

@xfix do you want me to add you as a maintainers for the newly added package? (also, I’ve seen you are not on the Discord server. If you want, there is bridged Matrix space at #skytemple:skytemple.org )

Superseded by #200020.


help about character corruption

HI, thanks for this great gem.
We are using Japanese in the chatwork,
the log generated was character corruption. (the content and files both)
How can I fix it by my own? or any function may be apply to solve this problem?
Thanks you.

@adofe-ask
Please give us source characters and result characters(corrupted logs).
If you have other informations help this issue, they also please.
And which plan do you use?

ChatWork
KDDI Chatwork(for enterprises)

We are using ChatWork.
Becasue of company secret I can't give you the source.
Just pick one of the corrupted photo file here

Thanks a lot

@adofe-ask
Sorry, I can't Investigate logical destruction images.
Could you try the following flow?

Create new group chatroom with only you(You can create from '+' button is upper part of the left of the menu).
Post some messages with no secret informations to group chatroom that you created in japanese.
Export  logs from group chatroom that you created with goodbye_chatwork gem.

@adofe-ask
# Check room_id of group chat that you created
$ goodbye_chatwork -i<EMAIL_ADDRESS>-p your_password
# Export logs
$ goodbye_chatwork -i<EMAIL_ADDRESS>-p your_password -e room_id

@adofe-ask Have you solved your question?

not solve yet ...
these days are busy.... will export logs on monday
thanks a lot

@adofe-ask Do you still have this problem?

@adofe-ask Hi.
În japan, some people have same issue on windows PC.
Is your PC windows?

I fixed the option when saving the download file, so please try out the new version.
I have not prepared the environment in which the problem occurs, so I can not confirm if this problem has been fixed


manifest.json: add gecko id

This is a requirement for Firefox add-ons using manifest v3.  The ID can take the form of an email-like identifier or a UUID.  A quick survey of my installed add-ons shows that most developers seem to use the UUID, so I just generated one locally.
Updates #4

This results in "Errors" in Chrome (but it's actually just a warning, if you click in to look):

Unrecognized manifest key 'browser_specific_settings'.

Do we expect to need other changes to manifest.json for Firefox? Would it make sense to create a separate manifest file per browser? Or if we'll be adding a build script to handle packaging it into an installable extension, maybe we could patch the manifest in that build script?


feat: Added linter rule to check format of properties name in the properties file.

Added linter rule - PROPERTIES_NAMING to check that properties name in the properties files (.properties and YAML) follow  predefined acceptable format such as java property naming conventions (db.username).

@dileepkumarv-avio @adesjardin Should we do it as "PROPERTY_NAME_PATTERN" rule that defaults the regex pattern but also allow to change it if needed?

@manikmagar Renaming this rule to PROPERTY_NAME_PATTERN makes sense to me. I will rename the rule to PROPERTY_NAME_PATTERN.
Also, i will add optional attribute within the rule to allow different pattern for property name.


feat: Add a Promise#rescue convenience for specifying on_reject.

@eapache for review
Javascript has a convenience function Promise.prototype.catch which is the same as Promise.prototype.then(undefined, onRejected) and would also be useful in ruby.
I defined a Promise#rescue method, since ruby uses a rescue keyword rather than a catch keyword for catching exceptions.  However, I have also included an Promise#catch alias for consistency with the ECMAScript standard interface.

:shipit:


Hi

I am interested in closer conversation.
which language is Indy-Form ? its not python ....

Its is elixir - https://elixir-lang.org .


About the HumanAct12 dataset in Humanml3d

Hi！I want to know what is the difference between the HumanAct12 dataset in Humanml3d and the original HumanAct12? What did you do? What does the number like P11G02R04F0752T0819A1001 in humanact.zip mean? Thank You！

They are the same. For the meaning of humanact12, please refer to https://drive.google.com/drive/u/1/folders/1hGNkxI9jPbdFueUHfj8H8zC2f7DTb8NG


Feedback for “Run a Collection”

In the documentation it says "unlimited" runs, but it's actually limited to 100 runs.
Why is limit set to 100 runs and is there a way to bypass it?
I've also tried the Bruno CLI, but can't see the parameter which indicates the number of runs.

Hey @mtosic,
Thanks for creating this issue. I need some time to discuss it with the team and will get back to you once I have more context on it.

@mtosic
There is no limit at all on Collection runs (In GUI or CLI)
Can you share a screenshot where you are seeing the runs being limited?

@mtosic
You can run collections manually as many times as you like.
However, if you're referring to iteration runs—where you can specify a number of loops and execute the collection N times—that feature is part of our paid offering and requires a license to access.

Hi @helloanoop, I have a license - I've entered 1000 in number of iterations and got popup screen that max number is 100.

@mtosic Thanks for sharing this. We should be able to remove the restriction on the iteration count.
Just curious to know, what is the iteration count that you are looking forward to test with?

Hey @mtosic,
I’ve created the issue on the main Bruno repository. Would you mind taking a look and adding any additional context if needed?
We're addressing this issue on the main repo, and your input would be helpful.


Markdown linting tests intermittently fail and block commits

What happened?
I modified a Pulumi Learn page (found at themes/default/content/learn/pulumi-fundamentals/configure-and-provision/index.md) to fix a separate issue (https://github.com/pulumi/devrel-team/issues/485). When I staged the file and attempted to commit, the pre-commit linting tests (as executed by yarn run lint-staged) fail on other, unmodified files. The list and number of files that "fail" the tests vary every time I try to commit.
Steps to reproduce

Modify a file.
Stage the file and attempt to commit.
Intermittently, the pre-commit linting tests will fail on other, unmodified files. (This doesn't always happen, and I have not yet been able to reliably reproduce the issue.)

Expected Behavior
I expected the pre-commit tests to run only on modified/staged files, and if errors are detected (perhaps because the changes came from a fork without pre-commit testing) then I expected the list of files that are causing the error to be consistent and reproducible.
Actual Behavior
The pre-commit tests seem to run against and flag unmodified files, and the list of files that produce an error varies/changes on every run (even when the tests are run manually using yarn run lint-staged).
Output of pulumi about
N/A
Additional context
Running make ensure to ensure that the latest versions are installed doesn't seem to make any difference. Modifying scripts/lint/lint-markdown.js and removing the testing for relref instances seems to fix the error.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

i believe it was intentional that it lints everything, so i removed the bug. but that doesn't mean we cant change it.

@susanev OK, sounds good. I still think this issue needs to stay open though, given the intermittent/unpredictable nature of the tests sometimes passing and sometimes failing.

of course, i think we should do this! i only don't want it tracked with the bugs, since it was implemented as designed.

I'm re-adding the kind/bug label because the linting tests fail intermittently and unexpectedly. Today, for example, manually running scripts/lint.sh (which in turn invokes /scripts/lint/lint-markdown.js) returned 3 errors, 6 errors, 8 errors, 18 errors, and no errors. Because these scripts intermittently fail and because they are set as pre-commit hooks, this is blocking commits.

can you share the output your getting? and the branch you are running them on?

Here's the output (note that the output varies in the number of files and which files it flags, but the "error" returned is constant):
Markdown Lint Results:
    - 929 files parsed.
    - 6 errors found.

Errors:

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/what-is/what-is-infrastructure-as-software.md:
Line File Header: Maximum call stack size exceeded.

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/what-is/what-is-yaml.md:
Line File Header: Maximum call stack size exceeded.

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/whitepapers/delivering-cloud-native-infrastructure-as-code.md:
Line File Header: Maximum call stack size exceeded.

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/whitepapers/enterprise-innovation-through-cloud-engineering.md:
Line File Header: Maximum call stack size exceeded.

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/whitepapers/point-of-view.md:
Line File Header: Maximum call stack size exceeded.

/Users/slowe/Work/Code/Repos/pulumi-hugo/themes/default/content/why-pulumi/_index.md:
Line File Header: Maximum call stack size exceeded.

I can reproduce this on two different systems (both macOS 13.1, both ARM-based Macs) on different branches of the "pulumi-hugo" repository (I've tested both the "master" branch as well as a feature branch with a change to one file). Both systems are running NodeJS 16.17; I suppose I can try a different version of Node.

If switching to Node 18 is "the" fix, then we should update make ensure to check for the correct version of Node so that others don't run into this issue.

are you running this on master? or a another branch?

This occurs both on master and on a feature branch.

okay im not getting this error on master, i can try on ur banch as well if you can share the name. ive also never seen these errors before in all my work in this repo. my node version is v18.7.0. let me ask a few more folks if they have ever seen them.

i think folks are resolved, so closing.


Random android crash when garbage collector clean object that was still internally used

Describe the bug
Backstory: we are using Unity (v2019.4.16f1) to develop Android VR app for Pico Neo3 devices.
We are using sample code from here as our starting point, we are really satisfied with recognition so far but app started randomly crashing in different intervals (really hard to reproduce, its totally random)
Error that we are getting in logcat is Error AndroidRuntime signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x79bc9b56a0 (always different address) (Unity console doesn't show any log on crashing, its totally disconnected by that point)
After a lot of researching, last try before giving up was trying to do test with disabled garbage collector and this was first time app didn't crash - worked as expected (besides memory filling but this is less important as culprit is found and this won't be used in final product).
Conclusion: Seems like gc is collecting object that is used internally by sdk which was still in use but flagged for cleaning (I read somewhere --- The problem is due to the program holding on to the raw handle (example IntPtr) without keeping a reference to the managed object holding on to the resource. Without keeping that reference, the object becomes eligible for finalization/collection), which also explain error above (fault addr).
Interestingly, in editor we never had any crash, but once app is built (using il2cpp), it does.
We are using latest version of sdk --- Microsoft.CognitiveServices.Speech.1.21.0.unitypackage

@PeraDllGD Thanks for the report, could you please provide information which sample you were using as base? Also are you able to see the problem with sample project? Any possibilities to share code which reproduces the issue?

@PeraDllGD Could you also provide Android Tombstone native crash file which we could analyze further by symbolicating it? You can for example use, https://github.com/hexhacking/xCrash to get the xcrash file.

After few more testings, I think its happening with longer sentences quite more often (example "hello, how are you today" and that calling gc.collect after its detected, has 20-30% chance to crash app)

Actually I did, I uploaded sample on google drive (and shared with you) - I didn't delete library folder, so you don't need to rebuilt it  Unity version 2019.4.16f1 (same as original project)
Tested on Huawei P20 Pro
3 modified things from sample (and from my testing)

I removed api key and region (which for me is endpoint) before sending
changed SpeechTranslationConfig.FromSubscription to SpeechTranslationConfig.FromEndpoint for CreateSpeechRecognizer method
when StopRecognition is called, I'm starting coroutine which will call GC.Collect() every frame (10 times)

To reproduce:

Start recognition
Say longer sentence, for example "hello, how are you today"
Stop recogntion
Start again
Say again, for example "hello, how are you today" but stop it at random point (it doesn't need to be fully processed)
Than start again
Say again, for example "hello, how are you today" but stop after you get result
(it should fail at this point, as its random, you might need to try multiple times to get it, but you will get it eventually)

Also before I noticed another problem if you stop/start in same frame, it would throw exception "ObjectDisposedException: Cannot access a disposed object." but I solve that in main project by adding queue of recognizer

@PeraDllGD Can you share the main code file here so others can look at it?

(I had to convert it to .txt extension to be able to send it here - convert it back to .cs before use)
SpeechRecognition.txt
So literally to create sample project, you will need to

download sample for Unity
change SpeechRecognition script with this one
provide credentials inside inspector (SpeechServiceRegion, because of code change I mentioned above, is actually EndPoint, not region (I didn't change name) - thats how I have my credentials so had to make that change)

Thats it, now press Continuous/Stop recognition with aforementioned reproduction steps

Hi, is there any update on this issue?

I was about to write really big review about all testings I did (prepared screenshots, screen recording, etc..) but at the end, I think I found what was issue (hint: Unity, its always Unity 🤣 )
Briefly
I tested P20 Pro again, took recording, etc.. than tried on S10e, same crash (it crashed literally each time I tried it, totally random from 1 to 10 stop recognition)
I also updated to latest version (1.22) still was getting same problem

Enable Translation was turned off

As for SpeechConfig -> SpeechTranslationConfig, yes, that was mistake on my part, as I initial changed it to wrong place, so I just copied it (but this is not problem)
Solution - I tried with updating Unity version to 2021.1.28f1, and I wasn't able to reproduce this issue anymore 🤦 I will need to test it bit more but so far so good
Then I went through all release notes starting from 2019.4.16f1 to 2021.1.28f1 (search for "garbage") (of course not all are important but still want to put this in here, maybe it will help somebody else - as far as I can tell, only 1 might be valid)

https://unity3d.com/unity/whats-new/2019.4.24

Build Pipeline: Fixed excessive garbage collection occurring during the build process.

https://unity3d.com/unity/whats-new/2020.1.0

Build Pipeline: Reduce amount of garbage collection performed inside the ContentBuildInterface.

https://unity3d.com/unity/whats-new/2020.1.14

Scripting: Fixed issue where thread statics that reused thread static slots would not adhere to type alignment. This would cause the garbage collector to incorrectly clean up thread static data because it would only scan pointer aligned memory for references. This would lead to memory becoming corrupted and inducing random crashes. --- this might be fix, but its saying also https://issuetracker.unity3d.com/issues/crash-on-mono-class-fill-runtime-generic-context-when-entering-play-mode-repeatedly that its fixed for 2019.4.15f1 🤷

https://unity3d.com/unity/whats-new/2020.2.0

Scripting: Added a way to get the stack trace without garbage collection in the Editor.
Scripting: Added: Added GarbageCollector.Mode.Manual, which disables automatic GC but still allows manual control by calling GC.Collect() or GarbageCollector.CollectIncremen
Asset Pipeline: Fixed an issue where Artifacts for deleted asset didn't get deleted in artifact garbage collection.
Build Pipeline: Reduced amount of garbage collection performed inside the ContentBuildInterface.

https://unity3d.com/unity/whats-new/2020.2.2

WebGL: Fixed a bug where calling unityInstance.Quit() from JavaScript would not let JS VM garbage collect away the Unity game instance.

https://unity3d.com/unity/whats-new/2020.3.6

Build Pipeline: Fixed an excessive garbage collection issue that occurred during the build process.

https://unity3d.com/unity/whats-new/2020.3.9

Profiling: GarbageCollectAssets is triggered frequently when higher frame counts are set ---- up to v19 this msg is spammed
WebGL: Fixed an issue where the Garbage Collector could corrupt memory on WebGL.

https://unity3d.com/unity/whats-new/2020.3.14

2D: Fixed SpriteResolver generates garbage every few frames when playing an animation

https://unity3d.com/unity/whats-new/2020.3.28

Particles: Added: Added a version of GetTrails that doesn't allocate any garbage.

https://unity3d.com/unity/whats-new/2020.3.31

Graphics: Fixed Brief garbage frame after changing resolution on Metal by ensuring that the recreated surface on size change doesn't dispose of its previously rendered contents

https://unity3d.com/unity/whats-new/2021.1.0

Package: Removed unnecessary allocations and garbage collections during runtime.

https://unity3d.com/unity/whats-new/2021.1.2

Build Pipeline: Fixed excessive garbage collection occurring during the build process.

https://unity3d.com/unity/whats-new/2021.1.7

Universal: Fixed an issue where ShadowCaster2D was generating garbage when running in the editor.

https://unity3d.com/unity/whats-new/2021.1.9

Profiling: GarbageCollectAssets is triggered frequently when higher frame counts are set

https://unity3d.com/unity/whats-new/2021.1.13

Core: Fixed an issue that caused incremental garbage collection to sometimes fail to use all of the available spare time before vsync.

https://unity3d.com/unity/whats-new/2021.1.14

Profiler: Fixed and issue where the contribution to asset garbage collection frequency from Profiler in the Editor wasn't removed.

@PeraDllGD Thanks a lot for the extensive testing and analysis. Initial crash stack also originates from Unity side, which matches to your analysis. I will close the issue.


Initial X Window configuration cleanup

This PR lays some groundwork for #216 by adding more flexibility for telling X how it should treat windows.
To implement that, it separates options more cleanly between the wayland and X backend, removes focusable as an option on X and replaces it with the wm-ignore flag, which now specifically just set's override redirect.
Additionally, it adds some other new options:

sticky
resizable
as well as adding the "utility" window type.

This PR is a breaking change in some configurations, as it will change how window positioning behaves depending on how the configuration looks currently.
Some smart defaults are implemented to avoid issues in most cases: wm-ignore will default to true (making eww behave similarly to how it did before), except if either reserve or windowtype are set. window-type defaults to dock if reserve is set.
migration
setups that previously relied on focusable="true" can now be implemented using wm-ignore="false". If the setup is a bar or similar, windowtype="dock" should be set, to properly apply reserve without making eww appear in application selectors or other places.

Pog!

This is integrated into master since the config rework, and can thus be closed


Feature: add missing methods to Oni.buffer including set scratch buffer

Update Buffer methods add new setScratchBuffer method

Sorry this fell through the cracks, @Akin909 ! Bringing it in now 👍


ROCm: Support more hipBLAS/rocBLAS and rocSOLVER functions

Most BLAS calls no longer raise HIPBLAS_STATUS_NOT_SUPPORTED (unless HIP does not support it)
Reduced the number of failures in tests/cupy_tests/linalg_tests/ by about 10 (ex: TestDet, TestSlogdet, etc are now error-free)

I think it'd take some efforts to make most tests pass, as we don't yet support rocsolver, but I consider this a good progress and should not be blocked.
TODO: run a few more tests, perhaps manually, to see if rocBLAS is well-behaving or not.

/test

btw, AMD folks recommended us to use MAGMA for lapack support

I was looking at the rocsolver APIs and found some of them have quite similar signatures with cusolver. Will try to look into that and see how far we can reach. If possible I'd rather not add magma as a dependency. In any case, that would be a separate PR from this one.

Jenkins, test this please

Jenkins CI test (for commit e6a09acfcdac41c78ce386af9cb53a42eb37411d, target branch master) succeeded!

Blocked by #3936.

@emcastillo I have updated the PR description. I think a lot of these work now! My question is: Do we want to skip the tests in which we know ROCm is not working yet (for example due to lack of complex number support), or you think it's fine to leave as is?

Jenkins, test this please

Jenkins CI test (for commit ebda4ee4b3c4ba986bc9537876a84ad757527ff2, target branch master) succeeded!


Documentation request: Where did you install the files?

Today I installed vcpkg. I followed the getting started instructions and then installed a single package (libusb). It installed many dependencies, then libusb. Great.
…where are the files?
I understand there is a cmake workflow for hooking up to vcpkg. But I wanted to know where the so-installed files were, for two reasons; one, I might want to delete them later, because some of the dependency packages installed (Python, CMake, Meson) sounded kind of large; two, I am not using cmake, I am using Rust "cargo", and Rust "cargo" depends on a environment variable named VCPKG_ROOT (this is its own problem, see here).
It turns out that the files are installed into the git checkout directory created in the getting started instructions. This git checkout directory also turns out to be the VCPKG_ROOT Rust wants (as identified by a file .vcpkg_root at the top level). I had to figure this out myself through detective work. It isn't described in the Windows quick start guide in the README, or the "Installing and Using Packages" guide the README recommends you read next. The quick start guide even makes reference to "[path to vcpkg]", but does not indicate what the path to vcpkg is (the git checkout). Writing this now I do find the "Getting Started guide" linked on the separate website vcpkg.io has the sentence "The repo can be cloned anywhere, and will include the vcpkg binary after bootstrapping as well as any libraries that are installed from the command line" but I didn't see this at the time and I personally find this sentence slightly ambiguous.
I guess it was "obvious" to whoever wrote this documentation that the vcpkg-bootstrap and vcpkg install installs itself in-place into the directory vcpkg has been checked out into but it was not obvious to me :(
"Expected behavior"
I recommend explaining this (that the "install directory" is the same as the git checkout directory) more explicitly in the README and also taking note of the support thread linked above.
Surfacing a little higher in the documentation a link to the explanation of the layout of this magic directory (the significance of .vcpkg_root; which subdirectories are installed packages and which are vcpkg plumbing; whatever it is you do to "reset" the git repo to its uninstalled state, I guess git clean -xffd?) would probably be good but is probably not required.
Environment
Windows 10 , 10.0.19045 Build 19045
Rust/Cargo 1.69.0
vcpkg… 768619a, I guess?

Hm if you open the documentation (https://learn.microsoft.com/en-us/vcpkg/) there is Integrate with a custom buildsystem (https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/manual-integration).
Maybe the README.md should link to documentation after the "How to setup"

Hm if you open the documentation (https://learn.microsoft.com/en-us/vcpkg/) there is Integrate with a custom buildsystem (https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/manual-integration).
Maybe the README.md should link to documentation after the "How to setup"

Hi, thanks for linking me this— this document is great and answers my remaining questions. Two notes, one, the "magic" .vcpkg_root file is not documented here, two, this document makes reference to the vcpkg root without explaining what the vcpkg root is. Maybe the "vcpkg root" does not need to be defined in the "custom buildsystem" document if it is defined more clearly elsewhere though.

vcpkg.io should redirect to learn.microsoft.com/vcpkg IMHO. The latter should also have a section "How it works" or something.

without explaining what the vcpkg root is

meow root is a common programming term describing a folder where meow is located.
Now that you know what vcpkg root is, how would you document it?

I agree that "meow root" is clearly "the folder where meow is located", but it is not at all obvious to me that "the folder where meow is located" is the git checkout of its source. My first minutes with vcpkg involved an install step through a "bootstrap" script, followed by a step using the actual name "install" step. Often, pieces of software which are distributed as software and have "install" steps such as this install to some other location (such as ~/.something or %APPDATA%), after which the distribution/source repo can be deleted. Although the "in-place" nature of the vcpkg repo/distribution is now clear to me, it was not inherently obvious at first.

Now that you know what vcpkg root is, how would you document it?

The getting started guide in the README begins with

First, download and bootstrap vcpkg itself; it can be installed anywhere, but generally we recommend using vcpkg as a submodule so the consuming repo can stay self-contained. Alternatively, vcpkg can be installed globally; we recommend somewhere like C:\src\vcpkg or C:\dev\vcpkg, since otherwise you may run into path issues for some port build systems.

… followed by sample invocations of git and .\vcpkg\bootstrap-vcpkg.bat. I would reword this as:

First, download and bootstrap vcpkg itself:

Sample code

The directory from which bootstrap-vcpkg was run is now a functioning vcpkg installation, and all packages downloaded will be installed within it. This directory can be installed anywhere, but generally we recommend using vcpkg as a submodule so the consuming repo can stay self-contained. Alternatively, vcpkg can be installed globally; we recommend somewhere like C:\src\vcpkg or C:\dev\vcpkg, since otherwise you may run into path issues for some port build systems.

Alternately, if the "root" language is important vocabulary to vcpkg (and not just an affectation of Cargo) the added sentence could refer to "a functioning vcpkg root" instead of "a functioning vcpkg installation.
Additionally, I would add a sentence to the getting started guide clarifying under what circumstances it is allowed to move the vcpkg root (for example: do things break if you move the directory after bootstrapping? if so, say so after you describe how to bootstrap. do things break if you move the directory after running integrate? if so, say so after you describe how to integrate).

Often, pieces of software which are distributed as source and have "install" steps such as this install to some other location (such as ~/.something or %APPDATA%), after which the distribution/source repo can be deleted.

VCPKG defaults to binary caching using the file provider, which results in each installed package being archived into a zip file which is stored in %APPDATA% . A second attempt to install the same package set (with the same vcpkg revision on the same system) will simply extract those zip files, while build-time-only dependencies won't be installed (unless you explicitly ask for them).
If you do not "need" vcpkg after it has provided for whatever libraries you wanted it to provision, you can use vcpkg export to have vcpkg generate a bundle with your libraries and their runtime (but not compile-time) dependencies, and once you have that bundle, delete the vcpkg checkout.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Is there release for Velox ?

Is it safe to use Velox in production environment as there is no release provided yet ?

Velox does not have a release cycle yet as the API is not stable enough for any compatibility guarantees. Once the API is stable enough there will be official releases. If you want to use velox you should pin a certain commit hash for consistency until there are releases.
You have to decide yourself if you want to use velox in production: For some the unstable, changing nature of the current API would be an absolute no-go, for some the power velox provides is such an improvement that it's worth using, even without releases. :shrug:


PR: Implement dedicated IPython consoles

Fixes #4418.
This is part of issue #4524.

TODO

[x] Close all Matplotlib plots before a new run.

Let's merge this for now to keep things moving. I'll probably need to revisit this in 3.2.1, but it's working reasonably well for now.

Problems during migration (so far):

If there is no console currently open, running a script crashes the IPython kernel, it restarts it but doesn't try to re-run the script. I can't see why the kernel dies because it's restarted immediately (I can only see a flash that it failed). I'll try updating my IPython / Jupyter to try to fix this, but in the meantime it's difficult to debug.

Whenever a script would crash before, I could do import pdb; pdb.pm() to immediately go to the failing code. This now puts me into o stack frame within IPython/core/compilerop.py down to IPython/core/interactiveshell.py (two frames) so I can't get to any variables.

Should I open a new issue to track such migration problems?

@Eric89GXL, yes, please open a new issue for these problems. I don't understand too well you first problem though, so could you post an animated GIF to better describe it? You can do it with a very nice program called Licecap (if you're on Windows or Mac).

The pdb problem seems to have gone away (maybe with a restart of Spyder?), I'll open new issues as things come up. Thanks @ccordoba12

Great to know!


Highlight semicolon that doesn't terminate a sublist

false && ; foo does not execute foo because ; is equivalent to \n. Highlight it accordingly, differently to a ; that terminates a sublist.
See also workers/43726.

Cross-referencing #691.


Python functions: build did not realize main.py was missing

main.py:
def hello(request):
    return "Hello world!"

requirements.txt:
functions-framework==1.4.1

Upon building and running this function, I get:
  File "/layers/google.python.pip/pip/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/layers/google.python.pip/pip/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/layers/google.python.pip/pip/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/layers/google.python.pip/pip/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/layers/google.python.pip/pip/functions_framework/_cli.py", line 37, in _cli
    app = create_app(target, source, signature_type)
  File "/layers/google.python.pip/pip/functions_framework/__init__.py", line 130, in create_app
    raise MissingSourceException(
functions_framework.exceptions.MissingSourceException: File /workspace/main.py that is expected to define function doesn't exist

It would be nice to:

catch during build step main.py doesn't exist when GOOGLE_FUNCTION_TARGET specified.
document this requirement (I should be able to develop a func without buildpacks ideally without bouncing much between repos).

@ahmetb I'm a little confused here, do you have a typo? In this example it looks like you have a main.py, I wouldn't expect that exception to raise.
Did you mean when you have a source file other than main.py, and GOOGLE_FUNCTION_SOURCE isn't specified?

I meant to say func.py. I will edit.

Got it! I think ideally all the function buildpacks should fail to build if GOOGLE_FUNCTION_SOURCE does not exist, regardless of whether the user has set it or if the default is being used.


Release v1.16

Tracking issue for releasing v1.16

[ ] https://github.com/mxschmitt/playwright-go/pull/224

Can we also add locators?

Can we also add locators?

@mxschmitt  Can you help in implementing it ?


GenericError not exported

Checklist

[X] I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
[X] I have looked into the API documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved
Following up to:

https://github.com/auth0/auth0-react/issues/636

it’s useful to have GenericError exported in addition to the other Error classes. This enables clients to quickly detect if they’re dealing with any kind of Auth0 Error:
import { GenericError, useAuth0 } from '@auth0/auth0-react'

const ErrorComponent = () => {
  const { error } = useAuth0()

  if (error instanceof GenericError) {
    console.log(error.error_description)
  }

  …

Describe the ideal solution
In auth0-react/src/index.tsx, export GenericError from auth0-spa-js:
  export {
    …
+   GenericError,
    …
  } from '@auth0/auth0-spa-js';

Alternatives and current workarounds
We can determine the GenericError by grabbing the prototype of any of the child errors:
import { AuthenticationError, useAuth0 } from '@auth0/auth0-react'

const ErrorComponent = () => {
  const { error } = useAuth0()

  const GenericAuth0Error = Object.getPrototypeOf(AuthenticationError)

  if (error instanceof GenericError) {
    console.log(error.error_description)
  }

  …

Additional context
All other errors were exported in:

https://github.com/auth0/auth0-react/pull/637

Thanks for reaching out about this, i will make sure to add this, thanks!


add cancel command for conflict attribute

Related to: https://github.com/neo-project/neo/pull/2818

Add cancel command.
Check if aimed tx is in mempool, if it is, choose the max networkfee between the current and the aimed. If it isn't, wait for inputting networkfee manually.
Add a NOP to tx.script to ensure not rejected by consensus.
Return error when aimed tx is already confirmed.

What is the reason behind this PR?
There is a logic that needs to work if the TX is send.

What is the reason behind this PR? There is a logic that needs to work if the TX is send.
Do you mean check if tx is already confirmed? It's just to avoid meaningless operation. No one wants to pay fee to cancel an already existed transaction. And if it's existed, no need to execute the rest code.

I mean the cancel command

Can the node current cancel a normal tx with command?
That is why I'm asking about the conflict. Why this "feature" is really needed? In particular, manually.

Can the node current cancel a normal tx with command? That is why I'm asking about the conflict. Why this "feature" is really needed? In particular, manually.

Cancel tx when it's not on-chain yet.(In mempool)

I mean the cancel command

It's for use Conflicts attribute.

Cancel tx when it's not on-chain yet.(In mempool)

Why do not add this feature to any tx in this case as well? Why just the ability to cancel `conflict?

Cancel tx when it's not on-chain yet.(In mempool)

Why do not add this feature to any tx in this case as well? Why just the ability to cancel conflict (if not on-chain)?

It's any tx, just in a new transaction attribute called Conflicts

@superboyiii format update please

@superboyiii format update please
Done


Change visit(TokenSyntax) function of SyntaxRewriter to return TokenSyntax

There should be no reason why a TokenSyntax should get rewritten to a different node kind and this allow us to remove a force unwrap in the diagnostics infrastructure.

@swift-ci Please test

https://github.com/apple/swift-stress-tester/pull/202
@swift-ci Please test

I think this is for the best, but I do wonder if we should extend it to others as well. Ie. should rewriting a function decl be able to rewrite to a statement? Or should we return a decl syntax there?

I was wondering the same. For TokenSyntax I was pretty sure that there’s no valid use case to rewrite it to any other node. For all the others, I would like to make a survey of the current SyntaxRewriter users (most notable swift-format and SwiftLint), whether they are making use of this option.

SyntaxRewriter already restricts for many return types; for example, a rewriter for FunctionDeclSyntax can only return other DeclSyntaxes. I think that's the right behavior, and this improvement for TokenSyntax is a good one.
One situation that comes to mind where it's valid to replace a node with one of a different kind is at a statement level; a CodeBlockItem can have a Decl, Expr, or Stmt as its child so one could feasibly want to reach for a rewriter that swaps one out for something else. However, that would also allow for invalid replacements (e.g., replacing a Decl with a Stmt in a member list), so such a replacement is probably better done at the CodeBlockItem level by replacing the child instead of allowing it at the child itself.

SyntaxRewriter already restricts for many return types; for example, a rewriter for FunctionDeclSyntax can only return other DeclSyntaxes. I think that's the right behavior, and this improvement for TokenSyntax is a good one.

Ah. I was looking at the private implementation method rather than the public one 😅. I'd still say this applies for all the functions that currently return Syntax though.

One situation that comes to mind where it's valid to replace a node with one of a different kind is at a statement level; a CodeBlockItem can have a Decl, Expr, or Stmt as its child so one could feasibly want to reach for a rewriter that swaps one out for something else. However, that would also allow for invalid replacements (e.g., replacing a Decl with a Stmt in a member list), so such a replacement is probably better done at the CodeBlockItem level by replacing the child instead of allowing it at the child itself.

I think in that case I'd be fine with requiring clients to visit the parent instead, ie. I'd rather to default to not being able to rewrite to completely bogus trees but if someone reallllyy wants to...


Hyperparameter sweeps with Optuna or Ray Tune

This should be a lot more efficient than naive grid search

Not clear if we actually want this


Add Team markup

only the markup
notice
partials/project/hero.html was moved to partials/hero.html because it can be used in more pages (projects, careers, team and stack)

I added the info I could gather about Manu, Timofei and Konstantin

@erizocosmico can/should u merge it?
or should I do it on my own?


Big model use case

Hi,
I successfully built an engine with 9 tmx sources totalling 23 Mio segments, and one text source (news shuffle) of 1.5 GB for monolingual extra data.
the engine folder totals 50 GB of which 15GB for the LM and 35 GB for the Sapt files.
I kept increasing the memory up to 90 GB of ram.
Never loaded the model successfully.
I am rebuilding with less data right now.
Just curious if you guys loaded such big size models and how long it takes.

Hi @vince62s ,
we're currently testing MMT with very large models. I think @cattoni has some results on this topic.
By the way, this is the activity we need to perform in order to make a production-ready release, so it's definitely in our roadmap.

update:
I divided the data by half, leading a engine folder size of 23 GB.
Model loads perfectly but takes twice the size in memory.
I did not expect this behavior.

good to know:

how long did it take to load the model at "start" command
how much ram do you have on the machine to load such a model ?

I've tested such engine on a m4.10xlarge AWS machine (40 cores, 160 GB RAM):

"mmt start" took 10m0.3s to complete (real time of command "time");
after "mmt start":

the RAM occupied by the engine was 39GB (command "free");
according to the command "top", the java process took 194GB of Virtual Mem, 122GB of Resident Mem, 86GB of Shared Mem

@davidecaroselli

do you find it "normal" ? is this normal SAPT behavior to use much more memory than its disk space ?
I think you need to update the "memory" requirement in the HW home page. it's much more than 1GB for 350MB of training data.

in the end, one will need many big machines to cover a 100 pairs of languages :)
cheers.

@vince62s
Thanks for the feedback on memory requirements, we will update that info.
For the ratio between disk space / RAM space: with the new infrastructure of MMT there is no more 1-to-1 ratio.
At the moment the LM is the one that definitely takes much RAM (both because of the monolingual data, and the optimization needed for the AdaptiveLM). While the SAPT are much less greedy of RAM.
Please notice also that lots of data-structures are memory mapped, this means that the OS keep them in RAM if it has enough free space (instead of waste free space, it tends to use it as much as it can). So it can be possible that on large machines MMT will try to occupy RAM if it's free in order to speed up the computation.
Generally speaking, this release is not a low-RAM engine yet. But in the future we will work to make the system more efficient for sure!
Thank you.


Correct connector-aci ingress

Was generating a path of //connector-aci/(.*)
Doesn't need to use the proxyPath (ingress just maps to a port)

Doesn't need to use the proxyPath (ingress just maps to a port)

The non-ACI ingress also references $nifiCluster.ingress.proxyPath (though doesn't hit the double-slash issue).

Doesn't need to use the proxyPath (ingress just maps to a port)

The non-ACI ingress also references $nifiCluster.ingress.proxyPath (though doesn't hit the double-slash issue).

non-ACI ingress does need to respect proxyPath, else nifi ui becomes inaccessible.


.net 8 support

Hi there,
When are you planning to support .net 8? Thanks.

Spark 1.0 was just released with .NET 8 support.


Pipe not supported

I created a Script step:
-<EMAIL_ADDRESS>    title: Kill Running Emulator
    is_always_run: true
    inputs:
    - content: |-
        #!/bin/bash
        # fail if any commands fails
        set -e
        # debug log
        set -x

        adb devices | grep device | cut -f1 | xargs -I_ adb -s _ emu kill

, which when run turned into:
+------------------------------------------------------------------------------+
| (0) Kill Running Emulator                                                    |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.3                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2017-04-23T20:29:25Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
+ adb devices
+ grep device
+ cut -f1
+ xargs -I_ adb -s _ emu kill
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | Kill Running Emulator (exit code: 123)                        | 0.47 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-script/issues             |
| Source: https://github.com/bitrise-io/steps-script                           |
+---+---------------------------------------------------------------+----------+

Hi,
This is not a script/step issue, this is how set -x prints the commands. set -x prints every command before it would execute it.
In your case it means:

Ran adb devices - was OK
Ran grep devices - was OK
Ran cur -f1 - was OK
Ran xargs .. -> failed

You can try this by simply saving the script into a file and then run it with bash ./path/to/script.sh (note: this step basically does this, it saves the script into a file and then runs it), or simply run set -x in your Terminal (if you use bash as your shell) to enable Bash's "debug logging".
If you have any questions just let us know!


Why the Nexus generator doens't handle relation includes?

All the find queries generated by the paljs nexus generator don't seem to care about the include field. So that rises two questions:

How are you guys handling this in your generated apis?
Does paljs has any intention to add this on the generator?

Just found out that it as my misunderstanding of GraphQL


Update codebase to require 6.0 as a minimum platform. Fixes #454

Includes:

Updating dependencies
Adding additional method in FileImporter due to updated API
Fixing minor deprecation issues (more to come)
Including code from http://www.randelshofer.ch/blog/ as AEM 6.0 uberjar does not include this code (test-scope only)
Removed two optional imports as they are included in 6.0

Confirmed that all tests pass and package is installable on 6.0 GA.

Sorry I pushed this to this repo instead of my fork, but it's a PITA to change that now.

Adios 5.6.1. It's been a fun ride...


pex creation fails under pants w/ No such file or directory error

23:06:05.36 [INFO] Starting: Resolving 3rdparty/python/constraints.txt
23:06:05.38 [WARN] /home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/base/exception_sink.py:313: DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  process_title=setproctitle.getproctitle(),
23:06:05.38 [ERROR] 1 Exception encountered:
Engine traceback:
  in select
  in `typecheck` goal
  in Typecheck using MyPy
  in pants.backend.python.typecheck.mypy.rules.mypy_typecheck_partition
  in pants.backend.python.util_rules.pex.create_pex
  in pants.engine.process.fallible_to_exec_result_or_raise
Traceback (most recent call last):
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/engine/process.py", line 241, in fallible_to_exec_result_or_raise
    raise ProcessExecutionFailure(
pants.engine.process.ProcessExecutionFailure: Process 'Building mypy.pex with 1 requirement: mypy==0.782' failed with exit code 1.
stdout:
stderr:
Failed to spawn a job for DistributionTarget(interpreter=PythonInterpreter('/usr/local/bin/python3.8', PythonIdentity('/usr/local/bin/python3.8', 'cp38', 'cp38', 'manylinux2014_x86_64', (3, 8, 5)))): [Errno 2] No such file or directory: '/home/toolchain/.pex/unzipped_pexes/49b4b32295a60a0a4dfc0659c3a44f93560c4a81/.deps/pex-2.1.16-py2.py3-none-any.whl/pex/__pycache__/variables.cpython-37.pyc.139923989690656'
Traceback (most recent call last):
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 256, in run
    engine_result = self._run_v2()
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 168, in _run_v2
    return self._maybe_run_v2_body(goals, poll=False)
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 185, in _maybe_run_v2_body
    return self.graph_session.run_goal_rules(
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/init/engine_initializer.py", line 125, in run_goal_rules
    exit_code = self.scheduler_session.run_goal_rule(
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 568, in run_goal_rule
    self._raise_on_error([t for _, t in throws])
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 527, in _raise_on_error
    raise ExecutionError(
pants.engine.internals.scheduler.ExecutionError: 1 Exception encountered:
Engine traceback:
  in select
  in `typecheck` goal
  in Typecheck using MyPy
  in pants.backend.python.typecheck.mypy.rules.mypy_typecheck_partition
  in pants.backend.python.util_rules.pex.create_pex
  in pants.engine.process.fallible_to_exec_result_or_raise
Traceback (most recent call last):
  File "/home/toolchain/.cache/pants/setup/bootstrap-Linux-x86_64/2.0.0b2_py38/lib/python3.8/site-packages/pants/engine/process.py", line 241, in fallible_to_exec_result_or_raise
    raise ProcessExecutionFailure(
pants.engine.process.ProcessExecutionFailure: Process 'Building mypy.pex with 1 requirement: mypy==0.782' failed with exit code 1.
stdout:
stderr:
Failed to spawn a job for DistributionTarget(interpreter=PythonInterpreter('/usr/local/bin/python3.8', PythonIdentity('/usr/local/bin/python3.8', 'cp38', 'cp38', 'manylinux2014_x86_64', (3, 8, 5)))): [Errno 2] No such file or directory: '/home/toolchain/.pex/unzipped_pexes/49b4b32295a60a0a4dfc0659c3a44f93560c4a81/.deps/pex-2.1.16-py2.py3-none-any.whl/pex/__pycache__/variables.cpython-37.pyc.139923989690656'

seeing this randomly from time to time in different CI runs.

Pants now invokes multiple instances of mypy concurrently: it's possible that this is related.

Looking very closely at the last line, I think this may be caused by the sys.executable value that lies issue on OSX framework builds (#1009 fixed by #1049) Since what pex thinks is a Python 3.8 interpreter is actually launching a Python 3.7 interpreter (the file not found is a 3.7 bytecode file Failed to spawn a job for DistributionTarget(interpreter=PythonInterpreter('/usr/local/bin/python3.8', PythonIdentity('/usr/local/bin/python3.8', 'cp38', 'cp38', 'manylinux2014_x86_64', (3, 8, 5)))): [Errno 2] No such file or directory: '/home/toolchain/.pex/unzipped_pexes/49b4b32295a60a0a4dfc0659c3a44f93560c4a81/.deps/pex-2.1.16-py2.py3-none-any.whl/pex/__pycache__/variables.cpython-37.pyc.139923989690656'.
I can't provide a causal chain reason yet though so I'll leave this open to work on a bit harder.

this happens in CI (circleci), not OSX.

Aha, ok - almost certainly something else then. I'll take a look.

Narrowing down a bit more, this error involves running the Pex PEX which is the one released by the Pex proejct and marked as --unzip. This means for the corresponding points above:

Since the PEX bootstrap is doing the unzipping into PEX_ROOT/unzipped_pexes using atomic_directory which is UUID4 best-effort it could also eagerly bytecode compile all files while under that lock to circumvent the much weaker best effort of CPython which just relies on object id - aka memory address - uniqueness.
This could explain the interpreter mismatch if we're running the Pex PEX with 3.8 but it then re-execs itself with 3.7. That needs more investigation though since the Pex PEX interpreter constraints are ">=2.7,<3.9,!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*" which allows for 3.8 and since Pex supposedly always uses the current interpreter instead of re-execing if the current interpreter matches constraints.

Alright, explanation in hand. The issue here is AtomicDirectory. That code is robust but should only be used when the contents of a directory you want to create atomically are immutable. In the case of --unzip (~/.pex/unzipped_pexes/...) and --not-zip-safe (~/.pex/code/...) and the unpacked wheel cache (~/.pex/installed_wheels/...) where the directory is populated with python code that will be executed later, the directory contents is appended to later by python bytecode compilation. Since AtomicDirectory has at least once semantics, in a race involving more than one process filling the directory atomically simultaneously we can have:

1st process creates the directory.
Another process executes against that directory and creates a temporary bytecode file but does not yet rename it: https://github.com/python/cpython/blob/4c2e299d80c53591f05de2669c0edeaf8acd8544/Lib/importlib/_bootstrap_external.py#L126-L132
2nd process (re) creates the directory, losing the temprary bytecode file from 2.
The process in 2 finds the temporary bytecode file it wrote is missing when attempting to atomically rename it: https://github.com/python/cpython/blob/4c2e299d80c53591f05de2669c0edeaf8acd8544/Lib/importlib/_bootstrap_external.py#L133

For atomic mutable directory creation we'll need an interprocess lock. Another approach would be to continue with AtomicDirectory but append an identifier to the path unique to the bytecode compilation, say cpython-37. This has the disadvantage though of keeping a copy of source code for each unique interpreter run against it.

Do either of these solutions need to be applied unconditionally, or we could try to detect when it's unsafe and only use these fixes then?

Do either of these solutions need to be applied unconditionally, or we could try to detect when it's unsafe and only use these fixes then?

They need to be applied unconditionally since detecting when its safe amounts to detecting if there are other similar processes racing which amounts to either implementing an interprocess lock (the proposed solution) or else eliminating the need for a lock (the alternative solution).

yay! thanks for fixing @jsirois !

Ok. Assuming Linux posix APIs are not broken, which is a very safe bet, the observation of temporary pyc files created by Python can only be via os.walk. Pex has at least one of those.

Another instance of this was found in #1098 and fixed in #1099.


<EMAIL_ADDRESS>hash check failed

Looks like explorer++ have a new version out so therefore the hashes don't match
explorerplusplus: <IP_ADDRESS>1 -> <IP_ADDRESS>5
Updating one outdated app:
Updating 'explorerplusplus' (<IP_ADDRESS>1 -> <IP_ADDRESS>5)
Downloading new version
explorerpp_x64.zip (2.0 MB) [=================================================================================] 100%
Checking hash of explorerpp_x64.zip ... ERROR Hash check failed!
App:         epower/explorerplusplus
URL:         https://ci.appveyor.com/api/projects/derceg/explorerplusplus/artifacts/explorerpp_x64.zip?branch=master&pr=false&job=Platform%3A%20x64
First bytes: 50 4B 03 04 14 00 00 00
Expected:    bf1c0b3462bc4fe92d5897bfcf9019a7e1eea4ae1964a87f60e240c7edd4e100
Actual:      7b0067e8a1a7e48b10cfaec463eb5085b860e99c627efdc86e898a104c29f9c5

Fixed, thanks!


Features/26 forget jutsu

Added it in the same way as with the clan page and resigning from a position to remain consistent.


no such file or directory: /home/prashant/..../zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

This shows up every time I open a new terminal.

I'm sorry you're having trouble, but that is not a bug in zsh-syntax-highlighting.  It's a bug in whatever code tries to invoke z-sy-h.

Are you trying to install z-sy-h or to uninstall it?


get_tags or get_paginated_response don't respect page_size

I noticed get_tags always return 50 tags per page even when passing page_size=200. It seems it's because that the next_page here always includes ?n=50 as a first param, so the second &n=200 is ignored. The url looks like /tags/list?n=50&next_page=...&n=200.

However even the first page seems to be ignoring page_size. The URL is just /tags/list?n=200 but
len(resp.json()["tags"])

returns just 50.
The Link header contains n=50 so maybe if the first page worked, the subsequent pages would work too?

I just confirmed with our previous implementation of registry API, the quay.io v2 API also ignores n=<int> param, so this is likely not coregio's fault.

So quay.io has a hard limit on the number of tags returned per page and it's 50. It is possible to set a lower page size, but not higher. The default in coregio is 100 but for quay.io it's not gonna do anything.


As an SDS, i want cumulus cataloging to be optional components.

Search, stage-in, stage-out, catalog are available as separate tasks so Cumulus cataloging is optional though highly recommended in workflows to enable search.


feat: complete queries, make overall project look pretty

This PR mainly adds the queries nvim-treesitter is capable to leverage, and adds some linting, prettying up of manifests and docs, and a CI action to ensure new commits don't fail
Thanks,
Amaan

Here's a demo with the updated queries in neovim using the tokyonight colorscheme

Also, it'd be nice if you could give me collaborator access to the repo, would like to set up actions to auto publish the package with a CI action as well (I maintain ~10 parsers if that makes you more inclined to add me :sweat_smile:)

Btw. I named the rules (_rule) purposefully like that to keep close to the original namings (of the parser in the ungrammar repo), but I'm fine with that naming as well, doesn't really matter...

Ungrammar's spec is loosely defined, and I find these names to fit better and be less "repetitive", I've always disliked grammars that suffix every rule with the same thing, for certain pieces (e.g. groups of directives and statements) it makes sense, but not everything imo :slightly_smiling_face:

When updating the queries for the nvim-treesitter PR, please replace @operator.repeat with @repeat :)


docs on bundles, chunks, long term caching

From @greaber on June 25, 2016 17:15
I'm posting this because I think I understand something about webpack, but I'm not sure, and whether I am right or not, I think the docs could be improved.
I have been using webpack for several months, and I was hazy for a long time about the difference between chunks and bundles.  As I now understand it, though, it is pretty simple.  a chunk is just any output produced by webpack, and a bundle is (essentially) all the outputs produced by webpack.  At any rate, the chunkhash directive, used in naming an output, expands to a hash of that output, while the bundle directive expands to a hash of all the outputs.  If this understanding is right, I think it could be made more clear in the docs.
Some things that make it confusing are that "bundle" is often used to name a particular output and that the long term caching docs suggest there are two options that you might equally want, using per-chunk hashes and using per-bundle hashes, whereas, if I understand correctly, you would almost always want to use a per-chunk hash.  (The only downside of that seems to be that, according to the docs, you cannot use it in conjunction with hot module replacement, but my understanding is that hot module replacement is a dev feature, and you don't need to use any of this hashing in dev because you can just use the dev server or simply disable caching.)
Another thing that is perhaps confusing about these concepts of chunks and bundles is the way the output section has options for filename and chunkFilename.  If my understanding is correct, all outputs are chunks, and all chunks outputs.  The filename option is just used to specify the names of entry chunks.  But the docs for it say "Specifies the name of each output file on disk", so I'm not sure.
Copied from original issue: webpack/webpack#2692

Doesnt this file solve this issue?

Yup. Time to close.

I came here trying to understand what a chunk is, but no help. The link @pksjce posted is broken, also

If it is the link to the "caching" documentation, that didn't help me to understand what a chunk is.

@rafaeleyng #970 is definitely the issue you want. I just re-opened.

Ok, I asked some questions there too. Thanks!