Problem with concatenate str

Describe the bug
While checking the logs I found this error:
This error originated from a custom integration.

Logger: custom_components.toyota
Source: custom_components/toyota/__init__.py:105
Integration: Toyota Connected Services (documentation, issues)
First occurred: 12:36:01 PM (1 occurrences)
Last logged: 12:36:01 PM

Unexpected error fetching toyota data: can only concatenate str (not "dict") to str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 164, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/toyota/__init__.py", line 105, in async_update_data
    data = await asyncio.gather(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/client.py", line 419, in get_driving_statistics
    raw_statistics = await self.api.get_driving_statistics_endpoint(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/api.py", line 96, in get_driving_statistics_endpoint
    return await self.controller.request(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/controller.py", line 219, in request
    "Internal server error occurred! - " + response
TypeError: can only concatenate str (not "dict") to str

I'm not sure when this happend and how to reproduce it.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Describe the bug While checking the logs I found this error:
This error originated from a custom integration.

Logger: custom_components.toyota
Source: custom_components/toyota/__init__.py:105
Integration: Toyota Connected Services (documentation, issues)
First occurred: 12:36:01 PM (1 occurrences)
Last logged: 12:36:01 PM

Unexpected error fetching toyota data: can only concatenate str (not "dict") to str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 164, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/toyota/__init__.py", line 105, in async_update_data
    data = await asyncio.gather(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/client.py", line 419, in get_driving_statistics
    raw_statistics = await self.api.get_driving_statistics_endpoint(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/api.py", line 96, in get_driving_statistics_endpoint
    return await self.controller.request(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/controller.py", line 219, in request
    "Internal server error occurred! - " + response
TypeError: can only concatenate str (not "dict") to str

I'm not sure when this happend and how to reproduce it.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.

Same issue my end - even with the last version update:
022-12-08 14:54:36.641 ERROR (MainThread) [custom_components.toyota] Unexpected error fetching toyota data: can only concatenate str (not "dict") to str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 225, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 181, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/toyota/__init__.py", line 105, in async_update_data
    data = await asyncio.gather(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/client.py", line 419, in get_driving_statistics
    raw_statistics = await self.api.get_driving_statistics_endpoint(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/api.py", line 96, in get_driving_statistics_endpoint
    return await self.controller.request(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/controller.py", line 219, in request
    "Internal server error occurred! - " + response
TypeError: can only concatenate str (not "dict") to str

Describe the bug While checking the logs I found this error:
This error originated from a custom integration.

Logger: custom_components.toyota
Source: custom_components/toyota/__init__.py:105
Integration: Toyota Connected Services (documentation, issues)
First occurred: 12:36:01 PM (1 occurrences)
Last logged: 12:36:01 PM

Unexpected error fetching toyota data: can only concatenate str (not "dict") to str
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 164, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/toyota/__init__.py", line 105, in async_update_data
    data = await asyncio.gather(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/client.py", line 419, in get_driving_statistics
    raw_statistics = await self.api.get_driving_statistics_endpoint(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/api.py", line 96, in get_driving_statistics_endpoint
    return await self.controller.request(
  File "/usr/local/lib/python3.10/site-packages/mytoyota/controller.py", line 219, in request
    "Internal server error occurred! - " + response
TypeError: can only concatenate str (not "dict") to str

I'm not sure when this happend and how to reproduce it.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.

Same issue here as well.

Logger: custom_components.toyota
Source: custom_components/toyota/init.py:105
Integration: Toyota Connected Services (documentation, issues)
First occurred: 16:51:16 (2 occurrences)
Last logged: 16:52:10
Unexpected error fetching toyota data: can only concatenate str (not "dict") to str
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 217, in _async_update_data
return await self.update_method()
File "/config/custom_components/toyota/init.py", line 105, in async_update_data
data = await asyncio.gather(
File "/usr/local/lib/python3.10/site-packages/mytoyota/client.py", line 419, in get_driving_statistics
raw_statistics = await self.api.get_driving_statistics_endpoint(
File "/usr/local/lib/python3.10/site-packages/mytoyota/api.py", line 96, in get_driving_statistics_endpoint
return await self.controller.request(
File "/usr/local/lib/python3.10/site-packages/mytoyota/controller.py", line 219, in request
"Internal server error occurred! - " + response
TypeError: can only concatenate str (not "dict) to str
I also have this issue too any update on resolving this issue. Thanks Peter

We recently released version 2.0.0 of the Custom Component with major changes and support for the new Mytoyota API.
As we unfortunately cannot provide support for Custom Component versions < v2.0.0, I hereby close your issue.
If the issue still applies to the current version, you are of course free to open a new issue. 😊


Cloud Save

We should use Dropbox, and maybe Onedrive to backup save files.

I personally do not believe it is our best interest to store world saves online for players. The amount of data we would need to store would exponentially grow. The best thing to do is a let a player zip of the world files and back up them up themselves. We should see all save files in the directory and give the player to load the worlds found, regardless if it was made on the users machine or a different one.

What I meant by this was allowing the player's to sign into their personal onedrive...dropbox...google etc and cloud save in their space.


ERROR: Source Location must be an object.

I received the above ERROR when I tried to contribute about 25 "declared licenses" at once.

@ariel11 Can you confirm this is still an issue for you? If not I'll close this and we can reopen if you have the trouble again.

@fossygirl - OK to close.  We will see if it happens again.

I received the above error when I tried to contribute the following components:
https://clearlydefined.io/definitions/git/github/abrkn/semaphore.js/4b7471c5efc348b3279621e58e0b47b55ac60040
https://clearlydefined.io/definitions/git/github/go-logfmt/logfmt/d4327190ff838312623b09bfeb50d7c93c8d9c1d
https://clearlydefined.io/definitions/git/github/go-stack/stack/100eb0c0a9c5b306ca2fb4f165df21d80ada4b82
It is likely there will be more components with the same issue in a big patch to curate for Azure Stack.

@geneh

@AE49 may i ask you what was the content of the contribution? I would like to reproduce it on our dev environment. Thanks!

@storrisi Hi, I was adding MIT as the Declared License, and when I hit contribute I get the error.

@AE49 thanks for clarifying it. I will check.

I'm sorry, but i'm still unable to reproduce this problem.
I've tried different approaches:

from the workspace list
from the detail page

The results is the same: every time i change something and hit Contribute, the Contribute Modal prompts correctly.
Maybe a screenshot when the error happens would help.

@storrisi thanks for checking. The first one is now showing as curated and the other two as pending so perhaps there's no issue to resolve. We can close this for now.

This is still happening -

This is being tracked on https://github.com/clearlydefined/website/issues/792.


Remove bundle install --cache

Removes the --cache option and replaces it with an error that asks the user to run bundle cache.

This currently violates some RuboCop style guidelines, but it should pass after I rebase master onto 2-0-dev and rebase 2-0-dev onto this branch.

👍🏻

@homu r+

:pushpin: Commit efa2a3e has been approved by segiddins

:hourglass: Testing commit efa2a3e with merge e56b718...

:sunny: Test successful - status


Linker error: Cardboard SDK 0.5.2, Unity 5.2.1, Xcode 7.1.1, -ObjC flag

There appears to be an issue building an iOS project when the "-ObjC" compiler flag is used (in this case, because the Cast Remote Display Plugin requires this flag). The output is below; is this an issue that can be addressed? Thank you.
Undefined symbols for architecture arm64:
"gvr::CreateMainApp__EXPECTED_EXACTLY_ONE_VR_MAIN_APP_STATEMENT__(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > > > const&)", referenced from:
l001 in libvrunity.a(vr_ios.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It is definitely being addressed for an upcoming release.  As a workaround, try including this code in a C++ file:
#include <vector>
namespace gvr {
    class VrApp;
    VrApp* CreateMainApp__EXPECTED_EXACTLY_ONE_VR_MAIN_APP_STATEMENT__(const std::vector<std::string>&) { return nullptr; }
}

Excellent, this allowed the build to succeed; thanks!

This should also be fixed in the new v0.6 release -- we pretty much did exactly the same thing in the native code.


Extracted inner interface to resolve Eclipse compilation issues and warnings

Inner interface SelectorComponentContext triggered Eclipse compiler errors and warnings

🎉 This issue has been resolved in v0.0.11 (Release Notes)


In a table-driven spec, gauge --failed should execute failed scenarios against failed table rows

In a table-driven spec with 3 scenarios, if 1st scenario failed for rows 1, 2, 4 and 2nd scenario for rows 1 to 3 then on running gauge --failed should execute scenarios against the failed table rows. So 1st scenario will be executed against 1,2,4 rows and 2nd scenario for rows 1,2,3
Depends on #415

Closing this as Gauge will not be implementing this feature.


Ensure react-resizable and react-draggable don't use deprecated lifecycle methods

[x] react-draggable
[x] react-resizable (candidates: https://github.com/STRML/react-resizable/pull/110, https://github.com/STRML/react-resizable/pull/107)

Blocker for 0.17.0 as I'd like it to be React 16.9-compatible out of the box.

React-resizable done in https://github.com/STRML/react-resizable/pulls?q=is%3Apr+is%3Aclosed.
Closing 0.17.0 milestone!


License Assignment Questions

Does the scheduler license get assigned to users, or to the Cortana account?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: db644b10-3e07-35eb-9f68-f0bf184e4c27
Version Independent ID: 6c17de36-8318-651c-35a4-afa31fe4b84f
Content: Scheduler for Microsoft 365 FAQs
Content Source: microsoft-365/scheduler/scheduler-faqs.md
Service: scheduler
GitHub Login: @AshaIyengar21
Microsoft Alias: v-aiyengar

@msbemba Thank you very much for the contribution and sharing this explanation. @adagioajanes Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

I believe this should be added to the documentation. It is not clear on any of the Scheduler documentation what account needs to be licensed. Please add that the license must be assigned to the end user, not the Cortana account.


Require Node.js 8, add TypeScript definition

I deliberately didn't manually type the .json files here, I've used the resolveJsonModule compiler option. I'm not sure whether this is a good solution for users, they'll get any for .yes, .no, and .all properties if they don't have this option enabled in their tsconfig.json. I think that maintenance-wise this is the way to go.

Sounds good


fix: documentation broken links in production.

These paths are using hardcoded absolute paths; this works in a local hugo serve, but will not work in hugo server --baseURL <host>/distribution/, which is how the actual production docs are deployed.
Either you convert all of these to relative- which means hugo still can't flag broken links like these- or you use the rel tag to have hugo render it.
The benefit of rel is it makes the content prefix movable, and hugo will break the build if you refer to something internal that doesn't exist.
Either way, this fixes the broken documentation; storage links, about links, etc.
For further commentary, see discussion thread in PR #4238.
For auditing/repro, this change was generated via:
grep -r '(/'  . -l | xargs -n1 sed -i -re 's:\(/([^)]+)\):({{< ref "/\1" >}})/:'

From there, a hugo build was ran to verify the changes didn't introduce broken intra-links.

@thaJeztah pardon to pull you across two PRs; I wound up poking at this and it was a few minutes rather than a shiteload of auditing.
Basically all of your abspath intra site documentation links are broken; see the PR, you can verify each manually.  This fixes it so they render correctly as long as --baseURL is set correctly (which you can test w/ either hugo serve or just a straight up hugo build).
This change will fix the issue of content being at /distribution . I'd suggest double checking your github workflows to ensure it shoves a proper baseURL into the doc builds; if it doesn't, you're still going to see issues from configuration.


Create abstraction over search_after for pagination

Elasticsearch recommends using search_after instead of the scroll API for pagination. Using it requires lots of knowledge about Elasticsearch though, and it's quite cumbersome currently.
We should provide a simple wrapper for this new pagination API.

@Radiergummi Hi
I added PIT mechanism as part of this issue, how can I push it?

Hi @chai-masalla, I'd be very much interested in this!
To add your changes, please follow the contribution guide by GitHub, and I will review and merge the PIT feature. Excited to have this in the library 🙂


[BUG]kbcli addon enable ob failed on upgrade kb

install kb  0.8.2-beta.13
upgrade kb to  0.8.2-beta.16
kbcli addon enable oceanbase failed

➜  ~ kbcli addon describe oceanbase
Name:               oceanbase
Description:        OceanBase Database is an enterprise-level native distributed database independently developed by Ant Group.
Labels:             addon.kubeblocks.io/model=RDBMS,addon.kubeblocks.io/name=oceanbase,addon.kubeblocks.io/provider=community,addon.kubeblocks.io/version=0.8.1
Type:               Helm
Status:             Failed
Auto-install:       false

Default install selector: NONE
NAME   REPLICAS   STORAGE   CPU (REQ/LIMIT)   MEMORY (REQ/LIMIT)   STORAGE-CLASS   TOLERATIONS   PV-ENABLED
main                        /                 /

Failed Message
TIME                         REASON                   MESSAGE
Mar 06,2024 12:35 UTC+0800   InstallationFailedLogs   Release "kb-addon-oceanbase" does not exist. Installing it now.
                                                      Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationE
                                                      rror(ComponentDefinition.spec.lifecycleActions.roleProbe): unknown field "failureThreshold" in io.kubeblocks.apps.v1alph
                                                      a1.ComponentDefinition.spec.lifecycleActions.roleProbe

dup https://github.com/apecloud/kubeblocks-addons/issues/334


How to set gradient ColumnarType1Renderer in custom renderer?

Hi
I doing custom ColumnarType1Renderer implement IRenderer. I want to set LinearGradient but i don't know position x0, y0, x1, y1 of wave ColumnarType1Renderer.
mPaint.shader = LinearGradient(
0f,
0f,
0f,
0f,
Color.parseColor("#FF7050"),
Color.parseColor("#B42F8F"),
Shader.TileMode.MIRROR
)
So. I want to know position to set gradient wave music ColumnarType1Renderer. Please , help me
Tks so much

Hi, @khiemdnt , I think you can try to set it according to mLastDrawArea field, please refer to the draw codes:
override fun render(canvas: Canvas) {
        canvas.save()
        canvas.translate(mLastDrawArea.left.toFloat(), (mLastDrawArea.top + mLastDrawArea.bottom) / 2F)
        mRenderColumns.forEach {
            canvas.drawRoundRect(it, mRadius, mRadius, mPaint)
        }
        canvas.restore()
    }


Crash when running make: Method 'append' not found for invocant of class 'Array'

I tried cloning this repo and building the docs. I ran make, the htmlify module crashed with the following error:
$ cd doc
$ make
perl6 htmlify.p6
Initializing ...
Creating html/ subdirectories ...
Reading type graph ...
Method 'append' not found for invocant of class 'Array'
  in method roles at /Users/shanek/code/perl6doc/doc/lib/Perl6/TypeGraph.pm:46
  in regex roles at /Users/shanek/code/perl6doc/doc/lib/Perl6/TypeGraph.pm:14
  in regex TOP at /Users/shanek/code/perl6doc/doc/lib/Perl6/TypeGraph.pm:22
  in method parse-from-file at /Users/shanek/code/perl6doc/doc/lib/Perl6/TypeGraph.pm:61
  in method new-from-file at /Users/shanek/code/perl6doc/doc/lib/Perl6/TypeGraph.pm:30
  in sub MAIN at htmlify.p6:124
  in block <unit> at htmlify.p6:764

I'm new to perl6, (and new to perl in general), but it looks like Array.append is not part of the language.
My environment (on OSX Yosemite) :
$ brew info rakudo-star
rakudo-star: stable 2015.09 (bottled)
Perl 6 compiler
http://rakudo.org/
Conflicts with: parrot
/usr/local/Cellar/rakudo-star/2015.09 (815 files, 37M) *
  Poured from bottle
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/rakudo-star.rb

$ perl6 --version
This is perl6 version 2015.09 built on MoarVM version 2015.09

Sorry, but your Rakudo is too old and I don't think there's a Rakudo Star release yet with the latest and greatest Rakudo in it. You could rakudobrew the latest and greatest though (scroll down further in the page for instructions): http://rakudo.org/how-to-get-rakudo/
We're still in Beta so things are changing rapidly :smile_cat:
Another option would be to checkout an older commit. I believe anything earlier than this one will work: https://github.com/perl6/doc/commit/e675207e08eb12cac4618a849a33bb8fd85def9e
I've ran make with the latest rakudo and all seems to work fine.
Cheers,
ZZ


Disable the submit button in the Request Connector form when needed

Related issue
https://github.com/CartoDB/cartodb/issues/15353
Acceptance
(This can be done in staging cloud)

Click on New dataset button
In Connect tab, click on Request connector. A new form will appear.
Inspect the form via DevTools.

[x] Check the submit button is really disabled and has is-disabled CSS class

Fill in the input text

[ ] Check the submit button is enabled and hasn't is-disabled CSS class

Clear the input text

[x] Check the submit button is really disabled and has is-disabled CSS class

Fill in the input text
Send the request
Click on Ok, got it and click on Request connector.

[x] Check the submit button is really disabled and has is-disabled CSS class

Hi! I have done the acceptance. I have checked that the button is always disabled in all the steps (which I think is the correct behavior) could you confirm that @alejandraarri?

Oh, I think I was checking the wrong button, testing again.


Maintainer wanted

If anybody want to maintain this project, please comment below. I'll transfer the ownership of this repository and the npm package (please let me know your npm account too).

No volunteering (yet), but please make sure the new maintainer isn't malicious, before transfering ownership...
A number of projects rely on this dependency and we don't want to get a second event-stream vulnerability in the wild, don't we? :)
I'll talk to my company and check if we can afford to invest some working days to maintain this package ourselves

@IlCallo Thanks for your advice. You're absolutely right. I'll try my best to ensure that the new maintainer isn't malicious.

Hello!
I've contacted the rest of the team from MDB  and we would be happy to continue maintaining the project :)
We've got both people and resources at the moment so it would be a "perfect" project for us. Please contact me directly at<EMAIL_ADDRESS>if you need any details :)
Our NMP: https://www.npmjs.com/~mdbootstrap

@filipkappa
Great to hear that! May I transfer the ownership to you or @mdbootstrap?

Please transfer directly to @mdbootstrap ;)

@filipkappa Thanks! I've sent the transfer request in GitHub. I've also transfered npm package, so please check it out.

Thanks guys!


Bump containers/image to v5.4.1

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

5.4.1 doesn't have @vrothberg https://github.com/containers/image/pull/889 which fixes the k8s errors.Is() dependency.  v5.4.2 will have that in it.

Let's wait for 5.4.2.


add better homing tracing and update vector encoder

adds a tracer for homing and updates the vector encoder

Changes Unknown when pulling 088fe8311d75a483159210684a92757865a80fa1 on homing_tracking_and_vector_encoder into ** on master**.

LGTM


Initial commit of the Heroclix character sheet

Changes / Comments
This is a new character sheet for the Heroclix miniatures game which is being played online on your site as a replacement for tabletop during Covid. The issue we face is not being able to see dials etc while playing which this character sheet should help with so that it is closer to a tabletop experience. The rules are freely available here: https://wizkids.com/heroclix/gameplay/rules-format/. As far as I know I have followed all the character sheet standards, except that I have not added rolls as the only rolls are 1d6 or 2d6 and I do not expect players to play with the character sheets open at all times.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Good call, missed the html tag, I assume for the Star wars one you're referring to the wiki link, is that an autogenerated page of some kind or do I have to create that once it's accepted? If it's autogenerated what's the naming convention?

No, I meant it as an example on how to use markdown to link to the sheet's readme file. The wiki thing is just some extra I've created for the sheet manually, and some may consider it overkill for some sheets.
That does remind me that if a sheet have lots of instructions or want to show multiple image of the sheet, creating and maintaining a Roll20Wiki page would be easier to maintain, than a Readme file or having the sheet instructions squeezed into the sheet.json's "instructions section. You can update the wiki at any time, and fit much more stuff, and others can easily contribute there, where as anything on GitHub can only be updated once a week. It's quite a bit more than most sheets need, but it's a nice thing. There is no drawback to have a small wiki-page with some instructions, tips on using the sheet, link to a relevant forum thread or external page, or just playing the game. And others can also add their tips if wanted.

I noticed that the a couple of Defense powers were mismatched for the powers they represent in the game. Impervious should be Pink and Invulnerability should be Gray. Also, Impervious has an abbreviation mismatch (Im or Ip?).
Thank you for putting this together and I am excited to play HeroClix on Roll20 with this.

Thanks @mam882002, I've fixed the defense powers in the latest PR, hope you enjoy and feel free to hit me up if you have any questions

Wonderful! Thanks bunches


Allow customization of mqtt client name

I now have two containers running with hms-mqtt-publisher inside and everything seems to be working ok.
I just get a lot (3-4 per second) of the following messages in my mosquitto log:
1709505662: Client hms800wt2-mqtt-publisher-ha already connected, closing old connection.
I think this is because both instances are using the same client name when connecting to mqtt. I see two possibilities:

Add the inverter id to the client name
Let the user configure the client name (or at least part of it)

Is it possible to do this?

I manually changed this in the code for the second container and can confirm that the name is the reason for the connection to mqtt dropping all the time.


fatal err or C1083: Cannot open include file. Installation issues

So after trying for hours and hours, I could still not fix it or know where the problem is occurring. Had to resolve other problems as well but this one persists. Can anyone please help me. I need to set this project up soon.

Hm, either the empty space in your path is causing issues, or the include file is missing. The file should be located in the cloned source directory of the autobuild folder somewhere in node_moduels/dlib-build/build in case you let the package auto build for you. If you are using an own build, the include path is probably wrong.

I did the package auto build for me.

I am pretty sure that the empty space in your path is causing this.

Ok thanks I will try fixing it with this.

I have a problem same with you.
Can you teach me , step by step for solve this error ?
please.


Problem with name of file

Hello, after scanning the source ( DTWAIN_AcquireFile ) it adds DTWAIN_SysDestroy to the file name and at the end I get the file name FILE.tifDTWAIN_SysDestroy

More than likely it is a bug in your program (maybe you are using a non-null-terminated string when a null-terminated string is expected?).  Please post the program.

DTWAIN_AcquireFile requires a null-terminated string as the file name.  Given the issue you are having, I am getting the suspicion that the name you are giving DTWAIN_AcquireFile is not null-terminated.  Whatever stray characters that appear after the "good" string is being picked up, all due to the null that's missing.
If you were to produce a full TWAIN log and inspected the DTWAIN_AcquireFile call in the call stack, it will show that the string you are passing is faulty, thus not an error in DTWAIN.

Closing, as this issue is in all likelihood due to passing a string that is not null-terminated string to DTWAIN_AcquireFile.


Add more unit tests

Simplify table test util (only assert tbody rows)
Fix combobox/select label connection
Add tab tests

Assert tab content
Assert tab state

I know, a little bit strange for me too, but I think for small unit tests it's ok.
Currently, there are two common ways for js tests:

test file besides the file which is tested
all test files in a "tests" folder

For me, the first option makes more sense for direct components (unit tests) and the second for integration tests.


Build using GitHub actions

@mcallegari, this is a first version of a github actions workflow to build the Linux variants.
In the project's actions settings, I configured the project to be restrictive with two exceptions.

The apt cache does seem to install only the first time it runs, so I added a fallback APT installation step.
It would be possible to add and run also the Windows build later as a second job.
As it was a longish way to get to this configuration, you may consider to squash-merge this pull request.

Hi @hjtappe thanks for this
Just one suggestion that I found while studying around the topic. It seems there's a shortcut to install Qt:
https://github.com/marketplace/actions/install-qt
Maybe it's worth a try to simplify the manifest?

@mcallegari, I can do that. Is there still a need for ppa:ubuntu-toolchain-r/test ? I do not see that any package of that one is requested. It might resolve the problems with the apt cache.
Is there a way to disable Travis for this branch? Otherwise, I am using unnecessary Travis minutes. Or I branch another time locally on my side only.

Perhaps removing the travis.yml file will not trigger a build? (which in the end is the purpose of this PR ;))

Hey @hjtappe thanks a lot for this huge work you're doing!
If there's anything I can do to help/assist you, please ask.
I'm wondering why you had to adopt static Qt on windows. Is dynamic not working?

Hello @mcallegari, I probably was a bit too ambitious when starting the work on the Windows build to offer that one as a replacement for appveyor. Windows is a world full of incompatibilities for host and target architectures and programs in the PATH variable. But I have hope because it should technically be possible.
The QT statis is (currently) needed due to:
make[3]: *** No rule to make target 'D:/c/opt/Qt/5.15.2/msvc2019_64/lib/libQt5Gui.a', needed by 'libhotplugmonitor.a'.  Stop.
I briefly wondered about that and then followed the path to remove this one error (just to see other problems due to changed paths). It could be possible to go back to the non-static QT later once I or we understand more of it.
If you run out of Travis minutes again, send me a ping and I can disable Windows, enable Linux and we are good to go. I can continue to debug & setup the Windows build on another branch then. I will send you an update on the actions configuration then because we are now using more actions than in the screenshot at the beginning of this pull request.
If you have ideas on how to setup the msys2 win32/i686 environment (or should we shift to amd64?) for the Windows build or have pleasure to work on it, we can certainly arrange something on a branch until one of us finds a way to make it pass. :-)

I do use MSYS2 on Windows to build QLC+.
Yeah, sometimes it includes frustrating outcomes, but in general it proved to work over the years.
I see something not right in the path you shared: /c/opt/Qt/5.15.2/msvc2019_64 is unexpected.
It seems you're either using the official Qt version for Windows or a MSVC variant of it.
Right now on MSYS2 the Qt version is 5.15.7 and it's for mingw32/64. That's the one you should use.
Example:
https://ci.appveyor.com/project/mcallegari/qlcplus/builds/45260155#L673
Setup of the environment is in appveyor.yml

Yes, I still have appveyor.yml open to find the trick. It's the file I started with before running into problems. It seems that the image selected in appveyor.yml is already different. On Github, it started with not finding pacman, and then proceeded with problems finding the right version of msys2 (32bit versus 64bit) etc.:
https://github.com/mcallegari/qlcplus/pull/1369/commits/415389118dc4042818d54a8101a35b2c1203fd63

@mcallegari, it looks like I am in a dead end with the current approach (qmake refuses to run g++) and I consider to rewind to zero (appveyor.yml standards) to find my luck with what I learned along the way about msys and Windows builds and github actions.
I need to suspend my work on this for at least a few days if not weeks. If you have experience in getting the Windows build to work, you could try to find the right parameters to setup the system consistently - or I can try on another branch. The actions documentation can be found on the github actions marketplace (https://github.com/marketplace?type=actions) and the msys2 documentation on the msys pages (https://packages.msys2.org/package/). Migrating the Windows build does not have a huge priority though, I think.
So I would propose, you could configure the actions permissions in your repository and then merge pull request to replace the travis build and we see how to proceed with the (deactivated) windows build:
awalsh128/cache-apt-pkgs-action@*, chocobo1/setup-ccache-action@*, egor-tensin/setup-mingw@*, jurplel/install-qt-action/action@*, jurplel/install-qt-action@*, msys2/setup-msys2@*,

OK, for now I would do this: migrate only the Linux builds to GH and abandon Travis.
Then I can invest some time also on Windows (and macOS) builds.
One question: does GH produce artifacts? Meaning: can I take the result of a build (.deb, .exe, .dmg) and upload it somewhere of my choice?
One advantage of Appveyor right now is that I can upload any build to the QLC+ website FTP very easily.
Losing this possibility would be a step backward for the project.
Another thing is coverage. If I remember correctly, once the "coverage" target is built by Travis, a trigger is invoked to pass the result to Coveralls. It would be interesting to keep this sort of mechanism also with GH and display a badge here:
https://github.com/mcallegari/qlcplus/wiki
It took me months to sort out all these mechanisms so I didn't expect this task to be easy at all (and that is why I haven't started this crusade myself yet 😉)

Yes, github can handle artefacts but as default is storing them in the build, see https://github.com/marketplace/actions/upload-a-build-artifact and https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts
There are actions to upload to FTP though: https://github.com/marketplace?type=actions&query=Upload+FTP which can be used as a final step.
For Windows, an artefact would be built, for QML, the Appimage could be composed through  https://github.com/marketplace/actions/build-appimage.
Not sure that this is possible for version 4/qt, but could be.
The coverage build is passing, the coverage will be uploaded through the related coveralls action.
Not sure why the appveyor build currently fails here. I  do not see how that would be affected. Should I briefly merge master to make it pass on the USB compile error?

Hi @hjtappe Windows builds started to fail because it was not possible anymore to revert to an older GCC.
This is a problem indeed and will eventually lead to adopt Qt 6.x quite soon.
In the meantime I applied a barbaric patch to build with GCC 12.x. So yes, merging master should be it.
As soon as I have some time, I will go back to the Qt 6 port and finalize it (I think everything works except for audio on some platforms)

@mcallegari Looking forward for the Windows Build to work... That way it will always be possible to download Edge Build without having to compile it myself right?

@mcallegari Looking forward for the Windows Build to work... That way it will always be possible to download Edge Build without having to compile it myself right?

Test builds can be found here: https://www.qlcplus.org/downloads/test/index.php?p=

@mcallegari Looking forward for the Windows Build to work... That way it will always be possible to download Edge Build without having to compile it myself right?

Test builds can already be found here: https://www.qlcplus.org/downloads/test/index.php?p=

Is that Edge Build for QLC+ 5?

Hi @hjtappe is this PR ready for merge?
Can we switch to GitHub actions?

Hi @hjtappe is this PR ready for merge? Can we switch to GitHub actions?

Well:

The Linux build is running
The Windows build needs work, it does not run currently
You asked to create an artifact, so I added that.
The qt5 (QLC+ v4) AppImage artefact is starting and running.
The qt5qml (QLC+v5) AppImage artefact fails (on Github, not on my local installation) with:
./qlcplus-qml: symbol lookup error: ../lib/x86_64-linux-gnu/libqlcplusengine.so.1: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1EPKcmRKS3_, version Qt_5

It seems to be a GCC ABI problem, induced by how the QT libs are built
I consider to separate the build steps completely and to install QT v6 for the qt5qml build.
Alternatively, I could revert installing the QT binaries from a different source (not using the action script currently used.
So, we might switch to the Linux Google Action build and address the Windows and AppImage ABI problem i a separate pull request branch. Let me cleanup the working copy before you actually merge, though.
What is your desired maturity before merge (a. build running and reporting Linux compile & test problems, b. Build providing a runnable Linux artifact, c. Build providing artifacts for Linux and Windows, d. something else)?

Hi @hjtappe don't worry about errors. I can help to fix them!
The important thing is that the structure is in place.
I'd say let's merge this and then fix it together.

OK, so here we go. The current status:

qt5 (v4) builds an AppImage, but I had to add the -fno-sized-deallocation option to g++, otherwise, it would not run un Ubuntu 22.04 (the build is using 20.04 and seems to have some ABI change)
qt5qml (v5) builds an AppImage, but it fails to run due to other ABI incompatibilities, potentially due to how the downloaded QT was built. I added a build-step to test-load the application, but with --help, it does not run into the undefined symbol.
Windows build is deactivated, I failed to bring the pieces together in a compatible configuration.

Note the Actions configuration at the beginning of this thread. The following actions are currently configured:
awalsh128/cache-apt-pkgs-action@*, chocobo1/setup-ccache-action@*, egor-tensin/setup-mingw@*, jurplel/install-qt-action/action@*, jurplel/install-qt-action@*, msys2/setup-msys2@*,
Feel free to merge it if you feel comfortable with this status. You might consider to resurrect the travis files until the build artefacts are usable.

@mcallegari Can you pls. Compile QLC+ v5 with newest changes... Would really like to try it, but Beta 2 had some defects / missing pieces so my setup dosen't work :-(

@hjtappe  Questions:

according to this it should be jurplel/install-qt-action@v3
is egor-tensin/setup-mingw needed if there is msys2/setup-msys2?
is http_parser changes needed for GA to work? (or can we separate that in another PR)

@mcallegari Can you pls. Compile QLC+ v5 with newest changes... Would really like to try it, but Beta 2 had some defects / missing pieces so my setup dosen't work :-(

Please do not hijack GitHub threads to ask personal questions. Use the forums instead.
And btw, I'll build v5 when I think it's worth to build it

Hello @mcallegari,

@hjtappe Questions:
* according to this it should be jurplel/install-qt-action@v3

https://github.com/mcallegari/qlcplus/blob/8464aff27e659968cbb061d26bf67881f44496d8/.github/workflows/build.yml#L105
In line 105, this is what I think I see. Which line do you refer to - or what is missing, please? In the security settings, this can be wildcarded.
For the Windows build, I also tried that, but with no success to come to a working setup. The Windows build should be fixed in another branch, I think.

* is `egor-tensin/setup-mingw` needed if there is `msys2/setup-msys2`?

I had been using that to try to get to a working setup, but without success. It can be omitted.
You can strip the module list in the security settings down to what is actually used and activated in the yml file.

* is http_parser changes needed for GA to work? (or can we separate that in another PR)

It came up while reading the logs. I have separated it (Werror on C files) in a separate merge request now. When I saw the warning, I had to find out if there is more warnings due to the compiler version used in the build setup; that's how it sneaked in.

@hjtappe merged and successfully built!
Thank you very much for your gigantic effort on this PR!
In the next days I'll try to set up also the Windows builds.
Would be awesome to build also the macOS version....but that's probably a real nightmare :rofl:


0.5.0-part-2 make helper methods

Issue

I’m finding myself quite frequently needing to modify them but not wanting them to be mutable - I really want a remake($override, $flags) method accessible on the object.

Scenarios:

New model with few changes
New model with few changes AND without some props

Solution

Add remake(array $override, $flags = default to object remaking from)
Add remakeOnly(array $onlyPropNames, array $override, $flags = default to object remaking from)
Add remakeExcept(array $exceptPropNames, array $override, $flags, = default to object remaking from)

# This
$remake = $made->remake(['with' => 'this'], ['not', 'these'], NONE);

# Instead of this
$remake = Dto::make(array_merge(
  $made->getDefinedProperties()
  ['whith' => 'this'],
), NONE);

# Or worse, this
$remake = Dto::make(array_merge(
  Arr:except($made->getDefinedProperties(), ['not', 'these']),
  ['whith' => 'this'],
), NONE);

I think we discussed $flags potentially inheriting from the object we're remaking. If that's what we're after then i think $flags should default to null rather than NONE (any value including NONE would act to override the object flags but obviously not the base flags) - if we aren't pursuing this behaviour then what's here is fine. My main use case for it was starting with a PARTIAL object and not wanting to have to re-provide the PARTIAL flag when remaking.
It would be nice if $override was an optional param (defaults to empty array).


[Variant page]: parse pQTL studies

Issue: https://github.com/opentargets/genetics/issues/532
Deploy preview: https://deploy-preview-204--genetics-app.netlify.app/

Thanks! This is what I expected. We will need to resolve some of these inconsistencies in the data/BE. Thanks @carcruz for opening the corresponding ticket


Build on Linux without system ACE will fail

Currently the UPDATE.sh script relies on the presence of ACE as system library. While this is ok for current Ubuntu, it is not the case for Scientific Linux or similar.
Since 27th June SuperBuild has the option to build its own ACE.
I see 2 options to fix this

UPDATE.sh accepts another argument which will set USE_SYSTEM_ACE=ON/OFF
Have the SuperBuild check whether ACE is found and if not to set USE_SYSTEM_ACE=OFF

I prefer the second option. Let's close it once https://github.com/CCPPETMR/SIRF-SuperBuild/issues/156 is closed.


Refactoring.

Renamed metrology:QuantityValue to metrology:Magnitude
Refactored 80000-concepts:UnitaryQuantityMagnitude as metrology:IsMagnitudeOfQuantity
Deleted redundant 80000-concepts:MeasurementUnit

Suggest renaming -magnitude1 and -magnitude2 to -magnitudes and -reflexive-magnitudes


error in npm

HI, @ghosta2211
npm does not have any error the error is on the project please give us a photo of the white words at the top of the console


clockhouse-batch-inserts

#25  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AmineAfia and the rest of your teammates on  Graphite


.eh_frame: Support sections other than .eh_frame

Such as .debug_frame, .zdebug_frame and others that might have the unwind information. This is important as some binaries, such as Golang's, don't seem to have .eh_frame. Not sure yet what the difference might be but perhaps the non-cgo binaries don't produce these tables?
[javierhonduco@fedora parca-agent]$ readelf -a ../parca/bin/parca  | grep eh_frame
[javierhonduco@fedora parca-agent]$

cc @kakkoyun @v-thakkar

Yes, the vanilla Go binaries don't generate .eh_frame sections. and we have a plan to support the .debug_frame sections as a follow-up to the initial implementation. https://github.com/parca-dev/parca-agent/issues/617
.zdebug_frame is just the gzip compressed version of the section. Which is a legacy implementation that has recently dropped. https://github.com/golang/go/issues/50796
Go binaries include .debug_frame when DWARF information is requested.
The difference between the formats is nicely explained in this blog post https://www.airs.com/blog/archives/460
Closing this on for the sake of existing issue  https://github.com/parca-dev/parca-agent/issues/617

Could you clarify all the above (different sections that we want to support, etc) in that issue? Thanks!


Fix broken javadoc link in release notes

@bot-gradle test and merge

OK, I've already triggered a build for you.

Error while merging successfully tested PR. Please contact the administrator.


Automated build triggered before tagging

The snap is automatically built using snapcraft.io's build feature. This happens on releases.
The release workflow adds an annotated tag to the repo and performs a Github release. This should theoretically trigger the build on snapcraft.io after tagging is done.
However, it looks like the trigger happens on code that isn't yet tagged. A subsequent manual build will read the tag just fine.
Work-around: Trigger manually after release via the Github CI workflow.

It seems like the build is triggered after commits and not after Github releases. This is also explained here: https://snapcraft.io/docs/build-from-github
That's why sometimes the tag is right, sometimes for one architecture only. If we tag and release immediately after commit on master, there is a chance that a slow build job picks up the tag.

For now:

Merge PRs:

That will automatically trigger the build and release to latest/edge. The version will be the latest annotated tag with a hash. E.g. 1.4.3+snap.8+git1.0cba711

To release:

Use the release Github workflow to tag
Trigger build manually at https://snapcraft.io/edgex-ekuiper/builds. The version will not have the hash, e.g.: 1.4.3+snap.9
Promote the new revision to latest/beta and 1/beta.

Moved the build to Launchpad: https://launchpad.net/~canonical-edgex/+snap/edgex-ekuiper
It can be triggered manually after release.
Nightly builds will have to be added at https://github.com/canonical/edgex-sync

Closed via https://github.com/canonical/edgex-nightly-build/pull/29


fixes for datadog agent

fixes the entrypoints dependencies on s6-overlay v2.x
depends on https://github.com/wolfi-dev/os/pull/18194/files

depends on https://github.com/wolfi-dev/os/pull/18194 landing


Sugar (Brix and SG)

Add support for conversion between Brix and SG

Coverage remained the same at 100.0% when pulling cc3923883f59412d875d90b42505e2e705048bae on mvolk/sugar into 35b0e77cb7f998c781bf6f5c8f1db81fcb6f8450 on master.


If vault_bastion_public_ip is false, the bastion's security group lacks internet access."

When vault_bastion_public_ip is true, the machine has internet through the internet gateway and its public IP. When vault_bastion_public_ip is false, this bastion uses the nat_gateway.

Found the issue:
Incorrect:
# Allow internet access.
resource "aws_security_group_rule" "bastion-internet" {
  count             = var.vault_create_bastionhost && var.vault_bastion_public_ip ? 1 : 0
...

Correct:
# Allow internet access.
resource "aws_security_group_rule" "bastion-internet" {
  count             = var.vault_create_bastionhost ? 1 : 0
...

Basically, this security group rule does not depend on vault_bastion_public_ip.


Fix integrate method for SO2

When the same vector reference is given to the integrate method as both
for input and for storing the output, the result is incorrectly
calculated due to inplace changes. This problem is fixed in this commit.
Close #1651

It is a bit weird to use the same input/ouput arguments at first glance.

I thought so too, when first examining the code. But integrating in-place is used a lot as operator+=, such as this code.

It is a bit weird to use the same input/ouput arguments at first glance.

I thought so too, when first examining the code. But integrating in-place is used a lot as operator+=, such as this code. What surprised me even more after realising this bug was why this issue has not shown up earlier.

I would say that because this part of the code is not more used with operator+= and some compilers may optimise some part of this code.

@Toefinder I've just force-pushed to align the histories.

Thanks @Toefinder, for your contributions. Greatly appreciated.


e2e test is flaky in CI

Description:

What issue is being seen? Describe what should be happening instead of
the bug, for example: Envoy should not crash, the expected value isn't
returned, etc.

https://github.com/envoyproxy/gateway/actions/runs/6431169623/job/17463786201
Repro steps:

Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Environment:

Include the environment like gateway version, envoy version and so on.

Logs:

Include the access logs and the Envoy logs.

    --- FAIL: TestE2E/RateLimit (2.13s)
        --- FAIL: TestE2E/RateLimit/block_all_ips (2.06s)

this is also happening on my PR, https://github.com/envoyproxy/gateway/actions/runs/6416541986/job/17420861887#step:6:2904.
    --- FAIL: TestE2E/RateLimitBasedJwtClaims (1.46s)
        --- FAIL: TestE2E/RateLimitBasedJwtClaims/ratelimit_based_on_jwt_claims (1.33s)

The logs for this run have expired and are no longer available. So closing this, we can open another issue if running into it.


How do i run multiple instances?

How do I run multiple instances?
I know with the smaller radius that I would need multiple instances

Let's see if I can help, I use Google to login, no PTC.  I just started using this app today and was able to run four for a while.
First off you need to have multiple Gmail accounts so get started on that.  Someone said in another post here that you only need 1 API code and I assume you have that.
So start up your first instance and get it going.  Then start the app again and when it comes up you need to click Logon with Google and then click on the drop arrow in the upper right where it shows your current email address.  Click on Sign out.  Click on Add Account and then login with another account.  Click on the Allow button and it should start a new window.  You then move the marker someone else of course.  Now in both windows you should see both of the scans running.

Don't use google accounts for scanning. Google accounts stop working after 30 mins.

No wonders the stop after a while!!  Thanks for the heads up, I will look into PTC accounts.


Problem reading Bitbucket private repository

I'm trying to deploy using a private Bitbucket repository. I've set Git access via SSH as instructed at Bitbucket https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Git
When I try to deploy it gives me:
[RuntimeException]
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Which means it connects succesfully to the server but it cannot access the remote repo. It's weird because I try to clone my repo manually and it works fine.

I've got the same issue with a private bit bucket repo. Are SSH keys not being forwarded ?  This works fine with Capistrano.

I have same problem and my solution is forward agent feature. Please try it.
server('dev-server', '<IP_ADDRESS>', 22)
    ->user('dev')
    ->forwardAgent()
    ->stage(['dev'])
    ->env('deploy_path', '/var/www/apps/dev')
    ->env('branch', 'develop')
;

And config your system support forward agent feature.

I am having the same issue with bitbucket keys. I can run the git clone command that is run by deploy:update_code exactly when done manually. Anyone find any solutions?

Dear @willmcl,
Please show you native command on shell and error on using deployer.


fix(Linux): Fix non-standard permission bug (fix #7992)

Fix non-standard permission bug

Closes #7992 , as the permissions are set correctly now.
Closes #7074 as well

Rest of the warnings mentioned in #7074 must be solved at user end itself, for example, by adding Copyright file, ChangeLogs, Maintainer, Categories etc. , and are not concerned as issues with Tauri itself.
So, yeah, both of the issues should be closed now!

I'm confused: aren't you setting 644 mode to all files, including main binary and sidecars?

I didn't merge this one yet because I still need to test it

Hi, yeah, I forgot that binaries must be executable :sweat_smile: . Sorry for that. Actually, earlier, I placed set_mode() belowe set_gid() , but it was having permission issues.
Anyways, I have written a function
            if (stat.mode() / 64)%2 == 1{
                header.set_mode(0o755);
            }else{
                header.set_mode(0o644);
            }

(x/64)%2 == 1 checks if there is executable permission set already, in that case, it will set mode to 755
Otherwise, for normal files, it will be set to 644
How does that sound? It is running on my machine as of now. Will test more latter.

Hi @olivierlemasle , it looks fine to me now. Can you please test and report?
Thank You.

So, @olivierlemasle and @lucasfernog , please review and test the changes.
I used set_metadata_in_mode() with HeaderMode::Deterministic, so that ownership is reset. Now, it also resets mtime to 2006, so I preserved the mtime as previous value.
Also, I added support for section and priority  settings.

@naman-crabnebula please keep this PR to fix permissions bugs, section and priority can be in another PR

@naman-crabnebula please keep this PR to fix permissions bugs, section and priority can be in another PR

Well, they are actually part of lintian errors as well. But I guess, I will just split pull requests and clean up things, and create 2 pull requests, one for https://github.com/tauri-apps/tauri/issues/7992 and another for rest of issues of https://github.com/tauri-apps/tauri/issues/7074


Add support for Safari clipboard API

Safari annoyingly doesn't support navigator.permissions and has a slightly different clipboard API.  This PR allows the copy and paste functionality to work with Safari in addition to the existing browser support.

Thanks for the PR!


Max Listeners exceeded in Vhost

I think when an internal reconnect happens, the Vhost object is re-created but the old event listeners are not cleaned up, causing an eventual "memory leak".
(node:1212) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 paused listeners added to [Vhost]. Use emitter.setMaxListeners() to increase limit (Use node --trace-warnings ... to show where the warning was created)
If the previous Vhost is destroyed or on re-create, Vhost could save the listeners as variables and we could unsubscribe to the events when a reconnect happens.
I'm not entirely sure the reconnect is where/why this is happening, it just feels likely

Hi @aycdinc,
Thanks for reporting. The only place I can find that Rascal registers an event listener on the vhost, is just before obtaining a channel before publishing a message. After it has obtained the channel, then the listener is removed. I added this recently to forward "paused" events from the vhost to the publication. I think it's possible that if you are publishing messages quite rapidly, the vhost may have more than 11 paused event listeners, however this is not actually a problem. I will see if I can reproduce and if so set the max listeners to zero to disable the warning.

That was it. I've disabled the warning and published as<EMAIL_ADDRESS>

Awesome! Thanks, will update. Yeah it wasn't causing problems, just wanted to make sure


Consistency adjustments for "Adding a Shortcut Menu in a Tool Window"

When I was following one of the tutorials, I encountered some inconsistencies. I updated the documentation to smooth them out.

 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.:x: BioChristou sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/extensibility/adding-a-shortcut-menu-in-a-tool-window.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use crew_controller_local() if accessed with Open On Demand

Open On Demand doesn't allow starting SLURM jobs, but you can treat it just like a multi-core computer and use crew::crew_controller_local(workers = 10) to run on multiple cores (just make sure you've requested enough cores on the OOD session).  Would be convenient if _targets.R programmatically detected whether you were on OOD or an interactive HPC session and set the correct controller.  Not sure if possible.

Can detect HPC vs. not HPC with HOSTNAME env var, by looking for hpc.arizona.edu.  Not sure how to detect OOD sessions though.
E.g.:
Sys.getenv("HOSTNAME")
#> [1] "junonia.hpc.arizona.edu"


added selenium cheatsheet

plz check and merge

Hello @HridoyHazard
Thanks for your contribution.
Let's connect ->
GitHub -> @Suryansh1720001 (Follow)
LinkedIn -> https://www.linkedin.com/in/suryanshprajapati17
And Star the Repo ⭐


python38Packages.py_scrypt: 0.8.18 -> 0.8.19

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.py_scrypt is: "Bindings for scrypt key derivation function library"
meta.homepage for python38Packages.py_scrypt is: "https://pypi.python.org/pypi/scrypt"
meta.changelog for python38Packages.py_scrypt is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.8.19 with grep in /nix/store/65kc86hc80ikjz27ynyqwkgnnzmxmp6h-python3.8-scrypt-0.8.19

found 0.8.19 in filename of file in /nix/store/65kc86hc80ikjz27ynyqwkgnnzmxmp6h-python3.8-scrypt-0.8.19

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
electrum-ltc
python38Packages.py_scrypt
python39Packages.py_scrypt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/65kc86hc80ikjz27ynyqwkgnnzmxmp6h-python3.8-scrypt-0.8.19 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.py_scrypt https://github.com/r-ryantm/nixpkgs/archive/c4a561c6ac9d0aa3b1e8c20b9f7897b446f675e7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/65kc86hc80ikjz27ynyqwkgnnzmxmp6h-python3.8-scrypt-0.8.19
ls -la /nix/store/65kc86hc80ikjz27ynyqwkgnnzmxmp6h-python3.8-scrypt-0.8.19/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

electrum-ltc
python38Packages.py_scrypt
python39Packages.py_scrypt

Maintainer pings

Updated in #149301


bug: Paniced when creating mv.

Describe the bug
See https://risingwave-labs.slack.com/archives/C048771BGKF/p1707467013682769
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

I guess it is because https://github.com/risingwavelabs/risingwave/issues/15074.


How to add image and text in the same message?

I would like to add an image and a caption line below it.

You can achieve that by creating your own custom viewholder.
an example can be found here : CustomOutcomingTextMessageViewHolder

As far as I understood, the design is still for one type per message.

@alouanemed is right. You can display any data in your custom layout by creating your own custom viewholder.


Fix fuzzing

Add in a fuzzer for:

tx
txin
txout

Fixes #22

Codecov Report
Patch and project coverage have no change.

Comparison is base (9e56767) 87.86% compared to head (6b90b43) 87.86%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   87.86%   87.86%
=======================================
  Files          26       26
  Lines        1253     1253
=======================================
  Hits         1101     1101
  Misses        152      152

Flag
Coverage Δ

unittests
87.86% <ø> (ø)

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

Impacted Files
Coverage Δ

src/import/cashaddr.c
82.43% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add benchmark for speed and accuracy against python package cvxopt

pymcef solves a set of LP problems with the parameter risk tolerance ranging from plus infinity to 0.
The optimization results contains all the optimal solutions coupled with the intervals of risk tolerance when this solution is optimal.
Such results can be compared with cvxopt if we provide all the risk tolerances.
Suppose pymcef return 1000 solutions, with 1000 risk tolerance intervals. We can call ovxopt to solve 1000 plain LP problems to compare the results for correctness and time cost for speed.

Done


Development: Use AssertJ for assertions in server tests

Checklist
General

[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines
[x] I documented the Java code using JavaDoc style.

Motivation and Context

Many tests use the default JUnit assertions instead of AssertJ, a powerfull library that offers many different assertion. It is considered to be best practice to use AssertJ, since it provides descriptive error messages.
Description

In this PR assertTrue, assertFalse, assertEquals, assertNull and assertNotNull are replaced with their AssertJ equivalents. The PR does not cover assertThrows,  this will be done in a follow-up. I also fixed a few instances where the expected and actual value were switched.
Review Progress

Look through the code and make sure the most specific assertions have been used. Also check if there are some assertions that might have been missed.
Code Review

[ ] Code Review 1
[ ] Code Review 2

Test Coverage
unchanged

Codecov Report

Merging #6588 (0994060) into develop (cf74c01) will decrease coverage by 4.44%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6588      +/-   ##
=============================================
- Coverage      84.94%   80.51%   -4.44%
- Complexity     13321    13323       +2
=============================================
  Files           1093     2365    +1272
  Lines          42898    90714   +47816
  Branches        4439    13388    +8949
=============================================
+ Hits           36440    73034   +36594
- Misses          4007     9732    +5725
- Partials        2451     7948    +5497

see 1275 files with indirect coverage changes

Flag
Coverage Δ

client
76.53% <ø> (?)

server
84.94% <ø> (ø)

Continue to review full report in Codecov by Sentry.

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

Code LGTM, only found instances of assertThrows, assertDoesNotThrow and fail on the branch. Maybe you could also test this e.g. with an additional test in the ArchitectureTest class
@Test
    void testNoJunitJupiterAssertions() {
        ArchRule noJunitJupiterAssertions = noClasses().should().dependOnClassesThat().haveNameMatching("org.junit.jupiter.api.Assertions");
        noJunitJupiterAssertions.check(testClasses);
    }

That's a really good idea :)
I will add it in the next PR, where last JUnit assertions still remaining will be replaced.


Fixed references to std::c_str

This PR updates the references to std::c_str::CString, which was moved to std::ffi::CString in rust-lang/rust#20444.
Note that this change in Rust also removed std::c_vec without a replacement. Sadly, I don't know the code well enough to create a suitable workaround. This is why the build is still failing.

Just FYI @nukep and I are working on a patch which fixes this, plus the CVec stuff, and also cleans up the audio subsystem. See drbawb/rust-sdl2/pull/2
It needs a little cleanup but it's almost ready to merge.

@drbawb That's great! I'll close this PR then.


SuperNova CompressedSNARK benchmark

This is to track the benchmark introduced in #131 and was run at this commit: https://github.com/lurk-lab/arecibo/pull/131/commits/1e1658b8273e8683d1ab3165edc9bd68788b9933
Note that a verification error and/or failure occurred on the largest circuit size below.
➜  arecibo git:(batched_spartan) cargo criterion --bench compressed-snark-supernova
   Compiling nova-snark v0.31.0 (/Users/clwk/fil/arecibo)
    Finished bench [optimized] target(s) in 19.00s
Gnuplot not found, using plotters backend
Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-0/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 8.1s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-0/Prove
                        time:   [804.57 ms 812.42 ms 822.02 ms]
CompressedSNARKSuperNova-1circuit-StepCircuitSize-0/Verify
                        time:   [32.799 ms 33.233 ms 33.534 ms]

Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-6565/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 11.6s.
 You may wish to increase target time to 19.4s.
 You may wish to increase target time to 33.7s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-55717/Prove
                        time:   [3.3087 s 3.3360 s 3.3650 s]
Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-55717/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 5.7s or enable flat sampling.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-55717/Verify
                        time:   [102.73 ms 103.94 ms 104.77 ms]

Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-121253/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 62.4s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-121253/Prove
                        time:   [6.2778 s 6.3212 s 6.3741 s]
CompressedSNARKSuperNova-1circuit-StepCircuitSize-121253/Verify
                        time:   [185.32 ms 187.87 ms 190.58 ms]

Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-252325/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 121.6s.
 You may wish to increase target time to 244.5s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-514469/Prove
                        time:   [24.369 s 24.774 s 25.280 s]
Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-514469/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 6.5s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-514469/Verify
                        time:   [633.70 ms 652.49 ms 672.07 ms]

Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-1038757/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 464.0s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-1038757/Prove
                        time:   [46.263 s 46.423 s 46.674 s]

Benchmarking CompressedSNARKSuperNova-1circuit-StepCircuitSize-1038757/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 13.0s.
CompressedSNARKSuperNova-1circuit-StepCircuitSize-1038757/Verify
                        time:   [1.2770 s 1.2878 s 1.3057 s]

res failed NovaError(ProofVerifyError)
thread 'main' panicked at benches/compressed-snark-supernova.rs:251:9:
assertion failed: res.is_ok()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Criterion.rs benchmark target compressed-snark-supernova exited with exit status: 101

For comparison, here is the regular Nova CompressedSNARK benchmark. As expected, we see slightly better performance than in the SuperNova case on an equivalent single-circuit proof.
This comparison is primarily intended as a sanity check that the SuperNova CompressedSNARK does not add catastrophic overhead or otherwise tank proving/verification performance.
➜  arecibo git:(batched_spartan) cargo criterion --bench compressed-snark
   Compiling nova-snark v0.31.0 (/Users/clwk/fil/arecibo)
    Finished bench [optimized] target(s) in 9.25s
Gnuplot not found, using plotters backend
Benchmarking CompressedSNARK-StepCircuitSize-0/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 7.5s.
CompressedSNARK-StepCircuitSize-0/Prove
                        time:   [746.97 ms 753.80 ms 764.46 ms]
                        change: [-6.4100% -4.8859% -3.1560%] (p = 0.00 < 0.05)
                        Performance has improved.
CompressedSNARK-StepCircuitSize-0/Verify
                        time:   [27.983 ms 28.055 ms 28.142 ms]
                        change: [-4.0002% -3.1284% -2.2740%] (p = 0.00 < 0.05)
                        Performance has improved.

Benchmarking CompressedSNARK-StepCircuitSize-6565/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 11.3s.
CompressedSNARK-StepCircuitSize-6565/Prove
                        time:   [1.1193 s 1.1261 s 1.1334 s]
                        change: [-6.7602% -4.9133% -3.1794%] (p = 0.00 < 0.05)
                        Performance has improved.
CompressedSNARK-StepCircuitSize-6565/Verify
                        time:   [41.404 ms 41.881 ms 42.832 ms]
                        change: [-6.1499% -3.7336% -0.9702%] (p = 0.02 < 0.05)
                        Change within noise threshold.

Benchmarking CompressedSNARK-StepCircuitSize-22949/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 18.3s.
CompressedSNARK-StepCircuitSize-22949/Prove
                        time:   [1.8469 s 1.8765 s 1.9117 s]
                        change: [-6.2170% -2.7697% +0.6235%] (p = 0.16 > 0.05)
                        No change in performance detected.
CompressedSNARK-StepCircuitSize-22949/Verify
                        time:   [60.269 ms 60.630 ms 61.237 ms]
                        change: [-6.0960% -4.1554% -2.0358%] (p = 0.00 < 0.05)
                        Performance has improved.

Benchmarking CompressedSNARK-StepCircuitSize-55717/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 34.7s.
CompressedSNARK-StepCircuitSize-55717/Prove
                        time:   [3.3189 s 3.3660 s 3.4138 s]
                        change: [-6.4090% -3.3243% -0.1846%] (p = 0.07 > 0.05)
                        No change in performance detected.
Benchmarking CompressedSNARK-StepCircuitSize-55717/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 5.6s or enable flat sampling.
CompressedSNARK-StepCircuitSize-55717/Verify
                        time:   [100.16 ms 101.00 ms 102.30 ms]
                        change: [-8.0060% -6.3649% -4.7889%] (p = 0.00 < 0.05)
                        Performance has improved.

Benchmarking CompressedSNARK-StepCircuitSize-121253/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 68.9s.
CompressedSNARK-StepCircuitSize-121253/Prove
                        time:   [6.2498 s 6.2791 s 6.3138 s]
                        change: [-5.0538% -3.5036% -2.2909%] (p = 0.00 < 0.05)
                        Performance has improved.
CompressedSNARK-StepCircuitSize-121253/Verify
                        time:   [180.18 ms 182.69 ms 185.41 ms]
                        change: [-6.5866% -3.7248% -0.7407%] (p = 0.03 < 0.05)
                        Change within noise threshold.

Benchmarking CompressedSNARK-StepCircuitSize-252325/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 121.5s.
CompressedSNARK-StepCircuitSize-252325/Prove
                        time:   [12.140 s 12.317 s 12.539 s]
                        change: [-6.0110% -3.9390% -1.6900%] (p = 0.00 < 0.05)
                        Performance has improved.
CompressedSNARK-StepCircuitSize-252325/Verify
                        time:   [370.96 ms 374.40 ms 378.00 ms]

Benchmarking CompressedSNARK-StepCircuitSize-514469/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 244.4s.
CompressedSNARK-StepCircuitSize-514469/Prove
                        time:   [24.024 s 24.374 s 24.883 s]
Benchmarking CompressedSNARK-StepCircuitSize-514469/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 6.2s.
CompressedSNARK-StepCircuitSize-514469/Verify
                        time:   [617.19 ms 629.14 ms 643.18 ms]

Benchmarking CompressedSNARK-StepCircuitSize-1038757/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 466.6s.
CompressedSNARK-StepCircuitSize-1038757/Prove
                        time:   [46.797 s 47.949 s 49.284 s]
Benchmarking CompressedSNARK-StepCircuitSize-1038757/Verify: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 13.3s.
CompressedSNARK-StepCircuitSize-1038757/Verify
                        time:   [1.3096 s 1.3383 s 1.3696 s]

Benchmarking CompressedSNARK-Commitments-StepCircuitSize-0/Prove: Warming up for 3.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 66.9s.
CompressedSNARK-Commitments-StepCircuitSize-0/Prove
                        time:   [6.6110 s 6.6417 s 6.6750 s]
CompressedSNARK-Commitments-StepCircuitSize-0/Verify
                        time:   [158.35 ms 160.13 ms 161.80 ms]

Fixed in #168


Setting up config file | Test Rico's WMT16 EN-DE

If I wanted to test Rico's model on a non-gpu instance would this be the setup to use:
Paths are relative to config file location
relative-paths: yes
performance settings
beam-size: 12
devices: [0]
normalize: yes
gpu-threads: 0
scorer configuration
scorers:
F0:
path: model.npz
type: Nematus
scorer weights
weights:
F0: 1.0
vocabularies
source-vocab: vocab.en.json
target-vocab: vocab.de.json
bpe: ende.bpe
debpe: true
cpu-threads: 8
gpu-threads: 0
devices: [1, 0]
When running ./bin/amun -c config.yml <<< "This is a test ." , I end up with Segmentation fault (core dumped) .
Would it be possible to run all four models model-ens{1,2,3,4}?

This works for me (BTW, does this mean you were able to compile?):
allow-unk: false
batch-size: 1
beam-size: 12
bpe:
  - deen.bpe
bunch-size: 1
cpu-threads: 8
devices: [0]
gpu-threads: 0
n-best: false
no-debpe: false
normalize: false
relative-paths: true
return-alignment: false
scorers:
  F0:
    path: model.npz
    type: Nematus
show-weights: false
softmax-filter:
  []
source-vocab:
  - vocab.de.json
target-vocab: vocab.en.json
weights:
  F0: 1
wipo: false

And for four models:
allow-unk: false
batch-size: 1
beam-size: 12
bpe:
  - deen.bpe
bunch-size: 1
cpu-threads: 8
devices: [0]
gpu-threads: 0
n-best: false
no-debpe: false
normalize: false
relative-paths: true
return-alignment: false
scorers:
  F0:
    path: model-ens1.npz
    type: Nematus
  F1:
    path: model-ens2.npz
    type: Nematus
  F2:
    path: model-ens3.npz
    type: Nematus
  F3:
    path: model-ens4.npz
    type: Nematus
show-weights: false
softmax-filter:
  []
source-vocab:
  - vocab.de.json
target-vocab: vocab.en.json
weights:
  F0: 1
  F1: 1
  F2: 1
  F3: 1
wipo: false

Hi @mehmedes
Can you pull the lastest version? What gcc version do you have? I tried to reproduce but it works on my machine.  I downloaded en-de model (using scripts/download_models.py) and replaced with your config.

I went back to 3a548b3 for testing.
I'll try your latest commit asap and let you know if it works. I'm using gcc 5.4.
Thank you so much for your invaluable input!  Have a nice weekend!

I've now been able to build the latest commit of amunmt.
When trying to create the config file, however, I still get the error:
Segmentation fault (core dumped)
Do you have any clues?
Thanks!

Can you please post your entire config file using the markup described here https://help.github.com/articles/creating-and-highlighting-code-blocks/

Sure. Thanks for the link.  I was always wondering how to get the proper formatting in Github.
Amunmt creates an empty config file, stating Segmentation fault (core dumped). I've also tried to use the both configs above but still Segmentation fault (core dumped).  Again, at the moment I'm not able to create a "real" config file. All I get is the error message with an empty file.

So, just to make sure I understand. You tried one of the above commands I posted, exactly the way I wrote them, and you get a segfault when you do this?
Note: your current working directory needs to be the directory the model files are located in.

I first tried  the exact commands above on 3a548b3.
I got Segmentation fault (core dumped).
Then I tried to create a config file according to the instructions:
path/to/amunmt/bin/amun -m model.npz -s vocab.de.json -t vocab.en.json
--bpe deen.bpe --cpu-threads 8 --gpu-threads 0 --dump-config
--relative-paths > config.yml
path/to/amunmt/bin/amun -m model-ens*.npz -s vocab.de.json -t vocab.en.json
--bpe deen.bpe --cpu-threads 8 --gpu-threads 0 --dump-config
--relative-paths > config.ens.yml
Again, Segmentation fault (core dumped).

I first tried one of the above commands. Didn't work.
Lastly I tried creating a config file with the above instructions.
Again Segmentation fault (core dumped).
The only command that works is ./amun -help

Interestingly, if I type ./bin/amun -help I get the help message.
If I type --help or -h, I get Segmentation fault (core dumped).

What's your boost version? We use boost::options in amuNMT for handling this.

Boost 1.54

Would this core file be of any use?
core.zip

I personally don't use core files. Being able to replicate your segfault is better so your model files, config file and the exact command you executed is better

This is one of the commands I tried for creating a config file for the English-German WMT model. The model files are in the same folder I ran the command in.
./bin/amun -m model.npz -s vocab.en-json -t vocab.de.json --bpe ende.bpe --cpu-threads 8 --dump-config --relative-paths > config.yml

The output:
Segmentation fault (core dumped)

Running that command is ok with me. However, I'm running on Ubuntu 16, boost 1.62, gcc 5.4
I'm trying to install a VM with your specs but it's quite difficult.
It may be better for you to update your OS

I've just test on OSX Sierra + boost 1.54 (1.54 doesn't build on Ubuntu 16). It works fine
So the problem is likely to be in Ubuntu 14 with the custom gcc & cmake install.

Alright. I'll update the OS and keep you updated!

Everything runs on Ubuntu 16 smoothly. Thanks!


build: Fix loading libnss

I could not find where systemd tries to load libnss_files, so probably
it does not do it directly. But apparently the loader does not like
the hardcoded /usr/lib path in the ACI rootfs, so instead put the
libnss_files libraries in the same directory as found on host.

I tested it on my computer (fedora 24) and all the tests that failed here (https://jenkins-rkt-public.prod.coreos.systems/job/rkt-master-periodic/os_type=fedora-24,stage1_flavor=src_master/105/consoleFull) passed. Didn't check other tests.

Basically, I called make functional-check GO_TEST_FUNC_ARGS="-run 'TestCapsNonRoot|TestAppUserGroup|TestNoNewPrivileges|TestPodManifest|TestAppIsolatorSeccomp|TestSupplementaryGIDs'".

I tested it on debian and fedora24 with the flavor src-v231 and it worked too.

lgtm

Travis is broken ATM: https://blog.travis-ci.com/2016-08-09-outage-gce-images
Merging anyway since the other tests passed.


import firebase in component

Hi guys, any idea how to import firebase into a .js file and call it from any component, in the code below it was for a project that is not electron
main-firebase.js
import firebase from 'firebase'
const _config = {
  apiKey: '<me-app-key>',
  authDomain: '<me-app-key>',
  databaseURL: '<me-app-key>',
  storageBucket: '<me-app-key>',
  messagingSenderId: '<me-app-key>'
}
let FbApp = firebase.initializeApp(_config)
module.exports.FireBase = FbApp.database().ref()
module.exports.FireStorage = FbApp.storage()
module.exports.FireAuth = FbApp.auth()

LandingPageView.vue
<template>
<div class="login-body">
        <el-input name="email" type="email" placeholder="Email" v-model="email"></el-input>
         <el-input name="password" type="password" placeholder="Correo" v-model="password"></el-input>
         <el-button type="primary" @click="onSubmitLogin()" :loading="loadLogin">INICIAR SESIÓN</el-button>
 </div>
<template>
<script>
  import { FireBase, FireAuth }  from '../main-firebase'
export default {
    name: 'landing-page',
    data () {
      return {
          email: '',
          password: '',
      }
    },
    methods: {
      onSubmitLogin () {
        this.loadLogin = true
        FireAuth .signInWithEmailAndPassword(this.email, this.password).then(result => {
          if (result !== null) {
            let _person= FireBase.ref(`persons/${result.uid}`)
            _person.once('value').then(data => {
              let obj = data.val()
              console.log(obj)
            })
          }
        }, error => {
          console.log('error-singin', error)
        })
      }
    }
  }
</script>

Node version: v6.3.0
NPM version: v3.10.9
Operating System: Win 10

As long as your firebase file is imported into your main.js, you can simply attach the services to the Vue prototype.
main-firebase.js
import Vue from 'vue'
import firebase from 'firebase'

const _config = {
  apiKey: '<me-app-key>',
  authDomain: '<me-app-key>',
  databaseURL: '<me-app-key>',
  storageBucket: '<me-app-key>',
  messagingSenderId: '<me-app-key>'
}

let FbApp = firebase.initializeApp(_config)
Vue.prototype.$FireBase = FbApp.database().ref()
Vue.prototype.$FireStorage = FbApp.storage()
Vue.prototype.$FireAuth = FbApp.auth()

Now you can use this.$FireBase, this.$FireStorage, and this.$FireAuth in all Vue component files.

Thanks for the solution, now my problem is that it does not recognize firebase.storage() and I get error in console
Uncaught TypeError: FbApp.storage is not a function
    at eval (eval at <anonymous> (renderer.js:1146), <anonymous>:49:76)
    at Object.<anonymous> (renderer.js:1146)
    at __webpack_require__ (renderer.js:661)
    at fn (renderer.js:85)
    at Object.<anonymous> (renderer.js:1896)
    at __webpack_require__ (renderer.js:661)
    at renderer.js:710
    at renderer.js:713

Firebase Storage is not included in the server side Firebase npm module.
Please check the link below.
https://www.npmjs.com/package/firebase#get-the-code-nodejs---server-and-command-line

Thanks the suggestion.  @re-fort @SimulatedGREG

Is there any way to import SCSS into the main.js?
example
import ElementUI from 'element-ui'
import './theme/index.css'
// import './scss/app.scss'

@Antoniobk
Assuming you have installed both node-sass and sass-loader, you can then add the sass-loader rule to the webpack.renderer.config.js file or just use <style lang="scss"> in your App.vue file and include using a CSS @import.
Going to close this since the original issue has been resolve, but feel free to comment any other questions.

I am facing problem on my electron-vue and firebase project- type error firebase.storage not a function
anyone can help me please.


Project seems to be abandoned - are there alternatives

Hi,
I am considering using this exporter.
However, given there have been no comments on issues and pull requests for months, are there any alternatives?

@glean-notes @okp4 both have active forks

stumbled on https://github.com/promhippie/

If you are interested in alternatives, I'm working on Actions integration you can track at https://github.com/promhippie/github_exporter/issues/123


Error: The argument type 'List?' can't be assigned to the parameter type 'List'

I am trying to set initialValue. My code looks like
MultiSelectBottomSheetField<Interest>(
                              initialChildSize: 0.4,
                              listType: MultiSelectListType.CHIP,
                              searchable: true,
                              buttonText: Text(item.key),
                              title: Text('Select ${item.key}'),
                              buttonIcon:
                                  Icon(CupertinoIcons.arrow_down_circle),
                              items: item.value
                                  .map((e) => MultiSelectItem(e, e.name))
                                  .toList(),
                              initialValue:
                                  initialInterests[item.key] ?? List.empty(),
                              onConfirm: (values) =>
                                  handleSave(item.key, values),
                              chipDisplay: MultiSelectChipDisplay(
                                  // onTap: (value) =>
                                  //     handleDelete(item.key, value),
                                  ),
                            ),
                          )

I am getting the following error
../../.pub-cache/hosted/pub.dev/multi_select_flutter-4.1.3/lib/bottom_sheet/multi_select_bottom_sheet_field.dart:169:31: Error: The argument type 'List<V>?' can't be assigned to the parameter type 'List<V>' because 'List<V>?' is nullable and 'List<V>' isn't.
 - 'List' is from 'dart:core'.
                initialValue: initialValue,
                              ^
Target kernel_snapshot failed: Exception

FAILURE: Build failed with an exception.

* Where:
Script '/Users/subhadip/Developer/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 1201

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command '/Users/subhadip/Developer/flutter/bin/flutter'' finished with non-zero exit value 1

My package version is 4.1.3

I am getting the same error, don't know why

Same error here

same error

same, anyone have a work around?


Added flipY parameter to image texture RE issue #37

I do not know if this issue also affects WebGPU, but just flipping the image texture with the flipY constructor parameter fixed the issue for me when viewing with WebGL.

Closing pull request because this is not the best place for the image flip to be done.


InputStream Helper API methods crash if InputStream Adaptive is not installed

It's possible to install InputStream Helper and call API methods when InputStream Adaptive add-on is not installed or disabled, this causes a crash.
Before executing an API method, we should check if InputStream Adaptive add-on is installed/enabled and try to enable or install it automatically.
Debug log:
2019-08-30 23:20:35.811 T:3976   DEBUG: [script.module.inputstreamhelper][routing] Dispatching to 'widevine_remove', args: {}
2019-08-30 23:20:35.812 T:3976   DEBUG: [script.module.inputstreamhelper-0.3.5]: Platform information: uname_result(system='Windows', node='DESKTOP-LSHI51P', release='10', version='10.0.17134', machine='AMD64', processor='Intel64 Family 6 Model 60 Stepping 3, GenuineIntel')
2019-08-30 23:20:35.816 T:3976   ERROR: EXCEPTION: Unknown addon id 'inputstream.adaptive'.
2019-08-30 23:20:35.878 T:3976   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <class 'RuntimeError'>
                                            Error Contents: Unknown addon id 'inputstream.adaptive'.
                                            Traceback (most recent call last):
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.inputstreamhelper\addon.py", line 48, in <module>
                                                plugin.run(sys.argv)
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.routing\lib\routing.py", line 115, in run
                                                self._dispatch(path)
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.routing\lib\routing.py", line 126, in _dispatch
                                                view_func(**kwargs)
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.inputstreamhelper\addon.py", line 44, in widevine_remove
                                                Helper('mpd', drm='widevine').remove_widevine()
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.inputstreamhelper\lib\inputstreamhelper.py", line 699, in remove_widevine
                                                widevinecdm = self._widevine_path()
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.inputstreamhelper\lib\inputstreamhelper.py", line 181, in _widevine_path
                                                widevine_path = os.path.join(cls._ia_cdm_path(), widevine_cdm_filename)
                                              File "C:\Users\test\AppData\Roaming\Kodi\addons\script.module.inputstreamhelper\lib\inputstreamhelper.py", line 154, in _ia_cdm_path
                                                addon = xbmcaddon.Addon('inputstream.adaptive')
                                            RuntimeError: Unknown addon id 'inputstream.adaptive'.
                                            -->End of Python script error report<--

Not sure if we can fix this before v0.4.0 release. And this is equally true for inputstream.rtmp.

Fixing this is not urgent. Should be fixed before v1.0 though.

When executing API methods we should also check if Kodi 18 or higher is used, on Kodi 17 remove_widevine crashes and install_widevine gives a nice error message "Kodi 18 or higher is required.

Removing should not really be a problem on Kodi v17.
If it is just a file operation.

I'm currently looking into this and I came to the conclusion that installing Widevine CDM alone doesn't make any sense. To use Widevine CDM, a user always need Kodi 18 and InputStream Adaptive add-on.
So, we must always check these dependencies before installing Widevine CDM and this is already implemented in the main function check_inputstream. In fact install_widevine is already duplicating existing functionality.
We must reconsider what functionality the API must contain and how we present this functionality to the user.
Any ideas a