NUTCH 2940 Develop Gradle Core Build for Apache Nutch

Fixed compile-core, except still generating unneeded bin in tmp dir.
EDIT: added temp fix to prior issue (manually deleting dir). Moved forward and also fixed jar, job, and runtime.
Thanks for your contribution to Apache Nutch! Your help is appreciated!
Before opening the pull request, please verify that

there is an open issue on the Nutch issue tracker which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
the issue ID (NUTCH-XXXX)

is referenced in the title of the pull request
and placed in front of your commit messages surrounded by square brackets ([NUTCH-XXXX] Issue or pull request title)

commits are squashed into a single one (or few commits for larger changes)
Java source code follows Nutch Eclipse Code Formatting rules
Nutch is successfully built and unit tests pass by running ant clean runtime test
there should be no conflicts when merging the pull request branch into the recent master branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled master branch.

We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Nutch in general, please sign up for the Nutch mailing list. Thanks!

Most recent commit has all tasks fixed up to and including runtime, pending review

Also note gradle clean jar results in the following issue. Please take a look into it.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD SUCCESSFUL in 4s
9 actionable tasks: 4 executed, 5 up-to-date

Thank you @jbsimmon

@lewismc Fixed errors with files not copying over, and also fixed the deprecated gradle feature error. Tried to implement compile-core-test but still getting an error about non-existent packages, not sure if dependency related. Please take a look at most recent commit for changes, thank you!

Also, when I run job and look into the artifact I see the following
jar tf build/apache-nutch-1.19-SNAPSHOT.job
META-INF/
META-INF/MANIFEST.MF
classes/
classes/plugins
org/
org/apache/
org/apache/nutch/
org/apache/nutch/tools/
org/apache/nutch/exchange/
org/apache/nutch/metadata/
org/apache/nutch/fetcher/
org/apache/nutch/tools/warc/
org/apache/nutch/crawl/
org/apache/nutch/util/
org/apache/nutch/segment/
org/apache/nutch/service/
org/apache/nutch/service/model/
org/apache/nutch/service/model/response/
org/apache/nutch/tools/arc/
org/apache/nutch/net/
org/apache/nutch/hostdb/
org/apache/nutch/protocol/
org/apache/nutch/service/resources/
org/apache/nutch/scoring/
org/apache/nutch/scoring/webgraph/
org/apache/nutch/net/protocols/
org/apache/nutch/plugin/
org/apache/nutch/util/domain/
org/apache/nutch/indexer/
org/apache/nutch/publisher/
org/apache/nutch/parse/
org/apache/nutch/service/model/request/
org/apache/nutch/service/impl/

No compiled classes, configuration resources or libraries are being packaged into .job. This needs to be fixed.

Going to merge @jbsimmon we can open new PR's when we identify issues.


Dead image link on doc page on Chrome

a simple link appears on Firefox

Seems like a css problem

the problem is that the src of the image is / which obviously points to nothing


Test branch

Description
Please include:

relevant motivation
a summary of the change
which issue is fixed.
any additional dependencies that are required for this change.

Closes: # (issue)
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have added a short summary of my change to the CHANGELOG.md
[ ] My code follows the style guidelines of this project
[ ] I have commented my code in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

A note about the CHANGELOG
Hello 👋 and thank you for contributing to Gradio!
All pull requests must update the change log located in CHANGELOG.md, unless the pull request is labeled with the "no-changelog-update" label.
Please add a brief summary of the change to the Upcoming Release > Full Changelog section of the CHANGELOG.md file and include
a link to the PR (formatted in markdown) and a link to your github profile (if you like). For example, "* Added a cool new feature by [@myusername](link-to-your-github-profile) in [PR 11111](https://github.com/gradio-app/gradio/pull/11111)".
If you would like to elaborate on your change further, feel free to include a longer explanation in the other sections.
If you would like an image/gif/video showcasing your feature, it may be best to edit the CHANGELOG file using the
GitHub web UI since that lets you upload files directly via drag-and-drop.

All the demos for this PR have been deployed at https://huggingface.co/spaces/gradio-pr-deploys/pr-22-all-demos


solid/reactivity is false positive for custom element event handlers & callbacks in context updates

Hi! First of all, thank you for a great plugin! I'm new to Solid.js, so I'm not even sure if it's a bug.
Describe the bug
It looks like the plugin gives a false positive warning in two cases:

When I use reactive variables in event handlers in custom elements
When I use reactive variables in callbacks for updating store values

Here is a code example:
import { createContext, createSignal, useContext } from "solid-js";

function CustomButton(props) {
  return <button onClick={props.onClick}>{props.label}</button>;
}

const CustomContext = createContext();

function CustomProvider(props) {
  return <CustomContext.Provider value={{}}>{props.children}</CustomContext.Provider>;
}

function App() {
  const [counter, setCounter] = createSignal(0);
  const [, setContextValue] = useContext(CustomContext);

  return (
    <>
      <CustomButton
        // ESLint: This function should be passed to a tracked scope (like createEffect) or an event handler because
        // it contains reactivity, or else changes will be ignored.
        onClick={() => {
          setCounter(counter() + 1);
        }}
      >
        Click me!
      </CustomButton>

      <button
        // ESLint: This function should be passed to a tracked scope (like createEffect) or an event handler because
        // it contains reactivity, or else changes will be ignored.
        onClick={() => setContextValue("key", (prev) => prev + counter())}
      >
        Click me!
      </button>
    </>
  );
}

[x] I would be willing to contribute a PR to fix this issue

same problem

What version of the plugin were you using, or were you using the playground? There was an issue that caused warnings like these that has now been fixed. When I load your example now, I see only two warnings.
  return <button onClick={props.onClick}>{props.label}</button>;

This one is valid—see reasoning here.
        onClick={() => setContextValue("key", (prev) => prev + counter())}

This one occurs because the linter doesn't know that setContextValue is supposed to be a store setter, because it's an arbitrary variable taken from a context. So, it doesn't know that the updater function is "special" and runs synchronously. I'll consider allowing updater functions to be passed to any set* function call, but for now this is working as expected.
Thanks for filing an issue and don't hesitate to ask if anything else comes up!


Pigeon hole sort

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
Added Pigeon hole Principle
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #3055

Kindly review this @bhav09 @ankitaggarwal23 @HarshCasper


sfdx sfpowerscripts:orchestrator:quickbuild - TypeError: Cannot read properties of undefined (reading 'prototype')

Describe the bug
When running sfpowerscripts:orchestrator quickbuild I receive TypeError: Cannot read properties of undefined (reading 'prototype')
To Reproduce
Steps to reproduce the behavior:
@salesforce/cli/2.6.9 win32-x64 node-v18.15.0
@dxatscale/sfpowerscripts 23.4.2
sfdmu 4.30.0
sfpowerkit 6.1.0
Run one of the following commands:
sfdx sfpowerscripts:orchestrator:quickbuild -v devhubname--buildnumber xxx --branch branchname
sfdx sfpowerscripts:orchestrator:quickbuild --diffcheck -v devhubname
Expected behavior
quickbuild runs without error
Screenshots
If applicable, add screenshots to help explain your problem.
Platform Details (please complete the following information):

OS: Windows 11 Home
Version [e.g. CLI Version  eg: 1.6.6]
Salesforce CLI(sfdx cli) Version:
salesforce/cli/2.6.9
NodeJs Version: 18.15.0
Plugin versions:
@dxatscale/sfpowerscripts 23.4.2
sfdmu 4.30.0
sfpowerkit 6.1.0

Additional context
Yesterday my sfdx stopped working, and I uninstalled and reinstalled the Salesforce CLI. Today I also reinstalled the plugins and I was able to use some sfpowerscripts commands as the pool list and fetch a scratch org, but I failed when trying to build the packages using orchestrator build. I've also authorized again the DevHub.

@emoraiss  sfpowerscripts latest version is no longer a sfdx plugin, you can install it using npm and then use as 'sfp'. globally


[deliver] issue with bundler 1.13.0

When attempting to execute deliver (1.13.3) we are seeing the following error relating to bundler (1.13.0)
/Users/andy/.rvm/gems/ruby-2.3.1/gems/bundler-1.13.0/lib/bundler/rubygems_ext.rb:23:in source': uninitialized constant Gem::Source (NameError)
Did you mean?  Gem::Source
from /Users/andy/.rvm/gems/ruby-2.3.1/gems/bundler-1.13.0/lib/bundler/rubygems_ext.rb:65:in extension_dir'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/basic_specification.rb:46:in gem_build_complete_path'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:2174:in missing_extensions?'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/basic_specification.rb:71:in contains_requirable_file?'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1067:in block in find_in_unresolved'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1067:in each'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1067:in find_all'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1067:in find_in_unresolved'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:73:in require'         from /Users/andy/.rvm/gems/ruby-2.3.1/gems/bundler-1.13.0/lib/bundler/rubygems_ext.rb:23:in source'
from /Users/andy/.rvm/gems/ruby-2.3.1/gems/bundler-1.13.0/lib/bundler/rubygems_ext.rb:35:in full_gem_path'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/basic_specification.rb:142:in block in full_require_paths'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/basic_specification.rb:141:in map'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/basic_specification.rb:141:in full_require_paths'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1542:in add_self_to_load_path'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1411:in activate'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1442:in block in activate_dependencies'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1428:in each'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1428:in activate_dependencies'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1410:in activate'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1442:in block in activate_dependencies'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1428:in each'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1428:in activate_dependencies'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/specification.rb:1410:in activate'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems.rb:299:in block in activate_bin_path'         from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems.rb:299:in synchronize'
from /Users/andy/.rvm/rubies/ruby-2.3.1/lib/ruby/site_ruby/2.3.0/rubygems.rb:299:in activate_bin_path'         from /Users/andy/.rvm/gems/ruby-2.3.1/bin/deliver:22:in '
from /Users/andy/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in eval'         from /Users/andy/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in '`
Reverting to bundler-1.13.0.rc.1 resolves the problem.
Is anybody else experiencing this issue?

@andyh200 Hi! We are aware of this issue and are working on a fix. It is being tracked elsewhere, but I cannot find it because 'bundler' is in every issue. Thanks!

This looks to be resolved now with deliver 1.13.3 and bundler 1.13.1

@andyh200 Really appreciate you updating us and so glad you got up and running. Hope that you have a great weekend coming up. 👍 💯


[BEAM-2508] Fix DoFn javadoc: StateSpec does not require a key

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify.
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @JingsongLi

Coverage increased (+0.007%) to 70.846% when pulling f99ab1a472868e4ce175a86e5d76823b1c09c10b on kennknowles:DoFn-javadoc into 0e429b33ff85eba08da5018c9febd0b99b44f720 on apache:master.

LGTM.


file loss

hi,the project include some .h file and i cant find
such as:BC7Config.h BC7Compressor.h and avpcl.h

i make ETCEncoder to lib，the application while shutdown when i compress.
`	std::string _strfile = "F:\all.png";
std::vector _image;
unsigned _width, _height;
unsigned _error = lodepng::decode(_image, _width, _height, _strfile, LCT_RGB, 8);
if (_error)
{
	return 0;
}
std::cout << _image.size() << ":" << _width << ":" << _height << std::endl;
uint8 *_imageinbuffer(new uint8(_image.size()));
memcpy(&_imageinbuffer, &_image, sizeof(_image));
uint8 *outBuffer = new uint8(sizeof(_image));
std::unique_ptr<FasTC::CompressionJob> pCompressJob(new FasTC::CompressionJob(FasTC::eCompressionFormat_ETC1,
	(const uint8*)_imageinbuffer,
	outBuffer,
	_width,
	_height));
DXTC::CompressImageDXT1(*pCompressJob);`

shutdown from this
  void ExtractBlock(const uint32* inPtr, uint32 width, uint8* colorBlock)   {     for (int j = 0; j < 4; j++)     {       memcpy(&colorBlock[j * 4 * 4], inPtr, 4 * 4);       inPtr += width;     }   }
I dont know where is error

thanks for your code，i had finish this

I'm unclear about what the problem or the solution was. For the .h files, some of those are generated through CMake's configuration process. If you have any other questions feel free to reopen a new issue.


Upgrading to voyager 1.* everything has voyager. prepended!

Laravel Version: 5.5.*
Voyager Version: 1.0.6
PHP Version: 7.0

Description:
I just upgraded to the latest voyager version from a 0.11 version and I followed the instructions however, after the ugprade all of the buttons and titles look like:

Steps To Reproduce:

@cadmicro you have to publish voyager assets, or maybe if you have custom views, verify your code.

The command you want is: artisan vendor:publish --force --provider=TCG/Voyager/VoyagerServiceProvider --tag=lang
Some people have reported issues when publishing the language assets.  A workaround for this is to manually copy the lang folder (vendor/tcg/voyager/publishable/lang) to your app (resources/lang).
This should resolve your issue


202308-notebook-distribution

A new notebook on analysing data distribution, including estimating rank, quantiles, and histograms. This has a focus on the Quantiles sketch.

This PR has:

[x] been self-reviewed.
[x] been tested in a test Druid cluster.
[ ] been tested on the Jupyter docker container.

Reminder to also add the Apache license to the notebook


Wait until deployment is ready before exiting

Fixes https://github.com/zeit/now-cli/issues/847

@rtsao Can you check your code again? I had to rebase - looks different than before.

Closing in favor of: https://github.com/zeit/now-cli/pull/940
Some changes in canary has made some changes in this PR unnecessary/irrelevant


Omit timestamp and colors from logs

Feature Request
I was wondering if it's already possible or might be a quick addition to allow for logging to omit timestamps and colors from logs
Motivation Behind Feature
Our logger already adds timestamps so when you download the logs the timestamp is there twice. The colors also seem to just add extra cruft in the logs.

Yes:
Color: https://docs.fastlane.tools/faqs/#disable-colored-output
Timestamp: https://docs.fastlane.tools/advanced/fastlane/#output-environment-variables


PP-6494 Trim and validate Worldpay 3DS Flex credentials

Trim leading and trailing whitespace from entered Worldpay 3DS Flex credentials and validate them according to the following rules:

Organisational unit ID: 24 lower-case hexadecimal characters e.g. “1234567890abcdef12345678”
Issuer: 24 lower-case hexadecimal characters e.g. “1234567890abcdef12345678”
JWT MAC key: a UUID ID in its lowercase canonical textual representation e.g. “abcdef12-3456-7890-abCd-ef1234567890”.

Trimming is because users will almost certainly be copying and pasting these values, so may unintentionally copy leading ortrailing whitespace.
If validation fails, display a standard error summary with error messages saying “Enter your organisational unit ID in the format you received it” or similar, and represent the form with the trimmed organisational unit ID and issuer (but not the JWT MAC key because we treat that like a password) entered by the user prefilled.
Remove the existing client-side validation that checks that a value is entered for each field to avoid mixing client-side and server-side validation (the new server-side validation ensures that no fields are left blank).
Add hint text to each form field saying it’s “Provided to you by Worldpay” with an example of valid input (taken from Worldpay’s test values).
Add parenthical “API ID” and “API key” notes to the issuer and JWT MAC key labels to more closely match how Worldpay describe them. Don’t bother adding Worldpay’s “org unit ID” abbreviation to the organisational unit ID because it’s obvious.
Consistently use regular sentence case when displaying terms like “organisational unit ID” in the admin tool, even though Worldpay use title case, to match our style.

Looks really good - 1 minor point.


Migrate knex repo to Typescript completely

Feature discussion / request
Hi all, I'm not sure where is the best place to discuss this, so I created this issue. This is my motivation: I have been using typeorm quite a bit, and have a mental wish list of desired features. I started by thinking I would create my own ORM on top of knex, because I have had such good experience with it. Then I discovered mikro-orm, which is great, is built on top of knex, and is closer to what I want.  However, it doesn't support SQL Server, which I need. So, I started trying to implement mikro-orm for mssql. However, it requires a bunch of monkey-patching knex, and since there are no types, this was inaccessible for me. So, I decided to see what it would be like to migrate knex to typescript.
My desire is to migrate knex source code to Typescript completely. I want to be backwards compatible and have no breaking changes if possible. I see that there are various discussions about advancing knex and making it into something like mikro-orm. But for me, I like knex as it is -- a query builder, and I like other projects to implement ORMs as they see fit. Having said that, I feel that moving to typescript will help to clean up the codebase considerably, catch existing bugs, and make future maintenance and enhancements easier.
I have forked this repo and have made a few commits, which you can find here. I have already been able to identify some potential bugs and greatly simplify some of the code. I am currently working with static analysis and will eventually get to making sure all the tests pass, once it compiles.
Please let me know what you think and if you have any comments/questions/concerns.

@OlivierCavadenti What do you think?
Personally I have mixed feelings about this. First, knex codebase is huge, and migration is going to be a very significant effort. Second, TS transpilation reduces amount of control one has for generated code, and this may result in unexpected performance issues, which is important for lower-level library such as knex.
@dustbort What about a middle ground between monkey-patching knex and rewriting it to TS entirely? Maybe some additional extension points could be added into knex, which would allow implementing necessary functionality in mikro-orm cleanly?

@kibertoad I am willing to put in the effort. The transpilation should not affect the performance in such a way. I have set the target as es2019, so there will not be much change to the original code, aside from the few features implemented after es2019. Es2019 is compatible with node13+, which is what the knex documentation states it supports.

I willing to help that effort, also +1 to

The transpilation should not affect the performance in such a way
Typescript is not entire different language, usually compilation is just removing types & transpiling basic things like .? operators

@kibertoad A happy medium could be to start adding JSDoc type comments to every function, and enabling TypeScript to check against that. Prevents you from having to have a build-step, but you still get the type-checking benefits of TypeScript, for example:
/**
 * @type {(input: string) => string}
 */
function example(input) {
  return 15; // Error due to incorrect return type
}


ZEPPELIN-358: Jetty server is HTTP ERROR 404

ZEPPELIN-358
Define local jetty temp directory.
varName: zeppelin.war.tempdir
default varValue: webapps
Zeppelin create temp directory in {zeppelin.home}/webapps when zeppelin server start.

Thanks. I have tested. works nicely and got this log
 INFO [2015-12-02 11:06:22,383] ({main} WebInfConfiguration.java[unpack]:478) - Extract jar:file:/zeppelin-0.6.0-incubating-SNAPSHOT/zeppelin-web-0.6.0-incubating-SNAPSHOT.war!/ to /zeppelin-0.6.0-incubating-SNAPSHOT/webapps/webapp

Looks good to me.
One minor thing is, do you mind add the environment variable to
https://github.com/apache/incubator-zeppelin/blob/master/conf/zeppelin-env.sh.template#L27
and the property to
https://github.com/apache/incubator-zeppelin/blob/master/conf/zeppelin-site.xml.template
and update documentation
https://github.com/apache/incubator-zeppelin/blob/master/docs/install/install.md

Thanks for your review.
I update the documents.

I update the documents.

Thanks for the contribution.
Looks good to me and merge if there're no more discussions.

Looks great to me, merging if there are no other discussions.


I want to implement Bilinear interpolation

I want to use the Bilinear interpolation technique to resize image @geekquad sir and @unnati914 ma'am please assign me this issue.

Go ahead @Ashishsingh619.

@geekquad Sir i cant do this issue please assign it to some other participant please.

@geekquad sir, Can I take up this issue?.. I want to implement this. I'm a gssoc'21 participant.

Go ahead @sherin527.


Tsx file returns error

Hi, when I try to use this plugin in tsx file, I face with following error:
E5108: Error executing lua ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: .../p
acker/start/refactoring.nvim/lua/refactoring/query.lua:23: No treesitter parser found. Install one using :TSInstall <language>
stack traceback:
        [C]: in function 'error'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:45: in function 'step'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:48: in function 'execute'
        ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:118: in function <...ck/packer/start/plenary.nvim/lua/plenary/async/
async.lua:117>
        ...start/refactoring.nvim/lua/refactoring/pipeline/init.lua:70: in function 'run'
        .../start/refactoring.nvim/lua/refactoring/refactor/106.lua:557: in function <.../start/refactoring.nvim/lua/refactoring/refacto
r/106.lua:538>
        ...k/packer/start/refactoring.nvim/lua/refactoring/init.lua:31: in function 'refactor'
        [string ":lua"]:1: in main chunk

Here is my treesitter.lua config
-- import nvim-treesitter plugin safely
local status, treesitter = pcall(require, "nvim-treesitter.configs")
if not status then
	return
end

-- configure treesitter
treesitter.setup({
	-- enable syntax highlighting
	highlight = {
		enable = true,
	},
	-- enable indentation
	indent = { enable = true },
	-- enable autotagging (w/ nvim-ts-autotag plugin)
	autotag = { enable = true },
	-- ensure these language parsers are installed
	ensure_installed = "all",
	-- auto install above language parsers
	auto_install = true,
	-- magic
	sync_install = false,
})

Hi @turalowski, thanks for opening an issue, and sorry for the late reply! The reason you are getting this error is because we don't currently support the typescriptreact filetype, which is highlighted in #233. A lot of people have been asking for typescriptreact support, so I think it is something we will certainly do in the future, but unfortunately until someone does implement it, the plugin can't really be used with this filetype. Of course, if you would be interested in contributing to the project and implementing it, feel free to do so! I have also written a small guide on how one might approach this in #233.


Add mod_cluster management resources

Linux Build 6818 is now running using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b

Linux with security manager Build 1716 is now running using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b

Windows Build 1893 is now running using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b

Linux with security manager Build 1716 outcome was FAILURE using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b
Summary: Tests failed: 11 (11 new), passed: 844, ignored: 322 Build time: 0:05:53
Build problems:
Failed tests detected
Failed tests
org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

##### there are 1 more failed tests, see build details

Linux Build 6818 outcome was FAILURE using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b
Summary: Tests failed: 12 (12 new), passed: 2863, ignored: 392 Build time: 0:44:12
Build problems:
Failed tests detected
Failed tests
org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

##### there are 2 more failed tests, see build details

Windows Build 1893 outcome was FAILURE using a merge of cc6ad5ba76e06cebf453395ae45a0e081554470b
Summary: Tests failed: 12 (12 new), passed: 2863, ignored: 392 Build time: 0:45:35
Build problems:
Failed tests detected
Failed tests
org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testSubsystem: <no details avaliable>

##### there are 2 more failed tests, see build details

Linux with security manager Build 1720 is now running using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0

Windows Build 1897 is now running using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0

Linux Build 6822 is now running using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0

Linux with security manager Build 1720 outcome was FAILURE using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0
Summary: Tests failed: 11, passed: 844, ignored: 322 Build time: 0:06:00
Build problems:
Failed tests detected
Failed tests
org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testSubsystem: <no details avaliable>

##### there are 1 more failed tests, see build details

Windows Build 1897 outcome was FAILURE using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0
Summary: Tests failed: 12, passed: 2863, ignored: 392 Build time: 0:48:18
Build problems:
Failed tests detected
Failed tests
org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystemTestCase.testSubsystem: <no details avaliable>

##### there are 2 more failed tests, see build details

Linux Build 6822 outcome was FAILURE using a merge of 5cb3aaa47388fc9120e8c51f95525fc30163a0f0
Summary: Tests failed: 15 (3 new), passed: 2858, ignored: 392, muted: 2 Build time: 0:48:54
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.remote.distinctname.EarDeploymentDistinctNameTestCase.testRemoteSLSBInvocation: <no details avaliable>

org.jboss.as.test.integration.ejb.remote.suspend.EjbRemoteSuspendTestCase.testSuspendedCallRejected: <no details avaliable>

org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

org.wildfly.extension.undertow.UndertowDefaultConfigUpgradeTestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem11TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem12TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testRuntime: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem20TestCase.testSubsystem: <no details avaliable>

org.wildfly.extension.undertow.UndertowSubsystem10TestCase.testRuntime: <no details avaliable>

##### there are 5 more failed tests, see build details

Windows Build 1961 is now running using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b

Linux Build 6886 is now running using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b

Linux with security manager Build 1783 is now running using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b

Linux with security manager Build 1783 outcome was SUCCESS using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b
Summary: Tests passed: 855, ignored: 321 Build time: 0:06:39

Windows Build 1961 outcome was SUCCESS using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b
Summary: Tests passed: 2925, ignored: 371 Build time: 0:48:41

Linux Build 6886 outcome was SUCCESS using a merge of d3f3f86306d761f276c6e14ae08b7fbc3914f63b
Summary: Tests passed: 2925, ignored: 371 Build time: 0:51:37

Linux Build 6891 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Windows Build 1966 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Linux with security manager Build 1788 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Linux with security manager Build 1788 outcome was SUCCESS using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests passed: 864, ignored: 311 Build time: 0:05:49

Windows Build 1966 outcome was SUCCESS using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests passed: 2929, ignored: 367 Build time: 0:51:07

Linux Build 6891 outcome was FAILURE using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests failed: 2 (2 new), passed: 2926, ignored: 367, muted: 1 Build time: 0:52:28
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.undeploy.RemoveSFSBOnUndeployTestCase.testSfsbDestroyedOnUndeploy: <no details avaliable>

org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

retest this please

Linux with security manager Build 1822 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Linux Build 6925 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Windows Build 2000 is now running using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65

Linux with security manager Build 1822 outcome was SUCCESS using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests passed: 864, ignored: 311 Build time: 0:06:40

Windows Build 2000 outcome was SUCCESS using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests passed: 2910, ignored: 372 Build time: 0:49:29

Linux Build 6925 outcome was FAILURE using a merge of 1ba078c6e19e06ab96e6bef9f9e4100af1224f65
Summary: Tests failed: 1, passed: 2907, ignored: 372, muted: 2 Build time: 0:51:05
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>


Body scrolls when dialog is open

Unlike the original sweetalert, the body still scrolls when the dialog is open.  This makes me sad.  :(  Any chance this can be added?

I personally don't see what's wrong with the ability to scroll the body when a modal is shown. Can you please explain why you think it's bad?

I'm closing this issue due to inactivity, reopen with argumentation why body scrolling is bad (and without the description of your emotions :wink:) if needed.

Hi I have the same problem. The problem is that page scrolls up when swal2 dialog appears.
Imagine you have TOS page with very long text, you have to scroll down, where is Accept button. But when check box "I accept TOS conditions" is not checked, I'd like to show warning dialog. But in that moment page scrolls up and after I close dialog, I have to scroll down again to reach Accept button.
I tested it with sweetalert2 6.11.4 and the problem persists.


What data-structures should belong in std?

Fake motivation:
Associative array data structures like some skiplists, B-trees, and radix/compact prefix trees need less to no randomness to get similar speed with less memory overhead. Ignoring compression, lower memory use means:

A friend's computer needs less RAM to run my interpreter, game/emulator, or crypto client while their browser/antivirus is running too.
Less granularity is required when doing greater-than-memory computations (faster batch processes)
A higher threshold before my server/router/cache/database hits swap (etc.), ulimits, or OOM.

And there's the problems/bikesheds of hashing/collision strategies and entropy source quality that I'd prefer not to leave to a standard library.
Real motivation:
I recently learned about a better crit-bit tree called a qp trie. Some people have measured speedup over hash maps (more for writes) and much better memory usage per key. There's a few Rust ports.
Caveats:

The qp trie's efficiency is somewhat dependent on the distribution of key prefixes (worst-case is still good) and allocation approach/API. This paper's approach to a trie may help.
The author's claims about a DNS organization using it in production show similar(?) results compared to hash array tries, though.

I think we should definitely add some more data structures in general, as right now we only have the following:

ArrayList
HashMap
LinkedList

Some extra things that may be useful to include.

BTree
Cuckoo Filter/Bloom Filter
Priority Queue
Fixed Ring Buffer (embedded)

Given that the stdlib will probably be heavily revised before 1.0 we can always experiment and figure out what works now with no huge worry. It would be important to clearly document the tradeoffs for each data structure to the user if there is potential overlap.
Aside: I have read that argument on SipHash. It seemed fairly flimsy though since if you have sufficient access to read the secret key from process memory, I think you have bigger issues/considerations.

Just want to note that boost has shown that circular buffers (or fixed ring buffers) are amazingly powerful for queues and stacks providing almost vector/arrayList like speed rather than the often 10x slower deque speed that they commonly are implemented with.

Practical restriction would be to allow only fully documented data structures.
Simple types like 2D and 3D point should be added, so people are not tempted to create their own.

Simple types like 2D and 3D point should be added, so people are not tempted to create their own.

I disagree. Aren't they mostly for graphics, windows, games, and scientific computing?

@tiehuis

that argument on SipHash. It seemed fairly flimsy

I don't personally care about SipHash (except its speed), but I do care that a server using a probabilistic data structure like a hashmap has to deal with (adversarial) worst case bucket balancing etc.

@0joshuaolson1
Simple types available in standard library may result in compatible libraries. In C every graphics library (like Cairo) got their point and rectangle.  Similar mess happened with boolean type in C, and (until stdint.h) with sized integers.

Little list of what I think should be in Zig in terms of data structures;

Pt2D/Pt3D
Vec2D/Vec3D
Complex Numbers (even C has it); 'technically' a data structure
Quaternions in all their glory, while Quaternions are complex numbers (or 4 tuples if you prefer) the operations on them are often specific to Quaternions and are often around rots, especially around conversion to angles or a rot like structure for games.
non-probabilistic hashmap
queues/stacks using a circular buffer, deque is just too damn slow, like a factor of up to 100
BigInt (I guess)
Decimal is a huge one too
Matrices are beautiful too

Just felt I should add my two cents

@BraedonWooding

BigInt (I guess)

Here's is detailed tutorial (consisting of 10 parts) how to implement multiple precision arithmetic, usable even for cryptographic applications.

Here is a quick vector thing I drafted up when I had a few hrs;
https://github.com/BraedonWooding/zig/blob/Vec/std/math/vector.zig
To me 300 lines is still like a little small to completely warrant a standard library entry, however I think that the whole keep it consistent business is important :).

"What data structures should belong in std?"
IMHO none. Why? Because the idea behind Zig is to be a more ergonomic/safe C or actually a more ergonomic/safe/portable assembly. The data structures should belong to a library.
I love data structures, kd-trees R-trees and friends among others. Why not create a project outside Zig that has everything dreamed of in various modules, geometric data structures, probabilistic data structures, string processing data structures.

@fithisux: projects outside would be suspected as being abandoned or obsolete. Being part of the distribution gives some assurance that the bloody thing may actually work.

Yep. To further clarify:
Nearly anything that is generally useful, and has minimal or no OS dependencies is welcome into the stdlib pre-1.0.0. This helps act as a test bed for the language, and helps give us real APIs to get working with each other as we work on the language and standard library.
Then, when we are nearing 1.0.0 and the language is stable, we'll have a comprehensive std lib audit. Everything gets fully documented. Many APIs are removed from std. Volunteers are welcome to take ownership of the removed code in separate repositories. APIs that remain are made to be consistent with each other in naming, style, and patterns. The overarching goal here is going to be for std to be as minimal as possible, except where such minimalism would harm the community or introduce dependency issues. Everyone should be happy with the zig package manager before we do this audit.

As a language user I prefer a usable and clean standard library to a featureful and spaghettified one.  I find it unlikely that things introduced will later be removed once people depend on them as the language grows.

I find it unlikely that things introduced will later be removed once people depend on them as the language grows.

If it's difficult to update imports when an std package is moved out, that's a language/tooling problem.

First of all, you do not have control over imported packages.  I cannot force someone to update their library to stop using someone else's library which uses deprecated stdlib features.  Difficulty with deprecation is a very real problem.
As to API stability, let's not forget the impact of Rust's API stability issues on its community.
I'm not clear on your IPFS comparison.  Are you suggesting that deprecated stdlib imports should alias to remotely resolved packages at build time?

Libraries shipped with the compiler are expected to be usable.
What I'd like as the ideal solution:

stdlib contains plenty of (properly maintained) libraries.
Project explicitly specifies which libraries from stdlib it wants to use.
These selected libraries (and associated documentation and tests) will be automatically copied inside project file structure.
If a library offers optional features, then it should be possible possible to omit any such feature. When the library (and docs) is copied, this skipped feature is removed from the source code copy (and the docs).

With this the programmer won't be overloaded and would have a chance to customize stdlib code.  Proposed band-aid features like struct extensions (#1170) won't be needed.

you do not have control over imported packages.

Neither can you control which Zig versions or platforms library is written for, but they're not always crap as PavelVozenilek put it. The problems of API changes and library writers changing things are similar.

I'm not clear on your IPFS comparison. Are you suggesting that deprecated stdlib imports should alias to remotely resolved packages at build time?

I'd imagine package management can be done separately from building.


Error: Missing value for input variable input_language in LLMChain call and chain chat history not working

While following the basic Quickstart tutorial: https://js.langchain.com/docs/getting-started/guide-chat#model--prompt--llmchain
I encountered an issue with the code provided.
Code:
const { LLMChain, ConversationChain } = require("langchain/chains");
const { ChatOpenAI } = require("langchain/chat_models/openai");
const { OpenAI } = require("langchain/llms/openai");
const {
  PromptTemplate,
  SystemMessagePromptTemplate,
  HumanMessagePromptTemplate,
  ChatPromptTemplate,
} = require("langchain/prompts");

async function main() {
  const chat = new ChatOpenAI({
    temperature: 0,
    openAIApiKey: process.env.OPENAI_API_TOKEN,
  });
  const translationPrompt = ChatPromptTemplate.fromPromptMessages([
    SystemMessagePromptTemplate.fromTemplate(
      "You are a helpful assistant that translates {input_language} to {output_language}."
    ),
    HumanMessagePromptTemplate.fromTemplate("{text}"),
  ]);

  const responseA = await chat.generatePrompt([
    await translationPrompt.formatPromptValue({
      input_language: "English",
      output_language: "French",
      text: "I love programming.",
    }),
  ]);
  console.log(responseA.generations[0]);

  const chain = new LLMChain({
    prompt: translationPrompt,
    llm: chat,
  });

  const responseB = await chain.call({
    input_language: "English",
    output_language: "French",
    text: "I love programming.",
  });
  console.log(responseB);

  const responseD = await chain.call({
    input: "hi from London, how are you doing today",
  });
  // ERROR
  console.log(responseD);
});

main();

Error:
Error: Missing value for input variable `input_language`
    at /app/node_modules/langchain/dist/prompts/chat.cjs:190:27
    at Array.reduce (<anonymous>)
    at ChatPromptTemplate.formatMessages (/app/node_modules/langchain/dist/prompts/chat.cjs:188:62)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ChatPromptTemplate.formatPromptValue (/app/node_modules/langchain/dist/prompts/chat.cjs:81:32)
    at async LLMChain._call (/app/node_modules/langchain/dist/chains/llm_chain.cjs:82:29)
    at async LLMChain.call (/app/node_modules/langchain/dist/chains/base.cjs:68:28)

When I replace the input with a text/input_language/output_language object, the chain doesn't track the context.
Also, chat memory doesn't seem to be working:
  const chat = new ChatOpenAI({
    temperature: 0,
    openAIApiKey: process.env.OPENAI_API_TOKEN,
  });
  const chatPrompt = ChatPromptTemplate.fromPromptMessages([
    SystemMessagePromptTemplate.fromTemplate(
      "The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know."
    ),
    new MessagesPlaceholder("history"),
    HumanMessagePromptTemplate.fromTemplate("{input}"),
  ]);

  const chain = new ConversationChain({
    memory: new BufferMemory({ returnMessages: true, memoryKey: "history" }),
    prompt: chatPrompt,
    llm: chat,
  });

  const responseA = await chain.call({
    input: "I love programming.",
  });
  console.log(responseA);
  //   {
  //   response: "That's great to hear! Programming is a fascinating field that allows you to create and build all sorts of things using code. What kind of programming do you enjoy doing?"
  // }
  const responseB = await chain.call({
    input: "What do I love to do?",
  });
  console.log(responseB);
  // {
  //   response: "I'm sorry, I don't have enough context to know what you love to do. Could you please provide more information?"
  // }

Ref: https://js.langchain.com/docs/getting-started/guide-chat#memory-add-state-to-chains-and-agents

The code you provided does not have any significant problems. I rewrote your code and it worked for me.

  const responseD = await chain.call({     input_language: "English",     output_language: "French",     text: "hi from London, how are you doing today",   });   console.log(responseD);
2. It worked for me when I tried it with a different prompt.

How about this one? 🙇
const chatPrompt = ChatPromptTemplate.fromPromptMessages([
    SystemMessagePromptTemplate.fromTemplate(
        "The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know."
    ),
    new MessagesPlaceholder("history"),
    HumanMessagePromptTemplate.fromTemplate("{input}"),
  ]);

  const conversation_chain = new ConversationChain({
    memory: new BufferMemory({ returnMessages: true, memoryKey: "history" }),
    prompt: chatPrompt,
    llm: chat,
  });

  const responseD = await conversation_chain.call({
    input: "hi from London, how are you doing today",
  });

  console.log(responseD);
  /*
  { text: "J'adore la programmation." }
   */

  const responseE = await conversation_chain.call({
    input: "Where am I?",
  });

  console.log(responseE);
  /*
  {
  response: "As an AI language model, I don't have access to your physical location. However, you mentioned that you are from London, so I assume that you are currently in London. Is that correct?"
  }
   */


Cannot drag a node in IE8.

I am not able to drag nodes in IE8. My OS is Win7. I have tried http://jimliu.github.io/angular-ui-tree/. I have also tried adding es5-sham and es5-shim in my project. I am using angujarjs 1.2.15. Any idea?
Thanks in advance.

+1.
I have also the same issue.
I'm using  es5-sham and es5-shim, jquery-1.11.2 and AngularJS v1.2.28.
During the try to drag and drop it i receive the error: "Member not found "
Error details: {
description: "Member not found.
",
message: "Member not found.
",
name: "Error",
number: -2147352573
}
The same is on your example --> http://jimliu.github.io/angular-ui-tree/ while using ie8.
It is easy to reproduce it from ie 11 (via ie8 mode in ie Developer tools)
Thank in advance for the help, hints and fix !

+1.
I'm also having the same issue. I'm using IE8 and the latest es5-shim. I'm encountering member not found in e.preventDefault() of dragStart, dragMove and dragEnd.
Any solution or hints for this one? I'd really appreciate if you have one.

if you comment e.preventDefault() at line 627 it works.

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.
Also Windows no longer supports IE8


Additional help added to Vite Basics tutorial

Added some extra instructions for vanilla JS users for my Vite guide on the docs!

I am not sure how much these changes are needed? The code is technically the same, but without types. The other changes are cosmetic.
A short sentence stating that JavaScript users will need to remove the types would be enough, no? Or am I missing something?

@RaananW The original tutorial was written for very new programmers who are only familiar with coding the Start Your Journey chapters in the Playground, and don't know how to move that knowledge into an IDE or code editor. I then had someone approach me who's been learning JavaScript for the first time by learning Babylon (who wanted a non-TS version of this documentation,) so putting an entire JS version of the code here also doubles as a way to show those readers that TS is not very different from JS.
Let me know if you still want me to condense this into simpler instructions though! I can do that if you still want me to

This will be a very confusing tutorial for someone who is just getting starting with JavaScript. It's not that i mind having it, i just think the way it's presented it's not helping as it should. If you are providing a JavaScript tutorial, do it fully. Otherwise newcomers will be lost. "Do this step, but if you are using JavaScript do what's in the parenthesis, except for step 9, which you  should copy from down below".
Just my two cents, to be honest. If you say that you think this is the right way to go I'll approve it and merge it.

Fair point, would it be better if I just link to the forum post with all the differing instructions for JavaScript users? It would be cleaner than trying to implement them directly into the same page as the TypeScript instructions like I tried to do here


Looping hat

Would it fit this sheeptester's utilities?

This is already in https://github.com/TurboWarp/extensions/pull/639

extension doesnt load?

Superseded by https://github.com/TurboWarp/extensions/pull/639


[BUG] Current buffer closes with preview if the preview and parent buffer are the same file

Describe the bug
If I preview the definition of something that is defined in the same file, and then close the preview, and then navigate to another buffer, the original buffer I was editing closes and no longer shows up in :ls
All key mappings are assuming the defaults.
To Reproduce
Steps to reproduce the behaviour:
In a file that both defines a new object and refers to that defined object:

With the cursor over the referrer, preview the definition with gpd
Close the preview with gP
2a. Note at this stage that :ls still shows the parent buffer.
Navigate away from the current buffer with :bn (or any other way you like)
:ls no longer shows the buffer, :bp and <C-^> cant return to it, the latter displaying "E23: No alternate file`

Expected behavior
The buffer I was editing/previewing from would still exist and be navigable to with <C-^>.
Baseline (please complete the following information):

OS: macOS Monterey (M1)
Neovim version: 0.7.0

Hey @MJB47 thanks for the issue submission. This line is likely the culprit. https://github.com/rmagatti/goto-preview/blob/37116fb5167d2a93cada8db9135c5032a25348a7/lua/goto-preview/lib.lua#L130
It's setting bufhidden to wipe for the buffer. So when you leave it it wipes that buffer from the buffer list.
I'll have to think about how to solve this

closed with the merging of the above


HTA08.v02.A04.Science_mouse_total

Collection/dataset this task is for:
A cell atlas of human thymic development defines T cell repertoire formation

file name - HTA08.v02.A04.Science_mouse_total
link to existing collection in cellxgene
ticket link to DCP wrangling ticket (if available)
link to ingest UI: https://contribute.data.humancellatlas.org/projects/detail?uuid=c1810dbc-16d2-45c3-b45e-3e675f88d87b

Relevant People

Wrangler
Contributor
dev

Primary Wrangler:
Associated files

SOP
Knowledge Sharing Drive
Ingest-cellxgene-submitter
Cellxgene-schema
Cellxgene-schema-validate
Cellxgene-submit-collection

Published study links

Paper:

Accessioned data:

Key Events

[ ] Collect necessary matrix, cell-type annotation, and embedding files
[ ] Modified var layer to meet cellxgene schema (adding feature_is_filtered)
[ ] Created/Modified raw.var to meet cellxgene schema
[ ] Modified obs layer to meet cellxgene schema
[ ] Created uns layer to meet cellxgene schema
[ ] Ensured obsm layer is present
[ ] Created h5ad with processed component parts using AnnData
[ ] Created h5ad with raw matrix and raw var using AnnData
[ ] Filtered ENSEMBL IDs from annotated and raw matrix
[ ] Combined processed and raw h5ad to one h5ad object
[ ] Run cellxgene-schema validate
[ ] Secondary review (?)
[ ] Submitted to collection in cellxgene

Stalled. Due to not having raw matrices for mice donors. Will contact authors.

This can be closed. I don't think we will ever do this.


[Bug]: Deleting account in german

What happened?
If you switch your account to german and try to delete your account the delete process doesn't accept the word LÖSCHEN for some reason and you are not able to delete your account.
Switching the language to english allows you to delete your account.
I guess the Ö is the issue somewhere
Steps to Reproduce

Login to your account in the webfrontend
Switch the language to german
follow the instructions under account to delete the account

What browsers are you seeing the problem on?
Firefox, Chrome, Safari
Relevant log output
No response
Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thank you for reporting this. While I believe users should type "DELETE" regardless of their language, I understand the need for a more inclusive solution. I'll work on addressing this issue and test it with several Latin-based languages as well as Chinese.
If anyone encounters a similar problem with a language not mentioned above, please let us know in this thread

Yes, DELETE works, and changing the language to french and spanish asks to type DELETE.

@berry-13 in my opinion, I think it's enough to write your email, this reduces the complexity and the discrepancy in languages.

and perhaps to keep a "second step" we can make sure the button requires 2 clicks, with a "confirm" step saying "are you sure?"

I think a confirm step like you suggested would be easier.

fixed in #4438


Add Jackson RC to Version Matrix

Description
Add Jackson RC to the Jackson version validation matrix.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - core


Add xz support to import-db, import-files, maybe export-db

Is your feature request related to a problem? Please describe.
xz is a very good compressor, which is being used more and more everyday. The linux kernel project releases in xz, by default, for example.
Describe the solution you'd like
Include support of xz compressed files for the commands 'import-db' and 'import-files'.
Describe alternatives you've considered
Currently gzip and tar are supported, so these can be used.
Additional context
So ideally I could import-db files compressed with xz (*.sql.xz) and import-files also compressed with xz (tar.xz).

For mysql, you should know that the mysq,, export-db and import-db commands accept stdin/stdout, so it's super easy to do the traditional thing:
xz -dc file.sql.xz | ddev mysql db
xz -dc file.sql.xz | ddev import-db
ddev export-db --gzip=false | xz >db.sql.xz
ddev exec mysqldump db | xz >db.sql.xz

However, I can see how this would be really great for import-db, if you use xz for compression and get the tarball down. Just recognizing .xz out of the box would be really nice.

I imagine we can do this someday, but in a year of the issue being open there hasn't been a "me too" added here. Happy to reopen in the future.


fix: use conflict-http code (409) instead of 500

fix: use conflict-http code (409) instead of 500
Description
Instead of using 500 http code which is for internal server code , we should now use 409 http code , which is for conflict

[ ] This change requires a documentation update
[ ] I have made corresponding changes to the documentation

Related Issue(s)
closes #1391
Screenshots
Notes
Please add any relevant notes if necessary.

@quest-bot loot #1391

@Ansh-Grover I can see that you're back with another account.
As before, the code you submitted isn't tested with the requirements of the issue.
Closing this PR which will be solved by @RS-labhub.

here now it shows 409

Yes, and it will show 409 on every other server error as well.

why are you obsessed with me ? , cool down


Add method to purge cells

From #259:
For FEM it's useful to be able to delete cells. Add a method to purge cells based on some expression related to cell data.
I.e. refactor this snipped from the sfepy horse example:
triangles = nanomesh_mesh.get('triangle')
idx = triangles.cell_data['physical'] != 2
triangles.cell_data['physical'] = triangles.cell_data['physical'][idx]
triangles.cells = triangles.cells[idx]

to something like:
triangles.purge(key='physical', func='lambda v: v!=2)

Can be both on instances of Mesh / MeshContainer.

Closed by #259


Create docs for https://github.com/babel/babili

Given https://github.com/babel/babel.github.io/pull/995 (curated plugin list) and https://github.com/babel/babel.github.io/pull/990 (readme from repos), we should render the readme's for babel-minify on the website!
cc @kangax @boopathi

https://github.com/babel/babel.github.io/pull/1004 is merged
If you want to include the readme from the monorepo you can do {% include package_readme.html from="babili" %}
Now we'll want to create a separate main page for babili

Moving over the already created plugin pages to use the README from babili
by adding
{% include package_readme.html from="babili" %}

[ ] babel-plugin-transform-inline-environment-variables
[ ] babel-plugin-transform-member-expression-literals
[ ] babel-plugin-transform-merge-sibling-variables
[x] babel-plugin-transform-minify-booleans
[ ] babel-plugin-transform-node-env-inline
[ ] babel-plugin-transform-property-literals
[ ] babel-plugin-transform-remove-console
[ ] babel-plugin-transform-remove-debugger
[ ] babel-plugin-transform-simplify-comparison-operators
[ ] babel-plugin-transform-undefined-to-void

Will also want to add the new plugins not listed ^

This is all done in https://github.com/babel/babel.github.io/pull/1029? @geordidearns
You can add a Fixes #999 in your commit or description of the PR to make this close when your PR is merged

Yep, I believe this is finished!


Output not displayed in the UI even if the build is failed

Hi,
I had successfully created a project and am trying to run a build.The build runs but am getting an error in the integrity.log file but the interesting part is in UI the output is not displayed
Following is the error:
D, [2011-01-06T16:46:00.410304 #18046] DEBUG -- : (cd builds/13 && git fetch origin 2>&1)
D, [2011-01-06T16:46:06.161570 #18046] DEBUG -- : (cd builds/13 && git checkout origin/master 2>&1)
D, [2011-01-06T16:46:06.530607 #18046] DEBUG -- : (cd builds/13 && git reset --hard 4e24aaf1f60a6461bb04929fed7dd542e5d4937b 2>&1)
I, [2011-01-06T16:46:07.096314 #18046]  INFO -- : (cd builds/13 && RUBYOPT=-I/usr/lib/ruby/gems/1.8/gems/bundler-1.0.7/lib -rbundler/setup PATH=/usr/lib/ruby/gems/1.8/bin:/var/lib/gems/1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games && rake 2>&1)
I, [2011-01-06T16:46:07.103039 #18046]  INFO -- : Build 4e24aaf1f60a6461bb04929fed7dd542e5d4937b exited with false got:
Please suggest where i am going wrong

richmeyers resolved this in pull request #131.


Fix the way content is distributed for SurfaceGroupsPage.html

An alternative way to https://github.com/StarcounterApps/Website/pull/171

Changes:

Fixes flaky auto- slot name assignment for dynamically created elements, (but this time by..)
Adds explicit slot elements and attributes - makes code more self-explanatory,
Allows blending individual surface groups, for example displaying them in CSS Grid,
Hides styling related elements
 in Shadow DOM.
Moves local styles to the Shadow DOM,
Does not relly on problemativc bootstrap to style
.

Sorry, I didn't know that was the intention, do you think CSS styling would be good enough replacemen, or do you really need
 element there for some reason?

I just think that those hr lines make it more readable and looks nice. But if You'll show comparatively good solution, I'm open for it!

Here is my proposition:

Howeve, I still wigth with a V0 polyfill bug.

This looks awesome! As soon as You deal with this polyfill bug I definitely want to try this out! Make sure that adding more than 3-4 surfaces to group won't break anything.

Here you have the results. it even looks more-or-less good in IE with flex instead of grid.
Fix for ::content support will follow in<EMAIL_ADDRESS>@warpech do you think it's worth making the fix for pre 3.0.0 version? (in juicy-composition)

Wow, looks really good! (and complex) But the view in Edge, FF and Chrome are all different. I'm not sure if we should do this in that way, where We have sightly different views on all browsers.

the view in Edge, FF and Chrome are all different

That's why the fix for starcounter-include is needed.

@warpech do you think it's worth making the fix for pre 3.0.0 version? (in juicy-composition)

No, unless you think that it is many days until 3.0.0 can be released in Starcounter?

I have some proposition, let's for now, reopen and merge https://github.com/StarcounterApps/Website/pull/171 as a fix for discovered issue, and let's consider this as an improvement/enchantment/update of SurfaceGroups view, since this got much further than just fixing an issue. Then I'll release fixed version, and this visual changes will come with next release. Can We do it this way?

@PatrykSzwer as fixes are now merged to <IP_ADDRESS>22, should we come back to this one?

Actually, as I've heard there will be meeting about Interface of website this week. I think We can hold It till then, and we will see what will came up there.

Are there any updates on the new design?

Turns out that we Didn't discussed yet design itself of app, more like data model and general structure.

@tomalec the app will be redesigned anyway, so we'd rather not merge this change unless it contains crucial changes. Is there something crucial in it?

Nothing that fixes functionality, but it

removes
 from light DOM, meaningful, functional elements (bad practise). So it will not end up copy and pasted in other apps
showcases one way how to use slot attribute with dom-repeat to gather a group of dynamically created elements together,
showcases how to use CSS Grid Layout,
showcases hot to use polyfill-next-selector

If we have such examples somewhere else, I'm fine with disregarding this one.

removes
 from light DOM, meaningful, functional elements (bad practise). So it will not end up copy and pasted in other apps

I have created an issue for that: https://github.com/StarcounterApps/Website/issues/207

showcases one way how to use slot attribute with dom-repeat to gather a group of dynamically created elements together

Examples should be in KitchenSink. I have created an issue for that: https://github.com/StarcounterApps/KitchenSink/issues/169

showcases how to use CSS Grid Layout,

I have created an issue for that: https://github.com/StarcounterApps/KitchenSink/issues/170

showcases hot to use polyfill-next-selector

I have created an issue for that: https://github.com/StarcounterApps/KitchenSink/issues/171

Closing this as too complex. Thank's a lot @tomalec anyway. Please proceed with separate issues linked above.


[HxAutosuggest] Tweaks to be able to use it as searchable select

Could you add a searchable select component to your collection (e.g. https://github.com/Blazored/Typeahead)?
It's the only missing component for CRM apps (e.g. for selecting a client in a form).

Hello @Apskaita5,
please take a look at HxAutosuggest (https://havit.blazor.eu/components/HxAutosuggest). It is designed to cover those scenarios.
Can you please add more information on what specific features are you missing?

Blazored/Typeahead component allows for both selecting from a list and search. HxAutosuggest only allows search, not selection from a list. HxSelect allows selection from a list, not search.

If you set MinimumLength="0" and Delay="1" (this is something we want to change to allow 0) you should get a selection from list (see similar demo for HxInputTags https://havit.blazor.eu/components/HxInputTags#StaticSuggestions).
Is that what you need?

That would be great except for two details:

the dropdown doesn't have it's own scrollbar, which is a problem for long lists (just try it with your example, it has item collection big enough to demonstrate graphical result);
the dropdown does not appear on focus when a value is already selected, which could be misleading for an end user.

;)

@Apskaita5 Got it.
There are some additional tweaks needed to be able to use HxAutosuggest as searchable select.
This is valid usage scenario and we will make the adjustments needed.
If you find any additional issues, please let us know.
cc @crdo @jirikanda

@Apskaita5 In the discussion we had today with the team, we decided to stick with the current behavior regarding the "dropdown does not appear on focus when a value is already selected" request. The referenced Typeahead component also does not open (it has a separate caret to open the dropdown).
We might reconsider the decision later, but for now, we think the current UX is better for most scenarios.


cannot execute binary file: Exec format error

OS: Gentoo Linux x86_64
Every time I tried to use the pho self-update command I had to reinstall the app manually for it to work. When I try to use it after the self-update command it always returns exec format error: pho

I installed pho in /usr/local/bin/

/usr/local/bin/pho: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=26NlcqdFZ9mApeKpmB-f/d-l02CSX6rLjYsxdAoWB/7_rg8S42IpWCT9pRcU8k/b1jqWN2VIeqdEUDWyRZi, stripped

Also this is an unrelated issue, but when I try to install a new appimage the command in the .desktop file is only the name of the executable file without the location. Because of that the desktop shortcuts no longer work and I need to update each one individually.

[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=OpenRGB
Comment=Control RGB lighting
Exec=OpenRGB
Terminal=false
Categories=Utility;
Icon=/home/pescu/Applications/openrgb/Openrgb.png

 /usr/local/bin/pho: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=a015ChDlJzjX4SgXymta/9mIIXSCMosz3GxC_U_U4/QZeKR2qXouxgMNQPxZU7/bOoKXpYn9A4k9UtSH95k, stripped
It looks like the self updater is downloading the arm version of the app

That's a weird issue, the update was bugged in old versions. Let me know if that happens with next update.

Seems like that .desktop file embedded within the AppImage did not use AppRun. Should have replaced if it was using that. I'll have to fix this.

The same apps worked before updating from version 0.4 directly to 0.9.

Seems like that .desktop file embedded within the AppImage did not use AppRun. Should have replaced if it was using that. I'll have to fix this.

The same apps worked before updating from version 0.4 directly to 0.9.

Has been fixed in https://github.com/zyrouge/pho/commit/f389502c9f613d9a5178c9f1d5c01dfd844419cb.

Feel free to create a new issue if you find any bugs.


Content of dockerfile gets out of sync with actual file after an edit

Editor sends a textDocument/didChange message with this payload:
{
  "contentChanges": [
    {
      "range": {
        "end": {
          "character": 21,
          "line": 48
        },
        "start": {
          "character": 21,
          "line": 48
        }
      },
      "rangeLength": 0,
      "text": "\n"
    },
    {
      "range": {
        "end": {
          "character": 0,
          "line": 49
        },
        "start": {
          "character": 0,
          "line": 49
        }
      },
      "rangeLength": 0,
      "text": "W"
    },
    {
      "range": {
        "end": {
          "character": 1,
          "line": 49
        },
        "start": {
          "character": 1,
          "line": 49
        }
      },
      "rangeLength": 0,
      "text": "O"
    },
    {
      "range": {
        "end": {
          "character": 2,
          "line": 49
        },
        "start": {
          "character": 2,
          "line": 49
        }
      },
      "rangeLength": 0,
      "text": "R"
    },
    {
      "range": {
        "end": {
          "character": 3,
          "line": 49
        },
        "start": {
          "character": 3,
          "line": 49
        }
      },
      "rangeLength": 0,
      "text": "K"
    }
  ],
  "textDocument": {
    "uri": "file:///Users/me/workspace/test/Dockerfile",
    "version": 5
  }
}

which triggers this error diagnostic through textDocument/publishDiagnostics notification:
{
  "diagnostics": [
    {
      "code": 38,
      "message": "Unknown instruction: WKRO",
      "range": {
        "end": {
          "character": 4,
          "line": 49
        },
        "start": {
          "character": 0,
          "line": 49
        }
      },
      "severity": 1,
      "source": "dockerfile-utils"
    }
  ],
  "uri": "file:///Users/me/workspace/test/Dockerfile"
}

So it appears that language server doesn't process changes correctly, resulting in content getting out of sync with actual file.

@rchl Thank you for your bug report. Were you typing at the end of the Dockerfile?

No, roughly in the middle. It also reproduces in empty file if I just type "WORK".
I suppose other editors might report edits differently (maybe collapse all edits into one) so might need to trigger such payload manually to reproduce.

No, roughly in the middle. It also reproduces in empty file if I just type "WORK".

@rchl OK, thanks. I can see it happening at the end of a file (which is the same as an empty file) and I've also been able to reproduce it in the middle of the file.

@rchl I've released a 0.1.1 which should help with this...?

Yes, that fix looks good. Thanks.

Yes, that fix looks good. Thanks.

@rchl Thanks for checking!


Upload artifacts to share them between workflows

Storing workflow data as artifacts - GitHub Docs

Let's try.


Bug: Missing navbar in Login page

The missing navbar in the login page affects the user experience

Add Screenshots

Steps To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'

The current behavior

The expected behavior

@subhadipbhowmik Please assign this task to me under gssoc24.

task is still not done.
@subhadipbhowmik, Please assign me I will do it ASAP


Uncaught 503 exception when Google OAuth is down

1. Which version of kreait/firebase-php are you using?
2.3.1
2. Which version of PHP are you using?
7.0.16
3. What's the issue?
In the rare cases when the Google OAuth service is down I believe the APIException class should handle this error.
 PHP Fatal error:  Uncaught GuzzleHttp\Exception\ServerException: Server error: `POST https://www.googleapis.com/oauth2/v4/token` resulted in a `503 Service Unavailable` response:
 {
  "error": "internal_failure",
  "error_description": "Backend Error"
 }

Looking at the list of handled Fig status this should be possible by adding a check for this value:
const STATUS_SERVICE_UNAVAILABLE = 503;
As even on master this does not appear to be handled: https://github.com/kreait/firebase-php/blob/672c2708c851c14340f37422390c48edf85f0d54/src/Firebase/Exception/ApiException.php#L38
4. Code that lead to the issue
This is just an unhandled exception in APIException.php. My version of the library was outdated, but the latest code still should support 503 errors.

Hey @x1nixmzeng! Thank you for taking the time to report this issue, you are right, the library should handle server errors! I will add support for that in the upcoming release!

@x1nixmzeng I believe this is not handled by an ApiException, but by the AuthException, but I am not sure. Can you please attach a full stack trace of the error, or a code example that led to the error? Looking at the code, any errors should be handled by ApiException or AuthException, but I can't test this at the moment.

Hello, sorry for the delay - is is the stack trace from the logs:
PHP Fatal error:  Uncaught GuzzleHttp\Exception\ServerException: Server error: `POST https://www.googleapis.com/oauth2/v4/token` resulted in a `503 Service Unavailable` response:
{
 "error": "internal_failure",
 "error_description": "Backend Error"
}

Stack trace:
 in /app/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
#0 /app/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 /app/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 /app/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), Array)
#3 /app/vendor/guzzlehttp/promises/src/TaskQueue.php(47): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}()
#4 /app/vendor/guzzlehttp/promises/src/Promise.php(246): GuzzleHttp\Promise\TaskQueue->run(true)
#5 /app/vendor/guzzlehttp/promises/src/Promi in /app/vendor/kreait/firebase-php/src/Firebase/Exception/ApiException.php on line 28

I also have another error in my logs which points to the server response returning HTML rather than JSON.
PHP Fatal error:  Uncaught Firebase\Exception\InvalidArgumentException: json_decode error: Syntax error in /app/vendor/kreait/firebase-php/src/Firebase/Util/JSON.php:55
Stack trace:
#0 /app/vendor/kreait/firebase-php/src/Firebase/Exception/ApiException.php(21): Firebase\Util\JSON::decode('<!DOCTYPE html>...', true)
#1 /app/vendor/kreait/firebase-php/src/Firebase/Database/ApiClient.php(78): Firebase\Exception\ApiException::wrapThrowable(Object(GuzzleHttp\Exception\ServerException))
#2 /app/vendor/kreait/firebase-php/src/Firebase/Database/ApiClient.php(70): Firebase\Database\ApiClient->request('PATCH', Object(GuzzleHttp\Psr7\Uri), Array)
#3 /app/vendor/kreait/firebase-php/src/Firebase/Database/Reference.php(389): Firebase\Database\ApiClient->update(Object(GuzzleHttp\Psr7\Uri), Array)
#4 /app/[redacted].php(569): Firebase\Database\Reference->update(Array)
#5 /app/[redacted].php(108): [redacted]->[method](Array)
#6 {main}
  thrown in /app/vendor/kreait/firebase-php/src/Firebase/Util/JSON.php on line 55

@x1nixmzeng When you update to Release 3.5.0 (out now \o/), could you please try again and see if things get better? The library should now be able to handle non-JSON responses better.

Closing this now, but feel free to add further comments or to open a new issue if the problem persists.

I'm am still getting sparodic errors on 3.5.0 with Firebase, but the JSON response errors are gone.
Here are the callstacks. At the moment I am adding further logging to my app to see if I can catch the issue.
PHP Fatal error:  Uncaught GuzzleHttp\Exception\ServerException: Server error: `POST https://www.googleapis.com/oauth2/v4/token` resulted in a `503 Service Unavailable` response:
{
 "error": "internal_failure",
"error_description": "Backend Error"
}

in /app/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Stack trace:
#0 /app/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 /app/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#3 /app/vendor/guzzlehttp/promises/src/TaskQueue.php(47): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}()
#4 /app/vendor/guzzlehttp/promises/src/Promise.php(246): GuzzleHttp\Promise\TaskQueue->run(true)
#2 /app/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promise\Promise::callHandler(1, Object(GuzzleHttp\Psr7\Response), Array)
#5 /app/vendor/guzzlehttp/promises/src/Promi in /app/vendor/kreait/firebase-php/src/Firebase/Exception/ApiException.php on line 50

And
PHP Fatal error:  Uncaught GuzzleHttp\Exception\ConnectException: cURL error 52: Empty reply from server (see http://curl.haxx.se/libcurl/c/libcurl-errors.html) in /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php:186
Stack trace:
#3 /app/vendor/guzzlehttp/guzzle/src/Handler/Proxy.php(28): GuzzleHttp\Handler\CurlHandler->__invoke(Object(GuzzleHttp\Psr7\Request), Array)
#0 /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(150): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array)
#1 /app/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php(103): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#2 /app/vendor/guzzlehttp/guzzle/src/Handler/CurlHandler.php(43): GuzzleHttp\Handler\CurlFactory::finish(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory))
#4 /app/vendor/guzzlehttp/guzzle/src/Handler/Pr in /app/vendor/kreait/firebase-php/src/Firebase/Exception/ApiException.php on line 50

Did you get some changes about this error ?
I have the same one right now without clue to fix it


Set FFC_PARAM_FLAG_VALIDATE_LEGACY on params generated with FIPS 186-2

Fixes #16261

There is a testcase that needs to be fixed that should cover this..
See dsatest.c dsa_test().
DSA_generate_key() and DSA_Sign() both fail but dont check the return value.
DSA_verify is also wrong since in returns -1 and then passes on the TEST_true()

The dsatest needs to be fixed to cover this..
The default dhtest is already working since it uses a generator with no q (so it does not do the simple_validate check).

Test fixed. I've verified it properly detects the issue if I revert the fix.

This pull request is ready to merge

Merged to master. Thank you for the reviews.


Lambda function invoked many times.

This started happening recently, when I was making some code changes so I though it must be my fault. I rolled back those edits and restarted npx sst dev but and even on the first invokation this happens.
When you invoke 1 lambda function once during dev, it appears to be invoked many time by the hot-relead runner. See attached screen shot.

Not sure what is going on, or even if it is a problem! Since one of the invokations seems to run and provide the expected response. Just looks weird that this happens and happens for no apparent reason.

https://github.com/sst/sst/issues/5173
Around the same time I got the above I had this "https://github.com/sst/sst/issues/5173" message.
After that it started running normally with one message per invokation. Seems like there were some dangling threads somehow? Possibly in the Lambda runner on the AWS side, since I had killed sst dev in between invokations and was still seeing the message. I would guess some unhandled exception left things into limbo in the Lambda dev runner.

I'll close this issue then. Let's look at the other one.

I cannot re-open or I would.
This happens a lot, I would say on most sst dev session. It will start with 1 Invoke per call, and then gradually increase over time to 2, 3, ... Usually I will have killed sst dev and started another session about then, but if you keep going, the Invokes per actual call only increases.

I will upgrade to latest and re-try it. If its still a problem, I will open a new issue for it.


Can't get into discord server

Describe the bug
Tried to get into the discord server from the links on the Table and Query pages. Nothing goes.
Your minimal, reproducible example
N/A
Steps to reproduce

Go here: https://tanstack.com/query/v4
Click "Discord"
"Accept Invite"

Expected behavior
It's just a bad link/invite code right?
How often does this bug happen?
Every time
Screenshots or Videos
This is after trying to accept the invite:

Platform

Mac and chrome

react-table version

v8

TypeScript version
N/A
Additional context
That should be enough?
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Huh. Thanks for the trouble I'll do that.

Here's the response from Discord:
Care to check if you've banned my IP address? <IP_ADDRESS>

If it is still you are unable to accept the invite, it's likely that your IP address is banned from the server. Could you ask one of the moderators to clear all bans in Server Settings > Bans? Restart the client afterward. Keep in mind that if you have an IP address that was used at any point by a user who was banned, you might be banned because of that.
Also, if you were a member of the server in the past, it is possible that a "ghost" version of your account is still a member. This will prevent you from joining again. Have the mods check their user list to make sure your Discord Tag isn't on it. If it is, and you're not in the server, it could be that you weren't fully kicked originally. Once your "ghost" is kicked, you should be able to join again.
Another option is that a moderation bot has your Discord Tag on its blacklist. You can ask the mods to check each bot's blacklist to ensure that your Discord Tag is not on it.
Next, please try to join a server by only using mobile data on your mobile device to see if the link will show as invalid again.
Lastly, please restart your router and try to temporarily disable your firewall on your PC, and then try to join the server again on your desktop client.
Just a friendly reminder, make sure that you're disconnected from any VPN.


Allow builders options for envify, to exclude files during build_runner

envify should most of the time only need to generate one file, but it tries to run on every file ,
(for example if your using json_serializable in the same project)

Output
...
[INFO] Heartbeat:6.6s elapsed, 17/26 actions completed.
[FINE] envify_generator:envify on lib/utils/union.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/build_information.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/azure_subscription.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/destination.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/basic_release_details.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/owner.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/app.dart:Running EnvifyGenerator
[FINE] envify_generator:envify on lib/api/model/release_details.dart:Running EnvifyGenerator
[INFO] Heartbeat:12.3s elapsed, 25/26 actions completed.
[FINE] envify_generator:envify on lib/state/app_state.dart:Running EnvifyGenerator

While checking and comparing with other builder packages I saw that it is possible to set options in build.yaml so I tried it also with envify like so:

build.yaml
targets:
  $default:
    builders:
      json_serializable:
        enabled: true
        generate_for:
          exclude:
            - lib
          include:
            - lib/api/model/*
            - lib/state/app_state.dart
        options:
          explicit_to_json: true
      envify:
        enabled: true
        generate_for:
          exclude:
            - lib
          include:
            - lib/utils/env.dart

But this only shows the following Warning, and still tries to run envify generator over every file.
pub run build_runner build --delete-conflicting-outputs --verbose
[INFO] Entrypoint:Generating build script...
[INFO] Entrypoint:Generating build script completed, took 631ms
[INFO] Bootstrap:Precompiling build script......
[INFO] Bootstrap:Precompiling build script... completed, took 4.7s
[WARNING] ApplyBuilders:
Configuring `envify:envify` in target `exampler:example` but this is not a known Builder

I'm pretty sure dart's analyzer will try to scan all those files. It is in fact a usual behavior with all the generators such as json_seriazable, ... etc.
But what you stated also makes sense, so I'll try to optimize it so that it only scan env.dart files (or possibly allow the user to exclude files). Thanks for taking the time to file this issue.


Does CAT work with 10.10.5 public as released on Aug 13?

Can someone please tell me if CAT has been found to work with 10.10.5 public? I have it working on 10.10.3 on a MBP early 2011 15" using the CAX implant and sure do not want to lost it.  Thank you

No, it does not. Tried 10.10.5 update on MBPro, Mac Pro - both worked fine with CAT 2.0.0 and 2.0.1 up until 10.10.4, no longer working after 10.10.5

Does it works with dongles?

I do not know, but it fails at the dongle detection stage that it never completes. I do not have a dongle.

On Aug 13, 2015, at 11:22 PM, mobile4<EMAIL_ADDRESS>wrote:
Does it works with dongles?
—
Reply to this email directly or view it on GitHub.

VERY disappointing.  So now we need to find out if Apple made the same "change" to 10.10.5 that they did in 10.11.  Perhaps if the CAT team can get CAT working for 10.11 that version will also work for 10.10.5?

CAT Worked great for me after updating to 10.10.5.  I'm running on a MBP (early 2011) 15" with transplanted CAX, BT/WiFi.  Screenshot attached with continuity working perfectly.

Brian.  Thank you very much.  Sounds like your computer is very similar to mine.  ??? did you just reinstall the same CAT 2.00 again after the upgrade to 10.10.5, or did you have to use the newest version (2.1?) that they are using with El Cap?

Not sure how you got it to work. Tried a clean install on bit the machines I mentioned, various versions of CAT, and none proceed beyond the detection of BT dongles in 10.10.5.

@TomHTX: I downloaded and ran the latest master build: https://github.com/dokterdok/Continuity-Activation-Tool/archive/master.zip.  I did not use the beta build...although, that might have worked, too.  @ebernet: I upgraded the built-in bluetooth card from the BCM94331PCIEBT4 to BCM94331PCIEBT4CAX.  I'm not using an external dongle.  I believe the CAX version has BT 4.0 and the no CAX version does not.  I also believe that that the CAX version was released with the 2012 MBP 15".  Again, I am running on an early 2011 15" model.  If I recall, I was prompted to insert a BT dongle while running CAT.  However, I'm not, so I chose to ignore or skip the dongle detection.  I hope that helps.

Master build - check
updated to the same internal BT - check
My model is the late 2011 MBPro rather than the early 2011
My Mac Pro -2008, with the BT 4.0/Wifi AC card
Again, both machines have been working fine with CAT since 10.0.0, both 1.1 and then 2.0.0. After upgrading to 10.10.5, both fail at the same spot (BT dongle detection). I am not using a dongle nor have one installed. Do not know how it is working for you, but everything I tried fails for me.

On Aug 16, 2015, at 8:37 PM, Brian Vermilyea<EMAIL_ADDRESS>wrote:
@TomHTX https://github.com/TomHTX: I downloaded and ran the latest master build: https://github.com/dokterdok/Continuity-Activation-Tool/archive/master.zip https://github.com/dokterdok/Continuity-Activation-Tool/archive/master.zip. I did not use the beta build...although, that might have worked, too. @ebernet https://github.com/ebernet: I upgraded the built-in bluetooth card from the BCM94331PCIEBT4 to BCM94331PCIEBT4CAX. I'm not using an external dongle. I believe the CAX version has BT 4.0 and the no CAX version does not. I also believe that that the CAX version was released with the 2012 MBP 15". Again, I am running on an early 2011 15" model. If I recall, I was prompted to insert a BT dongle while running CAT. However, I'm not, so I chose to ignore or skip the dongle detection. I hope that helps.
—
Reply to this email directly or view it on GitHub https://github.com/dokterdok/Continuity-Activation-Tool/issues/201#issuecomment-131671049.

Also, for what it's worth, the link to zipped file in my previous post contains files last modified on 8/13/15.  That's newer than the modified date of the beta zip, which is 8/10/15.

@ebernet: Sorry, I'm not sure why it's not working for you.  Were you prompted to skip (or something like that) the dongle detection?  I know I was prompted for something like that while I was running CAT.

Yes, I am prompted to insert dongle and hit any key or hit any key to proceed without dongle. I do and I just get a flashing terminal window title trying various things. Have tried many times, even with latest master.zip with August 13 dates. Is really no one else having this problem?
And again, these are two different computers with different hardware that had no issues until 10.10.5

On Aug 16, 2015, at 8:45 PM, Brian Vermilyea<EMAIL_ADDRESS>wrote:
@ebernet https://github.com/ebernet: Sorry, I'm not sure why it's not working for you. Were you prompted to skip (or something like that) the dongle detection? I know I was prompted for something like that while I was running CAT.
—
Reply to this email directly or view it on GitHub https://github.com/dokterdok/Continuity-Activation-Tool/issues/201#issuecomment-131672016.

Is there a way to run CAT in a verbose mode so as I can see what is going on?

Someone on the Macrumors forums patched it to get it working. http://forums.macrumors.com/threads/modded-continuity-activation-tool-btle-cards-with-el-capitan-is-working.1890715/page-2. I'm not sure what changes were made, though.

That's El Capitan. I have seen no mention of the issues with 10.0.5 other than my own. I have tried a clean install of 10.0.5 on both machines, but still to no avail. Is really no one else seeing this?

Well, I used that version to install on my 11" mid-2011 MacBook Air on 10.10.5, so I know that it works for that configuration at least.

Updated to 10.10.5. Using Gmyle dongle with btoadcom chipset. Macbook Pro 2010. Works perfect.
Steps I did:

Unistall CAT. Remove dongle. Reboot.
Install 10.10.5 update.
Insert dongle
install CAT

I can't be the only one with this problem... I reformatted my HD, installed a clean 10.0.5 from recovery partition after formatting, and tried - same issue. Please please, I've been asking for 3+ weeks about this, has anyone else found a solution or seen this?

Have you tried hitting any other key than the space key when the dongle detection screen is displayed? Cf. issues #106  , #95

You GOT to be freakin' kidding me.... that is EXACTLY what it was. Can't believe that:
a. This has not been fixed
b. That is took 3+ weeks for anyone to mention this as an issue.
At least fix it so that prompt says clearly to hit any key OTHER than the spacebar.... That should only take a minute....

It worked!!!!  So, after watching cautiously for comments by others, and being very careful to avoid the "spacebar" issue, I went ahead and updated to 10.10.5 this morning, and then immediately ran the latest master dated 8/13/15.  I am pleased to report that it did work, and that continuity and handoff seem to be working on my 2011 MBP 15 with the surgically implanted CAX card.  THANKS to dokterkok and to all who have contributed to this project, and to this thread.  Tom


refactor(polyclinic): migrate to clean architecture

Tests

[x] Create Polyclinic
[x] Show All Polyclinics
[x] Show Polyclinic by ID
[x] Update Polyclinic by ID
[x] Delete Polyclinic by ID

Prefer remove the past MVC.

Prefer remove the past MVC.

done

Please rename src/app/polyclinic/services/usercases.go to src/app/polyclinic/services/usecases.go.

Please rename src/app/polyclinic/services/usercases.go to src/app/polyclinic/services/usecases.go.

Done. Sorry it's a typo


Providing better workflow for repo + autotagging on travis-ci

I would suggest to call this 1.4 and not 1.3.1
This ist a major change in the repos structure

ok, changed to 1.4.0

Hi @piotr-zuralski! Thank you for your contribution.
I am quite confused with the PR though tbh.
Although some changes are valuable, like travis and readme, I am not sure whether we can find someone to maintain new workflow.

Hi @dfcreative,
I can describe more then proposed workflow to be more clear about steps and purposes, if you want.