Use export default a module but build a Unexpected statement

Describe the bug
Describe the bug

I have a card component like this:

card.vue:
<template>

this is a card components

</template>

Then imported like this:

index.js:
import Card from "./card.vue";

Card.install = (app) => {
  app.component(Card.name, Card);
};

export default Card

There is my vite build options:

vite.config.js
export default defineConfig({
  build: {
    publicDir:false,
    minify: false,
    lib: {
      entry: "./components/card/index.js",
      formats: ["es"],
    },
    rollupOptions: {
      external: ["vue"],
      output: [
        {
          format: "es",
          entryFileNames: "[name].js",
          preserveModules: true,
          preserveModulesRoot: "components",
          dir: "es",
        }
      ],
    },
  },
  plugins: [vue()],
});

After completing these operations. I got a es/card.js and es/index.js. The es/index.js like this:
import Card from "./card.js";
import { default as default2 } from "./card.js";
Card.install = (app) => {
  app.component(Card.name, Card);
};
export {
  default2 as default
};

It exported default2. Is not Card, so my origin install  function was lost , there is any problem with my configuration ?
Reproduction
https://github.com/yangzongliu/base-components-library
Steps to reproduce

pnpm i
pnpm run build3

System Info
System:
    OS: macOS 11.4
    CPU: (8) arm64 Apple M1
Binaries:
    Node: 16.15.0
    npm: 6.14.12
    pnpm: 7.17.1

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[ ] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[ ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[x] The provided reproduction is a minimal reproducible example of the bug.

https://github.com/vitejs/vite/issues/13107

It exported default2. Is not Card, so my origin install function was lost , there is any problem with my configuration ?

It is not lost.
If you run node foo/use.mjs in this stackblitz project, you can see install function exists.
https://stackblitz.com/edit/github-26piu2?file=foo%2Fuse.mjs

It exported default2. Is not Card, so my origin install function was lost , there is any problem with my configuration ?

It is not lost. It's a valid JS. If you run node foo/use.mjs in this stackblitz project, you can see install function exists. https://stackblitz.com/edit/github-26piu2?file=foo%2Fuse.mjs

Oh, thanks for your reply. Yes it works, as you can see i'm doing a components library demo. For the questions I raised, i fund if using my library in a webpack project, it will not find function install, but in a vite project, it will work. It is vite build esm product does not support webpack project or is there a problem with my understanding？Look forward to your reply！

It exported default2. Is not Card, so my origin install function was lost , there is any problem with my configuration ?

It is not lost. It's a valid JS. If you run node foo/use.mjs in this stackblitz project, you can see install function exists. https://stackblitz.com/edit/github-26piu2?file=foo%2Fuse.mjs

Hi, i found the problem where. same vite options when i use vite@4 & @vitejs/plugin-vue@4 , will not compiler default2

if using my library esm product in a webpack project, it will not find function install

I can't say anything without a reproduction of that, but I guess that's a bug in Webpack as this is a valid JS code.


Issues with API access token error message

If a user attempts to launch lichs without an API key, the following error is displayed:
The API-key is either empty or wrong. Please run the command 'lichess' and input your API-key as a second argument, i.e 'lichess <api_key>'. If you need more help, please see the instructions in the Github README:
https://github.com/Cqsi/lichess_terminal#how-to-generate-a-personal-api-token

But:

The command is lichs not lichess.
The header-tied link is https://github.com/Cqsi/lichs#how-to-generate-a-personal-api-key not https://github.com/Cqsi/lichess_terminal#how-to-generate-a-personal-api-token.
Lichess refers to the API keys as "API access tokens" not "API-keys." This isn't crucial to change, but could help consistency for users.

Thank you, this was an easy fix!


[Improvement-13146][Task-Relation] Support calling taskRelation api t…

…hrough projectCode and processCode to query taskCode

Purpose of the pull request
Support calling taskRelation api through projectCode and processCode to query taskCode
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This change added tests and can be verified as follows:
Added org.apache.dolphinscheduler.api.controller.ProcessTaskRelationControllerTest#testQueryProcessTaskRelation to verify the change.
Added org.apache.dolphinscheduler.api.service.ProcessTaskRelationServiceTest#testQueryProcessTaskRelation to verify the change.
(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

Could you please link this pr to an issue and describe why do you want to do that?

The issue is https://github.com/apache/dolphinscheduler/issues/13146,and the reason is when modifying the workflow definition, if I do not know the taskcode, I will not be able to modify the workflow definition. Therefore, can DS support calling the api through projectCode and processCode to obtain the corresponding taskCode, so that I can easily modify it.

The issue is https://github.com/apache/dolphinscheduler/issues/13146. And the reason is when modifying the workflow definition, if I do not know the taskcode, I will not be able to modify the workflow definition. Therefore, can DS support calling the api through projectCode and processCode to obtain the corresponding taskCode, so that I can easily modify it.

We can use queryProcessDefinitionByCode to query the process definition detail by projectCode and processDefinitionCode. So I think this pr is unnessnary. Feel free to correct me if I'm wrong.

The issue is https://github.com/apache/dolphinscheduler/issues/13146. And the reason is when modifying the workflow definition, if I do not know the taskcode, I will not be able to modify the workflow definition. Therefore, can DS support calling the api through projectCode and processCode to obtain the corresponding taskCode, so that I can easily modify it.

We can use queryProcessDefinitionByCode to query the process definition detail by projectCode and processDefinitionCode. So I think this pr is unnessnary. Feel free to correct me if I'm wrong.

I think queryProcessDefinitionByCode returns too much redundant information for me, which will take a long time. I just want processTaskRelation info

@SbloodyS Hello, can you help me merger it.

I think queryProcessDefinitionByCode returns too much redundant information for me, which will take a long time. I just want processTaskRelation info

I don't think this is necessary because it is an open source project, not a customized project. cc @ruanwenjun @zhongjiajie @caishunfeng @EricGao888

@LiJie20190102 BTW, please submit PR to dev branch instead of xxx-prepare. We always submit PR to dev branch for the first choice and furthermore, we usually do not accept new features into a xxx-prepare branch.

This is my first time to contribute code. I especially hope to contribute code to ds. Please give me a chance. I will contribute more code in the future. @SbloodyS @EricGao888 @ruanwenjun @zhongjiajie @caishunfeng

I think queryProcessDefinitionByCode returns too much redundant information for me, which will take a long time. I just want processTaskRelation info

I don't think this is necessary because it is an open source project, not a customized project. cc @ruanwenjun @zhongjiajie @caishunfeng @EricGao888

I'm +0 on this. Not -1. So if others think it's OK, please continue.

I think queryProcessDefinitionByCode returns too much redundant information for me, which will take a long time. I just want processTaskRelation info

I don't think this is necessary because it is an open source project, not a customized project. cc @ruanwenjun @zhongjiajie @caishunfeng @EricGao888

I'm +0 on this. Not -1. So if others think it's OK, please continue.
If others think it is OK, I will submit the code to the dev branch as soon as possible. @ruanwenjun @zhongjiajie @caishunfeng @EricGao888

@ruanwenjun @zhongjiajie @caishunfeng @EricGao888
Hello, can I submit my improve to the dev branch? If not, I will close the PR


Optional encoding kwarg for for partition_{html, email, text}

The goal of this issue is to add an optional encoding kwarg that allows users to pass in the encoding to bricks the process plain text files (partiton_html, partition_email, and partition_text). Currently, if you want to use a specific encoding, you need to read in the file yourself and pass it in as text, as shown below.
with open("example-docs/example-10k.html", "r", encoding="utf-8") as f: #also passed encoding here
    text = f.read()
elements = partition_html(text=text)

exactly, got same problem. encoding parameters should be pass to the wrapper.

I believe this has been implemented successfully in #339, which is included in the latest 0.5.3 release. I would consider upgrading your unstructured to take advantage of this new functionality.
This issue can be closed, I think.

Yep, this one should be closed now.


Symbol not found:

I get the following error when trying to run the app on my macbook pro 2015 with MacOS Monterey.
I keep having to give ytsearch security permisson to run. Finally it just shows this error when search
[5:01:25.866 pm] Logging Started...
[5:01:28.485 pm] YouTube Search[Script Filter] Queuing argument 'learn php'
[5:01:28.561 pm] YouTube Search[Script Filter] Script with argv 'learn php' finished
[5:01:28.565 pm] ERROR: YouTube Search[Script Filter] Code 134: dyld[9068]: Symbol not found: (_$s10Foundation12URLQueryItemV4name5valueACSSh_SSSghtcfC)
  Referenced from: '/Users/me/Applications/Alfred/Alfred.alfredpreferences/workflows/user.workflow.6844F6D8-4A33-4D6C-BEFE-F384209C2ABC/ytsearch'
  Expected in: '/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation'

You need Ventura to run the latest workflow version although v0.1.0 should be compatible with Monterey.

Great that works


Vim9: when debugging, automatic continuation lines are ignored

Describe the bug
In Vim9 script, when debugging a function, automatic continuation lines are ignored, which makes it harder to know which commands Vim is executing.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        var d = {
            a: 1,
            b: 2,
            c: 3,
        }
    enddef
    debug Func()
EOF
)

Press s then Enter, to execute the debugging command step and step into the function Func().
  Now, it joins too many; that is, it joins a subsequent comment:
vim9script
def Func()
    var d = {
        a: 1,
        b: 2,
        c: 3,
    }
    # some
    # very
    # long
    # comment
enddef
debug Func()

# after >step
line 1: var d = {  a: 1,  b: 2,  c: 3,  }  # some  # very  # long  # comment
                                           ^-------------------------------^
                                                        noise

This is especially noticeable when there is a long comment.  If the comment is too long, it seems Vim stops at some arbitrary length.

There is also the case of closures:
vim9script
def Func()
    def Inner()
        eval 1
        eval 2
        eval 3
    enddef
enddef
debug Func()

line 1: def Inner()  eval 1  eval 2  eval 3  enddef

I don't know what's best.  If we can't get each line separately, maybe they should be separated with bars?
line 1: def Inner()  | eval 1 | eval 2 | eval 3 | enddef
                     ^        ^        ^        ^

In legacy, only the header is printed:
fu Func()
    fu Inner()
        eval 1
        eval 2
        eval 3
    endfu
endfu
debug call Func()

line 1: fu Inner()

It's better, but there is yet another corner case.  If the comment is moved inside the dictionary, Vim truncates too early:
vim9script
def Func()
    var d = {
        a: 1,
        # comment
        b: 2,
    }
enddef
debug Func()

# after executing >step
line 1: var d = {  a: 1,

In legacy, the comment is removed, and the dictionary is printed in its entirety:
fu Func()
    let d = #{
    \    a: 1,
    "\ comment
    \    b: 2,
    \}
endfu
debug call Func()

# after executing >step
line 1: let d = #{    a: 1,    b: 2,}

It's better, but there is yet another corner case.  If the comment is
moved inside the dictionary, Vim truncates too early:
vim9script
def Func()
    var d = {
        a: 1,
        # comment
        b: 2,
    }
enddef
debug Func()

# after executing >step
line 1: var d = {  a: 1,

It's not perfect, but it is enough to see where you are, what the next
command is.
Passing the line range to the debug command is a bit of a hassle,
because the debug instruction is generated before the lines are parsed.
I rather not spend too much time on this and make the code a bit more
complicated.
--
hundred-and-one symptoms of being an internet addict:
7. You finally do take that vacation, but only after buying a USB modem
and a laptop.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


[Map] DM-Checkmate_v-=CoN=-

The download link from http://ut99maps.gamezoo.org  resolves to the website and NOT to the file/zip.

URL: https://unrealarchive.org/maps/unreal-tournament/deathmatch/C/dm-checkmate_v-con-_f332ff85.html
Hash: f332ff850ec745483a85f88e94823fbd6ec679be
Current name: DM-Checkmate_v-=CoN=-

It's also a dead site link. Removing.


Update README.md - add Contributors

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 73.41%. Comparing base (197ede8) to head (5a5cf18).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #189      +/-   ##
==========================================
- Coverage   73.52%   73.41%   -0.12%
==========================================
  Files          32       32
  Lines        1809     1809
==========================================
- Hits         1330     1328       -2
- Misses        479      481       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


The bot needs avatar

Hello!
Could you please add some avatar to the bot user so it can be distinguished from others?

Added one, image credit @ Theo


update: adds npm badge, annotation for code block

Overview
This PR,

adds npm package badge for @hotjar/browser.
adds javascript label for code-blocks in README

This is mostly a formatting update in the README.
Changes Introduced

Formatting changes  in README.md

Thanks!

cc @arrwhidev

Thank you for the PR :)


enhancement: Adds a more readable nestjs example

I just made a more readable nestjs example based on #41

@Goufix i don't like the fact that you have to call
BullModule.registerQueue({ name: 'person' })

twice, in order to pass it to the monitor. there is definitely something wrong with that.

@Goufix i don't like the fact that you have to call
BullModule.registerQueue({ name: 'person' })

twice, in order to pass it to the monitor. there is definitely something wrong with that.

I think que only way to not call twice is calling registerQueue inside de root AppModule. What is not considered a good pratice. But I'm open to suggestions.


Implement ICloneable for sgen objects

This would allow to copy and modify fields easily.

Implementing ICloneable is now actively discouraged in the MSDN reference manual. The reason seems to be ambiguity around whether Clone should perform a deep or shallow copy.
For C# record types the auto-generated implementation now provides a shallow-copy constructor and a new with operator which allows creating modified copies of existing record objects.
#15 and #13 provide the first half of such an implementation, by introducing copy constructors for all generated classes and an overload for triggering copy on input. This allows using the InputMapping operator to pull any desired properties from the input, while allowing specification of other properties.
Later we can take this approach one step further either by making the copy constructor public, or exposing a Copy method to allow emulating something similar to the with operator. At the moment I feel we should experiment a bit first with the workflow-based functionality to get a better feel about future requirements before committing one way or the other.

Closing this for now in favor of #13.


Using console.log in email/index.ts does not log anything

While digging into https://github.com/successor-software/mailing/issues/89 it was confusing to not be able to log anything from email/index.ts.

Hm, I'm seeing it work on my end. Perhaps the file wasn't imported yet? Here's what I see when the index file with console.log  gets required by mailing to send an email...

I discovered that this is due to having "isolatedModules": true in my root tsconfig.json under compilerOptions. If I comment that out, the console logging works. I discovered this by running:
yarn ts-node -e 'console.log("test")'

And if isolatedModules is enabled, there is an error message:
[eval].ts:1:1 - error TS1208: '[eval].ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

1 console.log("test")
  ~~~~~~~

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I don't get any error when running npx mailing but at least it makes sense! I only wanted this while figuring out https://github.com/successor-software/mailing/issues/89 so I'll close this as it seems out of scope of mailing although good to know.

got it, thanks for digging in. fyi i'm adding dotenv to the mailing cli right now and will have a new release out later today that will hopefully fix the prob you're having in #89.


SelectAll and Exclude for select query

Problem
Hi, not a problem here, fine with Prisma select now, work as my dream. Just wonder can you add this function?
Suggested solution
prisma.user.findMany({
select:{
    selectAll:true
    exclude:{password:true}
}
})

There is a popular feature request about this at https://github.com/prisma/prisma/issues/5042 - so I am going to close this issue here as a duplicate. Add a 👍 on the other issue @IRediTOTO.


route-emitter is logging private keys

In line:
https://github.com/cloudfoundry-incubator/route-emitter/blob/daf24b6488df7421809e14e1c135fa5b0cb71cf5/watcher/watcher.go#L522
Example:
<14>2016-02-17T23:07:47.503647+00:00 <IP_ADDRESS> vcap.route-emitter [job=diego_brain-partition-
de8bcce8d1b7d3d32e02 index=0] {"timestamp":"1455750467.503602505","source":"route-
emitter","message":"route-emitter.watcher.handling-desired-delete.complete","log_level":1,"data":
{"process-guid":"9534a282-6968-4ffa-92b3-5d649f2f4977-b26bafb5-495e-486e-9e5d-
02a9620769db","routes":{"cf-router":[{"hostnames":[],"port":8080}],"diego-ssh":
{"container_port":2222,"host_fingerprint":"65:97:cb:0d:c1:46:e2:fb:53:67:70:e1:85:37:1d:2f","private_key":
"-----BEGIN RSA PRIVATE KEY——\nMIICXQxxxxxxxx

Never mind we were looking at an older diego version.

Thanks, @roxtar! Yep, we fixed this in https://github.com/cloudfoundry-incubator/route-emitter/commit/37b053729c6e7c64af313d571c51fd43363b8d86.


Update Travis config to use Bundler 1.14.2

@tarcieri nope... 1.14.2 did not fixed the issue...

Yeah, issue still not fixed (it's not only us affected): https://github.com/bundler/bundler/issues/5349

Looks like they might have a path to a real fix though. I'll update for 1.14.3 when it comes out


make api_domain optional parameter in Client class

class Client:
    def __init__(self, token, api_domain='https://connection.keboola.com'):
        pass

so that you can init the client like this
client = Client('your-token')

What are the alternative api_domains anyway?

I wouldn't recommend to add default value there, connection URL should be always passed otherwise integration won't wok against other stacks.
At the moment we have two KBC stacks:

us-east-1 - https://connection.keboola.com
eu-central-1  - https://connection.eu-central-1.keboola.com/ (in BETA now)

eq.  if you are using this client in KBC docker extension you should set api endpoint from KBC_URL env variable https://developers.keboola.com/extend/common-interface/environment/#environment-variables

Ah okay


Status overview components

Examples of statusses

Coming
Preview
Stable
Show notification dot in navigation when something changed status

### Tasks
- [ ] Show status badge in component navigation documentation website
- [ ] Show status badhe in hero of component detail page
- [ ] Show status in storybook as well?

add a "dateStatusChanged" property to <component-name>.json so we can show a dot or star, or something else to indicate that the STATUS of the component has changed: Coming->Preview->Stable. To trigger users to look at which components they can start using (either in preview or stable).


Feature: Figma API integration

We'd love to be able to:

pull meta data about each icon stored in Figma
possibly export all of the icons and save them in our dir structure + make a ZIP file

Ideally it would run with yarn update-figma-icons or something like that.
There are two options:

Make a custom Figma plugin. I've never done this, so I'm not sure how much work it would be.
Use the description field and import that. Steven has already proposed a syntax for this second approach (seems like the easier approach)

See Slack conversation

I would suggest that we use that Description field for a verbal description of the icon (like alt text, eg. “Person with lab coat and stethoscope”), and a comma-delimited list of tags in square brackets. So, a description of the doctor_female icon would be something like: Woman with stethoscope [doctor, physician, woman, practitioner]

See API documentation https://www.figma.com/plugin-docs/api/ComponentNode/#description

Note: We should create a tag like dhis2:file_name for every icon that represents a DHIS2 icon. Then we can change the actual filename to be consistent, use hyphens, and be meaningful

I've got a start of this working.

I'm using the https://www.npmjs.com/package/figma-js package, but this might be even better? I'm not that familiar with GraphQL thugh https://github.com/braposo/figma-graphql


Isolate search to a specific Jira ticket

How do we isolate and verify fields on a specific Jira Issue (ticket)?
@JosephDSchwartz

You can use the project-names-to-search, issue-types-to-search, search-field-id, and search-value parameters to find the ticket you want. For instance, the use case behind the creation of this action was searching for a deployment task with a specific version number in the "Proposed Build" field.

I am wanting to search by ticket number, like WE-1234.  I want to verify that a specific ticket number has the properties desired.  How do I do that?
issue-types-to-search seems to be asking for issue type, not issue key.

There isn't a way to search by the issue key like you can in https://github.com/im-open/transition-jira-tasks-by-query. This action could be modified to do that, but that's not a current capability.


Improvement: Replace react-images

Informations
https://github.com/jossmac/react-images

This package hasn't been properly maintained in a long time and there are much better options available.

This task has been taken over by https://redmine.weseek.co.jp/issues/121095.


az apim release

Hello
I'd like to know the release plan for az apim (will it be released?), as it still throws this message when used:
Command group 'apim' is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus
I need to use it in a production environment.
Thanks.

@sjuarezgx Apologies for the late reply. We are looking into this and we will update once we have more details.
@adrianhall Could you please let us know when will the az apim CLI command be ready for production use ? Awaiting your reply.

Hello,
We are currently working on that specific release!  The next release will be GA, not experimental.
#please-close

The service team is not in control of the release schedule for the az CLI.  As a result, I do not have that information.

Ok, thank you.

This change will be released in July 5th.


What should the copyright header of each file be set to?

We should align on whether the copyright of each file should be empty, be based on the contributor, or OpenSSF as an organization. I'm leaning toward OpenSSF.

Copyright Notices in Open Source Software Projects provides LF recommendations on that. It's not gospel, but worth considering.
It particular, it recommends not trying to identify every contributor by name, and lists several variations. I would lean towards this variation:

Copyright Contributors to the OpenSSF project

Here's the rationale:

These statements are intended to communicate the following:

the work is copyrighted;
the contributors of the code licensed it, but retain ownership of their copyrights; and
it was licensed for distribution as part of the named project.
By using a common format, the project avoids having to maintain lists of names of the authors or copyright holders, years or ranges of years, and variations on the (c) symbol. This aims to minimize the burden on developers and maintainers as well as redistributors of the code, particularly where compliance with the license requires that further distributions retain or reproduce copyright notices.

There's more detail in that article about the problems of trying to keep contributor names up-to-date in these files.

I recommend just lifting the policy from CNCF which is applicable to almost
every LF project these days
https://github.com/cncf/foundation/blob/master/copyright-notices.md
In short, copyright always stays with the author.
On Mon, Oct 12, 2020 at 9:47 AM David A. Wheeler<EMAIL_ADDRESS>wrote:

Copyright Notices in Open Source Software Projects
https://www.linuxfoundation.org/blog/2020/01/copyright-notices-in-open-source-software-projects/
provides LF recommendations on that. It's not gospel, but worth considering.
It particular, it recommends not trying to identify every contributor
by name, and lists several variations. I would lean towards this variation:
Copyright Contributors to the OpenSSF project
Here's the rationale:
These statements are intended to communicate the following:

the work is copyrighted;
the contributors of the code licensed it, but retain ownership of
their copyrights; and
it was licensed for distribution as part of the named project.
By using a common format, the project avoids having to maintain lists
of names of the authors or copyright holders, years or ranges of years, and
variations on the (c) symbol. This aims to minimize the burden on
developers and maintainers as well as redistributors of the code,
particularly where compliance with the license requires that further
distributions retain or reproduce copyright notices.

There's more detail in that article about the problems of trying to keep
contributor names up-to-date in these files.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ossf/Project-Security-Metrics/issues/19#issuecomment-707165463,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSINPZEN7JA3BMBPVIH3SKMJGRANCNFSM4SMJFAEQ
.

--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1<PHONE_NUMBER>

@caniszczyk - I don't think @scovetta is literally asking "who owns the copyright", I think he's just asking "what text should we use as a copyright statement". Both of our links propose essentially the same answer, basically, use this text or something like it:

Copyright Contributors to the OpenSSF project

Without trying to list every contributor within the statement. If you want to know exactly who the contributors are, well, that's what version control systems (like git) are for :-).


UdpSocket: On Windows, never get notified by Readable event

This is found in one of our test: https://github.com/zonyitoo/coio-rs/blob/master/tests/echo.rs#L49
Environment: Windows 10 with Rust nightly, ANY ABI
The EventLoop itself runs in its own thread, and the UdpSocket is created on the other thread. UdpSocket is registered to the EventLoop with Readable | Writable, Edge triggered.
We were able to see writable event in the Handler::ready but we never saw readable in it.
All tests are passed in OS X and Linux.

Cannot reproduce now. Close.

@zonyitoo if there's remaining Windows bugs they're likely to be fixed by https://github.com/carllerche/mio/pull/426, could you try with that PR applied?

A bunch of windows bugs were fixed on master. I'm going to close this for now. If you find that the bug still exists, please open a new issue w/ a repro ideally.
Thanks.


Support TinyGo SDK for extension toolkit

resolves #101

Blocker: I would like to use wasi target of TinyGo which is yet to be merged to upstream (and I hope it will be merged soon)

According to the discussion with @lizan, I decided to use my fork branch of TinyGo which supports WASI target.

too heavy to build LLVM....

https://github.com/tinygo-org/tinygo/pull/1373 was merged finally so I use that nightly docker image for the extension builder's base

@yskopets thanks for review and I reflected your comments except the SDK specific ones.
I'm going to refactor the SDK here https://github.com/tetratelabs/proxy-wasm-go-sdk/pull/68

@yskopets refactored the SDK's API by removing ambiguity and make it aligned with original c++/rust SDKs' API (not envoy-sdk). PTAL

@lizan @yskopets @nullpo-head @musaprg Could anyone of you take a look at this? Combined with https://github.com/tetratelabs/getenvoy/pull/114, I think now we should release cut v0.2.1.

@yskopets Thanks a lot Yaro! Now the SDK becomes much better than before thanks to your review :+1: I'm going to merge this after I release v0.1.0 of SDK.


md-menu not showing up

Greetings!
I can't make the menu component render properly. When inspecting DOM, I found some weird element attributes:

Is there a bug here? Thanks!

Can you check if a valid anchor attribute is provided into md-menu?

@tanishqmanuja, thank you, adding an anchor solved the problem. Just couldn't figure it out myself without proper docs 😅

@tanishqmanuja, thank you, adding an anchor solved the problem. Just couldn't figure it out myself without proper docs 😅

Glad it helped 🙂, Docs are not yet complete for all components I guess.

@DmitryAvanesov can you share how you get this to work?

@treeder I provided a valid element as menu's anchor
const anchor = document.querySelector('#anchor');
const menu = document.querySelector('#menu');
menu.anchor = anchor;


Can now set a FEN position.

I needed functionality to set a FEN position in one of my own projects; so I forked this and added a set_fen_position function function to the Stockfish class.

Made requested changes.

Well done


Weird CPU and Disk usage

Issue Type: Bug
Vscode seems to be consuming a lot of CPU and disk resources while doing nothing. This only happens after the second time it has been invoked. Whether from the IDE or directly launching the vscode itself. Sometime it does not close or close very slowly.
VS Code version: Code 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898, 2022-04-06T14:50:12.141Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12700 (16 x 2112)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
63.85GB (56.19GB free)

Process Argv
--crash-reporter-id d2260390-d5d2-4374-ac92-97ff8d43b548

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

latex-workshop
Jam
8.24.1

python
ms-
2022.4.1

vscode-pylance
ms-
2022.4.0

jupyter
ms-
2022.3.1000901801

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

veriloghdl
msh
1.5.3

code-spell-checker
str
2.1.11

material-theme
zhu
3.13.20

(3 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30466689
vscaac:30438847
pynewfile477:30463512

First launch CPU & disk usage

Second launch

The UI is very laggy as well. Almost the same as pure software rendering in Linux
https://user-images.githubusercontent.com/68513313/162582810-5adfef21-949d-462c-b8a0-dd2a22ab2617.mp4

The UI is very laggy as well. Almost the same as pure software rendering in Linux
https://user-images.githubusercontent.com/68513313/162582858-3e93bff9-93fd-4334-9188-6bd93fa0a847.mp4

Here's the log file from the problematic launches. Just in case it may help
main.log

I confirm these issues, most probably duplicate of https://github.com/microsoft/vscode/issues/146737

@erinadreno can you provide the output of code --status when the high cpu usage happens.

@deepak1556
code --status  doesn't seem to provide anything. After a while vscode just crashed and this command still hangs in the terminal. The log still contains the same error message as I mentioned earlier.

@deepak1556
The crash is not a given, and possibly not related to the code --status command. It just crashed on its own. Nevertheless, here are the logs.
The code --status --no-sandbox returns
codeStatusOutput.txt
As for the Get-WmiObject, it gave me
getWmiOutput.txt
It seems that somehow this issue only occurs when I invoke vscode from the IDE via
"C:/Users/shinatose/AppData/Local/Programs/Microsoft VS Code/Code.exe" -g [file name]:[line number]
And I can spawn multiple such process by closing the GUI and relaunch it

This issue has been fixed in 1.67 release.


Proposal: Use MSBuild's Microsoft.Build.* libraries

Currently, dotnet-proj-info works with project files by invoking the command-line edition of MSBuild. This approach becomes unwidely when retrieving information from a project: a temporary target file is generated that specifies the names of the proeprties it needs, then MSBuild is invoked, writing the values of these properties to another temporary file. And this approach isn't perfect, resulting in bugs like #82. Even worse, pieces of the source code are MSBuild is being selectively piggybacked in a pretty brittle and clearly unsupported way, via the internal Dotnet.ProjInfo.Helpers project.
What I propose is to use the official MSBuild API, as offered through packages like Microsoft.Build. The benefits would be enormous. The codebase will be simplified, the performance will be increased, and the project will follow established best practices.
Caveats
This is gonna be a breaking change, more or less, but acceptable for me since we are still in version 0.x:

Support for .NET Standard will have to be removed. Only .NET Framework and Core will be supported. Personally I don't consider it a problem; I cannot imagine a .NET project analyzer that needs the ubiquity of platforms that .NET Stnadard can offer but .NET Core 2.x cannot. Besides, .NET 5's time draws near, reducing the framework fragmantation.

We have to reconsider the way the project deals with MSBuild installations. Currently it looks for MSBuild executable files, but what we would need are directories with the MSBuild assemblies. We would use the Microsoft.Build.Locator package as recommended by Microsoft. It can find only MSBuild installations from .NET Core SDKs when run on .NET Core, and only from Visual Studio when run from .NET Framework.

What is more, the MSBuild locator's implementation relies on hooking assembly resolving events, meaning that we might not be able to use multiple versions of MSBuild per program invocation. Still it seems a pretty exotic scenario for me.

To read solution files, we use a package that was last updated three years ago that also piggybacks from MSBuild source code. Using the official solution parser API would also cause trouble because it cannot retrieve the files inside a solution folder, which means that until dotnet/msbuild#1708 is fixed (preferably by enricosada/Sln#3), we have to keep using the package we are already using.

I am waiting for your feedback on these proposals. Once some ambiguities (like my second bullet point) are addressed, I will start working on an implementation.

I'm entirely in favor of doing something very much like this. Now that these libraries are maintained and made openly available it seems odd to not use them. I understand a worry about not being able to use multiple versions, but this package is pretty core/foundational to f# tooling so it generally stays pretty well maintained. Meaning we shouldn't worry about code rot.

@baronfel I have a question: should we keep supporting the legacy project files?
Things like getting the compiler arguments for them is complicated. Besides, the SDK-based project files can build .NET Framework assemblies too.

Support for .NET Standard will have to be removed

We can probably go even further with that and target only Core.

We have to reconsider the way the project deals with MSBuild installations.

Locator thing sounds good - TBF, all we care is finding the correct location from SDK

Breaking change

I'm planning to do a bunch of major releases soon (FSAC 1.0 and Ionide 5.0) so it's probably good idea to do those changes before that.

solution files

I'll message Enrico to transfer the sln repo to Ionide organization.

should we keep supporting the legacy project files?

We can probably go even further with that and target only Core.

@Krzysztof-Cieslak, I take my last question's answer as a yes.

It's interesting question... I think it would be nice to support legacy project files but if it's too complex or too much work we can live without it - we've been telling users that legacy project files support is not developed any more, so i feel it may be ok to remove it with next major Ionide/FSAC

Getting the compiler's command-line arguments from a legacy project is a pretty big deal, involving replacing an MSBuild target - that cannot be easily reproduced using library calls, and two piggybacked files from F#'s sources, so I will not port it.
Still it makes me curious, why we need to get the compiler's arguments in the first place?

why we need to get the compiler's arguments in the first place

To create correctly something called FSharpProjectOptions which is used by every FCS operation - this is true in case of both legacy and new project files.

Currently blocked by dotnet/msbuild#5856.

I've started the implementation of this in #88. PRs, suggestions and improvements are really welcomed - let's make DPI way better ;-)

My implementation is on https://github.com/teo-tsirpanis/dotnet-proj-info/tree/msbuild-library. I am not currently working on it because of the blocking bugs.
Jusging from comments in #88, I will entirely remove verbose project files when I start working on it again.

@teo-tsirpanis, Oh I haven't realized you've started implementing things already, sorry. Can you focus your efforts on the branch I've started in #88?

Currently blocked by microsoft/MSBuildLocator#86.

I've worked around this with -  https://github.com/microsoft/MSBuildLocator/issues/86#issuecomment-640275377


Installed basically works but doesnt send anything apart from /live/startup & /live/song/beat

Installed your repo as Midi Remote Script in Ableton Live 11 Mac.
It basically works because your script logs it can access the sockets
but when the session runs it doesnt send anything apart from
/live/startup
/live/song/beat
all other documented "API" arguments are not send at all.
Is this the state of development or a bug?
ps: developing an app that does all the network stuff properly..
the image below shows in example received msgs from touchOSC2 and the surprising single entry from AbletonOSC

ps2: the future plan for my app is to have some mac app that can in example edit the constant.py based on a dialog/app that was opened via os.open(...) to ask the user for the port numbers and IPs. This would make it possible for users to change the constants without even restarting Live.

seems to be by design.. hmm, limited but all good so far.
what i don't understand is when it uses a sender port and a receiver port, why the do values names carry /set and /get.
Assuming this was meant to introduce some request design pattern.

100% sure sending a Int32 datatype, made print logs in my code everywhere to be super sure.
when testing my own OSC API [_engine sendAddress:@"/live/track/get/volume" Int:0];
my log when building and sending the message looks like.. so i am sure i send i datatype.
got i, send i,
but i think i spotted some bug..
AbletonOSC: Error handling message: Traceback (most recent call last):   File "/Applications/AbletonLiveSuite64Bit/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/AbletonOSC/abletonosc/osc_server.py", line 71, in process     self.send(message.address, rv)   File "/Applications/AbletonLiveSuite64Bit/Ableton Live 11 Suite.app/Contents/App-Resources/MIDI Remote Scripts/AbletonOSC/abletonosc/osc_server.py", line 47, in send     for param in params: TypeError: 'float' object is not iterable

so changed test wise..
# in /abletonosc/osc_server.py
def process(self) -> None:
        """
        Synchronously process all data queued on the OSC socket.
        """
        try:
            while True:
                data, addr = self._socket.recvfrom(65536)
                try:
                    message = OscMessage(data)

                    if message.address in self._callbacks:
                        callback = self._callbacks[message.address]
                        rv = callback(message.params)

                        if rv is not None:
                            if rv is not tuple:
                                #self.logger.info("juijui: %s" % str(rv))
                                self.send(message.address, (rv,))
                            else:
                                self.send(message.address, rv)

                    else:
                        self.logger.info("AbletonOSC: Unknown OSC address: %s" % message.address)
                except ParseError:
                    self.logger.info("AbletonOSC: OSC parse error: %s" % (traceback.format_exc()))

which as assumed results with some proper answer on my request.

but now as told it answers with "/get/" which is kinda correct but still i would try to get rid of them its just wasting bandwidth..

Hey @designerfuzzi ,
first of all: There have been no developments and no answers on this project for 7 months.
So I'm afraid it has already been abandoned...
I don't know if you are aware of this, but to get automatic status update sent, you have to start a
listener on the desired parameters. I remember that I tried one or two and was able get these
automatic updates.
But there are only a few of these listeners implemented and also some (important) parameters
missing - I haven't looked into the Live API lately, but I'm pretty sure there must be more...

thanks for the reply..
But in general this means LiveOSC could work again with Live 11 when i do some tweaking..
LiveOSC suffers from the python2 switch a lot and i thought AbletonOSC looked more stable..
apart from the little problem i could solve today, it seems indeed a little less cumbersome to code for..
for the completeness i was going to compare it with the LiveOSC supported link list..
as more and more people will have the OSC challenge with Live11 your project is still kinda important..
dont forget that your work is never wasted..

I'm not the developer of this project!
I'm just a user and was happy when I found this port for Live 11 and a bit disappointed
when I realized it's far from complete and there is no ongoing development.
I understand a bit of what is listed in the Live API documentation, but not enough
of Python to work on the code. So if you are able and willing to improve and extend
this project, I'd be happy to assist and test.

My python knowledge is limited yet as well, but knowing C, C++, objc, swift it was not that hard to catch that little bug.
I would not say it is far from complete as of what i see in code.. i would more think its not tested enough, which made it possible for this bug to exist, i guess. Well nothing comes from heaven unless we pick it up.
The Live API to me is more of a structure with a naming scheme and property register that someone published, also just existing because someone picked it up..
haha, thought you where the dev of this repo :-)
I actually do this all here just because its a side project for the app partly shown in the pics.
Developed some kind a midi DAW that can hang in between ableton and hardware or in between Ableton and Logic or any kind of OSC device. Supports Push1&2, has midi filters, a independent Midi clock as well as MTC, and reads Elektron gear files from hardware and translates them to Ableton Sets with i dont know how much scenes are possible..
Pretty deep inside whats going on..

porting LiveOSC from python2 to python3 now.
After a lot import rule changes it works now, Ableton accepts the script and finds its _Framework dependencies
next, porting LiveOSC/OSC.py to do properly MessageBuilding
because
python2 unicode -> became python3 str
python2 str -> became python3 bytes
And this is where i am a little stuck at the moment..

porting LiveOSC from python2 to python3 now. After a lot import rule changes it works now, Ableton accepts the script and finds its _Framework dependencies
next, porting LiveOSC/OSC.py to do properly MessageBuilding because python2 unicode -> became python3 str python2 str -> became python3 bytes And this is where i am a little stuck at the moment..

Have you made any progress on porting LiveOSC? It would be amazing if you could get this working as I want to use Open Stage Control to dive a bit deeper than just sending MIDI messages to Abelton.
Many thanks for your effort on this!

LiveOSC up and running.
But as i decided to modernise it a little as well i will post the result in a couple of days.

Amazing!
Let me know whenever you need something to be tested.

LiveOSC for python3 up and running. Ended up changing the whole OSC unit to adapt the encode and decode mechanism of python3. While this simplified some code, other became more complex. Lessons learned, now i know why i love C.
But as i decided to modernise it a little as well i will post the result in a couple of days as a repo in my profile.

Thank you. I'm happy to test too. Many thanks!

@designerfuzzi Just wondreing if you've got an ETA for the update of LiveOSC please?
Sorry for asking but I desperatly want to test out my OSC control panel with Ableton.
Many thanks!
Kind regards,
Chris

@designerfuzzi Just wondreing if you've got an ETA for the update of LiveOSC please? Sorry for asking but I desperatly want to test out my OSC control panel with Ableton.
Many thanks!
Kind regards, Chris

designerfuzzi is not the initial developer of LiveOSC / AbletonOSC, so I doubt there will something like
an update release or ETA. Maybe we are lucky and he will share his personal achievements though...

Ahh, Ok thank you.
Yes very excited for this


Improve Netty connection pooling support

Change the default connection pooling configuration so that we don’t allow for an unbounded number of connections.
Improve our recently-added Netty builder APIs to let users configure their connection pooling, to either set fixed, elastic, or custom connection pools.

If I recall correctly, this issue can be closed. @jianghaolu Please do so if there is nothing that needs o be done here.

This is done in the PR https://github.com/Azure/azure-sdk-for-java/pull/5836, the builder accept reactor.netty.resources.ConnectionProvider that can be fixed/elastic/newConnection or a custom provider.


Error when loading ckpt for Dreambooth

It's a merged model that I downloaded as safetensors. Because I would get a similar error when trying to load it into Dreambooth, I merged it with 0 weight and saved as checkpoint (poor man's conversion) but it still won't load.
It will load and work just fine in SD, but not on DB. Anything I can do to train it? Thanks!

in DB it converts it to diffusers, the conversion script doesn't support safetensors format

So it's still safetensors even if it's a ckpt file?

So it's still safetensors even if it's a ckpt file?

Probably, I haven't tested it yet, I will later.

Thanks!

Getting the same error when trying to load a ckpt trained based on SD20 720px

Getting the same error when trying to load a ckpt trained based on SD20 720px

because it wasn't converted correctly

Getting the same error when trying to load a ckpt trained based on SD20 720px

because it wasn't converted correctly

It was trained with this repo and works in SD. No idea what I did incorrectly, but it was trained during the period of intensive changes following the release of SD20, so it's probably due to that.

yes, before the recent changes, the converting script was not working correctly, you will even notice the model doesn't really reflect the trained subject, but now it's fixed, any model converted before the change will not work.

Ok, thank you

I'm still having this issue, is there any way I can convert these models for use in dreambooth?
I can't use any of the the newer models, none will work.. Only old stuff and Base 1.5


fix build and broken links

🚀 Deployed on https://66fed1c92443dcebcbce6dc4--cozy-fox-0defec.netlify.app


MySQL adapter

Howdy,
I've created a MySQL adapter with liberal inspiration from @pdebelak's scenic_sqlite_adapter. It's available at https://github.com/EmpaticoOrg/scenic-mysql_adapter.
Bonus: The MySQL adapter also supports reliable schema loading by dumping views in topographical order. (cf: #191)

Thanks. I've added a link to the readme.


SIGSEGV: Use after free when RN is shutdown off the main thread

Environment
System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    Memory: 2.49 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.16.0 - /usr/local/opt/node@10/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 27, 28
      Build Tools: 28.0.3
      System Images: android-28 | Google APIs Intel x86 Atom
      Android NDK: 20.0.5594570
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react-native: 0.60.5 => 0.60.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Platforms
iOS
Versions

iOS: 12.4.1+
react-native-netinfo: 4.2.1
react-native: 0.60.5
react: 16.8.6

Description
It's currently possible for -[RNCConnectionStateWatcher update:] to be called after it has been deallocated when React Native was shut down on a background thread. The bridge cast in -[RNCConnectionStateWatcher createReachabilityRef] doesn't retain self so it is unsafe to use it in RNCReachabilityCallback. Perhaps a weak pointer should've been used here.
Here's a stacktrace of the crash:
Exception Type:  SIGSEGV
Exception Codes: SEGV_ACCERR at 0xa7eab7280
Crashed Thread:  0

Application Specific Information:
objc_msgSend() selector name: setState:

Thread 0 Crashed:
0   libobjc.A.dylib                      0x000000022c9ab530 objc_msgSend + 16
1   MyApp                                0x00000001036e4064 -[RNCConnectionStateWatcher update:] (RNCConnectionStateWatcher.m:65)
2   SystemConfiguration                  0x000000022e52c118 reachPerformAndUnlock + 504
3   CoreFoundation                       0x000000022d74c728 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 20
4   CoreFoundation                       0x000000022d74c6a8 __CFRunLoopDoSource0 + 84
5   CoreFoundation                       0x000000022d74bfe0 __CFRunLoopDoSources0 + 252
6   CoreFoundation                       0x000000022d746ecc __CFRunLoopRun + 1000
7   CoreFoundation                       0x000000022d7467c0 CFRunLoopRunSpecific + 432
8   GraphicsServices                     0x000000022f94779c GSEventRunModal + 100
9   UIKitCore                            0x000000025a109c38 UIApplicationMain + 208
10  MyApp                                0x000000010241fe98 main (main.swift:18)
11  libdyld.dylib                        0x000000022d20a8e0 start + 0

👋 Thank you for reporting this. I will look into it as soon as I can.

I've taken a look at this and I'm not able to see what the issue is. Are you able to submit a PR with your suggested changes?

@matt-oakes: I opened a PR. Let me know what you think. 😄

Fix merged (b43838f) and included in version 4.3.1.


Cache listeners per device, and clear them once device disconnect

Tackling Issue #54

Looks good, thanks!

I published an updated package version with this fix<EMAIL_ADDRESS>

That's perfect! Thank you very much


KAFKA-8306: Initialize log end offset accurately when start offset is non-zero

Failures look unrelated. Retest this please.


Multi-tenancy authorization in ASP Core 2.0

Hi!
How to make authorization separated per each tenant in ASP Core 2.0?
In Core 1.0 we were using IApplicationBuilder.UsePerTenant() extension method for this situation.
In Core 2.0 authorization configuration (including social networks authorization) is handled on IServiceCollection of ConfigureServices() method in Startup.cs.
Thank you!

Are talking about identity?

@Marcel0024 In core 1 authentication was set in Startup.cs:Configure with app.UseXYZAuthentication(). In core 2 it is set in Startup.cs:ConfigureServices with services.AddAuthentication().AddXYZ().
All UseXYZAuthentication-methods in IApplicationBuilder are deprecated in core 2, so it seems to be impossible to set authentication inside app.UsePerTenant((ctx, builder) => { ... }).

+1 for this. I'm currently trying to work through the samples and app.UsePerTenant seems to be a showstopper at the moment

Hi,
I just got this solution from the ChatGPT:
To achieve separate authorization per each tenant in ASP.NET Core 2.0, you can implement multitenancy using middleware and configure authorization services accordingly. You can create a custom middleware to identify the current tenant based on the request and then apply authorization policies specific to that tenant. Within the ConfigureServices method in Startup.cs, configure authorization services to handle tenant-specific authorization, including social networks authorization. Utilize tenant identification middleware to set the tenant context for each request, enabling authorization policies to be applied based on the current tenant. This approach ensures that authorization is separated per each tenant in ASP.NET Core 2.0, similar to the IApplicationBuilder.UsePerTenant() extension method used in Core 1.0.
Will it really work for me? please guide me in this regard.
Thanks


Enable filtering by file type

Is your feature request related to a problem?
I wanted to search Music NFTs in Dotsama and wasn't able to filter my file type
Describe the solution you would like
a dropdown with file types
Describe alternatives you have considered
or tickboxes
Screeenshots
No response
Are there opened related issues?
No response

duplicate/related with #1162


Regression: compilation errors no longer emitted

Steps:

Add a stray => to the code introduce a compilation error.
Add this plugin to Webpack:

function FailOnPluginErrorsPlugin() {
}

FailOnPluginErrorsPlugin.prototype.apply = function(compiler) {
  compiler.plugin("compilation", function(compilation) {
    compilation.plugin("after-optimize-chunk-assets", function(chunks) {
      if (compilation.errors && compilation.errors.length) {
        throw compilation.errors;
      }
    });
  });
};

module.exports = FailOnPluginErrorsPlugin;

Errors are not thrown  in ee1663991b37f243a65d0ee69e37169e6e113943 and later.

@nifgraup can you create minimum reproducible test repo?

Test case:
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>echo "=>" > error.js
# save FailOnPluginErrorsPlugin.js
webpack --plugin ../uglifyjs-webpack-plugin/dist/cjs.js --plugin ./FailOnPluginErrorsPlugin.js --entry ./error.js  --output-filename out.js && echo "Didn't fail as it should" || echo "Failed as it should"

It turns out I will not be needing FailOnPluginErrorsPlugin anymore, I used it get Webpack to return non-zero but now (after upgrading to webpack3?) it does.


Applied round shape on profile image

Fixes #2715
Describe the changes you have made in this PR -
In index.html, I added a class "search-image-cropper" to the div containing the user image.
In search.html, I did the same.
In search.scss, I tweaked the class "search-usersearch-image" as well as added a new class "search-image-cropper"
Screenshots of the changes (If any) -
Screen Shots
User Dashboard

Before
After

Search Page

Before
After

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 82.645% when pulling 59b5a689f6d1023281e871d0c7bf2739b778c3da on camperjett:Style-profile-pic#2715 into 0bb5b872665b6439ce640cf238f3cf88e9b21235 on CircuitVerse:master.

Do we need any changes? @vedant-jain03

Do we need any changes? @vedant-jain03

Wait for @nitin10s review.


Add CC Korea team members to github

You'll need to let me know all their usernames

I'm collecting them now. Will let you know tomorrow.

@mattl Can you add the following<EMAIL_ADDRESS>(username: nanshil<EMAIL_ADDRESS>

Can you tell me everyone's usernames? If they don't have one, they need to register :)

It's jenniferkang for<EMAIL_ADDRESS>Thanks! :)

@mattl, can you add jenniferkang and nanshil to this repository?


WMR does not support .mdx files

I'm looking to give XDM here a try with WMR, but am running into issues with loading .mdx or .md files, specifically the following:
Loading module from “http://localhost:3000/content/docs/foo.mdx” was blocked because of a disallowed MIME type (“text/mdx”).
Uncaught (in promise) TypeError: error loading dynamically imported module
Uncaught (in promise) TypeError: error loading dynamically imported module

Vague error message, but according to WMR's debug logs, it looks like the Rollup plugin isn't correctly handling the files and WMR is just serving the .mdx file directly. While I have no doubt that this is user error on my part, the ReadMe is 2400 lines long, full of expandable content sections, a maze of links back on itself, and no full samples. Reading through the Rollup, WMR, and Preact sections have me believing I just need to add the xdm/rollup.js plugin and set the jsxImportSource, but seemingly that doesn't result in a usable build.
// wmr.config.js
import { defineConfig } from 'wmr';
import xdm from 'xdm/rollup.js';

export default defineConfig({
    plugins: [
        xdm({ jsxImportSource: 'preact' }),
    ]
});

// bar.jsx
import Foo from './content/docs/foo.mdx';

export default function Bar() {
    return <Foo />;
}

// foo.mdx
## Hello world

bar

Having some examples would help massively in helping people get up and running (if they don't already exist somewhere), as the current ReadMe isn't really conducive to getting something usable.
As an API guide though, I don't believe I've seen anything more detailed, wow. Seriously impressive.

I don’t think anyone has ever combined WMR with xdm yet: WMR says it supports Rollup plugins, so I that’s why I linked to that section. If this doesn’t work, it’s either a WMR error on their side, or something we can document here.
I’m guessing that WMR is compiling MDX -> JS, because it says Rollup plugins are supported.
From that error, I think it’s not changing the file extension.
You could assert whether the MDX -> JS part is working or not, by adding a console call in your node_modules here:
https://github.com/wooorm/xdm/blob/bac5c48ae7eeccd5ae5abd133fac8c9e4824e48e/lib/integration/rollup.js#L36
From what I know of rollup plugins that work on different files (e.g., importing csv), that line should just work and Rollup should see the output as JS.
It might be something to raise with WMR folks.

Ah, gotcha. I had assumed someone gave it a test, and that it was just user error in the config on my part somewhere.
Seems to be that the plugin never has access to the asset at all. Logging all the paths that flow through, the .mdx file does not show up. Interesting, probably something in WMR then.

It might be something to raise with WMR folks.

I conveniently help out over there, though I'm far from experienced with this sort of thing. I'll definitely bring it up, not sure if you want to close this out or not, certainly helped point me in the right direction. Thanks!

To reproduce, do:
$ npm init wmr xdm-example
$ npm i xdm -D

Add to public/index.js:
import Content from './example.mdx';

Create public/example.mdx:
# Hello, world!

Change wmr.config.mjs:
import xdm from 'xdm/rollup.js';

export default function (config) {
	config.plugins.push(xdm());
}

Change node_modules/xdm/lib/integrations/rollup.js by adding on L32:
console.log('xxx:', path)

Start the WMR server, go to localhost:8080, and get:
xxx: ./style.css
xxx: ./index.js
xxx: ./pages/home/index.js
xxx: ./pages/_404.js
xxx: ./header.js
xxx: ./pages/home/style.module.css

And in the browser console:
TypeError: 'text/mdx' is not a valid JavaScript MIME type.

So WMR is not passing non-css/js files to Rollup. Which is a bug there.
I’d appreciate it if you could report that, or work on it yourself, so that it’s fixed in WMR!

Late night here, but will do in the morning! Thanks for your help.

Added a note to the readme for now!

@rschristian I think I saw a PR saying this was now fixed? Is that released already? If so: would appreciate hearing how to set up WMR and what your experience with xdm is!

@wooorm Apologies, forgot to return. Works great now!
Setting up a new project with WMR & XDM is super easy, all one needs to do is add the rollup plugin.
wmr.config.mjs
import { defineConfig } from 'wmr';
+import xdm from 'xdm/rollup.js';

// Full list of options: https://wmr.dev/docs/configuration
export default defineConfig({
    /* Your configuration here */
    alias: {
        react: 'preact/compat',
        'react-dom': 'preact/compat'
    },
+   plugins: [
+       xdm({ jsxImportSource: 'preact' })
+   ]
});

The only thing one needs to do is install xdm & add that diff to the wmr.config.mjs file that comes with newly created WMR projects. Then it's just standard module imports, import Foo from 'foo.mdx'; works great and as expected.
HMR doesn't work with updates to MD(X) files, but that's something for WMR to work on. Can't say I've noticed any other hiccups in the dev experience, the two work great.
I'll write up a quick PR for the docs now that it is supported.


Allow Devs to use MaterialApp Without it's Nav Logic

Use case
MaterialApp wraps the tree in a navigator/router (transitively via WidgetsApp). Since there are so many different approaches to navigation now (Nav 1, Nav 2, GoRouter, Nav 1 router based, etc) this massively balloons MaterialApp's constructor. Not to mention, MaterialApp breaks Nav 2 on Android (system back closes the entire app) and requires a workaround to use.
Here is a list of navigation related constructor arguments in MaterialApp:

navigatorKey
home - this would probably just be replaced by child if nav logic were removed
initialRoute
onGenerateRoute
onGenerateInitialRoutes
onNavigationNotification
navigatorObservers

Then there's the entire MaterialApp.router alternate constructor.
Many of these args have non-obvious runtime constraints too:
https://github.com/flutter/flutter/blob/3df4e735d5d0bd2db7930098eba1b3e620d77aa0/packages/flutter/lib/src/material/app.dart#L199
And, since most of these arguments are just proxies for WidgetApps/Router/Navigator, they're a maintenance burden to keep in sync, have unreadable inline docs (may depend on IDE settings), and their logic is hard to trace when clicking through the source code:

Proposal
Handling navigation logic in MaterialApp made sense when Flutter's navigation options were simple and limited. We are well past that point.
Here are a couple proposals of various levels of disruption that would resolve this problem. Note that all of these proposals probably involve modifying WidgetsApp to mirror the MaterialApp changes

Allow the developer to provide a navigator key corresponding to their own navigator, MaterialApp will bind the system back gesture to the navigator associated with that key, and provide no other navigation logic of its own. Pros: no disruption, minimal boilerplate. Cons: MaterialApp becomes more complicated instead of less, would be hard to disambiguate this new arg from the existing navigatorKey arg.
Alternate constructor that has no navigation based args, developer is responsible for putting a navigator in the tree and binding the system back gesture to it. Pros: no disruption, no subtle behavior. Cons: MaterialApp remains complicated, developer has to write a fair amount of boilerplate to opt out of material app nav.
Remove all navigation related logic from MaterialApp. Pros: simplifies dramatically. Cons: high disruption, newbies who would've been happy with basic default behavior now have to write a lot of boilerplate (PopHandler, Navigator).

Personally, I prefer 3-rip the band aid off. MaterialApp is a bit too "magical" and often produces subtle undesired nav behavior (eg only ever popping from it's own root navigator on system back-I wonder how many Flutter apps are live in production with this bug right now??). Forcing devs to handle their own nav logic is a bit of upfront friction, but will likely be less confusing and produce better app UX in the long run. It'll also give the Flutter community a lot more room to experiment with alternate navigators as right now MaterialApp makes it hard to use a navigation approach it doesn't itself provide.
However, 3 is so disruptive that I imagine the team will not be interested in it. As such I think proposal 2 probably makes the most sense, especially because it could evolve into a rollout step for 3.
Happy to hear your all's thoughts and am more than willing to write the associated PR(s) myself to make any of these 3 happen.

I wonder if there is a way to have the existing constructor more or less work the same by implicitly wrapping and we create a new constructor without any navigation logic, basically option 3 without a breaking change:
class MaterialApp {
  factory MaterialApp(/*existing args*/) {
    return _ImplicitNavMaterialApp(...);
  }

  factory MaterialApp.withoutNavigation(/**/) {
    // TODO: Implement.
  }
}

Based on reception/feedback we could either rename constructors in the future, or even have some sort of auto-fix that inlines the default constructor for users.

i use go_router for navigation  .  how   can i use  go_router with  proposals 3   !!!!

@samithe7 I haven't used GoRouter at all so I'm not familiar with it-perhaps someone else could pipe in on what that would look like? Though I'm increasingly thinking option 3 isn't a great approach anyway and I doubt the Flutter team would go for it so maybe it's a moot point?
FWIW It occurs to me the problem here might be one more of API discovery than anything else.
The problem isn't so much that MaterialApp is intercepting the system back as much as it is that if I want my navigator to respond to the system back gesture, something has to bind it to my navigator.
So right now the best workaround (which I am already using) I'd still have to use under proposals 2 and 3. This makes option 1 sound a lot more appealing.
Here's "option 2a" with this in mind:
2a. MaterialApp has an alternate constructor with the existing nav related arguments removed. It has a new VoidcallBack onSystemBack argument that it routes to a NavigationPopHandler.
I actually like this approach a fair amount as it gives the developer arbitrary navigation flexibility while guiding them through the process of binding their custom solution to the system back gesture.

To answer the request made in the title of this issue: It is already today possible to use MaterialApp without the nav logic by specifying the builder argument, see https://main-api.flutter.dev/flutter/material/MaterialApp/builder.html. Of course, this doesn't address the other issue of MaterialApp being to complex...

To answer the request made in the title of this issue: It is already today possible to use MaterialApp without the nav logic by specifying the builder argument...

Then it looks like the problem I have then is much more about the interpretability of MaterialApp rather than it's features or lack thereof. I think there might be a cascading series of UX issues that I'm having trouble with here.
I had checked the Builder argument before and skipped over it, maybe running through my thought process when exploring material App's UI would be helpful:

TransitionBuilder feels like a misnomer-it implies to me that this is for animating child widgets in and out. This was the primary reason I skimmed over MaterialApp.builder without realizing that it provides what I want. Perhaps a name change or equivalent typedef with an alternate name (similar to AnimatedBuilder/ListenableBuilder) could be helpful here?
The @Macro makes the inline documentation hard to follow, I usually just give up and move on when faced with @macro docs. Is there an IDE plugin/setting that can at the very least provide functional click through here?
The WidgetsApp.builder docs are pretty complicated and hard to follow. After reading it, I still don't really understand it. The hardest part is it seems to have a couple fairly unrelated purposes (overriding navigator behavior, overriding MediaQuery, etc).

All this considered, maybe this PR was pretty narrowly scoped in the end and my topline issue is more "Material App is complicated/confusing" than specifically the interaction of MaterialApp <> Nav. Is there any appetite for a broad design refresh here?

I would like to provide further insight from my experience. As was already mentioned and I agree, MaterialApp and WidgetsApp respectively are too complicated and have too many responsibilities. From that point of view, builder argument seems more like a workaround around an inflexible api rather than a solution to the problem.
I think Navigation should be opt in and a responsibility of the consumer of the API. What if I don't want a navigator and I want just a single page application? What if I want nested navigators? Most of the times navigation is gradual, meaning that you start with a simple navigation flow, consisting of a couple of pages. Then you realize you want parallel navigation histories, where you introduce nested navigators with the top one orchestrating which one is active. After that, you may want to add a loading or a sign in flow before the nested navigator. To conclude, I think navigation should be a separate issue not a responsibility of the top level app. This would unlock many possibilities of independent evolution.
It is the same as the implicit/explicit view in a multiview app, that is coming soon. Implicit is good for faster development, but explicitly manifesting the view hierarchy is a must for more advanced usecases.

@caseycrogers In my application, I disabled title bar of window and use builder to customize it.
  Widget builder(context, child) => Column(
        children: [
          if (Platform.isWindows || Platform.isMacOS) const WindowAppBar(),
          Expanded(child: ClipRRect(child: child)),
        ],
      );

It's a good example to explain what it does here.


note that this library is secure

I think it's important to note that this library is secured from known attacks.

Indeed it may be interesting to note that fact, but it don't really agree with the happy term you've used. People using a crypto library expect it to be secure, especially when the issue has been announced long time ago publicly, and this should be the standard. Your sentence can imply that people should be good with what they have, even though it's a critical vulnerability.

The status of each JWT library respect to this vulnerability is already documented at http://jwt.io. I don't see the point of explicitly saying that a library is secure, because that is the default expectation for everyone. Also, this was already mentioned in the changelog here: https://github.com/auth0/node-jsonwebtoken/blob/master/CHANGELOG.md#security


Create a gradle task that automatically creates the credentials for local sftp sites

This ticket is to create a gradle task that creates the DEFAULT-SFTP credentials for you, eg, it should make this call:
./prime create-credential --type UserPass --persist DEFAULT-SFTP --user <pass this in> --pass <pass this in>
It should take two parameters that are passed in to it:  the username and the password.    Default to 'foo' and 'pass' respectively.
Per conversation in this PR:  https://github.com/CDCgov/prime-reportstream/pull/1399

I think this is now covered by Thomas' new script, so I'm closing this issue.


Issue with table wrapper in main.js

Hi there,
I ran into a problem when I included more than four tables in a single blog post; they all appeared clustered together. It was quite odd, but I believe I've discovered a workaround.
At the end of the file changed:
main.js:
/* Responsive HTML table */
(function () {
    const tables = document.querySelectorAll('.gh-content > table:not(.gist table)');
    const wrapper = document.createElement('div');
    wrapper.className = 'gh-table';

    tables.forEach(function (table) {
        table.parentNode.insertBefore(wrapper, table);
        wrapper.appendChild(table);
    });
})();

TO:
/* Responsive HTML table */
(function () {
    const tables = document.querySelectorAll('.gh-content > table:not(.gist table)');

    tables.forEach(function (table) {
        const wrapper = document.createElement('div');
        wrapper.className = 'gh-table';
        table.parentNode.insertBefore(wrapper, table);
        wrapper.appendChild(table);
    });
})();

+1 Facing the same issue.

Thanks @GraydonGit for the proposed fix. This is now included in Source 1.2.2.


FLEX-3528 ~ Checks faulty timestamp value in event notification.

When smart devices have been stored for a long time, the supercap on the board looses it's charge. Then the RTC will reset to default value which causes a problem with timestamp in event notification messages.
This change checks the timestamp value and in case 20000000xxxxxx is detected, the server time is used instead of the timestamp value of the event notification message.

SonarQube analysis reported 2 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 DeviceManagementService.java#L146: Method has 8 parameters, which is greater than 7 authorized.
 DeviceManagementService.java#L210: Method has 9 parameters, which is greater than 7 authorized.

All is well.

This one is for development branch. Is there going to be a backport for 4.12.x prod branch?

No


Testing

At this moment I think that we've enough unit tests. This issue could be reopened in the future


Allow Ecto.UUID to dump values that are already 16 byte binaries

This is a fix for a bug I discovered while using changesets to insert binaries into :binary_id columns. If you try to insert a value that is already a 16 byte binary, instead of a hyphenated string, ecto raises an error such as:
[error] #PID<0.1306.0> running Dashboard.Endpoint terminated
Server: localhost:4000 (http)
Request: POST /applications
** (exit) an exception was raised:
    ** (Ecto.ChangeError) value `<<184, 235, 134, 244, 95, 86, 74, 133, 159, 153, 31, 111, 16, 28, 76, 15>>` for `Dashboard.Application.user_id` in `insert` does not match type :binary_id
        (ecto) lib/ecto/repo/schema.ex:610: Ecto.Repo.Schema.dump_field!/6
        (ecto) lib/ecto/repo/schema.ex:619: anonymous fn/6 in Ecto.Repo.Schema.dump_fields!/5
        (stdlib) lists.erl:1262: :lists.foldl/3
        (ecto) lib/ecto/repo/schema.ex:617: Ecto.Repo.Schema.dump_fields!/5
        (ecto) lib/ecto/repo/schema.ex:566: Ecto.Repo.Schema.dump_changes!/6
        (ecto) lib/ecto/repo/schema.ex:182: anonymous fn/11 in Ecto.Repo.Schema.do_insert/4
        (ecto) lib/ecto/repo/schema.ex:595: anonymous fn/3 in Ecto.Repo.Schema.wrap_in_transaction/6
        (ecto) lib/ecto/adapters/sql.ex:472: anonymous fn/3 in Ecto.Adapters.SQL.do_transaction/3
        (db_connection) lib/db_connection.ex:973: DBConnection.transaction_run/4
        (db_connection) lib/db_connection.ex:897: DBConnection.run_begin/3
        (db_connection) lib/db_connection.ex:671: DBConnection.transaction/3
        (dashboard) web/controllers/application_controller.ex:16: Dashboard.ApplicationController.create/2
        (dashboard) web/controllers/application_controller.ex:1: Dashboard.ApplicationController.action/2
        (dashboard) web/controllers/application_controller.ex:1: Dashboard.ApplicationController.phoenix_controller_pipeline/2
        (dashboard) lib/dashboard/endpoint.ex:1: Dashboard.Endpoint.instrument/4
        (dashboard) lib/phoenix/router.ex:261: Dashboard.Router.dispatch/2
        (dashboard) web/router.ex:1: Dashboard.Router.do_call/2
        (dashboard) lib/dashboard/endpoint.ex:1: Dashboard.Endpoint.phoenix_pipeline/1
        (dashboard) lib/plug/debugger.ex:93: Dashboard.Endpoint."call (overridable 3)"/2
        (dashboard) lib/dashboard/endpoint.ex:1: Dashboard.Endpoint.call/2

I got this when I selected a record with a primary key that's a :binary_id, and tried to insert that id into the foreign key column of another table that's also a :binary_id. It seems currently Ecto is expecting that value to be converted to a formatted string such as XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX at some point, as if it were being submitted from a form.
This PR allows it to be retrieved as a binary from one table and inserted into another table as a binary without being converted to a string first.

Thank you but this is not a bug. Ecto.UUID expects the data to be formatted as a string instead of a binary. If you have a binary, you have the wrong data, even if that is meant to be its final shape. For example, should we allow datetimes to kept as binaries as well in the format it is used by the database? I don't think we should. If you want binaries, then you should declare its type as :binary.


Tremorzilla griefing configs

While there is an option to disable super destructive tremorzilla beam griefing in Alex's Caves, there is no option to have no griefing. There is also no option to disable tremorzilla griefing blocks it walks into, which gets rather annoying when going up steep hills. Having these configs in TACT would be great.

Won’t that make the mob constantly stuck and unable to climb up any hill higher than 2 blocks steps? I assumed the griefing for walking was to let the mob actually move around

Maybe a step height config could be added alongside this?

I'll add the config but any pathfinding issues is something you'll have to live with and do not report the pathfinding issue to Alex's Caves if you turn off the block griefing


[ART-1799] Fix signature directory structure

@tbielawa should I close this PR, or merge it?

alright, so closing for now, since we've been signing stuff every week and i hadn't heard any complains so far ;D


Consider adding cover page

Something like this:

Basically, a page that always appears first. It does not show cut guides or footer.
There's 2 ways of going about this:

The cover is a built-in template. Only requirement is passing in --include-cover when building datasources (and probably extending definitions so a longer description can be supplied).

The cover is a user-built template (page-sized). Can contain anything, as it's probably built like all other cards.

The second can already be done without additional code. Basically make a datasource with a single card; let this card have a page-sized template and that's it. You have a cover. However, it will also show footer and cut guides just like all other pages. This also has the benefit of being able to have any arbitrary data be filled in to the cover, as it works just like all other datasources.
Maybe the argument should be --includes-cover, which just strips footer and cut guides from the first page?
Another solution could be to let --include-cover take a single value, e.g. --include-cover=cover.html, but then it cannot hold arbitrary data. It is simple, though.

This feature should have a toggle option similar to the one described in #111

I think i'm leaning more towards --include-cover=templates/cover.html. This way, we can easily control that it always appears first, and that it uses an empty page specifically for this purpose (no footer or cut guides, and is hideable from interface).
This might also be the way to go for #112

I've come to the conclusion that I much prefer using the already-working method of just using the page card size.
The only downside to this, is the added cut-guides and footer. I'm not totally against keeping the footer, but the cut-guides bother me.
One solution I can think of, is adding an additional card size that is identical to the page size, however, the difference being that the JavaScript would then find any pages of this type, and do additional things to it; like removing cut-guides and footers.


thrift: introduce PassThroughDecoderFilter

Description: The Thrift decoder state machine has a lot of FilterStatus methods, making simple Thrift filters a bit cumbersome. This introduces a base class that returns FilterStatus::Continue for all methods so that subclasses can override the methods that matter to them, as shown with the thrift rate limit filter.
Risk Level: low
Testing: existing
Docs Changes: n/a
Release Notes: n/a

cc @rgs1 also for review.


Disable max-lines for certain files

As discussed internally, we want to disable the max-lines rule for the following named files;

types.ts
*.types.ts
machine.{ts,tsx,js,jsx,mjs,cjs}
*.machine.{ts,tsx,js,jsx,mjs,cjs}

:rocket: Issue was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:

:rocket: Issue was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:

:rocket: Issue was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


i18n(pt-BR): updates to docs content

Description (required)

Small updates to recent changes in the docs
getting-started.mdx https://github.com/withastro/docs/commit/94d715311fc2a18733ab5a002c78188f26a54184
community-resources/content.mdx https://github.com/withastro/docs/commit/d16fc18c6475911ff3fde26c5e8212520266bd8d
guides/data-fetching.mdx https://github.com/withastro/docs/commit/d40b0fc51f99031a0dd667284990a08bbb7ff722
editor-setup.mdx https://github.com/withastro/docs/commit/9437b02756162b31d1ad4eb06e207c690fcbd9a3

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

pt-br
community-resources/content.mdx
Localization changed, will be marked as complete.

pt-br
editor-setup.mdx
Localization changed, will be marked as complete.

pt-br
getting-started.mdx
Localization changed, will be marked as complete.

pt-br
guides/data-fetching.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Proxy events

I forgot to remove the aborted event proxy from my previous PR. The docs were a bit misleading. I've fixed it via placing toStream.destroy() before emitting the aborted event. Also fixed the docs.
Also added proxy for the close event:
	fromStream.once('close', () => {
		if (fromStream.complete) {
			if (toStream.readableEnded) {
				toStream.emit('close');
			} else {
				toStream.once('end', () => {
					toStream.emit('close');
				});
			}
		} else {
			toStream.emit('close');
		}
	});

I think this is a minor change (3.1.0) :sweat_smile:

The only limitation after this PR is to implement the destroy() function: https://github.com/sindresorhus/mimic-response/pull/6#issuecomment-628203276
But people should do it on their own as replacing stream._destroy is ugly, not safe and people need to pass {autoDestroy: false} anyway.

This is failing on Node.js 12.

Fixed :)


Add module directory to include path

Several projects use an include path relative
to the project's root.
file:compile will look in three places for the include
files:
The current working directory
The directory where the module is being compiled
The directories given by the include option

We're gonna need a test with that to avoid accidental regressions. There's a basic explanation on how to write them in https://github.com/rebar/rebar3/blob/master/CONTRIBUTING.md#tests, but if you want some help, I can try to write something up at some point this week.

Sure, i'll try and get something done this week

2 new tests added

Sounds good, +1.


Update docs

PR checklist
Address #593

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/raredisease branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Ensure the test suite passes (nextflow run . -profile test_one_sample,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Plugin files don't have to supplied with vep_cache. It used to be set up that way because it made it easier for nextflow to stage those files, but we no longer use that approach. There are some plugin files that come bundled with cache (ex: pli), but not all.  For instance, we use custom plugins for annotations, and those are not part of vep's cache.

There are some plugin files that come bundled with cache (ex: pli), but not all. For instance, we use custom plugins for annotations, and those are not part of vep's cache.

Ah, I did not realise pli was bundled with the cache, I thought that was downloaded separately.

You are right, that was my memory failing me. We get that file from https://github.com/Ensembl/VEP_plugins 😅 Then I suppose at least for all of the plugins we use, the data doesn't come bundled with cache.

Yes, asking because I need to add the --vep_plugin_files parameter as well: https://github.com/genomic-medicine-sweden/nallo/pull/314 😃

aah.. well timed PR 😄

I think, in the test profile these:
LoFtool_scores.txt
pLI_values_107.txt
spliceai_21_scores_raw_indel_-v1.3-.vcf.gz
spliceai_21_scores_raw_indel_-v1.3-.vcf.gz.tbi
spliceai_21_scores_raw_snv_-v1.3-.vcf.gz
spliceai_21_scores_raw_snv_-v1.3-.vcf.gz.tbi

are currently provided to VEP both through --vep_cache with vep_cache_and_plugins.tar.gz and with --vep_plugin_files with vep_files.csv

vep_cache_and_plugins.tar.gz file was generated way back when there were no option to feed plugins files seperately so as a roundabout way we packaged the plugins alongside cache. Now even though we have moved to supplying plugin files seperately, we are still using the same file hence the discrepancy. 😄
But I would guess if the files end up in the main working directory and if plugin directory is specified in the command line, it should run the ones found in plugin directory. I am not 100% sure how to tell either.. last time I looked into this, I remember coming out more confused. Need to do a proper investigation sometime soon. 😄


fix broken link to source code

Source link was pointing to the wrong folder on the repo
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] New Binding Issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes. Issue #___
[x] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@nothingismagick I fixed the website here: https://github.com/tauri-apps/tauri-docs/pull/173


use OCMBot token for event publishing

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release Notes:

@phoban01, so far, the release event is only published for non-pre releases. Do we want to stick to this?


Component Inline problem

Recently i faced a problem inlining components.
If I import a template  in a component like :
templateUrl :"../app.component.html"
and the app.component.html contains some html with other components :

  Hello {{ world }}

I was expecting the "gulp-inline-ng2-template" also import  htmls of  and  and inline them in app.component.html. However  "gulp-inline-ng2-template" does not. I was wondering if you guys have any solution for this problem.

Hello. Currently such feature not supported


Lost Scroll Position?

This utility lists "lost scroll position?" as one of the problems it solves. Am I correct in assuming that there is an ability to insert rows without losing scroll position? If not, is it possible to add this ability by, for example, setting an anchor cell or index that stays while everything mutates around it?

It sounds like a great idea, but I think it's somewhat outside of the scope of the tool.
It can be easily achieved though: -[UITableView rectForRowAtIndexPath:] or -[UICollectionViewLayout layoutAttributesForItemAtIndexPath:] measured prior to the update and after it. However there are all sorts of subtleties that need to be considered and would make the API bloated.
Have you considered using -scrollToItemAtIndexPath:atScrollPosition:animated?

I have. Currently I have settled on manually setting the offset of the table view after I've calculated the height of everything that is being added. However that isn't the most elegant solution as I can't animate visible deletions and sometimes the table still flashes when things get reloaded. That's why when I saw "lost scroll position" as one of the listed problems this tool was supposed to solve I got really excited, but I suppose you meant something else.

Well, what I meant is that you see changes animating in, therefore user understands changes better than simply new cells appearing out of nowhere, but I understand your point, it does sound like a nice addition. Do you have an idea of how this API would look?

Couple of additional question, as it seems like you gave this problem some though already :smiley:

how do you know which cell is your anchor in advance without calculating diff between you old and new data?
how would you go around case when all visible cells are being deleted, what would be your anchor?

So 'UITableView' has an API called 'indexPathForVisibleRows' that I believe can be used to achieve an API addition to this tool that looks something like this:
'''

(void)wml_applyBatchChanges:(NSArray *)diffs
inSection:(NSInteger)integer withRowAnimation:(UITableViewRowAnimation *)animation andAnchorInVisibleRows:(NSInteger)anchorIndex;
'''
Where everything stays the same except the anchor would refer to a visible cell index returned from the above mentioned table view API. In the event that all visible cells are actually being removed, the anchor would be the first cell above the removed cells that isn't being removed. In the event that there is no cell above the removed cells, there would be no anchor. I haven't thought through all the possible edge cases as I've really only thought about something like this in the context of my own use cases, but I think this adequately covers the most immediate cases. What do you think?

So, as I understood, you'd prefer to maintain the original offset from the top of the UITableView viewport for specified indexPath, right?
I think the major problem would be with UITableView where, oppose to UICollectionView, no callback is being fired upon completion of the changes. And I'm always hesitant to add code relying on timers to compensate for the lack of completion callbacks. Any ideas?

Yes that is correct. You're also correct that there is no callback or any sort of completion handler, so I do think a timer is the best solution for this. Maybe something could be done with beginUpdates and endUpdates?

Ok, I'll think of a way to deal with it and will try to work something out when I have time.
Pull requests are welcomed by the way :)

Thanks! I'll definitely be taking a good long look at it as well, as it is an integral part of a project I'm currently working on. Best of luck!


Firefox Incognito Tab does not allow IndexedDB

This line
https://github.com/nimiq-network/jungle-db/blob/d39562369012e36218933c9633c57b2a17474319/src/main/platform/browser/JungleDB.js#L43
throws an InvalidStateError in Firefox Incognito. There is no error handling by JungleDB, thus no error message pops up in the Nimiq miner or wallet interfaces.

Here is the bug in Mozilla's system tracking it: https://bugzilla.mozilla.org/show_bug.cgi?id=781982

According to https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API#Browser_compatibility, IndexedDB is only supported in Chrome's incognito mode, not in any other browser's.


Removing ribbon and minor improvements

I believe that Ribbon is not needed since the minion can access the boss through the k8s service.
What do you think @Salaboy ?

@paolocarta totally, the only thing that you need to revert is the service name, we were using a fixed name instead of the chart to avoid including the helm release name. Thanks a lot for the clean up!

@Salaboy done!

@paolocarta totally.. that is what we are using I believe.. because the name of the service is the spring boot app name.


Check-on-check

With istio-on-istio, we have internal telemetry available for consumption by istio adapters. Internal policy enforcement is currently disabled. Its main purpose is to authorize Check calls. Note that there is no need to perform 2 RPCs here,  this can be done internally in Mixer, except for one problem: Mixer's sidecar strips some attributes as part of mTLS termination. This request is to add an option to forward missing attributes as gRPC metadata (to avoid modifying the request bodies). We already have a mechanism to do that with forwarded attributes. There is just one bit missing, which is to forward derived attributes, not just constants. We can then signify source.principal as the forwarded attributes on Mixer's policy sidecar, and decode it back in Mixer server to complement Check request body.
/cc @geeknoid @qiwzhang @douglas-reid

needed for sidecar-injected istio control plane


Table colunm visible doesn't work after first render

I'm trying to hide a column from a table using Visible, but only works on first render, if I have a button where I can change the status for false and use StateHasChanged, the column still visible.

yes. it's by design. please take a look for this https://www.blazor.zone/tables/column#Visible

I saw, thanks, but it's possibile change this by code using, example a variable bool on Visible in the colunm? it's because I have one colunm that's show for some user and for other no, but in the method OnParametersSetAsync(), but at the time that goes to check some details, the colunm is already visible, and I can't change, I have tried on your source code and I have made a few changes with the same idea of this two options and it's works. it's possible have this possibility? like change the visibile in any point by code.

@gmondin sound good! could you submit a PR for this issue?


Coursier causes build to fail, possible binary version mismatch

If hands-on-scala-js is built with sbt and coursier compilation fails with what appears to be a binary version mismatch (for details, see issue lihaoyi/hands-on-scala-js#42).  However, if coursier is disabled, compilation succeeds.
Looking at the output of last book/compile:run, the classpath lists all the same jars at the same version either way.
I enabled Coursier per the quick start:
~/.sbt/0.13/plugins/build.sbt

addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-M14")

sbt: 0.13.13

Seems to be fixed now (1.0.0-RC3 works fine for me).


chore(main): release 2.33.0

:robot: I have created a release beep boop
2.33.0 (2024-12-12)
Features

add info to inference detail (#283) (8d3c971)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ai4os/ai4-dashboard/releases/tag/v2.33.0 :sunflower: