Inline sign in without leaving the website

User story

As a guest contributor willing to make a recurring contribution, leaving the website to validate my email is not a great experience because I loose the context of the page
As a signed out but verified user, it's a poor experience to get the error message This email already exists, please sign in after I clicked "Contribute", then having to sign in and come back to the flow and fill my payment info all over again.
Contributing through the (not yet released) embed contribution flow (#3003) or white-labelled interface, I may be confused about why I am asked to sign in on "Open Collective".
My email provider might be opening the links in my emails, invalidating the tokens (#3656)

Best solution for this problem
Rather (or in addition) to sending a link to sign in, we could send a special code to copy-paste directly in the flow.
For example, let's say I tried to contribute using my email but I'm not logged in. Instead of showing an error, we could open a modal like the one below. After copy-pasting the correct code, the contribution would continue seamlessly.
Ideally, the code should be short enough so that it can eventually be typed manually (ie. if you don't have access to your mailbox on your computer and are retrieving the code from your phone) but long enough to be secure. 12 characters alphanum with symbols could do the job (ie. X5slr.6}lOw2).

Who else does that?
Many platforms that use email as a way to do 2FA implement similar flows. For example, the gaming platform Steam shows this when you sign in from a new location/browser:

MVP
An MVP would be to implement that for the contribution flow only, when contributing with an email from a verified account while being logged out. It's not affecting many users, but it's a terrible experience so good candidate for experimenting this.
We could start by using the raw token (that is normally passed in the URL), which is a bit ugly but simplifies the initial implementation.

From today's discussion:

Codes should be limited in time
We should not have any special character (difficult to type or copy paste on mobile)
Need to do some more research on what others are doing and what's a good level of security for the code

@znarf also shared this beautiful example:

From today's discussion:

Codes should be limited in time
We should not have any special character (difficult to type or copy paste on mobile)
Need to do some more research on what others are doing and what's a good level of security for the code

@znarf also shared this beautiful example:

Feedback from @znarf:

The problem with security code is that it doesn’t play well with 2FA, entering 2 different codes one after the other is a poor USER experience. But we could keep magic links for 2FA protected accounts.

This would help to resolve https://github.com/opencollective/opencollective/issues/4265


Add check to avoid untested new function

Suggested enhancement
At the end of basic-build-test.sh or in a script that runs after it, (optionally) check the list of functions that were not covered in tests against an allowlist (maintained in the repository) and return a failure status is there are uncovered functions outside that list.
Justification
There's rarely a good reason for a whole function to not be executed at all by any test and we should avoid introducing new functions that are not covered at all by the tests. The proposed mechanism would flag such a situation by causing a CI failure. We can then either add tests covering that function, or add the new function to the allowlist if it was determined acceptable after careful consideration.
Related to https://github.com/ARMmbed/mbedtls/issues/5530 but different: it's possible for the percentage of function coverage to not drop significantly while we introduce new untested functions, so the new test suggested here is more sensitive - and also more flexible.
It can be argued that ideally function coverage should be 100%, but we are not quite there yet, and looking at some of the currently not covered function it's not clear if writing tests for them has an attractive benefit/effort ratio (compared to other issues on our list). If we want to get to 100% function coverage, the mechanism above could be an intermediate step on the way - start with a non-empty allowlist then progressively work to make it empty.

We currently don't run test coverage before merging a pull request. We should do that before adding a likely cause of failure.

Note: After generating coverage data, the list of uncovered functions can be extracted with:
grep -B1 'coverFnLo">0<' Coverage/library/*.c.func.html | sed -n 's/[^>]*>[^>]*>\([^<]*\)<.*/\1/p'

(Sharing this to support quick explorations, but we'll want something more robust in the script - the above one-liner has the obvious drawback of silently returning the empty if the format of the output changes in unexpected ways.)
For reference in Mbed TLS 3.0 there are 24 untested functions:
mbedtls_internal_aes_decrypt
mbedtls_internal_aes_encrypt
mpi_uint_bigendian_to_host_c
aria_crypt_cfb128_wrap
aria_crypt_ctr_wrap
ccm_aria_setkey_wrap
mbedtls_ecdh_can_do
mbedtls_net_close
mbedtls_platform_set_calloc_free
mbedtls_platform_set_exit
mbedtls_platform_set_fprintf
mbedtls_platform_set_printf
mbedtls_platform_set_snprintf
mbedtls_platform_set_time
mbedtls_platform_set_vsnprintf
psa_crypto_recover_transaction
psa_driver_wrapper_get_builtin_key
psa_driver_wrapper_get_key_buffer_size
psa_get_se_driver_context
mbedtls_ssl_cookie_set_timeout
mbedtls_ssl_send_fatal_handshake_failure
ssl_buffer_make_space
mbedtls_ssl_conf_preference_order
ssl_conf_remove_psk


Green not displaying green

Not a question

[X] This is not a question. If you have a question, use discussions.

I investigated.

[X] I have read README.md, help documentation, and searched past issues but no solution.

Description
When I use the word green in my css file, it displays a tone of orange
Environments
Windows 11
NVIM v0.9.5
Build type: RelWithDebInfo
LuaJIT 2.1.1703942320
Minimal reproducible full config
return{
{
'uga-rosa/ccc.nvim',
event = 'VeryLazy',
opts = {
highlighter = { auto_enable = true, lsp = true },
},
},
}
Steps to reproduce
Go to a css file and type green as color property
Expected behavior
background of the word becomes green
Actual behavior
the background becomes orange
Additional context
Here is a photo of the problem

This is not a full config.

If there are deficiencies here, the issue will not be respond. Please understand that this is the most important section.
You must provide a working config based on this. Not part of config.
Users of packer.nvim should check to see if there any plugins left in ~/.local/share/nvim/site/pack/packer.

Copy the base minimal config to the ~/ccc-repro.vim.
Edit ~/ccc-repro.vim for reproducing the issue.
Open nvim -u ~/ccc-repro.vim.
Check steps to reproduce.

vim.o.termiguicolors = true

local lazypath = vim.fn.stdpath 'data' .. '/lazy/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system {
        'git',
        'clone',
        '--filter=blob:none',
        'https://github.com/folke/lazy.nvim.git',
        '--branch=stable', -- latest stable release
      lazypath,
    }
end
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
   {
    'uga-rosa/ccc.nvim',
        opts = {
            highlighter = { auto_enable = true},
        },
   },

       {
        'catppuccin/nvim',
        name = 'catppuccin',
        priority = 1000,
	config = function()
		vim.cmd.colorscheme 'catppuccin'
	end,
   },

   {
        'neovim/nvim-lspconfig',
        dependencies = {
            'williamboman/mason.nvim',
            'williamboman/mason-lspconfig.nvim',
	}
   },

},{})

require('mason').setup()
require('mason-lspconfig').setup()

local mason_lspconfig = require('mason-lspconfig')

local servers = {
    cssls = {
        filetypes = {'css'}
    }
}

mason_lspconfig.setup {
    ensure_installed = {'cssls'}
}

-- Set up language servers
for server_name, config in pairs(servers) do
    mason_lspconfig.setup_handlers {
        function(name)
            if name == server_name then
                require('lspconfig')[name].setup {
                    filetypes = config.filetypes
                }
            end
        end
    }
end

This is the minimal config, and I still have the same problem in windows and in the WSL

Using the previous version 1.7.0 works as expected btw

You'll need the css files too.
Also, is this color scheme really necessary for reproduction?

I am going to be honest I don't know why you are so fixiated with this reproduction procedure, I am just trying to point out something that is not working. The previous comment doesn't have anything more than your plugin, a colorscheme,  and a Lsp setup, but well since you want it without the colorscheme.
vim.o.termguicolors = true

local lazypath = vim.fn.stdpath 'data' .. '/lazy/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system {
        'git',
        'clone',
        '--filter=blob:none',
        'https://github.com/folke/lazy.nvim.git',
        '--branch=stable', -- latest stable release
      lazypath,
    }
end
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
   {
    'uga-rosa/ccc.nvim',
        opts = {
            highlighter = { auto_enable = true},
        },
   },

   {
        'neovim/nvim-lspconfig',
        dependencies = {
            'williamboman/mason.nvim',
            'williamboman/mason-lspconfig.nvim',
	}
   },

},{})

require('mason').setup()
require('mason-lspconfig').setup()

local mason_lspconfig = require('mason-lspconfig')

local servers = {
    cssls = {
        filetypes = {'css'}
    }
}

mason_lspconfig.setup {
    ensure_installed = {'cssls'}
}

-- Set up language servers
for server_name, config in pairs(servers) do
    mason_lspconfig.setup_handlers {
        function(name)
            if name == server_name then
                require('lspconfig')[name].setup {
                    filetypes = config.filetypes
                }
            end
        end
    }
end

The css file is just any css file, I'm going to make one on the same directory as the config.

And then same result as the previous ones, except that fooling around I found out blue also has a problem.

This is because this issue was not reproduced at hand. I can't fix a bug I can't confirm.
I'm still not sure what the cause is, but I found that I can reproduce this bug after formatting, even though it is not highlighted right after startup. Now I can finally investigate.


Create devcontainer.json

Summary
A clear and concise description of what the problem or opportunity is. Link to an issue if relevant.
Changes
Describe the changes this pull request introduces.
Task list

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.

@Srimlika it looks like this pull request was just opened as a test since the pull request template is not filled out. I'm going to close this out.


Log level not being fully applied

Is this a request for help?:
NO
Is this a BUG REPORT or a FEATURE REQUEST? (choose one):
BUG REPORT

Version of Anchore Engine and Anchore CLI if applicable:
anchore-cli version 0.2.4
anchore-engine version 0.3.2
What happened:
Setting the log level to ERROR on anchore-engine config.yaml don't set the log level for Twisted, then you still get all the simplequeue request logs on STDOUT.
What did you expect to happen:
Only get ERROR logs

Any relevant log output from /var/log/anchore:
[service:simplequeue] 2019-03-11 16:20:25+0000 [-] "<IP_ADDRESS>" - - [11/Mar/2019:16:20:25 +0000] "GET /v1/leases/analyzer_queue/release?client_id=anchore-engine-0%3A13%3A140150475228928%3A&epoch=13753874 HTTP/1.1" 200 - "-" "python-requests/2.20.0"
[service:simplequeue] 2019-03-11 16:20:27+0000 [-] "<IP_ADDRESS>" - - [11/Mar/2019:16:20:26 +0000] "POST /v1/queues/watcher_tasks/is_inqueue HTTP/1.1" 200 3 "-" "python-requests/2.20.0"
What docker images are you using:
docker.io/anchore/anchore-engine:v0.3.2
How to reproduce the issue:
Deploy anchore engine 0.3.2 and set log_level: ERROR on config.yaml file, you will see logs like previous ones
Anything else we need to know:

We've added a new configuration parameter 'enable_access_logging' which, when set to 'False' in anchore-engine's config.yaml (either globally or as an override, per service section) will prevent the twisted access logs from appearing in the anchore engine log output.
background: these particular access logs in twisted take a different path (which uses a very low level simple 'write' that is not processed through normal logging paths) than regular log level controlled log entries, and thus we opted to control them separately from the regular log level controlled information.  In addition, we felt that one may wish to view the access logs independent from the regular anchore log level controlled entries, which this solution permits.
This should address the core issue (happy to discuss any feedback on the solution, here!).  The option will be included in the next release of anchore engine (0.3.4) and versions moving forward.

Good news @nurmi , thanks for the update!

How to set this false using helm chart ?


SwiftModule and -Swift.h ObjC compatibility header not copied to framework

When building a framework that contains swift code, the generated framework is missing critical files.
When adding the swift code, a Foo-Swift.h file is generated so that Objective-C can call Swift functions. This is usually included in the framework.
Also, the Foo.swiftmodule file is usually included in the framework so you can use the Swift functions directly.
Location of these generated files, which are correctly generated by CMake:
_builds/ios-toolchain/bin/Release/Foo_0_0_0_0.swiftmodule/arm.swiftdoc
_builds/ios-toolchain/bin/Release/Foo_0_0_0_0.swiftmodule/arm.swiftmodule
_builds/ios-toolchain/bin/Release/Foo_0_0_0_0.swiftmodule/arm64.swiftdoc
_builds/ios-toolchain/bin/Release/Foo_0_0_0_0.swiftmodule/arm64.swiftmodule
This folder is meant to go in to the Modules/ directory of the generated Framework.
_builds/ios-toolchain/Foo/Bar.build/Release-iphoneos/Bar.build/DerivedSources/Foo_0_0_0_0-Swift.h
This file is meant to go in to the Headers/ directory of the generated Framework.
I am not sure how to do this myself.

As I said before, I haven't worked with Swift so can't give any advice here.

@ruslo That's fine (regarding Swift usage). However, could you give me some pointers in how to find the name of these folders?
I know how to find _builds/ios-toolchain/bin/Release but not sure how to find the name Foo_0_0_0_0 (That is, the soname with version).
Also unsure of how to work out the directory _builds/ios-toolchain/Foo/Bar.build/Release-iphoneos/Bar.build/DerivedSources
If I can get some variable name for these, I could fix the create_framework.py script.

I really don't know what all this is about :) The right solution would be to implement all this stuff in CMake itself and see what should go where.

It already is in CMake and those are the generated files.
Only Polly does iOS frameworks though so I just wanted to know how to calculate those directories so I can copy the relevant files to the framework.

The right solution would be to implement all this stuff in CMake itself and see what should go where

Actually I think iOS framework creation is fixed in CMake. I see iOS mentioned here:

https://cmake.org/cmake/help/latest/prop_tgt/FRAMEWORK.html

I've tried simple example and it looks good. Need to try something with complex structure.
@xsacha you can post your question to CMake bugtracker in this case.
@headupinclouds +cc

Need to try something with complex structure.

Works fine.
Don't use --framework - use CMake FRAMEWORK instead. Closing.

This is great news, thanks!


Is there a NuGet package for this available?

What I found is https://www.nuget.org/packages/Xake/1.0.3-alpha5 Is there more or is everything part of this package?
I would like to add this to the fake documentation as an alternative to the targets-syntax. Is this something you would be interested in?
Have you ever tried to use this in combination with the fake 5 runner?

Oh I didn't realize you are already on it (briefly mentioned in https://github.com/fsharp/FAKE/issues/1888).
Feel free to send PRs to fake docs if you are ready :)

@matthid, I would be glad this project to be part of FAKE 5 and currently working on migration everything to netcore. What do you think if we give it a different name, such as Fake.Recipes or Fake.Scripts?
Have you look the docs? There're a bunch of cool features such as incremental builds, estimate time prediction and progress indicator.
It currently works with FAKE5 and I just pushed the netcore-bootstrap example.

Ok to give you a rough roadmap: After the fake release the next logical step would be to extract some modules into their own repository. Therefore it doesn't make a lot of sense to make something part of the fake repository now until we are at some later stage.
From a users perspective it doesn't make a lot of difference where the code lives as the integration is easy. Like I said I welcome update to the docs (which should make it seamless and not noticeable to users where the actual code lives.
If you want to rename your project because if this that would be up to you but not required from my point of view. (though it would match the fake naming scheme)

@matthid, thanks, good!

To reword/clarify a bit (edited some errors above): It doesn't make a lot of sense to add stuff which already is perfectly split into it's own repository. But if the integration Fake-Xake happens to break in the future I'm perfectly open to adding it to the fake repository.
I guess for now we would have something like a new "folder" in the modules menu:

Modules

Build DSL

Fake.Core.Target
Xake

Closing this for now as I feel like we have similar ideas going forward. Looking forward to this :)

@matthid I completed migration to netcore/FAKE 5, extracted .NET specific tasks to a separate assembly, updated docs and so on.
Could you please add a module reference to FAKE 5 docs and RT https://twitter.com/olegzeee/status/996801367514677248?

Maybe Like this? Feel free to send updates - I have no idea how to integrate as we currently kind of used the "module-category" (basically the namespace). I'm open for ideas :)

@matthid that is fine now, thank you very much!


e2e-484 get appointment office location

Also aded spring profile for using a local file H2 database, this helps massively with application start-up & for using intellij database tools to connect.


Default Tailwind colors persist and hinder accessibility of custom colors in Histoire Design System

Describe the bug
The Histoire package has an issue with the Tailwind Design System feature where the default Tailwind colors continue to appear in the border and text color tabs, even after adding a custom colors object directly to the theme object in tailwind.config. This is not the expected behavior, as the custom colors object should override the default Tailwind colors, preventing them from being used and displayed.
Moreover, this issue is particularly annoying because it forces users to scroll down through the default colors to access their custom-defined colors.
Reproduction

Create a new project with the Histoire package.
Configure tailwind.config.js by adding a custom colors object to the theme object.
Run the project and navigate to the Histoire Tailwind Design System interface.
Observe that the default Tailwind colors are still displayed in the border and text color tabs, despite the custom colors object in the configuration.

System Info
System:
    OS: macOS 13.2.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 73.78 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.1 - /opt/homebrew/opt/node@16/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.19.3 - /opt/homebrew/opt/node@16/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 111.0.5563.146
    Chrome Canary: 114.0.5685.0
    Firefox: 101.0
    Safari: 16.3
  npmPackages:
    @histoire/plugin-vue: ^0.15.8 => 0.15.8
    @vitejs/plugin-vue: ^4.1.0 => 4.1.0
    histoire: ^0.15.9 => 0.15.9
    vite: ^4.2.0 => 4.2.1

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

Getting the same behavior. But for me I think it basically shows all of Tailwind's default colors on every section related to colors (background, text, border).
I'm using the following tailwind.config.ts in a SvelteKit project:
import type { Config } from 'tailwindcss'
import colors from 'tailwindcss/colors'

export default {
  content: ['./src/**/*.{html,js,svelte,ts}'],
  darkMode: 'class',
  theme: {
    colors: {
      transparent: 'transparent',
      current: 'currentColor',
      cyan: colors.cyan,
      yellow: colors.yellow,
      red: colors.red,
      slate: colors.slate,
      black: colors.black,
      white: colors.white,
    },
    extend: {},
  },
} satisfies Config

Hey guys 🙂
Thanks for this amazing tool.
I have the same problem as @samuveth, default Histoire Tailwind config persist despit setting Tailwind with my own config.
Any update on this ?

It's working with latest version for me when adding the colors to the theme directly and not to extend.


Fields of nested components are not updated immediately

Description
When we update fields of nested components, we don't see the updated values in the preview.
More info in the Loom:
https://www.loom.com/share/ea1f956c407f4d479c6f6a70d371edb2
Steps to reproduce

Have a nested component structure
Update a field of a nested component (e.g. on the 2nd or 3rd level of nesting)

Expected result
I would like to immediately see the updates in the preview.
Actual result
I need to save and reload the page to see the updates.
Environment
Tinacms Package Versions

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Tools

Tool
Version

browser
brave

os
ubuntu 20.04

node
16.14.2

npm
8.5.0

I was able to reproduce it by creating a reference to a template, and passing it into a few different fields.
https://www.loom.com/share/1af2d8fcbb8743bda02089248582a945
Here was the workaround for me:
https://github.com/jamespohalloran/nested-blocks-bug/commit/d327dd7923aa7fbf52803aa15c1a8eed0aacffd5
(I created a function to create new templates as needed, instead of passing the template references into the templates arry). Want to try that and see if it clears up your issue @Perni1984 ?

we'll give it a try and report back @jamespohalloran


Adapt to the recent changes in semanticidx format

Accepted benchmarking d14e916. This may take a while.

Finished benchmarking d14e916.

Benchmark
Before
After

RscParse
19.416 ms
18.917 ms

RscLink
47.766 ms
52.395 ms

RscOutline
43.625 ms
41.935 ms

RscSemanticdb
23.309 ms
23.771 ms

RscMjar
241.417 ms
263.559 ms

ScalacCompile
~10x
~9x

Full results are available at https://github.com/twitter/rsc/commit/c4298cfefda51ee65b08b7b8f53f71692e8dfaf9.

Travis doesn't feel well, so I'll be merging as is. I can confirm that I successfully ran sbt ci on my machine.


Browserify dependencies

This is pretty much yak shaving: I wanted to port this plugin to Safari, but Hogan templates can't be compiled live. Safari applies GitHub CSP is also to extensions (at least for inline-eval, but algolia search requests seem to be allowed). Additionally, Safari appears to load extension JS asynchronously, which means that content.js might be running before other scripts are fully executed.
To solve these issues without breaking existing plugins, I migrated the templates and dependencies to be included via Browserify. The compiled content.js seems to run in Safari as well as other browsers.
I also updated the dependencies as older versions of libraries weren't compatible with Browserify. This could've broken something. I wasn't able to test the extension as signed in user as private repository crawling seems to take quite a while for my account.

Wow, that's great! I started to look at the Safari port a few months ago but never took the time to nail it.
Using browserify everywhere is probably the right way to go. I'll check how it looks like in Chrome & Firefox later this week. I could also try to cleanup our code, kind of messy right now.
My only concern is maybe with the Firefox's moderation, they don't like minified/hidden/concatenated dependencies so I hope using browserify is OK for them.

Browserify might not be needed on Firefox as it seems to support npm modules since 38.0 with jpm. Not sure if it actually would work, though.
On the other hand, Firefox AMO review policies state that

Add-ons may contain binary, obfuscated and minified source code, but Mozilla must be allowed to review a copy of the human-readable source code of each version of an add-on submitted for review.

I'd interpret this as having a repo that can be used to produce the exact copy of the addon bundle would be enough. Shrink-wrapping dependencies could help in that, and perhaps it wouldn't be bad to produce more reliable builds in general.

Oh, I didn't know about jpm, that's good to know.

I'd interpret this as having a repo that can be used to produce the exact copy of the addon bundle would be enough.

That's also what I initially thought, but I ended up using all non-minified source to convince them :)

By the way, I've pushed the Safari branch to https://github.com/lautis/github-awesome-autocomplete/tree/safari. It works at least without OAuth, but I seem to get a timeout when accessing https://github.algolia.com/signin.

I'm gonna close this PR but I've taken some of your ideas in https://github.com/algolia/github-awesome-autocomplete/commit/0a717b05fe2b6be3ad9d418910ced32a60e65939. We definitely need to upgrade the underlying algoliasearch deps, but it's actually a patched version (that removes the JSONP capabilities for security reason). I'll also replace typeahead by autocomplete.js anytime soon.


Clarify spec after latest changes

Originally wanted to be done as part of https://github.com/api3dao/airseeker-v2/pull/226

More things accumulated, over time:

[ ] Update feed checks
[ ] Gas price fetching changes
[ ] Gas price scaling/sanitization

The spec is updated. Feel free to re-read it and comment/ask.


Team member Delete Api

Notion card
https://www.notion.so/saeloun/API-development-for-delete-team-member-ba3b8f43bff5483a8c3bb456bc28a4cc
Summary

Add internal api for Team page with destroy Method
Add specs for Api team_controller#destroy method

Preview

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

I have a few concerns with this PR and hence stopped reviewing further. We are not checking if the user being deleted is part of other companies or not. Discarding the user directly would discard the company_users associated with other companies making the user unable to login into other workspaces This scenario is not tested in the specs as well.
What is the exact requirement of this API? We can probably split this API into two.

User destroy API which will completely remove the access to Miru (For all the workspaces)
Company User destroy API which will destroy one particular company_user (For a particular workspace)

Also when we say team member it is not immediately clear if we are talking about the company_user or the larger user record cc @supriya3105 @harshaanNihal @akhilgkrishnan

Yes I agree with you.

I have a few concerns with this PR and hence stopped reviewing further. We are not checking if the user being deleted is part of other companies or not. Discarding the user directly would discard the company_users associated with other companies making the user unable to login into other workspaces This scenario is not tested in the specs as well.
What is the exact requirement of this API? We can probably split this API into two.
User destroy API which will completely remove the access to Miru (For all the workspaces)
Company User destroy API which will destroy one particular company_user (For a particular workspace)
Also when we say team member it is not immediately clear if we are talking about the company_user or the larger user record cc @supriya3105 @harshaanNihal @akhilgkrishnan

Agree we should discard the conmpany_user instead of user in this scenario.
Initially I was trying to port prewritten team_controller to internal API which was discarding user directly hence I overlooked this scenario.
Moving the PR to Draft for now

I have kept the controller name singular team instead of teams.
The controller will mainly manage the company_users and it's not tied to a specific model  i.e. Team.
Since each company will technically have only one team (company users belong to that company). As Team controller is not associated with any particular model / resource, but rather handle a set of functionality.  In this case, the pluralization doesn't make any sense to me.
Please let me know if you think otherwise and I will update the controller name to a plural form.
@rohitjoshixyz @akhilgkrishnan

Since each company will technically have only one team (company users belong to that company). As Team controller is not associated with any particular model / resource, but rather handle a set of functionality. In this case, the pluralization doesn't make any sense to me.

That makes sense, considering this and our previous discussion since this controller is only going to handle the company_user model's destroy action let's name it as company_users_controller. What do you think?

There is already a company_users_controller present. [for now it is been used for project Page ]
The Team_controller will be handling functionality specific to team page. [It is already implemented for ERB files]. We are porting it to APIs so that the team page can be ported into react components.
beside destroy method controller will have index update and probably edit.
Maybe once after the Team page is ported we can merge both team and company_user controller into single controller. if they share the functionality.


Complete baseline JIT WebAssembly compiler for amd64 target.

This commit completes the baseline (singlepass) JIT WebAssembly compiler
for amd64 target with the implementation for br_table instruction.
The implementation passes 100% of WebAssembly specification test,
just like our interpreter. This is the world's first JIT compilation engine purely
written in Go, and the implementation is stable under multple goroutines, and
never broken by Go runtime. The JIT engine is tested both for Linux and Darwin.
Even though this passes the spectests and is implemented as "JIT", our calling convention
proxies all function calls though non-native Go world, therefore there's some performance
overhead. This would be fixed in a following commit which allows us to make function calls
in the fully native way. See https://github.com/tetratelabs/wazero/pull/60 and RATIONALE.md for design details.
resolves #65 #42

I will mark this ready after adding more docs, but anyway now JIT compiler passes 100% of spectest!

@mathetake this is absolutely excellent work Mathew, kudos.

I can't believe I've done this in less than 2 months!


Pouch bridge network does not work

Ⅰ. Issue Description
Pouch bridge network does not work
Ⅱ. Describe what happened
Can not reach internet in container. Can not reach container using port banding.
Ⅲ. Describe what you expected to happen
none
Ⅳ. How to reproduce it (as minimally and precisely as possible)
none
Ⅴ. Anything else we need to know?
I have tried uninstall docker and delete docker net bridge. Did not work.
Ⅵ. Environment:

pouch version (use pouch version):1.0.0
OS (e.g. from /etc/os-release):centos 7
Kernel (e.g. uname -a):3.10.0
Install tools:
Others:

Could you describe more about what happened in the container:
you can add

how to create a container
how to get access to internet

@Shawnpku

@allencloud
Use command sudo pouch run -it -p 8080:80 nginx /bin/bash to run container then command curl localhost:8080 show nothing. Executing apt update in container can not connect internet either.

I use the same command in docker and it works fine. What command should I use? Also wondering what command should I use to let container be able to reach internet. Thank you~ @allencloud

@Shawnpku how do you install pouchd? by yum or source code? If it's done by yum, it has the issue. you can try it from master branch.

@fuweid I install pouch by yum.

@Shawnpku we have fixed this issue by https://github.com/alibaba/pouch/pull/2025, could you mind to install by the source code? 😄

Nginx works after I delete /bin/bash part. The command is really different with which I used in docker. I have not been used to it yet.

@fuweid Happy to see it has been fixed. Please add the new version to yum resource soon. Thank you~

@Shawnpku thanks! please feel free to close the issue 😄


hie-8.4.4 no longer builds

Cabal can't build because dependencies are now out of sync (something must've updated in the stack-8.4.4.yaml resolver, I'm going to guess):
PS > stack runghc --stack-yaml=shake.yaml --package shake --package directory --package extra install.hs hie-8.4.4
# git (for submodules)
Synchronizing submodule url for 'submodules/HaRe'
Synchronizing submodule url for 'submodules/HaRe/submodules/cabal-helper'
Synchronizing submodule url for 'submodules/HaRe/submodules/ghc-mod'
Synchronizing submodule url for 'submodules/brittany'
Synchronizing submodule url for 'submodules/cabal-helper'
Synchronizing submodule url for 'submodules/floskell'
Synchronizing submodule url for 'submodules/ghc-mod'
# git (for submodules)
# stack (for check-stack)
# cabal (for cabal)
# cabal (for cabal)
Warning: The update command is a part of the legacy v1 style of cabal usage.

Please switch to using either the new project style and the new-update command
or the legacy v1-update alias as new-style projects will become the default in
the next version of cabal-install. Please file a bug if you cannot replicate a
working v1- use case with the new-style commands.

For more information, see: https://wiki.haskell.org/Cabal/NewBuild

Downloading the latest package list from hackage.haskell.org
To revert to previous state run:
    cabal update --index-state='2019-04-29T23:28:49Z'
# stack (for hie-8.4.4)

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for Cabal-<IP_ADDRESS>:
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> Cabal-<IP_ADDRESS>

In the dependencies for apply-refact-<IP_ADDRESS>:
    ghc-8.6.2 from stack configuration does not match >=8.4.0 && <8.6  (latest matching version
              is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> apply-refact-<IP_ADDRESS>

In the dependencies for butcher-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.9 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> butcher-<IP_ADDRESS>

In the dependencies for cabal-install-<IP_ADDRESS>(+lib -native-dns):
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> cabal-install-<IP_ADDRESS>

In the dependencies for contravariant-1.4.1:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> contravariant-1.4.1

In the dependencies for free-5.0.2:
    containers-<IP_ADDRESS> from stack configuration does not match <0.6  (latest matching version
                       is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> free-5.0.2

In the dependencies for haddock-api-2.20.0:
    base-<IP_ADDRESS> from stack configuration does not match ^>=4.11.0  (latest matching version
                  is <IP_ADDRESS>)
    ghc-8.6.2 from stack configuration does not match ^>=8.4.2  (latest matching version is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-api-2.20.0

In the dependencies for haddock-library-1.6.0:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-library-1.6.0

In the dependencies for lens-4.16.1:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4.0 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.4 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> lens-4.16.1

In the dependencies for polyparse-1.12:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> polyparse-1.12

In the dependencies for primitive-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> primitive-<IP_ADDRESS>

In the dependencies for semigroupoids-5.2.2:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.3 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> semigroupoids-5.2.2

In the dependencies for stm-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.3 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> stm-<IP_ADDRESS>

In the dependencies for tagged-0.8.5:
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.8 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> tagged-0.8.5

Some different approaches to resolving this:

  * Set 'allow-newer: true' in C:\sr\config.yaml to ignore all version constraints and build anyway.

  * Consider trying 'stack solver', which uses the cabal-install solver to attempt to find some
    working build configuration. This can be convenient when dealing with many complicated
    constraint errors, but results may be unpredictable.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need
    to use a different GHC version with the matching base.

Plan construction failed.

******************************************************************
Building failed, Try running `stack clean` and restart the build
If this does not work, open an issue at
        https://github.com/haskell/haskell-ide-engine
******************************************************************

Error when running Shake build system:
  at src/Development/Shake/Internal/Args.hs:81:69-79:
* Depends on: hie-8.4.4
* Raised the exception:
user error (Development.Shake.command_, system command failed
Command: stack --stack-yaml=stack-8.4.4.yaml build
Exit code: 1
Stderr:
Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for Cabal-<IP_ADDRESS>:
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> Cabal-<IP_ADDRESS>

In the dependencies for apply-refact-<IP_ADDRESS>:
    ghc-8.6.2 from stack configuration does not match >=8.4.0 && <8.6  (latest matching version
              is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> apply-refact-<IP_ADDRESS>

In the dependencies for butcher-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.9 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> butcher-<IP_ADDRESS>

In the dependencies for cabal-install-<IP_ADDRESS>(+lib -native-dns):
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> cabal-install-<IP_ADDRESS>

In the dependencies for contravariant-1.4.1:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> contravariant-1.4.1

In the dependencies for free-5.0.2:
    containers-<IP_ADDRESS> from stack configuration does not match <0.6  (latest matching version
                       is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> free-5.0.2

In the dependencies for haddock-api-2.20.0:
    base-<IP_ADDRESS> from stack configuration does not match ^>=4.11.0  (latest matching version
                  is <IP_ADDRESS>)
    ghc-8.6.2 from stack configuration does not match ^>=8.4.2  (latest matching version is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-api-2.20.0

In the dependencies for haddock-library-1.6.0:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-library-1.6.0

In the dependencies for lens-4.16.1:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4.0 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.4 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> lens-4.16.1

In the dependencies for polyparse-1.12:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> polyparse-1.12

In the dependencies for primitive-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> primitive-<IP_ADDRESS>

In the dependencies for semigroupoids-5.2.2:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.3 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> semigroupoids-5.2.2

In the dependencies for stm-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.3 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> stm-<IP_ADDRESS>

In the dependencies for tagged-0.8.5:
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.8 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> tagged-0.8.5

Some different approaches to resolving this:

  * Set 'allow-newer: true' in C:\sr\config.yaml to ignore all version constraints and build anyway.

  * Consider trying 'stack solver', which uses the cabal-install solver to attempt to find some
    working build configuration. This can be convenient when dealing with many complicated
    constraint errors, but results may be unpredictable.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need
    to use a different GHC version with the matching base.

Plan construction failed.
)

Can you use the recommended command line, which is stack ./install.hs hie-8.4.4?

@nponeccop: Doesn't make a difference, same output. (BTW: stack runghc ... is the same as stack ./install.hs ..., if you peek into install.hs.)
PS > stack ./install.hs hie-8.4.4
# git (for submodules)
Synchronizing submodule url for 'submodules/HaRe'
Synchronizing submodule url for 'submodules/HaRe/submodules/cabal-helper'
Synchronizing submodule url for 'submodules/HaRe/submodules/ghc-mod'
Synchronizing submodule url for 'submodules/brittany'
Synchronizing submodule url for 'submodules/cabal-helper'
Synchronizing submodule url for 'submodules/floskell'
Synchronizing submodule url for 'submodules/ghc-mod'
# git (for submodules)
# stack (for check-stack)
# cabal (for cabal)
# cabal (for cabal)
Warning: The update command is a part of the legacy v1 style of cabal usage.

Please switch to using either the new project style and the new-update command
or the legacy v1-update alias as new-style projects will become the default in
the next version of cabal-install. Please file a bug if you cannot replicate a
working v1- use case with the new-style commands.

For more information, see: https://wiki.haskell.org/Cabal/NewBuild

Downloading the latest package list from hackage.haskell.org
To revert to previous state run:
    cabal update --index-state='2019-04-30T00:27:42Z'
# stack (for hie-8.4.4)

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for Cabal-<IP_ADDRESS>:
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> Cabal-<IP_ADDRESS>

In the dependencies for apply-refact-<IP_ADDRESS>:
    ghc-8.6.2 from stack configuration does not match >=8.4.0 && <8.6  (latest matching version
              is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> apply-refact-<IP_ADDRESS>

In the dependencies for butcher-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.9 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> butcher-<IP_ADDRESS>

In the dependencies for cabal-install-<IP_ADDRESS>(+lib -native-dns):
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> cabal-install-<IP_ADDRESS>

In the dependencies for contravariant-1.4.1:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> contravariant-1.4.1

In the dependencies for free-5.0.2:
    containers-<IP_ADDRESS> from stack configuration does not match <0.6  (latest matching version
                       is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> free-5.0.2

In the dependencies for haddock-api-2.20.0:
    base-<IP_ADDRESS> from stack configuration does not match ^>=4.11.0  (latest matching version
                  is <IP_ADDRESS>)
    ghc-8.6.2 from stack configuration does not match ^>=8.4.2  (latest matching version is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-api-2.20.0

In the dependencies for haddock-library-1.6.0:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-library-1.6.0

In the dependencies for lens-4.16.1:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4.0 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.4 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> lens-4.16.1

In the dependencies for polyparse-1.12:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> polyparse-1.12

In the dependencies for primitive-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> primitive-<IP_ADDRESS>

In the dependencies for semigroupoids-5.2.2:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.3 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> semigroupoids-5.2.2

In the dependencies for stm-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.3 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> stm-<IP_ADDRESS>

In the dependencies for tagged-0.8.5:
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.8 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> tagged-0.8.5

Some different approaches to resolving this:

  * Set 'allow-newer: true' in C:\sr\config.yaml to ignore all version constraints and build anyway.

  * Consider trying 'stack solver', which uses the cabal-install solver to attempt to find some
    working build configuration. This can be convenient when dealing with many complicated
    constraint errors, but results may be unpredictable.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need
    to use a different GHC version with the matching base.

Plan construction failed.

******************************************************************
Building failed, Try running `stack clean` and restart the build
If this does not work, open an issue at
        https://github.com/haskell/haskell-ide-engine
******************************************************************

Error when running Shake build system:
  at src/Development/Shake/Internal/Args.hs:81:69-79:
* Depends on: hie-8.4.4
* Raised the exception:
user error (Development.Shake.command_, system command failed
Command: stack --stack-yaml=stack-8.4.4.yaml build
Exit code: 1
Stderr:
Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for Cabal-<IP_ADDRESS>:
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> Cabal-<IP_ADDRESS>

In the dependencies for apply-refact-<IP_ADDRESS>:
    ghc-8.6.2 from stack configuration does not match >=8.4.0 && <8.6  (latest matching version
              is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> apply-refact-<IP_ADDRESS>

In the dependencies for butcher-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.9 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> butcher-<IP_ADDRESS>

In the dependencies for cabal-install-<IP_ADDRESS>(+lib -native-dns):
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> cabal-install-<IP_ADDRESS>

In the dependencies for contravariant-1.4.1:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> contravariant-1.4.1

In the dependencies for free-5.0.2:
    containers-<IP_ADDRESS> from stack configuration does not match <0.6  (latest matching version
                       is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> free-5.0.2

In the dependencies for haddock-api-2.20.0:
    base-<IP_ADDRESS> from stack configuration does not match ^>=4.11.0  (latest matching version
                  is <IP_ADDRESS>)
    ghc-8.6.2 from stack configuration does not match ^>=8.4.2  (latest matching version is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-api-2.20.0

In the dependencies for haddock-library-1.6.0:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-library-1.6.0

In the dependencies for lens-4.16.1:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.4.0 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.4 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> lens-4.16.1

In the dependencies for polyparse-1.12:
    base-<IP_ADDRESS> from stack configuration does not match <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> polyparse-1.12

In the dependencies for primitive-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> primitive-<IP_ADDRESS>

In the dependencies for semigroupoids-5.2.2:
    containers-<IP_ADDRESS> from stack configuration does not match >=0.3 && <0.6  (latest matching
                       version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> semigroupoids-5.2.2

In the dependencies for stm-<IP_ADDRESS>:
    base-<IP_ADDRESS> from stack configuration does not match >=4.3 && <4.12  (latest matching version
                  is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> stm-<IP_ADDRESS>

In the dependencies for tagged-0.8.5:
    template-haskell-<IP_ADDRESS> from stack configuration does not match >=2.8 && <2.14  (latest
                              matching version is <IP_ADDRESS>)
needed due to hie-plugin-api-<IP_ADDRESS> -> tagged-0.8.5

Some different approaches to resolving this:

  * Set 'allow-newer: true' in C:\sr\config.yaml to ignore all version constraints and build anyway.

  * Consider trying 'stack solver', which uses the cabal-install solver to attempt to find some
    working build configuration. This can be convenient when dealing with many complicated
    constraint errors, but results may be unpredictable.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need
    to use a different GHC version with the matching base.

Plan construction failed.
)

Perhaps this is related to us recently removing Cabal from the install requirements in https://github.com/haskell/haskell-ide-engine/pull/1184
cc @power-fungus

this is related to us recently removing

I wonder how CI works then. Should we rebuild the caches?

I have the same issue, I'm on a Windows computer

@FrancoAra, Can you post your stack version and windows version?
Also, which command did you invoke to produce this error?
Is the project up-to-date, e.g. git pull does not pull in updates?

I've reproduced it with both stack-1.9.3 and stack-2.1.3 and executing stack build --stack-yaml=stack-8.4.4.yaml and stack install.hs hie-8.4.4.
The error with stack-2.1.3 is:
....
In the dependencies for haddock-api-2.20.0:
    base-<IP_ADDRESS> from stack configuration does not match ^>=4.11.0  (latest matching
                  version is <IP_ADDRESS>)
    ghc-8.6.5 from stack configuration does not match ^>=8.4.2  (latest matching version
              is 8.4.4)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-api-2.20.0

In the dependencies for haddock-library-1.6.0:
    base-<IP_ADDRESS> from stack configuration does not match >=4.5 && <4.12  (latest matching
                  version is <IP_ADDRESS>)
    containers-<IP_ADDRESS> from stack configuration does not match >=<IP_ADDRESS> && <0.6  (latest
                       matching version is <IP_ADDRESS>)
needed due to haskell-ide-engine-<IP_ADDRESS> -> haddock-library-1.6.0

Some different approaches to resolving this:

  * Set 'allow-newer: true'
    in D:\sr\config.yaml to ignore all version constraints and build anyway.

  * Build requires unattainable version of base. Since base is a part of GHC, you most
    likely need to use a different GHC version with the matching base.

Plan construction failed.

Strangely i have not ghc-8.4.4 installed but stack doesn't download it but uses the ghc system wide:
PS D:\dev\ws\haskell\haskell-ide-engine> stack path --stack-yaml=stack-8.4.4.yaml
...
compiler-exe: D:\bin\stack\x86_64-windows\ghc-8.6.5\bin\ghc.EXE
...

A stack setup doesn't install ghc-8.4.4 but a stack setup --reinstall does it.
So it seems the error is triggered when you have a newer ghc (> 8.6) in the global path.
Probably this is the cause that makes the build work in the ci env.
I have to investigate more on this but maybe it will need open a ticket upstream.

After installing ghc-8.4.4 i have not able to reproduce again the error, even "uninstalling" it again, so there must be some other factor involved. 😟

Maybe another reporter still hits the error so we could reproduce it? @FrancoAra @bscottm?


Add terraform.ProviderScheduler

Description of your changes

Related to: https://github.com/upbound/provider-aws/issues/325
This PR adds terraform.ProviderScheduler interface and three implementations of it (terraform.NoOpProviderScheduler, a noop implementation, terraform.SharedProviderScheduler that shares Terraform provider processes among multiple reconciliation loops with a configured TTL, and a terraform.WorkspaceProviderScheduler that shares a Terraform provider process between the CLI invocations done in the context of a single reconciliation loop). Providers may opt to reenable the shared gRPC server runtime based on these schedulers, which properly isolate the forked Terraform providers to prevent some external resource leakage issues we had observed in the past with the shared server runtime. We have also performed a set of external resource leakage tests with this runtime, which will be discussed below.
The max ttl configuration for the terraform.SharedProviderScheduler puts a limit on the lifetime of a forked native plugin process, the TTL of a forked plugin process is incremented each time the Terraform CLI is to be invoked against it. So basically the TTL of a plugin process holds the number of times the process has been used to handle requests from Terraform client. After the a plugin process expires, the scheduler attempts to replace it. The scheduler also keeps track of whether a plugin process is actively in use or not and replacements are not allowed if the plugin process is in use. If the scheduler finds that an expired plugin process is in use, it allows new reuse requests for a grace period (measured as a percentage of the max ttl). After this grace period if the plugin process has not been replaced yet, then any new reuse attempts will be denied.
The terraform.WorkspaceProviderScheduler has a higher isolation level and shares a plugin process between the multiple Terraform CLI invocations and the multiple gRPC requests made by those CLI invocations only during a certain managed resource lifecycle event such as an observe, create, update or delete. It's meant to be used with certain provider configurations where using the shared scheduler will cause race conditions in the native provider.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

We are still evaluating the performance characteristics of this runtime. We are also collecting feedback from the community members who gave the provider packages consuming this runtime a try. Relevant issues are here:

https://github.com/upbound/provider-aws/issues/576
https://github.com/upbound/provider-azure/issues/404
https://github.com/upbound/provider-gcp/issues/255

We have also performed two long-running tests (one 2d 16h long, the other 4d 16h long) with a modified https://github.com/upbound/platform-ref-aws Crossplane configuration package (modified to depend on a upbound/provider-aws package that consumes this runtime). No leaks were observed. We also could not observe external resource leaks during an experiment with this runtime with 210 cognitoidp.UserPool resources spanning over 7 AWS regions, with 30 MRs per region. In this experiment, we also configured the poll interval to 1m to increase the likelihood of a race condition. This experiment lasted for 19h. Through another set of experiments involving 2 AWS regions conducted at the Terraform layer (not involving a Crossplane provider or upjet or the schedulers being discussed here) to stress test the isolation principle we've implemented. After 12h, no external resource leaks were observed.

We have a ttl value as 100. And also the ttlBudget is 0.1. As I understand, this means that, the native provider plugin process will be restarted after every 110 usage. For clusters with a low number of MRs, this means that the process will survive for a long time. Considering the memory leak problem on the Terraform side, how would it be to set a timeout for the relevant process? We can cover this in other iterations as well.

What about using ttlMargin instead of ttlBudget to avoid ambiguity.

Some test results that are done via this PR:
https://github.com/upbound/provider-aws/issues/576#issuecomment-1485259533
https://github.com/upbound/provider-aws/issues/576#issuecomment-1474137489
https://github.com/upbound/provider-aws/issues/576#issuecomment-1482747981

nit: What about using ttlMargin instead of ttlBudget to avoid ambiguity? We may also consider changing this in the next iteration.

Done.


Installation does not work

Installation does not work

I got sonnet and tensorflow and DNC to work

didi you use the pip ?


zero pubDate in RSS

https://github.com/gohugoio/hugo/issues/12438
The issue was not fixed for this site even if I use Hugo v0.128.1.

This problem doesn't exist in hugo-theme-yue.


Navigation submenus with down arrow key skips items

Summary

H
Steps to reproduce

Go to https://codepen.io/nickdjm/pen/YzMyraX (your demo)
tab into the nav
arrow left/right to an expandable menu item and expand it with space/enter
arrow down to cycle through it's and watch it skip every other item in the list

Expected Behaviour
It should not skip
Edit by maintainer: Fixed commented out content of issue

This has definitely been an issue before, but I thought it was resolved. I'll look to see if I can reproduce this locally.

@danderson421 I think this might have been fixed with some changes I made in 2.1.0. I've been testing out the demos with the latest version and it appears to be resolved. Are you able to confirm?


[node] Crash on websocket errors

Versions
What package version of the SDK are you using.
4.19.1-rc
What nodejs version are you using
18.14.0
What os are you using
Windows
Describe the bug
Give a clear and concise description of what the bug is.
With the recent fixes to the streaming framework, I can start the connection, but if I get an error, an unhandled exception is thrown from here, and I can't find a way to handle it. Looks similar to https://github.com/microsoft/BotFramework-DirectLineJS/issues/170.
To Reproduce
Connect to a URL that doesn't respond.
Expected behavior
It should propagate the error to be handled by the client code.

Reported originally here: https://github.com/microsoft/botbuilder-js/issues/4412#issuecomment-1406167695

@compulim do we have any updates on this?

@compulim Is this still a thing?


"unpack requires string length of 14" during xls upload

Test file: "Combined table 2.xls"
Bug courtesy The Star-Ledger

The full traceback:
WARNING *** OLE2 inconsistency: SSCS size is 0 but SSAT size is non-zero
Traceback (most recent call last):
  File "/Users/onyxfish/src/panda/panda/utils/xls.py", line 13, in extract_column_names
    sheet = book.sheet_by_index(0)
  File "/Users/onyxfish/.virtualenvs/panda/lib/python2.7/site-packages/xlrd/__init__.py", line 765, in sheet_by_index
    return self._sheet_list[sheetx] or self.get_sheet(sheetx)
  File "/Users/onyxfish/.virtualenvs/panda/lib/python2.7/site-packages/xlrd/__init__.py", line 998, in get_sheet
    sh.read(self)
  File "/Users/onyxfish/.virtualenvs/panda/lib/python2.7/site-packages/xlrd/sheet.py", line 1038, in read
    ) = unpack("<HHHHxxHH", data[:14])
error: unpack requires a string argument of length 14

Fantastic, this is fixed by simply upgrading to xlrd==0.7.3:
https://groups.google.com/d/msg/python-excel/kwR9sDf_SJY/dXRTRMm3dGYJ


Check StoreProvider arguments before using them

I was integrating osmosis for the first time in a new app. While doing that I tested what would happen if we don't provide the required arguments to StoreProvider.  See screenshots below when we for example don't provide store providers array. I think the new error I'm adding provides more context. Let me know if you have any suggestions.
Before

After

/cla-check.


Support Java 8 Optional (through reflections) #21

Coverage decreased (-0.2%) to 26.854% when pulling ecc3780a7bbc3ed1b0a023acce1a3f4bff851974 on zd0:master into b7da4773944f33ca0202ae4e79080e4a51771755 on zalando:master.

@zd0 could you maybe also add some tests to cover these changes?

Closing it as no activity for more than 6 years.


Allows header key/value to be empty

I have multiple environments and some need a header key with a header value. But my requests collections are the same. To handle it, all my environments have the header key and the header value as variable, but for the environment or is not useful, these values are empty.
There are two problems:

First, we can't save environments variable with an empty string, it's not persistent
Second, I can't send request with empty header name: "Error invoking remote method 'send-http-request': Error: header name must be a non-empty string". It is possible to make this check optional or be configurable to be skipped.

Using Bruno v1.11.0

Thanks for the PR @AntoninHuaut !
This will go out in the 1.13.0 release. Please subscribe to Discord announcement channel to stay notified on the releases.


Error occurs for parsing gpt4's response

Thanks for sharing your great work.
However, when I run RPG.py, I get an error like below.
NameError: name 'final_split_ratio' is not defined
I've tried changing the regex in mllm.py's get_params_dict function, but gpt4's response is giving me a response that doesn't match it, so I frequently get parsing errors.
like this :
### Final Output

**Overall split ratio:**
1;1;1

This is also the case with the regional prompt.
If anyone has solved this, please help😭

Similar Error I got,
Traceback (most recent call last):   File "/run/determined/workdir/home/RPG-DiffusionMaster/test.py", line 51, in <module>     images = pipe(   File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context     return func(*args, **kwargs)   File "/run/determined/workdir/home/RPG-DiffusionMaster/RegionalDiffusion_base.py", line 901, in __call__     matrixdealer(self,self.split_ratio,self.base_ratio)   File "/run/determined/workdir/home/RPG-DiffusionMaster/matrix.py", line 248, in matrixdealer     baseratio = baseratio2
UnboundLocalError: local variable 'baseratio2' referenced before assignment

I have also encountered similar problems, whether using llama or gpt4.

I am also observing similar problems. Sometimes the GPT4 output has:
#### c. Overall Ratio:
We need to combine the heights and widths in the specified format.
- Row0_height,Row0_region0_width,Row0_region1_width;Row1_height,Row1_region2_width,Row1_region3_width
- Final split ratio: 0.5,0.5,0.5;0.5,0.5,0.5

And split_ratio_match = re.search(r"Final split ratio: ([\d.,;]+)", response) in mllm.get_params_dict(output_text) can find the split ratio.
Other times the GPT4 output just has:
 ### Final Output
 - **Final Split Ratio:** 0.5,0.5,0.5;0.5,0.5,0.5

And split_ratio_match = re.search(r"Final split ratio: ([\d.,;]+)", response) in mllm.get_params_dict(output_text) doesn't find anything, even though we see the data is there.
I'm not understanding why the same prompt returns inconsistent output text. This is using the example prompt: ' A handsome young man with blonde curly hair and black suit  with a black twintail girl in red cheongsam in the bar.'

For whatever reason I encounter fewer of these parsing errors using the gpt-4o-mini or older gpt-4 models.


Change testing node count to 2

Currently when deploying cluster for testing purposes some pods will fail because there is not enough resources.
Changing node count from 1 -> 2 for testing fixes this.

LGTM.


Filesystem paths are not urlencoded

Description
File paths are templated into the html verbatim. Handlebars inserts html escape characters, but this doesn't handle things like filenames containing spaces correctly.
Steps to reproduce

touch 'file with spaces.txt'
Execute `http-server -h <IP_ADDRESS> -p 8080
Open http://<IP_ADDRESS>:8080
Click the files with spaces.txt link
The url is http://<IP_ADDRESS>:8080/files, which returns a 404

Environment
HTTP Server Version: v0.1.0
Operative System: Linux

@Benjamin-L a PR is available on #164! If you have any feedback please share it there!


Best tessdata Feedback -  Chinese

Ref: https://groups.google.com/d/msgid/tesseract-ocr/8cc88ed2-99c3-445e-b758-83ade0f680aa%40googlegroups.com?utm_medium=email
copied below
Good day!
Recently I was using tesseract (4.0 alpha) to do Chinese OCR and it works really great. Now I want to pick up a best model to use but I find several versions. What is the difference between them?

chi_sim from https://github.com/tesseract-ocr/tesseract/wiki/Data-Files (around 50M)
chi_sim from https://github.com/tesseract-ocr/tessdata/tree/master/best (around 13M)
chi_sim_vert from https://github.com/tesseract-ocr/tessdata/tree/master/best (around 13M)
HanS from https://github.com/tesseract-ocr/tessdata/tree/master/best (around 16M)

All of them can work but the results are slightly different. From my own evaluation #4 is the best, but I don't have any insight.
Appreciate for any help.

Please see https://github.com/tesseract-ocr/tessdata/commit/3a94ddd47be01fd897cbe31f05cbd2301454cf8a#commitcomment-23584234 which explains the difference between jpn and Japanese.
Similar logic will apply for Chinese.

Unrecognized characters in the chi_sim traineddata model
ref: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/vp2yug1Jjko/eIP4azwnBAAJ
partially copied below

I can recognize most of the characters, such as the han, ladin alphabet. But some characters, such as 'Joined', ' |Broken|0|1' at the file header, and |"|0|2, |m|0|2 at the end of the file, cannot be recognized by myself.

Can you explan what these characters mean?
4059    ki
4060    |ki|0|2
4061    |ki|1|2
4062    |in|0|2
4063    |in|1|2
 and so on

Thx alot.

'Joined', ' |Broken|0|1'

Those two also appear in other traineddata files.


bower.json is using wrong path for main

	"main": [
		"dist/2.0/slidebars.min.js",
		"dist/2.0/slidebars.min.css"
	]

should be
	"main": [
		"dist/slidebars.min.js",
		"dist/slidebars.min.css"
	]

Sorry duplicate of #242


:lady_beetle: plan status "vm fail" should be "partial fail"

Issue:
when one of more vms fails, we show status "vm fail" it's more helpful to call this status "partial"

There are 2 suggestions for the replaced migration status of this state where part of the VMs already failed but the plan migration is still not marked as failed:
option 1: a hard-coded "Some VMs Failed" status
option 2: a dynamic "X VMs failed" while X=num of current failed VMs  status
Screenshots:
Before:

After - option 1:

After - option 2:

@yaacov WDYT?

Current PR supports option 1

closing as duplicate of: https://github.com/kubev2v/forklift-console-plugin/issues/1285

sorry, https://github.com/kubev2v/forklift-console-plugin/issues/1285 is not a duplicate, it adds a case when vm is canceled instead of failed, and raise the question how to show users that some vms where canceled and not completed successfully.

addressed by #1318


Create /dashboard page

[x] create interaction table
[x] /dashboard endpoint
[x] interaction graph
[ ] tests
[ ] documentation

Codecov Report

Merging #92 (3c9f2a2) into dev (5478955) will decrease coverage by 2.25%.
The diff coverage is 72.72%.

@@             Coverage Diff             @@
##               dev      #92      +/-   ##
===========================================
- Coverage   100.00%   97.74%   -2.26%
===========================================
  Files           10       10
  Lines          126      133       +7
===========================================
+ Hits           126      130       +4
- Misses           0        3       +3

Impacted Files
Coverage Δ

apps/publishing/lib/publishing/helper.ex
100.00% <ø> (ø)

apps/publishing/lib/publishing/manage.ex
98.50% <0.00%> (-1.50%)
:arrow_down:

apps/publishing/lib/publishing/manage/article.ex
100.00% <ø> (ø)

apps/publishing/lib/publishing/interact.ex
88.23% <80.00%> (-11.77%)
:arrow_down:

Continue to review full report at Codecov.

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


High CPU Utilization

Describe the issue
CPU usage is high, ranging from 60-100% of 1 x vCPU.  This occurs after a full chain sync and with an empty wallet.
Expected behavior
CPU while the wallet is idle should be under 2%.  My experience is it uses onder 1%.
Screenshots

What platform are you using (Linux, Windows, Mac)
Linux Ubuntu 16.04 64-bit.with

Yep same here damn. I'll check the seeders.

When I only use the silknetwork seeders (silknetwork.net), I do not get peers.  When I only use the @MCDev seeders (dnsseeder.com, etc...), I get peers but the CPU usage is high.  When I add peers manually, CPU usage is normal and below 1%.
I will run it in debug mode and see what is causing the high CPU in the wallet.  Even if there is a problem with the seeders, it shouldn't affect the wallet like it does.  Sounds like an endless loop somewhere.

@MCDev The Silk Network Seeders had the same problem with CPU usage and it was indeed caused by a loop in the seeder. In the standard sipa-based seeder code, there is a line in main.cpp that asks for "Mainnet Seeds" and the problem arises from pointing the seeder at itself. Those nodes should be ip addresses to external nodes, not the sub/domain of the seeders.  If you point the seeder to itself it continually looks at itself to seed itself which turns into an endless loop. When a wallet connects to the Seeder, the first thing the Seeder does is point the incoming wallet connection to the Mainnet Seeds before it even sends the info on the nodes in it's DB. The solution is to remove that line of code completely (once the seeder has initiailized and connected to the network to find nodes) or to have those addresses point to an actual node rather than to a Seeder of nodes.
So, to illustrate, line 399 of main.cpp should look like this:
static const string mainnet_seeds[] = {"5<IP_ADDRESS>:62223", "104.555.186.122:62223" "562.555.163.103:62223", ""};
Not like this:
static const string mainnet_seeds[] = {"slk2.silknetwork.net", "slk1.silknetwork.net", ""};

As for why you are still unable to get a connection from the silk seeders, I do not know. I cannot replicate that issue. With a new build, new IP address, and clean DB, I connect within seconds every time.
I want to replace the old sipa seeder with this GO implementation, which has the added benefit of supporting more than one network with a single Seeder. https://github.com/gombadi/dnsseeder. First I need to create a GO version of the wallet, but it can be a very basic implementation --  as long as it works as a node. I won't be worried about wallet functionality.


[5.4] Added syncWithoutUpdating() function

This allows implements logic where only first user who created association can set data on pivot table.
https://github.com/laravel/internals/issues/679

No plans to add this right now.

@ddeath Thank you!


Add some documentation

This issue includes both the actual code documentation on the one hand and some (at least) basic docs for our Github page for users how to use the platform - including a kind of FAQ in the frontend.
ToDo:

[ ] Add some decent amount of code documentation
[ ] Add a (extensible?) FAQ to the frontend
[ ] Add basic docs for the Github page of this project.

This should be really important as it gets more and more difficult to add good documentation!


Fix/gen rust type from did

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

65 of 66 (98.48%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.7%) to 51.394%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

chainsight-cdk/src/convert/candid.rs
65
66
98.48%

Files with Coverage Reduction
New Missed Lines
%

../../../.cargo/registry/src/index.crates.io-6f17d22bba15001f/rust-format-0.3.4/src/lib.rs
1
62.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
2932

Relevant Lines:
5705

💛  - Coveralls


OpenAPI JS Wiki Example: Additional-Resolvers Import Path is mangled/broken [Windows only]

Describe the bug

Building with additional-resolvers.ts results in a mangled import path for it in the resulting artifacts:
Slashes are removed, the resulting code is bugged:
const additionalResolvers$0 = (0, tslib_1.__importStar)(require("..additional-resolvers.ts"));
// or even
const additionalResolvers$0 = (0, tslib_1.__importStar)(require("..srcadditional-resolvers.ts"));

To Reproduce
Steps to reproduce the behavior:
Build openapi-javascript-example, check .mesh/index.js

Expected behavior

Slashes are not to be removed - as they are required to organise files.
Environment:

OS: Windows 10 (not in WSL) - Linux does not reproduce the Bug
@graphql-mesh/cli:  0.56.3
NodeJS:  14

Additional context

Base issue: #2659 (Additional TypeScript Resolvers still require tslib dependencies at runtime in production)
Discovered while debugging: https://github.com/Urigo/graphql-mesh/issues/3628#issuecomment-1060445079

Fixed in the latest version


Are there file and folder pickers?

I'm looking a simple macOS app in Ruby, but need to pick files and folders. I can do this with Pashua, but it's not being actively supported.
If not what should I consider?
Thank you

Hi @MtnBiker
You can use open_file and save_file in Glimmer DSL LibUI.
https://github.com/AndyObtiva/glimmer-dsl-libui#extra-dialogs
Or is it something more different that you are looking for?

@kojix2 Looks like it. Now I'll try to look at glimmer-dsl-libui to sort out the syntax.
Thank you

@MtnBiker For selecting files, whatever @kojix2 mentioned is correct.
For selecting directories, that would be open_folder, but it won't be available until the next libui-ng C library release (a glimmer-dsl-libui included dependency), which should happen hopefully in the near future.
Otherwise, today, you could use Glimmer DSL for Tk with the Tk.chooseDirectory call to open a directory.
Alternatively, you could use Glimmer DSL for SWT in JRuby, which supports directory_dialog.open (as demonstrated in Hello, Directory Dialog!)

Hi, I just wanted to note that I just released glimmer-dsl-libui version 0.6.0.pre.0, which finally supports a newer version of the C libui library (the newer libui-ng), including support for open_folder (a variation on open_file that can open a directory).


Footer interface redesign

Current footer:

Proposed new redesign:

**Fonts are subject to change

This was fixed in #707


Scoreboard/Data commands

What problem does the feature solve
It is not easily possible to get data about a game from command blocks to display, e.g. custom signs/holograms
Describe the solution you'd like
Every game should be have a configurable scoreboard that stores data about a game.
The score board should show data like:

Player's health
Game info (similar to /bm info)
How many hits/kills each player has given/taken

Describe alternatives you've considered
Allow "/bm info" to select individual data, thus, allowing to be used in other commands. However, it will not work well with minecraft command blocks which largely revolve around /scoreboard and /execute for data manipulation.

A simple approach is to implement the PlaceholderAPI. Then, data will at least be neatly be available to other plugins (particularly most dynamic sign plugins).
In the long run, some sort of scoreboard would be really nice...

Version 0.6.0 has PlaceholderAPI implemented.


error in NB1_ClimateRegime.ipynb clim_reg.getLGP

@kidstoneszk Hi, apologies for the late reply. Several issues were reported to us, many due to the newer version of Numba (>v0.53), which does not support some of our scripts/commands. This should be fixed now. Please re-clone the updated repo. Let us know if the issue still persists.


no more strange "fast" string function but std.string

Removed the use of faststring as they served no purpose really.
If this thing is supposed to go into phobos at some point, I bet drinks at dconf, that this would have been flagged anyway.
Plus, less code!

thanks


Fixing MPI slicing issue

Fix for issue #1862. Lets see how CI reacts.
TODO:

Tidy up the fix.
Add lots of tests.

Also note #1010.

Superseded by #1947.


queue.publish span takes very long without any clear reason

How do you use Sentry?
Self-hosted / on-premises
SDK version
4.5.1
Steps to reproduce

We have a job that spawns multiple jobs
The 'spawning' job takes very long, due the cause of the queue.publish span

It's not really sure why. Any idea?
Expected result
This should be instant.
Actual result

What queue driver are you using? It looks like database? But maybe also sync?
Can you tell me a little more simplified about your setup (how the jobs are nested)?

What queue driver are you using? It looks like database? But maybe also sync? Or even sqs?
Can you tell me a little more simplified about your setup (how the jobs are nested)?

Yes, database driver. These are async jobs. These jobs are spawned from a scheduled command, the command iterates over tentants and repeats some business logic in the context of the tentant. Jobs are spawned when certain conditions are met.

Can you show me some code I could add to a new Laravel application that mimics what you are doing? So far I have not been able to figure what is happening or how to reproduce it on our side.

/close
Hasn't occurred for a while


[AutoPR datafactory/resource-manager] Creating new API version for ADF

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3270

Can one of the admins verify this patch?

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2136


Add monitor and milestones to boba

There are some contracts listed on L2Beat that are missing in discovered.json:
https://etherscan.io/address/0xC891F466e53f40603250837282eAE4e22aD5b088
https://etherscan.io/address/0x1A26ef6575B7BBB864d984D9255C069F6c361a14
https://etherscan.io/address/0x5fD2CF99586B9D92f56CbaD0A3Ea4DF256A0070B

Some changes that we can see in the discovery should be updated in the config L1MultiMessageRelayer is missing now L1LiquidityPool, L1NFTBridge changed address

Missing contracts added


Talks page

fetch talk & tutorial pages
readme change pip to pipenv

review file change

Hello @MozixReality, thanks for your work and sorry for the late review. I'll merge this PR and we will have some refactor works to do.


package mismatch

There is no Avalonia package available for the newest version (2.1.8). If I now use the Material.Icons package at some project (because of the ItemKind enum) and Material.Icons.Avalonia at some other project (latest version 2.1.0) then the enum values are wrong and the wrong icons are displayed. Additionally the newest icons can not be used with Material.Icons.Avalonia.
As is:

Expected (if I change the Material.Icons back to 2.1.0):

Solution would probably be to increase version number for the other projecs as well.

Hello, @Yinimi
Does the pinning the last version of Material.Icons in your launchable csproj resolves the problem?

Hmm, so we probably need to fix the icon's integers values nor the bumping Material.Avalonia package, isn't it?

I think if all assemblies are being updated and not only the Materials.Icons project the problem would be fixed #30

Ok, let's merge it, if it fixes the problem


cupyx.scipy.spatial.distance.pdist did not support jaccard and dice metric

Description
It would be good to add support to jaccard and dice metric. Thanks.
Additional Information
No response

Thanks for the request @seraphzl. It seems RAFT which backs pdist already supports jaccard and dice metric, so it should be easy to add support for them.
https://docs.rapids.ai/api/raft/stable/cpp_api/distance/#_CPPv4N4raft8distance12DistanceTypeE
cc/ @cjnolet

@kmaehashi I would like to add this.

any update?


Your mod will not run - Config need to accept empty values/or false

Hey,
I tried to get your mod to run, I added the Jar-Files to the config. But my Problem is, I dont have all mods installed which you fix. So i tried to leave the values of the non-installed mods "" or false, even removed the lines one time. But your mod will always crash and want me to put in these values.
For me its therefore unusable, but I thought you're may interested in that behavior. If there is a option to ignore uninstalled mods, you should add it to your wiki page how to set this in the config. I couldn't figure out^^
Thanks for your work =)
Petschko

Hello. If you don't have the mod installed you can just leave the value empty.
Make sure you have added the mod names on the right line, otherwise it will crash.
If you are still having errors, show your configuration file and the crash report.

Here is the message with the crash log
Config:
{
    "netherChest": "",
    "bloodMagic": "",
    "industrialForegoing": "",
    "actuallyAdditions": "",
    "thaumcraft": "Thaumcraft-1.12.2-6.1.BETA26.jar",
    "extraUtilities": "extrautils2-1.12-1.9.9.jar",
    "tinyProgressions": "",
    "theFarlanders": "",
    "enderio": "EnderIO-1.12.2-5.2.61.jar",
    "_comment": "Visit the wiki to learn how to configure it: https://github.com/Focamacho/DupeFix-Project/wiki",
    "thaumicWonders": "",
    "spiceOfLife": ""
}

[19:00:58] [main/INFO] [mixin]: SpongePowered MIXIN Subsystem Version=0.8 Source=file:/C:/Users/Peter/Downloads/Serenetity%20Online%20Server/./mods/DupeFixProject-1.12.2-3.0.3.jar Service=LaunchWrapper Env=SERVER
[19:00:58] [main/WARN] [FML]: The coremod DupeFixProjectCoreMod (com.focamacho.dupefixproject.asm.DupeFixProjectCoreMod) is not signed!
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Blood Magic. If the mod is present, check your configuration file.
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Nether Chest. If the mod is present, check your configuration file.
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Spice of Life. If the mod is present, check your configuration file.
[19:00:58] [main/INFO] [DupeFix Project]: Initializing Thaumcraft Fixes
[19:00:58] [main/INFO] [mixin]: Compatibility level set to JAVA_8
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Tiny Progressions. If the mod is present, check your configuration file.
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Industrial Foregoing. If the mod is present, check your configuration file.
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Actually Additions. If the mod is present, check your configuration file.
[19:00:58] [main/INFO] [DupeFix Project]: Initializing Extra Utilities Fixes
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for The Farlanders. If the mod is present, check your configuration file.
[19:00:58] [main/ERROR] [DupeFix Project]: Couldn't load fixes for Thaumic Wonders. If the mod is present, check your configuration file.
[19:00:58] [main/INFO] [LaunchWrapper]: Loading tweak class name com.forgeessentials.core.preloader.FELaunchHandler
[19:00:58] [main/INFO] [LaunchWrapper]: Loading tweak class name net.minecraftforge.fml.common.launcher.FMLDeobfTweaker
[19:00:58] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[19:00:58] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.common.launcher.FMLInjectionAndSortingTweaker
[19:00:58] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[19:00:58] [main/INFO] [TickProfiler]: TickProfiler v1.12-0.0.7 coremod injectData called, loading patches
[19:00:58] [main/INFO] [ModPatcher]: ModPatcher running under classloader net.minecraft.launchwrapper.LaunchClassLoader
[19:00:58] [main/INFO] [JavaPatcher]: Added patch minecraft: Patcher.ClassPatchDescriptor(name=net.minecraft.world.World, patches=[Patcher.PatchDescriptor(methods=func_72939_s()V, patch=clone), Patcher.PatchDescriptor(methods=func_72939_s()V, patch=insertCodeBefore), Patcher.PatchDescriptor(methods=updateEntities_withProfiling(), patch=replaceMethodCall), Patcher.PatchDescriptor(methods=updateEntities_withProfiling(), patch=replaceMethodCall), Patcher.PatchDescriptor(methods=updateEntities_withProfiling(), patch=replaceMethodCall), Patcher.PatchDescriptor(methods=updateEntities_withProfiling(), patch=replaceMethodCall), Patcher.PatchDescriptor(methods=updateEntities_withProfiling(), patch=replaceMethodCall)])
[19:00:58] [main/INFO] [JavaPatcher]: Added patch minecraft: Patcher.ClassPatchDescriptor(name=net.minecraft.network.play.server.SPacketCustomPayload, patches=[Patcher.PatchDescriptor(methods=, patch=addMethod)])
[19:00:58] [main/INFO] [JavaPatcher]: Added patch minecraft: Patcher.ClassPatchDescriptor(name=net.minecraft.network.NettyPacketEncoder, patches=[Patcher.PatchDescriptor(methods=encode(Lio/netty/channel/ChannelHandlerContext;Lnet/minecraft/network/Packet;Lio/netty/buffer/ByteBuf;)V, patch=replaceMethodCall)])
[19:00:58] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[19:00:59] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557
[19:00:59] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[19:00:59] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[19:00:59] [main/INFO] [LaunchWrapper]: Calling tweak class net.minecraftforge.fml.relauncher.CoreModManager$FMLPluginWrapper
[19:01:00] [main/INFO] [LaunchWrapper]: Calling tweak class codechicken.asm.internal.Tweaker
[19:01:00] [main/INFO] [STDOUT]: [codechicken.asm.internal.Tweaker:injectIntoClassLoader:30]: false
[19:01:00] [main/INFO] [LaunchWrapper]: Calling tweak class org.spongepowered.asm.launch.MixinTweaker
[19:01:00] [main/INFO] [mixin]: Initialised Mixin FML Remapper Adapter with net.minecraftforge.fml.common.asm.transformers.deobf.FMLDeobfuscatingRemapper@7063686f
[19:01:00] [main/INFO] [LaunchWrapper]: Calling tweak class com.forgeessentials.core.preloader.FELaunchHandler
[19:01:00] [main/WARN] [mixin]: MixinEnvironment::setCompatibilityLevel is deprecated and will be removed. Set level via config instead!
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: java.lang.reflect.InvocationTargetException
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at java.lang.reflect.Method.invoke(Unknown Source)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.run(ServerLaunchWrapper.java:70)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:main:34]: 	at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.main(ServerLaunchWrapper.java:34)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:run:75]: Caused by: java.lang.NoSuchMethodError: org.spongepowered.asm.launch.platform.MixinPlatformManager.addContainer(Ljava/net/URI;)Lorg/spongepowered/asm/launch/platform/MixinContainer;
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:run:75]: 	at com.forgeessentials.core.preloader.FELaunchHandler.acceptOptions(FELaunchHandler.java:91)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:run:75]: 	at net.minecraft.launchwrapper.Launch.launch(Launch.java:114)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:run:75]: 	at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
[19:01:00] [main/INFO] [STDERR]: [net.minecraftforge.fml.relauncher.ServerLaunchWrapper:run:75]: 	... 6 more

This may be caused by another mod loading an outdated version of Mixin. Probably ForgeEssentials.
Make sure you are using the latest version of ForgeEssentials (12.3.83).

I will close this issue, if the problem persists let me know.


[GUI] Fit texture scale to slate dimensions

See https://forum.babylonjs.com/t/image-doesnt-rescale-to-fit-the-new-dimensions-of-my-holographicslate/52938?u=raananw
Setting fitContentToDimensions to true will make everything work as expected

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15502/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15502/merge/testResults/webgl2playwright/index.html


Swarm webrouting - relative paths or path prefix

I'm trying to run swarmui behind nginx in a specific path.
When I open http://vhost.lan/swarmui/, it redirect to http://vhost.lan/Text2Image instead of http://vhost.lan/swarmui/Text2Image
I didn't found any setting to specify a prefix path and/or any setting to force swarmui to use relative paths.
There is a way?

as I'm not currently at home I don't have easy access to muck about with webservers to test against, but the above commit should make all or at least most paths relative, and thus work as intended. If anything doesn't work please let me know


ACC Stream

Are there any speccific needs, on the ACC stream? Can not make it load, at the player at all?
Is there any issue?

there is many kind of AAC stream... and even many kind of AAC (such as AAC+)
AAC+ streams that shoutcast use, are not supported, they are not compliant to standard used by flash and other browsers:
Look here, for just AAC+ support:
https://groups.google.com/forum/#!searchin/jplayer/bruno/jplayer/9Ks2Crfjwrg/jDCDBgv3qr0J


Why doesn't this project do my taxes for me?

Summary
What do you want to know about this project?
Why doesn't this project do my taxes for me? I don't understand why this feature does not exist.

Hi @oss-contributor, this feature doesn't fit in with our project. Thank you for the suggestion though.
Closing this issue.


Update namespacing tip (#1)

Prefer using enum namespaces rather than structs
since you can't construct a case-less enum.

Hi @jessesquires! 👋 Thanks for this suggestion. I'm personally not a big fan of the enum name spacing hack, since I feel like it's a bit unintuitive. Instead, I almost always avoid empty namespace-only types. In the example, the Map struct is not only a namespace, it's a model from a game that I'm working on. I also don't usually modify these tips unless there's some syntax or spelling error, since this repo is simply a collection of all my Swift tips from Twitter. Thanks a lot anyway 🙂

FYI that this "misusage" of enums is also adopted in Swift itself, which seem to suggest that this is intended usage. :)

@BasThomas I didn't say that it's misusage 😉 I just consider it a hack, and the Swift code base does (just like any other code base) of course contain it's fair use of hacks 😄

@BasThomas can you share where is it used in Swift itself? just curious 🙂
also, for structs, you can just add private init() {} and move on with it 🙂