Migrate repo labeler workflow to a maintained GitHub Actions

Fixes #31.

repo labeler dry run:
👉 Current labels
- name: A-build
  color: f7e101
  description: 'Area: CI build infrastructure.'
- name: A-clang-format
  color: f7e101
  description: 'Area: Wrapper around clang-format.'
- name: A-cli
  color: f7e101
  description: 'Area: CLI runner.'
- name: A-deps
  color: f7e101
  description: 'Area: Source and library dependencies.'
- name: A-distribution
  color: f7e101
  description: 'Area: Invoking with npx, packaging, etc.'
- name: A-embedded-bin
  color: f7e101
  description: 'Area: Embedded `clang-format` binaries.'
- name: A-performance
  color: f7e101
  description: 'Area: Performance improvements and optimizations.'
- name: A-project
  color: f7e101
  description: 'Area: Infrastructure for running an open source project.'
- name: A-release
  color: f7e101
  description: 'Area: npm releases and version bumps.'
- name: A-security
  color: f7e101
  description: 'Area: Security vulnerabilities and unsoundness issues.'
- name: C-bug
  color: c1c8ff
  description: 'Category: This is a bug.'
- name: C-docs
  color: c1c8ff
  description: 'Category: Improvements or additions to documentation.'
- name: C-enhancement
  color: c1c8ff
  description: 'Category: New feature or request.'
- name: C-quality
  color: c1c8ff
  description: 'Category: Refactoring, cleanup, and quality improvements.'
- name: C-question
  color: c1c8ff
  description: 'Category: Further information is requested.'
- name: dependencies
  color: 0366d6
  description: Pull requests that update a dependency file
- name: E-easy
  color: 02e10c
  description: 'Call for participation: Experience needed to fix: Easy / not much.'
- name: E-hard
  color: 02e10c
  description: 'Call for participation: Experience needed to fix: Hard / a lot.'
- name: E-help-wanted
  color: 02e10c
  description: 'Call for participation: Help is requested to fix this issue.'
- name: E-medium
  color: 02e10c
  description: 'Call for participation: Experience needed to fix: Medium / intermediate.'
- name: E-needs-test
  color: 02e10c
  description: 'Call for participation: Writing correctness tests.'
- name: O-linux
  color: 6e6ec0
  description: 'Target: Support for building on Linux (GNU / musl) targets.'
- name: O-macOS
  color: 6e6ec0
  description: 'Target: Support for building on macOS / Darwin targets.'
- name: O-windows
  color: 6e6ec0
  description: >-
    Target: Support for building on Windows targets like
    `x86_64-pc-windows-msvc`.
- name: S-blocked
  color: d3dddd
  description: >-
    Status: Marked as blocked ❌ on something else such as other implementation
    work.
- name: S-do-not-merge
  color: d3dddd
  description: 'Status: This pull request should not be merged.'
- name: S-duplicate
  color: d3dddd
  description: 'Status: This issue or pull request already exists.'
- name: S-invalid
  color: d3dddd
  description: 'Status: This issue or pull request is not well-formed.'
- name: S-speculative
  color: d3dddd
  description: 'Status: This is just an idea.'
- name: S-stale
  color: d3dddd
  description: >-
    Status: This PR is stale. Please open a new PR if you'd like to pick this
    back up.
- name: S-wip
  color: d3dddd
  description: 'Status: This pull request is a work in progress.'
- name: S-wontfix
  color: d3dddd
  description: 'Status: This issue or pull request will not be worked on.'

🏃 Running GitHub Labeler
[dryrun] ✅ Skipping update for 'A-build' label. Same color and description
[dryrun] ✅ Skipping update for 'A-clang-format' label. Same color and description
[dryrun] ✅ Skipping update for 'A-cli' label. Same color and description
[dryrun] ✅ Skipping update for 'A-deps' label. Same color and description
[dryrun] ✅ Skipping update for 'A-distribution' label. Same color and description
[dryrun] ✅ Skipping update for 'A-embedded-bin' label. Same color and description
[dryrun] ✅ Skipping update for 'A-performance' label. Same color and description
[dryrun] ✅ Skipping update for 'A-project' label. Same color and description
[dryrun] 🔨 Updating 'A-release' label with color 'f7e101' and desc 'Area: crates.io and npmjs.org releases and version bumps.'
[dryrun] ✅ Skipping update for 'A-security' label. Same color and description
[dryrun] ✅ Skipping update for 'C-bug' label. Same color and description
[dryrun] ✅ Skipping update for 'C-docs' label. Same color and description
[dryrun] ✅ Skipping update for 'C-enhancement' label. Same color and description
[dryrun] ✅ Skipping update for 'C-quality' label. Same color and description
[dryrun] ✅ Skipping update for 'C-question' label. Same color and description
[dryrun] ✅ Skipping update for 'E-easy' label. Same color and description
[dryrun] ✅ Skipping update for 'E-medium' label. Same color and description
[dryrun] ✅ Skipping update for 'E-hard' label. Same color and description
[dryrun] ✅ Skipping update for 'E-help-wanted' label. Same color and description
[dryrun] ✅ Skipping update for 'E-needs-test' label. Same color and description
[dryrun] ✅ Skipping update for 'O-linux' label. Same color and description
[dryrun] ✅ Skipping update for 'O-macOS' label. Same color and description
[dryrun] 🎨 Creating 'O-macOS-arm' label with color '6e6ec0' and desc 'Target: Support for building on ARM macOS / Darwin targets.'
[dryrun] ✅ Skipping update for 'O-windows' label. Same color and description
[dryrun] 🎨 Creating 'S-archive' label with color 'd3dddd' and desc 'Status: This pull request exists to archive an unmerged branch.'
[dryrun] ✅ Skipping update for 'S-blocked' label. Same color and description
[dryrun] ✅ Skipping update for 'S-do-not-merge' label. Same color and description
[dryrun] ✅ Skipping update for 'S-duplicate' label. Same color and description
[dryrun] ✅ Skipping update for 'S-invalid' label. Same color and description
[dryrun] 🎨 Creating 'S-postponed' label with color 'd3dddd' and desc 'Status: This issue or pull request is being postponed until later.'
[dryrun] ✅ Skipping update for 'S-speculative' label. Same color and description
[dryrun] ✅ Skipping update for 'S-stale' label. Same color and description
[dryrun] ✅ Skipping update for 'S-wip' label. Same color and description
[dryrun] ✅ Skipping update for 'S-wontfix' label. Same color and description
[dryrun] 🔫 Deleting 'dependencies'


custom config files not working for PROD

Hi,
When setting the path to a config file in the package.json or using arguments in PROD mode the resolved file is always the default version of the config.
in runBundle:
  const taskInfo = (options.isProd) ? ROLLUP_PROD_TASK_INFO : ROLLUP_TASK_INFO;
  rollupConfig = fillConfigDefaults(context, rollupConfig, taskInfo);

The task is identified as PROD and sent to fillConfigDefaults.
fillConfigDefaults will load the configuration files using getConfigFileData (util.ts)
getConfigFileData(task.fullArgConfig, task.shortArgConfig, task.envConfig, null, context) || {};

Now, let's assume using config values from package.json (env). There is not way to distinguish between prod / dev in the config section so the end result is always loading xxx.config.js and not xxx.prod.config.js. getConfigFileData does not implement prod/dev file selection.
Since config inside package.json is not aware of prod/dev modes you probably need to decide on a convention to load files based on configuration preset. Something like add .prod for prod etc...

You could pass your production config file in with command line arguments
--rollup ionic-rollup-prod.config.js
the other option would be to update src/bundle.ts line 159 to something like envConfig: 'ionic_rollup_prod',

@strictd the 1st option, using arguments, will probably work but I prefer using the config object.
Yes, explicitly looking for ionic_rollup_prod can be added to the code but then a user will need to do that for every config file, this is not ideal.
I think a convention should take place and having 1 config file with added convention name.

are you looking for prod configs for all ionic-app-script configs or just the rollup config? There is a rollup.prod.config.js file that the bundler defaults to on production builds.

@strictd I know the is a rollup.prod.config in the package, that's the point of this issue - being able to override it.

I see your point.. Originally my thought was you wanted a complete second set of config files for prod. Which could be useful past the rollup configs for reasons nobody has thought of yet.

We're not using a single rollup config file: https://github.com/driftyco/ionic-app-scripts/blob/master/config/rollup.config.js#L56
Within the configs you can now check for: process.env.IONIC_ENV == 'prod'

doing npm run build or ionic build goes production


Already up to date message is not shown in the pull from remote section.

@Nageswari-droid fix delivered - https://github.com/neel1996/gitconvex/commit/d4701801bc85de59201d17d88b107812d2bd59ed


[Bug report] eval_point is True

Hi yuan-yin,
Thank you for your great work! I noticed an issue when I ran the code, and hope to get clarified.
In the ode_model.py line 87, the condition eval_point is True always returns False regardless of the value (True/False) of eval_point. Is this normal? Will it affect the final result if I change the condition into eval_point == True?
Thank you for your assistance in advance!
Best regards,
Shurui

Hi Shurui,
Thank you for your interest in our work. If you look at L81, the eval_points are indeed generated, so it is not always True. Even though it's highly probable to be True at the beginning of training due to an epsilon around 1, as the epsilon decreases, the behavior will change.
Hope this helps you.
Best regards,
Yuan

Hi Yuan,
Thank you for your prompt response! What I mean was that the condition eval_point is True cannot work properly. Even when eval_point == True, eval_point is True will return False. This behavior leads to that the code between line 88 and line 95 will never be executed.
Best regards,
Shurui

Ah ok, sorry I didn't well understand the question. It's quite curious because when we originally wrote this code, it worked fine. Perhaps there have been some changes in the behavior of numpy. If changing to == works for you, feel free to proceed, and I'll investigate it further.

I am pretty sure right now that there was a behavior change in NumPy for numpy.bool_ type. Before, it was the same as Python's bulti-in bool. I will correct this. Thank you for your report.


Failure to create USB installer

Describe the bug
I followed the tutorial for new installation media preparation here. I choose a 16Gb USB 3.0 Cruzer Mini stick to prepare the installer. Installer creation failed with a The installation failed error when I tried to patch the installer
Expected behavior
USB installation media should be created successfully
Environment:

Running OSX version: macOS Catalina 10.15.1
Target drive OSX version: macOS Catalina 10.15.1
HaC Mini installer version: v 2.4

Additional context
Screenshots of patch options and the error -

Logs
install.log

Looks like the same as #96

@osy86 Sincerely appreciate all the effort you've put in the guide and your kindness in sharing it with the rest of the world.
Marking this issue as duplicate of #96 doesn't quite make sense as it seems like a Hackintosh is required to prepare a HacMini installer. For someone like myself without a Hackintosh to prepare an installer, is it correct to assume HacMini installer can only be prepared with a Hackintosh? If yes, this can be added a note of warning in the Gitbook guide....

I don’t know what you’re talking about, it’s the same error as seen in the install.log?

Yes, it is the same error from the install.log attached in #96.
What I am trying to say -- Adding a note or warning in the section - https://osy.gitbook.io/hac-mini-guide/installation-guide/installation, like here -

that SIP must be disabled when creating USB installation media in a real Mac (not Hackintosh) will help enthusiasts not get stuck right at the beginning.
Peace!

Sorry it’s indeed a bug and I haven’t had time to fix it yet. Once it’s fixed there isn’t a need to disable SIP.


Feature Request: Asset search

Hello,
i really like your project :)
It would be nice if it is possible to specify the binary that i want to download from a group of release assets.
e.g.:
https://github.com/CrunchyData/postgres-operator/releases
There are some assets:
pgo
pgo-bash-completion
...
postgres-operator.4.5.0.tar.gz

That want i want is just to install pgo and pgo-bash-completion.
What do you think of a new cli flag called --regex-search
bin install https://github.com/CrunchyData/postgres-operator --regex-search "^pgo$" ~/.local/bin/pgo
bin install https://github.com/CrunchyData/postgres-operator --regex-search "^pgo-bash" ~/.local/completions/pgo-bash-completion
Best regards
Stefan

Bump.
Still when i do: "bin install https://github.com/CrunchyData/postgres-operator/" i get the tar file instead of the binary i want.

Bump.
Still when i do: "bin install https://github.com/CrunchyData/postgres-operator/" i get the tar file instead of the binary i want.

That is because the repository in question does not name their release assets in a helpful way. I recommend you raise this issue in that particular repo.

It would be nice if it is possible to specify the binary that i want to download from a group of release assets.

I think this use-case might still be valid though. Maybe instead of doing something like --regex-search we can just add a --no-score flag or something similar so the user gets prompted with binary to download. WDYT @sirlatrom @breml ?

It would be nice if it is possible to specify the binary that i want to download from a group of release assets.

I think this use-case might still be valid though. Maybe instead of doing something like --regex-search we can just add a --no-score flag or something similar so the user gets prompted with binary to download. WDYT @sirlatrom @breml ?

Maybe something like --no-filter?

Maybe something like --no-filter?

Yep, that sounds better. Since scoring is an internal implementation detail.


'expires_in' response from Oauth token server is sometimes string

What happened?
I was using @auth/sveltekit with Azure-AD provider and ran into this issue. The expires_in is returned as a string, which fails this library's JWT checks.
Oauth Provider: Azure Active Directory (Azure AD)
Project: Sveltekit
Auth Library: @auth
Nodejs 18x
Version
2.3.0
Runtime
Node.js
Runtime Details
18.x
Code to reproduce
import { SvelteKitAuth } from '@auth/sveltekit'
import AzureAD, { type AzureADProfile } from '@auth/core/providers/azure-ad'
import type {
	AuthorizationEndpointHandler,
	OAuth2Config,
	TokenEndpointHandler
} from '@auth/core/providers/oauth'
const token: TokenEndpointHandler = {
	url: //url,
	request: async (context: any) => {
		console.log({ context })
	}
}
const authorization: AuthorizationEndpointHandler = {
	url: //url,
	request: async (context: any) => {
		console.log({ context })
	}
}
const params: OAuth2Config<AzureADProfile> = {
	id: 'azure',
	type: 'oauth',
	issuer: // issuer,
	name: 'Azure AD',
	authorization,
	token,
	clientId: process.env.AZURE_AD_CLIENT_ID,
	clientSecret: process.env.AZURE_AD_CLIENT_SECRET,
	client: {
		client_id: process.env.AZURE_AD_CLIENT_ID,
		client_secret: process.env.AZURE_AD_CLIENT_SECRET,
		redirect_uris: ['https://localhost:5173/auth/login/azure'],
		default_max_age: 60 * 60,
		require_auth_time: true
	}
}

export const handle = SvelteKitAuth({
	providers: [
		// eslint-disable-next-line @typescript-eslint/ban-ts-comment
		// @ts-ignore
		AzureAD({ ...params, tenantId: process.env.AZURE_AD_TENANT_ID })
	],
	secret: process.env.AUTH_SECRET,
	session: {
		maxAge: 60 * 60 // 1 hour
	}
})

Required

[X] I have searched the issues tracker and discussions for similar topics and couldn't find anything related.
[X] I agree to follow this project's Code of Conduct

It's the defined as a number, so the rejection is right in place. If you want, you can parse the Response instance and re-instantiate it with a fixed expires_in member.

Correct! Both libraries (this and @auth/core) expect the value as a number. It sounds like for some reason Azure returns it as a string.
There is a way to make the provider's response conform to spec, here is an example: https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/twitch.ts/#L87-L115
If you could open this issue on the right repository at https://github.com/nextauthjs/next-auth we could look into this. We also accept a PR if you want to fix this. The file that needs to fix is https://github.com/nextauthjs/next-auth/blob/main/packages/core/src/providers/azure-ad.ts


Fixing edit and issues link in docs.

Updating link to repository so that the edit and new issues link work.
Currently the links in the right sidebar still lead to the nextra repository:

I've changed it so it now points to the right one. The reason I noticed was that now macOs 13.5 is needed and I wanted to fix the docs. :) #3

Thanks for the change!


excel预览不显示，报错 Cannot read properties of undefined (reading 'anchors')，是因为有图片的原因么

Cannot read properties of undefined (reading 'anchors')
vue版本2.6.14
"@vue-office/excel": "1.7.3",

那就换个文件看看，确认下原因


Looks like toml does not support enums. But ktoml supports, need to make it configurable

Enums should beprocessed only with a config enabled
Entry point: KtomlConf

@akuleshov7 not sure I totally agree with this one, JSON does not have the concept of enums either, but enums are still serialized  in JSON with their name. Enums are only a way to store an info deserialized from the TOML data.

I wanted to make this configurable, but yes, it looks like a bad idea (as mentioned by @bishiboosh in the above comment)


Add 'requests' as a dependency

Thanks for writing this library! I just started using it and noticed that it uses the requests library, but it's not marked as a dependency in setup.py. Should it be added?

Thanks for pointing that out, totally missed that. I'll update it today.

Completed in https://github.com/nathan-fiscaletti/ipstackgeo-py/commit/51aede552bad193ab2d3616d951a750e0affd3c5


PowerBI shows blank entries

The PowerBI does not show any data in the screen, thought it shows data is being loaded.

There are no Firewall issues connecting to the SQL Database, and I can see entries in the Recommendations table.

The Power BI report shows empty if there aren't recommendations newer than 7 days in the SQL Database. It has a 7-days old filter in each of the pages. If the Ingest-RecommendationsToSQLServer runbook has been failing or hasn't ingested new recommendations in the last weeks, then this is an expected behavior. The reason for that is probably related to the other issue you reported. Once the runbook starts working again, you should see recommendations in Power BI.
As an alternative to the Power BI report, you can also use the Recommendations workbook you should find in the AOE Log Analytics workspace.

This is still an issue, where I still see the runbook job ... failing due to the below error :
Exception calling "ExecuteReader" with "0" argument(s): "String or binary data would be truncated in table 'sqldbxxxxx.dbo.Recommendations', column 'ImpactedArea'. Truncated value: 'Microsoft.ApiSecurity/apiCollections/apiCollection'. The statement has been terminated." (String or binary data would be truncated in table 'sqldbxxxxx.dbo.Recommendations', column 'ImpactedArea'. Truncated value: 'Microsoft.ApiSecurity/apiCollections/apiCollection'. The statement has been terminated.)
Please let me know if I need to raise this as a new issue.

@arunjvai , this is a known issue, which will be fixed in the next release. Meanwhile, please run the following T-SQL statement in the AOE database:
ALTER TABLE [dbo].[Recommendations] ALTER COLUMN [ImpactedArea] VARCHAR (255) NULL


ci: add tags to AWS instances

The new terraform runners support an extended lists of tags to get a greater precision on the stats we can extract from AWS cost center.

@bcl do you know anything about the failing test?

@bcl do you know anything about the failing test?

Yeah, it's triggered by something that only effects windows. govulncheck doesn't have any way to make it ignore things like that :/


Problems with LaTeX strings

First of all, thank you very much for the LaTeX string support introduced in v0.15! :)
I've currently found two problems with it which I'd like to report.

Trying to concatenate strings for tick labels fails

xticks = ([0.0, 1.0, 2.0, 3.0],
            [L"a = 0", # regular LaTeXString works fine
            "b = " * "1", # concatenating two regular strings works fine
            "c = " * L"2", # concatenating regular string & LaTeXString causes all latex string rendering for ticks to break
            L"d = " * L"3"]), # concatenating two LaTeXStrings causes all latex string rendering for ticks to break

It would be great if we could use multiple types of strings together. This seems to be due to the fact that the result is always the supertype String and not the more specific LaTeXString.
julia> typeof(L"c = 2")
LaTeXStrings.LaTeXString

julia> typeof("c = " * L"2")
String

Line breaks don't work and cause parsing errors

xticks = ([0.0], [L"a = \\0"])

This would be awesome to have more formatting options.

Inserting regular text causes parsing errors

xticks = ([0.0], [L"a = \text{INPUT} 0"])

Would be cool if this would allow to "inject" regular strings into LaTeXStrings.

Forced spaces in equations cause parsing errors

xticks = ([0.0], [L"a \; = \; 0"])

This would allow for more formatting options.

I'm not sure if I understand the problem fully, but these look like feature requests for: https://github.com/stevengj/LaTeXStrings.jl

I think you're right, most of them should be mentioned over there.
One thing that's likely a suggestion for Makie would be that the following
xticks = ([0.0, 1.0], ["a = 0", L"b = 1"]),

causes both tick labels to be displayed as regular strings, i.e. the LaTeXString is just displayed as $b = 1$ instead of being rendered by the engine.
Maybe it's possible to render the ticks one by one so that they can be treated separately?

The last three things are MathTeXEngine feature requests. The example with the two different types needs a specific routine handling multiple different AbstractStrings in one text plot, that could be a bit more difficult than it sounds due to the special requirement of latexstrings that there needs to be a linesegments plot for sqrt and frac lines.

Cant we just promote ([0.0, 1.0], ["a = 0", L"b = 1"]) to   ([0.0, 1.0], [L"a = 0", L"b = 1"]) ( i dont know the escaping by hard, but I guess one should be able to render a normal string in a latex string

Cant we just promote

This would be a workaround to force math rendering but if a user deliberately wants to combine regularly rendered strings and MathTeXEngine rendered strings, this would get in the way.

I mean my point was, that you can render regular strings as latex strings, no? Am I overestimating the escaping powers for Latex strings?

I may be wrong, but it seem MathTexEngine.jl can't yet render basic fonts (\mathrm{something}) nor spaces (, ; : etc) in LaTeX, otherwise it would be possible to use LaTeXStrings to replace strings. Also, it can't render accent symbols like \vec{a} yet. Well, at least that's what the MathTexEngine.jl says in its current github description.

Yes, I also checked for that, @ghralima. It definitely seems like MathTexEngine.jl needs a bit more work to support usual commands like spaces and text parts. Once that's implemented, we can simply use those tex commands to get what I would like to achieve (mixed formatting of standard strings and latex strings). Once this is done, I suppose promoting all regular strings to tex strings would solve the aforementioned problem with the tex rendering being omitted.

I reported the issues that goes to MathTeXEngine to keep track of everything.

Line breaks don't work and cause parsing errors

This will ignore text alignment at first, because MathTeXEngine currently has no mechanism to deal with text alignment by itself. For single line text this call always be dealt with by the backend so it is not a problem, for multiple lines some work will maybe be needed from the Makie side too.

Inserting regular text causes parsing errors

Once #1160 is finished, it will be accessible using $ e.g. L"$x = 2$ or sometimes $x = 42$".
Supporting other font commands should be possible in the future too (e.g. \mathrm).


Multiple workspaces

Hi, love the idea behind this project! It solves problems I encounter daily.
I have an idea for new functionality (if this is not already doable):
It would be very useful to specify config files per workspace, allowing multiple workspaces on the same machine.
For instance, I have multiple workspaces (directories containing related repos) and it would be useful to define separate configurations for each workspace – one for the company where I work, one for open source projects I contribute to, etc. That way, if I wanted to use fw at work, I could pass on my company config to my coworkers without necessarily including the open source projects I have in my other workspace.
The root/global config ~/.fw.json could contain entries for both of these workspaces to allow easy recreation for myself across multiple machines while also able to share the individual workspace configs easily among colleagues.
Here are some ideas I have about how this could work:

on each fw run, check for config in the current directory or parent directories (per-workspace configs), falling back to $FW_CONFIG_PATH/.fw.json (global config)
in the global config ($FW_CONFIG_PATH/.fw.json) have a settings.workspaces array containing the paths to each workspace
each workspace path would contain its own .fw.json to manage that workspace.

Changes to the CLI to support this could be:

setup flags --global (default, writes config to FW_CONFIG_PATH) and --workspace (writes config to workspace root)
for subcommands, it could work like this: fw my-company [subcommand] where my-company is the workspace name.

Let me know what you think. If this is a viable addition, I'm willing to contribute some code.

Thanks for opening an issue! Supporting more use cases is certainly something we'd like to do.
If the use case is sharing and splitting up in workspaces, that's already possible though I don't know how well it works for you:

create a tag "private", and have that tag override the project workspace directory
create a tag "company1" and have that tag override the project workspace directory to something else
tag private projects and company projects
export for a colleague is done with export and specifying the tag to filter (I don't think we have that feature currently but would be quite easy to add)

Let me know what you think about this.
I am currently not sure if it is desirable to support fw   because this would require you to choose a company every time (including when using something like workon to switch projects).

On 14. Nov 2018, at 23:03, Caleb Williams<EMAIL_ADDRESS>wrote:
Hi, love the idea behind this project! It solves problems I encounter daily.
I have an idea for new functionality (if this is not already doable):
It would be very useful to specify config files per workspace, allowing multiple workspaces on the same machine.
For instance, I have multiple workspaces (directories containing related repos) and it would be useful to define separate configurations for each workspace – one for the company where I work, one for open source projects I contribute to, etc. That way, if I wanted to use fw at work, I could pass on my company config to my coworkers without necessarily including the open source projects I have in my other workspace.
The root/global config ~/.fw.json could contain entries for both of these workspaces to allow easy recreation for myself across multiple machines while also able to share the individual workspace configs easily among colleagues.
Here are some ideas I have about how this could work:
on each fw run, check for config in the current directory or parent directories (per-workspace configs), falling back to $FW_CONFIG_PATH/.fw.json (global config)
in the global config ($FW_CONFIG_PATH/.fw.json) have a settings.workspaces array containing the paths to each workspace
each workspace path would contain its own .fw.json to manage that workspace.
Changes to the CLI to support this could be:
setup flags --global (default, writes config to FW_CONFIG_PATH) and --workspace (writes config to workspace root)
for subcommands, it could work like this: fw my-company [subcommand] where my-company is the workspace name.
Let me know what you think. If this is a viable addition, I'm willing to contribute some code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for opening an issue! Supporting more use cases is certainly something we'd like to do.
If the use case is sharing and splitting up in workspaces, that's already possible though I don't know how well it works for you:

create a tag "private", and have that tag override the project workspace directory
create a tag "company1" and have that tag override the project workspace directory to something else
tag private projects and company projects
export for a colleague is done with export and specifying the tag to filter (I don't think we have that feature currently but would be quite easy to add)

Let me know what you think about this.
I am currently not sure if it is desirable to support fw   because this would require you to choose a company every time (including when using something like workon to switch projects).

The export command currently only supports exporting one project. https://github.com/brocode/fw/blob/master/src/main.rs#L383
As @mriehl said exporting by tag would be quite easy to add.
I don't think looking up the directory tree for the an fw config would be that convenient. You would have to cd to that directory to be able to use workon.
I myself would add an alias to flip FW_CONFIG_PATH but I don't know if that would solve your problem.
You're not the first one to ask about something like this. The last time we added FW_CONFIG_PATH but never got feedback if it solved the problem. So if our suggestions don't work for you let us know what you think.

@br0p0p The new fw release support export-by-tag.


warmup api is not working?

I have  KNN plugin built from source and added as a plugin to ES OSS 7.8.0.
When I am running warmup api, I am hitting error. any pointers?
GET /_opendistro/_knn/warmup/bugdata,budata_knn?pretty

{
  "error" : "no handler found for uri [/_opendistro/_knn/warmup/bugdata,budata_knn?pretty=&pretty=true] and method [GET]"
}

looks like warmup api is not yet present in official release build of knn(i.e 1.9.0). please correct if i am wrong, else I will close the ticket and wait for next version to be available.

@mtikmani, yes your understanding is correct. Warmup api available from 1.10.0.

If my understanding is correct, is there a way I can manually load all the graphs post bulk indexing?
You will have to run few queries to load the graphs to memory. Probably run queries for a minute or two.


memcached ServerIsMarkedDead

I'm building a gem and added memcached as a dependency but then when I add it:
require "coinmarketcap/wrapper/version"
 require "coinmarketcap/wrapper/api_client"
 require "coinmarketcap/wrapper/coin"
 require "coinmarketcap/wrapper/market_data"
 require 'json'
 require 'api_cache'
 require "moneta"
 require "memcached"

 module Coinmarketcap
   module Wrapper
     BASE_API_URL = "https://api.coinmarketcap.com/v1"

     APICache.store = Moneta.new(:Memcached)
   end
 end

and then run bin/console I get an error:
Memcached::ServerIsMarkedDead: Key {"9aaf5eb3d6edd10f12643e3087b84d21"=>"<IP_ADDRESS>:11211:8"}
is there a configuration I am missing?

that means you have to make sure that Memcached server in your machine is running
ps aux | grep memcache


Python 3.7 - DeprecationWarning: the imp module is deprecated in favour of importlib during install

Issue description
pipenv install requests_html.
DeprecationWarning: the imp module is deprecated in favour of importlib
Expected result
Install package requests_html in pipenv.
Actual result
Creating a virtualenv for this project...
Pipfile: /home/kodi/Code/app/Pipfile
Using /usr/bin/python (3.7.0) to create virtualenv...
⠋Already using interpreter /usr/bin/python
Using base prefix '/usr'
/usr/lib/python3.7/site-packages/virtualenv.py:1039: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  import imp
New python executable in /home/kodi/.local/share/virtualenvs/app-z8LAYKO_/bin/python
Installing setuptools, pip, wheel...done.
Setting project for app-z8LAYKO_ to /home/kodi/Code/app

Virtualenv location: /home/kodi/.local/share/virtualenvs/app-z8LAYKO_
Creating a Pipfile for this project...
Installing requests_html...
⠇
Error:  An error occurred while installing requests_html!
Can not perform a '--user' install. User site-packages are not visible in this virtualenv.

pypa/virtualenv#1191. Not part of Pipenv.

My problem was that I had set "user = yes" in "~/config/pip/pip.conf"


learn.svelte.dev part 2/motion/tweens fails to render

This page:
https://learn.svelte.dev/tutorial/tweens
does not render in Google Chrome 119.0.6045.214 on a Google-branded Model C0A Chromebook.
The svelte code for this tutorial defines various buttons and a progress bar.  None of these are visible.

Hmm.  This is working now.
I wasn't seeing the "starting dev server" message before, when it was failing.


I can't setup CVCalendar

I made all.
@IBOutlet weak var menuView: CVCalendarMenuView!
 @IBOutlet weak var calendarView: CVCalendarView!

and
` override func viewDidLayoutSubviews() {
super.viewDidLayoutSubviews()
    menuView.commitMenuViewUpdate()
    calendarView.commitCalendarViewUpdate()
}`

but I don't see calendar. I see only white view on the top

@nikolaymac did your problem solve? got stuck in same problem

yes! I find solution :) They forgot about delegate in Docs.  Add CVCalendarViewDelegate,CVCalendarMenuViewDelegate
and this methods
func presentationMode() -> CalendarMode {
return .monthView
}
func firstWeekday() -> Weekday {
    return .monday
}


spdx3: element_writer: unindent creation information

Hello everyone,
This is my first issue to this repository. I am new to SPDX and apologize for possible misunderstanding of the intentions behind the code I am modifying.
I am integrating the SPDX 3.0 export to the StrictDoc tool, see https://github.com/strictdoc-project/strictdoc/issues/1541.
The starting point for this issue is the fact that the Creation Information block is suddenly nested with a tab character when I try to populate an spdx3.*.SpdxDocument and write to a string buffer. My IDE is set up to ignore tab characters, so the output is displayed as if the indentation level was 1 character wide.

In this MR, the creation info is unindented, and a test is added to demonstrate the behavior I would expect to see.

I think that the indentation was intentional. As sub-structures within an object are also come with indentation in other places. Maybe we could indent with spaces instead of \t to be more stable.

I think that the indentation was intentional. As sub-structures within an object are also come with indentation in other places. Maybe we could indent with spaces instead of \t to be more stable.

This makes sense. Definitely it would make sense to replace \t with \n\n for example.
An extra thought regarding the indentation of creation info: in YAML things are indented when there is a key that bundles together indented content. On the screenshot above, the role of a "key" is played by a comment Creation Information which to me looks confusing visually because it is just a comment and on actual key.
In YAML this would look like:
creation_info:
  spec_version: ...
  ...

I am ready to both engage or disengage, so how could we proceed? Is it worth to use this MR for replacing \t with \n\n everywhere?

we would appreciate if you would make the changes to spaces. But you could also just put it into a new issue, if you want.

we would appreciate if you would make the changes to spaces. But you could also just put it into a new issue, if you want.

Please check the change I've made.


[Minor] Simplify window using null array

Which issue does this PR close?

Rationale for this change
Code simplification

What changes are included in this PR?
Use new_null_array

Are there any user-facing changes?
No

Codecov Report

Merging #370 (7c5975a) into master (1fc48da) will increase coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #370      +/-   ##
==========================================
+ Coverage   82.49%   82.60%   +0.10%
==========================================
  Files         162      162
  Lines       43980    44167     +187
==========================================
+ Hits        36282    36483     +201
+ Misses       7698     7684      -14

Impacted Files
Coverage Δ

arrow/src/compute/kernels/window.rs
100.00% <100.00%> (ø)

parquet/src/encodings/decoding.rs
92.47% <0.00%> (-0.02%)
:arrow_down:

arrow/src/error.rs
8.88% <0.00%> (ø)

arrow/src/csv/writer.rs
82.64% <0.00%> (ø)

parquet/src/column/writer.rs
93.29% <0.00%> (ø)

arrow/src/array/raw_pointer.rs
100.00% <0.00%> (ø)

arrow/src/array/array_string.rs
96.05% <0.00%> (ø)

arrow/src/util/string_writer.rs
73.33% <0.00%> (ø)

arrow/src/array/array_boolean.rs
90.90% <0.00%> (ø)

arrow/src/array/array_primitive.rs
92.93% <0.00%> (ø)

... and 16 more

Continue to review full report at Codecov.

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


Sample repo with Gemfile and sample database.yml files

Also, maybe a rake task to generate database.yml files


TypeError: Cannot read properties of undefined (reading 'state') in Production Mode

Hi,
I built the source code and served it with serve, however, I encountered the following issue as bellow

npm install
npm run build
serve -s dist

Could you help give some advice?

Looks like Vite is not configured correctly for deployment. Something related to compatibility with the browsers.
I am not currently maintaining this code and it was indeed just intended for demonstration, not for production. The dev version works. I am afraid I have not used Vite or Vue for a while and it would take me quite a while to fix it.
You can try to change some parameters according to this guide:
https://vitejs.dev/guide/build.html
Also, I think if you just copy the dist folder to a server it should work for production at least in Chrome and Firefox.
I can't guarantee I will fix it...


integration tests: setup LND

Reopening #74

Ok I made those changes :) I managed to commandeer my partner's Macbook to figure out what the trouble was on MacOS (wish I had thought of that earlier) and I think it's solved now. Lmk if it works for you @carlaKC

@carlaKC Awesome :) Thanks for all the reviews!


 The main thing is that there's a single command to run which
does all this and we can update what that command actually does at our
leisure.
Thinking more broadly, it might make sense to make it a convention
across all projects that they have such a command.

Great!


recommendation on how to handle "disable the other plugin" messages

This commit introduced warning messages whenever we configure Noice to take over handlers from LSP or notify. In particular, the messages suggest along the lines of

Either disable the other plugin or set config.<optiosn>= false in your Noice config.

what is the intended behaviour here? Does this mean that whenever Noice is active (namely, if these options are active) one needs to disable the other plugins (notify, cmp, lsp) altogether? Wouldn't this however introduce a behaviour of Noice claiming to be explicitly incompatible with the plugins, so it is either Noice or the others (and they cannot be used together)? What is the suggested course of actions here?
(I find it a little strange to have to disable the other plugins or those handlers altogether, because they may be still needed for other custom functions that users defined or external plugins).

If you tell noice to handle vim.notify for example, and later we see another plugin took that over, then obviously the noice handler wil no longer work.
Is up to the user to decide how to handle the situation.
I'm sure things like that happen frequently in other plugins, but they don't have any checks in place. And that can obviously lead to issues.
So again. Totally up to you.
Out of curiosity what did you get this for?

Out of curiosity what did you get this for?

I am getting this messages upon starting neovim, without even exacuting anything or opening any files. In particular I am using the configuration shown in the README
 override = {
      ["vim.lsp.util.convert_input_to_markdown_lines"] = false,
      ["vim.lsp.util.stylize_markdown"] = false,
      ["cmp.entry.get_documentation"] = false,
    },

which makes me puzzle: according to your comment above

and later we see another plugin took that over, then obviously the noice handler wil no longer work.

does this mean that either lsp/cmp or noice must be enable, and not both of them at the same time? See screenshot below
https://user-images.githubusercontent.com/15387611/198841128-3bcf3cda-41ae-4917-be85-663c96aa3391.mov
(in particular about the vim.lsp/cmp handlers). So while I do agree that if one explicitly invokes a handler from another plugin to take over, warning messages must occur, I would like to better understand why these messages are generated upon start-up in the context of lsp/cmp.

ok, so there was a bug in the healthcheck.
Apparently plugged doesn't use standard Neoivm pack site paths so detection went wrong. Should be fixed.
All those handlers are already Noice, so you should be good :)

I confirm it's fixed, thank you for looking into it!


chore: implement arbitrary comparison for BLS keys

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (main)
[ ] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the GitHub PR explorer

Should we add a test?

Should we add a test?

test added in a45fcb5


Flutter won't run on iOS after updating to 1.15.22-pre.18. Xcode build failing

I am writing a flutter app that was working fine up until tonight. It compiled and ran on both iOS simulator and iOS device. This evening, VSCode informed me there was a new version of Flutter so I upgraded. After the upgrade, Flutter Doctor told me to upgrade cocoapods, which I also did (after having to mess around with the Ruby 2.3 SDK since i'm on OSX 10.14.6. However, now my project won't build for either iOS simulator or iOS device.
I've tried 'flutter clean' but to no avail.
The error I get is:
** ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS13.2.sdk/usr/lib/libSystem.tbd, missing required architecture x86_64 in file /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS13.2.sdk/usr/lib/libSystem.tbd (4 slices) ld: building for iOS, but linking in object file (/var/folders/fh/fs6qqn7x5_5c3bbq36ct4nj40000gn/T/debug_app-2d4374.o) built for iOS Simulator, file '/var/folders/fh/fs6qqn7x5_5c3bbq36ct4nj40000gn/T/debug_app-2d4374.o' for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) Command: xcrun clang -x c -arch x86_64 /var/folders/fh/fs6qqn7x5_5c3bbq36ct4nj40000gn/T/flutter_tools_stub_source.F8IoZt/debug_app.cc -dynamiclib -fembed-bitcode-marker -Xlinker -rpath -Xlinker @executable_path/Frameworks -Xlinker -rpath -Xlinker @loader_path/Frameworks -install_name @rpath/App.framework/App -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS13.2.sdk -o /Users/paul/Documents/Development/flutter/scale_practice_app2/.dart_tool/flutter_build/eabd0dc878995215df4262cdd052ace8/simulator_framework build failed. note: Using new build system note: Planning build note: Constructing build description Could not build the precompiled application for the device.
It appears that your application still contains the default signing identifier. Try replacing 'com.example' with your signing id in Xcode: open ios/Runner.xcworkspace
Error launching application on Paul's iPhone XR.**
Here is the output of 'flutter doctor -v':
**[✓] Flutter (Channel master, v1.15.22-pre.18, on Mac OS X 10.14.6 18G3020, locale en-GB) • Flutter version 1.15.22-pre.18 at /Users/paul/Apps/flutter • Framework revision 8bff33e497 (2 hours ago), 2020-03-13 17:26:02 -0700 • Engine revision 9226a3881e • Dart version 2.8.0 (build 2.8.0-dev.14.0 a303769fad)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3) • Android SDK at /Users/paul/Library/Android/sdk • Android NDK location not configured (optional; useful for native profiling support) • Platform android-29, build-tools 29.0.3 • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405) • All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1) • Xcode at /Applications/Xcode.app/Contents/Developer • Xcode 11.3.1, Build version 11C504 • CocoaPods version 1.9.1
[✓] Android Studio (version 3.5) • Android Studio at /Applications/Android Studio.app/Contents • Flutter plugin version 43.0.1 • Dart plugin version 191.8593 • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.43.0) • VS Code at /Applications/Visual Studio Code.app/Contents • Flutter extension version 3.8.1
[✓] Connected device (3 available) • Paul's iPhone XR • 00008020-001B64482ED8003A • ios • iOS 13.3.1 • iPhone XR • 154A94BD-01CF-40B0-B25E-88073359CA3E • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-3 (simulator) • macOS • macOS • darwin-x64 • Mac OS X 10.14.6 18G3020
• No issues found!**
I followed some Google suggestions to re-create my pod files etc but that hasn't fixed it. I have also created a fresh Flutter project, copied in my .dart and assets files but the new project still won't build, with the same errors.
Any help would be greatly appreciated.
Thanks

Complete uninstall and re-install of cocoapods, flutter, and xcode (including manually clearing out all preferences) worked.


export (ENUM) var a little verbose

Version: 4547e223
Currently when an enum or const dictionary are supplied to an export var in the inspector.
Not sure if this is desirable, since the spirit of the enumerations is to shield our eyes from magic numbers.  Can get pretty messy in some cases.

I agree, the number should not be needed and makes it look kinda ugly.

I agree as well, but is that the consensus? Specifically, should the solution to this issue be that we delete the number or have it be connected to a setting the user can change?

This only happens when using the hint_string format that explicitly specifies the values: elem_one:0,elem_two:1,....


Add support for a custom PR template description used by gh-prx

Support a Go-template PR template that is used by gh prx separate from the github repositories default location. This would allow users of gh prx CLI to create templated pull-requests but also allow users to create pull-requests from the Web UI using a non-templated markdown template.
.github/PULL_REQUEST_TEMPLATE.md

E.g. ideally a user could specify in their .github/.gh-prx.yaml
pr:
   title: "{{.Type}}{{.Prefix}}{{with .Issue}}({{.}}){{end}}: {{humanize .Description}}" # PR title template
   ignore_commits_patterns: ["^wip"] # Patterns to filter out a commits from the {{.Commits}} variable
   answer_checklist: false # Whether to prompt the user to answer PR description checklists. Possible answers: yes, no, skip (remove the item)
   push_to_remote: true # Whether to push the local changes to remote before creating the PR
issue:
   provider: jira # The provider to use for fetching issue details (supported: github,jira,linear)
   types: ["fix", "feat", "chore", "docs", "refactor", "test", "style", "build", "ci", "perf", "revert"] # The issue types to prompt the user when creating a new branch
   pull_request_template: .github/PULL_REQUEST_TEMPLATE.ghprx.md # default is .github/PULL_REQUEST_TEMPLATE.md
   ignore_pull_request_template: false # If true, the pull request template in the repository will be ignored.

Hi @dougnukem
I'm terribly sorry for the long wait.
I've implemented those changes for you. Please note that pull_request_template_path is now in the root of the config, i.e.:
pr:
  ...
issue:
  ...
pull_request_template_path: <your_custom_path_from_repo_root>

Let me know if that solves your use case!


chore(deps): update dependency org.jruby:jruby-complete to v1.7.27

This PR contains the following updates:

Package
Type
Update
Change

org.jruby:jruby-complete
build
patch
1.7.26 -> 1.7.27

Release Notes

jruby/jruby (org.jruby:jruby-complete)
v1.7.27
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (1.7.27). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Gardens on xDai: Deploy Garden template

We have to deploy a new version of the Garden template that includes the latest changes.
Depends on #143

Done with: https://github.com/1Hive/gardens/pull/167/files#diff-9b56308ebc94a2c823e81976f496087112941dad7f4a720e8b42edf95f6da49c


Show defined datums on tolerance list view / properties pane

Add Datums section to properties pane and add datums to tree

Implemented with #416


Feature Request: User Defined List of Strings to Exclude When Searching for Artists or Albums

Users should have the option to define specific strings that will be stripped from the artist or album tag to increase the likelihood of a match, without having identical artist/album names to those listed in Apple Music. Ideally, this would be defined in a text file.
For example, I would like to exclude the following strings:
(Children’s)
(Christmas)
(Holiday)
[Live]
(Live)
and his orchestra
& his orchestra
and her orchestra
& her orchestra
: music from the original motion picture
 - music from the motion picture
(original soundtrack)

or even
(wildcard)
[wildcard]

Expanding upon the wildcard concept, adding *" feat. " and *" feat " would likely fix song titles what include a feature artist that is different from the primary artist

Sorry, I meant songs...
I believe that get_cover_art is doing a lookup for each song using existing [artist] and [album] metadata. If there is extraneous metadata, it causes the search to fail even though Apple Music has the artwork for that album.
Currently, punctuation is removed but--reviewing my skip_artwork.txt--get_cover_art appears to not strip parenthetical data (i.e. words in parentheses or brackets in the artist or album field) or words in the artist name including "feat. [name of featured artist]".
For example, George Strait Feat Willie Nelson - Honky Tonk Time Machine should be normalized to
[George Strait] and [Honky Tonk Time Machine]
As noted initially, other extraneous data that causes the search to fail include user-added parentheticals such as (holiday) or different stylings of an artist name such as the inclusion of "and his orchestra" for classical music/big band. Similarly, motion picture album metadata may have a lot of variants, so reducing the search term in the soundtrack album name will improve results.
For example, Celine Dion - Deadpool 2 Original Motion Picture Soundtrack should be normalized to
[Celine Dion] and [Deadpool 2]


Resolve full path of XCHammer for bazel_build.py

This fixes an issue with generating the path to bazel_build.py. The error message:
~/Library/Developer/Xcode/DerivedData/HammerLyft-apdrvgdqsckgxbeluodmnicxohsd/Build/Intermediates.noindex/HammerLyft.build/Debug-iphonesimulator/ArchitectureCore-Bazel.build/Script-SSBP_7741122292.sh: line 3: ./bazel_build.py: No such file or directory

The fix is to use ProcessInfo.processInfo.arguments instead of CommandLine.arguments because the former has the full path to XCHammer while the latter has just whatever was given on the command line, which will often be just "XCHammer".

Thanks for the PR @kastiglione  🎉. LGTM - and if our test suite is passing it should be mergeable. I don't remember why it originally used the Commandline.arguments vs this.