Vertex buffer stride set to zero when reflecting from SPIR-V

Bevy version
f6b42b86691bdea92613df3e1e754dbc9455dbc2
Operating system & version
Windows, Vulkan NVIDIA drivers
What you did
When you reflect vertex buffer layout with reflect_layout(false), the resulting ShaderLayout has stride set to zero. Unlike in OpenGL, in Vulkan this does not result in tightly packed attribute data. It must be set manually by the application to make the resulting attribute data useful. This is a footgun, IMO; a better alternative would be to set the stride to a value that makes the vertex attributes tightly packed.

I agree that the suggested change would make the results more useful, but its worth calling out that we've dumped this reflection code in the new renderer in favor of a more manual approach. We made a number of "opinionated" calls in the current reflection code that make it suitable for common cases, but not suitable for arbitrary cases. Until we can solve the "generic reflection" problem properly, we'll probably favor the more explicit approach.

Sure, at the very least I suggest calling it out in the documentation for the reflect_layout() function, when that gets written. :)

Closing because we have removed the old reflection system in favor of something a bit more explicit. We might ultimately tie naga reflection into our pipeline system, but we dont have any explicit plans for that yet.


Improve logging when clusterloader fails during nodevert tests

Irrespective of whether clusterloader failed to launch the required number of pods or the actual run duration exceeded expected duration, the exit code from the script is 1, for example at https://github.com/openshift-scale/workloads/blob/master/workloads/templates/workload-nodevertical-script-cm.yml.j2#L73
For new user this maybe misleading as even though the test executed successfully (required number of pod were created), the workload pod is marked as Error due to the return code. As a first step we can improve logging in the script to make it more explicit.

@chaitanyaenr FYI


Feature/kafka support

Description

Add MSK support
link: https://github.com/zappa/Zappa/issues/1084
GitHub Issues

added the test cases. @monkut

@liuwenjie it's failing at lint, you need to run make black, and make isort.

@monkut done.

Coverage decreased (-1.0%) to 72.66% when pulling 1d89b0c4424ff627af1611a395fa306125b57e41 on liuwenjie:feature/kafka_support into 19f61daacf01cce27929e9912e2066bbe5f81681 on zappa:master.

@liuwenjie Currently the linter is failing due to too complex.
get_event_source() needs to be refactored.
Looks like the easiest way to resolve this issue is to move the  *EventSources outside of the get_event_source() function.
Not sure the whole effect this will have on speed, but it may be a first step.

@monkut fixed.


[GOCA] Return Reserved Vnet ID on Reserve call

Description
When a reservation on a network is done, it creates a new virtual network which is a "lease" of the parent.
The Children ID (the reservation) is returned in the response body but it is not returne by the "Reserve" function in Goca.
To Reproduce
perform a network reservation using the Goca, the new resource ID is not returned
Expected behavior
Returns the response.BodyInt() to get the new ID of the reservation
Details

Affected Component: Goca
Hypervisor: -
Version: 5.8

Additional context
I have the fix available, I will propose it as a pull request

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PR ID: #3581


No "cancel" button in navigationSearchBar

.navigationSearchBar {
SearchBar("Search", text: $searchText)
}

This has been fixed.


[Cartesian] dace:cpu performance: OpenMP and Expansion Tuning

This is a first of a sequence of PRs improving the performance of the dace:cpu backend.
In this first iteration,

adding OpenMP parallelism
the loop order, array layout and tile sizes are chosen equal to those of cpu_kfirst
test region predicates on a single index  with equality instead of two inequalities

I was not able to fully verify this on pace:

this is already includes "no storage" with which pace is not  yet compatible
runing pace translate tests with the equivalent branch gronerl/dace_cpu_performance_oldstorage which is still based on the storage classes gives a hand full of failed grid points with very small errors on some translate tests. @jdahm  coul you or someone at ai2 please verify that this is acceptable? I'll make sure to update dace_cpu_performance_oldstorage alongside this one.

We get within a factor of 1.5 of gt:cpu_kfirst with this PR for a 6 rank c192 run.

bors try


fix(ListRow): Add hover state and remove overflow menu and button fro…

…m the link

What:
Add hover state and remove overflow menu and button from the link in the list Row. Also, adjust te paddings accordingly"

Why:

How:

Checklist:

[X] Documentation
[X] Tests
[ ] Ready to be merged

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Gs/try web components

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

Please, next time, try to propose something of your mind and personal effort, or at least try to do some major changes
https://github.com/twbs/bootstrap/compare/gs/try-web-components?expand=1  ! ! !


CSI I and CSI O wrongly listed in output of ":set termcap"

Describe the bug
The CSI I and CSI O terminal sequences are wrongly listed in the output of :set termcap.
To Reproduce
Run this shell command:
vim -Nu NONE +'set termcap'

Notice that the sequences ^[[I and ^[[O are at the end of the "Terminal keys" section.  And they're not mapped to any Vim keycode.
Expected behavior
I'm not sure, but either of these 2 statements should be true:

^[[I and ^[[O are not listed in :set termcap, at all
^[[I and ^[[O are listed in :set termcap, but they are prefixed with a Vim pseudo-key, like <FocusGain> and <FocusLost>

Rationale: They are the only sequences which are not mapped to any Vim key or pseudo-key, which is inconsistent.
Environment

Vim version: 8.2 Included patches: 1-2380
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(363)

Additional context
These sequences started to appear in 8.2.2345, when FocusGain and FocusLost were introduced.

I found this while using a custom command that turns the output of :set termcap into a Vim script, which in turn can be sourced to restore all terminal options/keys.  These 2 orphan sequences break this script.

I found this while using a custom command that turns the output of :set termcap into a Vim script, which in turn can be sourced to restore all terminal options/keys.  These 2 orphan sequences break this script.


[BUG] build failed , while installing requirement

i even installed VS-code as it says , but still not workign
info :
OS : wind 11 ,
python = 3.11

      copying psutil\tests\__init__.py -> build\lib.win-amd64-cpython-311\psutil\tests
      copying psutil\tests\__main__.py -> build\lib.win-amd64-cpython-311\psutil\tests
      running build_ext
      building 'psutil._psutil_windows' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for psutil
  Building wheel for winsdk (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for winsdk (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [332 lines of output]

It's asking you to install visual studio, not visual studio code.

Same problem, I already installed visual studio and cmake.. still getting this error

Same problem, I already installed visual studio and cmake.. still getting this error

You need to modify your visual studio by going to the Installer > Individual componets and search for Windows SDK and C++ build tools, that worked for me.
Still, yasb's installer seems to be broken as shown in this issue, i wouldn't bother tinkering with this since the project seems to be pretty dead.

@Hackett99  im just curious, why they are not providing a prebuild binary  of YASB ?
:( it would be so much better

@Hackett99 im just curious, why they are not providing a prebuild binary of YASB ? :( it would be so much better

Development for YASB v1 has been halted as I am currently working on rewriting yasb in rust. The rewrite will include a prebuilt binary release.
Marking as closed as this issue appears to have been resolved


Export and import media album info

Suppose you want to reupload you media from a Pixel device, but downloading, deleting and uploading will remove all reuploaded media from all albums.
To solve this, album info for each item can be extracted and then imported to restore the album assignment.

I suppose this could just be a CSV that gets exported by the tookit before doing a move, then ingested after re-upload to automate restoring the existing albums?

Yes, but i'm thinking json instead of csv

Have you thought of what is sufficient to uniquely identify photos? Filename won't cover all cases (but might be OK if it could ignore any possible collisions before doing anything to the files). Does the "undocumented api" export file checksums? That would be nice :)

Filename + size would be enough I guess. Checksums would be nice, but api does not expose them.

There is still a way to do it, with the current capabilities of the script.
But it requires more manual action.

Make sure every media item in your library belongs to at least one album.
Use "Exclude albums" filter, select all of them, select action "add to album" You may encounter #2, just run it again, create a new album, until none are left.
Download a single album, delete all its media, reupload
Again use "Exclude albums" filter in the same way, now all your reuploaded items will be grouped in an album.
Repeat for every album

I have not tested it myself, but it should work.

@oryjkov great, i'll take a look when i get the time!


Can't migrate accentuated classes - Class not found

Some on my entries have accents, and when I created a migration the class of the migrated entry is accentuated too! The creation of the migration is successfull, but when I try to migrate it from production environnement, the following error occured :
Error:
Error
Class 'craft\contentmigrations\m190206_181015_migration_entry_théolaur' not found

    1. in /home/clients/3723fd0999eae3cde8e8969455853f77/web/beta/vendor/craftcms/cms/src/db/MigrationManager.php at line 119
<PHONE_NUMBER>13114115116117118119120121122123124125126127128

                            {
            if (!is_dir($this->migrationPath)) {
                throw new Exception("Can't instantiate migrations because the migration folder doesn't exist");
            }

            $file = $this->migrationPath . DIRECTORY_SEPARATOR . $name . '.php';
            $class = $this->migrationNamespace . '\\' . $name;
            require_once $file;

            return new $class;
        }

        /**
         * Upgrades the application by applying new migrations.
         *
         * @param int $limit The number of new migrations to be applied. If 0, it means
         * applying all available new migrations.
         * @throws MigrationException on migrate failure
         */

Migration Manager generated the following class :
<?php

namespace craft\contentmigrations;

use craft\db\Migration;
//use craft\db\MigrationManager;
//use craft\helpers\MigrationHelper;

use firstborn\migrationmanager\MigrationManager;

/**
 * Generated migration
 */
class m190206_181015_migration_entry_théolaur extends Migration
{
    /**
    Migration manifest:

    ENTRY
        - théolaur
            */

private $json = <<<JSON
{"content":{"entries":[{"slug":"théolaur","section":"clients","sites":{"default":{"slug":"théolaur","section":"clients","enabled":"1","site":"default","enabledForSite":"1","postDate":{"date":"2019-02-01 15:46:00.000000","timezone_type":3,"timezone":"Europe/Zurich"},"expiryDate":null,"title":"Théolaur","entryType":"clients","fields":{"clientImage":[{"elementType":"craft\\\\elements\\\\Asset","filename":"theolaur.png","folder":"clients","source":"images"}],"clientType":["couleur"]}},"french":{"slug":"théolaur","section":"clients","enabled":"1","site":"french","enabledForSite":"1","postDate":{"date":"2019-02-01 15:46:00.000000","timezone_type":3,"timezone":"Europe/Zurich"},"expiryDate":null,"title":"Théolaur","entryType":"clients","fields":{"clientImage":[{"elementType":"craft\\\\elements\\\\Asset","filename":"theolaur.png","folder":"clients","source":"images"}],"clientType":["couleur"]}},"german":{"slug":"théolaur","section":"clients","enabled":"1","site":"german","enabledForSite":"1","postDate":{"date":"2019-02-01 15:46:00.000000","timezone_type":3,"timezone":"Europe/Zurich"},"expiryDate":null,"title":"Théolaur","entryType":"clients","fields":{"clientImage":[{"elementType":"craft\\\\elements\\\\Asset","filename":"theolaur.png","folder":"clients","source":"images"}],"clientType":["couleur"]}}}}]}}
JSON;

	/**
	 * Any migration code in here is wrapped inside of a transaction.
	 * Returning false will rollback the migration
	 *
	 * @return bool
	 */
	public function safeUp()
	{
	    return MigrationManager::getInstance()->migrations->import($this->json);    }

    public function safeDown()
    {
        echo "m190206_181015_migration_entry_théolaur cannot be reverted.\n";
        return false;
    }
}

Solution
I fixed it by changing "m190206_181015_migration_entry_théolaur" class name with "m190206_181015_migration_entry_theolaur".
CraftCMS
PHP version | 7.2.14
Craft edition & version | Craft Solo 3.1.8
Database driver & version | MySQL 5.6.33
Migration Manager | 3.0.17

Sorry! To make it work I had to change the name of the class (without accents) but also the name of the file! Thanks

We are currently facing the same issue and are testing this solution. Should this solve the issue, I'd mark this as a huge bug.

@MichaelCaraccio  @filip-van-hoeckel working on a fix for this.

@MichaelCaraccio @filip-van-hoeckel fixed in latest release


prevent NullReferenceExceptions on ConsumeResult

resolves #919 by throwing a more verbose exception when accessing the
convenience properties in ConsumeResult.

@confluentinc It looks like @enzian just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

few comments then lgtm, thanks!

Finally had time to process the feedback! Thanks for the review!

... and i finally had time to look through the list of open PRs. LGTM - thanks!


--get-filename places a timestapmp at the end of file name if URL points to the live stream

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.05.18 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
yt-dlp -- palces a timestamp at the end of the retrieved file name if there is a live stream
#!/bin/bash
# Following stream is always available, therefore taken for example
ChannelPath="https://www.youtube.com/c/TheGoodLiferadio/live"
video_id=$(/usr/local/bin/yt-dlp --no-warnings --get-id "$ChannelPath")
echo "$video_id"
url="https://www.youtube.com/watch?v=$video_id"
VideoFilename=$(/usr/local/bin/yt-dlp -vU --get-filename -o "%(upload_date)s %(title)s" "$url")
echo "$VideoFilename"```

The last call produces a string with yyyy-mm-dd hh_mm before the extension.

### Verbose log

```shell
19hKXI1ENrY
[debug] Command-line config: ['-vU', '--get-filename', '-o', '%(upload_date)s %(title)s', 'https://www.youtube.com/watch?v=19hKXI1ENrY']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out UTF-8 (No ANSI), error UTF-8, screen UTF-8
[debug] yt-dlp version 2022.05.18 [b14d52355] (zip)
[debug] Python version 3.6.8 (CPython 64bit) - Linux-3.10.0-1160.62.1.el7.x86_64-x86_64-with-centos-7.9.2009-Core
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: ffmpeg -bsfs
[debug] exe versions: ffmpeg 3.4.10, ffprobe 3.4.10
[debug] Optional libraries: Crypto-3.12.0, certifi-2021.10.08, sqlite3-2.6.0
[debug] Proxy map: {}
Latest version: 2022.05.18, Current version: 2022.05.18
yt-dlp is up to date (2022.05.18)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=19hKXI1ENrY
[youtube] 19hKXI1ENrY: Downloading webpage
[youtube] 19hKXI1ENrY: Downloading android player API JSON
[youtube] 19hKXI1ENrY: Downloading m3u8 information
[youtube] 19hKXI1ENrY: Downloading m3u8 information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] 19hKXI1ENrY: Downloading 1 format(s): 96
20211207 Deep House Radio _ Relaxing & Chill House, Best Summer Mix 2022, Gym & Workout Music 2022-06-14 23_52

This is expected behavior. Use full_title instead to get the title without timestamp. See the readme for difference b/w the two

@pboettcher if pukkandan's reply solves your problem, please close this issue

Yeah, that's the one. My bad


Fix Maven version in description of Java Maven stack

https://catalog.redhat.com/software/containers/ubi9/openjdk-17/61ee7c26ed74b2ffb22b07f6?image=65a90783d59cca758b7d8d64&container-tabs=packages https://catalog.redhat.com/software/containers/ubi8/openjdk-11/5dd6a4b45a13461646f677f4?image=6639ed26fe2c35406921c084&container-tabs=packages
What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?
Which issue(s) this PR fixes:
Link to github issue(s)
PR acceptance criteria:

[ ] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[ ] Test automation
Does this repository's tests pass with your changes?
[ ] Documentation
Does any documentation need to be updated with your changes?
[ ] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

I'm wondering if we should not remove the Maven version as I do not think it is very important

/ok-to-test

LGTM +1 on not removing the Maven version. @kadel could you please review as the owner of the stack?

Bump @kadel


Match community names case-insensitively

This PR:

Updates the community exists error message to match the new ExperienceBundle message.
Matches community names case-insensitively.

Fixes an issue discovered by @Julian88Tex in SalesforceFoundation/SAL#2116.
Critical Changes
Changes
Issues Closed

Fixed an issue where the create_community task would throw an exception on an existing community despite skip_existing being true.

Sorry my comment was pending.

Weird. It actually put the comments in created order, but out of chronological order as displayed.

I can approve but I'd rather not switch to casefold pervasively unless we are confident that its better (i.e. more like Salesforce).

You're right. I looked it up and this particular resource is calling String.equalsIgnoreCase().
Updated.


Detect and report hashbag as unsupported

If I run sjs over a NodeJS source which has #!/usr/bin/env node then I get the error
Error: Line 1: Invalid regular expression

I wasn't able to find a clean way to remove the offending line from the source and continue parsing.
Perhaps throwing a more direct error message? This PR would instead give the error
Error: Line 1: HashBang interpreter directive is not supported

Closing because this is probably obviated with the release of 1.0.


NFHttpClient uses deprecated MaxHttpConnectionsPerHost for connection pool size

Looks like NFHttpClient is still uses MaxHttpConnectionsPerHost for the connection pool size even though the property is deprecated by MaxConnectionsPerHost.
https://github.com/Netflix/ribbon/blob/5e6066dd63253014599b4fd89713a7b51f19d165/ribbon-httpclient/src/main/java/com/netflix/http4/NFHttpClient.java#L165
https://github.com/Netflix/ribbon/blob/5e6066dd63253014599b4fd89713a7b51f19d165/ribbon-core/src/main/java/com/netflix/client/config/CommonClientConfigKey.java#L83
Related issue: https://github.com/spring-cloud/spring-cloud-netflix/issues/1466
Thanks
Weiping

+1


how to stop grafana from hitting the server if server is not working

when the server side is not working, Grafana is still hitting the server. how to stop grafana from syncing the server every min.

Also initial Request(Synchronize with data) is disabled

@ashishagarwal7 You can use custom code as described in documentation.


App Groups for FZ

Create customs shortcuts to launch paired apps to specified zones (preferably, can ignore active layout).

good idea, #5901 is the tracking


feat(axisPointer): add option to disable emphasis. close #18495

Brief Information
This pull request is in the type of:

[ ] bug fixing
[X] new feature
[ ] others

What does this PR do?
This PR adds a triggerEmphasis option to the axisPointer that enables the user to disable the emphasis/highlight behavior associated with the axis pointer.
Fixed issues

#18495

Details
Before: What was the problem?
Prior to this PR, the axis pointer would always trigger highlight behavior. When you have a line chart with multiple series, the axis trigger tends to highlight all the series, which is often unhelpful and can be really confusing to users.

There is not a good way to work around this currently. You can see an example of some issues related to this in https://github.com/perses/perses/pull/1112.
After: How does it behave after the fixing?
After this PR, the user has the option to disable this behavior on a given axis by setting axisPointer.triggerEmphasis to false. When set to false, the highlight/emphasis behavior will not trigger with the axis pointer. Other highlight/emphasis (e.g. on mouseover a specific line) is retained.
The default value for axisPointer.triggerEmphasis is true when not set, retaining the prior behavior.
Below is a screenshot of the axisPointer.triggerEmphasis: false visual test. You can see the diff is whether or not all the lines are highlighted. Note that it still retains highlight behavior on mousing over a particular line.

Document Info
One of the following should be checked.

[ ] This PR doesn't relate to document changes
[ ] The document should be updated later
[X] The document changes have been made in https://github.com/apache/echarts-doc/pull/343

~I'm happy to take a stab at making a PR to the docs once we're sure about the naming of the new option. I may need some help with the zh-based language bits. Let me know if you'd prefer I help with this or leave it to the maintainers.~ One of my teammates helped me with the translation, but it could use a second set of eyes to make sure we got it right.
Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
I added two test cases to test/tooltip-axisPointer2.html. One for the false case and one for the true case. Let me know if you think I should break this out into a separate test case, and if so, what you think the best name is for it.
I added visual tests for each test case that take screenshots at the following points:

When mousing over a section of the chart without a line. This validates the axis pointer's configuration is behaving as expected.
When mousing over an individual line. This validates non-axis-pointer highlight behavior is not impacted.

Others
Merging options

[x] Please squash the commits into a single one when merging.

Other information
I was unsure of the best name for this configuration option. This behavior is referred to as emphasis in the configuration of the styling, but is referred to as highlight when triggering the event. I started with triggerEmphasis because I thought users might be more familiar with the styling configuration, but I can see arguments for triggerHighlight. I used the trigger* naming to match the similar-ish triggerTooltip option. I'm happy to rename it to whatever the maintainers think is best.

The code looks good to me but it seems some of the tooltip-related test cases fail in the visual test.

@juliepagano Can you have a look?

Sure thing! The diff from "tooltip-axisPointer2" is from the case where triggerEmphasis is false, so that's expected (screenshot below). I'll take a closer look at the other failing tests to see what's going on there.

The visual tests look much better after the commit I made to remove triggerEmphasis from the conditional for involveSeries. The only failing tooltip test is now the expected one for triggerEmphasis: false.
Screenshot of the expected visual diff and showing all the other tooltip tests passing.

Scrolling down to screenshot the other tests.

I'm working with one of my teammates to get help with the Chinese translation, so I can put up a docs PR to go with this. Hoping I'll have that up some time today.

Thank you for this high-quality pull request!

We ususally release a new version every two months. If you want to use this feature ASAP, you can use the [nightly](npm install echarts@npm:echarts-nightly) version in your development environment.


TagGroup: Field support

Adds label, description, error message, and contextual help support to TagGroup.
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Test new story at TagGroup: 'with label, description, contextual help'. Use controls to test combinations of validation states.
🧢 Your Project:

Action button seems to immediately lose focus now. Not sure what's causing it, looking into it.

Action button seems to immediately lose focus now. Not sure what's causing it, looking into it.

Needed to update which ref was being passed into useTagGroup. Should be fixed now.

Noticed that tags don't line up with other form elements.
I noticed that in the TagField contributions, there is always a border or line to show it's a Field, so it's ok that what is inside doesn't line up since the border does. I wonder if maybe TagGroup shouldn't be in Forms and instead TagField would be? or maybe we get rid of the leading margin, which will be hard for multiple rows since this isn't flex


Md-Chips Not rendering on iOS 10.3.3 (iPad)

Bug, feature request, or proposal:
MdChips don't show up at all on iPad.
What is the expected behavior?
That they work on iOS
What is the current behavior?
Chips don't render at all.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
I can't get Plunker template to load at all. Here's the code snippet I use.
`
<md-chip-list #testChips>
<md-chip *ngFor="let color of selectedColors;let i=index" removable="true" (remove)="selectedColors.splice(i,1)">{{color}}
  <md-icon mdChipRemove>cancel</md-icon>
</md-chip>

<input MdChipInput placeholder="Type here to add chips" (mdChipInputTokenEnd)="addChip($event)" [mdChipInputFor]="testChips" [mdChipInputAddOnBlur]="true" [mdChipInputSeparatorKeyCodes]="[13, 188]" [mdAutocomplete]="testAC" [formControl]="testControl"
/>

<md-autocomplete #testAC="mdAutocomplete">
  <md-option *ngFor="let color of getFilteredVals(testControl.value)" [value]="color">
    {{color}}
  </md-option>
</md-autocomplete>

`
What is the use-case or motivation for changing an existing behavior?
To make chips work on ios touch devices.

The code above works on Android and also on iOS simulator on Mac.

Apologies. The issue was on my end. Closing.


App crash in release mode

Describe the bug
Sometimes app crash right after launch.
To Reproduce
Steps to reproduce the behavior:

Build app in release mode and deploy
Start app
If it did not crash, restart app

Expected behavior
Expected normal start without crash
Desktop (please complete the following information):

OS: [e.g. Windows 10 1909 18363.815]
App version: [v0.7.9]

Additional context
Built from develop branch.

I wonder if this is related to the changes @ADeltaX made...

@yaichenbaum Just reverted his changes and it is still crash

@yaichenbaum As i understand, that happen because of my changes about theme change

Oh, I did notice you switched to a different method for the get\set.

What do you mean?

Before your change, the setting for acrylic was a simple get and set, this would automatically save the setting as well saving us from needing to detect it when launching the app. An example of how it should be is,
public bool AcrylicSidebar
{
     get => Get(false);
     set => Set(value)
}

I remember this, but this implementation was buggy for toggle switches, to enable or disable it you had to click it twice. So i reworked it and it work good in debug mode.

We need to figure out why this implementation causes that issue, it's worth it to use the implementation I shared above since it is more compact. I have used a similar implementation for settings in others apps and it worked fine, so I must of missed something when copying it over.

Good example, preference page, onedrive toggle working good, to enable or disable next toggle(show dialog...) you have to click twice, but if you click only once and reload settings page, toggle will change  state. But, anyway, i don't think get and set of acrylic parameter can cause app crash.

I wonder if this is related to the changes @ADeltaX made...

My code is 200% stable 😂😂😂
Anyway, jokes aside, I've had the same issue before my commit, and only in Release mode, so...
(PS: it happened on 0.7.7 store version for some reason but it's more random and rare)

I canceled the rollout of the v0.7.9 release. I am not sure what's going on but I would appreciate if someone can figure it out.

@yaichenbaum We can revert my changes until problem will not be fixed. Currently i really don't understand what's wrong with my patch in release mode. Any help appreciated.

@tsvietOK Did you get an exception when you tried running the app in release mode?

@yaichenbaum No, i can't catch any exception, app just crash right after start(Sometimes it starts fine).

@yaichenbaum Some notice, if comment line app starts fine(of course theme change in this case is not working)

"Unhandled exception at 0x00007FFA571232E0 (Windows.UI.Xaml.dll) in Files.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000001ECFDD83BA0, 0x0000000000000002)."

@yaichenbaum Sorry, i don't know what to do with this info:(

@tsvietOK I tried commenting out the line you linked and I still get the issue.

@yaichenbaum There is another line.

@yaichenbaum problem somewhere in lines
https://github.com/tsvietOK/files-uwp/blob/36e1853cd6ab068b28d1c1417e31aeca8e295140/Files/Helpers/ThemeHelper.cs#L113
https://github.com/tsvietOK/files-uwp/blob/36e1853cd6ab068b28d1c1417e31aeca8e295140/Files/Helpers/ThemeHelper.cs#L119
https://github.com/tsvietOK/files-uwp/blob/36e1853cd6ab068b28d1c1417e31aeca8e295140/Files/Helpers/ThemeHelper.cs#L125
If comment them, it works fine

@yaichenbaum The problem is in var TintLuminosityOpacity in AppTheme. For some reason setting a value to this var in methods SetDefaultTheme(), SetLightTheme() and SetDarkTheme() causes app crash.

It turns out this issue goes back pretty far, it shouldn't be an issue for the store build.

@yaichenbaum We can keep this PR open until we will be sure that there is no issue for the store build

@yaichenbaum Bug in v0.7.9 still exists

@tsvietOK Even if you open the app a second time?

@yaichenbaum After reinstall and clear data first and second start - crash, third start successful

That is fine, does it work to create a new tab?

@yaichenbaum It crash when opening new tab

@yaichenbaum My PR should fix that

@tsvietOK Thank you for working on this issue, the fix is now out in production.


Stream is consumed when using ReadAsAsync

Problem: If HttpResponseMessage.Content is read with ReadAsAsync the stream will be consumed. This causes issues when the user then tries to read the content of a cached response resulting in a null stream.
Solution: Serialise the response before adding it to the cache and deserialise it before retrieving it. This should be done with HttpContent.

Seems that HttpContentMessage only exists in the Microsoft.AspNet.WebApi.Client package which does not have support for targeting .NET Standard. According to this issue it will have support in version 5.2.4 but that's not released yet.
Should we accept this as an error and let people use the other methods of reading content until we can use 5.2.4 or find another solution?

This was fixed in https://github.com/joakimskoog/Cashew/commit/6f4406b0e468a7815ede9e36cc870308c06c4625. It's not a really sexy fix since we need to cache the content as bytes which takes up extra space, but it's the best we can do for now until we move to .NET Standard 2.0 or wait for the 5.2.4 version of the library.


added profile to icon mode

Which category your Pull Request in? (check all applicable)

[x] 🚀 Added new entry
[ ] 🐛 Grammatical Error
[ ] ➕ Tools Update
[ ] 🚩 Other

Add a simple description why your code is in this section
Add my profile in icon mode category.
Add the profile link here
https://github.com/biplab-nag

Thank you so much @biplab-nag


Could not support jupyterlab 3.0

Hi, after upgrade jupyter-lab, the extension not longer work, could you please fix it? I found your extension is very useful. Thank you.
`Conflicting Dependencies:
JupyterLab                 Extension      Package

=3.0.3 <3.1.0             >=2.0.0 <3.0.0 @jupyterlab/application
=3.0.2 <3.1.0             >=2.2.0 <3.0.0 @jupyterlab/apputils
=5.0.1 <5.1.0             >=4.2.0 <5.0.0 @jupyterlab/coreutils
=3.0.3 <3.1.0             >=2.2.0 <3.0.0 @jupyterlab/documentsearch
=3.0.2 <3.1.0             >=2.2.2 <3.0.0 @jupyterlab/launcher
=3.0.2 <3.1.0             >=2.1.1 <3.0.0 @jupyterlab/mainmenu
=6.0.2 <6.1.0             >=5.2.1 <6.0.0 @jupyterlab/services
See the log file for details:  /tmp/jupyterlab-debug-tew_5_t9.log`

same for me.


[macos] enable python (and pipx) on macOS13

Description
python (and pipx) added to MacOS13
Related issue:
https://github.com/actions/runner-images/issues/7590
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

image generated successfully: https://dev.azure.com/mseng/AzDevNext.Deploy/_build/results?buildId=19942253


Add link to legacy app

Add link to legacy app from V2.
Desktop:

Mobile:

Tiny nitpick otherwise good to go.


allow to change tooltip target

Sometimes, the tooltip must be displayed on an element different from the form control.
To allow this in a flexible manner, let's support a new attribute axInputTooltipHolder, which takes a CSS selector (no binding) in order to find a tooltip.

Upgrade Information
The axInput control directive now supports a new attribute axInputTooltipOnParent which can be added to attach the validation message tooltip to the parent of the form control.

Implemented on master (v1.2.0).


"Install Another Version" shows incorrect timestamps

Testing #138068
I have an extension which I published 0.0.1, 0.0.2, then after a while 0.0.4, then 0.0.3, all using the odd/even : release/pre-release convention. When I go to "Install another version", the picker incorrectly shows

It treats all but 0.0.1 as "just now" even though 0.0.2 was around the same time as 0.0.1, and even the others were >10 minutes ago.

Can you please share me the extension to try and repro?

They're now showing up as all "1 hour ago", when in fact it's more like 12 hours ago
https://marketplace.visualstudio.com/items?itemName=jaaxxx.pre-release-test.

It's hard to tell whether this is working correctly now

looks good


how to solve fields are not being encoding when be set default value in proto3?

This is as proto3 format is supposed to work. Encoder does not encode zero value, decoder assumes zero value for all missing fields.


Update ManagedNetwork

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Move location to resource so that policy/group will contain it.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@azuresdkci  It is patch from MNC team, and we are moving location from trackresource to resource

@MyronFanQiu Hi, can you help us review it? It blocks our jobs. Thanks!

Add python md

@zikalino Hi Zim. Could you please check the python.md? I just saw the multi-api in the md file. @yanfa317 Maybe you should also modify the readme.md as well. Zim is the python SDK owner.

@MyronFanQiu I added the python md since we need to create python sdk. I copied and rewrite it from other models. Should I remove the multi-api part? Thanks

@MyronFanQiu@zikalino I have remove the multi api part. Can you help us review it again? Thanks!

@yanfa317 Hi. @zikalino will help you to generate Python SDK. So it's will much helpful to let him review this PR before you send an SDK request to him. Multi-API is not a problem. I just don't have enough knowledge for this part. Zim will go through this readme.python.md anyway eventually. @zikalino Could you please take a look?

Thanks @MyronFanQiu @zikalino Can you explain what is multi api? Do we need it? Also, can you help us review it early? It blocks a lot of our works. Thanks so much!


[Question]: Why did you removed productName from WindowsDeviceInfo ?

What is your question?
You removed almost all WindowsDeviceInfo .. why did you do this ?

Hey!
It was me who added all the necessary information for Windows in https://github.com/fluttercommunity/plus_plugins/pull/814 including the productName.
It got reverted because of not incrementing the versions semantically.
Some Flutter engineers got confused by it at #1000.
Instead of actually trying to increment the version of device_info_plus in pubspec.yaml of their app, they tried editing package's internal code or forcing dependency overrides. I'm speechless.
At the moment you have two choices:

Force pin device_info_plus version to 4.0.2 in your pubspec.yaml file.

dependencies:
  device_info_plus: 4.0.2

Use package from my fork.

dependencies:
  device_info_plus:
    git:
      url: https://github.com/alexmercerind/plus_plugins.git
      path: packages/device_info_plus/device_info_plus
      ref: main

dependency_overrides:
  device_info_plus_platform_interface:
    git:
      url: https://github.com/alexmercerind/device_info_plus.git
      path: packages/device_info_plus/device_info_plus_platform_interface
      ref: main
  device_info_plus_windows:
    git:
      url: https://github.com/alexmercerind/device_info_plus.git
      path: packages/device_info_plus/device_info_plus_windows
      ref: main
  device_info_plus_linux:
    git:
      url: https://github.com/alexmercerind/device_info_plus.git
      path: packages/device_info_plus/device_info_plus_linux
      ref: main
  device_info_plus_macos:
    git:
      url: https://github.com/alexmercerind/device_info_plus.git
      path: packages/device_info_plus/device_info_plus_macos
      ref: main


Regular Expression Denial of Service in mime 1.4.0

According to NSP, there is a regular expression denial of service in one of your dependencies. The mime package needs to be updated to either version 1.4.1 or greater than or equal to 2.0.3.
This is rated as a high severity by Node Security Platform.
https://nodesecurity.io/advisories/535

A fix will be released Monday Oct 6 (see statement at https://github.com/expressjs/express/issues/3431). The dependency may have an issue, but the issue does not impact this module. There is no patch available for the dependency without a semver-minor change, so we cannot simply release a patch version of this module.

I would love to update it earlier as a patch if you know a method in which we can achieve a semver-patch upgrade of the dependency that has the fix.

Right now master is staging a semver-minor release of this module. I'm talking about bumping from the current-published version of 1.3.4.

Sorry, it's hard to describe anything now. I'm getting multiple emails a minute now about this before I had a change to do anything. Now my hands are basically being tied, unable to perform any code / releases / help and instead endlessly replying to emails.


Latj/implement usage suggestions

Summary of the changes (Less than 80 chars)
Implement Extension methods "As**" to get file contents as string, filestream, memorystream...
Implement static testsource access to reduce usings and code needed.
Implement test coverage
Addresses #bugnumber (in this specific format)

/azp run

/azp run

Updated project structure, targets, and fixed references with the upgraded snapshooter. Now it works in Linux and WSL (ubuntu and ubuntu latest).
Ready for a review :)


Added a newline at the end of a gziped tsv file

Missing newline at the end of tsv file made spark not to read the last event from each file.

Thanks @kazjote! Will get this scheduled for the next release.

Hi,
i upgraded our kinesis-s3 sink from 0.4.0 to 0.4.1 and i had to backport this PR, as it didn't make it upstream. Is this still scheduled?

This is important - bringing forwards...

Do you think this could be released as a 0.4.2 bugfix release?

@christoph-buente It will be part of 0.5.0 which is currently in development (sorry for the delayed answer, didn't get an email somehow).


Add cache state to task summaries on real runs

This PR returns the cacheState all the way down to execContext.exec() , and then stores it in the taskHashTracker so we can assign it to the taskSummary. I'm not sure if taskHashTracker is the best place to keep this data, but we're storing other things there with the same pattern there for the same purpose, so I felt like it was a good fit.
I'm not easily able to write a test that validates that this works against a Remote cache, but because of how the cache package is designed, it should Just Work™.

This test seems to be passing non-deterministically locally. Need to resolve that before merging


Issue #657 LiftComponent refactor

Hi!
Let me know if this is how you intended it to be refactored.
I wrapped all related liftdata fields into one a "LiftData" class.

Codecov Report

Merging #670 into dev will decrease coverage by 0.02%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##                dev     #670      +/-   ##
============================================
- Coverage     57.42%   57.39%   -0.03%
  Complexity     1723     1723
============================================
  Files           177      177
  Lines          8831     8835       +4
  Branches        769      769
============================================
  Hits           5071     5071
- Misses         3559     3563       +4
  Partials        201      201

Impacted Files
Coverage Δ
Complexity Δ

...in/com/almasb/fxgl/dsl/components/LiftComponent.kt
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 378ea6a...f2c6b33. Read the comment docs.

Hi, this is in the right direction. Can we apply stricter refactoring and get rid of repetition: currently the data for X and Y is repeated. Ideally we should have:
val liftDataX = LiftData()
val liftDataY = LiftData()

liftDataX.timer ..
liftDataX.isGoingPositive
liftDataX.duration

// etc.

I don't know if this can be refactored that way, but it should be possible given a lot of existing code duplication

@AlmasB Thanks for the feedback!
I tried to make the LiftData object more general (see 2nd commit). Perhaps you can check again?

@AlmasB I like your suggestion. Perhaps you can check once again (see 3rd commit)? I checked behaviour again with the help of the BBoxSample and it looks like before the PR.


Use TOML configuration, parse command-line options, cleanup & more

Now uses toml4j to parse config.toml instead of Java Properties file config.properties.

Configuration values are now stored in the new Config class.

Add sounds.toml file that contains the path and description of all sounds in the AudioFiles/ folder (closes #8).

Sounds in the database are automatically updated every time the bot starts.

Now uses commons-cli to parse command-line option.
usage: hydrabot
    --config <arg>      The TOML configuration file. Defaults to
                        config.toml
    --help              Print this text and exit.
    --logfolder <arg>   The folder where log files are stored. Defaults to
                        logs/

Add / handler to the WebApi:

note I'm not a 100% sure if the link to add the bot contains all permissions that the Bot actually requires. It would be good to list them in the README (see below).

Merged and updated #7 (Enhance db-services).

Updated README.md (which, after adding the / handler, we could change to something else again), with how to add the bot to your Discord server, including the permissions (that I think) it needs.

No longer catch exceptions for critical failures (closes #6)

Fixes https://github.com/Stixxl/HydraBot/projects/1#card-5355663


Code style vpn_l2tp

Just a note, PPTP is going to be removed on 2.3, then please do not waste your time touching those files. You are doing an awesome job here, thanks!


Disallow public module level variables

Purpose
According to the "Module variable declaration" section of the spec, module level variables cannot be public.
module-var-decl :=
   metadata
   [final]
   typed-binding-pattern = expression ;

"The scope of variables declared in a module-var-decl is the entire module. Note that module variables are not allowed to be public."
This PR disallows marking module level variables as public. Getters/setters are introduced where applicable in tests.
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/13619

Codecov Report

Merging #14032 into master will decrease coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master   #14032      +/-   ##
============================================
- Coverage     64.56%   64.51%   -0.05%
+ Complexity      426      425       -1
============================================
  Files          2156     2156
  Lines         95554    95551       -3
  Branches      12744    12742       -2
============================================
- Hits          61697    61648      -49
- Misses        28843    28875      +32
- Partials       5014     5028      +14

Impacted Files
Coverage Δ
Complexity Δ

...erinalang/compiler/parser/BLangPackageBuilder.java
89.71% <ø> (-0.01%)
0 <0> (ø)

...erinalang/compiler/parser/BLangParserListener.java
68.64% <100%> (-1.34%)
0 <0> (ø)

...t/ParserRuleFunctionDefinitionContextResolver.java
62.26% <0%> (-18.87%)
0% <0%> (ø)

...g/compiler/tree/expressions/BLangSimpleVarRef.java
90.24% <0%> (-4.88%)
0% <0%> (ø)

...rinalang/runtime/threadpool/ThreadPoolFactory.java
61.9% <0%> (-4.77%)
0% <0%> (ø)

...java/org/ballerinalang/bre/bvm/BLangVMStructs.java
48.33% <0%> (-3.34%)
0% <0%> (ø)

...va/org/ballerinalang/util/codegen/PackageInfo.java
83.15% <0%> (-2.11%)
0% <0%> (ø)

...ain/java/org/ballerinalang/net/websub/hub/Hub.java
69.53% <0%> (-1.57%)
0% <0%> (ø)

.../java/org/ballerinalang/bre/bvm/BLangVMErrors.java
73.95% <0%> (-1.05%)
0% <0%> (ø)

... and 8 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a058720...4abe517. Read the comment docs.


[locale] de, de-at, de-ch: add german translation for week

Issue: when adjusting thresholds for humanize, Moment.js displays english version for 'week' only
For example:
moment.locale('de');
moment.duration(604800000).humanize({ h: 24, d: 7, w: 4 });  // 604800000 = 7 days

results to:
'a week'

instead of
'eine Woche'

This works for days, hours, etc. but not for weeks.
This PR adds translation for 'week' in german locales for relative time formats to address this issue.
Original author of languages: @lluchs

Coverage decreased (-0.01%) to 88.469% when pulling 00a3af77d53d360ea91333f1f8637f22ded4df55 on carlmrichter:add-german-week-translation into 1872bb22ff6cd19c56e7dc30c5765489d48e65f1 on moment:develop.

@carlmrichter  - thank you for this PR. Could you also add some tests?
@Oire can you review this?

or @sschueller can you review?

@carlmrichter - thank you for this PR. Could you also add some tests?

@marwahaha I hope the last commit is what you're looking for. I found no tests for duration.humanize's thresholds at all, even in en locale ...

This is great!


Minimal LSP support

It seems that unification efforts (e.g. https://github.com/lassik/emacs-format-all-the-code/issues/4) stalled a bit. I'd like to propose (and kindly ask to be implemented, since my elisp is basically non-existent) a minimal solution for LSP integration inside format-all-the-code which would make my developer life a bit more consistent.
I'd imagine it'd work this way:

If lsp-mode is not enabled for the current buffer, fallback to the current behaviour.
Otherwise, check for textDocument/formatting capability of the current language server (or maybe servers, since that's apparently a supported workflow). If it's not available, fallback to current behaviour.
Otherwise, use textDocument/formatting (probably via lsp-format-buffer) instead of the predefined tool.

Does this sound sensible and would you consider this for format-all-the-code?

Thanks for bringing LSP to our attention. Sounds sensible to support it in format-all, but I know almost nothing about it so I don't know what the best approach is. lsp-format-buffer could be the right thing. I'm a bit swamped with other projects right now...

That's only fair, more reason for me to dive into elisp :)
However, I've looked into code and noticed that doom-emacs, which I'm a user of, does quite a bit of wrapping around format-all. Might be a better idea to check for LSP in the doom-emacs auto-formatter and leave format-all as it is.
@hlissner: what do you think?

Either approach is fine with me. However, format-all is designed to work with bare Emacs for all users.
How does LSP work from a user's standpoint? Is there a separate server (command line program) for each language (or group of languages), and Emacs commands to start them in the background and connect them to Emacs?

Yes, exactly, there is protocol (https://microsoft.github.io/language-server-protocol/), so that a single editing mode can communicate with a range of so-called "language servers". One of the commands is textDocument/formatting which asks the language server to format code (whole buffer, snippet, etc., depending on language server's capabilities).


Drop /infowindow endpoint from API

Not used anymore (since version ?)
See also #101

Will be removed with https://github.com/CartoDB/Windshaft-cartodb/issues/257


Shell activation workflow makes everything slow down?

Hi, thanks for making a great tool.
But I noticed that shell activation workflow makes everything slow down.
I'm using zsh. So I followed the instructions.
https://moonrepo.dev/docs/proto/commands/activate#zsh
Then, I ran echo "hello", it took over 200 ms.
When I removed shell activation, it only took about 20 ms.
That is a huge difference. 🥲

@asapo Does it happen every time? There will be an initial hit when you need to download the WASM plugins.
If you add PROTO_LOG=trace to your shell, you can see what's taking long.

Does it happen every time?

Yes, it happens every time.

If you add PROTO_LOG=trace to your shell, you can see what's taking long.

I'm not sure how can I read correctly but...
Small one:
[TRACE 10:57:12.534] starbase::app  Running shutdown phase
[DEBUG 2024-07-16 10:57:12.545] proto  Running proto v0.38.2  bin="proto" args=["activate", "zsh", "--export"] pid=29980

Another small one:
[DEBUG 10:57:12.547] proto_core::tool  Creating tool npm and instantiating plugin
[TRACE 10:57:12.562] warpgate::plugin  Created plugin container  id="go"

This one seems big:
[DEBUG 10:49:47.392] proto_core::tool  Located possible globals directories  tool="pnpm" dirs=["/Users/user/.local/share/pnpm", "/Users/user/Library/pnpm", "/Users/user/.proto/tools/node/globals/bin"]
[TRACE 10:49:47.523] proto_core::version_detector  Attempting to find version from .prototools files  tool="deno"

Making some changes here https://github.com/moonrepo/proto/pull/557

Made some improvements in v0.39, can you give it a shot?

Thank you!
I tried proto 0.39.1 and it works faster as without proto. 🙌

Awesome!


Using NVMe storage appears to fail in v6.0.0

Describe the bug
We just upgraded from 5.16 to 6.0 and our jobs fail shortly after they begin.
Steps To Reproduce
Steps to reproduce the behavior:

Set up the stack with m5dn.large instances and enable EnableInstanceStorage
Run a job
Jobs fail with a message like this:

Setting up elastic stack environment (v6.0.0) | 0s
-- | --
  | Checking docker
  | CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES
  | Checking disk space
  | df: /mnt/ephemeral/docker: No such file or directory
  | Cleaning up docker resources older than 4h
  | Total reclaimed space: 0B
  | Checking disk space again
  | df: /mnt/ephemeral/docker: No such file or directory
  | Disk health checks failed

Expected behavior
In v5 we were able to use NVMe storage on these instance types with the EnableInstanceStorage setting.
Actual behaviour
Jobs fail at the disk health check phase
Stack parameters (please complete the following information):

AWS Region: us-east-2
Version v6.0.0
instance types: m5dn.large
EnableInstanceStorage: true
RootVolumeEncrypted: true

Additional context
Add any other context about the problem here.

I can confirm this is a bug - I built my own AMI with the following and the boxes came up.
echo 'mkdir -p /mnt/ephemeral/docker' | sudo tee -a /usr/local/bin/bk-mount-instance-storage.sh

Thanks for reporting this @geoffharcourt and @joemiller. And huge props to @mpestritto for finding a fix 💖
We will get this out with the next version.

I am still seeing failures at boot on new nodes with instance storage enabled. Is it just me, or are others still seeing this too?

@joemiller If you can send us the parameters you are setting on the stack, and some cloudwatch logs, especially from the log group /buildkite/elastic-stack/<instance-id>. You can send these to<EMAIL_ADDRESS>if there are sensitivity concerns.

@triarius sure, I can't do it at the moment but should be able to get that info tomorrow

@triarius thanks for the hint about the cloudwatch path. I found this:
/usr/local/bin/bk-mount-instance-storage.sh: line 32: mdadm: command not found


Meta package goals

if we're doing this metapackage thing?

Originally posted by @asinghvi17 in https://github.com/JuliaGeo/JuliaGeo.jl/issues/1#issuecomment-2438442281

I'd say this will at least help with (first) installations, and getting up to speed in tutorials.
When re-exporting, we'd have to make sure there are no clashes
This might also be a nice testing ground for combined tests/tutorials.
?

What level of tutorial are we pushing this at?  I'd almost be tempted to not put it in the geocompx book, and if we can get all the needed imports into Rasters and GeometryOps (Extents, GeoFormatTypes, etc), the only purpose of this package would be to load backends.
To restate - the clashes are GeoJSON between GeoFormatTypes and GeoJSON, coverage, rebuild, reproject between GeometryOps and Rasters, and union, intersection` between Extents and GeometryOps.

Some of these definitions can be folded into each other - the only true issue might be Rasters coverage.

After converting some terra code I've come around to Geo.func being better than Rasters/|GeometryOps/GeoDataFrames.func for explaining things to beginners, because its hard to know which package does what.
geocompx could start with just using Geo for an easy introduction, then transition to using specific packages where only one is needed. We can have both the easy syntax for beginners and just using the tool you need for more advanced users.


Check if smart-guess algorithm is working correctly

It appears that at least for some (most? all?) people no categories are guessed (except commute, but this is a special case).
We have to investigate and figure out what is going on with this. If there is a bug, fix it. If there is not, let's see if we can improve it somehow (without unreasonable effort) to work better again.

I've added some more logging to the app, let's see where that gets us.

After looking at this a lot, I don't think there's anything wrong with the code itself. The problem is in the logic we use to handle smart guesses. For the amount of guesses I usually have (around 20) it's not easy to find one 5 hours away within a week from a given new time slot.
This will be probably fixed with #657 or #651. So I would close this for now.
I'm thinking, maybe we should also include some default smart guesses. For example: For almost everybody (except Paul) breakfast is around 8:30.


Clangd doesn't work in files without an extension

Given a file named no_extension with the contents of int x = 5;, upon didOpen there's an error saying Could not build CompilerInvocation for file /home/bstaletic/Temp/sparsehash-c11/no_extension. hover response is {"error":{"code":-32001,"message":"invalid AST"},"id":"2","jsonrpc":"2.0"} and completion response is {"id":"3","jsonrpc":"2.0","result":{"isIncomplete":false,"items":[]}}.
The complete clangd log:
V[21:59:09.337] <<< {"id":"1","jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"textDocument":{"completion":{"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}}}},"initializationOptions":{},"processId":4848,"rootPath":"/home/bstaletic/Temp/sparsehash-c11","rootUri":"file:///home/bstaletic/Temp/sparsehash-c11"}}

I[21:59:09.337] <-- initialize("1")
I[21:59:09.337] --> reply:initialize("1") 0 ms
V[21:59:09.337] >>> {"id":"1","jsonrpc":"2.0","result":{"capabilities":{"codeActionProvider":true,"completionProvider":{"resolveProvider":false,"triggerCharacters":[".",">",":"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"}","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"hoverProvider":true,"referencesProvider":true,"renameProvider":true,"signatureHelpProvider":{"triggerCharacters":["(",","]},"textDocumentSync":2,"workspaceSymbolProvider":true}}}

V[21:59:09.338] <<< {"jsonrpc":"2.0","method":"initialized","params":{}}

I[21:59:09.338] <-- initialized
I[21:59:09.338] unhandled notification initialized
V[21:59:09.338] <<< {"jsonrpc":"2.0","method":"workspace/didChangeConfiguration","params":{"settings":{}}}

I[21:59:09.338] <-- workspace/didChangeConfiguration
V[21:59:09.339] <<< {"jsonrpc":"2.0","method":"textDocument/didOpen","params":{"textDocument":{"languageId":"cpp","text":"auto x = 5;\n","uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo","version":1}}}

I[21:59:09.339] <-- textDocument/didOpen
I[21:59:09.340] Updating file /home/bstaletic/Temp/sparsehash-c11/foo with command [/home/bstaletic/Temp/sparsehash-c11/build/tests] /usr/sbin/clang++ -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/. -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3 -c /home/bstaletic/Temp/sparsehash-c11/foo -resource-dir=/usr/lib/clang/9.0.0
V[21:59:09.343] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wall'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-c'
V[21:59:09.343] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[21:59:09.343] Could not build CompilerInvocation for file /home/bstaletic/Temp/sparsehash-c11/foo
V[21:59:13.216] <<< {"id":"2","jsonrpc":"2.0","method":"textDocument/hover","params":{"position":{"character":5,"line":0},"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo"}}}

I[21:59:13.217] <-- textDocument/hover("2")
V[21:59:13.220] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-Wall'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-c'
V[21:59:13.221] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
I[21:59:13.221] --> reply:textDocument/hover("2") 4 ms, error: invalid AST
V[21:59:13.221] >>> {"error":{"code":-32001,"message":"invalid AST"},"id":"2","jsonrpc":"2.0"}

V[22:10:25.890] <<< {"jsonrpc":"2.0","method":"textDocument/didChange","params":{"contentChanges":[{"text":"auto x = 5;\n\n"}],"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo","version":2}}}

I[22:10:25.890] <-- textDocument/didChange
V[22:10:25.892] <<< {"id":"3","jsonrpc":"2.0","method":"textDocument/completion","params":{"position":{"character":0,"line":1},"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo"}}}

I[22:10:25.892] <-- textDocument/completion("3")
V[22:10:25.896] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wall'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-c'
V[22:10:25.896] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[22:10:25.896] Couldn't create CompilerInvocation
I[22:10:25.896] Code complete: 0 results from Sema, 0 from Index, 0 matched, 0 returned.
I[22:10:25.896] --> reply:textDocument/completion("3") 4 ms
V[22:10:25.896] >>> {"id":"3","jsonrpc":"2.0","result":{"isIncomplete":false,"items":[]}}

I[22:10:26.392] Updating file /home/bstaletic/Temp/sparsehash-c11/foo with command [/home/bstaletic/Temp/sparsehash-c11/build/tests] /usr/sbin/clang++ -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/. -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3 -c /home/bstaletic/Temp/sparsehash-c11/foo -resource-dir=/usr/lib/clang/9.0.0
V[22:10:26.396] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wall'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-c'
V[22:10:26.396] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[22:10:26.396] Could not build CompilerInvocation for file /home/bstaletic/Temp/sparsehash-c11/foo

Note: Providing a different compile_commands.json or even removing one completely doesn't change the behaviour at all.

It looks like inferred compile commands is missing the language
option(-xc++/header) for files without extensions
Could you also provide compile commands.json?
On Mon, Feb 18, 2019, 10:14 PM Boris Staletic<EMAIL_ADDRESS>wrote:

Given a file named no_extension with the contents of int x = 5;, upon
didOpen there's an error saying Could not build CompilerInvocation for
file /home/bstaletic/Temp/sparsehash-c11/no_extension. hover response is {"error":{"code":-32001,"message":"invalid
AST"},"id":"2","jsonrpc":"2.0"} and completion response is
{"id":"3","jsonrpc":"2.0","result":{"isIncomplete":false,"items":[]}}.
The complete clangd log:
V[21:59:09.337] <<< {"id":"1","jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"textDocument":{"completion":{"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]}}}},"initializationOptions":{},"processId":4848,"rootPath":"/home/bstaletic/Temp/sparsehash-c11","rootUri":"file:///home/bstaletic/Temp/sparsehash-c11"}}
I[21:59:09.337] <-- initialize("1")
I[21:59:09.337] --> reply:initialize("1") 0 ms
V[21:59:09.337] >>> {"id":"1","jsonrpc":"2.0","result":{"capabilities":{"codeActionProvider":true,"completionProvider":{"resolveProvider":false,"triggerCharacters":[".",">",":"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"}","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"hoverProvider":true,"referencesProvider":true,"renameProvider":true,"signatureHelpProvider":{"triggerCharacters":["(",","]},"textDocumentSync":2,"workspaceSymbolProvider":true}}}
V[21:59:09.338] <<< {"jsonrpc":"2.0","method":"initialized","params":{}}
I[21:59:09.338] <-- initialized
I[21:59:09.338] unhandled notification initialized
V[21:59:09.338] <<< {"jsonrpc":"2.0","method":"workspace/didChangeConfiguration","params":{"settings":{}}}
I[21:59:09.338] <-- workspace/didChangeConfiguration
V[21:59:09.339] <<< {"jsonrpc":"2.0","method":"textDocument/didOpen","params":{"textDocument":{"languageId":"cpp","text":"auto x = 5;\n","uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo","version":1}}}
I[21:59:09.339] <-- textDocument/didOpen
I[21:59:09.340] Updating file /home/bstaletic/Temp/sparsehash-c11/foo with command [/home/bstaletic/Temp/sparsehash-c11/build/tests] /usr/sbin/clang++ -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/. -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3 -c /home/bstaletic/Temp/sparsehash-c11/foo -resource-dir=/usr/lib/clang/9.0.0
V[21:59:09.343] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wall'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:09.343] Ignored diagnostic. argument unused during compilation: '-c'
V[21:59:09.343] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[21:59:09.343] Could not build CompilerInvocation for file /home/bstaletic/Temp/sparsehash-c11/foo
V[21:59:13.216] <<< {"id":"2","jsonrpc":"2.0","method":"textDocument/hover","params":{"position":{"character":5,"line":0},"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo"}}}
I[21:59:13.217] <-- textDocument/hover("2")
V[21:59:13.220] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-Wall'
V[21:59:13.220] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-O3'
V[21:59:13.221] Ignored diagnostic. argument unused during compilation: '-c'
V[21:59:13.221] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
I[21:59:13.221] --> reply:textDocument/hover("2") 4 ms, error: invalid AST
V[21:59:13.221] >>> {"error":{"code":-32001,"message":"invalid AST"},"id":"2","jsonrpc":"2.0"}
V[22:10:25.890] <<< {"jsonrpc":"2.0","method":"textDocument/didChange","params":{"contentChanges":[{"text":"auto x = 5;\n\n"}],"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo","version":2}}}
I[22:10:25.890] <-- textDocument/didChange
V[22:10:25.892] <<< {"id":"3","jsonrpc":"2.0","method":"textDocument/completion","params":{"position":{"character":0,"line":1},"textDocument":{"uri":"file:///home/bstaletic/Temp/sparsehash-c11/foo"}}}
I[22:10:25.892] <-- textDocument/completion("3")
V[22:10:25.896] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wall'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:25.896] Ignored diagnostic. argument unused during compilation: '-c'
V[22:10:25.896] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[22:10:25.896] Couldn't create CompilerInvocation
I[22:10:25.896] Code complete: 0 results from Sema, 0 from Index, 0 matched, 0 returned.
I[22:10:25.896] --> reply:textDocument/completion("3") 4 ms
V[22:10:25.896] >>> {"id":"3","jsonrpc":"2.0","result":{"isIncomplete":false,"items":[]}}
I[22:10:26.392] Updating file /home/bstaletic/Temp/sparsehash-c11/foo with command [/home/bstaletic/Temp/sparsehash-c11/build/tests] /usr/sbin/clang++ -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/. -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3 -c /home/bstaletic/Temp/sparsehash-c11/foo -resource-dir=/usr/lib/clang/9.0.0
V[22:10:26.396] Ignored diagnostic. /home/bstaletic/Temp/sparsehash-c11/foo: 'linker' input unused
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/.'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-I /home/bstaletic/Temp/sparsehash-c11/tests/.'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wall'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wextra'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wpedantic'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-Wno-missing-field-initializers'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-D NDEBUG'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-O3'
V[22:10:26.396] Ignored diagnostic. argument unused during compilation: '-c'
V[22:10:26.396] Ignored diagnostic. unable to handle compilation, expected exactly one compiler job in ''
E[22:10:26.396] Could not build CompilerInvocation for file /home/bstaletic/Temp/sparsehash-c11/foo
Note: Providing a different compile_commands.json or even removing one
completely doesn't change the behaviour at all.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/clangd/clangd/issues/16, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2yE7otIddrFHrc2EDLZQWDdk_5o7fdks5vOxfRgaJpZM4bBnnT
.

[
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/bench.dir/bench.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/bench.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/bench.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/testmain.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/testmain.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/testmain.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/sparsetable_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/sparsetable_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/sparsetable_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/simple_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/simple_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/simple_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/hashtable_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/hashtable_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/hashtable_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/hashtable_c11_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/hashtable_c11_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/hashtable_c11_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/fixture_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/fixture_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/fixture_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/sparsehash_unittests.dir/allocator_unittests.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/allocator_unittests.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/allocator_unittests.cc"
},
{
  "directory": "/home/bstaletic/Temp/sparsehash-c11/build/tests/gtest",
  "command": "/usr/sbin/clang++   -I/home/bstaletic/Temp/sparsehash-c11/. -I/home/bstaletic/Temp/sparsehash-c11/tests/.   -std=c++11 -Wall -Wextra -Wpedantic -Wno-missing-field-initializers -O3 -DNDEBUG -O3   -o CMakeFiles/gtest.dir/gmock-gtest-all.cc.o -c /home/bstaletic/Temp/sparsehash-c11/tests/gtest/gmock-gtest-all.cc",
  "file": "/home/bstaletic/Temp/sparsehash-c11/tests/gtest/gmock-gtest-all.cc"
}
]

Not clear to me whether files without extension that aren't in the CDB should be parsed with a fallback command (probably -x objective-c++) or ignored somehow, assuming they're plain text.
Regardless, the current behavior is clearly broken.

Ycmd has been blindly setting -xc++ for those files and it has worked for us. Ignoring isn't a good option, because it would stop users (including me) from navigating inside STL headers.

Fixed in r360153.
The change is that:

when there is a compilation database governing a file (found in ancestor dir or via flag)
and the file is not in the compilation database
and the file has no recognized extension
and we heuristically match it against some other file in the CDB, and use its compile command
then we'll add the -x flag from the other file (using the -header variant)

The case where there is no governing database, or we fail to heuristically match it, should have been working already, using the fallback command with -x objective-c++. The case where the extension is recognized should have already been adding -x where appropriate.

I have similar issue but with files having a .inl extension. I am getting the same invalid AST message from lsp. I am pretty sure thats because clangd can't find flags and isn't compiling the file. I have been searching for a solution to this but haven't found anything yet. I have tried adding flags via compile_flags.txt but I think clangd is not considering .inl a valid source file.
Sorry lots of speculation here but I hope someone more knowledgeable would know more.

Try adding an explicit language flag (-x<language>).

I am not invoking clangd manually so can't test this directly but since I am using lsp-mode I have tried (setq lsp-clients-clangd-args '("-j=4" "-background-index" "-log=error" "-xc++")) and this isn't working. Is that what you meant?

.inl is not considered a cpp extension by default on clang, you can find the list in https://github.com/llvm/llvm-project/blob/master/clang/lib/Driver/Types.cpp#L194 and send a quick patch explaining your reasoning why it should be considered as a cpp file. Then it will automatically get picked up by most of clang-based tools including clangd.
Otherwise you need to specify it manually within your compile commands container( compile_commands.json/compile_flags.txt/ycm_extra_conf). Make sure -xc++ flag is stated before file name otherwise it has no effect.

Thanks for the link I looked into this and for now I can get away with using .hh instead. I am trying to gather some reasoning for .inl and will submit an MR if I can justify it to myself. One of the problems with using .inl the way I am is that these are not complete translation unit so even if clang recognises it, it doesn't solve the problem. clangd still can't build it. So I had to include .hpp in .inl which is gross. By using .hh mean it comes early in the company suggestions which is annoying me :). .inl doesn't have that issue.


encoding: null is a hard-to-find trick when response body is not utf-8

Hi,
i am requesting some xml file encoded in iso-8859-1 and have to go through this
var icon = require('iconv-lite');
request({url: myurl, encoding: null}, function(err, res, body) {
  var str = iconv.decode(body.toString('binary'), 'Latin1');
  // do stuff with utf-8 string
});

to convert it to utf-8.
The encoding: null thing is particularly tricky !
Don't you think request API should be more explicit ?

Definitely, it's not user friendly IMO. Any suggestions on improving it are greatly appreciated.


Binding Element to Starting Point for Animation

Hey there!
This is probably a dull question, but I was mocking up a CodePen for a blog post, started muddling around with mojs for awhile(I may have gotten a little sidetracked, haha), and while tinkering I was wondering if there was a way to bind an animation to a specific element? As in just to designate a start point always from that element, wherever it may be.
http://codepen.io/zfrisch/pen/YpvbZE?editors=1010
In the code I created a helper object to do this with methods that would return the coordinates of whatever Pokemon and then just tuned the coordinates to the left and top properties when I started the animations, but I wasn't sure if there was a built-in way to do this.

Hi, Zak!
Thanks for the issue, awesome effects! I think you did it right, you have the animation and tune the animation to coordinates whatever your object is currently at.
Another approach is to use parent property that expects an HTMLElement that your effect will be placed in, so you might want to wrap your <img />s with an  inline-block and position: relative element and send it to the parent property of the effect demo. Of course, with this approach, you will have two instances of the same effect instead of one that you have and reuse right now, but you can make a helper function that will bootstrap the effect for you and return the object back. demo.
Hope it helps, please let me know if you have any questions.
Cheers! // @zfrisch

Excellent! I was looking at the parent property but wasn't positive how to use it. The demo made it super clear! Thank you for being so responsive!
By the way, awesome work on this library so far! I'm not a pro at SVG graphics, but mojs feels very natural to work with!

Happy to help! Thanks for the kind feedback and your support! 👍  🎉


Reload codebase from within console instance

Would be great to be able to keep all the variables that have been set but reload the code in place.

Hey Samuel - this is a good suggestion, and we'll see if we can get it included.

Hey @gausie - spent some time thinking about this but have come to feel that such a reload (while maintaining console state) is probably unrealistic. It would be difficult to ensure that local variables that point to model instances (and other LB components) got reloaded with the new code. It's possible to do in a poor way but complex to do comprehensively. Sorry about this!


 Refs #62.

This looks pretty good. Could you (1) add your Signed-off-by: Name  to the commit messages and (2) add a couple unit tests for the new interfaces (see https://github.com/ceph/go-ceph/blob/master/rbd/rbd_test.go)?

https://travis-ci.org/ceph/go-ceph/jobs/429766070#L2393
looks like -EPERM. There is an option in ceph that allows pools to be deleted which is off by default. I wonder if there is such an option for rbd?

Need to force removal from trash if the deferment time has not expired yet ;-)


Connector cli: command to clean old Nango connections

Part of: https://github.com/dust-tt/tasks/issues/258
Cli command to remove the connectionId if we don't have a matching SlackConfiguration in db.
Note: Nango does not offer a way to filter the list of connections: https://docs.nango.dev/api-reference/connection/list, so I'm manually filtering them for Slack. This is probably not sustainable on the long term, and I'm not even sure this will be okay with the current number of connections but let's try and find a plan B if needed.

Also I asked about paginating this endpoint on their Slack community channel.
Conversation is here: https://nango-community.slack.com/archives/C04ABR352H0/p1701095836255929

Agreed on higher priority of conversation rendering :+1:

@lasryaric I answered your questions, I think code should be shipped as is for both 🙏🏻

(Merging but won't run it until I shipped the Production check)


Catch em all

Extends the do catch construct to catch all run time errors.
The interpreter also keep the error information if one wants it.

reroll: spell


Mismatched colors

Hello, my terminal is xterm, why is this effect
I tried to use the default settings of the terminal, and the default settings of the theme, but still this effect

Hello, my terminal is xterm, why is this effect I tried to use the default settings of the terminal, and the default settings of the theme, but still this effect

What effect are you talking about? Everything looks ok


Reflect arr rename to list.

Replace all occurrences of arr.eval and arr().eval to list.eval and list().eval.

Thank you @avimallu


Support enum-like objects with numeric literal values

Search terms
enum, enum-like object
Problem
TypeDoc already supports enum-like objects with string literal values via #1675 and #1740. However, enum-like objects with numeric literal values are not supported. For the following code example:
// index.d.ts

/**
 * This enumeration defines some values.
 *
 * @enum
 */
export declare const SomeStringLiteralEnum: {
    /**
     * This is the auto property.
     */
    readonly AUTO: "auto";
    /**
     * This is the manual property.
     */
    readonly MANUAL: "manual";
};

/**
 * This enumeration also defines some values.
 *
 * @enum
 */
 export declare const SomeNumericLiteralEnum: {
    /**
     * This is the auto property.
     */
    readonly AUTO: 0;
    /**
     * This is the manual property.
     */
    readonly MANUAL: 1;
};

TypeDoc will document SomeStringLiteralEnum as an enum and SomeNumericLiteralEnum as a variable:

Suggested Solution
Support enum-like objects with numeric literal values in the same way as those with string literal values. I think it would only require some minor changes in src/lib/converter/symbols.ts.

If this is something we'd like to support in TypeDoc, I'd be happy to contribute this feature - I've already done some tinkering in the source code. :)


Make iterating MVP fast and easy.  Make it simple to keep what works, discard the rest.
Don't care about tech debt, architectural vision or consistency
Do care about automation and minimum levels of testing/quality - make it hard to merge bad style.

Year 5 (50-200 engineers / 100s customers):

Stabilise / standardise / collaborate
Never do the big rewrite.  Shadow & replace.
Pay down tech debt before it drowns you

Year 6+ (>150 engineers / 1000s customers):

Maintain vision / collaborate
Remove / refactor the major bottlenecks


Added a rule of implicit getters

@ThibaultKlein @paulmiard
Good rule inherited from GitHub. I've taken this approach, and I highly recommend it.

:+1:

bump @paulmiard

:+1:


permute function in convert_hf_checkpoint.py

The convert_hf_checkpoint.py replaces wq, wk and wv with single wqkv. I am confused about the purpose of permute function in the creation of wqkv. Current implementation of wqkv creation does not give same result as individual projections as tested below:
import torch

dim = 12
n_head = 3
n_local_heads = 3
head_dim = 12 // 3
wq = torch.randn(dim, dim)
wk = torch.randn(dim, dim)
wv = torch.randn(dim, dim)
inputs = torch.randn(10, dim)

def permute(w, n_head):
    return (
        w.view(n_head, 2, head_dim // 2, dim)
        .transpose(1, 2)
        .reshape(head_dim * n_head, dim)
    )

wq_p = permute(wq, n_head)
wk_p = permute(wk, n_local_heads)
wqkv = torch.cat([wq_p, wk_p, wv])  #as implemented at line 112

# projecting separately (as in original llama)
q_o = inputs @ wq.T

# projecting collectively (as in fast-gpt)
kv_size = n_local_heads * head_dim
q_f, k_f, v_f = (inputs @ wqkv.T).split([dim, kv_size, kv_size], dim=-1)

assert (q_o == q_f).all()

Hi @Sohaib9920 could you share the reason to permute only k and q? I'm also confused here, thank you!

@yuanzhedong
Hugging face checkpoints permute the wq and wk of original checkpoints such that if num_heads = 2 and head_dim = 4 then projected q and k using the permuted wq and wk will have embeddings with order [1,3,2,4 , 5,7,6,8] instead of [1,2,3,4 , 5,6,7,8] because hf rotary implementation has embeds per head represented as [all x1 = (1,3) , all x2 = (2,4)]. We need to permute back to the original weights such that embeds of each head are [1,2,3,4] and not [1,3,2,4] as required by original rotary implementation.
You can get this info from huggingface docs under usage tips which provide conversion script in which weights are permuted to get HF weights. So we need to permute back to original weights.

@yuanzhedong Hugging face checkpoints permute the wq and wk of original checkpoints such that if num_heads = 2 and head_dim = 4 then projected q and k using the permuted wq and wk will have embeddings with order [1,3,2,4 , 5,7,6,8] instead of [1,2,3,4 , 5,6,7,8] because hf rotary implementation has embeds per head represented as [all x1 = (1,3) , all x2 = (2,4)]. We need to permute back to the original weights such that embeds of each head are [1,2,3,4] and not [1,3,2,4] as required by original rotary implementation.
You can get this info from huggingface docs under usage tips which provide conversion script in which weights are permuted to get HF weights. So we need to permute back to original weights.

Thank you! That make a lot of sense now!


Add Option to set Cache Directory for po_token_verifier

Is your feature request related to a problem? Please describe.
Using the po_token_verifier option on servless hosting platforms, may cause an error due to read-only file-system limitations.
Currently, when using this option, pytubefix stores the provided information (poToken + visitorData) in a cache directory, which may not be writable.
Describe the solution you'd like
It would be helpful to allow users to set the cache directory path via an additional argument, providing more flexibility and avoiding issues with unwritable file systems (eg. using '/tmp' directory instead, which is allways writable).
Example:
from pytubefix import YouTube

yt = Youtube(cache_dir="/path/to/cache")

Related Code-Section in Repository:
innertube.py - Cache Variable: _cache_dir

Nevermind, the token_file options is already available!


[#8] added configurable line separator option to AT_Context

Solves #8 by adding a configurable line separator String to AT_Context.
The new field AT_Context.lineSeparator replaces the hardcoded one in AsciiTable and AT_Rendeder.
Naturally this needs to be a String instead of char, because MsWin would use \r\n.
The default separator is \n to stay compatible with previous versions.

I have changed the table context and the renderer to use line separator. This had implications to the render methods on table and renderer. Thus now (new version on master), the render method names are harmonized, table context has configurable member for separator (default null), renderer has configurable member for line separator (default null).
This means that there are 4 possible variations of line separator:

context null & renderer null -> System.getLineSeparator()
context != null & renderer null -> context
context null & renderer != null -> renderer
context !=null & renderer != null -> renderer

So the renderer overwrites context, if both null then system default. This way the renderer has the final control but the table can recommend a value. If user doesn't care, system default will be used.
See if new version solves your problem (I also needed to update the sister repos for asciilist and asciiparagraph, thus is took a while, sorry for that!)
/sven

Works fine, thanks for the release.

Thanks for the new feature :)