text:
Vue2 errors with vue-demi

Like in https://github.com/wobsoriano/v-perfect-signature/issues/6 I get the following errors when adding library in Vue2:
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(5,34):
5:34 '"./node_modules/vue-demi/lib/index"' has no exported member named 'DefineComponent'. Did you mean 'defineComponent'?
    3 | import * as winbox from 'winbox';
    4 |
  > 5 | declare const _default: vue_demi.DefineComponent<{
      |                                  ^
    6 |     options: {
    7 |         type: PropType<winbox.Params>;
    8 |         required: true;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(31,13):
31:13 Namespace '"./node_modules/vue-demi/lib/index"' has no exported member 'ComponentOptionsMixin'.
    29 | }, {}, {
    30 |     initialize(): void;
  > 31 | }, vue_demi.ComponentOptionsMixin, vue_demi.ComponentOptionsMixin, ("onmove" | "onresize" | "onclose" | "onfocus" | "onblur")[], "onmove" | "onresize" | "onclose" | "onfocus" | "onblur", vue_demi.VNodeProps & vue_demi.AllowedComponentProps & vue_demi.ComponentCustomProps, Readonly<{
       |             ^
    32 |     options?: unknown;
    33 |     portalSelector?: unknown;
    34 |     portalComponent?: unknown;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(31,45):
31:45 Namespace '"./node_modules/vue-demi/lib/index"' has no exported member 'ComponentOptionsMixin'.
    29 | }, {}, {
    30 |     initialize(): void;
  > 31 | }, vue_demi.ComponentOptionsMixin, vue_demi.ComponentOptionsMixin, ("onmove" | "onresize" | "onclose" | "onfocus" | "onblur")[], "onmove" | "onresize" | "onclose" | "onfocus" | "onblur", vue_demi.VNodeProps & vue_demi.AllowedComponentProps & vue_demi.ComponentCustomProps, Readonly<{
       |                                             ^
    32 |     options?: unknown;
    33 |     portalSelector?: unknown;
    34 |     portalComponent?: unknown;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(31,197):
31:197 Namespace '"./node_modules/vue-demi/lib/index"' has no exported member 'VNodeProps'.
    29 | }, {}, {
    30 |     initialize(): void;
  > 31 | }, vue_demi.ComponentOptionsMixin, vue_demi.ComponentOptionsMixin, ("onmove" | "onresize" | "onclose" | "onfocus" | "onblur")[], "onmove" | "onresize" | "onclose" | "onfocus" | "onblur", vue_demi.VNodeProps & vue_demi.AllowedComponentProps & vue_demi.ComponentCustomProps, Readonly<{
       |                                                                                ^
    32 |     options?: unknown;
    33 |     portalSelector?: unknown;
    34 |     portalComponent?: unknown;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(31,219):
31:219 Namespace '"./node_modules/vue-demi/lib/index"' has no exported member 'AllowedComponentProps'.
    29 | }, {}, {
    30 |     initialize(): void;
  > 31 | }, vue_demi.ComponentOptionsMixin, vue_demi.ComponentOptionsMixin, ("onmove" | "onresize" | "onclose" | "onfocus" | "onblur")[], "onmove" | "onresize" | "onclose" | "onfocus" | "onblur", vue_demi.VNodeProps & vue_demi.AllowedComponentProps & vue_demi.ComponentCustomProps, Readonly<{
       |                                                                                ^
    32 |     options?: unknown;
    33 |     portalSelector?: unknown;
    34 |     portalComponent?: unknown;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(31,252):
31:252 Namespace '"./node_modules/vue-demi/lib/index"' has no exported member 'ComponentCustomProps'.
    29 | }, {}, {
    30 |     initialize(): void;
  > 31 | }, vue_demi.ComponentOptionsMixin, vue_demi.ComponentOptionsMixin, ("onmove" | "onresize" | "onclose" | "onfocus" | "onblur")[], "onmove" | "onresize" | "onclose" | "onfocus" | "onblur", vue_demi.VNodeProps & vue_demi.AllowedComponentProps & vue_demi.ComponentCustomProps, Readonly<{
       |                                                                                ^
    32 |     options?: unknown;
    33 |     portalSelector?: unknown;
    34 |     portalComponent?: unknown;
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(47,23):
47:23 Cannot find namespace 'WinBox'.
    45 | }>;
    46 |
  > 47 | declare const WinBox: WinBox.WinBoxConstructor;
       |                       ^
    48 | declare function useWinBox(): (options: WinBox.Params) => winbox;
    49 |
    50 | export { _default as default, useWinBox };
ERROR in ./node_modules/vue-winbox/dist/index.d.ts(48,41):
48:41 Cannot find namespace 'WinBox'.
    46 |
    47 | declare const WinBox: WinBox.WinBoxConstructor;
  > 48 | declare function useWinBox(): (options: WinBox.Params) => winbox;
       |                                         ^
    49 |
    50 | export { _default as default, useWinBox };

When I have "skipLibCheck": true I get
WARNING  Compiled with 1 warning
 warning  in ./node_modules/vue-winbox/dist/vue-winbox.esm.js
"export 'Teleport' was not found in 'vue-demi'

Despite the error it seems to be working though.

this problem still stands. is there a fix for the warning to not pop up ? The UI works fine for me as well..

Module parse failed: Unexpected token (72:8)
You may need an appropriate loader to handle this file type.

repo: wobsoriano/vue-winbox


text:
npm run start

运行start 无法启动项目
pnpm run start:vue2 单独运行 vue2 项目 报错

前提条件：你每个子应用的依赖有没有安装好，npm run install 无法成功后，就单个应用里面去安装

已经搞好了.跟你类似的思路处理

source: gharchive/issue

authors: alminchen wocwin

license: MIT

license_type: permissive

license_source: github-api


text:
RROR: Unable to lock database: Permission denied ERROR: Failed to open apk database: Permission denied

How to install package in the docker4drupal container e.g. the nginx container. I tried the apk add ru y, it fails with permission denied. What's the user name and password or what's the default password for root user? thanks.

Hi,
you should try this
ocker-compose exec --user=root --privileged nginx sh

nginx is name of the container, you may have to change that.

authors: igorbiki tingan

license: mit

license_source: bigquery


text:
import github library

You wrote that importing a library with the git https clone url should work ...
Or is it a must that the imported lib is a du-lua project?
$ du-lua import https://github.com/EasternGamer/AR-Library.git
Lua CLI Utility for Dual Universe v0.6.3 by Wolfe Labs @ Node v10.16.0
Downloading library files from: "https://github.com/EasternGamer/AR-Library.git"
(node:324) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
    at validateString (internal/validators.js:125:11)
    at Object.join (path.js:427:7)
    at Function.getProjectInfo (C:\Users\tiramon\AppData\Roaming\npm\node_modules\@wolfe-labs\du-luac\library.js:178:53)
    at Function.loadExternalLibrary (C:\Users\tiramon\AppData\Roaming\npm\node_modules\@wolfe-labs\du-luac\library.js:142:37)
(node:324) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not
handled with .catch(). (rejection id: 2)
(node:324) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Ok just found out while reading the code that this is the passage that should tell me that target lib does not have a project.json ... maybe you want to fix that ;)

Fixed the typo, at last!

repo: wolfe-labs/DU-LuaC


text:
Update README.md

The link for the Swift port in README was broken, I have updated it to point to my own implementation of SymSpell in Swift.

Thank you for your SymSpell Swift port!

source: gharchive/pull-request

authors: gdetari wolfgarbe

repo: wolfgarbe/SymSpell


text:
Allow mutliple threads/cores per workflow in agent

Clear and concise description of the problem
It is possible to increase the number of workflows that run in parallel by increasing WOODPECKER_MAX_WORKFLOWS. However it seems like each workflow only gets a single CPU core/thread. I haven't confirmed this, but I did see that cargo was using only a single thread.
Suggested solution
It would be nice if we could increase the number of threads that each workflow gets. Workflows that can take advantage of many cores would benefit from this. For example, cargo will spawn multiple threads to compile things in parallel, which greatly speeds up compilation.
This should be configurable through an environment variable like WOODPECKER_MAX_THREADS_PER_WORKFLOW.
Alternative
Using multi-pipelines does allow multiple pipelines to run in parallel, which is amazing but not enough as steps like compiling one package can't be broken into multiple pipelines.
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

It looks like the code already supports (anong others) these config on a pipeline step:

cpu_quota
cpuset
cpu_shares

https://github.com/woodpecker-ci/woodpecker/blob/a884e13885b9519c6c7bf7f6e41a2f177207b50d/pipeline/frontend/yaml/container.go#L31-L34
See here for the meaning: https://docs.docker.com/config/containers/resource_constraints/#cpu
Can you try if this solves your problem.
As these are not documented ,use at your own risk

I don't have any limits placed on the agent though. It seems like the agent is placing limits on the containers it spawns. Is there a configuration for that?

Have you tried to put this into your pipeline configuration on the step / container you want more CPU?
The code says you can do something like this:
   -name: Run on more CPU
    image: debian
    cpu_shares: 100000
    commands:
     - ...

These should be the settings used by the agent to start the container, but i only started to understand the code.

re

It looks like the code already supports (anong others) these config on a pipeline step:
* cpu_quota

* cpuset

* cpu_shares

https://github.com/woodpecker-ci/woodpecker/blob/a884e13885b9519c6c7bf7f6e41a2f177207b50d/pipeline/frontend/yaml/container.go#L31-L34
See here for the meaning: https://docs.docker.com/config/containers/resource_constraints/#cpu
Can you try if this solves your problem.
As these are not documented ,use at your own risk

reminder: if it's not documented, it's a "feature" that can be refactored away at any time ... if it does get in the way ... until its officially added to the docs

how to handle resources ... is a bigger topic ..., ideas are welcome but I personally consider other issues more important for now :sweat:

authors: 6543 SeriousBug smainz

repo: woodpecker-ci/woodpecker


text:
Generalize inline ignore rules

This follows #187, which addresses #124:
I think we want a bit more syntax here to enable multiple ignores.
For example:

Ignore everything: # zizmor: ignore[*]
Ignore two or more rules: # zizmor: ignore[rulea,ruleb]

As part of this generalization, we should also probably switch to using yamlpath's comment extraction APIs.
Originally posted by @woodruffw in https://github.com/woodruffw/zizmor/pull/187#discussion_r1854915346

I thought about it a bit, and I'm going to hold off on ignore[*] for now -- that's going to be too much of a footgun.

repo: woodruffw/zizmor


text:
How to upgrade to 5.x

Hi,
I have issues upgrading remark, remark-cli or remark-lint. Currently I use these:
    "dependencies": {
        "remark": "^4.2.2",
        "remark-lint": "^4.2.0",
        "remark-lint-sentence-newline": "^2.0.0",
        "remark-validate-links": "^4.1.0"
    }

And I get valid warnings e.g. for hello.md
## Hello world!

bold

***foo***

$ remark --use remark-lint hello.md 1> /dev/null
hello.md
   1:1-1:16  warning  First heading level should be `1`     first-heading-level
   1:1-1:16  warning  Don’t add a trailing `!` to headings  no-heading-punctuation
    3:1-3:4  warning  Do not use HTML in markdown           no-html
   3:8-3:12  warning  Do not use HTML in markdown           no-html
       5:10  warning  Remove 1 line after node              no-consecutive-blank-lines

When I try to upgrade remark-lint to 5.x or 6.x, the same command outputs: "no issues found".
Same when I try using the latest remark-lint with remark-cli 3.0.0 (I already tried installing both recommended and consistent presets, and set them as presets (in remarkrc and using --use), and set them as plugins, none of which yielded warnings).

Hi @tkruse!
Sorry about that, I didn’t have time to write that info yet. I just added the info to the releases page.
I think that makes things more clear, but could you let me know if not, here or on Gitter?

Hi Titus,
The releases page still does not help me much. My problem is that I do not get any warnings any more. E.g. see this example:
    $ npm install remark remark-lint remark-preset-lint-recommended remark-preset-lint-consistent
/scripts/nodejs
└── remark@7.0.0

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.1
$ remark --use lint --use remark-preset-lint-recommended --use remark-preset-lint-consistent hello.md 1> /dev/null
hello.md: no issues found

There should be issues (see initial post), and remark-lint 4.x finds them. Do I need to pass each rule using --use? Or install more rules?

Hi Tim! 👋
remark-lint 4x find those issues because it includes the rules you want (first-heading-level, no-heading-punctuation, etc.). remark-lint 6x does not find those issues, as it’s not configured to!
If you amend your hello.md like so:
 ## Hello world!

 bold

-***foo***
+***foo*** ___bar___

And now run remark on that (remark . -u preset-lint-consistent), you’ll get messages:
hello.md
  5:11-5:20  warning  Strong should use `*` as a marker    strong-marker    remark-lint
  5:13-5:18  warning  Emphasis should use `*` as a marker  emphasis-marker  remark-lint

⚠ 2 warnings

That works because remark-preset-lint-consistent includes those rules. If you want to enable different rules, you need to use them too (or create your own preset).

I see. thanks, that helps a bit. I assumed all rules were included in the recommended set, that was my mistake. So now I  migrated my .remarkrc file. The documentation for that is also a bit weak. Before I had this:
// package.json
    "dependencies": {
        "remark": "^4.2.2",
        "remark-lint": "^4.2.0",
        "remark-lint-sentence-newline": "^2.0.0",
        "remark-validate-links": "^4.1.0"
    }

// .remarkrc
{
    "presets": ["lint-recommended", "lint-consistent"],
    "plugins": {
        "remark-lint": {
            "unordered-list-marker-style": "consistent",
            "list-item-bullet-indent": true,
            "no-multiple-toplevel-headings": true,
            "maximum-line-length": 9000,
            "maximum-heading-length": 300,
            "no-tabs": true,
            ...
        }
    },
    "settings": {
        "bullet": "*",
        "listItemIndent": "1",
        "strong": "*",
        "emphasis": "*"
    }

Now with remark-lint 6.x, it looks like this
´´´
// package.json
"dependencies": {
"remark-cli": "^3.0.0",
"remark-lint": "^6.0.0",
"remark-lint-first-heading-level": "^1.0.0",
"remark-lint-list-item-bullet-indent": "^1.0.0",
"remark-lint-maximum-line-length": "^1.0.0",
"remark-lint-no-heading-punctuation": "^1.0.0",
"remark-lint-unordered-list-marker-style": "^1.0.0",
...
"remark-lint-sentence-newline": "^2.0.0",
"remark-preset-lint-consistent": "2.0.0",
"remark-preset-lint-recommended": "2.0.0",
"remark-validate-links": "^6.0.0"
}
// .remarkrc
{
"plugins": {
"remark-preset-lint-recommended": true,
"remark-preset-lint-consistent": true,
"remark-lint-no-heading-punctuation": false,
"remark-lint-maximum-line-length": 40,
...
},
"settings": {
"bullet": "",
"listItemIndent": "1",
"strong": "",
"emphasis": "*"
}
´´´
That was quite painful to find out for me, maybe I was not seeing the obvious. I recommend you write a small migration guide, with the necessary steps, e.g.:

in remarkrc, convert presets to plugins
in remarkrc, extract remark-lint rule configuration as plugins (if desired)
in package.json, install all individual plugins and presets (used in remarkrc), name is prefixed with "remark-lint-" (unless installed by presets?)
give small example of new structure

It is quite painful to migrate, because normally a project will already have markdown files satisfying most rules, so to confirm that after the migration, the configuration still works, one would have to manually try violating each rule and check that this still generates a warning. (That way I just found out in my 4.x version, "no-multiple-toplevel-headings": true, had no effect).
Another thing I notice is that remark will not produce an error for adding a disabled non-existing plugin, like:
       // in .remarkrc
        "remark-lint-hsadgafdfdsa": false,

that is a little annoying when trying to make sure preset rules are being disabled.
Is there a way to run remark and print a normalized configuration? Such as what individual rules are provided by presets, which rules are activated after applying presets and other rules?
Also I tried to install

vhf/remark-lint-no-empty-sections
vhf/remark-lint-no-url-trailing-slash

But those did not generate any warnings for me(did not try with 4.x). Do they need to be changed to work with remark > 5.x? (might be nice to notify the authors of plugins).
Also I see on npm that there are several more rule packages by you which seem not to be included in the presets, nor mentioned in the remark-lint README, in particular regarding definitions and tables.
What I would love to do is to enable a large such set of rules for a project, then see by the warnings which rules would be useful to include. Is there any easy way to get that (e.g. a remark-lint-preset-all-wooorm)?

So now I migrated my .remarkrc file. The documentation for that is also a bit weak.

I’ve updated the releases page with some examples. I’d gladly accept a PR on docs or an issue for more if you have suggestions.

Is there a way to run remark and print a normalized configuration? Such as what individual rules are provided by presets, which rules are activated after applying presets and other rules?

Use the DEBUG="*" env variable.

might be nice to notify the authors of plugins

That’s exactly what I’ve been doing the last two weeks.
I’ve also mentioned which rules are not updated yet.

Also I see on npm that there are several more rule packages by you which seem not to be included in the presets, nor mentioned in the remark-lint README, in particular regarding definitions and tables.

Rules are listed here.

What I would love to do is to enable a large such set of rules for a project, then see by the warnings which rules would be useful to include. Is there any easy way to get that (e.g. a remark-lint-preset-all-wooorm)?

How would that deal with configurable rules?
I think that’s a good idea. Would you be interested in creating a preset for that?

thanks for the doc updates. I wish I had the tie to help coding, but sadly, I don't.

Cheers! Contributions to docs are also greatly appreciated!

authors: tkruse wooorm

repo: wooorm/remark-lint


text:
Cannot publish

Hi,
I couldn't publish my package with 'npm publish' command. It throws 404 error:
c:\sandbox\how-to-npm>npm publish npm ERR! publish Failed PUT 404 npm ERR! code E404 npm ERR! 404 missing : @emrealtann/emrealtann npm ERR! 404 npm ERR! 404  '@emrealtann/emrealtann' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.
I've attached the log file too. Thanks for help.
2017-04-20T14_36_31_291Z-debug.txt

Unfortunately I get the same issue with the exact same log file.
When I go to http://localhost:15443 in my browser it outputs a JSON style response with the property error:"missing".

https://github.com/nodeschool/discussions/issues/1561 seems to have fixed it

authors: emrealtann marcinwasilewski scaredcat

repo: workshopper/how-to-npm

license: ISC


text:
Bind to touch events

Allow the usage on some portable devices, tested only with iPad

that's fixed in master now
https://github.com/wout/svg.draggable.js/commit/00e68cd3ebeeea6a10f767ec190cfffc82ba270e
web,android,iphone,ipad tested

authors: TrabacchinLuigi bubenshchykov


text:
Can't connect to subsonic server

When i configure my subsonic server into pimusicbox, the log give me a Error authentication. I try several things : different user, url in xxx.subsonic.org and the direct IP address but nothing works.
Any idea ?

Could you try posting this at discuss.mopidy.com if you are still having problems.

I just found the solution myself. I posted it here :
Each version of Subsonic use a specific API version. You need to edit the file connection.py in /usr/local/lib/python2.7/dist-packages/libsonic and change the version of the API a tthe line "API_VERSION" To find your API Version, go to http://www.subsonic.org/pages/api.jsp

So, there is scope here to at least improve our documentation.

And is that really the only way to modify the API version? That is horrible

The libsonic Connection class constructor accepts an apiVersion parameter which mopidy_subsonic isn't specifying. Perhaps it should be configurable.
@benjbubu What version of the server are you running? Does everything work once you change the version?

I using the 4.8 version of Subsonic and the api version by default in libsonic is for 4.9. Anyway the last version of Subsonic is 5.2.1 and the number of api version is different. ANd yest everything is working fine !! :D

Isn't the default api version v1.11.0 AKA subsonic version 5.1 (https://github.com/crustymonkey/py-sonic/blob/master/libsonic/connection.py#L25) ?

Ahh ok, the released version is 4.9 (the bump to 1.11.0 only happened in the code repository yesterday!)

I cant seem to get it working with subsonic 5.2.1 even if changing the API_VERSION to 1.12.0
Did anyone manage get it working on that version?

authors: benjbubu kingosticks osos

repo: woutervanwijk/Pi-MusicBox


text:
Move command over to new v2 structure

The following changes need to be made to move the command over to the v2 structure:

[ ] Make sure the correct framework is required:composer require wp-cli/wp-cli:^2

[ ] Require the testing framework as a dev dependency:composer require --dev wp-cli/wp-cli-tests:^2

[ ] Use the .travis.yml file from wp-cli/wp-cli:wget https://raw.githubusercontent.com/wp-cli/wp-cli/master/.travis.yml

[ ] Add the default script configuration to Composer file:  "scripts": {
      "lint": "run-linter-tests",
      "phpcs": "run-phpcs-tests",
      "phpunit": "run-php-unit-tests",
      "behat": "run-behat-tests",
      "prepare-tests": "install-package-tests",
      "test": [
          "@lint",
          "@phpcs",
          "@phpunit",
          "@behat"
      ]
  },

[ ] Remove scaffolded binary files:git rm bin/install-package-tests.sh
git rm bin/test.sh

[ ] Remove scaffolded Behat setup:git rm features/bootstrap/*
git rm features/extra/*
git rm features/steps/*

[ ] Remove scaffolded Behat tags util script:git rm utils/behat-tags.php

[ ] Add command packages that are needed for Behat tests as --dev dependencies.
The following commands are already available, anything else needs to be explicitly required:

cli *
config *
core *
eval
eval-file
help

[ ] Update all dependencies:composer update

[ ] Optional - Add PHPCS rule set to enable CS & compatibility sniffing:wget https://raw.githubusercontent.com/wp-cli/wp-cli/master/phpcs.xml.dist

[ ] Run and adapt tests to make sure they all pass:composer test

Correct me if I'm wrong, but I don't think this process applies to this project, which isn't a command.

Thought that might be the case. 🙂

authors: ptrkcsk schlessera

repo: wp-cli/dash-docset-generator


text:
Fixed 'edit page' button URL

There was an old URL in edit page button - just fixed it :)

Thanks! Good catch. 😄

authors: jasonbahl palmiak


text:
LLVM: Out of memory

This may to relate to or be the cause of #187. When doing a simple motor characterization, after disabling autonomous after running a test (usually the 2nd or third test), the tool doesn't immediately popup reporting amount of rotations like normal and has a popup saying NT timeout a few seconds later instead. It turns out the RoboRIO actually runs out of memory. I recall this happening when I was running each test close to a minute. This is not a problem when I run the tests for a shorter amount of time like 25 seconds.
My suspicion is with the telemetry string on disable:
https://github.com/wpilibsuite/frc-characterization/blob/main/frc_characterization/logger_analyzer/templates/Robot.java.mako#L376-L379
Attached is a driver station log.
2021_03_27_15_06_09_Sat.zip
I can't get the log messages to show when opening it on another device but one of the last messages is "LLVM: out of memory"

We should probably document that running it for a minute is a bad idea

We should probably document that running it for a minute is a bad idea

This doesn't particularly make sense. For most systems, characterising 12V is "logical" -> this will take 48s at the default quasistatic ramp rate.

Generally speaking, you don't need to collect data points from 0V to 12V as you only need a change in maybe a few volts (for quasistatic) to get the general trend.  Running the quasistatic tests for too long seems to only increase the likelihood of crashing the roborio (as this issue shows) so this should be documented so that people following a similar logic to yours don't end up with similar issues.

A fix for this has been merged into https://github.com/wpilibsuite/sysid, and SysId will be replacing frc-characterization.

repo: wpilibsuite/frc-characterization


text:
Add support for a convnet/pooling model

Another kind of neural model for sequences.

See

Kim, Y. Convolutional neural networks for sentence classification. In EMNLP, 2014.
Collobert, R., Weston, J., Bottou, L., Karlen, M., Kavukcuoglu, K., and Kuksa, P. Natural language processing (almost) from scratch. In JMLR, 2011

repo: wpm/mycroft


text:
sendListMessage não está sendo enviada

WA-JS Version
3.7.0
WhatsApp Version
2.3000.1015145967
Browser Version
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
Operation System
windows 10
Steps to reproduce
WPP.chat.sendListMessage('[number]@c.us', {buttonText: 'Click Me!', description: "Hello it's list message",title: 'Hello user', footer: 'Click and choose one', sections: [{title: 'Section 1',rows: [{rowId: 'rowid1',title: 'Row 1',description: "Hello it's description 1",},{rowId: 'rowid2',title: 'Row 2',description: "Hello it's description 2",}]}]});
What is expected?
que a mensagem seja enviada
What is actually happening?
A mensagem não é enviada, no whatsapp web aparece o simbolo de alerta avisando "Ocorreu um erro. Clique para saber mais" ao lado da mensagem.
Não dá nenhum erro no console.
O retorno possui o id da mensagem, e sendMsgResult: fulfilled
Any additional comments?
No response

Does button Messages still work ? i though it's disabled by Meta (for non-biz users) this year.

authors: Saifallak luidiva

repo: wppconnect-team/wa-js


text:
bind foreign methods is slow

You must strcmp class names and method signatures every time when WrenBindForeignMethodFn is called (by the VM). The more foreign methods you have, the more you call strcmp.
// Returns a pointer to a foreign method on [className] in [module] with
// [signature].
typedef WrenForeignMethodFn (*WrenBindForeignMethodFn)(WrenVM* vm,
    const char* module, const char* className, bool isStatic,
const char* signature);

Nothing prevent the user to use a better approach than to test symbols one
by one.
Other solutions have some disavantages compared to this lazy/at demand
approach.

Yes, binding is fairly slow, but the idea is that you don't bind methods in performance-critical code. Foreign methods are bound when the class declaration itself executes, not when the method is called. So, in this code:
class Foo {
  foreign method(arg)
}

for (i in 1...1000) {
  var foo = Foo.new()
  foo.method()
}

The VM will only call your bind function once, at the point that the class is declared, not each time an instance is created or a method is called inside that loop.

authors: liigo mhermier munificent

repo: wren-lang/wren


text:
Converting boolean data types from database to 1.0 and 0.0 value metrics?

I run into this INFO log when trying to bring in a boolean data type from the postgres db:
INFO[0088] Unparseable column type - discarding:  pg_importer_table success <nil>
After a little investigation, it seems that the exporter does not handle float conversion of boolean data types to float.  I was thinking we can slap an if statement giving it a 1.0 if true, 0.0 otherwise.  This would be useful to track in Prometheus, especially for alerts when a value becomes true/false.
Is this something that can be incorporated?  I wouldn't mind sending in a PR, just wanted to see get some feedback from anyone.

This seems reasonable, but the PR has linter errors preventing it from being merged at the moment.

authors: miguelHx wrouesnel


text:
Add template for RESTful service

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ThishaniLucas can we close this PR? Since this is already covered with another tutorial?

@Asitha : this functionality is covered in a guide. If only a guide is enough for this scenario, then we're good to close this.

Closing this PR since this scenario is already covered by the guide [1] and the guides are going to be considered as templates as well.
[1] https://github.com/wso2/ballerina-integrator/tree/master/docs/content/src/learn/tutorials/integration-patterns-and-soa/exposing-soap-service

authors: Asitha CLAassistant Shakila ThishaniLucas


text:
Init version 3

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant janithRS


text:
[Improvement][IntegrationStudio] Allow add Environment Variables to the Embedded Microintegrator

Description:
In Integration Studio with the embedded microintegrator it does not allow us to add environment variables to the Launch Configuration. This would be very useful as with Docker Environments we heavily use environment variables and there is no easy way to achieve this with the embedded mi.
Suggested Labels:
Improvement
Suggested Assignees:

Affected Product Version:
Integration Studio 7.0.2
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Just got this link: https://medium.com/@rosensilva/how-to-inject-environment-variables-to-wso2-integration-studio-runtime-83b8f0cb882e
So, we can close the issue.


text:
Masking in APIM

Description:
Current Documentation Does not contain any details related to masking the sensitive data in the log. However, the admin doc and is doc contain that information. Therefore, Please create or update a page in aim doc with the information of masking
https://docs.wso2.com/display/ADMIN44x/Masking+Sensitive+Information+in+Logs
https://is.docs.wso2.com/en/latest/setup/masking-sensitive-information-in-logs/
Suggested Labels:
Improvement

@RakhithaRR , please work on this task as discussed offline.

@RakhithaRR has fixed this issue in the above mentioned PRs.

authors: Mariangela vanjikumaran


text:
Correct formatting errors in Consuming Data, Cleansing Data, Enriching Data, and Transforming Data guides.

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? Yes
Ran FindSecurityBugs plugin and verified report? Yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? Yes

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant RukshiW


text:
Invalid value "true" is selected in the dropdown box for the fileLockScheme property in the file connection creation view for Local connection type

Description:

The valid values for the File Locking Behaviour (fileLockScheme) parameter for Local connection type are Local and Cluster. But in the file connection creation view, the value is set to true in the dropdown list by default. However, in the source view, the value is saved as Local.

The latest release v1.1.0 has resolved the issue. Please reopen if the problem persists.

authors: gigara sajinieKavindya


text:
Unable to deploy synapse artifacts at gateway error printed on startup

Description:
When starting the APIM pack, the following error is printed continuously,
ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway.
Full log output is shown below,
TID: [-1234] [client-registration/v0.17] [2020-07-07 14:23:19,199]  INFO {org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration} - An instance of org.wso2.carbon.identity.oauth2.token.OauthTokenIssuerImpl is created for Identity OAuth token generation.
TID: [-1234] [] [2020-07-07 14:23:20,929]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTransportHandler} - Starting jms topic consumer thread for the keyManager topic...
TID: [-1234] [] [2020-07-07 14:23:20,939]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTransportHandler} - Starting jms topic consumer thread for the throttleData topic...
TID: [-1234] [] [2020-07-07 14:23:20,980]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTransportHandler} - Starting jms topic consumer thread for the tokenRevocation topic...
TID: [-1234] [] [2020-07-07 14:23:21,005]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTransportHandler} - Starting jms topic consumer thread for the cacheInvalidation topic...
TID: [-1234] [] [2020-07-07 14:23:21,019]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTransportHandler} - Starting jms topic consumer thread for the notification topic...
TID: [-1234] [] [2020-07-07 14:23:21,023]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server           :  WSO2 API Manager-3.2.0
TID: [-1234] [] [2020-07-07 14:23:21,034]  INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2 Carbon started in 89 sec
TID: [-1234] [] [2020-07-07 14:23:22,376]  INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL  : https://localhost:9443/carbon/
TID: [-1234] [] [2020-07-07 14:23:22,377]  INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - API Developer Portal Default Context : https://localhost:9443/devportal
TID: [-1234] [] [2020-07-07 14:23:22,378]  INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - API Publisher Default Context : https://localhost:9443/publisher
TID: [-1] [] [2020-07-07 14:23:31,361]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#notification was successful!
TID: [-1] [] [2020-07-07 14:23:31,362]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#tokenRevocation was successful!
TID: [-1] [] [2020-07-07 14:23:31,359]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#keyManager was successful!
TID: [-1] [] [2020-07-07 14:23:31,369]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#cacheInvalidation was successful!
TID: [-1] [] [2020-07-07 14:23:31,370]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Connection attempt: 1 for JMS Provider for listener: Siddhi-JMS-Consumer#throttleData was successful!
TID: [-1] [] [2020-07-07 14:23:31,384]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTaskManager} - Task manager for Siddhi-JMS-Consumer [re-]initialized
TID: [-1] [] [2020-07-07 14:23:31,386]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTaskManager} - Task manager for Siddhi-JMS-Consumer [re-]initialized
TID: [-1] [] [2020-07-07 14:23:31,388]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTaskManager} - Task manager for Siddhi-JMS-Consumer [re-]initialized
TID: [-1] [] [2020-07-07 14:23:31,389]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTaskManager} - Task manager for Siddhi-JMS-Consumer [re-]initialized
TID: [-1] [] [2020-07-07 14:23:31,390]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSTaskManager} - Task manager for Siddhi-JMS-Consumer [re-]initialized
TID: [-1] [] [2020-07-07 14:23:31,741]  WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : tokenRevocation
TID: [-1] [] [2020-07-07 14:23:31,741]  WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : keyManager
TID: [-1] [] [2020-07-07 14:23:31,746]  WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : cacheInvalidation
TID: [-1] [] [2020-07-07 14:23:31,747]  WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : notification
TID: [-1] [] [2020-07-07 14:23:31,746]  WARN {org.wso2.carbon.apimgt.jms.listener.utils.JMSUtils} - Cannot locate destination : throttleData
TID: [-1] [] [2020-07-07 14:23:32,387]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Started to listen on destination : notification of type topic for listener Siddhi-JMS-Consumer#notification
TID: [-1] [] [2020-07-07 14:23:32,387]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Started to listen on destination : tokenRevocation of type topic for listener Siddhi-JMS-Consumer#tokenRevocation
TID: [-1] [] [2020-07-07 14:23:32,389]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Started to listen on destination : throttleData of type topic for listener Siddhi-JMS-Consumer#throttleData
TID: [-1] [] [2020-07-07 14:23:32,390]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Started to listen on destination : keyManager of type topic for listener Siddhi-JMS-Consumer#keyManager
TID: [-1] [] [2020-07-07 14:23:32,391]  INFO {org.wso2.carbon.apimgt.jms.listener.utils.JMSListener} - Started to listen on destination : cacheInvalidation of type topic for listener Siddhi-JMS-Consumer#cacheInvalidation
TID: [-1] [] [2020-07-07 14:23:47,211] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 60 seconds
TID: [-1] [] [2020-07-07 14:24:47,213] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 120 seconds
TID: [-1] [] [2020-07-07 14:26:47,215] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 240 seconds
TID: [-1] [] [2020-07-07 14:30:47,216] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 480 seconds
TID: [-1] [] [2020-07-07 14:38:47,217] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 960 seconds
TID: [-1] [] [2020-07-07 14:54:47,219] ERROR {org.wso2.carbon.apimgt.gateway.listeners.GatewayStartupListener} - Unable to deploy synapse artifacts at gateway. Next retry in 1920 seconds

Steps to reproduce:
Start APIM.
Issue was noticed in 6.7.79-SNAPSHOT build.
Environment details (with versions):

OS: Ubuntu 18.04
Client:
Env (Docker/K8s):

Experiencing the same in the API Manager deployment pattern 1 in a Kubernetes environment.

authors: chirangaalwis uvindra


text:
An error occurs while trying to create a new version with lengthy string

Description:
An error occurred while trying to add a lengthy version.

I'm getting the following issue in the carbon console but didn't give any warning in the publisher UI and created a new version.
[2020-08-19 14:07:19,574] ERROR - ApiMgtDAO Error while adding the API: jane-AT-test.com-phone-900000000000000000000000000000000000000000000000000000000000 to the database
com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1534) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:436) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:387) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7003) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2340) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:371) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at sun.reflect.GeneratedMethodAccessor178.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114) ~[jdbc-pool_9.0.16.wso2v1.jar:?]
at com.sun.proxy.$Proxy49.execute(Unknown Source) ~[?:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI_aroundBody248(ApiMgtDAO.java:5697) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI(ApiMgtDAO.java:5663) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI_aroundBody48(APIProviderImpl.java:890) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:888) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion_aroundBody154(APIProviderImpl.java:3394) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion(APIProviderImpl.java:3145) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.createNewAPIVersion_aroundBody2(UserAwareAPIProvider.java:92) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.createNewAPIVersion(UserAwareAPIProvider.java:87) [org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisCopyApiPost(ApisApiServiceImpl.java:3971) [classes/:?]
at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisCopyApiPost(ApisApi.java:892) [classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_111]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
[2020-08-19 14:07:19,799] ERROR - ApisApiServiceImpl Error while copying API : 1a51f234-d1f0-4ace-8098-06661027acbc
org.wso2.carbon.apimgt.api.APIManagementException: Failed to create new version : 900000000000000000000000000000000000000000000000000000000000 of : phone
at org.wso2.carbon.apimgt.impl.AbstractAPIManager.handleException_aroundBody132(AbstractAPIManager.java:1873) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.AbstractAPIManager.handleException(AbstractAPIManager.java:1872) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion_aroundBody154(APIProviderImpl.java:3418) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion(APIProviderImpl.java:3145) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.createNewAPIVersion_aroundBody2(UserAwareAPIProvider.java:92) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.UserAwareAPIProvider.createNewAPIVersion(UserAwareAPIProvider.java:87) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.rest.api.publisher.v1.impl.ApisApiServiceImpl.apisCopyApiPost(ApisApiServiceImpl.java:3971) [classes/:?]
at org.wso2.carbon.apimgt.rest.api.publisher.v1.ApisApi.apisCopyApiPost(ApisApi.java:892) [classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:193) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:103) [cxf-rt-frontend-jaxrs-3.2.8.jar:3.2.8]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:267) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:216) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:301) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:220) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-servlet-api_9.0.31.wso2v1.jar:?]
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:276) [cxf-rt-transports-http-3.2.8.jar:3.2.8]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat_9.0.31.wso2v1.jar:?]
at org.wso2.carbon.identity.context.rewrite.valve.TenantContextRewriteValve.invoke(TenantContextRewriteValve.java:86) [org.wso2.carbon.identity.context.rewrite.valve_1.4.0.jar:?]
at org.wso2.carbon.identity.authz.valve.AuthorizationValve.invoke(AuthorizationValve.java:110) [org.wso2.carbon.identity.authz.valve_1.4.0.jar:?]
at org.wso2.carbon.identity.auth.valve.AuthenticationValve.invoke(AuthenticationValve.java:75) [org.wso2.carbon.identity.auth.valve_1.4.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:145) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) [tomcat_9.0.31.wso2v1.jar:?]
at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.wso2.carbon.tomcat.ext.valves.RequestCorrelationIdValve.invoke(RequestCorrelationIdValve.java:119) [org.wso2.carbon.tomcat.ext_4.6.0.jar:?]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1639) [tomcat_9.0.31.wso2v1.jar:?]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat_9.0.31.wso2v1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_111]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat_9.0.31.wso2v1.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]
Caused by: org.wso2.carbon.apimgt.api.APIManagementException: Error while adding the API: jane-AT-test.com-phone-900000000000000000000000000000000000000000000000000000000000 to the database
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.handleException_aroundBody320(ApiMgtDAO.java:7297) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.handleException(ApiMgtDAO.java:7295) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI_aroundBody248(ApiMgtDAO.java:5724) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI(ApiMgtDAO.java:5663) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI_aroundBody48(APIProviderImpl.java:890) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:888) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion_aroundBody154(APIProviderImpl.java:3394) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
... 57 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: String or binary data would be truncated.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1534) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:436) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:387) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7003) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2340) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:371) ~[mssql-jdbc-6.1.4.jre7-preview.jar:6.1.4.jre7-preview]
at sun.reflect.GeneratedMethodAccessor178.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114) ~[jdbc-pool_9.0.16.wso2v1.jar:?]
at com.sun.proxy.$Proxy49.execute(Unknown Source) ~[?:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI_aroundBody248(ApiMgtDAO.java:5697) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO.addAPI(ApiMgtDAO.java:5663) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI_aroundBody48(APIProviderImpl.java:890) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.addAPI(APIProviderImpl.java:888) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
at org.wso2.carbon.apimgt.impl.APIProviderImpl.createNewAPIVersion_aroundBody154(APIProviderImpl.java:3394) ~[org.wso2.carbon.apimgt.impl_6.7.196.SNAPSHOT.jar:?]
... 57 more
Steps to reproduce:

Try to create a new version with lengthy characters.

Affected Product Version:

Environment details (with versions):

OS:
Client: MSSQL 2017
Env (Docker/K8s):

Optional Fields
Related Issues:

Suggested Labels:

Suggested Assignees:

Not reproduced in wso2am-3.2.0.0-SNAPSHOT. Fixed already done in master.

authors: Meruja hasuniea


text:
Iot-Analytics : ERROR  JSONObject["value"] not found

Hi all,
When I go to dashboard Analytics https://localhost:9445/portal/dashboards/  , I authenticate and I access well and without error to the portal.
When I click on the Android-IOT dashboard, i have an error in the console :
[IoT-Analytics] ERROR {org.wso2.carbon.event.output.adapter.ui.JaggeryWebSocketHelper} -  JSONObject["value"] not found. org.json.JSONException: JSONObject["value"] not found
I'm looking for where it might come from. Anyone to help me?

Hello everyone,
For several days, I am looking for a solution for this error code. I can not find. Someone would have an idea?
[IoT-Analytics] ERROR {org.wso2.carbon.event.output.adapter.ui.JaggeryWebSocketHelper} -  JSONObject["value"] not found.
org.json.JSONException: JSONObject["value"] not found.

Thank for your help.

I just checked with Ubuntu in localhost.
The error is also present:
[IoT-Analytics] ERROR {org.wso2.carbon.event.output.adapter.ui.JaggeryWebSocketHelper} -  JSONObject["value"] not found.
org.json.JSONException: JSONObject["value"] not found.

@Nirothipan will work on this.

@sinthuja Thank you for your information
I can see the work in progress where?

Hi,
With the IoT 3.1.0 release, we have removed that individual dash board options and the statistics related to devices are displayed in the Device details page itself.
Hence this issue is invalid.
Thank you

authors: Nirothipan Tofdu31 sinthuja


text:
Account lock: account of the super admin is also subjective to locking

The super admin account is also subjective to be locked. In real world use case is it practical to lock the super admin account? Shouldn't the super admin be exempted of account lock?

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.

authors: erandidesilva isharak


text:
[Doc]Wrong requests and responses pointed to get user by id in scim2

Please correct the details in [1]. Currently, it shows create user details but it must show the get user by id details.
[1]https://docs.wso2.com/display/IS540/apidocs/SCIM2-endpoints/#!/operations#UsersEndpoint#getUser by id

Fixed in 5.4.0 and 5.5.0 [1]
[1] https://docs.wso2.com/display/IS550/apidocs/SCIM2-endpoints/#!/operations#GroupsEndpoint#getGroupbyID


text:
The actual behavior and the WARN printed on logs for updating a user role in scim 1.1 is confusing

The actual behavior and the WARN printed on logs for updating a user role in scim 1.1 is confusing
If we call HTTPPatch when adding a user to a role as in[1] the logs on identity server prints a WARN as in [2]. However, the user is actually added to the role as shown in the screenshot [3].
[1]method to add a user to a role
    public void testCreateAdminUser() throws Exception {

        for (int i = 0; i < 1; i++) {
            JSONObject member = new JSONObject();
            member.put(SCIMConstants.DISPLAY, ProcessJsonFile.getJsonObject().get("userName"));
            member.put(SCIMConstants.VALUE_PARAM, userId);
            members.add(member);
        }
        groupObject.put(SCIMConstants.MEMBERS, members);

        updateRoleRequest(client,groupURL,groupObject,getCommonHeaders());
    }

    public static HttpResponse updateRoleRequest(HttpClient client, String url, JSONObject jsonObject,
                                                 Header[] headers) throws Exception {
        HttpPatch request = new HttpPatch(url);
        if (headers != null) {
            request.setHeaders(headers);
        }

        request.setEntity(new StringEntity(jsonObject.toString()));
        return client.execute(request);
    }

[2]Identity server logs
[2018-12-17 15:36:14,254]  INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  'admin@carbon.super [-1234]' logged in at [2018-12-17 15:36:14,254+0530]
[2018-12-17 15:36:14,408]  INFO {org.wso2.carbon.identity.scim2.common.impl.SCIMUserManager} -  User: scim1admin is created through SCIM.
[2018-12-17 15:36:14,518]  WARN {org.wso2.carbon.identity.scim.provider.impl.SCIMUserManager} -  There is no updated field in the group: admin. Therefore ignoring the provisioning.
[3]

In this scenario I am not updating the user role name but calling HTTPPatch and updating the Members of the groups. However, the WARN shows as "There is no updated field in the group: admin. Therefore ignoring the provisioning."

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.

authors: isharak shavantha


text:
[ISSUE] SAML Logout HTTP-Redirect

Describe the issue:
I have configured a trust connection between a SAML 2.0 Shibboleth SP and WSO2 IS 5.9.0. When configuring frontend logout on HTTP-Redirect I receive an error. The SP cannot inflate the logout response.
After tracing the message flow it seems that WSO2IS is sending the logout response via a Form POST. The SAML2 standard states the response should be sent via an Location header for HTTP-Redirect.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.9.0
OS: Linux

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!

authors: hefesita isharak


text:
Bump Dependencies #5156885874

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5156885874

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging 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.

authors: CLAassistant jenkins-is-staging


text:
Bump identity-conditional-auth-functions version

Purpose
$Subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/8370496413

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/8370496413
Status: success

Already updated with: https://github.com/wso2/product-is/pull/20063


text:
Bump Dependencies #648

Bumps dependencies for product-is.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging 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.

Closing due to newer one getting merged


text:
Update Ruby version in Gemfile to 3.3.0

Updated the Ruby version in the Gemfile from 3.2.2 to 3.3.0 to ensure compatibility with the latest version of Ruby.

@genesis-writing You can keep working on this Pull Request. You don't have to create a new Pull Request for the change I requested.

authors: genesis-writing wuletawwonte

repo: wuletawwonte/ethhire-api


text:
OpenAPI / REST object as query parameters does not work

Bug description
OpenAPI / REST object as query parameter does not work
How to reproduce
Used:
https://github.com/typesense/typesense-api-spec/blob/master/openapi.yml
Query:
query searchProduct {
  typesense_searchCollection(
    collectionName: "product"
    searchParameters: {q: "test", query_by: "category"}
  ) {
    found
  }
}

Wundergrap create request
/collections/product/documents/search?searchParameters=%7B
Expected behavior
Should request
/collections/product/documents/search?q=test&query_by=category
WunderGraph information
const typesense = introspect.openApi({
  apiNamespace: 'typesense',
  source: {
    kind: 'file',
    filePath: './openapi.yml',
  },
  baseURL: 'https://eeeeeee.site:2096/',
  headers: builder =>
    builder
      // this header has no effect on introspection
      .addClientRequestHeader('x-typesense-api-key', 'eeeeeee')
      // this header is shared between introspection and actual requests
      .addStaticHeader('x-typesense-api-key', 'eeeeeee'),
})

Environment & setup
node.js 17
WunderCtl Version
latest

Thank you for reporting.

We are currently investigating this and get back to you asap.

Thank you for the update.

@webcredo sorry for the delay, the new oas introspector has been released and I've just tested this. It works 👍
const typesense = introspect.openApiV2({
	id: 'typesense',
	apiNamespace: 'typesense',
	source: {
		kind: 'file',
		filePath: './test.yml',
	},
	baseURL: 'https://x.m.pipedream.net',
	headers: (builder) =>
		builder
			// this header has no effect on introspection
			.addClientRequestHeader('x-typesense-api-key', 'eeeeeee')
			// this header is shared between introspection and actual requests
			.addStaticHeader('x-typesense-api-key', 'eeeeeee'),
});

query searchProduct {
	typesense_searchCollection(collectionName: "product", searchParameters: { q: "test", query_by: "category" }) {
		... on typesense_SearchResult {
			hits {
				document
			}
		}
	}
}

Feel free to re-open this issue if you run into other issue with the introspection.

@Pagebakers  Thank you!

authors: Pagebakers Slickstef11 webcredo

repo: wundergraph/wundergraph


text:
X-CSRF-Token header is missing due to mismatch in operationName and OperationMetadata keys

Bug description
In the newest @wundergraph/sdk@0.132.0, I noticed that the X-CSRF-Token header is no longer present in the requests, causing the WunderGraph backend to reject the request.
I think this is due to this comparison, where the keys in operationMetadata no longer match the actual operation names, causing this if condition to always evaluate to false. For example, if I define an operation in .wundergraph/operations/images/GetImages.graphql, the operationName becomes images/GetImages while the key in operationMetadata is ImagesGetImages.
How to reproduce
see above
Expected behavior
No response
WunderGraph information
@wundergraph/sdk@0.132.0
Environment & setup

OS:
Go version:
Database:
Node.js version:

WunderCtl Version
wunderctl 0.127.0

Thanks for reporting. We'll have a look.

authors: alasdairtran jensneuse


text:
Migrated documentation of HipChat to WunderWay

This PR resolves issue #65

Once this PR is merged, we can remove the doc from Drive: https://docs.google.com/document/d/18R-RglYUJuLOYT-D2LxbtxkTLQNBlNB1Vf91SwbLA8c/edit#
@steveparks, can you please keep an eye on this? Or shall I just ping you?

I'll try to keep an eye - but it's worth you or whoever merges this pinging me as a nudge.

Great idea to merge this in @huberfl - I've reviewed and made a few minor comments.

Looks good to me. Thanks for adding this to WunderWay @huberfl

authors: huberfl joesb steveparks

repo: wunderkraut/WunderWay


text:
Nested resource - design question

I'm wading into a a Java implementation and I'm curious what your findOne or find interface looks like for nested URLs. For example when fetch /articles/1/author , as found in this section, how do you call findOne such that you fetch the author from article 1?

If my memory serves me correctly, this is a two step process which is not automated. First you have to do a findOne for articles/1. The returned resource will have Resource (to-one) or LinkedResourceCollection (to-many) objects for it's relationships fields. If the related resources were not sideloaded, these only include the URLs and optionally IDs.
If you then want to load these related resources you can create a Query for that resource or that collection and load them using the find or findOne methods that take a query. For to-one relationships you can also use the ensure method.

Awesome, thanks for the information.
On Tue, Sep 1, 2015, 6:59 AM Ward van Teijlingen notifications@github.com
wrote:

If my memory serves me correctly, this is a two step process which is not
automated. First you have to do a findOne for articles/1. The returned
resource will have Resource (to-one) or LinkedResourceCollection
(to-many) objects for it's relationships fields. If the related resources
were not sideloaded, these only include the URLs and optionally IDs.
If you then want to load these related resources you can create a Query
for that resource or that collection and load them using the find or
findOne methods that take a query. For to-one relationships you can also
use the ensure method.
—
Reply to this email directly or view it on GitHub
https://github.com/wvteijlingen/Spine/issues/31#issuecomment-136731736.

authors: FreakTheMighty wvteijlingen

repo: wvteijlingen/Spine


text:
Texte posten

ID 3 - Als Nutzer möchte ich Texte posten können, um meine Gedanken zu teilen

Mein Aufwand: 1,5 Stunden