Test on MacOS Big Sur and Monterey

I have Big Sur 11.7.9 installed on a daily driver with a lot of Notes.  If you want any help with testing on that OS version.  Let me know if I can help.

@chadmando thanks! I'm working on another project at the moment but want to get back to macnotesapp soon as I've got some things I want to implement. Will definitely appreciate the help testing.

I walked through the tests this morning using pytest -v -s tests/ using python 3.11 on Big Sur.  The only failures that I see all relate to Note count/length.  The test's counts were all +2 greater than the Notes app's counts. This included both collectively (iCloud + On My Mac) and the iCloud only count.  I didn't see the On My Mac count to determine if it was something only related to the iCloud count.
Disclaimer: I have been moving a LOT of notes from Evernote to Notes app and I have found some "dead notes" in that process as I add them to iCloud.  I will walk through my most recent imports and double check all are valid.
failed tests for reference:
=============================================================== short test summary info ================================================================
FAILED tests/test_applescript_interface.py::test_notes_len - AssertionError: assert False
FAILED tests/test_applescript_interface.py::test_notes_notes - AssertionError: assert False
FAILED tests/test_applescript_interface.py::test_notes_generator - AssertionError: assert False
FAILED tests/test_applescript_interface.py::test_account - AssertionError: assert False
================================================= 4 failed, 19 passed, 1 skipped in 945.97s (0:15:45) ==================================================

Thank you for taking time to do this!  On the note counts, did you include "Recently Deleted"? Those are part of the overall count. On Ventura my counts match when including Recently deleted (and any other accounts, like Google, that have notes enabled).
If your counts are still off with recently deleted I'll take a look to see if I can debug this. I don't have access to Big Sur but do have a Monterey virtual machine I can use.

@all-contributors please add @chadmando for user testing

Thank you for taking time to do this! On the note counts, did you include "Recently Deleted"? Those are part of the overall count. On Ventura my counts match when including Recently deleted (and any other accounts, like Google, that have notes enabled).
If your counts are still off with recently deleted I'll take a look to see if I can debug this. I don't have access to Big Sur but do have a Monterey virtual machine I can use.

Good call.  It was the Recently Deleted causing my confusion.  Counts match when I include those.

@RhetTbull have you tested on Sonoma? I have access to Sonoma and can test sometime in the near future.

@chadmando I've tested on the Sonoma beta which I installed in a VM and everything works fine. I'd welcome test feedback from the released version of Sonoma. On my two personal Macs I tend to lag 1 major version.  I've now got an M1 Mini and virtualization works well on the Apple Silicon so I've been able to create VMs for additional testing.


Animation : Citrine poses for website

Need about 50 poses for website , all poses should have transparent background for easier web development.

Maybe like 30 tops.
I think we have enough material in the assets/poses directory: https://github.com/webaverse/assets/tree/master/poses

About 17 poses made, currently in gdrive - is that the best place?

https://drive.google.com/drive/folders/1AlBtFqtQdEl8QjZgzQDrv76Mw0CVUKJm also the face / pose matrix directories

Are the poses saved in the blend?

just uploaded the blend file in the poses directory , above link


Group identify is not working

The group tracking (assigning a group, group properties) does not add data to the events in Amplitude.
Expected Behavior
The following code should add data to groups and group_properties field of tracked events, but it does not do that.
amplitude.setGroup('Workspace', workspaceId)
const groupIdentity = new amplitude.Identify()
groupIdentity.set('workspaceId', workspaceId)
amplitude.groupIdentify('Workspace', workspaceId, groupIdentity, {
  user_id: userId,
})

amplitude.track('CTA click', eventProperties, {
  user_id: userId,
})

Current Behavior
Since this new library is finally something for JS/Node that has implicitly documented group behavior, I thought it will work better or be less verbose than the older libraries. It turns out there is no group info getting to amplitude. Is there anything that I am missing?
There is nothing in groups and group properties in raw event data:

There is no Group name (Group Type) in Account lookup

Possible Solution
I don't know the culprit here, the whole group identity setup is pretty complex, all Amplitude client libraries do it differently, Segment does it differently. I am not sure if the mistake here is just in how the API is being called or there is some functionality not implemented yet.
Steps to Reproduce

Run the code above.
Check raw event data in amplitude.

Environment

JS SDK Version: 0.4.0
Installation Method: Yarn (3)
Browser and Version: Brave 1.42.88

Hi @jakubzitny  Thank you for reporting bug. I'll look into it.

@jakubzitny Just want to confirm, Did your org purchas account add-on? Group and Group properties are features that need to enable by account add-on.

Yes, of course @bohan-amplitude. Thanks for looking into this.

Hi @jakubzitny, wanted to reach out to you with regards to this issue. I am now seeing through your account that you have been able to instrument group and group properties to amplitude using the Node SDK. Is this an accurate? Feel free to share any findings you had with regards to this issue and also let us know if there are any other support we can provide. Thank you so much.


CSS and Performance Improvement

At the moment, recommended way of importing styles of this library is by literally linking to the compiled and minified stylesheet file (~400kb). This file, as far as I understand, includes styles of all of the components.
While this is totally fine/usual way to deal with the css in react, it also kinda defeats the purpose of using svelte. It should not be necessary to include 400kb of CSS for a simple component which would take five carbon components and 15kb of JS.
Is there a consideration to allow building a css bundle of the used components (and dependancies) only?

I'm glad you brought this up. Documentation on real (production) set-ups is forthcoming.
The example in the README is a "quick start" method.
For now, please refer to this boilerplate for a full SASS webpack set-up. Note that the SASS import is still not optimized per component.

I'm currently doing this:
<script>
  import { Button } from 'carbon-components-svelte';
</script>

<main>
	<Button>Primary</Button>
</main>

<style lang="scss" global>
  @import 'carbon-components/scss/components/button/button';
</style>

Sadly, this bundles the button CSS globally with the 'global' attribute, without it, Svelte will remove the import in build time because it doesn't know it's being used(See https://github.com/kaisermann/svelte-preprocess/issues/44).
You need postcss installed.

I've been trying to do the same with rollup and purgecss but it removes all of carbon's css

@uribalb we are working on a custom Carbon class/element extractor for purgecss

@uribalb we are working on a custom Carbon class/element extractor for purgecss

OK. Little precision: I'm using the routify 2.x template (npx @roxi/routify init --branch 2.x). It uses postcss and rollup to build the project. I do:
<style  global>
  @import "carbon-components-svelte/css/all.css";
</style>

in App.svelte
Would you recommend to keep using carbon normally and change the config files when the plugin is ready or is there something that I should start doing with my code to make future config easier ?

@uribalb SCSS is currently the best method for optimizing CSS performance (i.e. minimizing the CSS size). Check out the Carbon guide on optimizing Sass builds.
Essentially, SCSS allows your to import the styles for individual components.
Dependencies:

node-sass
carbon-components (version 10.21 or greater)
@carbon/themes (if using any theme besides the default white theme)

The equivalent SCSS for all.css:
  $feature-flags: (
    enable-css-custom-properties: true,
    grid-columns-16: true
  );

  @import "@carbon/themes/scss/themes";

  :root {
    @include carbon--theme($carbon--theme--white, true);
  }

  :root[theme="g10"] {
    @include carbon--theme($carbon--theme--g10, true);
  }

  :root[theme="g90"] {
    @include carbon--theme($carbon--theme--g90, true);
  }

  :root[theme="g100"] {
    @include carbon--theme($carbon--theme--g100, true);
  }

  $css--font-face: true;
  $css--helpers: true;
  $css--body: true;
  $css--use-layer: true;
  $css--reset: true;
  $css--default-type: true;
  $css--plex: true;

  @import "carbon-components/scss/globals/scss/_css--reset.scss";
  @import "carbon-components/scss/globals/scss/_css--font-face.scss";
  @import "carbon-components/scss/globals/scss/_css--helpers.scss";
  @import "carbon-components/scss/globals/scss/_css--body.scss";
  @import "carbon-components/scss/globals/grid/_grid.scss";

  /* import individual components SCSS */
  @import "carbon-components/scss/components/button/button";

@metonym So from what I think you mean, I made a style.scss file in my src folder, pasted all of this stuff you've written and imported that into my App.svelte how large should my exported css be. Because theres still alot of css being generated for a single button. Can you make a "For Dummies" style guide, I'm very new to all of this css stuff and I'm having a hard time following along.

@metonym  Thanks. I think your comment should be in the docs and readme, as the official method for css optimization (for now) since svelte people tend to care a lot about these things

Would it be feasible for the components to import their own CSS directly, so you would only need have things such as the theme and the reset CSS in the global style?

@ion1 I've previously explored generating CSS for individual components from the source SCSS. However, even by taking out the reset styles, there is still a lot of duplicate CSS because many components import the same SCSS mixins/helpers.
Therefore, you'll still need an extra, build-step that removes unused selectors.
Currently, the best approach (recommended by the core Carbon team) is to use SCSS and import individual component styles.


gradle buildSrcLibs generates "buildSrc/buildSrc/src..."

I updated to 0.50.0 and executed
gradle buildSrcLibs
in the project root.
I already had an existing buildSrc directory including a Libs.kt file (from refreshVersions 0.40.*).
After executing the task these changes happened:

buildSrc/build.gradle.kts has been overwritten with a nearly empty file only containing

plugins {
    `kotlin-dsl`
}
repositories {
    mavenCentral()
}

empty buildSrc/.gitignore fhas been created
Libs.kt file under buildSrc/buildSrc/src/main/kotlin/Libs.kt has been created.

gradle buildSrcVersions shows the same behavior

This still happens with 0.50.1

Thanks for the bug repot.
Not sure that we will have time soon to get on this though to be honest :(

This is still occurring with 0.51.0
I don't understand how this isn't a major bug. Gradle isn't looking in buildSrc/buildSrc, it's looking in buildSrc/src
It's even documented here: https://splitties.github.io/refreshVersions/add-dependencies/#using-buildsrclibs
Is there something I'm missing?

I assume the developers are not using this feature.


For some reason, cross sections are sideways

Appears with the Grottberget model

This turned out to be an input error.


Bugfixes

Another try to resolve some bugs.
Relates to conversation in previous P/R: https://github.com/txn2/kubefwd/pull/189

@flupec After test this PR has a couple of problems.

kubefwd no longer creates entries for Pods backing headless services.
some entries remain in the /etc/hosts after exit.


Examples don't work in Safari or Safari Mobile

The example sounds are oggs which are apparently not supported by Safari or Mobile Safari - somehow I never noticed this until now. We should choose some example audio clips that work across the three major browsers. Probably use Howler's example sounds if possible.

If it's not working for you, and you end up here. Make sure your phone isn't on silent! 😂
Safari not supporting ogg was the original issue but I was seeing some really odd behavior, even after adding the mp3s. It turned out that my phone was on silent. Need more ☕ I guess!

I met such problem So did you fix by using MP3

Yes, take a look at the example sources. I’m now using both MP3 (for most browsers) and (ogg) for Firefox.

Thanks for your replay

I want to play it on Android Browser but I cann't do it.
<ReactHowler src= "/sounds/lost.ogg" playing={this.state.isPlay===3}  ref={(ref) => (this.lostPlayer = ref)}/>

Do the examples work on that browser? Are you getting any errors in the console?


Proposal: prettier

prettier 1.4.0 support TypeScript.

Release 1.4.0: TypeScript and CSS support · prettier/prettier

It will replace current eslint-typescript.
Should we switch to prettier?
Example: https://github.com/azu/faao/pull/10

Yes! I will remove it after next prettier is released.
(Current version 1.5.2)
https://github.com/almin/almin/pull/227#discussion_r126716188

https://github.com/prettier/prettier/releases/tag/1.6.0


Allow a team to be omitted from the rankings

This closes #31.
This only contains the database and API portion of this change. This change does NOT include a UI change to allow users to toggle this setting on their own.

So I would recommend that this PR come with a UI implementation in addition to the API implementation. That way we can roll the feature to all platforms at once

@jakahn What's the status on this PR? Are you using the code in it, or can I close this and move it to an issue?

@atti1a Go ahead and either merge and create a UI issue or close it and open a full-stack issue, whichever you think is best. Thanks!

Closing this issue due to stale code and lack of response


Extract named query parameter

Feature Request
Extract named parameters from query strings (?param1=foo&param2=bar).
Detailed Description
tide supports query extraction (#14) using UrlQuery. For example:
async fn hello_world(UrlQuery(q): UrlQuery<String>) -> String {
    q // "param1=foo&param2=bar" (how to extract the value of param1?)
}

UrlQuery<T> parses T using FromStr, but if we want to parse the query and extract individual parameters we're on our own.
Context
Working with query parameters is common in all kinds of applications.
Possible Implementation
Looking at tide itself, it could be implemented similarly to named segments. Alternatives from other frameworks:

Rocket: Derivable FromForm trait. Function parameter is marked as query string in route declaration.#[get("/hello?<q>")]
fn hello_world(q: &MyTypeThatImplsFromForm) -> /* ... */

actix-web: Parameter Query<T: Deserialize> newtype using serde_urlencoded.
tower-web: Derivable Extract trait. Function parameter must be named query_string.

#[get("/query-string")]
fn hello_world(&self, query_string: Option<Foo>) -> /* ... */

The actix-web approach might be best for Tide, because no macro magic is involved. (Well ... except that in Serde).

Related: https://github.com/rustasync/tide/issues/108

This should be easier to explore now that #156 has landed!

#175 is an updated version of this PR.


Wrong value for DisableArchiveScanning

"DisableArchiveScanning" should be either 0 or $False to make Windows Defender not scanning archives.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dbad993c-9f2b-9f51-6438-b56cd913ba1b
Version Independent ID: cc8d93f2-8837-4169-0fc7-167d0ffca777
Content: Set-MpPreference (defender)
Content Source: docset/windows/defender/set-mppreference.md
Product: w10
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Hi @LuigiBruno
Thank you for reaching out!
If we specify either 0 or $False or not specified, Windows Defender scans archive files.
If we specify either 1 or $True, Windows Defender stops scanning the archive files.
Hope this clarifies your query. Kindly confirm. Thank you.

Hi @sowjanya365.
Thank you.

@LuigiBruno
This issue has already been addressed with the following commit.
[51ccac0] Update set-mppreference.md
The issue is thus being marked as resolved.
Thank you for your feedback and taking the time to follow-up.

@officedocsbot close

@LuigiBruno
This issue has already been addressed with the following commit.
[51ccac0] Update set-mppreference.md
The issue is thus being marked as resolved.
Thank you for your feedback and taking the time to follow-up.

Thanks @e0i.

So, when will these updates be reflected on docs.microsoft.com?

So, when will these updates be reflected on docs.microsoft.com?

I think the Microsoft Docs page has been updated.

Confirmed as updated. Thank you.


unneeded changes?

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Current dependencies on/for this PR:

main

PR #829

PR #830

PR #831

PR #832

PR #833

PR #834

PR #837

PR #845

Current dependencies on/for this PR:

main

PR #829

PR #830

PR #831

PR #832

PR #833

PR #834

PR #837

PR #845


Timers / read only sliders

Is your feature request related to a problem? Please describe.
I currently use the timer-bar-card to display the amount of time an entity has been "on", when that entity turns itself off after a predefined time. This feels similar to the Spotify seeking example given in the readme.
This is what I am hoping to re-create:

Describe the solution you'd like
The "value" of the slider I would like to be templateable, allowing me to get how long an entity has been on, and for the slider to be set to be read only / not draggable.
Describe alternatives you've considered
I am currently using the custom:timer-bar-card card, although am trying to move to tile cards where possible.
Additional context
type: custom:service-call
entries:
  - type: slider
    range:
      - 0
      - '{{ states("number.heating_downstairs_timeout") }}'
    thumb: line
    value: '{{as_timestamp(now()) - as_timestamp(switch.heating_downstairs_relay.last_changed) | float}}'

I am aware that the value option I've used here isn't anywhere. As far as I can tell, value_attribute is used everywhere. However, given this isn't an attribute on the entity, I felt maybe it wasn't appropriate to overload that option.

value_attribute refers to the attribute (or just state) that should be used for the custom tile features internal value and wouldn't be used like that, but I get what you mean.
I should be able to calculate the current timer value and have the slider update to accurately display that. I don't want to make the slider not do anything when tapped by default, but should also add some logic so that it does nothing if tap_action.action is none or not set.

I've got timers working as of the latest beta with this config:
type: custom:service-call
entries:
  - type: slider
    value_attribute: elapsed
    thumb: flat
    slider_style:
      height: 10px
      width: 90%
      justify-content: flex-end
      right: 0px
    background_style:
      height: 10px
      border-radius: 12px
      width: 80%
      right: 0px
    label_style:
      justify-content: flex-start
    style:
      flex-direction: row
    label: |-
      {% set minutes = (VALUE / 60) | int %}
      {% set seconds = VALUE - 60*minutes %}
      {{ minutes }}:{{ 0 if seconds < 10 else "" }}{{ seconds | int }}
    step: 1
    range:
      - 0
      - |-
        {% set hms = state_attr("timer.timer_test", "duration").split(":") %}
        {{ (hms[0] |int ) * 3600 + (hms[1] | int) * 60 + (hms[2] | int) }}

elapsed isn't an actual attribute, but I'm using it as a fake one just for timers so other attributes can be accessed by users as needed.
TODO:

Make slider do nothing and not change position or value if tap_action.action == 'none'.
Figure out what's causing the render delay.

Probably due to value not being set until the interval delay happens, I should set the value once before setting the interval.

That template wouldn't have worked anyway, since templates only update when entities change. While I could possibly add a field for value template, I wouldn't be able to make it update frequently without a lot of additional specialized logic.
Why not create an automation that sets the timer using the heating controller information?
alias: Heating Timer Trigger
description: ""
trigger:
  - platform: state
    entity_id:
      - switch.heating_downstairs_relay
    to: "on"
    from: "off"
condition: []
action:
  - service: timer.start
    target:
      entity_id: timer.heating_downstairs
    data:
      duration: >-
        {% set seconds =  states("number.heating_downstairs_timeout") %}
        {% set minutes = (seconds / 60) | int %}
        {% set seconds = seconds - 60 * minutes %}
        {% set hours = (minutes / 60) | int %}
        {% set minutes = minutes - 60 * hours %}
        {{ '%02d' % hours }}:{{ '%02d' % minutes }}:{{ '%02d' % seconds }}
mode: single

Fixed the late rendering and made the slider not interactable if tap_action.action is set to none. Here's an even better read only timer slider config:
features:
  - type: custom:service-call
    entries:
      - type: button
        value_attribute: elapsed
        label: >-
          {% set minutes = (VALUE / 60) | int %} {% set seconds = (VALUE - 60 *
          minutes) | int %} {{ minutes }}:{{ 0 if seconds < 10 else "" }}{{
          seconds | int }}
        style:
          overflow: visible
          height: 12px
          border-radius: 0px
          '--color': none
      - type: slider
        tap_action:
          action: none
        value_attribute: elapsed
        thumb: flat
        style:
          flex-basis: 1200%
          height: 10px
          '--tooltip-label': >-
            {% set minutes = (VALUE / 60) | int %} {% set seconds = (VALUE - 60
            * minutes) | int %} {{ minutes }}:{{ 0 if seconds < 10 else "" }}{{
            seconds | int }}
        step: 1
        range:
          - 0
          - >-
            {% set hms = state_attr(config.entity, "duration").split(":") %} {{
            (hms[0] |int ) * 3600 + (hms[1] | int) * 60 + (hms[2] | int)
            }}
      - type: button
        value_attribute: duration
        label: '{% set hms = VALUE.split(":") %} {{ hms[1] | int }}:{{ hms[2] }}'
        style:
          overflow: visible
          height: 12px
          border-radius: 0px
          '--color': none
  - type: custom:service-call
    entries:
      - type: button
        icon: mdi:timer-check
        tap_action:
          action: call-service
          service: timer.start
          target:
            entity_id: timer.timer_test
      - type: button
        icon: mdi:timer-pause
        tap_action:
          action: call-service
          service: timer.pause
          target:
            entity_id: timer.timer_test
      - type: button
        icon: mdi:timer-cancel
        tap_action:
          action: call-service
          service: timer.cancel
          target:
            entity_id: timer.timer_test
type: tile
entity: timer.timer_test

As for supporting devices that have internal timers but do not have timer entities - I don't think there's a good way to do so in a standardized way. The implementation wouldn't be standard across all devices, and the devices aren't using the same entity or attribute names or time formats. Like your heater doesn't provide a finishes at datetime or a remaining time sensor.
It should be possible to create timer helpers from the existing heater entities, and those should work with this card now.

@Jab2870 if you're okay with creating timer helpers for internal device timers, then the latest 3.3.2 beta should be the release candidate for this feature.

Thanks very much @Nerwyn . Creating timers like that should be fine. Thanks. I'm using that beta and all seems good. Thanks again.

Added in 3.3.2


Change prebuild infrastructure to use prebuildify

https://github.com/prebuild/prebuildify and https://github.com/prebuild/node-gyp-build
It looks like the prebuild module has been superceeded by prebuildify
The approach of the latter is to put all the prebuilt binaries in the npm tarball. This replaces the prebuild-install library which downloads binaries at install time.
If the binaries already exist in the npm tarball then there's no need to do extra work at install time.

Switched to using prebuildify. Feel free to check if I am doing correctly, since it seems that it is only prebuilding for Windows, since I am doing dev on Windows. Or maybe that's a good thing, because Windows is the hardest OS to get binary addons to build?

Thanks kris ! I’ll take a look when I get a chance


UpdatedColumns() returns nothing every time.

public T Update<T>(object id, T poco) where T : class
        {
            var current = _database.SingleById<T>(id);
            var snap = _database.StartSnapshot(current);

            _database.Update(poco, snap.UpdatedColumns());
            _database.Dispose();

            return Select<T>(id);
        }

the record in DB doesn't get updated.

You didn't update any of the columns after you started the snapshot.

i passed in the poco object that has the updated columns. I need to map poco to current?

Don't use snapshotting then.

there are use cases where I want to pass User { ID = 5, Age = 50, Email =<EMAIL_ADDRESS>} and only update those with this UOW pattern. I'd pass in a poco with those data points updated and would expect snapshot to "merge" poco to current.

I wound up implementing this:
        public T Update<T>(object id, T poco) where T : class
        {
            var current = _database.SingleById<T>(id);
            poco = poco.Merge(current);

            _database.Update(poco);
            _database.Dispose();

            return Select<T>(id);
        }

public static class GenericExtensions
    {
        public static TEntity Merge<TEntity>(this TEntity original, TEntity target)
        {
            var properties = original.GetType().GetProperties();

            foreach (var currentProperty in properties.Where(p => p.CanWrite))
            {
                var originalValue = currentProperty.GetValue(target);
                var value = currentProperty.GetValue(original, null);

                if (!originalValue.Equals(value))
                    currentProperty.SetValue(target, value, null);
            }

            return target;
        }
    }

Works like a charm.

Thats pretty much what it already does now, but each to their own.


Hot Module replacement

there is possible using nodemon for refreshing server and hot reloading for client react?.

+1 what would be the best way to implement HMR for this? @william-woodhead


Upgrade to click ^7.0

It would seem that when using python-semantic-release in a project, click v7 cannot be used.
❯ poetry add click
Using version ^7.0 for click

Updating dependencies
Resolving dependencies... (0.0s)

[SolverProblemError]
Because no versions of python-semantic-release match >4.1,<4.1.1 || >4.1.1,<5.0
 and python-semantic-release (4.1.1) depends on click (>=6.2,<7.0), python-semantic-release (>4.1,<5.0) requires click (>=6.2,<7.0).
And because python-semantic-release (4.1.0) depends on click (>=6.2,<7.0), python-semantic-release (>=4.1,<5.0) requires click (>=6.2,<7.0).
So, because mano depends on both click (^7.0) and python-semantic-release (^4.1), version solving failed.

Consider this a feature request to have python-semantic-release upgrade to ^7.0 of click.

Happy to accept a pr for this.

I was just thinking about this.  Does this project really need click 7.0?  If not we should not require ~7.0.  In fact, I suspect version 2.0 is enough.  I downgraded and all tests pass.  (I mean all tests that were passing before continue to pass.  There are 2 which are expected to fail.)  I set requirements/base.txt to click>=2.0.


Tests fail when 'org.jetbrains.idea.maven' dependency is present

What happened?
I have a small test project, the tests of which are failing.
But if I remove the org.jetbrains.idea.maven dependency from plugin.xml, everything starts working.
In the real project, I need this dependency for the implementation of functionality
Relevant log output or stack trace
No response
Steps to reproduce
Run gradle test
Gradle IntelliJ Plugin version
1.15.0
Gradle version
8.3
Operating System
macOS
Link to build, i.e. failing GitHub Action job
No response

Thanks for reporting, Yuri!
I was able to reproduce the issue — looks like Maven affects how PSI is resolved.
However, this issue is not directly related to the Gradle IntelliJ Plugin.
Did you try to debug that with PSI Viewer?
Please file an issue in YouTrack so relevant team could pick up this case, thanks!

Hello @hsz
I hope this message finds you well. I am writing to kindly request your assistance regarding a ticket escalation in the JetBrains tracker.
It has been a couple of weeks since I submitted a ticket, but unfortunately, there hasn't been any response or action taken on it. I understand that everyone's busy but your assistance in accelerating this process or providing me any updates about the situation would be greatly appreciated.
Thank you in advance for your time and support on this matter.

@yorlov The team already picked up this issue. The problem is reproduced, and further investigation is ongoing. Sorry for the delays. I'll keep an eye on it!


[move-lang] Update compiler API

Overhaul compiler API for a 'Compiler' struct entry point
Will make it a lot easier to deal with a extra flags

Motivation

We will need a bunch of extra flags especially with named addresses. The struct-based entrypoint will make that easier
I also tried to clean up the pattern of match result { PassResult(ast) => ast, _ => unreachable!() }  by using const-generics. If conditions on const generics ever land we will get some neat stuff with run. It might be a bit overboard right now but I thought it was better than stamping out a bunch of different compiler-structs for each pass

Test Plan

ran the tests

I'm probably not going to have time to give you a detailed review on this, so please don't wait for me.

/land


List search and sort doesn't appear to work

I've recently been reworking a project to utilise the newest version of MetroUI4 (v4.3.5) compared against a version roughly 1 year old. So far it's being going great, excellent work on the continued development by the way. Unfortunately I can't for the life of me spot the reason causing this issue, but I simply cannot get my "List" component to search and sort. It functioned fine previously.
It grabs the JSON external data and renders as expected, just fails to sort when the buttons are clicked and returns a blank list if anything is entered into the search box. Find attached an example JSON file (Data modified for data protection reasons) and the HTML snippet for the List.
test.json.txt
html snippet.txt

Just attaching a couple of screenshots that show default rendering vs the blank results when searching.

use Metro.getPlugin(...) to access to component API

function sortList(col, dir) {
    Metro.getPlugin('#students', 'list').sorting(col,dir,true);
}

add classes student-surname, student-dob into the appropriate divs

"template": "<a href='<%this.student_id%>/'>

<img height=90px width=90px src='<%this.img_src%>' alt='Student Image'>

<%this.student_surname%>,
<%this.student_forename%>

<%this.student_dob%>

"

Hi Olton,
Thanks for the quick response. I'll give it a shot in a short while. You may want to reflect the changes in the documentation too when you get chance. I did not see the examples under Lists utilise Metro.getPlugin() at all?

https://metroui.org.ua/components-api.html

Sure, however https://metroui.org.ua/list.html contains an example that does not use Metro.getPlugin(). That's what threw me for a loop on this one.
Thanks again for your help. It's working perfectly now that's sorted :)

Metro.getPlugin('#all-list','list')._createItemsFromHTML()


Using Frame Processor outside RN component✨

What feature or enhancement are you suggesting?
Hi,
I would like to use your package, in particular Frame Processor in a foreground service (Android only). Thus even when the app is in a killed state.
But it seems that using this implies to return a JSX component <Camera />, or maybe I miss something...
Is this use case possible?
Thanks
What Platforms whould this feature/enhancement affect?
Android
Alternatives/Workarounds
No workarround found...
Additional information

[X] I agree to follow this project's Code of Conduct
[X] I searched for similar feature requests in this repository and found none.

Hey Jared!
Can you give me an example repo/code? I've never had such a use case before

Thank you for your answer !
Unfortunately, I do not have code or repo.
But I'm using rn-foregroud-service
https://github.com/Raja0sama/rn-foreground-service
It allows to run JS task in the foreground service.
Thus, I need a pure JS function, which of course may call native module, to process Frame Processor.
In this kind of function, I can't use any hook, or return JSX component.
Do you think your lib may be adjusted for such an use case?

An example of what you're trying to achieve would helpful, as right now it's kinda hard to understand the use case you're talking about.  From the sound of it, you're trying to process frames from a camera component that isn't rendered (meaning there are no frames coming from it to process in the first place).  It sounds like you'd be better served by capturing the frame/photo, storing it to a state object, and processing it from that instead of trying to hook into the frame processor.
Have you looked at React Native's in-library NativeEmitter class?  That might be of more use to you for this.  Like I said though, an example of your specific use case would help a lot.

OK I see.
What I want to achieve in this part of my app, is to capture motion detection from front camera, and then make an http request to a home automation software, so that the device acts as a PIR motion sensor.
But I need this in a foreground service, without rendering anything, and without user interaction.
So maybe I need a loop that compare the frame at time t-1 with the one at time t and a kind of AI that may detect a change (for exemple if light is turn on/off in the room, the picture will change, but there is no motion...)
Do you have any idea how I can achieve that ?
Thanks for your help!

@jared-94 did you manage to get this going?
Facing similar problems - https://github.com/mrousavy/react-native-vision-camera/issues/1011

Hey, it needs to render in an app.


Backpacks spec

Backpacks

unlimited # of backpacks (as many items as you can make)
can integrate with Accessories plugin
can trigger cosmetic; unique settings for each backpack
open by

right-clicking a backpack item while it's in your inventory
holding the backpack item in your main hand and right-clicking (air only?)

toggleable item collection

TODO: decide when backpacks can pick up items. do they have to be in an accessory slot? if not, can you select more than one at a time? how is the order determined?
Backpacks can pickup items automatically
Some backpacks (not all) will have this feature
To activate this feature the backpack must be active in an accessory slot
Backpacks cannot be placed inside another backpack

API

get by id (just the backpack content/object? or the corresponding "physical" itemstack too?)
open (backpack) by item

Commands

/backpacks give [player]

Features

Players can add rows to their backpacks
configurable styling of controls for item collecting

this includes what slots (AND title :), so larky can make even more awesome GUI :D

pagination (can edit/style these items/buttons as well)
can edit the backpack item (?, == custom name, lore?)

display name
material
lore
custom model data

Updated spec

No nesting of backpacks

Updated spec

reflect changes in approach


Docker exec not writing to stream

Hello,
I'm trying to use Docker Exec in order to attach to a container and execute commands.
I change the stdin and use the same approach as when using container and attach but it doesn't seem to have the same response. I get the response the cmd (bash prompt) but when I try and write a command into bash it fails.
Here is an example:
https://gist.github.com/BenHall/0863b723fde31f712301
Any ideas?
Ben

@BenHall It shouldn't be required, but I've found adding a 100ms or so delay before writing to the exec stream makes a huge difference. I haven't yet had time to figure out the root cause, but I'd be curious to hear if it helps with your case or not.

@rmg Great idea, but sadly that doesn't seem to work for me :(

@BenHall maybe because you have typo in "Detach" argument? It is written as "Detact"

Can we close this one?

Yes. With the right combination of settings it does work as expected

Can you share your working code .. it doesn't seem to work for me

I have found a problem in the docs of docker API, the exec start request body just '' Detach 'and "Tty", i have the problem, Imcompelete, only when the configuration file with stream: true, stdin: true, stdout: true, stderr: true, chunk can write correctly. Do not know why, -_- !!!


add basic button & input components

Resolve #9 & resolve #4
Hope you don't mind I'm making this PR, it's my first time working with tailwind css

can you provide screenshot? Because i think, its break input and button style.
before :

After:

I think its, class in variable baseClass is not recall by tailwindCSS
better to use packages like clsx for constructing className strings conditionally.

Hi @naufaldi , I just resolved this. The real issue is not about baseClassName or finalClassName not recalled by tailwind, but really about me not knowing that the new component folder must be specified under tailwinds config.
Kindly check it out on the new preview build


Convert cpan dependency manager to use local perl packages

Turns out cpanm leaves the packages it downloads under ~/.cpanm/latest-build. This PR removes the cpan deps web service dependency during the build and it will increase our build's reliability.
/cc: @danielsdeleo @ryancragun
/cc: @marcparadise / After this we can enable fatal transitive dependency licensing in Chef Server build pipeline.
PS: Since spec fixtures are heavily modified here, you can use below command to review:
git diff sersut/cpanm master --name-only | grep -v '^spec/fixtures/' | xargs git diff master sersut/cpanm --

👍


Library not loaded: /usr/local/lib/libffmpeg.dylib (OSX)

I have not used electron in a while, started a new project with npm i --save-dev electron-prebuilt and am receiving this error. I don't see anything in the README.md about installing anything special. I have pasted the error below for reference. Any help is greatly appreciated, I will continue to try and resolve this as well.
Thanks!
Process:               Electron [633]
Path:                  /usr/local/lib/node_modules/electron-prebuilt/dist/Electron.app/Contents/MacOS/Electron
Identifier:            Electron
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        node [632]
Responsible:           Terminal [621]
User ID:               501
Date/Time:             2016-03-11 22:22:11.129 -0800
OS Version:            Mac OS X 10.11.3 (15D21)
Report Version:        11
Anonymous UUID:        20D3F0F9-F258-669F-C057-F75504E4FF80
Time Awake Since Boot: 250 seconds
System Integrity Protection: enabled
Crashed Thread:        0
Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /usr/local/lib/libffmpeg.dylib
Referenced from: /usr/local/lib/node_modules/electron-prebuilt/dist/Electron.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
Reason: image not found
Binary Images:
0x7fff6ba45000 -     0x7fff6ba7c007  dyld (360.19) <9D05FDF4-65CE-3B53-86D4-ABE1A5BF35F3> /usr/lib/dyld
0x7fff8a8b9000 -     0x7fff8aa87ffb  com.apple.QuartzCore (1.11 - 410.14)  /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff8ecb6000 -     0x7fff8ecb7ffb  libSystem.B.dylib (1226.10.1) <5A4257EF-3145-3BB3-87A4-0D2404A9462D> /usr/lib/libSystem.B.dylib
0x7fff8f644000 -     0x7fff90267ff7  com.apple.AppKit (6.9 - 1404.34) <467468E2-C551-3408-B351-414B21F57DEB> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff905e0000 -     0x7fff905eefff  com.apple.opengl (12.0.40 - 12.0.40)  /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff912f9000 -     0x7fff9143efff  com.apple.QTKit (7.7.3 - 2943) <6DD72D38-9449-3289-904E-B6E148993AA5> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff9b46b000 -     0x7fff9b4dffff  com.apple.framework.IOKit (2.0.2 - 1179.20.6)  /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff9bb72000 -     0x7fff9bbc5ff7  libc++.1.dylib (120.1) <8FC3D139-8055-3498-9AC5-6467CB7F4D14> /usr/lib/libc++.1.dylib
0x7fff9d6b5000 -     0x7fff9d6b5fff  com.apple.Carbon (154 - 157) <34263101-328D-3FE4-B212-14BD3CFF6965> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon

The same happening here. :-(

Here is the electron repository: http://github.com/atom/electron
On Sat, Mar 12, 2016 at 2:36 PM, Hildeberto Mendonça <
<EMAIL_ADDRESS>wrote:

The same happening here. :-(
—
Reply to this email directly or view it on GitHub
https://github.com/electron-userland/electron-prebuilt/issues/104#issuecomment-195820376
.

Known issue https://github.com/atom/electron/issues/4765

It's been fixed at atom/electron#4769


CORS issue with Vimeo in Flutter Web (Access to XMLHttpRequest has been blocked by CORS policy)

Steps to Reproduce

We use pod_player for running Vimeo videos in our flutter web application
Within the plugin we get a cors error to hit the video API and we provide access "Access-Control-Allow-Origin" :"*" and the issue still arises
What we can do now to resolve the cors error in our web app

Flutter Version :  3.3.9
Dart SDK version: 2.18.5
##plugin
pod_player_new : 0.0.6

possibly a pod_player issue
related issues:

https://github.com/flutter/flutter/issues/32622


A host function that calls another host function loses access to the memory

Describe the bug
So I'm not entirely sure this is a bug report or a feature request. I came across this issue while implementing C++ exceptions support for Emscripten in Wazero. Apparently it's possible that Emscripten uses the generated invoke_xxx methods (which is a host function) to call another host function, without a "proxy" through the guest. I then found out that it's also possible to reproduce it without using C++ exceptions.
This issue causes the second host function not to have access to the memory, because the second host function is being called by invoke_xxx, which is in the env module, and receives the env api.Module, while the invoke_xxx is also in the env module, it does receive the main application memory, and this is also mentioned in the comments of GoModuleFunction:
// This function can be non-deterministic or cause side effects. It also
// has special properties not defined in the WebAssembly Core specification.
// Notably, this uses the caller's memory (via Module.Memory). See
// https://www.w3.org/TR/wasm-core-1/#host-functions%E2%91%A0

While it does make sense to give this the caller's memory (if we didn't, the host functions would be way less usable), but in my case, this means that the second host function call does not have access to the memory, just because it was called from another host method and not from the guest, while it would have access to it if it would have been called by a "proxy" function in the guest.
I'm not sure what the best solution to this would be. Perhaps it would be possible to have an option to override the moduleInstance or memoryInstance in m.Engine.LookupFunction or f.CallWithStack so that we can use it in InvokeFunc.Call() to maintain access to the memory when doing host to host calls.
Given the sample code in the next block, the following two things will happen:

invoke_i (host)
you_could_say_im_a_host_function_proxy (guest)
you_could_say_im_a_host_function (host)
m.Memory().ReadByte(200)

Works :tada:

invoke_i (host)
you_could_say_im_a_host_function (host)
m.Memory().ReadByte(200)

Breaks :bomb: (failed: runtime error: invalid memory address or nil pointer dereference)
To Reproduce

C code compiled with Emscripten
#include <stdio.h>
#include <stdlib.h>
#include <setjmp.h>

extern int you_could_say_im_a_host_function();

void jmpfunction(jmp_buf env_buf) {
   longjmp(env_buf, 42);
}

int you_could_say_im_a_host_function_proxy() {
  return you_could_say_im_a_host_function();
}

int main () {
   int val;
   jmp_buf env_buffer;

   val = setjmp( env_buffer );

   if( val != 0 ) {
      printf("Returned from a longjmp() with value = %d\n", val);
      you_could_say_im_a_host_function_proxy();
      you_could_say_im_a_host_function();
      exit(0);
   }

   printf("Jump function call\n");
   jmpfunction(env_buffer);

   return(0);
}

emcc -sERROR_ON_UNDEFINED_SYMBOLS=0 -sSUPPORT_LONGJMP=emscripten -g invoke_host.c -o invoke_host.wasm

Go code with the host function implemented
package main

import (
	"context"
	_ "embed"
	"github.com/tetratelabs/wazero"
	"github.com/tetratelabs/wazero/api"
	"github.com/tetratelabs/wazero/experimental"
	"github.com/tetratelabs/wazero/experimental/logging"
	"github.com/tetratelabs/wazero/imports/emscripten"
	"github.com/tetratelabs/wazero/imports/wasi_snapshot_preview1"
	"log"
	"os"
)

//go:embed invoke_host.wasm
var wasm []byte

func main() {
	ctx := context.WithValue(context.Background(), experimental.FunctionListenerFactoryKey{}, logging.NewLoggingListenerFactory(os.Stdout))
	r := wazero.NewRuntime(ctx)

	defer r.Close(ctx)

	if _, err := wasi_snapshot_preview1.Instantiate(ctx, r); err != nil {
		log.Fatal(err)
	}

	compiledModule, err := r.CompileModule(ctx, wasm)
	if err != nil {
		log.Fatal(err)
	}

	functionExporter, err := emscripten.NewFunctionExporterForModule(compiledModule)
	if err != nil {
		log.Fatal(err)
	}

	envModule := r.NewHostModuleBuilder("env")
	functionExporter.ExportFunctions(envModule)
	envModule.NewFunctionBuilder().WithGoModuleFunction(api.GoModuleFunc(func(ctx context.Context, m api.Module, stack []uint64) {
		m.Memory().ReadByte(200)
		stack[0] = 42
	}), []api.ValueType{}, []api.ValueType{api.ValueTypeI32}).Export("you_could_say_im_a_host_function")
	_, err = envModule.Instantiate(ctx)
	if err != nil {
		log.Fatal(err)
	}

	moduleConfig := wazero.NewModuleConfig().
		WithStartFunctions("_start").
		WithStdout(os.Stdout).
		WithStderr(os.Stderr)

	_, err = r.InstantiateModule(ctx, compiledModule, moduleConfig)
	if err != nil {
		log.Fatal(err)
	}
}

Full sample zip:
invoke_host.zip
Environment (please complete the relevant information):

Go version: 1.20.2
wazero Version: v1.4.0
Host architecture: amd64
Runtime mode: both

Additional context
This was also discussed a bit on Slack: https://gophers.slack.com/archives/C040AKTNTE0/p1691699092428169

verified that #1636 fixes the repro:
$ go run .
Jump function call
Returned from a longjmp() with value = 42


Add default constraint to the full list of generic constraints

The list of constraints does not document where T: default, which is a valid constraint for overrides and explicit member implementations: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-9.0/unconstrained-type-parameter-annotations#default-constraint.
While constraint is documented at C# 9.0 location above, it is hard to find -- most searches for "generic constraints in C#" link to the full constraint list.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5712215d-b167-d9cb-bd51-80df0e300d50
Version Independent ID: 22b2c77c-2721-9384-3863-046e391ea4b1
Content: Constraints on type parameters - C# Programming Guide
Content Source: docs/csharp/programming-guide/generics/constraints-on-type-parameters.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for noting this @ashmind
I'll take care of it this month.


Bastion AMI list

A python script that generates a list of recently created AMI for each region, serialized in YAML.

LGTM


Default to Unicode strings

Would it be possible, when inserting data, to default to Unicode strings? That is, instead of having to use ExplicitUnicodeString, to force people to use ExplicitNonUnicodeString when they don't want Unicode? I realize this might be a breaking change, but it seems like the right thing to do. Am I missing something that makes this a bad idea?

@vgrigoriu I guess it all depends on the use case, i never liked the naming though UnicodeString should have been better as a class name.
What you could do and has less side effects is keeping the code as is but

Add Ansistring in same way as we now have ExplicitUnicode
Add overload option to insert update etc which is by default false threatallstringsasunicode (expect the ones explicitly using a type like ansistring or unicodestring)

What do you think about this ?

I don't think there's any use case in which defaulting to ANSI strings is correct. Either you only use ASCII characters, so you don't care, or you use accented characters, in which case clearly what you want is an Unicode string. If we make Unicode strings the default and someone's code behavior changes then it was almost certainly a bug.
I think the right thing to do would be:

deprecate ExplicitUnicodeString
add AnsiString, as you suggested
default to formatting normal .NET strings as Unicode SQL strings.

If you agree, I'll try to send a PR this weekend.
cc @Ashthos who originally introduced ExplicitUnicodeString.

Fixed in 2.0.0

Wow 😄
Thanks for finally getting this in!

It was a rough ride. 1 month of work went into the 2.0 release.


Applied tokens show in plugin UI but not in Figma UI. When removing those particular tokens, all other tokens seem to be removed too.

To Reproduce
Steps to reproduce the behavior:

Select the layer that has tokens applied
Check what tokens are applied in the plugin UI (Inspect tab) and compare it to the tokens shown in the figma UI
Remove applied tokens via plugin UI and see that ALL other tokens seem to have been removed according to the figma UI.

Expected behavior
Plugin UI and Figma UI should both show the same tokens applied
Screengrabs

In plugin UI the focus border colour appears to be applied, however does not show in the Figma UI.
Having selected the border focus colour and removed it ALL of the tokens disappear from the Figma UI, even though they still show in the plugin UI.

Also, when attempting to undo these changes, tokens are not RE-applied where they once were. I am left unsure as to whether they were actually applied in the first place

I am also facing the same issue. But what I am doing is, I closed the Figma Tokens window and reopened it then applied the same token then It's working. Maybe you can try that until we get the fixed version :)

@uipetals That doesn't work for me. In fact, when I reopen the plugin, the tokens which I just removed are still applied. Other than these little glitches, I'm loving the recent updates @six7 :)

Thanks for reporting! Seems like we remove all relaunchData (the stuff in the figma ui bottom right) when removing a token via Inspect.
To clarify: Those tokens itself are not removed, just the relaunchData in the bottom right is (which is just being used to show users SOME tokens are applied here, but other than that this serves no purpose)

Thanks for the update. So is the plugin still doing its job or should we wait for a fix?

No need to wait, it's really just that button on the bottom right that's affected (however that has nothing to do with applied tokens). Also that button isn't reliable anyway as it doesn't work for instances


Misleading diagnostics for !pip

Pylance keeps showing errors for !pip.

I get pip is not defined, install is not defined, and pandas is not defined.
The errors seem to be from Pylance.
Here's another example screenshot:

Dup of https://github.com/microsoft/vscode-jupyter/issues/1497


Custom functions

Knex it's very flexible And allow me write things like
knex
  .select(knext.raw(...))
  .from(function() { ... });

in my current my project I'm using postgres and I've started tu use WITH syntax to simplify some complex queries
I have to do something like this

var queryA = knex.select(...).from(...);
var queryB = knex.select(...).from(...);

return knex.raw ('WITH queryA_ As ( ' + queryA.toString()  + ') ' + queryB.toString() )
  .then(function(resp) { ... });

Maybe some way to write custom code that allow use them as knex.select(knex.raw(...)), for example

// WITH alias_1 AS (
//         ...
// ), alias2 AS (
//         ...
// )
// SELECT ...
// FROM ...;
kext.custom('with', function(kext, alias) {
  return 'WITH ' + alias + ' AS ( ' + kext.toString() + ') ';

 // WITH instructions are separated wih comma  , character
 // this is hacky maybe a better with to do
 this.separator = ',';
});

var queryA = knex.select(...).from(...);
var queryC = knex.select(...).from(...);
kext
  .with(queryA)
  .with(queryB) //
  .select(...).from(...); // this is queryB

Is there any way to use proposed custom outside of CTE? If not, there's a task for CTE support #716

CTE support has been added to knex. If any other usecases pop up, feel free to reopen.


Produced an unexpected new value... was null.. but now cty.SetValEmpty(cty.String)

Describe the bug

Running an apply with the same code again causes the diff to change (I have noticed the diff changes happen for either user or group in a similar way)

and gives error:
Provider produced inconsistent result after apply Error : When applying changes to platform_group.mrgroup, provider produced an unexpected new value: This is a bug in the provider, which should be reported in the provider's own issue tracker. . members: was null, but now cty. SetVa1EmptyCcty. String) .

Code snippet
resource "platform_group" "my-group" {
  name             = "my-group"
  description      = "My group"
  auto_join        = true
  admin_privileges = false
}

resource "artifactory_managed_user" "test-user" {
  name     = "test-user"
  password = "dcfsdcfsdc1sdcsdZ!£"
  email    =<EMAIL_ADDRESS>  groups   = [platform_group.my-group.name]
}

resource "artifactory_local_generic_repository" "test-repo" {
  key          = "test-repo-2"
  description  = "Test repository"
}

resource "artifactory_remote_generic_repository" "test-repo-2-remote" {
  key          = "test-repo-2-remote"
  description  = "Test repository"
  url          = "https://test.com"
}

resource "artifactory_virtual_generic_repository" "test-repo-2-virtual" {
  key          = "test-repo-2-virtual"
  description  = "Test repository"
  repositories = [artifactory_local_generic_repository.test-repo.key, artifactory_remote_generic_repository.test-repo-2-remote.key]
}

resource "platform_permission" "my-permission" {
  name = "my-permission-name"

  artifact = {
    actions = {
      groups = [
        {
          name = platform_group.my-group.name
          permissions = ["READ", "WRITE"]
        }
      ]
    }

    targets = [
      {
        name = artifactory_local_generic_repository.test-repo.key
        include_patterns = ["**"]
      }
    ]
  }
}

Requirements for and issue

[x] A description of the bug
[x] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue). If this is not supplied, this issue will likely be closed without any effort expended.
[x] Your version of artifactory: 7.98.9
[x] Your version of terraform: 1.9.8
[x] Your version of terraform provider: 1.19.0

Expected behavior

Re-running an apply against the same Terraform code shouldn't cause any diff change to either groups or users when the code has not been changed

Another example of the error happening this time on a user (I am using CDKTF in this context, but still reproduced via raw TF)

Produces the same error:

@zamanh I'll be opening a PR with a fix to this issue shortly. However, I recommend using ignore_changes with platform_group.members attribute to avoid state drift in the first place. Because after the second apply, the user will be removed from the group and now artifactory_user.groups would have different value.


Added policy for scc's

What is this PR About?
SCCs live under security.openshift.io/v1 for v4
How do we test this?
_test/tests.bats or check action output
cc: @redhat-cop/day-in-the-life

@pabrahamsson ; good to merge?


Flame Graph for Profiling Data

Pull Request Description
Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result).
Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed]
https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4
Important Notes

Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day).
re-instated the behaviour that logs are shown in the JS console if development mode is active.

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, and Rust style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH ./run dist and ./run watch.

Current (pre-#3270) profiler data model vs. design
The demo shows a Chrome-style-callgraph. This is not the type of graph in the design doc, which I've referred to there as a run-graph (out of a set of tasks, it shows which one is running).
Specifically, the difference between the two graphs is:

In a Chrome-style-callgraph, a block represents the lifetime of a profiler, and rows indicate stack depth.
In a run-graph, there is one row for each profiler (or profiler lifetime[^1]); blocks within a row show the intervals that that profiler is active.

[^1]: Side note: it's not clear from the image in the design doc whether a row contains the active-intervals for all lifetimes of a particular profiler, or each time that profiler is created it gets its own row. I think the former is a better default, but in the future we'd want to support distinguishing multiple lifetimes of a profiler, maybe with an expand-widget that breaks down a profiler into a different row for each lifetime, that is only used when one profiler has multiple overlapping lifetimes.
The demo reflects the currently-implemented data model: Before #3270, profiler did not log enough information to generate a run-graph. However, once we have await timings, it will be possible to implement a graph like in the design doc.
Extend the design?
Only the run-graph can make clear the lifetimes and relationships of async tasks; however, a callgraph is better at showing non-async code (a run-graph would spread stack frames across too many rows, and not stack them nicely by depth). I think we should revise the design to include both types of graph.
One approach to creating a hybrid would be:

Render a run-graph of the async tasks, providing a high-level view.
Below it, render a callgraph of non-async profilers.
When a block in the run-graph is clicked, zoom to that interval in the callgraph (is this easy to implement?).

Effects on implementation
Although the data is organized differently between the two graph types, they are rendered in almost the same shapes; the current implementation is almost capable of rendering either. In order to support full run-graphs, it would need a container-block type to show lifetimes: a lifetime is rendered as a container-block that spans part of a row, and has leaf blocks inside it. (In the design doc image, lifetimes are light gray, with green blocks inside them.)

The PR is updated to the new profiling API. @kazcw A review of the integration and changes to the profiling API would be very appreciated.
Note that the previous use of now failed in the IDE, and I thus changed it to us our own API wrapper instead.

Current (pre-#3270) profiler data model vs. design
The demo shows a Chrome-style-callgraph. This is not the type of graph in the design doc, which I've referred to there as a run-graph (out of a set of tasks, it shows which one is running).
Specifically, the difference between the two graphs is:
* In a Chrome-style-callgraph, a block represents the lifetime of a profiler, and rows indicate stack depth.

* In a run-graph, there is one row for each profiler (or profiler lifetime[1](#user-content-fn-1-1793f4dc309c9cec8d687af7f8cc7a0b)); blocks within a row show the intervals that that profiler is active.

The demo reflects the currently-implemented data model: Before #3270, profiler did not log enough information to generate a run-graph. However, once we have await timings, it will be possible to implement a graph like in the design doc.
Extend the design?
Only the run-graph can make clear the lifetimes and relationships of async tasks; however, a callgraph is better at showing non-async code (a run-graph would spread stack frames across too many rows, and not stack them nicely by depth). I think we should revise the design to include both types of graph.
One approach to creating a hybrid would be:
* Render a _run-graph of the async tasks_, providing a high-level view.

* Below it, render a _callgraph of non-async profilers_.

* When a block in the run-graph is clicked, zoom to that interval in the callgraph (is this easy to implement?).

Effects on implementation
Although the data is organized differently between the two graph types, they are rendered in almost the same shapes; the current implementation is almost capable of rendering either. In order to support full run-graphs, it would need a container-block type to show lifetimes: a lifetime is rendered as a container-block that spans part of a row, and has leaf blocks inside it. (In the design doc image, lifetimes are light gray, with green blocks inside them.)
Footnotes
1. Side note: it's not clear from the image in the design doc whether a row contains the active-intervals for all lifetimes of a particular profiler, or each time that profiler is created it gets its own row. I think the former is a better default, but in the future we'd want to support distinguishing multiple lifetimes of a profiler, maybe with an expand-widget that breaks down a profiler into a different row for each lifetime, that is only used when one profiler has multiple overlapping lifetimes. [leftwards_arrow_with_hook](#user-content-fnref-1-1793f4dc309c9cec8d687af7f8cc7a0b)

Sorry for the confusion, there was a design discussion with Wojciech, I have created a new PR to the design documents with the results. We wanted to see the implementation first.
You make some excellent points about improvements to the visualization, but I think we should have that discussion as part of a new PR to the design, while this PR creates a first useful literation.

Now the async intervals will be drawn in the right place, but I think their non-async children will be floating below--they are drawn at their hierarchy level, which is no longer the same as parent_row+1.
The test case could use some async fn coverage.

Good point! I’ve updates this to behave correctly now and extended the demo scene to include both calls from sync to async and async to sync.

@farmaazon @mwu-tow @4e6 This still requires a code-owner review for the lock file.


Update 9.x to include a ROOT variant

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

I've created a new branch in conda-forge/clangdev-feedstock which corresponds to how 9.0.1 was build named 9.x. This PR then modifies an older version of master to build for 9.x and include a variant for ROOT 6.24.00. In principle the next release of cling should be able to use this patches directly as well.
I'm running some final tests locally but I'm eager to get this merged so I can update the ROOT package so if you have any comments let me know.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/clangdev ready for review
I've created a new branch in conda-forge/clangdev-feedstock which corresponds to how 9.0.1 was build named 9.x. This PR then modifies an older version of master to build for 9.x and include a variant for ROOT 6.24.00. In principle the next release of cling should be able to use this patches directly as well. I’ve already ran tests building root for most platforms and everything seems to be working as expected.


governance: Add Technical Charter

This adds the OPI Technical Charter into the repository. I've also
removed the older GOVERNANCE.md file, which we used to help form the new
Technical Charter. The Technical Charter is a combination of standard LF
technical charter verbiage with our own governance desires and
discussions over the past few months.
Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

@ tbenzies thanks for the draft of this technical charter!


perf: cache file stats/reads

This is some work towards fixing (not entirely) #121. File reads and stat calls are cached for the lifetime of the code execution. This takes the number of times files are stated dramatically down (on our build, one file goes from 13,000 stat calls to 1,300), however browser-resolve still does many file reads/stats using its own mechanism - so further PRs will be arriving next week around this, as files are still read multiple times when they don't need to be.
It may be worth clearing the read file cache out on an ongenerate rollup call or something?
Thoughts/comments welcome.
/cc @mislav who worked on this with me

Yes the other issue is if a file gets into an error state, then that error state is cached indefinitely. I think I'll address some of these concerns though as Im not entirely comfortable merging this PR in this state.

@lukastaegert would be good to get your thoughts about this new change. I've changed two things since last review:

If the stat/read calls error (except if a stat call occurs on a non-existent file) then delete the cache, so they are re-read/stated each time.
The plugin adds the write hook (per https://github.com/rollup/rollup/wiki/Plugins#creating-plugins) to flush the caches every time a compile is run.

Thanks for your efforts here! Would be nice if you could rebase against current master as this will add a "prepare" script that should enable direct installation from Github. This should make it easier to test this PR in different scenarios.

Rebased 😸

Fixed up those issues. I'm comfortable enough with this now. We've been testing this internally for a while now and it works well.

Hey @keithamus, sorry for not getting back to you. So it seems that while I do not have the npm publishing rights for this plugin, you  do have them. So I was wondering if you would want to take it upon you to release the latest PRs for this plugin?
I'm also asking because @kellyselden was asking me about the state of #140 and #141.

For sure - are you happy with each of these PRs?

Yup, thanks for taking care of this 👍! This really helps @guybedford and myself concentrate on maintaining rollup core. If you want a review from us for anything, don't hesitate to add us as reviewers.

By the way, at the moment I am fledging out a solution to get precise performance timings for rollup both for internal code as well as time spend in plugin hooks rollup/rollup#2045.
When bundling rollup with<EMAIL_ADDRESS>rollup spends about 180ms resolving ids on my machine. With<EMAIL_ADDRESS>this drops to 4ms! Amazing work indeed! 🎉


use old ghz

Workaround for https://github.com/bojand/ghz/issues/340

Need to rebase after https://github.com/LesnyRumcajs/grpc_bench/pull/198 is merged


endSubmission is called whenever onSubmit returns false

With the type = normal and an onSubmit hook:
{#autoForm schema=registerSchema class="p-t-15" id="registerForm" type="normal"}}
  <!-- ... -->
{{/autoForm}}

AutoForm.addHooks ['registerForm'],
  onSubmit: (doc) ->
    # Run some async code that calls this.done() when is complete
    false

Looking at https://github.com/aldeed/meteor-autoform/blob/8544c659ea5235bbbc9f737e170d405c11e23cac/formTypes/normal.js#L54, it seems that this.endSubmission() is called when the onSubmit hook returns false. Shouldn't endSubmission be called inside the call of done (passed to the hook)?

You're right. Fixed in 5.7.1


Create custom types for Express request objects

Just because it's worth learning how to do.

Not useful for my situation (route parameters).


transformer to inline css scripts?

We could inline our 1/2 dozen css scripts into the main html file, to eliminate multiple resource loads at startup.

We'll move to serving the UI off of appengine, and use its built in pagespeed service.


BubbleUPNP devices not being discovered

swyh.txt
The devices are responding to SSDP but not sure what's going on after that. These all show up in swyh original but not in -rs

please attach the complete (unedited) debug log.

log.txt

Thanks.
The problem is simple: the location header in the SSDP response should be uppercase "LOCATION:", but for some reason Bubble uses "Location:". You will see in your log that all other devices properly use LOCATION.
Easily fixed, probably tomorrow.

Should be fixed in release 1.12.1.

The reason: it's the only device I have ever encountered that puts the Location header last.
Everyone else puts it at the top, and I stopped scanning at the St header, so the Location header was missed.
I'll yank 1.12.1 and release 1.12.2.

This time I hope I fixed it properly. Sorry for the mess...

log.txt
Almost there :)
Now only "Living room speaker" shows up in UI but I can see all the other devices are being discovered now in the log.
There should be 4 devices exposed from BubbleUPNP as DLNA:
Living room speaker
Master Bedroom speaker
Entryway speaker
Speaker group
Let me know if you need any more info from me, thanks for your quick responses

If I expose an openhome renderer in BubbleUPNP that one takes the place of the "Living room speaker (DLNA)" renderer in the UI. Possibly only the first BubbleUPNP renderer is being properly shown?
log.txt

If I release a new beta to test, do you need the setup or is a debug binary sufficient?

If it's just replacing the swyh-rs.exe I can handle that

There's a new beta setup.

I expected problems but I thought the buttons for the players would at least show up.
However, since the streaming is totally disconnected from UPNP, I have no means to connect a device that is currently streaming to the buttons in the GUI, and I don't think I can solve that. I only have the IP address of any device that starts streaming, and nothing more. So it's probably not something that I can support reliably.

But I'll see if I can up with something that works if you are prepared to wait a bit.

The beta has been updated. I think it should work now.
Some things will probably no longer work, let me now if you find something (or if it still doesn't work at all).

Looks to be the same with beta 2, albeit with no regression either from what I can tell.
log.txt

The beta has been updated again. I think it should work now, honestly :)
Some things will probably no longer work, let me now if you find something (or if it still doesn't work at all).

Beta 3 also looks to be exact same behavior, still able to stream to the one exposed dlna device just fine:
log.txt

For some reason you're still running the original beta. This line:
Renderer Denon AVR-S760H Denon AVR-S760H ip <IP_ADDRESS> at urlbase http://<IP_ADDRESS>:60006/ has 9 services

should be similar to this one:
Renderer Marantz UPNP UpMPD ip <IP_ADDRESS> at location http://<IP_ADDRESS>:49152/uuid-fdfabe96-b6c6-92ff-31dd-dca63239e1f0/description.xml has 7 services

I have no idea how this is possible, as I delete the old setup every time and replace it with the new one on Github.
But it certainly explains why you don't see any changes...

I downloaded the setup from Github and it installed the latest version, showing the correct messages in the log.
I replaced it again, but this time the app should show the version 1.12.3-b3 in the title bar:

I have no idea if Bubble or Chromecast support changing the volume, reading it out seems to work though.
Looking at your screenshot, I see that the SSDP interval is extremely short, if you're on shaky WiFi connections it might interfere with the streaming.
I will wait a couple of days before releasing this officially, in case you find any problems.
One restriction when using devices sharing the same IP address: if you start streaming from swyh-rs, and terminte it with some other means (breaking the streaming connection from the device end), swyh-rs is not able to reflect this on the button, it will remain lighted even though the device is no longer streaming.

Oh, and thanks for testing this and bearing with my attempts to fix it. Much appreciated!

Fixed with release 1.12.3.


Update variation property to account for multiple alleles

Addresses issue #57. In order to capture zygosity (and genotype) in CaseLevelVariants completely, we need to be able to account for the situation where a caseLevelVariant contains two alternate alleles, neither of which is the reference. I would recommend requiring the first element of a variations array, element 0, to be the reference allele, and subsequent alternate alleles to be numbered accordingly. Then zygosity can be represented as in the beacon-ri implementation:
            "caseLevelData": [
              {
                "zygosity": {
                  "label": "0/1",
                  "id": "GENO:GENO_0000458"
                },
                "biosampleId": "HG03770"
              }
            ],

with the labeling schema extended in the style of VCF, with values like 1/2.

More specifically, this allows for the specification of the GENO:0000402 value for zygosity:

compound heterozygous: A heterozygous quality inhering in a single locus complement comprised of two different varaint alleles and no wild type locus. (e.g.fgf8a/fgf8a)


[Instagram] RegexNotFoundError while downloading a reel

Checklist

[X] I'm reporting a broken 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
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
India
Description
Getting RegexNotFoundError with instagtam while downloading https://www.instagram.com/p/CeDdG5TOldD/ . Using cookies and verified that they are still valid.
Verbose log
[Instagram] CeDdG5TOldD: Downloading webpage
WARNING: [Instagram] unable to extract username; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
ERROR: [Instagram] CeDdG5TOldD: Unable to extract video url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
Ignoring exception in on_command_error
Traceback (most recent call last):
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 642, in extract
    ie_result = self._real_extract(url)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/instagram.py", line 415, in _real_extract
    video_url = self._og_search_video_url(webpage, secure=False)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 1340, in _og_search_video_url
    return self._html_search_regex(regexes, html, name, **kargs)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 1235, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags, group)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 1226, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
yt_dlp.utils.RegexNotFoundError: Unable to extract video url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 1395, in wrapper
    return func(self, *args, **kwargs)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 1465, in __extract_info
    ie_result = ie.extract(url)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 668, in extract
    raise type(e)(e.orig_msg, **kwargs)
yt_dlp.utils.RegexNotFoundError: [Instagram] CeDdG5TOldD: Unable to extract video url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/.heroku/python/lib/python3.9/site-packages/discord/ext/commands/core.py", line 85, in wrapped
    ret = await coro(*args, **kwargs)
  File "/app/bot.py", line 725, in dl_yt
    await in_dl_instance.downloadVideo(ctx, url, copt, usrcreds)
  File "/app/NeodiumUtils/download.py", line 203, in downloadVideo
    raise e
  File "/app/NeodiumUtils/download.py", line 195, in downloadVideo
    info = await ydl_async(url, ops, False)
  File "/app/NeodiumUtils/download.py", line 51, in ydl_async
    result = await loop.run_in_executor(pool, y_dl, url, ytops, d)
  File "/app/.heroku/python/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/app/NeodiumUtils/download.py", line 47, in y_dl
    info = ydl.extract_info(url, download=d)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 1386, in extract_info
    return self.__extract_info(url, self.get_info_extractor(ie_key), download, extra_info, process)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 1413, in wrapper
    self.report_error(str(e), e.format_traceback())
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 936, in report_error
    self.trouble(f'{self._format_err("ERROR:", self.Styles.ERROR)} {message}', *args, **kwargs)
  File "/app/.heroku/python/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 879, in trouble
    raise DownloadError(message, exc_info)
yt_dlp.utils.DownloadError: ERROR: [Instagram] CeDdG5TOldD: Unable to extract video url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

probably a duplicate but can't verify if its same as #3077


Add test of flutter create --plugin

Resolves https://github.com/flutter/flutter/issues/9454

yay tests :-)
LGTM


Update Privacy Statement and Imprint

According to data privacy experts, we should improve the privacy statement and describe the legal basis of data collection in Artemis better based on DSGVO.
The imprint statement is now part of Artemis. Linking to an external source is not necessary any more. It can be changed by providing a custom html file in the public folder (like the privacy statement)
The Accept terms option is now deactivate by default because acceptance is not necessary in terms of education and examination (as this is the duty of the corresponding university and it does not really makes senes that students can decline to it): Artemis admins who absolute want their users to accept terms can still opt-in in the yml files.

Note:

After recommended by the data privacy expert, I adapted the privacy statement from https://dsms.datenschutz.tum.de/privacy-policy
After recommended by the data privacy expert, I adapted the new imprint from https://dsms.datenschutz.tum.de/imprint

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.

Steps for Testing

Read the privacy statement
Read the imprint
Try to adapt both files in the public folder
Log in to Artemis

Code reviews are highly appreciated as well.
Screenshots

Thanks, I fixed the issues and also removed a paragraph that was not necessary and was found in the review of the data privacy expert. If there are no more issues, I think we are good to go 👍

Thanks, I fixed the mention typos.

Thanks again, I fixed the remaining typos. Let me know if you find even more 👍

... und das Bayerische Fernprüfungserprobungsverordnung (BayFEV).
das -> die
This really is the last one I found 😅 🙈

thanks, fixed.


Duplicate values on unstack

What happened?
I unstacked a dataset and got values I didn't expect. It turns out that, when unstacking, my dataset had multiple values for the same index. This is clearly a case of user error, but it silently passed.
What did you expect to happen?
A warning or error would be raised to say, "this isn't going to work".
Minimal Complete Verifiable Example
import datetime as dt
import xarray as xr

ds = xr.DataArray(
    [[1, 2, 3], [4, 5, 6]],
    dims=("lat", "time"),
    coords={"lat": [-60, 60], "time": [dt.datetime(2010, 1, d) for d in range(1, 4)]},
    name="test",
).to_dataset()

ds = (
    ds.assign_coords(
        {
            "month": ds["time"].dt.month,
            "year": ds["time"].dt.year,
        }
    )
    .set_index(time=["month", "year"])
)
ds = ds.unstack("time")

# the output only has 2 values, which isn't what I expected
ds["test"].data

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
No response
Anything else we need to know?
It's not clear to me where the error is. It might just be that this particular order of operations leads to a case that isn't otherwise caught. Looking at intermediate output, I thought the error was in unstack but maybe it's more complex than that...
Environment

INSTALLED VERSIONS
commit: e678a1d7884a3c24dba22d41b2eef5d7fe5258e7
python: 3.8.13 | packaged by conda-forge | (default, Mar 25 2022, 06:04:14)
[Clang 12.0.1 ]
python-bits: 64
OS: Darwin
OS-release: 21.5.0
machine: arm64
processor: arm
byteorder: little
LC_ALL: None
LANG: en_AU.UTF-8
LOCALE: ('en_AU', 'UTF-8')
libhdf5: 1.12.2
libnetcdf: 4.8.1
xarray: 0.1.dev4312+ge678a1d.d20220928
pandas: 1.5.0
numpy: 1.22.4
scipy: 1.9.1
netCDF4: 1.6.1
pydap: installed
h5netcdf: 1.0.2
h5py: 3.7.0
Nio: None
zarr: 2.13.2
cftime: 1.6.2
nc_time_axis: 1.4.1
PseudoNetCDF: 3.2.2
rasterio: 1.3.1
cfgrib: <IP_ADDRESS>
iris: 3.3.0
bottleneck: 1.3.5
dask: 2022.9.1
distributed: 2022.9.1
matplotlib: 3.6.0
cartopy: 0.21.0
seaborn: 0.12.0
numbagg: 0.2.1
fsspec: 2022.8.2
cupy: None
pint: 0.19.2
sparse: 0.13.0
flox: 0.5.9
numpy_groupies: 0.9.19
setuptools: 65.4.0
pip: 22.2.2
conda: None
pytest: 7.1.3
IPython: 8.5.0
sphinx: None

Thanks for the report @znichollscr.
Maybe we should check pandas.MultiIndex.is_unique in Dataset.unstack() like in Dataset.from_dataframe()?
df = ds.drop_vars("lat").to_dataframe()

xr.Dataset.from_dataframe(df)
# ValueError: cannot convert a DataFrame with a non-unique MultiIndex into xarray

Maybe we should check pandas.MultiIndex.is_unique in Dataset.unstack()

Better to check this in PandasMultiIndex.unstack() actually.

Ok great thanks, solutions sound good

I just stumbled over this and opened #8737. Happy to get a review.


New Actions type is overly restrictive

Describe the problem
I took a stab at upgrading to SvelteKit post #5748.  There's a fundamental regression of capability with the Action type compared to how POST page endpoints worked previously.  Before 5748 landed, the returned body of the POST handler would be layered on top of the body of the GET handler.  This allowed the POST handler to influence the rendering of the page component by providing additional data.
The Action type allows something similar by returning the error value, but it's limited to the Record<string, string> type which doesn't allow passing complex data back to the page component.
Describe the proposed solution
I'd suggest replacing error with form_result (action_result?)  and loosening the type from Record<string, string> to something like Record<string, any> or the old JsonValue.
Alternatives considered
Alternative 1: Serialized JSON Hack
Theoretically you could pass serialized json as one of the string values in error: Record<string, string> but that obviously feels like a hack counter to the spirit of what error is supposed to represent.
Alternative 2: External Data Passing
The developer can externally store the complex data somewhere and manually look it up the next time the page's load function is invoked.  (Think cookies or memory store).  This external storage method adds complexity to the form handling process.
Importance
would make my life easier
Additional Information
This "pass data from the POST handler to the page component" functionality is important for how I've implemented the "form-local actions" I described in https://github.com/sveltejs/kit/discussions/5875#discussioncomment-3410368

This is meant as a short-term fix until whenever the result of #5875 lands.  Ideally that solution also accommodates this use case.

The main issue (regression in capability) is fixed.
I'm guessing you're looking at the s/error/form_result as the possible second issue.  It's definitely not a blocker and not something I'd push for changing right now, especially considering 5875 is coming down the pipe.  My thinking there is that since the Action type allows for setting the status (including possibly a 2xx code), error is not the semantically correct name - after all a 2xx status does not imply an error.
If that's a change the maintainers are interested in pursuing, I'd be happy to open another issue for tracking.  Otherwise I can work with a 2xx returning an error as long as I can pass complex data types through

Thanks for the answer, closing then. After the form discussion proposal is finalized and implemented, you can revisit this and open an issue if you like.


Bug in langchain_community/embeddings/huggingface_hub.py  HuggingFaceHubEmbeddings.embed_query

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.

Example Code
from langchain_community.embeddings import HuggingFaceHubEmbeddings
url = "https://svvwc5yh51gt1pp3.us-east-1.aws.endpoints.huggingface.cloud"
text = "You do not need a weatherman to know which way the wind blows"
token = "<my_token>"
embeddings = HuggingFaceHubEmbeddings(
model = url,
huggingfacehub_api_token=token
)
qembed = embeddings.embed_query(text)
Description
The code above should call my HuggingFace inference endpoint and generate an embedding.  Instead, it throws:
Traceback (most recent call last):
File "/Users/jraby/python/hfhub/callhub2.py", line 29, in
qembed = embeddings.embed_query(text)
File "/opt/homebrew/lib/python3.10/site-packages/langchain_community/embeddings/huggingface_hub.py", line 109, in embed_query
response = self.embed_documents([text])[0]
KeyError: 0
The "[0]" at the end of line 109 is incorrect.  self.embed_documents returns JSON, -not a list.  The first node in the JSON is 'embeddings', and it contains the list of embedding arrays.
I believe that this line:
response = self.embed_documents([text])[0]
Should be replaced with this:
response = self.embed_documents([text])['embeddings'][0]
This resolves the problem for me.
System Info
Platform = MacOS
python version  = 3.10
pip3
huggingface_hub (0.20.2)
Related Components

[ ] LLMs/Chat Models
[X] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

@jrabyIBM
Did you run it on you machine without amazon endpoint locally ?
Sorry, a bit off-topic, but I'm also facing some difficulties when running HF with Langchain on pretty similar task.
It seems they are more focused on collaborating with OpenAI than on local inference.
fyi, my issue

@tempdeltavalue no, I have not run it against a local model.  I've just update the comment above.  The fix should be to replace:

response = self.embed_documents([text])[0]
with this:
response = self.embed_documents([text])['embeddings'][0]

in langchain_community/embeddings/huggingface_hub.py.  Making this change resolves the problem for me.

@jrabyIBM  Did you try SelfHostedHuggingFaceEmbeddings in langchain_community/embeddings/self_hosted_hugging_face.py. That might fix your issue.

@keenborder786 Thanks for the suggestion.  However this is clearly a bug, which prevents use of the HuggingFaceHubEmbeddings class.  It may be that some other langchain classes are not affected by this bug, but that doesn't change the fact that HuggingFaceHubEmbeddings is broken.
The embed_query method calls the embed_documents method, which returns JSON like this:

{
'embeddings':
[
[0.08688841015100479,
...
]
]
}

The current code then calls:
response = self.embed_documents([text])[0]
The line of code throws a KeyError.  It is incorrect code for processing the JSON that is returned.  The correct code should be:
response = self.embed_documents([text])['embeddings'][0]
I need to use HuggingFaceHubEmbeddings to use a HuggingFace inference endpoint.

@javi-aranda the following code is working fine for me, if their was a bug then the following should also have not worked.

from langchain_community.embeddings import HuggingFaceHubEmbeddings
text = "You do not need a weatherman to know which way the wind blows"
embeddings = HuggingFaceHubEmbeddings(
model = 'TinyLlama/TinyLlama-1.1B-Chat-v1.0',
huggingfacehub_api_token=''
)
qembed = embeddings.embed_query(text)

@keenborder786 that is very similar to the code that throws a KeyError exception for me.  I think that the difference is that you are specifying an actual model (which I think means that you are accessing a self-hosted local model?) whereas I am specifying a URL in the model field, which tells langchain that this is a HuggingFace hosted inference model.
I think your experiment is helpful.  It clarifies that the bug only occurs when accessing a remote, HuggingFace inference endpoint via HuggingFaceHubEmbeddings.


Add support for pip

Modern Python comes with pip bundled in, making it easy to install the library.
ParaText could be installed using pip. It could be hosted on git or, better, on pypi.

+1 👍

Yes, it would be really great.
You don't have to host it on pypi yet.
You just need to create a setup.py, see this small tuto
It would enable us to do pip3 install git+https://github.com/wiseio/paratext


Enable Missing loaders from esbuild

Is your feature request related to a problem? Please describe.
Add configuration and middleware for the missing middleware (that is not ts/jsx/tsx) for the dev server

text - https://esbuild.github.io/content-types/#text
binary - https://esbuild.github.io/content-types/#binary
base64 - https://esbuild.github.io/content-types/#base64
data url - https://esbuild.github.io/content-types/#data-url
external files - https://esbuild.github.io/content-types/#external-file

At compile time we have support for these thanks to esbuild but at devtime we need to add middleware for it
Describe the solution you'd like
Add middleware like the one in the Middleware module inside Server.fs that do the correct transform so the server emulates esbuild's behavior and can be used both in the dev server and at build time

partially addressed from #40 we now need to enable these as middleware


Add captdns to extras

Responds to any DNS request with the access point IP. To use this, you also need to enable router and DNS server option fields in dhcpserver (https://github.com/SuperHouse/esp-open-rtos/pull/421). Should I create an example of how to configure this?
Ported from Sprite_tm's libesphttpd, upstream at http://git.spritesserver.nl/libesphttpd.git/

Closing/reopening to trigger CI build

Thanks @flannelhead. I would really like to see an example on how to use this.

@kanflo Thanks for reminding of this. Actually now I remember why I didn't add an example yet. Any meaningful, working example would depend on the ability to advertise the soft AP IP as a router via DHCP extra fields. Support for this in dhcpserver is added in https://github.com/SuperHouse/esp-open-rtos/pull/421 but also in ourairquality's patchset https://github.com/SuperHouse/esp-open-rtos/pull/437.
If eventually either of these gets merged, I'll be able to write an example, perhaps by expanding the access_point example which is the most logical location for such an example.

Great @flannelhead, looking forward to it.

This will be superseded by https://github.com/SuperHouse/esp-open-rtos/pull/458 if that PR gets merged - it contains the very same captive DNS code.

https://github.com/SuperHouse/esp-open-rtos/pull/458 landed - closing this.


fix: make sortable table header chevron clickable

Description

Add span beside column header to show sort chevron
Updates column header style to show a chevron when the header is hovered

Which issue(s) does this PR relate to?

Closes #856

Testing

Tested locally on storybook
video: https://www.loom.com/share/7c16b244c69c43d28a08d1ebbcf4d156
Added test case to stimulate the behaviour

Trade-offs

Screenshots

Checklist

[ ] If any new components were added, there are exported from packages/index.ts
[x] This PR is associated with a JIRA and mentions in the commit message footer ("Closes …")
[ ] This PR contains breaking changes and states in the commit message body ("BREAKING CHANGE: …")
[x] I have reviewed the changes and provided detail to the sections above

It's working well!  Tested it out in Storybook ✅

@nataliepina please check now, I have rebased and fixed snapshot

@nataliepina please check now


Enhancement request: threaded inserts support

I would like to have those things as on the image, which can be used for threaded inserts or just as screw hole. On the lid and/or on the base.
I want to mount box on a bicycle, so I need some reinforcement.

General questions and enhancements should be posted as a comment on my website at this post.

Those words were here, on GitHub without referencing your Website. If you set your rules, you have to announce them in a place, where they apply. This is a kind of respect to people. Telling them about some rules only then, when they act - it's a clear disrespect.
And if you deal with people without respect, don't expect the respect from them.
You can do my request or not, it doesn't matter for me anymore.


Update example to use internal FileProvider, autolink works perfectly on RN60

This is built on #567 and relies on the work from #490 so that autolink works perfectly and should make #549 provably solved, as the example autolinks and works with RN60
If #567 is approved this just has one commit - so this commit is the one to review: https://github.com/react-native-community/react-native-share/pull/570/commits/354bcb464d24a044e761beab572f2ec876536c88
I'll rebase the PR and re-push if/when #567 goes in
Overview

Test Plan

rebased/pushed after responding to @friederbluemle feedback on #567

Just gave a quick review after the rebase and it looks good to me. IM going to test this today and merge if everything runs fine.

Just tested the example app here and it runs without any problem. If anyone got problems with the example app after this, please let us know. Also, thanks for updating the example app @mikehardy :smile:

And now my weekly github security alerts email will be (I think) empty :-). Cheers