vee-validate beufy example; does not update field state

Versions

vee-validate: 2.#.#
vue: 2.#.#

Describe the bug
vee-validate buefy example has a bug.
Changing the checkbox state doesnt correclty update the field data
To reproduce
Steps to reproduce the behavior:

Go to https://codepen.io/blowsie/pen/XyqmWz?editors=1010
Scroll down to I agree to the terms and conditions
Click on I agree to the terms and conditions
See that the field data doesn't correctly update, the changed flag remains false.

Expected behavior
The field data should update
Demo link
https://codepen.io/blowsie/pen/XyqmWz?editors=1010
Im not sure if this is an issue of vee-validate or beufy.

VeeValidate sets the flags when validation events are triggered, like input or changed or even custom ones, disabling the events entirely will result in some flags not updating properly. This works properly for validation provider components, the fix for the directive was implemented and should land in the next release.


Using variables in @imported file

I'm trying to include SemanticUI's LESS in my project and failing. They include their theme.config file, which sets a @themesFolder variable and then does @import "theme.less", which in turn tries to use the variable in another import: @import<EMAIL_ADDRESS>but fails stating that @themesFolder is not set.
So far, I've traced this down to:
Less_Tree_Import::ParseImport() imports theme.config and does:
$root = $parser->parseFile($full_path, $uri, true);
$ruleset = new Less_Tree_Ruleset(array(), $root->rules );
After that, the variable exists in $ruleset. It then calls:
$ruleset->evalImports($import_env);
Function evalImports($env) iterates through $this->rules and if the rule is an import, then calls:
$rules = $rule->compile($env);
Now, since the received $env is passed, what happens is that the variables defined in this particular ruleset up to the import are not available.
Am I on the right tracks? Is this a bug?

I tested your issue again my fork https://github.com/kylekatarnls/less.php and I confirm the bug. I will inspect it.

@kylekatarnls  -  any insight on that?

Not solved, I have the following clue:
This fails only in the @import statement string. If I do a static-path import, then call themesFolder inside, it works.
So it's something about getting all the variables when calculate an import path.

Hi, it's fixed. Could you try to update to "dev-master" version to check it works with your case before I release the tag?

Unfortunately not. I still get the error, which is thrown in Less_Tree_Variable::compile(). When I var_dump the $env there, I see that the variable exists in $env->rules, but the function loops $env->frames looking for the variable.

I confirm, something's missing in my merge.

Sorry for the delayed answer, but - yeah works now. Thanks.
(Works = "got past that, onto another error.")

Hi Guys,
indreksiitan did you manage to get SemanticUI's LESS to compile ok. Im using octobercms which uses oyejorge/less.php to compile but am experiencing the same issues.
/* variable @themesFolder is undefined in file /.../assets/vendor/semantic-less/theme.less in theme.less on line 16, column 9 14| 15 */
Any help would be great, thanks!

Unfortunately not. I managed to put together a repeatable test case and been trying to get in contact with @kylekatarnls in various ways to send it to him, but have not been able to.

Thanks for the reply.
Are you using october CMS?
in meantime i will keep looking for an answer and will let you know if i find anything.
Kind regards, Lee.
Lee Robinson - Digital Director
22 Chorley New Road, Bolton, BL1 4AP
T: 01204-393-048  M: 07813-803-349
E<EMAIL_ADDRESS><EMAIL_ADDRESS>W: timmarner.co.uk http://www.timmarner.co.uk/
F: /timmarner https://www.facebook.com/timmarner T: /timmarner https://twitter.com/timmarner I: /timmarner https://instagram.com/timmarner/
Company Registered in England and Wales. Company Number 9339543.
This e-mail and attachments are intended for the above name only and may be confidential. If they have come to you in error, you must take no action based on them, nor must copy or show them to anyone; please reply to this e-mail and report the error. Security warning: Please note that this e-mail has been created in the knowledge that the internet is not a one hundred percent secure communication medium. We advise that you understand and observe this lack of security when emailing us. Virus: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good practice the recipient should ensure they are actuallyvirus free. If you have received this e-mail in error please notify<EMAIL_ADDRESS><EMAIL_ADDRESS>
On 4 May 2018, at 14:03, Indrek Siitan<EMAIL_ADDRESS>wrote:
Unfortunately not. I managed to put together a repeatable test case and been trying to get in contact with @kylekatarnls https://github.com/kylekatarnls in various ways to send it to him, but have not been able to.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/oyejorge/less.php/issues/352#issuecomment-386594681, or mute the thread https://github.com/notifications/unsubscribe-auth/AM2LeSGlCp9uTuPgRasb0bjxe7OZykF2ks5tvFGUgaJpZM4PR_R-.

Nope, we're using our own homegrown framework.

Thanks,
Have you come across a SASS version of semantic UI? OctoberCMS can compile SASS also so it may be an option
Kind regards, Lee.
Lee Robinson - Digital Director
22 Chorley New Road, Bolton, BL1 4AP
T: 01204-393-048  M: 07813-803-349
E<EMAIL_ADDRESS><EMAIL_ADDRESS>W: timmarner.co.uk http://www.timmarner.co.uk/
F: /timmarner https://www.facebook.com/timmarner T: /timmarner https://twitter.com/timmarner I: /timmarner https://instagram.com/timmarner/
Company Registered in England and Wales. Company Number 9339543.
This e-mail and attachments are intended for the above name only and may be confidential. If they have come to you in error, you must take no action based on them, nor must copy or show them to anyone; please reply to this e-mail and report the error. Security warning: Please note that this e-mail has been created in the knowledge that the internet is not a one hundred percent secure communication medium. We advise that you understand and observe this lack of security when emailing us. Virus: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good practice the recipient should ensure they are actuallyvirus free. If you have received this e-mail in error please notify<EMAIL_ADDRESS><EMAIL_ADDRESS>
On 4 May 2018, at 14:06, Indrek Siitan<EMAIL_ADDRESS>wrote:
Nope, we're using our own homegrown framework.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/oyejorge/less.php/issues/352#issuecomment-386595387, or mute the thread https://github.com/notifications/unsubscribe-auth/AM2LeZe07PZ5AznJ6ztq4fehKLt7D_pKks5tvFJBgaJpZM4PR_R-.

is there a SASS version of semantic?

Not that I'm aware of.

Actually, there seems to be: https://github.com/doabit/semantic-ui-sass

thanks. have just tried it and getting error if i include some element. the browser guest give me any info on the error though.
Sorry to go off topic but how can i find the whats causing the error. i can pinpoint the file.
thanks

Tried the SCSS version. It compiles for me, although takes over 40 seconds to do so.

But the real bummer is that there's virtually no customization besides font name and size - all colors etc are hardcoded.

yeh it does take a while. if i disable importing or grid or menu it work but they both cant be imported or it throughs a error. stange.
Going back to the Semantic LESS i think its down to this @{variable} thats the problem in string  @import url. is there an other way to do this:
@import<EMAIL_ADDRESS>


Check WorldBank datareader  functionality

#814 implemented a quickfix to deactivate the failing WorldBank-datareader tests.
This issue is a reminder to check whether the datareader still works.

Closing as migrated to wbdata by @glatterf42


Fixed issue #224

@hongsudt  Currently, the template only allow referencing to the visible column only. We need to allow the annotation to access the formatted value of any columns in the Tuple.
Instead of referring the ref.colums, I am referring the ref._table.columns to find the column and format it accordingly.

On Oct 03, Chirag Sanghvi modulated:

@hongsudt Currently, the template only allow referencing to the visible
column only. We need to allow the annotation to access the formatted
value of any columns in the Tuple.
Instead of referring the ref.colums, I am referring the
ref._table.columns to find the column and format it accordingly.

This sounds about right to me. Just to be sure: the mustache template
should also be referencing the columns by their real names in the
ERMrest table definition, not influenced by any column renaming done
for display purposes. Right?

I wonder if there is some additional complexity in this. Like if we are going to use formatted values as the input to markdown, do we need a dependency graph just to determine what order the formatting of values should be processed in?

@robes Formatting is totally dependent on the type of the column. The Tuple.values() getter first gets the formatted values and then starts the templating with markdown following it. So the order wouldn't matter. https://github.com/informatics-isi-edu/ermrestjs/blob/master/js/reference.js#L1261

@robes I think it should be in two phases:

pre-formatting, which is single-column only and does not include markdown
mustache templates, which can sample all pre-formatted values

there should not be any recursion of mustache templates. each one
should see the exact same input environment regardless of which order
they are evaluated.

@chiragsanghvi @karlcz makes sense.


Fix condition about displaying the Gather Feedback on Coming soon Connection

No impact has dataSource Intercom was not allowed in the Prod Pro and Free Trial plans so we were showing this modal, but this is the condition we want to have.

Merging already has fairly small.


Small bug fixes, reading run stop

Fixed bug in TParsingDiagnostics
ODB from event ID 0x8001 is parsed to get run start and stop and set the run length based on those.
If the file is the last from the run this will read the correct stop time, otherwise the stop time will be zero!
Restricted all calls to TClass::IgnoreTObjectStreamer to ROOT 5 (will be removed soon).
Switched ErrorReport.sh from echo to printf so that "\n" creates actual newlines.

I've changed back all of the std::getline(foo,bar) != nullptr commands. This doesn't port to mac, and I think just doing a while(std::getline(foo,bar)) is sufficient.

Also offsetfix got mangled somewhere in here and functions got eaten by other functions. I've moved mine to .C for now.

This was fixed in PR #921, and using while(std::getline(foo, bar)) uses an implicit conversion to boolean, which is not advised. Using std::getline(foo, bar).good() is much better.
And the offset fix was an issue of closing brackets missing for MacOS, which is fixed in PR #922.


Fix engine relnotes

Fixes https://github.com/docker/docs-private/issues/965

Deploy preview for docsdocker ready!
Built with commit 8c7075545d5c37e1456099d2245cd18bfa964faa
https://deploy-preview-8257--docsdocker.netlify.com


publish fails with "callback called twice"

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
When publishing to S3, I sometimes (20-40% of the time) receive an error.
Here's the log:
✔ Checking your system
✔ Resolving Forge Config
We need to package your application before we can make it
✔ Preparing to Package Application for arch: x64
✔ Compiling Application
✔ Preparing native dependencies
✔ Packaging Application
Making for the following targets:
✔ Making for target: dmg - On platform: darwin - For arch: x64
✔ Making for target: zip - On platform: darwin - For arch: x64
✔ Resolving publish target: s3
⠙ Uploading Artifacts 1/2
An unhandled exception has occurred inside Forge:
callback called twice
Error: callback called twice
    at onCb (/usr/local/lib/node_modules/electron-forge/node_modules/pend/index.js:36:23)
    at Response.<anonymous> (/usr/local/lib/node_modules/electron-forge/node_modules/s3/lib/index.js:303:11)
    at Request.<anonymous> (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:364:18)
    at Request.callListeners (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:685:12)
    at Request.callListeners (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
    at Request.emit (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/usr/local/lib/node_modules/electron-forge/node_modules/aws-sdk/lib/state_machine.js:14:12)

Screenshot: https://i.imgur.com/ZE8qh4I.png
Command: electron-forge publish --platform=darwin --target=s3
It's unreliable; can't always reproduce.
package.json
{
  "name": "Name",
  "productName": "Name",
  "version": "1.0.5",
  "description": "Description",
  "main": "src/js/main.js",
  "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "eslint src --color"
  },
  "keywords": [],
  "author": "Author",
  "license": "MIT",
  "config": {
    "forge": "src/js/config/forge.js"
  },
  "dependencies": {
    "deepmerge": "^2.1.0",
    "electron-compile": "^6.4.2",
    "electron-log": "^2.2.14",
    "electron-squirrel-startup": "^1.0.0",
    "node-localstorage": "^1.3.0",
    "uberproto": "^1.2.0"
  },
  "devDependencies": {
    "babel-plugin-transform-async-to-generator": "^6.24.1",
    "babel-preset-env": "^1.6.1",
    "babel-preset-react": "^6.24.1",
    "electron-forge": "^5.1.1",
    "electron-prebuilt-compile": "1.8.2",
    "eslint": "^3.19.0",
    "eslint-config-airbnb": "^15.1.0",
    "eslint-plugin-import": "^2.9.0",
    "eslint-plugin-jsx-a11y": "^5.1.1",
    "eslint-plugin-react": "^7.7.0"
  }
}

forge.js
// Aws config path
var fs = require('fs'),
    awsPath = __dirname + '/aws.json',
    aws = {
        "auth": {
            "key": "***",
            "secret": "***"
        },
        "s3": {
            "bucketName": "files.s3bucket.com.local"
        }
    };
if (fs.existsSync(awsPath) === true) {
    var content = fs.readFileSync(awsPath, 'utf8');
    aws = JSON.parse(content);
}

// Let's do this
module.exports = {
  "make_targets": {
    "darwin": [
      "dmg",
      "zip"
    ],
    "linux": [
      "deb",
      "rpm"
    ],
    "win32": [
      "squirrel"
    ]
  },
  "electronPackagerConfig": {
    "asar": true,
    "ignore": [
      "/src\/images\/icon\.1024x1024\.dev\.png",
      "/src\/images\/icon\.1024x1024\.local\.png",
      "/src\/images\/icon\.1024x1024\.prod\.png",
      "/src\/js\/config\/aws\.json",
      "/src\/js\/config\/forge\.js"
    ],
    "appCategoryType": "public.app-category.graphics-design",
    "appBundleId": "com.anchor.macOS.appName",
    "osxSign": {
      "identity": "Mac Developer: Developer Name (KEY)"
    },
    "packageManager": "npm",
    "icon": "src/images/icon.icns"
  },
  "electronWinstallerConfig": {
    "name": "Name"
  },
  "electronInstallerDMG": {
    "background": "src/images/background.png",
    "icon": "src/images/icon.icns"
  },
  "electronInstallerDebian": {},
  "electronInstallerRedhat": {},
  "s3": {
    "accessKeyId": aws.auth.key,
    "secretAccessKey": aws.auth.secret,
    "bucket": aws.s3.bucketName,
    "folder": "releases",
    "public": true
  },
  "windowsStoreConfig": {
    "packageName": "",
    "name": "Name"
  }
};

Current theory is the s3 module we use is broken 😢 We could fix this probably by moving to directly use aws-sdk


Fix #1496: Follow-up: fix for sample-data after user classes refactored

Describe your changes :
Previous patch to fix the sample-data users didn't work. This patch fixes it.

Type of change :

[x] Bug fix

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers


Switches on/off with icon

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Instead of the usual colored Switche on/off, it would be a nice feature to have a Switche with icons that are passed, even the colors must be passed, so if it is in the on state it has a different color and icon than what it is state is off.
Examples 🌈

@Angelk90 Sorry, we have no plan for this. Thanks for the suggestion.

@oliviertassinari :
Can't be put as a future new feature instead of closing directly?

I would rather keep it close, so we can focus on the priorities.


Package update

I created them on my virtual environment.

With this? [create-adapter](https://github.com/ioBroker/create-adapter/blob/master/.github/workflows/test-and-release.yml)

I don't know how to update it properly.


Are Client_ID and username the same?

When using an application id for a username and the application key for the password, are the username and client_id fields the same in the sample code?

I don't think so. Client id is not the username. I tried the username as the email address that was registered with azure with no luck, but username leaving the domain out i saw a different error
Exception in thread "main" java.util.concurrent.ExecutionException: com.microsoft.aad.adal4j.AuthenticationException: {"error_description":"AADSTS90019: No tenant-identifying information found in either the request or implied by any provided credentials.\r\nTrace ID: e40596bf-5661-4d99-aa7e-3b7165581e00\r\nCorrelation ID: 649b78be-4308-4917-b595-f1ae56c4c78c\r\nTimestamp: 2017-11-23 22:14:51Z","error":"invalid_request"}

Indeed, clientId and username are the the same. the clientId is a GUID which represents the application
Thanks for the feedback. The sample was updated with clear instructions on how to register the Azure AD application (or even scripts to do that)


Move issue template to ./github dir.

GitHub provides a new version of issue templates. These are now stored in a .github/ISSUE_TEMPLATE directory and the best practice is to have different templates for bugs and features.
Also, Pull Request templates can be added to the .github dir.

Thanks for the approval @dvlato. Can we merge this?


New user  session handling

Why
We want to provide an option for users to decide if they want to use persistent session tracking which can persist a session between page navigations (static websites) and synchronize a session across browsing contexts (tabs and windows). The new session manager invalidates or better creates new session if a session is invalid.
Users can also pick in-memory session management which aligns to the concepts of the above as far as possible.
But it has limitations, especially om static websites because all state is hold in-memory.
We will enhance this situation in the follow-up PRs.
This is the first PR to present, test and refine the concept. We will improve things in the next weeks.
What

Add a throttle function — used an own implementation to keep the additional payload small
Add a service to wrap the local storage APIs
Add the session manager module which contains utility functions for the session managers as well as both session managers. I didn't use a class to save on bundle size because classes are not minimized well by nearly all common minifiers.

Note
This PR is a (bigger) PoC and will likely be heavily refactored.
Already known refactorings

we'll change the in-memory session manger to use Session Storage. This is to make it easier to make session data outlive page navigations

See: https://github.com/grafana/faro-web-sdk/issues/355
Links
Checklist

[x] Tests added
[ ] Changelog updated
[ ] Documentation updated

in which version is this planned to be released?

in which version is this planned to be released?

@pawan-regoti
A first experimental version of it will be available with the next release of the web-sdk but it is in experimental state and not meant for production use!
So we expect some refactorings till a v1 of this feature is ready. Also features like sampling based on sessions are not implemented yet (we will start working on it soonish).
Cheers,
Marco
cc @cedricziel


ngx_stream_lua_api.c is missing?

File api/ngx_stream_lua_api.h defines some functions like ngx_stream_lua_add_package_preload and ngx_stream_lua_get_session but I am unable to find their source. I can assume ngx_stream_lua_api.c is missing after looking at https://github.com/openresty/lua-nginx-module/blob/master/src/ngx_http_lua_api.c
Am I wrong?

@antony66 Yeah, they might be missing since the existing test suite do not cover these APIs yet. Patches welcome! :)


Reopen the last results

Is it possible to reopen the window with the last command results?
E.g. If I do find usages, and go to the first usage, I might want to go to another usage, after I reviewed the first one. Would it be possible to save the results and have an option to reopen the window?
Or another way to implement something like that would be to duplicate results into the QuickFix window; so you can run copen and look at them later.
BTW, thanks for the great plugin.

Hello!
That was a good idea, I've implemented it in the latest commit with a new command LspFuzzyLast. I prefer to keep the quickfix window for multi-selection so the last results also use the FZF window.
Note that you need to set save_last to true in the plugin configuration for the command to work. This is because I didn't want to introduce memory and speed overhead when the results are thousands lines long.


releaseescrow api returned unexpected error

Due to a client bug, I called releaseescrow before the timeout was complete on a main net LTC order. The error returned was
 "reason": "Escrowed currency does not support automatic release of funds to vendor"

It looks like it hit this condition
if !(&repo.SaleRecord{Contract: contract}).SupportsTimedEscrowRelease() {
		ErrorResponse(w, http.StatusBadRequest, "Escrowed currency does not support automatic release of funds to vendor")
		return
	}

This is a multisig moderated order.

this was fixed


quiche: enable some quiche tests in CI

Signed-off-by: Dan Zhang<EMAIL_ADDRESS>Enable tests with tag "test_included" in @com_googlesource_quiche:// in all the CI.
Risk Level: Medium, quiche test failure will fail all the CIs.

/assign @lizan

ping? I don't think these ci failures are related.

Can you merge master again to see if CI is fixed?

The error is system.IO.IOException: No space left on device.
Can someone kick the workflow again?

/retest

ping @lizan


field messages is required when using code completion

What happened?
an error :field messages is required" occured when using code completion on a custom openai

Relevant log output or stack trace
CodeGPT
field messages is required (request id:
20240711173509677817336G6FsrA8p)

Steps to reproduce
I used custom openai and turned on the "enable code completions"
CodeGPT version
1.16.0
Operating System
Windows

I also meet this problem.

It sounds like you're using the /chat/completions api instead of the default /completions.

/chat/completions requires a messages entry, and ignores prompt and suffix.
/completions requires prompt, supports suffix for gpt-3.5-turbo-instruct, and ignores messages.

Since it sounds like you've changed the default configuration; can you tell us what your config you are using? Which model are you using, and how are you sending $PREFIX and $SUFFIX? I believe that gpt-3.5-turbo-instruct is the only model that supports fill-in-the-middle (of the openai models), and that model is only suported by the /completions endpoint.

The same


App crashes on Heroku

Boarding worked for me on Heroku for a couple months. Today I discovered that it's now broken - without me making any changes to it. This is what Heroku says:

Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.

This is the log I get - restarted the app on Heroku right before that (to no availal):
2018-06-02T13:09:53.226862+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/lib/puma/configuration.rb:243:in app'
2018-06-02T13:09:53.226863+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/lib/puma/runner.rb:138:in load_and_bind' 2018-06-02T13:09:53.226864+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/lib/puma/cluster.rb:397:in run'
2018-06-02T13:09:53.226866+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/lib/puma/launcher.rb:183:in run' 2018-06-02T13:09:53.226867+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/lib/puma/cli.rb:77:in run'
2018-06-02T13:09:53.226874+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.2/bin/puma:10:in <top (required)>' 2018-06-02T13:09:53.226875+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in load'
2018-06-02T13:09:53.226877+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.3.0/bin/puma:22:in <top (required)>' 2018-06-02T14:04:40.500198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=push-testflight-signup.herokuapp.com request_id=e50e9377-bb8f-4ef9-aca1-610ce8d80e2f fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https 2018-06-02T14:04:40.883461+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=push-testflight-signup.herokuapp.com request_id=e56d4b4c-d8b4-4f29-9241-ff2a4b170a9c fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https
Tried to deploy a clean build to Heroku but I get the same issue as described here: https://github.com/fastlane/boarding/issues/217

See #217
Related to https://github.com/fastlane/fastlane/issues/12577

Thank you, @Thwaitesy. Clicking continue on the popup after logging in with the build account fixed the issue.


can't switch from fullscreen to windowed mode

to switch to windowed mode the monitor ptr must be set to null, however the monitor param of kgl's window.setMonitor() function is non-nullable, making this operation impossible

Ah rip, that's a bug.
If you're not using mpp you can call glfwSetWindowMonitor directly as a workaround.
Feel free to send a PR in the meantime. Dunno when I'll get to this myself.

Created a fix. CI failed because of apt though. Gonna try again tomorrow.

fixed with #34. Will be in next release

fixed with #34. Will be in next release


Add Speed Limit Requests

Changes
continuous_checker

Add continuous_checker param to LaneBlocker node. This param is a bool with default value false.
If obstacles are static, continuous_checker should be left as false. If obstacles are dynamic/moving, set continuous_checker to true.
When continuous_checker is false, the LaneBlocker node will only check an obstacle for intersection with all lanes when the obstacle first appears.
When continuous_checker is true, the LaneBlocker node will continuously check an obstacle for intersection with all lanes as long as the obstacle is present.

add speed limits

Lanes can now be in Closed state, Speed Limited state and normal state
Refactored the lane open and lane close msg creation and sending
Add speed limit and speed unlimit msg
Handle all 6 possible state transitions
Add python bindings for agv::FleetUpdateHandle::limit_lane_speeds() and agv::FleetUpdateHandle::remove_speed_limits()  - related PR in rmf_demos

@Yadunund since this is targeting your draft PR #210 I'll leave it up to you if/when/how this gets merged.


fix typos in Docs

sorry about a whole pull request for this.

A fine use of a pull request. Good catches! Thanks.


Corrected logo spelling error

It has been brought to my attention that the logo I originally contributed was mispelled. How embarrassing!

Hello! I'm the build bot for the Mono project.
I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.
Contributors can ignore this message.

@jongalloway We're all humans :)

Thank you for your contribution!


MF2 Improvements - Take Two

This is an attempt to rewrite the previous PR. It takes away some of the extra complexity and tries to simplify, while accomplishing the same goals.

Again the
Matthias Pfefferle mentioned this Article on Array.

problem and a broken type detection.

I committed the tests, perhaps they will help.

I tested several sites manually, but I will try against the tests.

I got 0 errors without the changes and 6 after your changes... but feel also free to recheck/extend my test cases...

I intend to keep working at it until I get it to work to spec.

The current version is not that bad, but perhaps you have some exotic examples...

That is why I am not giving up. I think the changes I want to make sets up for a lot of future improvements.

Somehow on rebasing, accidentally lost the commit. Going to have to fix.

I will not open a new PR until it passes the tests.


BNP - Inconsistency in pointer position on android native and mWeb

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.60-1
Reproducible in staging?: y
Reproducible in production?: new feature
Issue reported by: Applause - Internal Team
Action Performed:

Click on 'FAB'
Click on 'Request money'

Expected Result:
Pointer position should be consistent across platform. Pointer at end would good to clear zeros first before putting number.
Actual Result:
Android pointer position is start and mWeb and Web pointer position is at end
Workaround:
n/a
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/93399543/bd66595b-db7f-4110-ba40-f992d1201831
https://github.com/Expensify/App/assets/93399543/a7060846-e69b-41d6-a430-a7e06ae86dfb
View all open jobs on GitHub

@mountiny issue is fixed now.
https://github.com/Expensify/App/assets/43996225/574831ea-de32-4de1-8ee4-dbc7c5bf73e3
https://github.com/Expensify/App/assets/43996225/2ebd936c-7f18-4ef5-8602-41f9e0295119

Thanks!


Payone Decorator Conflicts with SWAG Commercial Plugin: Needs to Extend Shopware AccountOrderController

When the SWAG Commercial Plugin and Payone are installed together, I encounter the following error:
Shopware\Commercial\B2B\OrderApproval\Storefront\AccountOrderControllerDecorator::__construct(): Argument #1 ($decorated) must be of type Shopware\Storefront\Controller\AccountOrderController, PayonePayment\Storefront\Controller\Account\AccountOrderControllerDecorator given, called in /app/localCache/var/cache/dev_h512f707b3a123fefeec142b66749ede4/ContainerFWnGjxV/Shopware_Core_KernelDevDebugContainer.php on line 16042

Actual Behavior
The error message above appears, indicating that Payone's decorator does not properly extend the required class, causing a conflict when used with the SWAG Commercial Plugin.
Expected Behavior
Payone's AccountOrderControllerDecorator should extend Shopware\Storefront\Controller\AccountOrderController to ensure compatibility with the AccountOrderControllerDecorator of the SWAG Commercial Plugin.
Steps to Reproduce
Install both the SWAG Commercial Plugin and Payone plugin.
Create a Customer
Create a Order with the Customer
Login as the Customer
Try to open the Order in ur Profile Page or perform any action that requires the use of the AccountOrderController.
The error will appear as described above.

The issue occurred because we had a problem with the Swag Commercial plugin, and we performed a reinstall via the CLI. This action changed the installation_at date in the database, which caused the behavior where the PayonePayment plugin installation date being earlier than the Swag Commercial plugin's resulted in an error.
Error:
PayonePayment installed_at = 2024-11-28
SwagCommercial installed_at = 2024-12-02
No Error:
PayonePayment installed_at = 2024-12-04
SwagCommercial installed_at = 2024-12-02

Hello @No-999
thank you for your issue.
we already have fixed this issue with the PR https://github.com/PAYONE-GmbH/shopware-6/pull/329.
sadly this change hasn't released yet. I will push this to the internal.
I will close this issue because it has been already fixed.


installer updated?

Just a heads up, I installed using curl https://raw.githubusercontent.com/a16z/helios/master/heliosup/install | bash but couldn't connect to op-mainnet as described in the readme. Then I noticed it used to be called optimism, which worked.

Ah good catch. We changed the naming recently an have not pushed an update to the installer. Our next release is coming soon and will resolve.


Access to Trained Modules and Data files

Hi, I found your paper to be very interesting. In my attempt at running this code, I realized that the preprocessed dataset and trained models cannot be downloaded. I am assuming they are not hosted anymore, but can this be verified? Also if it would be possible to re-upload them? Thank you.

Super embarrassing. I did not have wget installed - my bad.


Protocol spec doesn't specify that "id" fields must be UUIDs

When reading the specification there is not a hard requirement that the "id" field returned for shares and schemas be a properly formatted UUID.
When attempting to use DataBricks as a click if values are encountered in the "id" field that aren't UUIDs this means that the share/schema cannot be accessed.
Does the protocol specification need to be updated to list this requirement or is this a choice of DataBricks' implementation of the Delta Client?

Hi @rustyconover , I recently noticed this problem and sent out https://github.com/delta-io/delta-sharing/pull/262 and https://github.com/delta-io/delta-sharing/pull/263 to make it more clear.
Share IDs and Table IDs are still optional since all open connectors do not require their presence. However Databricks choses to enforce table ID to present for a consistent access control with the rest of the platform (but I'm going to remove the requirement on Share IDs in Databricks soon).


Compiler Warnings

I am seeing a number of messages like:
In file included from ../ccutil/clst.h:24:0,
                 from ../ccstruct/blobbox.h:23,
                 from workingpartset.h:24,
                 from workingpartset.cpp:21:
../ccstruct/blobbox.h: In member function ‘void BLOBNBOX::set_reduced_box(TBOX)’:
../ccutil/host.h:79:25: warning: overflow in conversion from ‘int’ to ‘signed char:1’ changes value from ‘1’ to ‘-1’ [-Woverflow]
 #define TRUE            1
                         ^
../ccstruct/blobbox.h:236:17: note: in expansion of macro ‘TRUE’
       reduced = TRUE;
                 ^~~~

Would it be possible to switch the 'debug' flag from 'configure' to include '-Wall -pedantic', or to at least require all patches and changes to compile without any warnings and errors?
It's not unusual for contracts to include a provision that all code must compile without warnings, and it's generally a good practice to at the very least test enough to make sure that you're not getting compiler warnings before heading to production.
It's also much easier for the person who wrote the code to decide if the compiler warnings matter, or, for example, if simply using a cast will result in the same logic if certain bounds are impossible.
I can submit a one time cleanup once  #995 is resolved, but in the future it'd be great if reducing compiler warnings would be encouraged.

Environment

Tesseract Version: 4.0.0(alpha or dev)
Platform: Linux [hostname] 4.12.0 #1 SMP Tue Jul 11 14:56:49 EDT 2017 x86_64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz GenuineIntel GNU/Linux

I addressed the reported and some more warnings in pull request #1039.

See also #584

@stweil Can this be closed now?

We still get lots of warnings, for example 1370 warnings with Visual Studio. This issue can be closed if we agree that all those warnings can be ignored.
If we care for warnings, we also have to decide which compiler warnings should be enabled for the GNU compiler or for CLANG.

C4018: '<': signed/unsigned mismatch
C4018: '>=': signed/unsigned mismatch
C4068: unknown pragma
C4146: unary minus operator applied to unsigned type, result still unsigned
C4244: '=': conversion from 'FLOAT64' to 'FLOAT32', possible loss of data
C4244: '=': conversion from 'const double' to 'float', possible loss of data
C4244: '=': conversion from 'double' to 'FLOAT32', possible loss of data
C4244: '=': conversion from 'double' to 'PRIORITY', possible loss of data
C4244: '=': conversion from 'double' to 'float', possible loss of data
C4244: '+=': conversion from 'const int64_t' to 'int', possible loss of data
C4244: '+=': conversion from 'double' to 'float', possible loss of data
C4244: '+=': conversion from 'float' to 'int', possible loss of data
C4244: '-=': conversion from 'double' to 'float', possible loss of data
C4244: '-=': conversion from 'float' to 'int', possible loss of data
C4244: '/=': conversion from 'double' to 'float', possible loss of data
C4244: '=': conversion from 'FLOAT32' to 'int', possible loss of data
C4244: '=': conversion from 'FLOAT64' to 'FLOAT32', possible loss of data
C4244: '=': conversion from 'UNICHAR_ID' to 'float', possible loss of data
C4244: '=': conversion from 'const double' to 'float', possible loss of data
C4244: '=': conversion from 'const tesseract::XHeightConsistencyEnum' to 'float', possible loss of data
C4244: '=': conversion from 'double' to 'FLOAT32', possible loss of data
C4244: '=': conversion from 'double' to 'PRIORITY', possible loss of data
C4244: '=': conversion from 'double' to 'float', possible loss of data
C4244: '=': conversion from 'double' to 'int32_t', possible loss of data
C4244: '=': conversion from 'float' to 'int', possible loss of data
C4244: '=': conversion from 'float' to 'int32_t', possible loss of data
C4244: '=': conversion from 'int' to 'FLOAT32', possible loss of data
C4244: '=': conversion from 'int' to 'float', possible loss of data
C4244: '=': conversion from 'int16_t' to 'int8_t', possible loss of data
C4244: '=': conversion from 'int16_t' to 'uint8_t', possible loss of data
C4244: '=': conversion from 'int64_t' to 'int32_t', possible loss of data
C4244: 'argument': conversion from 'FLOAT32' to 'const int', possible loss of data
C4244: 'argument': conversion from 'FLOAT32' to 'int', possible loss of data
C4244: 'argument': conversion from 'const double' to 'float', possible loss of data
C4244: 'argument': conversion from 'const float' to 'int', possible loss of data
C4244: 'argument': conversion from 'double' to 'FLOAT32', possible loss of data
C4244: 'argument': conversion from 'double' to 'const int', possible loss of data
C4244: 'argument': conversion from 'double' to 'float', possible loss of data
C4244: 'argument': conversion from 'double' to 'int', possible loss of data
C4244: 'argument': conversion from 'double' to 'int16_t', possible loss of data
C4244: 'argument': conversion from 'double' to 'l_float32', possible loss of data
C4244: 'argument': conversion from 'float' to 'int', possible loss of data
C4244: 'argument': conversion from 'float' to 'int16_t', possible loss of data
C4244: 'argument': conversion from 'float' to 'int32_t', possible loss of data
C4244: 'argument': conversion from 'int' to 'float', possible loss of data
C4244: 'argument': conversion from 'int' to 'l_float32', possible loss of data
C4244: 'argument': conversion from 'int32_t' to 'float', possible loss of data
C4244: 'initializing': conversion from 'double' to 'float', possible loss of data
C4244: 'initializing': conversion from 'double' to 'int', possible loss of data
C4244: 'initializing': conversion from 'float' to 'int', possible loss of data
C4244: 'initializing': conversion from 'int' to 'float', possible loss of data
C4244: 'initializing': conversion from 'int16_t' to 'uint8_t', possible loss of data
C4244: 'initializing': conversion from 'int32_t' to 'float', possible loss of data
C4244: 'initializing': conversion from 'int64_t' to 'int', possible loss of data
C4244: 'return': conversion from 'const double' to 'float', possible loss of data
C4244: 'return': conversion from 'double' to 'FLOAT32', possible loss of data
C4244: 'return': conversion from 'double' to 'PRIORITY', possible loss of data
C4244: 'return': conversion from 'double' to 'float', possible loss of data
C4244: 'return': conversion from 'float' to 'int', possible loss of data
C4251: 'tesseract::TessPDFRenderer::offsets_': class 'GenericVector' needs to have dll-interface to be used by clients of class 'tesseract::TessPDFRenderer'
C4251: 'tesseract::TessPDFRenderer::pages_': class 'GenericVector' needs to have dll-interface to be used by clients of class 'tesseract::TessPDFRenderer'
C4267: '=': conversion from 'size_t' to 'int16_t', possible loss of data
C4267: 'argument': conversion from 'size_t' to 'const char', possible loss of data
C4305: '=': truncation from 'double' to 'FLOAT32'
C4305: '*=': truncation from 'double' to 'float'
C4305: '=': truncation from 'double' to 'FLOAT32'
C4305: '=': truncation from 'double' to 'float'
C4305: 'argument': truncation from 'double' to 'float'
C4305: 'initializing': truncation from 'double' to 'FLOAT32'
C4305: 'initializing': truncation from 'double' to 'float'
C4305: 'initializing': truncation from 'double' to 'l_float32'
C4305: 'initializing': truncation from 'int' to 'float'
C4566: character represented by universal-character-name '\u05BE' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u0640' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2000' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2001' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2002' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2003' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2004' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2005' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u200E' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u200F' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2010' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2011' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2012' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2015' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2028' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2029' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u202A' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u202C' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2032' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2212' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\u2606' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uE003' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uE006' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uE007' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uE008' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uE009' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uFB01' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uFB02' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uFE58' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uFE63' cannot be represented in the current code page (1252)
C4566: character represented by universal-character-name '\uFF0D' cannot be represented in the current code page (1252)
C4838: conversion from 'double' to 'FLOAT32' requires a narrowing conversion
C4996: 'ltoa': The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _ltoa. See online help for details.
C4996: 'putenv': The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _putenv. See online help for details.
C4996: 'strdup': The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _strdup. See online help for details.
C4996: 'ultoa': The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _ultoa. See online help for details.
C4996: 'unlink': The POSIX name for this item is deprecated. Instead, use the ISO C and C++ conformant name: _unlink. See online help for details.

C4566: character represented by universal-character-name '\uFF0D' cannot be represented in the current code page (1252)

https://msdn.microsoft.com/en-us/library/mt708819.aspx

CC: @egorpugin
About C4566 ...

Pull request #1554 adds /utf-8 for the MS VC compiler which fixes C4566.

Warnings sorted by frequency:
      2 C4146
      4 C4267
      4 C4838
      6 C4068
     14 C4996
     20 C4251
     82 C4018
    416 C4305
2054 C4244

The most common warning is for conversions from double to float (and its synonyms). This can also be a performance issue because such conversions possibly cost execution time.

Some source files contain pragmas to  suppress msvc's warnings.

I'm just testing a new pull request which removes all those pragma statements.  :-)

Citing @db4 (from issue #2816):

I'm not sure it's a duplicate of #1036. The current behavior was introduced 01-Nov-2019 14:30:15 in 5e3772c and is specific to MSVC (while old #1036 mostly addresses gcc/clang). And it should be fixed before 4.1.1 release (in my case it's a real show-stopper: travis CI build job cannot complete in 1 hour)

Travis CI should work for 4.1.1, of course.

@db4, this is the latest Travis build for 4.1: https://travis-ci.org/tesseract-ocr/tesseract/builds/613358145. We don't use MSVC there.
MSVC is used with Appveyor CI: https://ci.appveyor.com/project/zdenop/tesseract/builds/28928329.

@stweil

MSVC is used with Appveyor CI

Sure. Of course, I meant Appveyor CI. Here is my failing build:
https://ci.appveyor.com/project/db4/conan-tesseract/builds/29433440

And a successful build after /Wall is removed:
https://ci.appveyor.com/project/db4/conan-tesseract/builds/29491104

@zdenop, what do you think? Can we remove /Wall for cmake in the 4.1 branch? That would be an easy solution. Fixing compiler warnings in that branch seems wasted time for me, I prefer focusing on the master branch.

IMO: Yes, we can remove it from 4.1.1 (e.g. as part of release process ;-) ) and keep it for master/devel.
To remove it completely: No. If we want to solve "all" warnings for all compilers (different compiler report could report different problem), we should report them somewhere... At the moment we report them only for debug release...

I sorted the compiler warnings by their frequency, and 99 % (12924) of all warnings are C4514 (unreferenced inline function has been removed). Is there a command line switch which only suppresses C4514? Then I'd suggest to add that to 4.1 and master.

/wd4514 iirc

Thank you, @egorpugin. @db4, could you please test whether `/Wall /Wd4514 works for you?

@stweil

could you please test whether /Wall /Wd4514 works for you?

No:
cl : Command line error D8021: invalid numeric argument '/Wd4514'

It should be /Wall /wd4514 (lower case w). Could you please try that?

@stweil
/wd4514 does not change much. 1 hour is still not enough for CI build (20K+ warnings are generated):
https://ci.appveyor.com/project/db4/conan-tesseract/build/job/db42lnclq3e2tgnh

@db4, that protocol lists 9557 warnings. The most frequent ones are 3864 times C4820 and 1088 times C4625. So /Wall /wd4514 /wd 4820 /wd1088 might be enough.

Maybe you need also /wd4458.

@stweil
OK, I can try these options as well. But I don't understand the purpose. If it's a workaround why don't just remove /Wall? The proper fix (in master branch?) should address source code inaccuracies that trigger warnings, not just selectively disable them.

I'd disable those warnings in master, too. Not every warning indicates a problem which has to be fixed (for example C4514 is normal), and other warnings are very low priority or shown by gcc or clang compiler, too, so there is no harm when they are disabled for MSVC.
As there are still backports of fixes from master to 4.1, disabling all warnings would give us no indicator of any progress or potential new problems.

Well, /Wall /wd4514 /wd 4820 /wd1088 /wd4458 options make AppVeyor compile time reasonable (just two times slower that Release build). But /Wall now looks like overkill even for Debug build (it generates warnings even in Microsoft headers). Maybe just use /W4 instead? That's what Microsoft itself recommends:

/W4 displays level 1, level 2, and level 3 warnings, and all level 4 (informational) warnings that are not turned off by default. We recommend that you use this option to provide lint-like warnings. For a new project, it may be best to use /W4 in all compilations; this will ensure the fewest possible hard-to-find code defects.

https://docs.microsoft.com/en-us/cpp/build/reference/compiler-option-warning-level?view=vs-2019
MSVC's -Wall seems like Clang's -Weverything.
-W<n> should be used.

@zdenop, can we replace /Wall by /W4 as suggested by @db4 for 4.1 and master?

Yes.

@db4, branch 4.1 and master now use /W4. Is this sufficient for your build to make it work?

@stweil

Is this sufficient for your build to make it work?

Yes, it is. Thank you very much.


Don't depend on filedistribution

No need to depend on filedistribution anymore, config defs are now in configdefinitions module

👍


should not replace this original data id with ES _id

I don't think this is a good way:
$attributes = $hit['_source'];
$attributes['id'] = $hit['_id'];
and if you search like this:
Question::search(['query'=>['match'=>['_all'=>'beijing']],'_source'=>['location','title','body']]);
I originally  don't want to get "id",but now I was forced got it ,in this case,it should be as a bug.

The _id field should be present even if you haven't created it in ES, so no errors should arise. Are you getting any error? What do you mean that you didn't want to get id, but now you're forced to get it?

@fadion I mean,that query's result was supposed not to have id,but i got it,cause id is is forced added from $hit.
In addition,_id from ES must be same as id from database? If i need use id in business logic would may get error or wrong data.

Bouncy creates a 1-to-1 mapping between ES and the database. In that way, it provides the convenience of Eloquent models, but without hitting the database on searches. When data is indexed via the index() method, the _id field is set the same as the row's id. For consistency, that _id is put back to the model when data is retrieved from ES.
Now that you mentioned it, I believe that using the _id in such a way can be problematic to those who index data manually and don't follow Bouncy's way of indexing. Will remove it.

@fadion Thank you .

Hello!
Well. I am unsure whether it was good  idea - to remove
$attributes['id'] = $hit['_id'];

I index also manually.
Using Bouncy for searching - and I like that I receive back eloquent model. But my methods within model rely on having set $attributes['id']
And I think in most cases it is more useful,to keep setting $attributes['id'] automatically.
Maybe it can be part of the config - to make it possible to disable auto setting $attributes['id']
What do you think?


Add ability to have extensions to dsc.exe

Summary of the new feature / enhancement
We should allow for community extensions to dsc.exe so they show up as sub-commands.  For example we may want to have dsc cache --clear which is supported by PS-Adapter extension.
Proposed technical implementation details (optional)
Extensions should be executables (or maybe an extension manifest?) that have -dsc suffix to the command, like cache-dsc.exe

Proposals:

Define a set of extension points for where/how the extension can interact with DSC.
Require a manifest, with a similar data structure as resources to indicate how the extension integrates.

1. Extension Points
I think we probably want to define a few common extension points to enable hooking into existing DSC commands. Separately, we should consider whether we want to support something similar to the GitHub CLI extension model, where integrating developers can define new commands for DSC.
Proposed built-in extension points

dsc cache <clear|refresh|init> (Cache) - A cache extension defines three commands - one to initialize a cache, one to refresh it, and one to clear it. Users can invoke the cache commands directly (e.g. dsc cache refresh. Before DSC executes a configuration operation, it follows the code path for initializing all known caches. The init command for a cache extension should return as soon as it knows whether the cache is already initialized. I'm not sure what input, if any, these commands should receive. They should exit with code 0 on success and can send messages, but not output, back to DSC.
dsc config resolve (Resolver) - A resolving extension defines a single command that operates on and returns a DSC configuration document. DSC calls this hook at the beginning of any dsc config operation, before final validation of the resolved document by DSC. This would enable extensions to pre-process a configuration - for example, you could define a resource instance generator or fill in non-specified default values, or whatever. Theoretically, you could also use this extension to enable authoring custom configuration functions. The only input and output for these extensions is a DSC configuration document.
dsc <command> [<subcommands>] (Command) - a command extension defines a new command for DSC at the top-level. The names of these commands must be unique and can't conflict with built-in commands.

Theoretically, an extension could do more than one of these, but it's probably better to have separate manifests, even if the app is shared across the three kinds.

Example command extensions

# Extension that shows a node graph for a configuration document or result
cat ./app.config.dsc.yaml | dsc graph # Show node graph for config document
dsc config get | dsc graph            # Show node graph for get result

# Extension that shows terminal-help for resources
dsc explain --resource Microsoft/OSInfo                     # Show full help
dsc explain --resource Microsoft/OSInfo --property codename # Show property help only
dsc explain --manifest ./tstoy.dsc.resource.json            # Inspect manifest for help

# Extension that helps with resource manifest DevX
dsc manifest new --type TailspinToys/tstoy --capabilities Get, Set, Export # Scaffold manifest
dsc manifest new --interactive                                             # Create with prompts
dsc manifest validate ./tstoy.dsc.resource.json                            # Test manifest
dsc manifest show ./tstoy.dsc.resource.json                                # Pretty-print manifest
dsc manifest show ./tstoy.dsc.resource.json --schema                       # Pretty-print schema

# Extension that handles packaging, installing, updating resources
# Validate that the MyResource folder has everything needed to publish a resource package
dsc package validate --folder ./MyResource
# Package the resource for publishing
dsc package build --folder ./MyResource --output-folder ./packages
# Publish the resource to the default repository
dsc package publish  ./packages/MyOrg.MyResource.dsc.package.json
# Search the GitHub container registry for resources
dsc package find resource
# List all locally installed packages
dsc package list
# Update locally installed packages
dsc package update

2. Manifests
I think that we should either require standalone manifests for an extension or extend the resource manifest to enable defining extensions. I'm hesitant to support both for the complexity/ambiguity.
I prefer a standalone manifest from an integration, testing, and packaging perspective.

Cache extension

$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/bundled/extension/manifest.json
type: Microsoft.DSC/PowerShellCache
description: Manage caching adapted PowerShell resources
tags:
- PowerShell
cache:
  init:
    executable: pwsh
    args:
    - -NoLogo
    - -NonInteractive
    - -NoProfile
    - -Command
    - './psDscAdapter/powershell.cache.ps1'
  clear:
    executable: pwsh
    args:
    - -NoLogo
    - -NonInteractive
    - -NoProfile
    - -Command
    - './psDscAdapter/powershell.cache.ps1 -Clear'
  refresh:
    executable: pwsh
    args:
    - -NoLogo
    - -NonInteractive
    - -NoProfile
    - -Command
    - './psDscAdapter/powershell.cache.ps1 -Refresh'

Example resolver extension manifest

$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/bundled/extension/manifest.json
type: Microsoft.DSC/InstanceGenerator
description: Pre-process a configuration to generate instances from a configuration function.
tags:
- DevX
resolve:
  executable: dsc-igen
  input:      stdin

Example custom command extension manifest (args)

$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/bundled/extension/manifest.json
type: Microsoft.DSC.Docs/Explain
tags:
- Docs
- Help
customCommand:
  executable: dsc-explain
  help:
    arg:   --help
    command: help
  args:
    - name: --resource
      type: string
      description: The type of the resource to show help for.
    - name: --property
      type: string
      description: The property of the resource to show help for.
    - name: --manifest
      type: string
      description: The path to the resource manifest to show help for.
  argSets:
    - required: --resource
      args: [--resource, --property]
    - required: --manifest
      args: [--manifest, --property]
  # In this case, we can be relatively lazy and just indicate it returns a Markdown string;
  # If the extension returned structured data, we would need to have the full schema here
  # for users and integrating tools.
  outputSchema:
    $schema: https://json-schema.org/draft/2020-12/schema
    $id:              https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/extensions/explain/output.json
    type:             string
    contentMediaType: text/markdown
    title:            Resource Documentation
    description:      The Markdown documentation for a resource or a property of the resource.

  # Has no subcommands, but use the same definition structure recursively.
  subcommands: []

This is probably the roughest example, as we need to be able to determine the argument definitions from the manifest. This requires much more thorough design and investigation. An alternative would be to require custom commands to specify a JSON schema for input and output both, then generate the CLI arguments from the schema properties (but always send the data to the extension as JSON either over stdin or to the JSON input argument).

Example custom command extension manifest (input schema)

$schema: https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/bundled/extension/manifest.json
type: Microsoft.DSC.Docs/Explain
tags:
- Docs
- Help
customCommand:
  executable: dsc-explain
  help:
    arg:   --help
    command: help
  args: []
  input: stdin
  schemas:
    input:
      $schema: https://json-schema.org/draft/2020-12/schema
      $id:              https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/extensions/explain/input.json
      oneOf:
      - required: [resource]
      - required: [manifest]
      properties:
        resource:
          type:        string
          description: The type of the resource to show help for.
        property:
          type:        string
          description: The property of the resource to show help for.
        manifest:
          type:        string
          description: The path to the resource manifest to show help for.
    output:
      $schema:          https://json-schema.org/draft/2020-12/schema
      $id:              https://raw.githubusercontent.com/PowerShell/DSC/main/schemas/2024/04/extensions/explain/output.json
      type:             string
      contentMediaType: text/markdown
      title:            Resource Documentation
      description:      The Markdown documentation for a resource or a property of the resource.


⚠ Young Discoverers has degraded performance

In ff3ec9e, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 5679 ms

Resolved: Young Discoverers performance has improved in 0676335.


Support new failOnDynamicVersionResolution()/failOnChangingModuleResolution() options for the ResolutionStrategy API

To support deterministic dependency resolution and build/test reproducibility, we need a way to prevent dependency versions from being selected/resolved dynamically and changing between builds at runtime.
Expected Behavior
The ResolutionStrategy API could include 2 new settings like:
failOnDynamicVersionResolution()
failOnChangingModuleResolution()

which would cause a Gradle failure when either dynamic version resolution or changing module resolution was to be used for selecting the resolved dependency artifact.
e.g: with failOnDynamicVersionResolution() set, I would expect that declaring a dependency on com.fasterxml.jackson.module:jackson-module-guice:2.9.8 which has a transitive dependency on com.google.inject:guice:[3.0,5.0) will cause a gradle failure unless I have also declared a dependency on a specific version of that module say com.google.inject:guice:4.2.0
Current Behavior
There is no clean/easy way to do this within the existing Gradle DSL, though it is possible to approximate the desired behavior by throwing an exception when a resolvedDependencyResult's selectionReason's description starts with "didn't match versions", but that doesn't seem to work for all dynamic versions and it's a really hacky solution!
Context
We're managing a large build system spanning multiple teams and repos, with one of our design goals being: reproducible builds/tests for any given git commit. A consequence of this is that we need our dependency resolution results to be deterministic for any given git commit.
We've been using lockfiles to support deterministic dependency resolution, but that isn't an ideal solution since the update procedure is burdensome on our devs, and it is still possible for any team to introduce dynamic dependencies that can require constant updates to keep the affected lockfiles up-to-date.
To help prevent our devs from shooting themselves in the feet like this, we want to implement a policy that just prohibits any reliance on dynamic dependency resolution in our builds, and fails fast when such a dependency is accidentally added.

As you stated, if the objective is reproducible build, dependency locking is the answer Gradle has.
I am not sure I understand the burdensome aspect you describe. Moving away from dynamic versions + locking back to single version declarations will move the burden to updating these versions away from updating the lock. I can understand the later feels more familiar initially though.

Since it's not obvious, let me try to describe the burdensome nature of our dev experience in maintaining the lockfile mechanism.
Our multi-project build currently comprises 431 projects, from 20+ separate teams, requiring 6043 lockfiles be checked-in.
With this quantity and scale of lockfiles it is not realistic to expect our devs to do any manual or targeted editing of these lockfiles. Instead, the common workflow is for devs to simply regenerate a complete replacement set of lockfiles starting from the root project directory, and then to include those lockfile changes in their commits.
This situation is problematic for us in a number of ways:

A 1 line change to the dependencies in the wrong project can literally require updates to tens of hundreds of lockfiles because of the transitive dependencies between projects.

We're using Bitbucket for our source control, and our code review process is significantly impacted when these overwhelming numbers of lockfile diffs are displayed. We have been hearing tons of complaints about this from our devs, and we have no real work arounds for them. There's no way to automatically hide or minimize just the lockfile diffs, meanwhile our devs are complaining that they're accidentally missing important changes in the PRs they are reviewing, because they have to manually pick the important changes out from so many hundreds of un-informative lockfile diffs.

The large surface area presented by the high numbers of lockfile changes in these commits also makes these PRs much more likely to be blocked for merge conflicts. Our devs back this up by grumbling that they are often required to do more than one pass through the whole "merge the latest changes from master", "regenerate lockfiles", "push new changes", "find reviewers for signoff", and "wait for the CI build/test cycle to complete successfully" workflow (for what they feel are trivial dependency changes), because their first attempts are being blocked by merge conflicts before their CI build/tests and reviewers have even had time to finish.

Being that regenerating the lockfiles is a manual step, we've found that this step is also often being missed by devs when they go to push a dependency update to their downstream projects, and as a consequence they waste a bunch of time shepherding an extra PR/merge that has no effect, or worse the devs move-on to doing other work with the false impression that their change is in effect and that their change has passed all the CI tests, while in fact the next unsuspecting dev to regenerate the lockfiles is now on the hook as the first dev to actually test their change.

To ensure that this manual step has not been missed and to avoid placing this burden on an unsuspecting downstream dev, we've implemented a pre-commit build pipeline task that ensures the lockfiles are always up-to-date for the declared dependencies of a change when the PRs are submitted. At this point we might as well be automating the process of regenerating the lockfiles to avoid the human errors, but then we're back to non-reproducible builds wherever a project declares a dynamic dependency for resolution.

This makes our build pipelines fragile. Since, there's currently no supported Gradle mechanism to enforce a policy which prohibits the use of dynamic dependency resolution, any dev can introduce dynamic dependencies that will then require constant updates to keep the lockfiles current. And since a dev could do this, a dev did do this: We had a dev decide their team's integration tests would depend on the latest build artifacts coming out of an upstream CI build pipeline. They used a dynamic version dependency 4.5.* for that, and as a consequence the related lockfiles were out-of-date after every build of that upstream CI pipeline. This then caused widespread CI build/test failures for unrelated teams, since the lockfile up-to-date checking pipeline task would detect that the affected lockfiles in all PRs (including PRs with no changes to dependency declarations) were now out-of-date after every run of that upstream CI pipeline.

I hope I have managed to illustrate how the lockfile mechanism is not an adequate solution for us to achieve reproducible builds. The lockfile mechanism does not make it easy to implement reproducible builds, and it does not guide our devs into doing the right thing of declaring reproducibly resolvable dependencies.
What we really want is a policy enforcement mechanism that will prevent devs from introducing any runtime dynamism into the dependency version resolution process. And, if we had had that mechanism to start with we wouldn't have needed to introduce the lockfile mechanism or the burdens that came with it.

As locking does not seem practical / desired in your setup, here is how you can make sure no dynamic versions enter the graph:
plugins {
    `java-library`
}

repositories {
    mavenCentral {
        // The lister referenced here will be called _every time_ a dynamic version is requested
        // if and only if the result is not cached by Gradle. Cache expires after 24h by default
        setComponentVersionsLister(DenyDynamicVersion::class.java)
    }
}

dependencies {

    // Adding the following declaration skips the dynamic resolution
//    implementation("com.google.inject:guice:4.2.2")

    // Adding the following will clean the metadata to remove the dynamic version
//    components {
//        withModule("com.fasterxml.jackson.module:jackson-module-guice", ForceGuiceVersionWhenDynamic::class.java)
//    }

    // A transitive dependency on com.google.inject:guice:[3.0,5.0) will trigger the version lister, failing resolution.
    implementation("com.fasterxml.jackson.module:jackson-module-guice:2.9.8")

    testImplementation("junit:junit:4.12")
}

class DenyDynamicVersion : ComponentMetadataVersionLister {
    override fun execute(details: ComponentMetadataListerDetails) {
        throw IllegalStateException("Using a dynamic version for ${details.moduleIdentifier}")
    }

}

class ForceGuiceVersionWhenDynamic : ComponentMetadataRule {
    override fun execute(t: ComponentMetadataContext) {
        t.details.allVariants {
            withDependencies {
                filter { it.group == "com.google.inject" && it.name == "guice" && it.versionConstraint.displayName.contains("[")}.forEach {
                    it.version { require("4.2.2")}
                    it.because("No dynamic versions are allowed")
                }
            }
        }
    }
}

I recommend setting up something like that in your build as there is no plan to add the requested methods.

For changing version, again a ComponentMetadataRule is what you need:
dependencies {
    // Adding the following will prevent _changing_ modules in  in direct and transitives dependencies
    components {
        all(DenyChangingModules::class.java)
    }
}

class DenyChangingModules : ComponentMetadataRule {
    override fun execute(t: ComponentMetadataContext) {
        if (t.details.isChanging) {
            throw IllegalStateException("Detected changing module ${t.details.id}")
        }
    }
}

Note that ComponentMetadataRule are executed in order in which they are added. If another rule in the build changes a component to changing after this rule has been applied, then it will not be detected.

Closing as adding the feature is not planned and solutions have been provided.

This will be integrated in upcoming Gradle 6.1, see PR #10936 for details

The PR has been merged. @steffenyount would be great if you could try this nightly and let us know if it works for you.

@melix - Hi!
I wanted to let you know that I'm really excited that this change has made it into the mainline codebase, and I'm looking forward to rolling it out on our large multi-project build!
Unfortunately, that build still needs to be fixed to avoid some deprecated functionality with the move to Gradle 6+ versions. So simply plugging the nightly build into that project for an acceptance test isn't as straightforward as I would like.
Alternatively, I guess I could build a local toy/test project that exercises the new code, but I'm a bit strapped for time right now (probably for the next few weeks), and I assume you've already done something similar in your test codes?
Again, thanks and this is awesome!

I assume you've already done something similar in your test code?

Yes we do, but nothing's better than a real world project to test :)


I can edit my details including: photo, name, bio, phone, email and password

[ ] name
[ ] bio
[ ] photo
[ ] phone
[ ] email
[ ] password


FMP OpenShift mode S2I Failed running assemble script - /bin/sh: 1: /usr/libexec/s2i/assemble: not found

Description
I am trying the FMP plugin in order to deploy Spring Boot application to an OpenShift platform. However, as the build process is in progress, it failed when running some kind of assemble script(?):
...omitted...
[INFO] F8: STEP 1: FROM openjdk:8
[INFO] F8: STEP 2: LABEL "io.openshift.build.source-location"="/tmp/build/inputs"       "io.openshift.build.image"="openjdk:8"
[INFO] F8: STEP 3: ENV OPENSHIFT_BUILD_NAME="springboot-s2i-demo-s2i-1"     OPENSHIFT_BUILD_NAMESPACE="cipley-project"
[INFO] F8: STEP 4: USER root
[INFO] F8: STEP 5: COPY upload/src /tmp/src
[INFO] F8: STEP 6: RUN chown -R 1001:0 /tmp/src
[INFO] F8: STEP 7: USER 1001
[INFO] F8: STEP 8: RUN /usr/libexec/s2i/assemble
[INFO] F8: /bin/sh: 1: /usr/libexec/s2i/assemble: not found
[INFO] F8: subprocess exited with status 127
[INFO] F8: subprocess exited with status 127

Which then proceeds with it throwing an error:
[ERROR] F8: Failed to execute the build: org.apache.maven.plugin.MojoExecutionException: OpenShift Build springboot-s2i-demo-s2i-1 failed: Failed: GenericBuildFailed
This might be related to #1663
The Build Config is generated on OpenShift, however the build itself is failed, and the pod is not running.
Build Config

Build

mvn -X output
mvn_out.txt
Info

f-m-p version : 4.4.1
Maven version (mvn -v) :

Apache Maven 3.6.3 (NON-CANONICAL_2019-11-27T20:26:29Z_root)
Maven home: /opt/maven
Java version: 11.0.7, vendor: GraalVM Community, runtime: /home/cipley/.sdkman/candidates/java/20.1.0.r11-grl
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.6.15-1-manjaro", arch: "amd64", family: "unix"

Kubernetes / OpenShift setup and version : OpenShift Code Ready Container 1.12
There is a project already created named cipley-project.
If it's a bug, how to reproduce : from sample project, execute mvn clean initialize package, with CRC running and logged in as developer.
If it's a feature request, what is your use case : N/A
Sample project : https://github.com/cipley/springboot-s2i-demo.git

It probably is related to #1663
It looks like the generated Assembly artifact is no longer compatible with the S2I build image.
We are currently shifting all our development efforts towards Eclipse JKube. I think our current alpha-4 version should be stable enough for your use case (we'll be releasing an RC-1 very soon too). It would be very helpful :heart: for us if you tried JKube and shared your feedback for your current use cases.

Ah, I see. I checked out the JKube some time ago, upon discovering that it is the successor of FMP, however I shied away from it since it is still in alpha.
I guess I have to give it a try now that FMP is unsupported.
Since I want to try the S2I capability, is there any workaround for my current setup or should I just change to JKube altogether?

Since I want to try the S2I capability, is there any workaround for my current setup or should I just change to JKube altogether?

It should work OOTB for you. Just be sure to use openshift-maven-plugin:
<plugin>
    <groupId>org.eclipse.jkube</groupId>
    <artifactId>openshift-maven-plugin</artifactId>
    <version>1.0.0-alpha-4</version>
</plugin>

HI @manusa , I have tried to use JKube with the version that you provided, however I still have the same error.
I'm not sure whether to continue the issue here or should I open another one in JKube page instead?

:( Please if you can open the issue on JKube and provide some way to reproduce.

OK, just saw your attached project
Image is not S2I compatible. Try to replace your base image with ours quay.io/jkube/jkube-java-binary-s2i:0.0.7. (${docker-from})

OK, just saw your attached project
Image is not S2I compatible. Try to replace your base image with ours quay.io/jkube/jkube-java-binary-s2i:0.0.7. (${docker-from})

Hi @manusa your suggestion worked!
Granted, I was not aware that the base image was not compatible, since I was just tried the DMP in order to deploy to OpenShift.
I retried my build using the FMP 4.4.1 just like my initial configuration.
The s2i build was succeeded for the first deployment. Alas, for the subsequent deployments, it still throws error while trying to build as attached:

Perhaps it was time to move on to JKube.....

@manusa I confirmed the above error does not show up with JKube.
So I guess I have to move on to JKube as you suggested. Still, many thanks for your inputs!
I'll close this issue.

Perhaps it was time to move on to JKube.....

Time to move on ;)
I'm sorry, I was unclear, the base image I proposed is specifically designed for JKube and its provided generators.


GN-4323: Insert fragment

N.B. Note that this PR is one of 5 (currently) PRs for insert fragment functionality, I've tried to break them down into smaller parts.
Overview

This PR completed the 5 part series of PRs for Fragment insert, you can actually insert a fragment with this PR :D
Connected issues and PRs:
https://binnenland.atlassian.net/browse/GN-4323
Setup
You will need a running https://github.com/lblod/app-reglementaire-bijlage for this to work.

Start the app-reglementaire-bijlage
Create some snippets there
Start this package with PORT=4300 npm run start
Go to https://localhost:4300, observe same as in video

https://github.com/lblod/ember-rdfa-editor-lblod-plugins/assets/769698/75c64db8-2719-476a-8a49-19b7cd316782

For convenience, could you please merge this pr stack into 1, it's getting quite annoying to work with


Improve flow for contributors adding emails

When contributors want to add their city, they are directed to the "issues" page, and then they're on their own to add an issue, maybe following the given template.
This directly links them to an already templated issue, ready for them to read the succint guidelines and adapt the skeleton. This should move a significant amount of editing and moderating work out to the masses, instead of the team here.

I asked quickly in discord what people thought of this idea, and several seemed to like it. We can see if I managed to keep the template guidelines in the right balance of brief and detailed.


Line beginning prepend auto list

‸

Some text...‸

‸Some text...

- ‸Some text...

Should optionally result in a auto list too.

What you think?

@aight8 This is actually sort of an intentional behaviour at the moment.
There are legitimate reasons to want to being an block with a Markdown list character without wanting it converted to a list, and so this plugin only converts them as lists are started from scratch. The draft-js-markdown-shortcuts-plugin approach is different: they check the entire line when an input is typed to convert. That’ll catch the use case you’re after, but it doesn’t give the same flexibility.


Description for fields is missing

Describe the Bug
Description for fields is missing
Steps to Reproduce

Have this template and apply it:

{
    "$schema": "https://unpkg.com/<EMAIL_ADDRESS>    "name": "WS Caller Task",
    "id": "com.camunda.example.WsCaller",
    "description": "Requires the user to provide a Web Service URL.",
    "appliesTo": [
      "bpmn:ServiceTask"
    ],
    "properties": [
      {
        "label": "Web Service URL",
        "description": "Specify the url of the web service to talk to.",
        "type": "String",
        "binding": {
          "type": "camunda:property",
          "name": "webServiceUrl"
        },
        "constraints": {
          "notEmpty": true,
          "pattern": {
            "value": "^https://.*",
            "message": "Must be https URL."
          }
        }
      },
      {
        "type": "Hidden",
        "value": "com.camunda.example.WsCaller",
        "binding": {
          "type": "property",
          "name": "camunda:class"
        }
      }
    ]
  }

===> Notice that the description for the custom input is not displayed in the UI
"description": "Specify the url of the web service to talk to."

Expected Behavior
Description for inputs are shown in UI in accordance with template configuration.
Environment
https://github.com/bpmn-io/bpmn-properties-panel/pull/161

This is a missing feature on the CustomProperties.


Adding Lawtex language support

This adds support for the Lawtex language.

Lawtex is a language developed by a Brazilian startup. The purpose of it is to make programming easier for law students or law professionals. The ideal of the startup is to make programming more accessible and facilitate the creating of programs that write and format legal documents.
Since it is a Brazilian startup all the documentation that I have concerning the language is in Portuguese, so I'm not sure what I should share here.

I'll close this now. Without documentation, I cannot review this. There's also the problem that searching for "lawtex" only yields a popular Tex package.


Manifest Issue

We can not use this in an OSGI env since you have declared all the packages private.
Private-Package: hu.akarnokd.rxjava3.jdk9interop

Hi. Thanks for the report. Should be fixed in v3.0.1 I just released.


examples/c/calc/calc.c fails

  YACC     examples/c/calc/calc.c
Assertion failed: kernel_base[i] + kernel_size[i] <= kernel_base[i + 1], file: src/lr0.c, line: 167, function: kernel_check

Note this has assertions on - possibly because I had been working with a debug bison build.

with assertions off, it is still failing. A testcase is now in tests called basic.sh. Run it and it gets killed... Optimization bug?

fails when building at no-opt too (darn)


Bower/Browserify dependancies with plugins

There seems to be a dependency requirement issue In the plugin files in the Bower package.
The KUTE.js/kute-jquery.js file has the correct requirement of the kute.js file. However the other plugins us  define(['kute.js'], factory); and module.exports = factory(require('kute.js'));
In order for the files to compile correctly with Browserify, I have to change those to reference the kute.js file itself (notice the ./ ):  define(['./kute.js'], factory); module.exports = factory(require('./kute.js'));
Is that a change that should be made in the plugin files or should I requiring KUTE in a different way?
Here's an example of my js file:
require( '../../node_modules/jquery/dist/jquery.js' ); require( '../vendor/KUTE.js/kute.js' ); require( '../vendor/KUTE.js/kute-jquery.js' );
Which works file. But when I add:
require( '../vendor/KUTE.js/kute-css.js' ); (or any of the other plugins files) I get an error: "Cannot find module 'kute.js'"
But when I changed the lines I mentioned above to use the file, they worked and were compiled correctly.

You must require exactly as they wrote in the README.md as this
require( '../vendor/KUTE.js/kute.js' ); doesn't look fine to me.

I guess the question I was asking is more along the lines of:
When i include the plugins in the same way, only the kute-jquery plugins works. And looking at the top of the files I can see why.
The kute-jquery plugin is looking for the dependency of './kute.js'  however the other plugin files are looking for the dependency of 'kute.js'.  Here's the top of kute-css.js:
(function(root,factory){
if (typeof define === 'function' && define.amd) {
define(['kute.js'], factory);
} else if(typeof module == 'object' && typeof require == 'function') {
module.exports = factory(require('kute.js'));
} else if ( typeof root.KUTE !== 'undefined' ) {
factory(root.KUTE);
} else {
throw new Error("CSS Plugin require KUTE.js.")
}
})(this, function(KUTE){
'use strict';
And here's the top of kute-jquery.js:
(function(root,factory){
// We need to require the root KUTE and jQuery.
if (typeof define === 'function' && define.amd) {
define(["./kute.js", "jquery"], function(KUTE, $){
factory($, KUTE);
return KUTE;
});
} else if(typeof module == "object" && typeof require == "function") {
// We assume, that require() is sync.
var KUTE = require("./kute.js");
var $ = require("jquery");
// Export the modified one. Not really required, but convenient.
module.exports = factory($, KUTE);

} else if (typeof root.KUTE !== "undefined" && (typeof root.$ !== 'undefined' || typeof root.jQuery !== 'undefined' ) ) {
// jQuery always has two ways of existing... Find one, and pass.
var $ = root.jQuery || root.$, KUTE = root.KUTE;
factory($, KUTE);
} else {
throw new Error("jQuery Plugin for KUTE.js depend on KUTE.js and jQuery");
}
})(this, function($, KUTE) {
'use strict';
Obviously different but if you look at line 10 of kute-jquery.js you'll notice that the reference to kute.js is to the file:./kute.js` and not to just "kute.js".
However the other plugins do not refer to the file, and therefore do not compile correctly.
Currently (after some more fiddling) I'm requiring the files like so (the only difference is the path to the library is in a separate vendor folder and needs the proper path):
var kute = require( '../vendor/kute.js' ); require( '../vendor/kute.js/kute-jquery' ); require( '../vendor/kute.js/kute-css' );
And it successfully compiles kute.js and kute-jquery, but errors on kute-css with the error of "Cannot find module 'kute.js'" because it's not using the file reference in kute-css.js (per the examples I pasted in above. If I change the two references in that top portion of kute-css.js to ./kute.js instead of just kute.js it compiles perfectly.

I am not the one who have done the UMD wrappers, I may have changed them to not work anymore, I really cannot tell.
Can you please fork it, do the changes as you see fit, install from Github and report back?

https://github.com/thednp/kute.js/commit/a8ca9a53172a3b225838863aeb910e7aa9b2c422


Language Report

As a member of the cultural research team at the organization, I want to know the number of people who speak Chinese, English, Hindi, Spanish, and Arabic, including the percentage of the world population, to help in planning cultural events and language-based programs.

Completed.