Error in running "./scripts/setup-intellij.sh"

I got the following error message:
ERROR: /Users/syan/code/heron/integration-test/src/python/test_runner/BUILD:5:1: Executing extra_action //tools/python:checkstyle_python on //integration-test/src/python/test_runner:test-runner failed: bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
 Found 7 spaces, expected 6 (bad-indentation)
W:142, 0: Bad indentation. Found 7 spaces, expected 6 (bad-indentation)
W:153, 0: Unnecessary semicolon (unnecessary-semicolon)
C:161, 0: Unnecessary parens after 'if' keyword (superfluous-parens)
C:171, 0: Line too long (101/100) (line-too-long)
C:188, 0: Line too long (114/100) (line-too-long)
C:  1, 0: Missing module docstring (missing-docstring)
C: 20, 0: Missing function docstring (missing-docstring)
W: 29, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 32, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 42, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 55, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 70, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 36, 5: Unused variable 'httpResponseCode' (unused-variable)
C: 79, 0: Missing function docstring (missing-docstring)
W: 81, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 86, 6: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 90, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
C: 93, 0: Missing function docstring (missing-docstring)
W:104, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
W: 94, 6: Unused variable 'i' (unused-variable)
C:108, 0: Missing function docstring (missing-docstring)
W:120, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
W:122, 6: Unused variable 'i' (unused-variable)
C:130, 0: Missing function docstring (missing-docstring)
W:135, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
W:139, 6: Specify string format arguments as logging function parameters (logging-not-lazy)
W:141, 7: Specify string format arguments as logging function parameters (logging-not-lazy)
W:144, 2: Specify string format arguments as logging function parameters (logging-not-lazy)
C:148, 0: Missing function docstring (missing-docstring)
W:159, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
C:168, 0: Missing function docstring (missing-docstring)
W:204, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W:206, 6: Specify string format arguments as logging function parameters (logging-not-lazy)
W:209, 4: Specify string format arguments as logging function parameters (logging-not-lazy)
W:211, 6: Specify string format arguments as logging function parameters (logging-not-lazy)
W:  7, 0: Unused import threading (unused-import)
W: 10, 0: Unused import mimetools from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import GONE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import FakeSocket from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPS_PORT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTP from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import REQUESTED_RANGE_NOT_SATISFIABLE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import SERVICE_UNAVAILABLE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import CannotSendHeader from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import MOVED_PERMANENTLY from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import BadStatusLine from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UnknownProtocol from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import LENGTH_REQUIRED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import REQUEST_ENTITY_TOO_LARGE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import LineAndFileWrapper from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import FOUND from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import array from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import ACCEPTED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import BAD_GATEWAY from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import REQUEST_TIMEOUT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import SWITCHING_PROTOCOLS from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTP_PORT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import EXPECTATION_FAILED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import USE_PROXY from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UNAUTHORIZED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPException from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import REQUEST_URI_TOO_LONG from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTP_VERSION_NOT_SUPPORTED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import warnings from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import IM_USED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import InvalidURL from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import SEE_OTHER from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import re from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UNPROCESSABLE_ENTITY from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import BAD_REQUEST from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import GATEWAY_TIMEOUT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import py3kwarning from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import IncompleteRead from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import FAILED_DEPENDENCY from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import MULTIPLE_CHOICES from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import INSUFFICIENT_STORAGE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import PAYMENT_REQUIRED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import CONFLICT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import responses from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import LineTooLong from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import TEMPORARY_REDIRECT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import MAXAMOUNT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import INTERNAL_SERVER_ERROR from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import PARTIAL_CONTENT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import CREATED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import RESET_CONTENT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import PROCESSING from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import PRECONDITION_FAILED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NOT_MODIFIED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import ResponseNotReady from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import ssl from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UnknownTransferEncoding from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NOT_ACCEPTABLE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UNSUPPORTED_MEDIA_TYPE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPS from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPResponse from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NotConnected from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import OK from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NOT_FOUND from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import MULTI_STATUS from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import urlsplit from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NOT_EXTENDED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NON_AUTHORITATIVE_INFORMATION from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import LOCKED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import socket from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UnimplementedFileMode from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import METHOD_NOT_ALLOWED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import StringIO from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NO_CONTENT from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import ImproperConnectionState from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import NOT_IMPLEMENTED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import CONTINUE from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPMessage from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import error from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import HTTPSConnection from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import PROXY_AUTHENTICATION_REQUIRED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import CannotSendRequest from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import UPGRADE_REQUIRED from wildcard import (unused-wildcard-import)
W: 10, 0: Unused import FORBIDDEN from wildcard import (unused-wildcard-import)
Jul 17, 2016 9:39:15 PM com.twitter.bazel.checkstyle.PythonCheckstyle main
INFO: 1 python files found by checkstyle
Exception in thread "main" java.lang.RuntimeException: python checkstyle command failed with status 20
	at com.twitter.bazel.checkstyle.PythonCheckstyle.runLinter(PythonCheckstyle.java:119)
	at com.twitter.bazel.checkstyle.PythonCheckstyle.main(PythonCheckstyle.java:88)

@yanxz Hi, Python style checking was just enabled yesterday and I am sorry I forgot fix Python coding style under integration_test.
will do it now.

Thanks for the issue. A PR has been submitted to fix this issue: https://github.com/twitter/heron/pull/1100

Hi, @yanxz
#1100 is merged. Could you please pull the master branch, do bazel clean, and try again?

@objmagic pulled the change and reran the script, it works now! Thanks for such quick response, it's really awesome!


Preset for Travix

What's done

New frint-preset-travix package for installing all Frint packages in one go.
The preset will take care of versioning for all the packages for us.

The primary reason for keeping it in the monorepo is Lerna's feature of automatically updating the version numbers in package.json on every new release.
And instead of manually updating all the package's versions in our private repositories later, we only need to update to latest preset every time.
It may be extracted out into a separate repository in future.

Coverage remained the same at 97.312% when pulling d49a47d814419f54c786e258ee7ba0dd5f38dfa3 on frint-preset-travix into 9ec55e1a0c208e7ef75cfa208aaf20481df63909 on master.


:soap: Refactor of Create NFT

:tada: created BasicNumberInput
:zap: created BaseTokenForm
:zap: added CollectionSelect and few types
:globe_with_meridians: added translation for editions
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:construction: Refactoring Creating NFT
:art: finishing touches for the create NFT
:art: calculating fees a bit smarter
:globe_with_meridians: added translation for setting price warning
:broom: move set loading for a bit later
:bug: only push list interaction if there is price
:bug: forgot to add advanced settings for mint
:broom: playing with base types
:zap: BaseTokenForm now takes edition visibility as prop
:soap: CustomAttribute has now name
:construction: Creating Unique NFT

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Do a quick check before the merge.
PR type

[x] Bugfix
[ ] Feature
[x] Refactoring

What's new?

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted screenshot of demonstrated change in this PR

/giphy launch rockets

/giphy yolo


Chapter 8 & 9 Typos [version 2022-05-02]

Chapter 8 (Message Passing)

<IP_ADDRESS> - p.359 (latex) line 3: typo "by"-->"bu".

We can define multiplication and division in the Gaussian case bu using canonical forms, as follows.

Chapter 9 (Variational inference)

9.3.2 - p.384 (latex): 'control variates':

"CV" abbreviation appears in text without definition, it is pretty clear from the context what is meant by "CV" but it might be helpful to be explicit.
superscripts: eqs 9.117 & 9.118 use "CV" in caps as superscript, eq. 9.119 uses lower case "cv" as superscript.

fixed, thanks


Ansible tutorial: replace geerlingguy.git with alternative that is not already installed on VMs

The Ansible tutorial expects the user to have a failed playbook run when installing a package. However, this doesn't happen because Git is already installed.
Solution: we need to use a different module as an example.
(This was discussed prior to and during admin training at BCC 2020.)

Do geerlingguy.memcached, that's a pretty harmless service.


Separate stdout and stderr in run

Introduces new variables:
$output_stdout, $output_stderr, $lines_stdout, $lines_stderr
Existing $output and $lines variables remain.

I found this while looking into #55 and noticed it never made it into a PR.
@duggan Thanks for the excellent contribution. I hope you don't mind.
@ahippo Was previously tagged in the branch as well.
Any thoughts on merging this @sstephenson? There was already a good bit of discussion about the topic in #55.
This is not my code. I'm just making a PR for code that I believe adds the feature that I would like.
I see it cannot be merged cleanly. I wouldn't mind cleaning it up to get it merged. Let me know.

I found this while looking into #55 and noticed it never made it into a PR.
@duggan Thanks for the excellent contribution. I hope you don't mind.
@ahippo Was previously tagged in the branch as well.
Any thoughts on merging this @sstephenson? There was already a good bit of discussion about the topic in #55.
This is not my code. I'm just making a PR for code that I believe adds the feature that I would like.
I see it cannot be merged cleanly. I wouldn't mind cleaning it up to get it merged. Let me know

Yeah, it would be great to have this merged!
There is some tricky code though.
I can also help if needed.


Why is it still using Webpack, or is it broken?

I first tested in a much more evolved but still CRA based with TypeScript project. Didn't seem to be using esbuild. The yarn build still took ~10s.
Start a fresh new project:
cd /tmp/
npx create-react-app@latest my-ts-app --template typescript
cd my-ts-app
yarn build
# takes about ~5s

Then I followed the steps in the readme verbatim. And when I type yarn build you can see that it's supposedly using craco:
▶ yarn build
yarn run v1.22.10
$ craco build
Creating an optimized production build...
Compiled successfully.

File sizes after gzip:
...

But still takes about ~5s to build. I don't know what I'm doing but I did open node_modules/react-scripts/scripts/build.js and with some scatter console.log it seems it's still using webpack.
Is it busted at the moment? Or is something missing in the readme?

Is there any cure for this? Also use craco esbuild and the build time remais the same.

For small build (like 5s) you won't see any difference as the biggest part of that time is actually used by webpack. This project is still using webpack along with esbuild, babel is replaced by esbuild but the bundling is still handled by webpack.
For example, compiling the example of this repo using CRA takes 33 seconds, with esbuild it goes down to 16 seconds so a 50% win.

@pradel -- I'm not seeing that ESBulid is being utilized at all after the changes I linked above.  We utilize CRA in several extremely large production projects and after I attempted to implement this plugin I simply receive the following:

[esbuild-loader] ESBuildPlugin is no longer required for usage and will be removed in the next major release. Please refer to the docs and release notes for more info.

And see no improvement in transpilation.

@cjones26 okay that's not normal in that case yeah. The warning you had was fixed in the latest version so maybe you can give it another try?

Same here. Tested a few times, didn't see much difference, both took over 2 minutes to complete

You can compare before and after with the speed-meassure-webpack-plugin
const SpeedMeasurePlugin = require("speed-measure-webpack-plugin");

const CracoEsbuildPlugin = require("craco-esbuild");
const smp = new SpeedMeasurePlugin();

module.exports = {
  plugins: [{ plugin: CracoEsbuildPlugin }], // <-- comment this line to see w/o esbuild
  webpack: {
    configure: (webpackConfig) => smp.wrap(webpackConfig),
  },
  // eslint: {  enable: false, }, // <-- this shaves a couple of seconds for me
};

In a small-ish project I'm trying it shaves 50% of the build time (39sec -> 20sec)


Add events to show/hide fragments

hello
thank you for your work.
can you please add events to fragments called when fragment is show/hide ?
for example when new fragment displayed , fire event in old fragment "onHide()"
when back button pressed and fragment onDestroy called , fire event on backstack fragment "onShow"

Hi @Amenocy, Thanks for testing out the library!
We will look into adding these changes in a future release.

@Amenocy those hooks are  now available in release 1.1.0. You should be able to implement/override 2 event listener onShown and onHidden.


Allow suppression of pidfiles.

When unbound is maintained by a system manager that can actually keep
track of what daemons are running correctly, a pidfile is an
opportunity for extra failures, rather than a way to avoid failures.
In particular, if unbound terminates roughly, it might leave the
pidfile lying around. Then a subsequent unbound instance will think
that another unbound process is running when it isn't (particularly if
some other stable process happens to have landed on the same process
ID).
So for a system manager that is already capable of keeping track of
whether the daemon is running or not, it would be nice to have the
ability to avoid these extra failure modes by just ignoring pidfiles
entirely.
Since the same unbound config file might need to be used on a
distribution that might use different system managers, being able to
control the use of a pidfile by a command-line argument is probably
the cleanest way to go (see https://bugs.debian.org/867192).

Closing this PR, was also submitted as patch to our bugzilla (https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=1349) and is applied.


Add targeting validation

With the addition of a rigorous targeting schema for flagd, we can validate targeting rules. We should validate CRDs with these.
Tasks:

[ ] add JSON schema validation for RULES only (we don't need to validate entire flag configs, just rules)

[ ] clear error messaging to admins when this validation fails

[ ] add option arg to disable validation in OFO (should be on by default)
[ ] associated tests

@odubajDT Are you still interested in working on this one?

Hi @toddbaert sorry for not tackling this already, have quite full backlog, but I can start working on it during this/next week. Would that be ok?

I am very sorry, but I currently do not have the capacity to handle this issue :/ Unassigning myself to not block this


Error installing redis image

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


Roll Plugins from e11cb245bb8e to 417b37009871 (1 revision)

https://github.com/flutter/plugins/compare/e11cb245bb8e...417b37009871
2022-12-28<EMAIL_ADDRESS>Roll Flutter from ae292cc4e5e4 to 17482fd425ee (28 revisions) (flutter/plugins#6889)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


[SPARK-35185][SQL] Improve Distinct statistics estimation

What changes were proposed in this pull request?
This PR improves Distinct statistics estimation by rewrite it to Aggregate.
Why are the changes needed?
The current implementation will lack column statistics. Some rules before the ReplaceDistinctWithAggregate may use it. For example: https://github.com/apache/spark/pull/31113/files#diff-11264d807efa58054cca2d220aae8fba644ee0f0f2a4722c46d52828394846efR1808
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit test.

Test build #137796 has started for PR 32291 at commit 00739ec.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42325/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42325/

Test build #137796 has finished for PR 32291 at commit 00739ec.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/137796/

cc @cloud-fan @maropu

Merged to master.

Unfortunately, this seems to be merged with no review and approval.

the change looks good but we should merge PRs with review and approval. @wangyum please be more patient next time.


Unsupported API Call Exception on Build Publishing

Dear all,
I'm currently trying to publish documentation of a python project to a confluence instance, but the process keeps aborting with a HTTP 500 error from the server. Can you help me diagnose the root cause?
Thanks!
Output from the Report Command
(system)
 platform: Darwin-20.6.0-x86_64-i386-64bit
   python: 3.6.2 (default, Jun 21 2021, 15:27:31) [GCC Apple LLVM 12.0.0 (clang-1<IP_ADDRESS>)]
   sphinx: 4.2.0
 requests: 2.26.0
  builder: 1.6.0

(configuration)
confluence_page_hierarchy: True
confluence_parent_page: (set)
confluence_publish: True
confluence_publish_dryrun: False
confluence_server_pass: (set)
confluence_server_url: https://<removed>
confluence_server_user: (set)
confluence_space_name: (set; upper)

(error loading configuration)
unable to load configuration

(confluence instance)
 connected: no

Partial Output of the Build
I used the command sphinx-build -b confluence doc doc/_build/confluence -E -a -vvv -T to start a build.
writing output... [100%] space-migration
[app] emitting event: 'doctree-resolved'(<document: <target...><section "migrating one or more confluence sp ...>, 'space-migration')

publishing documents... [  8%] index
[app] emitting event: 'build-finished'(ConfluenceBadApiError('---\nAn unsupported Confluence API call has been made.\n\nREQ: PUT\nRSP: 500

Traceback (most recent call last):
  File "/projectdir/venv/lib/python3.6/site-packages/sphinx/cmd/build.py", line 280, in build_main
    app.build(args.force_all, filenames)
  File "/projectdir/venv/lib/python3.6/site-packages/sphinx/application.py", line 337, in build
    self.builder.build_all()
  File "/projectdir/venv/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 257, in build_all
    self.build(None, summary=__('all source files'), method='all')
  File "/projectdir/venv/lib/python3.6/site-packages/sphinx/builders/__init__.py", line 360, in build
    self.finish()
  File "/projectdir/venv/lib/python3.6/site-packages/sphinxcontrib/confluencebuilder/builder.py", line 601, in finish
    self.publish_doc(docname, output)
  File "/projectdir/venv/lib/python3.6/site-packages/sphinxcontrib/confluencebuilder/builder.py", line 458, in publish_doc
    uploaded_id = self.publisher.storePage(title, data, parent_id)
  File "/projectdir/venv/lib/python3.6/site-packages/sphinxcontrib/confluencebuilder/publisher.py", line 535, in storePage
    self._updatePage(page, page_name, data, parent_id=parent_id)
  File "/projectdir/venv/lib/python3.6/site-packages/sphinxcontrib/confluencebuilder/publisher.py", line 742, in _updatePage
    self.rest_client.put('content', page['id'], updatePage)
  File "/projectdir/venv/lib/python3.6/site-packages/sphinxcontrib/confluencebuilder/rest.py", line 186, in put
    raise ConfluenceBadApiError(errdata)
sphinxcontrib.confluencebuilder.exceptions.ConfluenceBadApiError: ---
An unsupported Confluence API call has been made.

REQ: PUT
RSP: 500
URL: https://confluence-instance.example.com/rest/api
API: content
DATA: {
  "statusCode": 500,
  "message": "",
  "reason": "Internal Server Error"
}

Hey @nausicaea,
Assuming that the server URL is configured properly (it looks to be listed as https://confluence-instance.example.com/..., but it is assumed that this has been manually sanitized -- mentioning it, just in case), such an error is either due to an issue with content generated by this extension or an issue with the Confluence instance. Unfortunately, it is not always straight forward what it is. But there are approaches that can be made.
If it is data related, there is an undocumented data trace call which can be set:
confluence_adv_trace_data = True

When running with this option, a trace.log file will be generated in the working directory of the call and will output the raw contents of data into a file for each document that is processed. As documents are processed, generated output will be added into this file. Based on the above output, it is assuming that there might be some output in the index file which Confluence is not accepting. You could try to examine the contents of the last [data] entry  in the trace log to look for what might be causing this issue. Another approach is to hack out the respective restructuredText content from the document to see what may be causing the issue (e.g. improper/unsupported characters, bug in the output of this extension, etc.).

Other possible issues may be related to the connection of the instance publishing documentation to the target Confluence instance. Assuming confluence_server_url is properly set, other issues this may be:

If the environment uses a proxy and the Confluence instance you are connecting to should not being going through a proxy, you may need to ensure your environment's no_proxy option is configured appropriately.
Another case may be that the target Confluence instance may be serviced through a reserve proxy and requires additional header data to process requests (see also #441). However, only your system administrators of your instance would know if this is a requirement. If custom header options are needed to communicate with the configured instance, options could be set via the confluence_publish_headers option.

A crude sanity check you could try is manually browsing the Confluence REST API endpoint from your browser. For example,
if the configured Confluence URL was https://confluence-instance.example.com/, the following page:
https://confluence-instance.example.com/rest/api/search

Should output something like the following in a browser:
{"statusCode":400,"data":{"authorized":false,"valid":true,"errors":[],"successful":false},"message":"com.atlassian.confluence.api.service.exceptions.BadRequestException: cql query parameter is required"}

Dear @jdknight, I'm sorry I haven't replied yet. I haven't had the chance to test it out because other work issues had higher priority. I'll see to it that I can try out your suggestions this week, and then I'll get back to you.

I applied the data trace call option and looked at the last [data] entry in the trace.log file. As far as I was able to see, the code looked fine. But to be sure, I copied the contents in to the Confluence Source Editor of an empty page, and the content renders exactly as I would want it to, when saving the page. I followed the following steps:

Create an empty page in Confluence on my personal space
Save the page
Edit the page and click on "Open in source editor" in the upper right-hand corner of the page editor
Copy the contents of the last [data] section in trace.log directly into the source editor
Click on "Apply" and then on "Update" to save the page

Based on this experiment, I'm assuming that your extension correctly generates the Confluence storage format content from the restructuredText files.

Regarding the Confluence instance URLs: I did check the URL and the parameter confluence_server_url multiple times, and it is correct. We do serve Confluence behind an Apache2 proxy, but that hasn't caused any problems so far. We don't use a WAF or anything similar on the other hand. I am the "deputy" service administrator, but I'm not aware of any special headers we employ for authentication. Thanks for pointing that out though!
We also use the REST API for other things and it works as documented by Atlassian. But to be sure, I navigated to the Search API endpoint, and I'm getting exactly the unauthorized response you're suggesting.
I will try to publish the documentation by directly using the local Confluence server (circumventing the proxy): I'll post an update later.

Unfortunately, running the confluence builder plugin directly on our dev server didn't fix the issue. I'm still getting the same internal server error as before.
However, issuing a direct authenticated call to the REST API results in the expected response:
curl --basic -u <username> http://localhost:8090/rest/api/content/search?cql=space=AI
I'm sending you the full output of my command line. Maybe you'll see something that I am not seeing:
sphinx-build -b confluence doc doc/_build/confluence -E -a -vvv > output.log 2>&1
output.log

I think I found the reason. First off, thank you for all the detailed information, it for sure helpful.
Inspecting the logs show this is part of the publish request:
  "id": "60129330",
  ...
  "ancestors": [
    {
      "id": "60129330"
    }
  ]

It is trying to update page with the same identifier that it is also trying to set the page as a child of. On Confluence Cloud, this is reported as a 400 error with a description message "Cannot add an existing ancestor as a child!"; but on (some) Confluence self-hosted solutions, it appears to give the non-descriptive 500 error.
It appears to me that you have root document titled Confluence Migration Assistant (CMA), which is trying to publish as a child of itself on the space. This is most likely due to confluence_parent_page being set to the same value. I believe you want to either do one of two things:

Instead of using confluence_parent_page, switch to confluence_publish_root instead. Although, this would require using the Confluence generated page identifier (observed from the URL or in the page's properties on Confluence) instead of a string value -- but with this you will be guaranteed it will be stored under a specific document (although, not flexible if you are using multiple spaces/languages base points; depending on the environment). For example (based on the output files provided):

confluence_publish_root = 60129330

(recommended) Remove the option confluence_parent_page completely. If you already have a page name on the Confluence instance created, any updates will update the existing document and child pages (with confluence_page_hierarchy being set) will be still stored inside the page. Moving this base page around in a space (if the space has mixed content) should not cause any issues with update, where it will still respect* maintaining updates within the base page (* without getting into title issues; and some corner cases with orphan pages).

If you try any of these changes and it does not work, please let me know.

On that note, there are improvements that can be made to this extension. I will try to implement something to detect this use case and provide a more presentable error message to users. This also relates to #348 -- where there is for sure room for improvement in dealing with pre-detecting more error cases related to other nested page cases.

Ah! Now I understand! Thank you so much! I ended up opting for solution 1 and things worked out perfectly! :)


magneticio/mesos:0.22.0 docker images is not published

The docker-compose.yml references magneticio/mesos:0.22.0 which isn't published to the public docker registry.

Good catch. Pushing it as we speak. If you are in a hurry you can clone this repo and build it at https://github.com/magneticio/vamp-docker/tree/master/dockerfiles/mesos

Thnx, got it running :+1:


hotfix: no tickets load on frontend because of remote db compatibility issues caused by incomplete migrations

What type of PR is this? (check all applicable)

[ ] Refactor
[ ] Feature
[X] Bug Fix
[ ] Optimization
[ ] Documentation Update

Description
when you run yarn dev, no tickets load on frontend, there was a discrepancy between db states, essentially the remote db didn't have the same seed file so it had the wrong data, app_constants didn't include status constant and that was creating a problem as well as the requests table didn't have the right info on the status col.
Related Tickets & Documents
i dont have a ticket for it. it's a bug i dont see why we need to create a ticket on project board when the documentation is all here

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings
pending screenshots when it actually works
Added/updated tests?

[ ] Yes
[X] No, and this is why: not a functional change
[ ] I need help with writing tests

Can reviewers merge this PR upon approval?

[X] yes, reviewers can merge this PR
[ ] no, the author of this PR needs to merge it

[optional] Are there any post-deployment tasks we need to perform?

how do i make reseed remote db? the seed.sql file has the right data that would fix the issue. i dont want to manually recreate the needed data on remote

Updated the database types. That should fix the generate-types issue. I really need a GitHub action that just does that automatically...

how do i make reseed remote db? the seed.sql file has the right data that would fix the issue. i dont want to manually recreate the needed data on remote

I found this: https://github.com/supabase/cli/pull/1105
I think we could also just truncate the tables and then run the seed file in the SQL editor on Supabase

If there was an issue with seeding why did you not change the seed.sql file? I think I'm not fully understanding this change.
It seems like part of the issue is resetting the shared supabase account, and part of it is the configuration of the status column?

how do i make reseed remote db? the seed.sql file has the right data that would fix the issue. i dont want to manually recreate the needed data on remote

I found this: https://github.com/supabase/cli/pull/1105
I think we could also just truncate the tables and then run the seed file in the SQL editor on Supabase

I like the truncate method it's simple and fast I'll get that done

If there was an issue with seeding why did you not change the seed.sql file? I think I'm not fully understanding this change.

I pushed the seed file then realized if we keep track of changes in seed file it'll be changed every push since everytime we Regen it the uuid for everything will be different and if we consistently want the 1000 tickets it'll be a big diff to track every migration change. I like the paste in SQL editor route

It seems like part of the issue is resetting the shared supabase account, and part of it is the configuration of the status column?

Correct

Updated the database types. That should fix the generate-types issue. I really need a GitHub action that just does that automatically...

I will work on that once I'm done with filtering, meanwhile I made sure to run gen types but I forgot to rerun it after removing the local view I made


feat: setup initial DA module structure

Description

closes: #XXXX
Motivation and context

How has this been tested?

Screenshots (if appropriate):
Checklist:

[ ] I followed the contributing guidelines and code of conduct.
[ ] I have added a relevant changelog to CHANGELOG.md
[ ] I have added tests to cover my changes.
[ ] I have updated the documentation accordingly.
[ ] I have updated API documentation client/docs/swagger-ui/swagger.yaml

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tkxkd0159:x: Jaeseung LeeJaeseung Lee seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


allowsBackgroundLocationUpdates

Can you please help me to get location when application in background mode.
I am having Google Map integrated in my app and confused in getting location in background.
Thanks in advance

Background is working totally fine with me
But I am stuck in updating location while app is terminated
@malcommac  If you can clear that whether I can implement this feature using you library ?
Thank you so much for this library helped me a lot already.

@manish-1988
How you manage to get location in background??
can you post your code here please?

You should as this question in stackOverflow only not here , but since I also did asked a question here is the standard solution to your query
Step - 0 Open pList as source code and add these lines in your code.
NSLocationAlwaysUsageDescription
This App requires your location
NSLocationWhenInUseUsageDescription
This App requires your location
Step 1 - In target - capabilities
Switch on the location updates in background mode, regenerate provisioning profile if needed.
Step II - Request for authorization
& Initialize locationManager
/// MARK:- LOCATION MANAGER INITIALIZATION
    func initLocationManager(target: UIViewController)
    {
        self.locationManager = CLLocationManager()

        self.locationManager.delegate = self

        self.locationManager.distanceFilter = CLLocationDistance(50.0)

        self.locationManager.requestAlwaysAuthorization()

        self.locationManager.desiredAccuracy = kCLLocationAccuracyBest

        self.locationManager.startMonitoringSignificantLocationChanges()

        if #available(iOS 9.0, *)
        {
            self.locationManager.allowsBackgroundLocationUpdates = true
        } else
        {
            // Fallback on earlier versions
        }

        if (CLLocationManager.locationServicesEnabled())
        {
            switch(CLLocationManager.authorizationStatus())
            {
            case .NotDetermined:

                print("NotDetermined")

            case .Restricted:

                print("Restricted")

                Singleton.sharedInstance.showLocationAlert(target)

            case .Denied:

                print("Denied")

                Singleton.sharedInstance.showLocationAlert(target)

            case .AuthorizedAlways, .AuthorizedWhenInUse:

                print("Location Service => AuthorizedAlways | AuthorizedWhenInUse")

                self.locationManager.startUpdatingLocation()

            }
        }else
        {
            //Yet nothing to do in this condition
        }
    }

This below delgate will be called even in background if device gets location update.
    func locationManager(manager: CLLocationManager, didUpdateLocations locations: [CLLocation])
     {
         **// Here you can send your location to server using webService.**
     }

Thanks Manish,
Is this solution valid for SwiftLocation Library???
I mean i have SwiftLocation library installed so do i need to do all above procedure to get location in background??
Thanks again for your quick response.

In any case you need to perform the target - capabilities thing and plist thing I mentioned in my above answer rest,
If you want to use this library it is clearly mention in the documentation how to do it.
You just need to add this

SwiftLocation works even in background; just use Location.allowsBackgroundEvents = true (don't forget to define UIBackgroundModes array).
So
There is a property Location.allowsBackgroundEvents make it true.
Following is the code you can use I am using previous version of the library.
       LocationManager.shared.allowsBackgroundEvents = true // This line is important for you  LocationManager.shared.observeLocations(.Room, frequency: .ByDistanceIntervals(meters: 50), onSuccess: { (location) in             print(location)             }) { (error) in                 print(error)         }

Do let me know if it works.

Thanks Brother for helping,
will let you know if it works

No problem, you're welcome. thanks to @manish-1988 for support.

@manish-1988
did you get solution for updating location even if app is terminated?

@swabzz  Yes what I did is I have used region monitoring. First I created a background task before app termination and created a region as soon as the device crosses the region, I have created another region from the current coordinates while entering and exiting from regions,  did update location delegate gets called and I get the updated coordinate while application is in terminated mode.

Thanks for quick reply @Manish
Your solution is awesome but can you share your code please ?
It will be easy for me to implement in my project. :-)

Hi,
I have a question about this background issue. In swiftLocation documentation Location.allowsBackgroundEvents = true code writes for activate background location updates. I integrate SwiftLocation to my new project but, there is not any variable to set allowsBackgroundEvents
When I am trying to get location there is a log like
A new request is added to the queue [LOC:826CB3FC-F0BD-4CB8-B8E2-EB6B598BE02F] - Acc=Room, Fq=Significant. (Status=running, Queued=true) oYn4pRVBj3e56KTO0QXIhgABzT32 An existing request was removed from the queue [LOC:826CB3FC-F0BD-4CB8-B8E2-EB6B598BE02F] - Acc=Room, Fq=Significant. (Status=idle, Queued=false) Location monitoring failed due to an error backgroundModeNotSet
In my info.plist I insert the required background modes and I also open Location updates in Background Modes in Capabilities section.
What can be the problem ?
Thanks for any help
My code is below:
`//Taking Location
    Location.onAddNewRequest = { req in
        print("A new request is added to the queue \(req)")
    }
    Location.onRemoveRequest = { req in
        print("An existing request was removed from the queue \(req)")
    }

    let x = Location.getLocation(accuracy: .room, frequency: .significant, success: { (_, location) in
        print("A new update of location is available: \(location)")
        let longitude = location.coordinate.longitude
        let latitude = location.coordinate.latitude
        self.firebaseManager.setLocation(uid: uid!, longitude: longitude, latitude: latitude)

    }) { (request, last, error) in
        request.cancel() // stop continous location monitoring on error
        print("Location monitoring failed due to an error \(error)")
    }
    x.register(observer: LocObserver.onAuthDidChange(.main, { (request, oldAuth, newAuth) in
        print("Authorization moved from \(oldAuth) to \(newAuth)")
    }))

    //taking Location end`


Fixed Contact us Alignment

Closes #323

Solved the alignment issue of contact us page

Well done @IkkiOcean

Can you give star to this repo?

@Anuj3553 I already have starred it :)


Please 🐦 about v0.46.0 release

Hi,
can you please tweet about v0.46.0 so i'll can retweet it ❔ 🙏

cc @microwavables

🐦 ✔


How can i use this in ios13?

Great component!!!
Will this support ios13 version?

Hi, I received your Issue in NavigationViewKit and SheetKit.
Thank you for your love of NavigationViewKit and SheetKit.
Since iOS 13 and iOS 14 have the same hardware requirements, only a very small number of users (with enough hardware to support iOS 14) are still using iOS 13. SwiftUI 1.0 (iOS 13) was quite immature and didn't become more stable until SwiftUI 2.0 (iOS 14). Therefore neither library provides support for iOS 13.
SheetKit is theoretically iOS 13 capable if you remove the code that supports BottomSheetViewController. Likewise if you make NavigationViewKit support iOS 13 you need to remove quite a bit of that functionality to make it work.
From my own practice, I would also recommend that your app start supporting iOS 14.
Translated with www.DeepL.com/Translator (free version)


I wanted to Export the value of SketchField

Hi @tbolis,
Just wanted to know, Where can I get the value of the whiteboard after drawing.. something like exporting or is there any way to get the value of the SketchField whatever it stores.
I need a data on export like this file data.json.controlled.js have.
So, that I can load that data at any time..
i.e.,
<SketchField width='1024px'                           height='768px'                           tool={Tools.Pencil}                           lineColor='black'                          lineWidth={3}                         value={something} />
Can you please help me in this.
Thanks in advance.

Try this:
<SketchField ref={sketchRef} />
...
const drawnObjects = sketchRef.current.toJSON()


Add Opera /NoAutostart param

Add /NoAutostart param for opera since newer versions annoyingly add an autorun entry to registry by default. https://www.reddit.com/r/operabrowser/wiki/opera/installer_commands/
Description
The param got added where params seem to be normally added.
Motivation and Context
As above, upgrading/installing Opera makes it autostart with Windows.
How Has this Been Tested?
I hope this is enough as testing is stopping me from submitting PRs, need to learn how to test such changes and I don't have quite time for that. Filling this template already took longer than the small changes themselves.
Anyways, I ran:

choco pack in the opera folder in git repository
 choco install Opera --debug --verbose --source . --params "'/NoAutostart'" -f
Installation completed, no autorun entry was found

Screenshot (if appropriate, usually isn't needed):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[x] My change requires a change to documentation (this usually means the notes in the description of a package).
[x] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

Can you also fixup the commit message to include the package name, i.e. (opera) <COMMIT MESSAGE>?

I hope it's fine now

:white_check_mark: Package verification completed without issues. PR is now pending human review

@Destroy666x awesome work! Thanks for your contribution!


Proposal: add Dictionary#get method

Godot version:
3.1.alpha.custom_build.3f46295
The [] operator throws an error if a key does not exist:
var my_key = 5
var my_dict = {1: 2, 3: 4}

print(my_dict[my_key])
-> Invalid get index '5' (on base: 'Dictionary')

If we're not sure whether the key exists, we have to resort to ugly workarounds like this:
var value = my_dict[my_key] if my_dict.has(my_key) else null
print(value)

So we have to use an extra variable and a less readable expression. This is especially tedious if my_key is not a variable, but a more complex expression, in which case we end up with two helper variables.
Moreover, the has check followed by the [] results in two dictionary lookups where one should suffice, so it's bad for performance as well.
Both of these could be solved if we implemented a get(key, default) method like Python has:
print(my_dict.get(my_key, null))

And like in Python, the default should be optional and default to null. The behaviour would be equivalent to:
func get(key, default = null)
    return self[key] if self.has(key) else default

Awesome, thanks! Don't know how that didn't come up in my search. Maybe I didn't remove the issue:open because my build is pretty recent to begin with XD


Changing the query should bring scroll to the top in extension viewlet

Testing #8215
It serves no purpose to maintain the scroll position if the search query is changed, as all the items become animated dots anyways and they all change after I type the new query

Agree, not cruical -> july, joao


Add a robots.txt that allows scraping

https://github.com/gdmen/garymenezes.com/commit/e44c776546220529451a7557bcdf680d6ae21a9e


Build with Grails 2.5, Spring Security Core 3.2.8

Master is Grails 3, use the 2.x branch for the Grails 2 plugin. Closing since there's rarely any benefit to using a newer version of Grails for developing plugins, only for apps. It's trivial to update to the latest version of Spring Security, will do that for the next release.

The PR also contains this commit (https://github.com/tcrossland/grails-spring-security-core/commit/d66d44bfc80ebe956b99bdde95d7b358f358fb18) which ensures the test apps (and Travis build) test the current version of the plugin instead of any old 2.0-SNAPSHOT version that happens to be installed.

@burtbeckwith would you like me to create a new PR for the grails 2 branch with the fix for the test apps? Or should I create an issue. (This PR was created in July before any grails 3 work had been done on the plugin).

See #388


[TRACKER] Scene Inheritance related issues

This is a tracker for issues related to Scene Inheritance:

[x]  IMPORT:: New meshes introduced into scene lose their name https://github.com/godotengine/godot/issues/2223 (bug)
[x] "Parse Error: Unexpected end of file" in inherited .tscn files https://github.com/godotengine/godot/issues/3897 (bug)
[x] Inherited scenes: float variables always seen as custom, can't be reset https://github.com/godotengine/godot/issues/4759 (bug)
[x] Editing exported boolean of base scene child is not working in inherited scene  https://github.com/godotengine/godot/issues/3904 (bug)
[x] Inherited scene saving parent nodes in incorrect order https://github.com/godotengine/godot/issues/3945 (bug)
[x] Scenes are unable to remember it's nodes fold state https://github.com/godotengine/godot/issues/3395 (bug)
[x] Tscn/tres: Inconsistencies in the extension filters of the save/open file dialogs https://github.com/godotengine/godot/issues/2946 (enhancement)
[x] Signal already connected" error in inherited scenes https://github.com/godotengine/godot/issues/6106 (bug)
[ ] Exported vars not immediately updating for inherited scenes. https://github.com/godotengine/godot/issues/5997 (bug)
[ ] Impossible to change physic mode for instanced/inherited physic objects https://github.com/godotengine/godot/issues/6216 (bug)
[ ] CollisionShapes related issues https://github.com/godotengine/godot/issues/5798, https://github.com/godotengine/godot/issues/8103 (bug/enhancement)
[ ] Sub-inherited scene is not updated properly in the editor https://github.com/godotengine/godot/issues/7984 (bug)
[ ] Ability to modify Animation player in inherited scenes https://github.com/godotengine/godot/issues/6169 (enhancement)
[ ] Ability to change node type of inherited scene https://github.com/godotengine/godot/issues/6215 (enhancement)
[ ] Ability to extend base scene script easily for inherited scenes https://github.com/godotengine/godot/issues/4585 (enhancement)
[ ] Document new scene inheritance concept https://github.com/godotengine/godot/issues/3354 (docs)

2.1 milestone since at least bug fix should be considered for 2.1

done with the bugs

Updated the list, hopefully I didn't miss anything.

would be nice to see how much of this changed

Actually have this on my todo list :) I will update it at the beginning of the next week!

I was searching today for new scene inheritance related issues in order to update tracker. But I haven't found anything new...  (only one issue that I submitted earlier today)

#3354 is fixed.

Ability to modify Animation player in inherited scenes #6169 (enhancement)

Is this fixed? Even importing animations as separate files only persists changes until the next time you export your scene, at which point all your added tracks are wiped out.
@akien-mga's last comment was

AnimationTreePlayer is deprecated in Godot 3.1 and will be removed in Godot 3.2. It is replaced by AnimationTree, which was written from scratch and likely fixes/deprecates this issue.

However, I'm unclear on how AnimationTree can replace the need for adding audio/call tracks to animations. I mentioned some use cases on https://github.com/godotengine/godot/issues/28275, maybe that issue should be part of this list?


Deep cloning the theme object on every render hurts performance

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Steps to reproduce

Create an empty flowbite-react project

Add the following code
import * as React from "react";
import { getTheme } from "flowbite-react";

const Child = () => {
  const theme = getTheme();
  return
child {theme.accordion.content.base}
;
};

function App() {
  const [count, setCount] = React.useState(0);

  return (
    <>

count: {count}

      <button onClick={() => setCount(count + 1)}>inc</button>
      {Array.from({ length: 1000 }).map((_, i) => {
        return <Child key={i} />;
      })}
    </>
  );
}

Open performance tab of chrome devtool

Record the performance

Click the inc button 100 times

See the result

Current behavior

There are many long tasks. I think the root cause is that we're deep cloning the entire theme object on every render for all components which are using getTheme() API.
// packages/ui/src/helpers/clone-deep.ts
import { isObject } from "./is-object";

export function cloneDeep<T>(source: T): T {
  if (!isObject(source)) {
    return source;
  }

  const output: Record<string, unknown> = {};

  for (const key in source) {
    output[key] = cloneDeep(source[key]);
  }

  return output as T;
}

// packages/ui/src/theme-store/index.tsx
export function getTheme(): FlowbiteTheme {
  return cloneDeep(store.theme);
}

Expected behavior
In such a simple project like this, I'm expecting to have no long tasks:

Context
I'm assessing the new UI library for our internal projects.

Known issue, we are working to provide another approach for v1.0.0 release. The current theme is totally experimental, as quoted in the docs.
Closing this one.

But even if we don't use getTheme() in the application code, the experimental theme approach has already been used in the current implementation of many flowbite-react's components, so the performance would be the same when using 1000 flowbite-react's components.


feat: add Kong Hybrid mode on GCP

Unable to move forward from Portainer checking, looks like a firewall problem. This is resolvable from within the VM but not outside.
➜  ~ curl -v http://<IP_ADDRESS>:9000/
*   Trying <IP_ADDRESS>:9000...
* connect to <IP_ADDRESS> port 9000 failed: Operation timed out
* Failed to connect to <IP_ADDRESS> port 9000 after 75011 ms: Operation timed out
* Closing connection 0
curl: (28) Failed to connect to <IP_ADDRESS> port 9000 after 75011 ms: Operation timed out

I noticed in the VM console that the firewall is disabled.

The doc says to have those open.

Configure Kong Konnect Enterprise Chart section
You copy the helm values file to konnect-dp.yaml. Then later we apply a helm overrides file with oc apply? This does not work. This should be an instance of the Kong operator.
This section needs a Kong Operator instance to apply, preferably one that uses $KONG_CP_URL that can be referenced by environmental variable.

In Kong Konnect Enterprise Control Plane, we are creating an instance of a VM in google.  Due to the fact that we are all using the same project in GCP, if more than one person is testing this document they would have to creat a new GCP_VM_NAME. It is extremely simple to miss the hard coded --tags sections in the gcloud compute instances create command. This stopped me from being able to proceed the first time i ran it.
It would be simple if the tags command were referencing $GCP_VM_NAME like the command references $GCP_PROJECT_NAME and $GCP_ZONE. Change the hardcoded tags to --tags=$GCP_VM_NAME

This information was not in Claudio's doc. We could save a lot of time and effort by stating which OCP version to use.
Maybe it was already in there and I missed it somewhere?

No, you didn't miss anything. The original version of the document mentioned the use of OCP 4.7. I tested on 4.8. As you correctly mentioned, we need to explicitly mention which versions we tested.
I will fix this

It would be simple if the tags command were referencing $GCP_VM_NAME like the command references $GCP_PROJECT_NAME and $GCP_ZONE. Change the hardcoded tags to --tags=$GCP_VM_NAME

You're right about the tags. But I was treating the document as being provided to Customers. In this case, they should not (?) have several virtual machines with Control Plane. Accordingly, the issue with the firewall will be irrelevant.
If we want to make this process as flexible as possible for our testing, then I have one more suggestion. I think you encountered this when creating firewall rules. GCP does not allow to create firewall rules with the same name. Perhaps we should use the VM name as a prefix/postfix. But in general, I don’t really like this idea, it seems to me more suitable for testing

Very good thoughts, i personally really like that idea for our testing since it would allow someone that was unfamiliar with the inner workings of GCP to get through easily. At the end of the day i don't see this as a "big deal" because more than likely there will not be more than one person testing at a time. I definitely do see your point. This is great work, and a really long doc. Just pointing this out incase we get in a position where multiple people are testing at the same time.

I kept hitting this error while trying to install the Operator. It happened on OCP 4.10 and 4.9. "apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; "
Turns out that the cluster must be an OCP Cluster <= v4.8 as 4.8 uses Kubernetes 1.21.

Fixed, I mentioned testing versions with reference document about changes in CRD

It would be simple if the tags command were referencing $GCP_VM_NAME like the command references $GCP_PROJECT_NAME and $GCP_ZONE. Change the hardcoded tags to --tags=$GCP_VM_NAME

Fixed, replaced tags with GCP_VM_NAME and firewall rules like rule-name-GCP_VM_NAME to support our testing purpose.

You copy the helm values file to konnect-dp.yaml. Then later we apply a helm overrides file with oc apply? This does not work. This should be an instance of the Kong operator.

Totally correct. Rewrited this section

This is not required at this point. The task was for mesh.


Response content-type change

Right now when you change Response Content Type in select list the format of response isn't change - path is set on initialization. write a little fix for it - switch between json and xml.

I have used @aurelian pull request to sync the swagger-ui assets


Added Ugly Numbers code.

I have added Ugly Numbers program code. I am trying to participate in hacktober fest. Please accept my pull request.

@all-contributors add @Apurva-K-S for code


Adding footer

🎇 Description
feature is to add footer at the end of the website, currently website doesn't have one
🖼 Screenshots
No response

actually there is footer, but its not visible due to linking wrong classes in css
i have fixed that already in this PR #70

ok, i'll close this issue. thank you !!


Sylius 1.12 updates

Untested changes to upgrade to Sylius 1.12

Thanks @jmwill86
Can you also add it to the build matrix so CI also tests this new version?
https://github.com/stefandoorn/sitemap-plugin/blob/master/.github/workflows/build.yml#L26

I've pushed some changes to master so everyone can at least install using Sylius v1.12 from dev-master - but build still red on all kind of errors.. that still needs a bit of a look into.

Hi @stefandoorn!
In ecs.php change ContainerConfigurator type to ECSConfig. It will fix your error :).

Thanks!

@stefandoorn any plans to merge?

I did put some time into this a while ago but if I remember there were conflicting packages that made the version constraints testing matrix difficult/impossible. I think we may need a major version bump, but it's a while since I've looked into this.

I only added v1.12 back then to the matrix, as there were too many conflicts and issues arising with the previous versions. So for then I decided only to test with the latest Sylius version, and maybe try to add older versions back into the matrix and see what happens.
Most of the changes in this PR have been implemented already, so I think we can close this one. For sure thanks for the suggestions, as they have been applied separately.
Hope we can add some PR's to add e.g. Sylius v1.11 again and maybe Symfony 6.


[Bug] Lack of compability with Crafting Station: JEI Edition

Though Crafting Station: JEI Edition is compatible with JEI and EMI is compatible with JEI, there is still a little imcompability between them.

GUI overlap
Crafting station doesn't support instant crafting. No matter how you click stack or recipe, items are just filled into the slots but no crafting.

(Though Crafting Station: JEI Edition is open source, it doesn't accept issue, so I can only comment this issue under its curseforge comments page, and report it here.)

Can you enable the dev exclusion area setting and send this screenshot again?

I can't craft into inventory or craft into cursor. I can only fill in the slots.

This mod isn't defining any exclusion areas to EMI or JEI, so EMI can't move out of the way. They need to specify them in a plugin.


Upgrade to 11.0 SP9

This needs to be tested against 11.0 SP9 and upgraded if necessary.

Hi,
with some minor changes this will also work for SP9, see my pull request.
One remark:
This project is at the first glance 'yet another GUI' example. But one interesting feature isn´t mentioned in the readme.
This example shows how to handle self created HTML-buttons! Handling HTML-elements is a little bit different than handling the standard Aras GUI elements.

Resolved by pull request #2. Closing this issue.


Move addresses to separate table

In order to optimize stats selects
Move addresses from division & legal_entity to separate table

some division's addresses are not added to division_addresses.
Ex. at the moment there are 4 divisions, which addresses do not represented in division_addresses
division_id
091c9efa-37fd-44c9-a7d1-a5249ae7ff26
439456c7-67a2-4d8d-bf6a-ea135cfd68e6
998b224b-6ae8-443e-8f54-8bde72817174
aab1911e-4a3f-48d9-9b18-8125510eafb7


inconsistent use of species_id

In the retriever, species_id refers to the column before AOU. In this project, we use species_id as a synonym for AOU.
What's the best way to avoid inconsistency when we try to do things like join the species table to the abundance table? We could change get_species_data with one line of code, but we'd still have this inconsistency between our database and our R code. Or we could change all instances of species_id to match the database, but that seems like a pain.

Assuming the AOU's are all unique (which they should be), I'd probably vote for removing the species_id line from the Retriever scripts (both BBS and BBS50) since AOU is already the equivalent and more useful field for a primary key.

Should I file an issue/PR on the retriever?

That would be great!

Actually, on further review, I think the earlier column could be useful.  Apparently, it contains the identifiers used in the "56th Supplement to AOU Check-list of North American Birds," which could be valuable for matching with other data sets.
The identifiers in the AOU are only used for internal BBS purposes, and would thus be less useful for linking the data set to others.
(that's not a typo: the AOU's identifiers are in the seq column, and the BBS's internal identifiers are in the AOU column)

Ah, I misread the code when looking at it as well. I have no strong feelings on how to manage this in our code.


Guarantee ordering for SignalR client HttpConnection.send #10780

Resolves #9901

I only evaluated the runtime changes, not the build changes.


[LIVY-987] NPE when waiting for thrift session to start timeout.

What changes were proposed in this pull request?
Fix NPE when waiting for thrift session to start timeout.
https://issues.apache.org/jira/browse/LIVY-987
How was this patch tested?
manual tests by beeline and set timeout to 10s.
0: jdbc:hive2://username:password@thrift-server> select 123;
RSC client is executing SQL query: select 123, statementId = 681bc017-8f37-4665-a575-da355db77254, session = SessionHandle [c17f1729-6ee1-4260-b82b-aebec3b08e14]
Livy session has not yet started. Please wait for it to be ready...
Error: java.util.concurrent.TimeoutException: Futures timed out after [10000 milliseconds] (state=,code=0)
0: jdbc:hive2://username:password@thrift-server> Closing: 0: jdbc:hive2://username:password@thrift-server
Please review https://livy.incubator.apache.org/community/ before opening a pull request.

Can we add a UT to ensure that such problem will not appear again in the future?

Can we add a UT to ensure that such problem will not appear again in the future?

thank you for your reply. Of course, please review again.

Codecov Report

Merging #416 (c2ad37a) into master (5dccc47) will decrease coverage by 36.92%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master     #416       +/-   ##
=============================================
- Coverage     65.50%   28.58%   -36.92%
+ Complexity      952      378      -574
=============================================
  Files           103      103
  Lines          6062     6062
  Branches        916      916
=============================================
- Hits           3971     1733     -2238
- Misses         1542     3976     +2434
+ Partials        549      353      -196

see 86 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Looks good, only a question and a minor style change

My point is that this test is used to cover the case where Furetur#isCompleted is true.

This may be a bit redundant. If you suggest removing it, I can add a commit to this PR to remove it,

LGTM

I am having some problems to merge this as the current script requires Python2 while I have only python3 on my M1 OSX and installing python 2 is not easy. We should probably migrate the merge script to python3. I will try and do that in the next days, but if someone else wants to merge this, LGTM


[Concurrency] Imported macros are actor independent

Macros are thread safe. Marking them actor-independent will avoid
imported macros being reported as not concurrency safe.
Fixes: rdar://73203807

@swift-ci please smoke test

@swift-ci please smoke test


Feature/logfile

Added a flag to define a log file that saves the log seperatly.

i've no idea why github didnt send any notifications for your last message, so sorry about that; i'll pull the branch and see why that test is failing

ok, so i ran this a couple of times over the last 2 weeks and it does fail sometimes with timeout. There have been some fixes for tests in the meantime, could you try to rebase on latest and push? Thanks

Thank you for your answer, i did the rebase. Hope it works now.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@4ca8170). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage        ?   66.14%
=======================================
  Files           ?      156
  Lines           ?     9347
  Branches        ?        0
=======================================
  Hits            ?     6183
  Misses          ?     2498
  Partials        ?      666

Flag
Coverage Δ

e2e
50.39% <0.00%> (?)

integration
57.31% <0.00%> (?)

unittests
47.19% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

cool, the tests run now; just need to signoff for the DCO

seems this didnt get any updates since last year; i'll comandeer later on and merge


Compilation failed on ubuntu 18.04 LTS

while compiling ktls_test tool failed.
make[2]: Leaving directory '/home/localadmin/Integration/tools/contributed/tls_ext/test_ktls/ktls_test/wolfssl'
make[1]: Leaving directory '/home/localadmin/Integration/tools/contributed/tls_ext/test_ktls/ktls_test/wolfssl'
+ cd -
/home/localadmin/Integration/tools/contributed/tls_ext/test_ktls/ktls_test
+ gcc -I./wolfssl tls_server.c -L./wolfssl/src/.libs -lwolfssl -lm -o tls_server
tls_server.c: In function ‘config_ktls’:
tls_server.c:71:39: error: storage size of ‘crypto_256’ isn’t known
  struct tls12_crypto_info_aes_gcm_256 crypto_256;
                                       ^~~~~~~~~~
tls_server.c:91:19: error: ‘TLS_CIPHER_AES_GCM_256_KEY_SIZE’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_128_KEY_SIZE’?
      (key_size != TLS_CIPHER_AES_GCM_256_KEY_SIZE)) {
                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                   TLS_CIPHER_AES_GCM_128_KEY_SIZE
tls_server.c:91:19: note: each undeclared identifier is reported only once for each function it appears in
tls_server.c:115:6: error: ‘TLS_1_3_VERSION’ undeclared (first use in this function); did you mean ‘TLS_1_2_VERSION’?
    : TLS_1_3_VERSION;
      ^~~~~~~~~~~~~~~
      TLS_1_2_VERSION
tls_server.c:119:6: error: ‘TLS_CIPHER_AES_GCM_256’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_128’?
    : TLS_CIPHER_AES_GCM_256;
      ^~~~~~~~~~~~~~~~~~~~~~
      TLS_CIPHER_AES_GCM_128
tls_server.c:203:35: error: ‘TLS_RX’ undeclared (first use in this function); did you mean ‘TLS_TX’?
   if (setsockopt(sockfd, SOL_TLS, TLS_RX, crypto_info,
                                   ^~~~~~
                                   TLS_TX
tls_server.c: In function ‘servelet’:
tls_server.c:273:29: error: ‘TLS_GET_RECORD_TYPE’ undeclared (first use in this function); did you mean ‘TLS_SET_RECORD_TYPE’?
        (cmsgh->cmsg_type == TLS_GET_RECORD_TYPE)) {
                             ^~~~~~~~~~~~~~~~~~~
                             TLS_SET_RECORD_TYPE
sh: 1: ./tls_client_12: not found

OS:
Distributor ID: Ubuntu
Description:    Ubuntu 18.04 LTS
Release:        18.04
Codename:       bionic

kernel:
Linux 5.10.30-051030-generic x86_64

Looks like you're either missing kernel headers or the TLS feature wasn't enabled in your kernel. All of those defines should be found under /usr/include/linux.


Documentation wrong?

In https://github.com/peter-winter/ctpg?tab=readme-ov-file#regular-expressions it says the sequence for escaped character in hex format is:
\\x20

But in my tests it looks like it is actually
\x20

And thanks for the project. I find it great :) .

Yes. Nicely spotted. Thank you.
Thank you for the kind words, it means a lot.


add support to log in to private registry for non-dockerhub images.

this will allow using private registries that are protected by password login.

PG1 1132

PG2 1028

rebased and merged in 2d52ba03ca35684a5b7c58f27d68b45d17e2831b


Fix for background activities trying to register the plugin

Added a check to registerWith to prevent background flutter view from trying to register the plugin, as there won't be any activity.
Fixes #65

It does yes.

I am also running it in my project to test and so far so good

Hi, unfortunately I have no iOS development experience. Not even sure this is an issue on iOS.


https://probot.github.io/api/ pages 404'ing

The Probot "Reference" side nav links that should go to api/latest pages currently result in a 404 page.  This includes Probot, context, run, and createNodeMiddleware links.

Link section in question
Probot, context, run, & createNodeMiddleware linksjust lead to this sad Probot

The probot.github.io/blob/master/api/latest directory appears to be correctly symlinked to the latest version, assuming there hasn't been some other repo change that would consume the symlink differently than it has been for a while.
The probot.github.io/tree/master/api/12.2.1/classes directory appears comparable to the 12.2.0/classes directory (of course that comparison assumes the api pages were generated and deployed as expected with the 12.2.0 docs [1]).
Hopefully, someone who knows this repo and documentation process, better than I, can figure out why the api directory is 404ing.
[1]: Sadly, the only snapshot is from way back in 2020.

It seems like we updated typedoc recently, which changed the way these names were generated. Thank you for reporting this, I'll fix it soon.


Add link from README to Open Service Broker API

Should have gotten this in the last PR.  Oops

LGTM

I think we would all be fine if you shoved it in the previous PR.
LGTM anyway.

LGTM


Cannot initiate a deposit while processing another deposit

Actual deposit:

Error:

Console logs:

This issue isn't correct (witness several other issues from folks who were doing multiple deposits at a time successfully). The transaction in question here (https://ropsten.etherscan.io/tx/0x23f0c73e2349d8d8ee747fed3a74ea4fdfa38c79c081435506f2601f45035841) ran out of gas. I'm interested in finding out why that is compared to others, so if you run into any other transactions that run out of gas, please open an issue with the URL, transaction id, etc. I'm going to close this issue for now as we haven't seen issues dealing with parallel deposits that I know of, and the transactions in question don't seem to be affected by parallelism issues.

@Shadowfiend
It wasn't out of gas because I had more than enough Ropsten ETH.


UI for new types of questions

UI for the new types of questions added for: https://github.com/rancher/rancher/issues/27926

Instead of relying solely on questions.yml to create the deploy/launch applications pages for these applications, we will be creating custom forms for our applications.
Any other applications can use the standard questions.yml format that we had supported previously.
Those set of questions should be supported with #837


MetaR object has no attribute 'relation_learner'

Please how to solve this problem？
What is 'relation_learner' ?

I've tried the code, and there is no problem. Did you change the code or use your own dataset? Could you please give more details? Thanks!


Unable to login (Bad Gateway)

Script
nginx-proxy-manager
Describe the bug
Unable to login, get "Bad Gateway" error message
System info:

Proxmox Version: 7.3-6
Alpine Version: 3.17.2

Screenshots

Additional context
I have tried to upgrade with the setup.sh script again but got the same error that #103
So I am unable to use Nginx Proxy Manager
Can someone help me please ?

I am getting the same error
System info:

Proxmox Version: 7.2-3
Debian GNU/Linux 10 (buster) (LXC)
Installation on a existing debian 10 lxc
Nginx Proxy Manager (NPM) v2.9.19

Describe the bug
At first I installed using the installation script that creates the LHK container and got an error after rebooting.
After that, I decided to try installing it again through the "alternative usage".
My actions:

Installed the Debian 10 LXC
Updated Debian and installed NPM
Made a live backup LXC
Logged into NPM with a standard username and password
Changed the login and password.
Uploaded my hosts and got certificates (everything worked fine).
After 12-16 hours, I tried to login to npm to change my hosts, but got "Bad Gateway" on login.
Restored the LXC container from backup and repeated step 4-6
Turned off the container and made a backup to restore it with my login password and hosts.
Turned on the container, tried to enter but immediately received "Bad gateway" at the entrance.

ps. sorry my english can be bad

Update node js to current version. It worked for me.


FD-007.3 Customize styling member app google form

We will be keeping our current google form instead of building a new form to store our user data. The current google member form will be used for our users to sign up to be on our app. Now we want to customize the styling to match our theme
Since we have embedded the Google Form in our website and want to customize the CSS to match the theme of our website, we can achieve this by applying custom CSS styles to the elements of the embedded form. Here's how we can do it:
Step 1: Identify the Google Form Elements
Inspect the elements of the embedded Google Form using your browser's developer tools. This will help you identify the HTML structure and classes used by the form elements. You can right-click on the form fields and choose "Inspect" or "Inspect Element" to open the developer tools.
Step 2: Create Custom CSS
In your website's CSS file, you can create custom CSS rules to target and style the specific form elements you identified in Step 1. You can override the default styles provided by Google Forms with your own styles to match your website's theme.
For example, let's say your embedded Google Form has a text input field with the class "entry-field". You can style it with the following custom CSS:
/* Example custom CSS to style the text input field */
.entry-field {
  background-color: #f5f5f5; /* Change the background color */
  border: 1px solid #ccc; /* Change the border */
  padding: 10px; /* Add padding */
  color: #333; /* Change the text color */
  font-size: 14px; /* Change the font size */
  /* Add any other styles you want to customize */
}

You can apply similar custom CSS rules to other form elements like checkboxes, radio buttons, select dropdowns, etc., to style them according to your website's theme.
Step 3: Include Custom CSS in Your Website
Make sure to include your custom CSS file in your website's HTML. You can link the CSS file in the <head> section of your website's HTML code:
<head>
  <!-- Other meta tags and links -->
  <link rel="stylesheet" href="path/to/your/custom.css">
</head>

Step 4: Test and Refine
After applying your custom CSS, test your embedded Google Form to ensure that the styles are as you intended. You may need to make adjustments to the CSS as necessary to fine-tune the appearance and ensure it matches your website's theme.
Remember that the ability to customize the form's appearance through CSS is limited to the elements exposed by Google Forms. More advanced customizations might not be possible through CSS alone.
As a best practice, always test the form on various devices and browsers to ensure it looks good and functions well across different platforms.
Use this figma as a reference:

Hi. I can work on this issue. Please assign it to me

Hi. I can work on this issue. Please assign it to me

Upon further investigation I see i can use an attribute "srcdoc" to embed the custom form and it should still work like the external form


Add github & slack integration to portainer/portainer repo

Hello!
Is it possible to add "github & slack integration"(https://github.com/integrations/slack) app to portainer/portainer repo?

Link to setup https://github.com/apps/slack/installations/new

Done.

Are you sure?

Either the app isn't installed on your repository or the repository does not exist. Install it to proceed.
Note: You need to be an organization owner to install the app (or ask one to install it for you).

Yes.

Unfortunately it doesn't help

Ping me on slack, I believe this is not the place to tackle this problematic.


Abstraction dev tools

Objective

Fixes #12368

Solution

Create DevTool that holds unique id and state.
Create DevToolsStore resource that stores new DevTools.
Make existing tool use new abstraction

I'm not convinced we should have a "dev tool" abstraction like this:

What constitutes a "dev tool" is extremely nebulous. I do not think there is a good clear line between a "dev tool" and a "bevy engine feature".
This moves configuration outside of the standard "ECS resource" pattern and into a consolidated DevToolStore resource. This increases the clunkiness of accessing dev tool config significantly and makes it impossible to use ECS change detection to determine when the config has changed.
If we want to expose an existing Bevy feature in some "dev tool debug interface", we shouldn't need to refactor how it is configured.
The motivation appears to be "we want a queryable catalog of dev tools and their configuration, with a common on/off switch". I would argue that "Dev tool" is too general of a concept to be a useful generic "category of thing". Instead, consumers of Bevy features (such as a "dev tool debug interface") should be responsible for choosing what Bevy features to expose and how to expose them (including what it means to enable and disable a feature). The "dev tool debug interface" can be responsible for being the catalog of features to expose.
If we really need a "common on/off switch", that is something that should be considered holistically. However without consideration for the lifecycle of adding/removing features (systems, config, etc), I don't think this would provide significant value. Instead, just add enabled: bool to whatever feature-config resource makes sense. It should be easy to bind specific bool values to whatever debug interface we are building.

I think, if we were to embrace a generic pattern like this, it should be done at the Plugin level and after significant consideration about "plugin/feature configuration and lifecycles".

@cart I understand your concerns. I'll aim to write up a proper response and design vision in an RFC, and link it here (and the linked issue). I think there's very good reasons to want a cohesive method of control (even if this might not be the best possible design), but those aren't clearly articulated anywhere.


Add atan signature with two input

To be a little bit more compliant with GLSL spec atan function has two signatures.
See here: https://www.khronos.org/registry/OpenGL-Refpages/gl4/html/atan.xhtml

Thank you, @nkint - I was aware of the two arities, but settled for the 1-arg version so far, since the other sig would also need special treatment in the JS code gen and I was hoping to work on this as part of #96. So I'd propose we do support the 2 arities of the atan builtin, but emit only the single arg version (by first dividing a over b, if needed), at least for now:
export function atan<T extends Prim>(a: Term<T>): FnCall<T>;
export function atan<A extends Prim, B extends A>(a: Term<A>, b: Term<B>): FnCall<A>;
export function atan(a:Term<any>, b?: Term<any>) {
    return b
        ? builtinCall("atan", a.type, div(a, b))
        : builtinCall("atan", a.type, a);
}

Actually, since the 2 atan versions have different output ranges [-π/2, +π/2] (single arg) vs [-π, +π] (2 args), it should be like this:
export function atan<T extends Prim>(a: Term<T>): FnCall<T>;
// prettier-ignore
export function atan<A extends Prim, B extends A>(a: Term<A>, b: Term<B>): FnCall<A>;
export function atan(a:Term<any>, b?: Term<any>) {
    return b
        ? mul(builtinCall("atan", a.type, div(a, b)), 2)
        : builtinCall("atan", a.type, a);
}

(also adding prettier-ignore to keep fn overloads more easy on the eye)

This will make it temporarily minutely slower, but at least is correct... and once the function dispatch updates (#96) are done, we can update this here once more

Soo... scrap my 2 last comments, the differences are (sadly) quite different. See this little comparison I just made: http://glslsandbox.com/e#56557.0

So, let's just keep your version and I will add a note to the readmes that atan w/ 2 args is not supported by the JS code gen yet...

Also just once more for reference (note to future self): https://en.wikipedia.org/wiki/Atan2#Definition_and_computation


[WIP] Template prep kit box barcode fix (service)

Closes #
-Failing lint currently
Changes proposed in this pull request:
Back end changes for moving template_prep_kit_box_barcode to library from run
Coupled with ui PR: https://github.com/sanger/traction-ui/pull/495

Changes CSV generator to use library template prep kit box barcode
Removed template prep kit box barcode from run model
Replaced library kit barcode with template prep kit box barcode for libraries

This PR contains migrations

Just to bear in mind data migration :) might need a rake task

Just to bear in mind data migration :) might need a rake task

I don't think it should be necessary. We will just need to check that the template prep kit box barcodes are the same as the library kit barcode.


add support for PlantUML.

Hello I'm not an expert with Plantnum but I would like to avoid adding this type of hidden dependencies in the lib. If it's really something we want to support I'm happy to add it in the dependencies but i would need a little bit of context.
Can you show what is not achievable with the current implementation, why it's important for us to support it and  what should be doneto install it (I hope that it's a simple pp install but never know.... #graphiz)

From my point of view, plantuml is a common uml plot which makes sense to support.
As there is obviously demand for it and eralchemy was always meant to bea expandable and have different export types, i do see it as a favorable contribution.
Have to look through the changes in the next days though

I just tested it and found that https://pypi.org/project/plantuml/ does not work if six is not installed, which is not given as a dependency of it, and it does not seem to be supported as well.
So I would vote for taking this PR without the plantuml lib and instead directly call:
import base64
from zlib import compress
zlibbed_str = compress(plantuml_text.encode('utf-8'))
compressed_string = zlibbed_str[2:-4]
return base64.b64encode(compressed_string).translate(b64_to_plantuml).decode('utf-8')

instead of deflate_and_encode from an unmaintained new lib?

@noboruatkek would you still like to work on this? Generally, I think that PlantUML is a very useful contribution to this library.


Possible Issue with Mod Author?

I was not sure where to post this since there is no Discord link on your CurseForge page or website to contact you privately and I wanted you to be aware of something:
MJRLegends recently made a mod that is an add-on to Galacticraft. It is exact to how you progress or do things in Advanced Rocketry. Here is a link to the screenshot with the description in case he decides to change it later and claim this is being fabricated to make him look bad:
The mod: https://minecraft.curseforge.com/projects/planet-progression
The description: https://imgur.com/a/dr5fI
A friend of mine spoke to him about it when he first discovered the mod and shared this with me. MJRLegends' answer was not nice and in my opinion was outright disrespectful, especially given the fact that both of you are mod authors.
Our conversation: https://imgur.com/a/pUaQm
I don't know if there is anything you can do, but I felt that you should be aware of what is going on. If I can help in any way, please let me know.

Thanks for letting me know.  Advanced Rocketry is technically released under the MIT license so there's nothing stopping him from using the assets from AR if he really wanted to.
That being said, I do find his comment about Advanced Rocketry being "trash" kind of amusing despite the fact he's going along with identical concepts.
Hopefully he'll help add some more variety into the space stuff for MC.  I might actually take a look and see about adding integration.  Though it doesn't look like there's much yet to integrate to.


ApplicationArchitecture  - fix example

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Always
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

Check out the picture to get more

Last commit contributes to:

ApplicationArchitecture - add an abstract API to the Data layer follow up #184

Review and close this issue.

contributes to the

ApplicationArchitecture - add an abstract API to the Data layer follow up #184


Header moves to the right after F5

I have a table with a lot of columns. If I scroll horizontal to the right and then reload the page (F5), the header moves to the right, but not the rest of the columns. So the alignment doesn't work. I'm not sure, if it is a bug or if I'm just missing a parameter. I have to apologise, because my example doesn't work correct on jsfiddle, because you can not reload the frame. But you can download the html with script and should reproduce locally. Btw on your homepage (http://mkoryak.github.io/floatThead/#issues) you link to jsfiddle.com, but you have to link to jsfiddle.net
You can find the example here: https://jsfiddle.net/8ggygd81/2/
specs:

Windows 7
FF 51.0.1
JQuery 1.10.2
floatThead 2.0.0

Thank you for your work.
Dominik

this is fixed on master


[KOGITO-3960] Store OLM logs for PR checks and nightly builds

Signed-off-by: Karel Suta<EMAIL_ADDRESS>https://issues.redhat.com/browse/KOGITO-3960
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test

/jenkins test

/jenkins test

No space left on device
Lets try it again
/jenkins test

/jenkins test

/jenkins test

Seems better now, but the failure seems to be related to environment:
2020-12-03 16:10:51  | 2020-12-03 16:10:51  |        | dmn-drools-quarkus-metrics-86578cdcb4-vnjk5.164d40c3c1448f98  | -     | -                                            | Warning  | Evicted              | -        | -                  | -                                 | The node had condition: [DiskPressure].

/jenkins test


Return buildId when starting build

To insert build url into a report, you need a buildId, for example:
http://localhost:8080/40da0b32-8e01-4296-89e8-453e89f5eb50?buildId=d6bdd77c-59ad-4717-9548-58db501a385a
Now we can't get buildId.

backend updated
SDK will be updated in according task


WIP: Add Multiple Accounts to Settings page.

Adds a "Multiple Accounts" Bucket to the settings page.
Should be able to Enable / Disable Multiple Accounts.
Should be able to Add rows of accounts.
Should be able to delete rows of accounts. (Excluding the first row)
Data should end up stored as an array of objects [{ robinHoodValue: '' }]
Currently does NOT sanitize data
Currently does NOT validate input

Just a heads-up, I was thinking about scraping the Robinhood account username and using it as a name on the properties, as a way of allowing multiple accounts to be set up.

Just a heads-up, I was thinking about scraping the Robinhood account username and using it as a name on the properties, as a way of allowing multiple accounts to be set up.

Okay. Definitely will need a bit of cleanup, but should be functional at this point.

Okay. Definitely will need a bit of cleanup, but should be functional at this point.

I'm going to plan to take a look a this over the weekend!

I'm going to plan to take a look a this over the weekend!

I'm going to plan to take at look a this over the weekend!

Yeah, hopefully I'll get to look at it some more and clean it up before then. A bit more swamped than usual due to the shorter work week.

I'm going to plan to take at look a this over the weekend!

Yeah, hopefully I'll get to look at it some more and clean it up before then. A bit more swamped than usual due to the shorter work week.

Closes #16

Closes #16


Add more tests for validating EOF subcontainer kinds

🗒 Description
Test cases that check subcontainer validation in a deeply nested subcontainer, and in code sections other than section 0.
🔗 Related Issues

✅ Checklist

[ ] All: Set appropriate labels for the changes.
[ ] All: Considered squashing commits to improve commit history.
[ ] All: Added an entry to CHANGELOG.md.
[ ] All: Considered updating the online docs in the ./docs/ directory.
[ ] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[ ] Tests: A PR with removal of converted JSON/YML tests from ethereum/tests have been opened.
[ ] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[ ] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

Also, could we add this PR to the changelog in the same format as other EOF PRs? Thanks.


PostSolve contact callback reports zero normal impulse.

We are seeing a zero normal impulse reported when a dynamic body with a circle shape hits a static body polygon box shape under a large gravity and high restitution running at 120Hz as demonstrated here:
https://gist.github.com/MelvMay-Unity/605ac702a0943fafd1752013c5d4df29

Closing this until I can get more detailed information on reproducing the test case.


Are you storing feeds in a single JSON file?

I looked at the code and it looks like the feeds are stored in the portal.json file. Won't it get really slow parsing a single file once feeds starts to grow?
@pfrazee started to work on a dat shared indexed db: https://github.com/beakerbrowser/ingestdb Maybe it's worth the look as this looks like a perfect use case.

We'll migrate to ingest for sure. This is only temporary, while Rotonde has a bit of traffic at the moment, we're still running on a proof-of-concept code created in an afternoon.

Sure thing! Feel free to close the issue in you find in non-relevant :).

Closing, we can open a new one to discuss the ingest implementation in the future.


Entries in a set-of are not being sorted

X.690 (08/2015), section 11 (Restrictions on BER employed by both CER and DER), subsection 11.6 (Set-of components) reads:

The encodings of the component values of a set-of value shall appear in ascending order, the encodings being compared
as octet strings with the shorter components being padded at their trailing end with 0-octets.
NOTE – The padding octets are for comparison purposes only and do not appear in the encodings.

This library does not currently sort set-of components in canonical order when encoding DER.

Oh, that's right. Thank you!