WIP: Generate opam lockfiles

This PR introduces a new command that generates a .opam.locked file from the local dune-get.
The generated opam files contains the dependencies and all the pin depends necessary to have a reproducible opam workflow.
For now the opam lockfile doesn't contain all the information the dune-get file does but I'm looking into this so that we can totally replace the dune-get file, using x- extra opam fields.
One annoying thing is that the pin-depends don't allow us to track the ref initially used to do the commit resolution i.e. the tag for regular packages or the eventually the branch for the pinned ones.
The pinned packages won't cause much trouble since we'll probably record them in an extra field somewhere, with the branch information stored so if we want to run the equivalent of duniverse update it's still possible.
For the regular ones we still have the version but we lose the tag we inferred. It's not much work to recompute it but it still feels like we lose a bit of information and I'm wondering if it can cause issues in some cases.
Also the opam file might contain the same information but it won't be structured in a duniverse friendly way. Again, it's not blocking but it will complexify this part of the code slightly.
Just to summarize if I got this correctly, the next steps are:

Add extra field so that the generated lockfile holds the same information as the dune-get
Add functions to parse such a lock file to the internal Duniverse.t representation
Make it so duniverse init generates that instead and do not use dune-get internally

Another point worth discussing is how should we deal with multi-packages repos. Right now there's a single lockfile with all the deps for the root packages. The idea is to use it as a strict replacement for the dune-get file so we're keeping the same convention. As we discussed on slack it might make sense to generate one lockfile per package, as long as we pin the internal deps to the local package so that it "inherits" their pin-depends but that does make the lockfiles less standalone so I'm not too sure about that. Right now all the deps are described in this lockfile, including transitive ones and I'm not sure how that should translate into multiple lock files. Anyway that's definitely not necessary for our first prototype!

@avsm feel free to give this a try as the fields relevant to opam won't change and this should already give you an opam installable setup.
If you want to give it a spin the workflow would be:

run duniverse init to generate a dune-get file if you don't already have one
run duniverse to-opam to generate the corresponding opam lockfile
run opam install ./duniverse-lock.opam.locked to install the locked dependencies using pins

It should work from there!

A quick note on what's left to do:

[ ] the depends and pin-depends aren't actually enough to recompute the exact internal Duniverse.t so we either need to store it in a separate field, either just what's required so we don't duplicate the information from depends and pin-depends or a complete representation of the source and opam deps to ease the parsing of the lockfile. The latter seems alright even though it induces quite some redundancy in the lockfile.
[ ] decide what to do about depexts. I kind of liked the idea that the lockfile would be standalone, i.e. it defines all dependencies, including transitive ones + the depexts but if those are going to be installed through opam anyway, there isn't much value in doing so I guess.
[ ] Make it so the opam lockfile becomes the default duniverse config file, replacing dune-get. I'll keep the to-opam command I added for testing, renaming it migrate-dune-get so that existing users can migrate their dune-get file without having to recompute the lock from scratch, might be helpful for RWO for instance.

We'll keep the depext field for now to maintain the same set of features!

@avsm I think this has everything we need now, you should give it a spin! I'll look into re-implementing pull using opam's lib in the meantime!

Looks good. It's possibly finding a few latent bugs in opam's lockfile handling: lots of the below when running on duniverse itself:
[0install-solver.2.17] synchronised from git+https://github.com/0install/0install.git#4a837bd638d93905b96d073c28c644894f8d4a0b
[WARNING] Lock-file /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/0install-solver/0install-solver.opam.locked doesn't exist, using
          /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/0install-solver/0install-solver.opam instead.
0install-solver is now pinned to git+https://github.com/0install/0install.git#4a837bd638d93905b96d073c28c644894f8d4a0b (version 2.17)
[alcotest.1.2.1] synchronised from git+https://github.com/mirage/alcotest.git#6ca7cc04ea07f5bd5b001fed4a0313d82e4b3cc0
[WARNING] Lock-file /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/alcotest/alcotest.opam.locked doesn't exist, using
          /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/alcotest/alcotest.opam instead.
alcotest is now pinned to git+https://github.com/mirage/alcotest.git#6ca7cc04ea07f5bd5b001fed4a0313d82e4b3cc0 (version 1.2.1)
Processing: [astring.0.8.4+dune: git]
[astring.0.8.4+dune] synchronised from git://github.com/dune-universe/astring.git#baa4e7e2bf919293aac2c899786c2ac40757dd9b
[WARNING] Lock-file /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/astring/astring.opam.locked doesn't exist, using
          /Users/avsm/src/git/ocamllabs/duniverse/_opam/.opam-switch/sources/astring/astring.opam instead.
astring is now pinned to git://github.com/dune-universe/astring.git#baa4e7e2bf919293aac2c899786c2ac40757dd9b (version 0.8.4+dune)

It looks like opam expects both a .opam and a .opam.locked.  Things improved when I did a mv duniverse-lock.opam.locked duniverse.opam.locked.  Perhaps we should just pick the root package (from dune-project (name)) rather than duniverse-lock. That would let opam switch create . --locked work out of the box.
More worryingly, the pin-depends handling is really slow in 2.0. I'll try that in 2.1alpha3 to see if its improved.

You might have a bit of a hard time trying it with opam 2.1 as the opam lib has introduced breaking changes between now and then unfortunately.
Also do you understand why changing the name of the lockfile would fix the above warnings? Is it because if it doesn't have .opam corresponding to the .opam.locked, it expects a .opam.locked for all the packages?
I'll change it to use the package name when there's only one and eventually prompt for user input when there's more. I think we should really think the multi-opam scenario through as it might be really confusing. Having such different .opam and .opam.locked for the main package because it includes the dependencies for all packages might come off as a suprise to users of regular .opam.locked files. Even worse, what if there are non co-installable packages in the repo? I think we can't go wrong if we let the user chose in those cases.

Hmm now that I think about this further not having a fixed name or our own extension makes it harder to reliably find the duniverse lock file in most commands.
Using the name from the dune-project slightly improves this on our side but it comes with the same issues I mentioned above.
Understanding exactly why opam goes nuts if there's no corresponding .opam file might actually help figuring out the best solution here. I'll take a look.

Just changed it so that it uses the only package name or if there are several, the project name from the dune-project!

Is there anything blocking here or is this good to go?
One thing I was thinking we could improve before we merge is to eventually generate the lock file from the main package opam file so that the other fields (maintainer, authors, etc...) are consistent rather than filled with dummy values. For single package repos it's definitely an improvement, for multi-opam ones I'm not so sure.What do you think?


Additional props

Adds support for inline zIndex and disabled props.

Whoops! We meant to open this against our fork (being aware this repo isn't currently maintained).
Apologies for the noise.


Change deprecated import with lib to dep for scala-cli

Before submitting pull request:

[ ] Check if the project compiles by running sbt compile
[ ] Verify docs compilation by running sbt compileDocs
[ ] Check if tests pass by running sbt test
[ ] Format code by running sbt scalafmt

Cosmetic change :)

Thanks :)


[Feature] Fixed path for snarkVM parameters

🚀 Feature
It would be amazing if we could move the location where the parameters are store to a fixed location. Right now when I start it, it points to
~/.cargo/registry/src/github.com-1ecc6299db9ec823/snarkvm-parameters-0.5.4/src/testnet1/
Could it be something like ~/.snarkvm/parameters?
Motivation
That would help the work done with persistent storage. Right now it seems to very with every release it changes so we cannot mount persistent storage in that path. We have to run it, figure out what the path will be, and build again with that directory as mount point.

@Protryon what's your opinion on this?
From my perspective, it seems to make sense to put parameters in ~/.snarkvm/parameters, however for developers working on snarkVM this results in saving 600MBs of parameter data to a folder they may be unaware of.

There is separately a question for the WASM context what the best convention for loading parameters is.

@howardwu
May be this is a bug?  when the relative path and the absolute path doesn't exist, the parameter can never be stored locally.
https://github.com/AleoHQ/snarkVM/issues/193
// load_bytes() -> store_bytes

            fn store_bytes(
                buffer: &[u8],
                relative_path: &std::path::Path,
                absolute_path: &std::path::Path,
                file_path: &std::path::Path,
            ) -> Result<(), crate::errors::ParameterError> {
                use snarkvm_utilities::Write;

                println!("{} - Storing parameters ({:?})", module_path!(), file_path);
                // Attempt to write the parameter buffer to a file.
                if let Ok(mut file) = std::fs::File::create(relative_path) {
                    file.write_all(&buffer)?;
                } else if let Ok(mut file) = std::fs::File::create(absolute_path) {
                    file.write_all(&buffer)?;
                } else {
                  .....
                }
                Ok(())
            }

where I can download inner_snark_pk-68eebd0.params?
node crash after ~30% of downloading

Parameters are currently stored in .aleo/resources/


Porting: bank module

Description
This PR intends to port the bank module implementation from heimdall to cosmos-sdk v0.50.2.
Please look out for comments prefixed with // TODO HV2 or // HV2, as they indicate open points that need action or changes that impact heimdall within this PR.

Considering the merge of bank and supply modules, is there anything we need to import from here?

Considering the merge of bank and supply modules, is there anything we need to import from here?
Nothing I felt was specific to heimdall as such; the code seemed to have been directly ported into heimdall v1.

I tried to run go mod tidy in the root folder on this branch and I get several changes which are not staged for commit
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   x/circuit/go.mod
        modified:   x/circuit/go.sum
        modified:   x/evidence/go.mod
        modified:   x/evidence/go.sum
        modified:   x/feegrant/go.mod
        modified:   x/feegrant/go.sum
        modified:   x/nft/go.mod
        modified:   x/nft/go.sum
        modified:   x/upgrade/go.mod
        modified:   x/upgrade/go.sum

Also, when running bash scripts/go-mod-tidy-all.sh, I get an unknown revision version on simapp
go: downloading cosmossdk.io/simapp v0.0.0-00010101000000-000000000000
go: cosmossdk.io/x/feegrant/simulation tested by
        cosmossdk.io/x/feegrant/simulation.test imports
        github.com/cosmos/cosmos-sdk/x/bank tested by
        github.com/cosmos/cosmos-sdk/x/bank.test imports
        cosmossdk.io/simapp<EMAIL_ADDRESS>invalid version: unknown revision<PHONE_NUMBER>00

Can we please make sure all the changes are committed (maybe you just need to pull auth branch once more) and that we get no errors while running such scripts?
Thanks

I'm also getting some compile errors when running tests...unfortunately still some remaining references to functions that were removed. Admittedly they are in irrelevant modules for heimdall but you still will need to address in order to get the entire project to compile.
Issues are in:
/x/circuit -> we call authtypes.NewModuleAddressOrBech32Address()
/x/evidence -> sdk.AccAddressFromBech32()
/x/upgrade -> authtypes.NewModuleAddressOrBech32Address()

I'm also getting some compile errors when running tests...unfortunately still some remaining references to functions that were removed. Admittedly they are in irrelevant modules for heimdall but you still will need to address in order to get the entire project to compile.
Issues are in: /x/circuit -> we call authtypes.NewModuleAddressOrBech32Address() /x/evidence -> sdk.AccAddressFromBech32() /x/upgrade -> authtypes.NewModuleAddressOrBech32Address()

@glnro I solved them in auth porting module branch, which is the target of this PR
I believe these errors will just get solved when @Raneet10 pulls the latest changes from mardizzone/POS-1956-auth branch

I'm also getting some compile errors when running tests...unfortunately still some remaining references to functions that were removed. Admittedly they are in irrelevant modules for heimdall but you still will need to address in order to get the entire project to compile.
Issues are in: /x/circuit -> we call authtypes.NewModuleAddressOrBech32Address() /x/evidence -> sdk.AccAddressFromBech32() /x/upgrade -> authtypes.NewModuleAddressOrBech32Address()

@glnro I solved them in auth porting module branch, which is the target of this PR I believe these errors will just get solved when @Raneet10 pulls the latest changes from mardizzone/POS-1956-auth branch

This should fix it.

Since this PR is raised against [mardizzone/POS-1956-auth](https://github.com/0xPolygon/cosmos-sdk/tree/mardizzone/POS-1956-auth) I'd suggest you @Raneet10 to merge back that branch into yours before merging this PR. It will solve the conflicts and would be able to run the x/bank tests again (adjusting them in case or errors). I did the same for the gov PR

As requested, I did one last pass on this PR (after being merged). No concerns from my part, just one minor comment. Regarding previously open convos, I don't see anything left to do: you can resolve all of them AFAWAC.


change default group

close #436
This pull request addresses #436.
I replaced the "all" group by default(hosts_default_group|default('generic')) with a regex replace.
I simply adjusted the defaults in the following way:
$ find . -type f -name "*.yml" -exec sed -i "~s,hosts: all,hosts: \"{{ default(hosts_default_group|default('generic')) }}\",g" {} \;
$ find . -type f -name "*.yml" -exec sed -i "~s,|default('all'),|default(hosts_default_group|default('generic')),g" {} \;

As I haven't been working on this for very long, it may well take a little more work, but perhaps we can dare to do so :-)

Sorry, i accidentally missed to push a rework.
Now it should be as intended.
@berendt ready for review

Damn, it seems that a chained "default" is not accepted by "ansible-lint" but valid.


Responsible AI Service is too strict

Type: Bug
Hello, how are you?
I asked Copilot to "@workspace tell me about this website" and it was filtered by the Responsible AI Service.... Refreshed and got a high quality response.
Next prompt was "I want to remove the inline styles and put them in a css file from line 21" and again Responsible AI filtered and this time refresh did noting
I believe these to be common questions and well within the frontEnd dev requests ... is there a strickness setting I am missing?
Extension version: 0.21.1
VS Code version: Code 1.94.1 (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
AMD Ryzen 7 4800H with Radeon Graphics          (16 x 2895)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
15.36GB (1.75GB free)

Process Argv
C:/code/frontendMasters/fem-01-04-css-foundations/ --crash-reporter-id 5f40061a-7c7c-4a06-931f-41080ca28ff3

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
g316j359:31013175
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca1:31150322
notype1:31151523
showchatpanel:31153267
5fd0e150:31155592

Thanks for creating this issue! We figured it's covering the same as another one we already have: https://github.com/microsoft/vscode-copilot-release/issues/2625. Please refer to that one for updates and discussions. Feel free to open a new issue if you think this is a different problem.


FSCalendar Improvements

Hey @f33chobits,
First of all thank you for FSCalendar it certainly is a nice tool for iOS. Here I suggest a couple of improvements for it:
· FSCalendar should let select multiple dates by the user (with more than one circle).
· FSCalendar should programmatically let add circles to the desired dates(for instance from a [NSDate]).
Thank you again for the effort you have put in it!

Thanks for you advice.
As for the first one, I'll add it later. It should take some time.
As for the second one , you can do it by setting the selectedDate of FSCalendar, but there seems to be a little problem calling it in viewDidLoad, I'll fix that later.
Thanks again.


[2.0] Internal Updates

[x] Embed structures in their php_ wrapper rather than a pointer to them. See #40
[x] Consider only allocating buffers when they're needed. See #61
[x] Make sure that all functions, constants and macros are namespaced.

This is now outdated.


Recommend path for pulling Application Insights data

Global Service Monitor has been used to ping against a couple dozen URLs for a couple of years now.
The resulting data is extracted and summarized by a custom application to show periods of unavailability (start, finish, timespan) of each URL.

I have prototyped a working sample that pulls data directly from the REST APIs (https://api.applicationinsights.io/v1/apps/) using HttpClient.
I also have another working prototype that references Microsoft.Azure.ApplicationInsights and Microsoft.Azure.Management.ApplicationInsights, but both are in preview and haven't been updated in a while. Are these two going to move forward? If so, any estimates on when they'll RTW?

Hi! I've been working towards a 1.0.0 (stable) release for the Microsoft.Azure.ApplicationInsights package. We plan to continue supporting the C# SDK as a way to retrieve, metrics, events, and logs. Prior to stable release, we may rename the package along the lines of Microsoft.Azure.ApplicationInsights.Query to reduce ambiguity with Microsoft.ApplicationInsights (for sending telemetry to App Insights).
I'm currently syncing up a fairly large PR with breaking changes After that, I'd like to have a chance to start to see some usage with the new version and work out kinks. I'd expect something stable here soon -- ideally Oct '18, conservatively  Dec '18.
I can't comment on a timeline for the management plane side of things. These will likely get some love in the near-but-not-immediate future.
If I can help in other ways with the App Insights REST API, please let me know 😊

@alfredmyers BTW -- New package is live. I'm still working on reference info + docs for this. If you prototyped, it looks fairly similar to the existing client. Key changes:

Metrics, Events, and Query are distinguished into their own interfaces, with method names slightly renamed to reflect this.

e.g. client.GetMetric -> client.Metrics.Get
for metrics extension methods there is still e.g. client.Metrics.GetMetricSummary. This isn't consistent with the other naming, is a possible candidate for further refinement as e.g. client.Metrics.GetSummary

AppId is now a parameter to methods rather than a property on the client. This makes querying more than one app easy with a single client.
Query results should now return values as their actual types, rather than forcing them all into strings.
Various parameter fixes. C# TimeSpans don't model all of our time values properly, so some are strings. Tightened and loosened validation as necessary on some other parameters (e.g., MetricId, MetricsAggregration)

If you are interested in trying this out, I'd love to get some direct feedback to shape any additional changes before 1.0.0 👍 Unfortunately until the docs are sync'd as well (in progress), I can only point to the source and tests for specific usage.

@alexeldeib Maybe SDK documentation should be updated as well, as it still points to the old NuGe package.


stanc produces invalid C++ when sqrt called on int.

Summary:
If a Stan program contains an expression of the form sqrt(e), where e is an int, the generated code leads to a C++ compiler error "call to 'sqrt' is ambiguous."
Description:
Modern C++ compilers have different signatures for sqrt other than just double sqrt(double), and so a call of sqrt(_e_), where _e_ is of type int, leads to ambiguities as to which signature is intended.
Reproducible Steps:
Run stan_model on this code:
data {
  int x;
}
parameters {
  real y;
}
model {
  y ~ normal(sqrt(x), 1);
}

The call fails with error: call to 'sqrt' is ambiguous. (Note that this error is buried deep in the output; I had to redirect output to a file to even find it.)
If I replace int x; with real x; then the stan_model() call succeeds.
Current Output:
Expected Output:
Additional Information:
Current Version:
I was running RStan 2.17.3, compiled from source.

Thanks for reporting.  The problem is some kind of ambiguity arising in the RStan envionment, but the fix needs to be made in the math lib, for which the issue is this:
https://github.com/stan-dev/math/issues/712
You can workaround with x + 0.0, too.


E2E: Improve documentation/usage

Closes #783
Closes #782
Basics

[x] I added a line to /doc/CHANGELOG.md
[x] The PR is rebased with current master.

[x] References to issues, e.g. close #X, are in the commit messages.
[ ] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed the introduction tour
[ ] I wrote migrations in a way that they are compatible with already present data
[ ] I fixed all affected decisions
[ ] I added unit tests for my code
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
(exceptions are documented)
[ ] Code is consistent to our Design Decisions

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Examples are well chosen and understandable

It seems to have a problem with executing a shell script as entrypoint for the e2e docker image.

Which line of code has this problem? It is quite clearly indicated that something like this shouldn't be done.

The real complication here is that I need to delete all maps from the database after a local test run and I dont have to do that in CI. So I get these two different use cases which I both need to handle somehow.

Why would you need to delete all maps? You can simply require that E2E are only executed on an empty database.

Also the entrypoint.sh is used from the top level makefile. So I really dont want to duplicate any lines of code here.

Yes, I agree.

Which line of code has this problem?

I cant clearly tell. I would guess it doesnt like the shell script invocation inside the dockerfile.

It is quite clearly indicated that something like this shouldn't be done.

Yes I agree, I was just not sure how "dangerous" this really is. I will try to find another way, just like the other scripts maybe.
I thought it would have been nice to have a docker entrypoint.

Why would you need to delete all maps? You can simply require that E2E are only executed on an empty database.

You need to do that everytime you rerun the e2e tests otherwise you will get wrong test results.

You need to do that everytime you rerun the e2e tests otherwise you will get wrong test results.

No problem for me. Let us better to keep everything simple.

Let me know if anything is unclear/complicated or I have forgotten something and if you can run e2e tests locally.


A syntax error occurs in SQL formatting

When sql code has "!= "operator, formatting code gets wrong syntax formatting"! = ". There is an extra space between the  "!" symbol and the "=" symbol
for example：
SELECT
  *
FROM
  tableName
WHERE
  dt = '2021-11-09'
  AND some != '111'

i‘ll get it
SELECT
  *
FROM
  tableName
WHERE
  dt = '2021-11-09'
  AND some ! = '111'

browser：Chrome@latest

This library doesn't do code formatting, so it doesn't seem like it could be responsible for this.

This library doesn't do code formatting, so it doesn't seem like it could be responsible for this.

Yes, I just found it. Thank you for your reply.


Avoid needing to tag a version as part of a pull request

I've run into problems around having the tag as part of the PR when you often rebase commits to make amends.  It seems like Travis CI should be able to do that step in the deploy hook after a successful merge into master.
http://stackoverflow.com/a/28230711/2250435
In addition, this doesn't play that nicely when you have multiple PRs open at the same time.

One challenge to address would be the fact that it might be hard to programmatically determine whether to make the change a major/minor/patch update.  Is there a reason that that is relevant?  Something like a colorscheme I wouldn't expect to follow proper semver, since it's not like it will be a dependency of anything where that metadata is relevant.
What's the reason for needing to tag every change?  Some of the package managers require that?  I only use vim-plug and AFAIK it just monitors a remote branch and updates with any changes.

Related comments:
https://github.com/trevordmiller/nova-vim/pull/41#issuecomment-253657242
https://github.com/trevordmiller/nova-vim/pull/43#issuecomment-253657400

@alexlafroscia I agree. I'll probably add semantic-release to tag after CI succeeds; this does unfortunately add a requirement to have specific commit messages (so you know what type of change it is - major, minor, or patch - for semver). What do you think? Probably better than running npm version (via push script) locally.

Hmm, that's interesting. I had seen it but never really dug into trying it out. Seems like a really interesting option though, and I generally love the idea of commit messages having a particular format.  I think it's important that commits include the details on the what and why of the changes, and driving the version change from that data is a cool idea.

Yeah I'm willing to try it out; I've made a few packages (which rely on semver + versioning) and haven't found a great solution to follow semver but still have easy contributing and PRs. I'll add this in when I have some time and we can try it out and see what we think :)

Yeah, it's always tough. I find it fascinating that the Elm language can actually do it automatically by looking at your code and determining if anything changed! Pretty amazing, but poor old JavaScript will probably never see anything like that 😝

I did some more research and it doesn't see that semantic-release is a good option for a few reasons:

it auto-publishes the package to npm after CI success (which this Vim plugin doesn't need, its only on GitHub)
it forces a pretty prescriptive setup that I feel is even more of a burden than manual tagging and resolving conflicts on multiple PRs
It has a lot of unresolved issues on GitHub, seems like it creates more problems than it solves

Unless there is another, slimmer alternative to semantic-release, I feel the best options are to either

continue to have contributors own manual tagging or
remove deploy from CI and have the repo admin (myself) version and deploy after each pull request is merged

What do you think @alexlafroscia? Do you know if there is a better option that package authors  (both on and off npm) normally use for semver version bumping, or do they do one of the two things I mentioned above?

Another option, since Vim doesn't care about semver, is to always auto tag with npm version minor or something, but that feels dirty. Also, I'm looking for a solution I can use with my other packages.

Asked on twitter:
https://twitter.com/trevordmiller/status/787048100380618752

@designfrontier suggested option #2 from above, which I'm willing to do to remove the burden from contributors. Just means I can't merge stuff from my phone anymore 😆


Multiple executions of scheduled function when laptop is waked up

Hello! It seems that I ran into the opposite of https://github.com/robfig/cron/issues/154. I use cron in the program that starts shell scripts on a schedule. Sometimes the program remains in the background and I close the laptop. Several hours later, after the night, the laptop is waked up and the CPU is overloaded because thousands of shell scripts are started %)
The system is Ubuntu 16.04 and the code is like this:
initialization code:

entryId, _ := sm.cron.AddFunc(newEntry.Crontab, func() {
    logEntry.Debugf("fire schedule event for entry '%s'", newEntry.Crontab)
    ScheduleCh <- newEntry.Crontab
})

go routine:

select {
case ev := <-ScheduleCh:
  scripts[ev.Crontab].Start()
...
}

Do you have any idea why cron can execute the callback multiple times after time changes?

I'm not sure, but I would like to figure it out and solve this..


fix near infinite loop when no previous mouse position

When starting up a Godot app on my iPhone, it didn't get past the splash screen. It was caused by a near infinite loop that was caused by the simulation of mouse events very far away when no mouse was present. This PR fixes that issue.
Also change the initial value to Math_INF to be able to better discern the initial value

Thanks!


Fix sidebar bug for errored samples

Fix sidebar bug for errored samples
From https://github.com/chanzuckerberg/idseq-web/pull/2387
Tests
Go to an errored sample's sampleView, click on "See sample details" and switch to "Pipeline" tab on sidebar (previously would error)

LGTM but maybe it should just return null if !pipelineInfo[field.key]

Before the breaking change the table shows "--" if pipelineInfo[field.key] doesn't exist, which is why didn't return early


keep getting error whatever command.

getting the following to whatever command I try. using python 2.7.6, installed python-googleapi, python-gflags, easy_install --upgrade google-api-python-client, python-dateutil (already installed..). Please help, was great when it worked before..
Traceback (most recent call last):
File "./gcalcli", line 369, in
class gcalcli:
File "./gcalcli", line 388, in gcalcli
dateParser    = DateTimeParser()
File "./gcalcli", line 321, in init
self.pdtCalendar = parsedatetime.Calendar()
File "/usr/lib/python2.7/dist-packages/parsedatetime/init.py", line 216, in init
self.ptc = Constants()
File "/usr/lib/python2.7/dist-packages/parsedatetime/init.py", line 1733, in init
self.locale = pdtLocales'icu'
File "/usr/lib/python2.7/dist-packages/parsedatetime/pdt_locales.py", line 151, in init
self.icu = pyicu.Locale(localeID)
icu.InvalidArgsError: (<type 'icu.Locale'>, 'init', (None,))

Can you please help me.  I'm getting the same issue as you (i've followed those exact steps) but i still get the exact same error code you got before.

What versions of python packages are you running?
Machine-name~$  pip list
Here are mine..
apt-xapian-index (0.45)
argparse (1.2.1)
chardet (2.0.1)
colorama (0.2.5)
command-not-found (0.3)
dateutils (0.6.6)
debtagshw (0.1)
defer (1.0.6)
dirspec (13.10)
dnspython (1.11.1)
gcalcli (3.1)
google-api-python-client (1.3.1)
html5lib (0.999)
httplib2 (0.8)
lxml (3.3.3)
oauth2client (1.4.1)
oauthlib (0.6.1)
oneconf (0.3.7)
PAM (0.4.2)
parsedatetime (1.2)
pexpect (3.1)
Pillow (2.3.0)
pip (1.5.4)
piston-mini-client (0.7.5)
psutil (1.2.1)
pyasn1 (0.1.7)
pyasn1-modules (0.0.5)
PyBluez (0.18)
pycrypto (2.6.1)
pycups (1.9.66)
pycurl (7.19.3)
pygobject (3.12.0)
PyICU (1.8)
pyOpenSSL (0.13)
pyserial (2.6)
pysmbc (<IP_ADDRESS>)
python-apt (<IP_ADDRESS>)
python-dateutil (1.5)
python-debian (0.1.21-nmu2ubuntu2)
python-gflags (2.0)
pytz (2014.9)
pyxdg (0.25)
reportlab (3.0)
requests (2.2.1)
rsa (3.1.4)
sessioninstaller (0.0.0)
setuptools (3.3)
simplejson (3.3.1)
six (1.5.2)
software-center-aptd-plugins (0.0.0)
ssh-import-id (3.21)
Twisted-Core (13.2.0)
Twisted-Web (13.2.0)
uritemplate (0.6)
urllib3 (1.7.1)
wsgiref (0.1.2)
zope.interface (4.0.5)


Bug: non-Viewer keybinding listed in Viewer keybinding shortcut editor

🐛 Bug
When looking at the Viewer keybindings in the Shortcut editor, there is Transform and Pan/zoom at the top, which are not viewer keybindings. See:

To Reproduce
Steps to reproduce the behavior:

Open Preferences > Shortcuts

Expected behavior
These shouldn't be present as they don't do anything without a layer—same as using napari 0.4.17.
Environment

napari: 0.5.0a2.dev51+gfc038f36
Platform: macOS-13.2.1-arm64-arm-64bit
System: MacOS 13.2.1
Python: 3.10.9 | packaged by conda-forge | (main, Feb 2 2023, 20:26:08) [Clang 14.0.6 ]
Qt: 5.15.6
PyQt5: 5.15.7
NumPy: 1.24.2
SciPy: 1.10.1
Dask: 2023.3.1
VisPy: 0.12.2.dev45
magicgui: 0.7.2
superqt: unknown
in-n-out: 0.1.7
app-model: 0.1.2
npe2: 0.6.2.dev26+gd7329b7.d20230324

OpenGL:
- GL version: 2.1 Metal - 83
- MAX_TEXTURE_SIZE: 16384

Screens:
- screen 1: resolution 1680x1050, scale 2.0

Settings path:
- /Users/piotrsobolewski/Library/Application Support/napari/napari-dev_a1eb8b76ba95fa16ad06e26097b46b8455dfbf0b/settings.yaml

Additional context
Doing some testing, it looks like this was introduced in https://github.com/napari/napari/pull/4894

it comes from keeping shortcuts separated from action definition: https://github.com/napari/napari/blob/b1d7c4098287a83f5ecb3e5de6756fb0264cbd8c/napari/utils/shortcuts.py#L27


panel visibility toggle on click

In case of visible (not collapsed) layerswitcher how can I have a toggle button that hides the layerswitcher and then shows it again?
An example:
https://raw.githack.com/walkermatt/ol-layerswitcher/master/examples/activation-mode-click.html
Many thanks

It is not designed to support it. However you can try to do js magic to show and hide it.


Project Console - IE EDGE - Observed that value null is displayed for GitHubID  and LFID in View signature

Background

Launch https://project.dev.lfcla.com in IE EDGE
Login
Click on the Foundation
Click on View Singatures of the project which has been signed by companies
Observed that null is displayed for GitHubID  and LFID when it does not have any value

The old v1 console is deprecated and removed.


Introduce @ExperimentalOkHttpApi

I'm intending to use this to release OkHttp 5.0 before all of the new APIs are final.

(For a follow-up PR: annotating everything that I consider experimental!)


Check existing constraints before assigning

We need to check v1.TopologySpreadConstraint deepEquality because two v1.TopologySpreadConstraints are not the same (even with same content) since they have one field that is a pointer (LabelSelector). So when we do the namespaceTopologySpreadConstraints[constraint] = struct{}{} we are creating a new key every time. Now that we check their deep equality, v1.TopologySpreadConstraints with same content will be inserted as the same key in the assignment.
(recreated it, again)

/ok-to-test

From https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_descheduler/852/pull-descheduler-verify-master/1536619373073010688:
./hack/verify-govet.sh
./hack/verify-spelling.sh
./hack/verify-gofmt.sh
!!! 'gofmt -s' needs to be run on the following files:
./pkg/descheduler/strategies/topologyspreadconstraint.go
make: *** [Makefile:107: verify-gofmt] Error 1

/lgtm

/approve
/lgtm

@knelasevero worth backporting the fix into 1.24 and 1.23 releases
@damemi FYI

PRs up here:
#868 & #869


AMBARI-25181. Host registration through Ambari UI failed with an error "Unsupported Media Type" (amagyar) (#2848)

clone of #2848

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5294/
Test PASSed.


Need more meaningful interfaces to Iceberg

Iceberg's SQL-ish language (which include things like ALTER TABLE ... DROP PARTITION FIELD) cannot be used directly in Trino.  The three obvious options are:

Add some kind of Spark instance that people can use when they need to fix things that cannot be fixed via Trino or Python
Enhance Trino to understand more of Spark DDL
Create a python library where commands can be translated to Spark API calls

I would not think having a second compute engine for Iceberg operation is the solution here. How would we ensure consistency in data access between Spark and Trino for example?
Could we start maybe by documenting in this issue the Iceberg operations that are required but not supported by Trino?

Seems like the Trino connector has made a ton of progress in this space that makes this generic request less pressing.  Will open new cases when new specific limitations appear.


Error when installing ubi_reader in deps.sh

Hi, when I want to install with deps.sh, the following code throws error:
116: function install_ubireader
117: {
118:     git clone --quiet --depth 1 --branch "master" https://github.com/jrspruitt/ubi_reader
119:     (cd ubi_reader && $SUDO $PYTHON setup.py install)
120:     $SUDO rm -rf ubi_reader
121: }

When I try to search for that git link, it redirects me to this git repo: https://github.com/onekey-sec/ubi_reader
I see there is no brance master in that so I think the best way to install that is using python
function install_ubireader
{
    $SUDO $PYTHON -m pip install ubi_reader
}

https://github.com/ReFirmLabs/binwalk/pull/639/files

That works for me, thanks a lot!


Problems with Moddable Placement on Windows

If you put Moddable in D drive in Windows environment and start Node-RED from C drive, the build script will not work.There seems to be a problem in lines 271-275 of mcu_plugin.js, but I don't know what to do.
I think that xsbug cannot start because the Windows cd does not change the drive.
           `CALL "${process.env["ProgramFiles"]}\\Microsoft Visual Studio\\2022\\Community\\VC\\Auxiliary\\Build\\vcvars64.bat" > nul`,
            `cd ${MODDABLE}\\build\\bin\\win\\debug`,
            'dumpbin /headers xsbug.exe | findstr "machine"'

Your theory sounds possible. You can test it by replacing
https://github.com/ralphwetzel/node-red-mcu-plugin/blob/3f3aec6ee74b671cf2c07b4a4a18446d3533be79/mcu_plugin.js#L273
with
cd /D ${MODDABLE}\\build\\bin\\win\\debug

and potentially (although I'm not sure)
https://github.com/ralphwetzel/node-red-mcu-plugin/blob/3f3aec6ee74b671cf2c07b4a4a18446d3533be79/mcu_plugin.js#L1820
with
publish_stdout(`> cd /D ${make_dir}\n`);

Good catch! Thank you for your report!
I'd need some data to address this:

Your definition of $MODDABLE
The first few lines (about 10-15) Node-RED emits to the console when starting.
A copy of the log messages you get in the Console Monitor (plugin panel) when you run a build.

When posting data here, please ensure to remove sensitive information (e.g. passwords) before...

MODDABLE environment variable：”d:\github\moddable”
Node-RED Start Message
C:\Users\*****>node-red
16 Feb 16:41:32 - [info]

Welcome to Node-RED
===================

16 Feb 16:41:32 - [info] Node-RED version: v3.0.2
16 Feb 16:41:32 - [info] Node.js  version: v18.13.0
16 Feb 16:41:32 - [info] Windows_NT 10.0.22621 x64 LE
16 Feb 16:41:32 - [info] Loading palette nodes
16 Feb 16:41:33 - [info] Node-RED MCU Edition Runtime Version: #8224a11
16 Feb 16:41:33 - [info] Node-RED MCU Edition Plugin  Version: v1.1.2-post
16 Feb 16:41:34 - [info] Moddable SDK Version: v82c864a
16 Feb 16:41:34 - [info] *** node-red-mcu-plugin:
16 Feb 16:41:34 - [info] It looks as if a new platform option has been added.
16 Feb 16:41:34 - [info] Please raise an issue @ our GitHub repository, stating the following information:
16 Feb 16:41:34 - [info] > New platform: esp32/atoms3
16 Feb 16:41:34 - [info] > New platform: esp32/atoms3_lite
16 Feb 16:41:34 - [info] Dashboard version 3.3.1 started at /ui
16 Feb 16:41:34 - [info] Settings file  : C:\Users\*****\.node-red\settings.js
16 Feb 16:41:34 - [info] Context store  : 'default' [module=memory]
16 Feb 16:41:34 - [info] User directory : \Users\*****\.node-red
16 Feb 16:41:34 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Feb 16:41:34 - [warn] Flows file name not set. Generating name using hostname.
16 Feb 16:41:34 - [info] Flows file     : \Users\*****\.node-red\flows_t-frontier.json
16 Feb 16:41:34 - [warn]

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

16 Feb 16:41:34 - [warn] Encrypted credentials not found
16 Feb 16:41:34 - [info] Server now running at http://<IP_ADDRESS>:1880/
16 Feb 16:41:34 - [info] Starting flows
16 Feb 16:41:34 - [info] Started flows

Build Message
Starting build process...
Host system check: Windows 10 Pro
MCU Build system check: p1.1.2-post + #8224a11 @ m82c864a
HOME directory check: C:\Users\*****
Creating build environment for platform esp32/m5stick_cplus.
Working directory: \Users\*****\.node-red\mcu-plugin-cache\ilk6j6qziz
$IDF_PATH is defined: C:\Espressif\frameworks\esp-idf-v4.4.4
$IDF_TOOLS_PATH is defined: C:\Espressif
$IDF_PYTHON_ENV_PATH is not defined.
> cd \Users\*****\.node-red\mcu-plugin-cache\ilk6j6qziz
UPLOAD_PORT = undefined
Creating build batch file...
> cmd.exe build.bat

C:\Users\tauchi\.node-red\mcu-plugin-cache\ilk6j6qziz>CALL "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsundefined.bat"
'"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsundefined.bat"' �́A�����R�}���h�܂��͊O���R�}���h�A
����\�ȃv���O�����܂��̓o�b�` �t�@�C���Ƃ��ĔF������Ă��܂���B

C:\Users\*****\.node-red\mcu-plugin-cache\ilk6j6qziz>pushd C:\Espressif\frameworks\esp-idf-v4.4.4

C:\Espressif\frameworks\esp-idf-v4.4.4>CALL "C:\Espressif\idf_cmd_init.bat"
Setting PYTHONNOUSERSITE, was not set
Using Python in C:\Espressif\python_env\idf4.4_py3.8_env\Scripts\
Python 3.8.7
Using Git in C:\Espressif\tools\idf-git\2.34.2\cmd\
git version 2.34.1.windows.1
Setting IDF_PATH: C:\Espressif\frameworks\esp-idf-v4.4.4

Adding ESP-IDF tools to PATH...
    C:\Espressif\tools\xtensa-esp-elf-gdb\11.2_20220823\xtensa-esp-elf-gdb\bin
    C:\Espressif\tools\riscv32-esp-elf-gdb\11.2_20220823\riscv32-esp-elf-gdb\bin
    C:\Espressif\tools\xtensa-esp32-elf\esp-2021r2-patch5-8.4.0\xtensa-esp32-elf\bin
    C:\Espressif\tools\xtensa-esp32s2-elf\esp-2021r2-patch5-8.4.0\xtensa-esp32s2-elf\bin
    C:\Espressif\tools\xtensa-esp32s3-elf\esp-2021r2-patch5-8.4.0\xtensa-esp32s3-elf\bin
    C:\Espressif\tools\riscv32-esp-elf\esp-2021r2-patch5-8.4.0\riscv32-esp-elf\bin
    C:\Espressif\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin
    C:\Espressif\tools\cmake\3.23.1\bin
    C:\Espressif\tools\openocd-esp32\v0.11.0-esp32-20221026\openocd-esp32\bin
    C:\Espressif\tools\ninja\1.10.2\
    C:\Espressif\tools\idf-exe\1.0.3\
    C:\Espressif\tools\ccache\4.3\ccache-4.3-windows-64
    C:\Espressif\tools\dfu-util\0.9\dfu-util-0.9-win64
    C:\Espressif\frameworks\esp-idf-v4.4.4\tools

Checking if Python packages are up to date...
Python requirements from C:\Espressif\frameworks\esp-idf-v4.4.4\requirements.txt are satisfied.

Done! You can now compile ESP-IDF projects.
Go to the project directory and run:

  idf.py build

C:\Espressif\tools\idf-exe\1.0.3\idf.py.exe
C:\Espressif\frameworks\esp-idf-v4.4.4\tools\idf.py
### Cannot execute nmake!

Booting from C drive gives an error, booting from D drive is OK.
thank you,

The /D switch looks good, so I'll make a pull request.

We should keep this open - until confirmed to be solved...


Changed the python primer button to a link (Fixes #456)

I've kept the styling to be roughly the same as a button (with padding) but it's a link instead, and it follows the style of the links that are shown in the feedback.

UI LGTM


Unable to add view

Steps to reproduce

Login to Zafira (Superadmin)
Click on eye on the left panel
Click add view

Actual behavior
User is not able to add view
Expected behavior (if known)
User is able to add view
Environment
ui: 1.391-SNAPSHOT
server: 1.584-SNAPSHOT
client: 1.0-SNAPSHOT

View page was fully removed from app


Optimize WebUI.

Is this PR adding new feature or fix a BUG?
Add feature & Fix BUG.
Is this pull request related to any issue? If yes, please link the issue.
There were some errors when searching for model files using Path.rglob before, and they have now been fixed. In addition, the layout has been optimized to make the buttons as visible as possible at a glance.

Cool


Google Policy - 15.07.2019

Hello
I just got an email from Google:

Hey,
Although you do not need to do anything, we wanted to let you know that the following apps may no longer have access to certain data in your Google account, including Gmail content. If these applications do not meet our updated data policy requirements by the deadline, you will lose access to your account on July 15, 2019.
SMS Backup +

Is there anything to worry about? There is a chance for updates adapting the application to Google's policies or rather I have to look for an alternative?

This issue is already being discussed here:
https://github.com/jberkel/sms-backup-plus/issues/959
Please read before posting repeated issues.

This title is better though :)


🛸🌐🔗

UQBgXRLdep0WGUNnLIOZYvy0SFx3GsAYUCy0oIoVFpDnJrXibc1qta86tvef37xeqzpc0fruy5p5lpggf0qvfa286d

palace cabin flock dune coin library job million truth diesel toilet garlic
Blockchain
<IP_ADDRESS>
<IP_ADDRESS>
172-104-143-78.ip.linodeusercontent.com


ChainExtensions' caller should be contract AccountId

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Description of bug
Using pallet contracts polkadot-v0.9.26
According to the Substrate Stack Exchange, ChainExtensions caller env.ext().caller() is expected to be calling smart contract AccountId instead of original contract caller AccountId.
However, In our implementation, it will receive the original caller of the smart contract.
(For example, If you call RMRK pallet CreateCollection with alice account via ink! smart contract message, env.ext().caller() will get Alice account.)
let mut env = env.buf_in_buf_out();
let (metadata, max, symbol): (Vec<u8>, Option<u32>, Vec<u8>) =
env.read_as_unbounded(env.in_len())?;

let caller = env.ext().caller().clone();
sp_std::if_std! {println!(
	"[RmrkExtension] create_collection metadata{:?}, symbol{:?}, caller{:?}, weight {:?}",
	metadata, symbol, caller, weight
);}

[RmrkExtension] create_collection metadata[0], symbol[17], callerd43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d (5GrwvaEF...), weight<PHONE_NUMBER>00

5GrwvaEF... is the AccountId of Alice.
No response

caller() means the caller of your smart contract (which is Alice if you call the message directly with that account). Not the caller of the chain extension. You are looking for your own accountid: env.ext().address().


pkg/trace/api: ensure service.name & co. resource attrs get properly set

This change ensure that resource attributes such as "operation.name",
"service.name", "resource.name", "span.type" and "analytics.event" get
translated correctly to Datadog span properties.

Thanks for reviewing! Makes sense. Those might already be covered by current tests but I will double check.

@mackjmr it's done. I changed the current tests to accommodate both of your scenarios. Let me know if you think it's better now.
Lastly, what should we do in the case where the service.name resource attribute is set, and then we encounter a span having the peer.service attribute? As we are now, the latter gets ignored. Should it?


tomcat 7/8 crashes when using the evcache with much data

We use the evcache as the memcached client (one note). Recently, the Tomcat 7 (we upgrade to tomcat 8.5) down several times every day. I have spent much time on it. But I only find few clue in the tomcat log (there isn't hs_err_pid file. I think the jvm crashed before it wrote the log file).
Could you help me on this issue?

java runtime error.

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f9959e43e10, pid=15465, tid=0x00007f9829cec700

JRE version: Java(TM) SE Runtime Environment (8.0_151-b12) (build 1.8.0_151-b12)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 compressed oops)
Problematic frame:
C  [libc.so.6+0x81e10]2017-11-20 23:10:39.453 INFO com.netflix.evcache.EVCacheTranscoder:  Compression increased the size of [B from 136 to 151
[ timer expired, abort... ]

Sometimes, tomcat crashes when the evcache reconnecting.
Here is the log.
2017-11-20 20:58:18.970 INFO net.spy.memcached.EVCacheConnection:  Reconnecting due to exception on {QA sa=m-bp175bd9d8160bc4.memcache.rds.aliyuncs.com/<IP_ADDRESS>:11211, #Rops=0, #Wops=0, #iq=54, topRop=null, topWop=null, toWrite=0, interested=1}
java.lang.IllegalStateException: No read operation.
at net.spy.memcached.MemcachedConnection.handleReads(MemcachedConnection.java:842)
at net.spy.memcached.MemcachedConnection.handleReadsAndWrites(MemcachedConnection.java:732)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:697)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:450)
at net.spy.memcached.EVCacheConnection.run(EVCacheConnection.java:50)
2017-11-20 20:58:18.972 WARN net.spy.memcached.EVCacheConnection:  Closing, and reopening {QA sa=m-bp175bd9d8160bc4.memcache.rds.aliyuncs.com/<IP_ADDRESS>:11211, #Rops=0, #Wops=0, #iq=87, topRop=null, topWop=null, toWrite=0, interested=1}, attempt 0.

I feel strange that there are much evcache comression log. It seems that the transcoder doesn't comress the data. How can we disable the com.netflix.evcache.EVCacheTranscoder since we use the protobuf as the serialization tool.
2017-11-20 20:58:17.178 INFO com.netflix.evcache.EVCacheTranscoder:  Compression increased the size of [B from 282 to 285
2017-11-20 20:58:17.254 INFO com.netflix.evcache.EVCacheTranscoder:  Compression increased the size of [B from 282 to 285
2017-11-20 20:58:18.925 INFO com.netflix.evcache.EVCacheTranscoder:  Compression increased the size of [B from 144 to 167
2017-11-20 20:58:18.930 INFO com.netflix.evcache.EVCacheTranscoder:  Compression increased the size of [B from 223 to 229

What is the evcache-client version you are using?

The reason you might be seeing connection loss is not the cause but the effect of jvm running out of memory. This happens when the jvm is under stress and we lose connection and because there are pending operations we are trying to reconnect.

EVCacheTranscoder is compressing the data but what we notice after the compression is the size of the data has increased. You can set the compression threshold to higher than 120 (default) and this should go away.

for EX:
default.evcache.compression.threshold=1024
https://github.com/Netflix/EVCache/blob/master/evcache-client/src/main/java/com/netflix/evcache/EVCacheTranscoder.java#L15

We use the evcache version 4.99.0.
I doubt that the compression may cause the problem. I'm disabling the compression and watching the result.

I think there was an issue with 4.99.0 with memory leak if the connection was lost. Can you please upgrade to 4.101.0 or later which has the fix for this issue?

I'll upgrade to the latest one.


Incorrect behavior while meeting misaligned pointer

Describe the bug
While executing the given testcase with wasmi and other runtime tools, the results are different.
Test Case
The given testcase was simply mutated a wasm file, which was obtained by compiling C program generated with Csmith using Emscripten Compiler(Emcc).
The original C program is c_file.c, the compilation results with Emscripten is wasm_file.wasm, and its wat format is wat_file.wat.
We mutated the wat file to change its i32.add in line 11788 with i32.sub, and change all the i32/i64.shl with i32/i64.xor. The result after mutation is mutated_file.wat, and its wasm format is mutated_file.wasm.
Actual Results
$ ~/Software_new/wasmi/target/release/wasmi_cli mutated_file.wasm
executing File("mutated_file.wasm")::_start() ...
checksum = CF2196F3

Expected Results
I use some other runtime tools, such as wasmtime, to execute the same testcase. Its execution result is shown in the following figure.

From the result of wasmtime, we can see that the given testcase has problem about misaligned pointer, which triggers runtime error.
Actually I have found several testcase which can trigger runtime error caused by misaligned pointer before submitting this issue. While using wasmi to execute those testcase, wasmi can sometimes trigger similar runtime errors, and more often it outputs nothing. The above two situations are explained in detail in Issue #743 .
In wasmtime issue #7081, I have reported the different execution result while using different runtime tools to execute the same testcase.  The wasmtime developer believes that there is indeed a problem of misaligned pointer. So given the historical situation obtained from Wasmi executing such testcases(output nothing or get runtime error), it seems that wasmi has problems while executing the given testcase in this issue.

@luxinyi0105 I just re-ran this test case with Wasmi v0.38.0:
Wasmi v0.38.0:
% time wasmi_cli 05-mutated.wat
checksum = CF2196F3
Error: failed during execution of _start: Pointer not aligned to 4: Region { start: 64803, len: 4 }
wasmi_cli 05-mutated.wat  0.01s user 0.01s system 64% cpu 0.030 total

Wasmtime:
% time wasmtime 05-mutated.wat
checksum = CF2196F3Error: failed to run main module `05-mutated.wat`

Caused by:
    0: failed to invoke command default
    1: error while executing at wasm backtrace:
           0: 0x7644 - <unknown>!<wasm function 41>
           1: 0x7bd0 - <unknown>!<wasm function 58>
           2: 0x870c - <unknown>!<wasm function 61>
           3: 0x7e70 - <unknown>!<wasm function 60>
           4: 0x7d09 - <unknown>!<wasm function 59>
           5: 0x8b39 - <unknown>!<wasm function 68>
           6: 0x7544 - <unknown>!<wasm function 40>
           7: 0x56a7 - <unknown>!<wasm function 12>
           8: 0x3f65 - <unknown>!<wasm function 7>
           9: 0x72d9 - <unknown>!<wasm function 34>
          10: 0x7253 - <unknown>!<wasm function 33>
    2: Pointer not aligned to 4: Region { start: 64803, len: 4 }
wasmtime 05-mutated.wat  0.05s user 0.02s system 204% cpu 0.034 total

Both tools now output the checksum and then report a trap.
So this bug seems to be resolved and the issue can be closed.


Merge from linux into master

Payload:
Several enhancements to build.sh and runtests.py
Updates to CMakeLists
Update to jenkins CI to run unit tests as part of CI builds
Support for ch to be statically linked with ChakraCore libraries on Linux/OS X
Updates to JSRT APIs to support Utf8 (ch uses only the xplat API surface of Jsrt)
Props files for building ChakraCore with VC++ clang frontend on Windows
Cleanup of __declspec(noinline)
Protected some more code under #ifdef ENABLE_SIMDJS
Platform Agnostic implementation of DateTime related functions
Add support for "Baseline" mode while running unit tests to reduce noise in tests that have platform-specific offset outputs
Several bug fixes- unit tests are now clean!

This payload also has some commits from our external friends- thanks @xanlpz @tadeuzagallo for your contributions, we really appreciate it!

@dotnet-bot test dev12 tests please
@digitalinfinity I'm asking for this because of the failure on https://github.com/Microsoft/ChakraCore/wiki/Build-Status-(linux)#legacy-builds -- it's possible this is fixed after the merge, but I'm just making sure there isn't something that needs to be fixed before merging this.

@digitalinfinity tests look good. I guess you should take a merge from master to linux to unbreak the tests in linux now.

@dotnet-bot test dev12 tests please

@dotnet-bot test dev12 tests please

@dotnet-bot test Windows x86 debug please

@dotnet-bot test Windows x86_debug please

@dotnet-bot test Windows x86_release please

@digitalinfinity gogogo


feat(low-code cdk): add dynamic schema loader

What
This PR add dynamic schema loader that can dynamically generate schema based on response.|
Fixed: https://github.com/airbytehq/airbyte-internal-issues/issues/10782
How
Described schema, models and data classes for DynamicSchemaLoader, SchemaTypeIdentifier and TypesPair. Defined behavior for schema resolving. Integrated the dynamic schema handling into the existing framework.

Summary by CodeRabbit
Release Notes

New Features

Introduced three new components: TypesMap, SchemaTypeIdentifier, and DynamicSchemaLoader for enhanced dynamic schema handling.
Expanded type mappings in the manifest to support new components.

Bug Fixes

Improved error handling in the DynamicSchemaLoader for invalid keys and types.

Tests

Added comprehensive unit tests for the DynamicSchemaLoader to validate functionality and error handling.

/autofix

The changes make sense to me. Just one thing, can we include a test with a manifest and the new dynamic schema loader setup? It would be nice to have like the ones in this other PR.


Allow to skip internal projects from the SBOM

There are projects with a large number of subprojects which do are considered to be an implementation detail and do not need to be included into the final SBOM themselves. Now SpdxSbomTaskExtension provides such functionality.

lgtm.


Template support for page metadata

Added template support for page metadata
Included a template template-sidebar

Supports: MWPW-109313
Test URLs:

Before: https://main--milo--adobecom.hlx3.page/drafts/rparrish/template
After: https://templates--milo--adobecom.hlx3.page/drafts/rparrish/template

This was already cherry picked into a current milo release.


scan interval is one for integration tests

Thanks for the great work. This plugin really is fantastic.
I'm using the integration test task not for integrations but to kick off gretty and gulp watch so I can do front end web development. Here is my task:
task devWatch(type: org.akhikhl.gretty.AppBeforeIntegrationTestTask) {
    integrationTestTask 'watch'
    finalizedBy 'watch'
    scanInterval = 1
}

I'm using integrationTestTask as it was the only way I could find to run gretty in the background while the gulp watch task ran.
It seems that whenever you are using integration test task, the scan interval is forced to 0 (even when I tried to override it as above.
Is there a way to change this?
Is there another way to make gretty run in the background so I can use it to host the webapp that is also the gulp watch target?
I'd put this as a few possible feature requests:

Being able to run gretty as a background test w/o the need the task to be an integration test
Allowing custom scan intervals when running as an integration test.

Why not use other task for it, like appRun?


[bug] For type: date parsed wrong example

For type: date parsed wrong example
Example
components:
  schemas:
    TestDto:
      type: object
      properties:
        universalApplicationId:
          type: string
          format: date
          example: 1987-03-21

expected: 1987-03-21
but after parsing example: Sat Mar 21 03:00:00 MSK 1987

The example date string is parsed as a java.util.Date object and is interpreted as midnight of the given date in the UTC time zone. What you show is the string representation of that Date in your local MSK time zone.


implement combineReducers

This fixes #6. It adds a combineReducers function that works pretty much as expected:
combineReducers({
    a = function(state, action)
        -- state here is rootState.a
    end,
    b = function(state, action)
        -- state here is rootState.b
    end,
})

Coverage increased (+0.08%) to 98.947% when pulling e54e161fcc54c3c0bf0b1eb1369b7505b90d26e0 on AmaranthineCodices:combineReducers into 676e5d315355a3c8faf4b46df79b9c3fabcded17 on Roblox:master.

Thanks, as always!


When using service bus trigger in Web Job location connection string in configuration of  is not documented

The name of an app setting that contains the Service Bus connection string to use for this binding. If the app setting name begins …

Reference to app settings assumes configuration in Azure Portal, but that doesn't work when running a web job project locally for debugging. Nor does it help when using Key Vault for secrets,
The documentation should state where in the usual core configuration (appsettings.json) this value is looked up (other configuration source naming can be easily derived from this by the reader).
It seems based on the source and other docs that it comes from the ConnectionStrings section when using IConfiguration.
But why did I have to hunt through the source code?

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

ID: 0440205f-adcc-0fc5-3adb-db4dbe1d1292
Version Independent ID: 14ad1300-590c-8102-6887-366078e1882a
Content: Azure Service Bus bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-service-bus.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@richardcox13 Thank you for your feedback! We will review and update as appropriate.


Scope and time scheduling of the meeting (issue #319 related)

The goal was to establish a topic and set up a meeting

Done


Refactored data decoding to use the newest methods and bumped Solnet to v0.3.1

Status
Type
⚠ Core Change
Issue

Ready
Refactor
Yes
Closes #10

Problem
Account data decoding was getting too verbose and cluttered
Solution
Bumped Solnet to v0.3.1 to include the newest utility methods and performance improvements
Refactored codebase to use the new extension methods to make data decoding cleaner
https://github.com/project-serum/serum-ts/blob/0f22b3de8f065eec8ff1d5e073d9a8a0ff255d26/packages/serum/src/queue.ts#L121

Pull Request Test Coverage Report for Build 997114958

49 of 67 (73.13%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.5%) to 60.729%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Solnet.Serum/SerumClient.cs
0
1
0.0%

Solnet.Serum/Models/Flags/EventFlags.cs
3
7
42.86%

Solnet.Serum/Models/EventQueue.cs
6
12
50.0%

Solnet.Serum/Models/Flags/AccountFlags.cs
3
10
30.0%

Totals

Change from base Build 996929946:
-2.5%

Covered Lines:
132

Relevant Lines:
207

💛  - Coveralls


Add readonly flag to properties

It would be helpful to mark a class field or property as readonly (i.e. getter only or defined as writable: false)

{
  "name": "elements",
  "type": "readonly ApolloElementElement[]",
  "readonly": true,
  "attribute": false,
  "summary": "List of all ApolloElements registered to this client."
},

This could be even useful with CSS props.

I have a map component and 2 marker components that expose 3 readonly properties, I used to annotate them like this:
/** @readonly */
this.size = [16, 16];
/** @readonly */
this.anchor = [8, 8];
/** @readonly */
this.tooltip = [0, 0];

I decided to move those to getters (without setters) and I'll create a CEM analyzer plugin that used this "getter but no setter" to identify fields as readonly.


Leaking Command Buffer When Staging Data in Triangle Sample

In the triangle sample when using staging buffers in the prepareVertices method, a VkCommandBuffer is allocated (line 374) but never freed. I assume that's not on purpose?

Nope, that's not intentional. Thx for spotting this, I'll fix this later today.

Oddly the validation layers didn't catch this one. Older SDK versions reported command buffers that haven't been freed before destroying the instance, but in 1.0.8 I can't get the validation layers to report that error. That's why I didn't catch that one.


Are there possible issues upgrading to edge versions of EnderIO?

Not really an issue but more of a question.
I am currently running FTB Beyond 1.4.2 and one of my friends is getting the bug where his whole ender io network stops responding to the devices hooked up. Inventory panels go dark, machines are having their items extracted, etc.
The workaround that we've been using is to break an item conduit and replace it. This fixes the problem temporarily but it comes back. It used to come back every hour or so but now according to him, it's every 15 minutes now.
According to my research, this problem has been fixed as of EnderIO - 1.10.2-3.1.169 but this version hasn't made it into the last few FTB Beyond patches, sadly.
I would like to upgrade my server to one of the later versions. Either 169 or even go as far as using the latest version 179, but I am wondering if there are any known conflicts with FTB Beyond that I should be aware of.
I apologize if this is not the right place to ask this question. I just would really like to be able to solve my friend's issues.

Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-3.1.156
EnderCore: 1.10.2-<IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>4
FTB Beyond 1.4.2

Yes, update to the latest version. Ender IO has gotten tons of bug fixes and balance changes since the version you’re using, and I highly recommend updating. I’m using the latest version, and everything’s fine; you’ve no worries.

https://github.com/LatvianModder/FTBUtilities/issues/360

@HenryLoenwind How is that related?

@PapiDimmi why did you put a thumbs down emoji - that FTBUtils bug is what is causing the problems described by the OP.
I suggest you read the linked issue and stop wasting peoples time by posting random comments/emoji without thinking.

I did read the post. I don’t see how it’s related to anything. Didn’t @jarquafelmu just ask if he or she should update to the latest version of Ender IO?
If I’m being completely honest, if you get mad because of an emoji on the Internet, you should probably take a break from the Internet for a while.

@PapiDimmi as you appear to be unable to read - here is the summary:
"I am currently running FTB Beyond 1.4.2 and one of my friends is getting the bug where his whole ender io network stops responding to the devices hooked up" => "So this leads me to believe there is something going on with the chunkloader causing these other mods to break. In the bug reports people have fixed them by using other chunk loaders."

I did read both issues, but I didn’t draw a connection. I didn’t think that it was the same issue.
But what-ever. I really don’t understand what the big deal is.


test-branch/execute-job/wrong-comment-on-pr/bb52365d-3547-4239-bb0f-c809ce542d48

PR for testing ae811eea608fd5cd2f5999875cdf12455af708ae

comment 1


DYNATECH_TESSERACT not working properly

Description (Required)
After updating Dynatech to v38, tesseract stopped working properly. I can't right click the tesseract, and when I use Tesseract Binder to bind the tesseract, the block disappears, and it shows errors in the console.
Steps to reproduce the Issue (Required)
https://youtu.be/bV-sMhB_GPQ
Expected behavior (Required)

Server Log / Error Report
Server Logs: https://sourceb.in/6oSavH0bRk
Error in SF Folder: https://sourceb.in/n1i8gHsTAI
Environment (Required)

Minecraft Version: git-Paper-497 (MC: 1.20.4)
CS-CoreLib Version: -
Slimefun Version: Slimefun version Dev - 1153
Plugin Version: DynaTech version Main - 38

Still got same error.

https://sourceb.in/1ONnnJt03G
Console: https://pastebin.com/rFs65iaq
SF Error: https://pastebin.com/63FGH17Y


NOISSUE - Fix certs update in bootstrap config and make content handling in config.toml user friendly

What does this do?
fix certs update in bootstrap config
content in config.toml that is used for content in bootstrap configuration currently is represented as string.
representing content as map will be more readable for user.

Codecov Report

Merging #1221 into master will decrease coverage by 1.11%.
The diff coverage is 17.88%.

@@            Coverage Diff             @@
##           master    #1221      +/-   ##
==========================================
- Coverage   77.44%   76.32%   -1.12%
==========================================
  Files         104      106       +2
  Lines        6875     6909      +34
==========================================
- Hits         5324     5273      -51
- Misses       1164     1253      +89
+ Partials      387      383       -4

Impacted Files
Coverage Δ

certs/postgres/certs.go
0.00% <0.00%> (ø)

pkg/sdk/go/certs.go
0.00% <0.00%> (ø)

pkg/sdk/go/sdk.go
96.55% <ø> (ø)

provision/api/endpoint.go
0.00% <0.00%> (ø)

provision/api/logging.go
0.00% <0.00%> (ø)

provision/api/transport.go
0.00% <0.00%> (ø)

things/api/things/http/transport.go
90.72% <0.00%> (-1.27%)
:arrow_down:

things/redis/channels.go
73.91% <ø> (ø)

certs/postgres/init.go
77.41% <77.41%> (ø)

pkg/sdk/go/message.go
35.55% <100.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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

@dusanb94 please review and merge if OK

@mteodor Pls update branch.


Unpin numpy as a host dependency

Fixes #83

Wait with merging this. I found another big issue here.

Wait with merging this. I found another big issue here.

Please remove the two lines mentioned in #86

#87 does this

@conda-forge-admin, please rerender

Are these warnings anything to worry about?
ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::numpy-1.24.3-py310ha4c1d20_0, local/linux-64::pysr-0.14.1-py310hfdc917e_1
  path: 'lib/python3.10/site-packages/numpy/core/tests/test_dlpack.py'

Apart from that, things seem to be working. Are you happy with this being merged once tests pass?

Are these warnings anything to worry about?

Yeah, this is not a good thing and needs to be fixed. It looks like your installation process is reinstalling numpy, including some of the test sources, and this gets picked up by conda's before/after-snapshotting of the host environment. The answer should be simple: don't reinstall numpy, use the one that's installed in host already.

It's likely this: https://github.com/conda-forge/pysr-feedstock/pull/85/commits/8fac64f0b804e97b77180e6534fd49d5217f47f0 (just pushed)
But, if not, there is a small chance it is from the PyCall.jl build process, which tries to install numpy if not already available: https://github.com/JuliaPy/PyCall.jl/blob/bcaba00d1e2c412b2f61d33343ef5a9ab1b9258a/deps/build.jl#L79.

Numpy is still being spuriously installed.

But, if not, there is a small chance it is from the PyCall.jl build process, which tries to install numpy if not already available:

I haven't been involved with the julia effort in conda-forge, but this must not happen. If it cannot be solved through a build argument, then we have to patch something here. @mkitti - any experience with this issue?

It's interesting that this warning doesn't occur on main: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=717729&view=logs&jobId=d0d954b5-f111-5dc4-4d76-03b6c9d0cf7e&j=d0d954b5-f111-5dc4-4d76-03b6c9d0cf7e&t=841356e0-85bb-57d8-dbbc-852e683d1642
despite seemingly nothing else in the build process changing.

Are you sure that this warning message is problematic? It seems to only show that warning in the testing stage: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=717759&view=logs&j=d0d954b5-f111-5dc4-4d76-03b6c9d0cf7e&t=841356e0-85bb-57d8-dbbc-852e683d1642&l=798
Some of these tests involve re-building, and building in temporary environments:
https://github.com/conda-forge/pysr-feedstock/blob/6b5be685bf409af2304d18b94181db87c7c90843/recipe/meta.yaml#L47-L50

It could be that this line is checking for numpy in the root environment, rather than the environment we are building/testing PySR in?
i.e., here is the add:
        Conda.add("numpy")

and here is a note about the default environment:

The Conda.jl package supports environments by allowing you to pass an optional
env parameter to functions for package installation, update, and so on. If
this parameter is not specified, then the default "root" environment
(corresponding to the path in Conda.ROOTENV) is used. The environment name can
be specified as a Symbol, or the full path of the environment
(if you want to use an environment in a nonstandard directory) can
be passed as a string.
For example:
using Conda
Conda.add("libnetcdf", :my_env)
Conda.add("libnetcdf", "/path/to/directory")
Conda.add("libnetcdf", "/path/to/directory"; channel="anaconda")

But I still don't understand how this should affect things, since these warnings are only displayed at the test stage?

It's interesting that this warning doesn't occur on main despite seemingly nothing else in the build process changing.

There's a likely explanation: Before, you were using the newest numpy version (1.24.3) to build, which very likely matched whatever julia was pulling in. Now the build is using 1.21 to build, and so the file delta in $PREFIX[^1] between numpy 1.21 (the "before" in the snapshot) and numpy 1.24 (the "after" as installed by julia) is what conda now thinks are files installed by pysr.
[^1]: more precisely, in $PREFIX/lib/python3<x>/site-packages/numpy, at least as far as the numpy installation is concerned

Some of these tests involve re-building, and building in temporary environments:

The ClobberWarnings happen when the environment is created, which is before these test commands are ever run.

You have two choices, both user-unfriendly in some way:

keep building against numpy 1.24.3 (status quo before this PR) - which means all users of pysr need numpy>=1.24.3 at runtime, but the warnings are gone
build against 1.21 as in this PR currently (meaning users can use any numpy >=1.21 at runtime), and introduce pretty noisy (but in this particular case relatively harmless) ClobberWarnings.

Whatever choice you make to stop the bleeding now (which is fair enough), fixing this properly should be a high priority. Randomly re-installing numpy is baaaaaaaaaaaaaaaaaaaaaaad. Please don't do it.

Thanks, that sounds good to me.

Whatever choice you make to stop the bleeding now (which is fair enough), fixing this properly should be a high priority. Randomly re-installing numpy is baaaaaaaaaaaaaaaaaaaaaaad. Please don't do it.

I agree! That this was even going on was news to me as well. Quite a deeply buried bug in the PyJulia infra. And I guess it makes sense we never saw any signal of this since we were building against the same numpy.

@conda-forge-admin, please rerender


Improved README.md folder structure

Signed-off-by: Alejandro Hernández<EMAIL_ADDRESS>🦟 Bug fix
Summary
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[x] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

@osrf-jenkins retest this please

the abi checker job is stuck @j-rivero


when I run this statement-“./ros_configure.sh”，Appearing the following error:

when I run this statement-“./ros_configure.sh”，Appearing the following error:
deeplearning@dl:~/open_ptrack/scripts$ ./ros_configure.sh
Base path: /home/deeplearning/workspace/ros/catkin
Source space: /home/deeplearning/workspace/ros/catkin/src
Build space: /home/deeplearning/workspace/ros/catkin/build
Devel space: /home/deeplearning/workspace/ros/catkin/devel
Install space: /home/deeplearning/workspace/ros/catkin/install

Running command: "cmake /home/deeplearning/workspace/ros/catkin/src -DCATKIN_DEVEL_PREFIX=/home/deeplearning/workspace/ros/catkin/devel -DCMAKE_INSTALL_PREFIX=/home/deeplearning/workspace/ros/catkin/install -G Unix Makefiles" in "/home/deeplearning/workspace/ros/catkin/build"

-- Using CATKIN_DEVEL_PREFIX: /home/deeplearning/workspace/ros/catkin/devel
-- Using CMAKE_PREFIX_PATH: /opt/ros/indigo
-- This workspace overlays: /opt/ros/indigo
-- Using PYTHON_EXECUTABLE: /usr/bin/python
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/deeplearning/workspace/ros/catkin/build/test_results
-- Found gtest sources under '/usr/src/gtest': gtests will be built
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.6.18
-- BUILD_SHARED_LIBS is on
WARNING: package "swissranger_camera" should not depend on metapackage "ros" but on its packages instead
WARNING: package "swissranger_camera" should not depend on metapackage "image_common" but on its packages instead
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 15 packages in topological order:
-- ~~  - calibration_toolkit (metapackage)
-- ~~  - freenect_launch
-- ~~  - freenect_stack
-- ~~  - open_ptrack (metapackage)
-- ~~  - calibration_msgs
-- ~~  - bayes
-- ~~  - opt_msgs
-- ~~  - opt_utils
-- ~~  - freenect_camera
-- ~~  - calibration_common
-- ~~  - kinect
-- ~~  - detection
-- ~~  - swissranger_camera
-- ~~  - opt_calibration
-- ~~  - tracking
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin metapackage: 'calibration_toolkit'
-- ==> add_subdirectory(calibration_toolkit/calibration_toolkit)
-- +++ processing catkin package: 'freenect_launch'
-- ==> add_subdirectory(freenect_stack/freenect_launch)
-- +++ processing catkin package: 'freenect_stack'
-- ==> add_subdirectory(freenect_stack/freenect_stack)
-- +++ processing catkin metapackage: 'open_ptrack'
-- ==> add_subdirectory(open_ptrack/open_ptrack)
-- +++ processing catkin package: 'calibration_msgs'
-- ==> add_subdirectory(calibration_toolkit/calibration_msgs)
-- Using these message generators: gencpp;genlisp;genpy
-- calibration_msgs: 3 messages, 1 services
-- +++ processing catkin package: 'bayes'
-- ==> add_subdirectory(open_ptrack/bayes)
-- +++ processing catkin package: 'opt_msgs'
-- ==> add_subdirectory(open_ptrack/opt_msgs)
-- Using these message generators: gencpp;genlisp;genpy
-- opt_msgs: 12 messages, 2 services
-- +++ processing catkin package: 'opt_utils'
-- ==> add_subdirectory(open_ptrack/opt_utils)
-- Eigen found (include: /usr/include/eigen3)
-- +++ processing catkin package: 'freenect_camera'
-- ==> add_subdirectory(freenect_stack/freenect_camera)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   thread
-- +++ processing catkin package: 'calibration_common'
-- ==> add_subdirectory(calibration_toolkit/calibration_common)
-- Using these message generators: gencpp;genlisp;genpy
-- Boost version: 1.54.0
-- Eigen found (include: /usr/include/eigen3)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- looking for PCL_COMMON
-- looking for PCL_OCTREE
-- looking for PCL_IO
-- looking for PCL_KDTREE
-- looking for PCL_SEARCH
-- looking for PCL_SAMPLE_CONSENSUS
-- looking for PCL_FILTERS
-- looking for PCL_FEATURES
-- looking for PCL_KEYPOINTS
-- looking for PCL_GEOMETRY
-- looking for PCL_SEGMENTATION
-- looking for PCL_VISUALIZATION
-- looking for PCL_OUTOFCORE
-- looking for PCL_REGISTRATION
-- looking for PCL_RECOGNITION
-- looking for PCL_SURFACE
-- looking for PCL_PEOPLE
-- looking for PCL_TRACKING
-- looking for PCL_APPS
-- Found required Ceres dependency: Eigen version 3.2.0 in /usr/include/eigen3
-- Found required Ceres dependency: Glog in /usr/local/include
-- Found Ceres version: 1.9.0 installed in: /usr/local
-- +++ processing catkin package: 'kinect'
-- ==> add_subdirectory(calibration_toolkit/kinect)
-- Using these message generators: gencpp;genlisp;genpy
-- Boost version: 1.54.0
-- Eigen found (include: /usr/include/eigen3)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- looking for PCL_COMMON
-- looking for PCL_OCTREE
-- looking for PCL_IO
-- looking for PCL_KDTREE
-- looking for PCL_SEARCH
-- looking for PCL_SAMPLE_CONSENSUS
-- looking for PCL_FILTERS
-- looking for PCL_FEATURES
-- looking for PCL_KEYPOINTS
-- looking for PCL_GEOMETRY
-- looking for PCL_SEGMENTATION
-- looking for PCL_VISUALIZATION
-- looking for PCL_OUTOFCORE
-- looking for PCL_REGISTRATION
-- looking for PCL_RECOGNITION
-- looking for PCL_SURFACE
-- looking for PCL_PEOPLE
-- looking for PCL_TRACKING
-- looking for PCL_APPS
-- Found required Ceres dependency: Eigen version 3.2.0 in /usr/include/eigen3
-- Found required Ceres dependency: Glog in /usr/local/include
-- Found Ceres version: 1.9.0 installed in: /usr/local
-- +++ processing catkin package: 'detection'
-- ==> add_subdirectory(open_ptrack/detection)
-- Using these message generators: gencpp;genlisp;genpy
-- Eigen found (include: /usr/include/eigen3)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- looking for PCL_COMMON
-- looking for PCL_OCTREE
-- looking for PCL_IO
-- looking for PCL_KDTREE
-- looking for PCL_SEARCH
-- looking for PCL_SAMPLE_CONSENSUS
-- looking for PCL_FILTERS
-- looking for PCL_FEATURES
-- looking for PCL_KEYPOINTS
-- looking for PCL_GEOMETRY
-- looking for PCL_SEGMENTATION
-- looking for PCL_VISUALIZATION
-- looking for PCL_OUTOFCORE
-- looking for PCL_REGISTRATION
-- looking for PCL_RECOGNITION
-- looking for PCL_SURFACE
-- looking for PCL_PEOPLE
-- looking for PCL_TRACKING
-- looking for PCL_APPS
PCL_INCLUDE_DIRS
/usr/include/pcl-1.7;/usr/include/eigen3;/usr/include;/usr/include/ni;/usr/include/vtk-5.8
PCL_LIBRARY_DIRS
/usr/lib
PCL_DEFINITIONS
-DEIGEN_USE_NEW_STDVECTOR;-DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET;-DFLANN_STATIC;-Dqh_QHpointer
PCL_COMMON_LIBRARIES
/usr/lib/x86_64-linux-gnu/libboost_system.so;/usr/lib/x86_64-linux-gnu/libboost_filesystem.so;/usr/lib/x86_64-linux-gnu/libboost_thread.so;/usr/lib/x86_64-linux-gnu/libboost_date_time.so;/usr/lib/x86_64-linux-gnu/libboost_iostreams.so;/usr/lib/x86_64-linux-gnu/libboost_serialization.so;/usr/lib/x86_64-linux-gnu/libpthread.so;optimized;/usr/lib/libpcl_common.so;debug;/usr/lib/libpcl_common.so
-- +++ processing catkin package: 'swissranger_camera'
-- ==> add_subdirectory(open_ptrack/swissranger_camera)
-- Using these message generators: gencpp;genlisp;genpy
-- Eigen found (include: /usr/include/eigen3)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- looking for PCL_COMMON
-- looking for PCL_OCTREE
-- looking for PCL_IO
-- looking for PCL_KDTREE
-- looking for PCL_SEARCH
-- looking for PCL_SAMPLE_CONSENSUS
-- looking for PCL_FILTERS
-- looking for PCL_FEATURES
-- looking for PCL_KEYPOINTS
-- looking for PCL_GEOMETRY
-- looking for PCL_SEGMENTATION
-- looking for PCL_VISUALIZATION
-- looking for PCL_OUTOFCORE
-- looking for PCL_REGISTRATION
-- looking for PCL_RECOGNITION
-- looking for PCL_SURFACE
-- looking for PCL_PEOPLE
-- looking for PCL_TRACKING
-- looking for PCL_APPS
PCL_INCLUDE_DIRS
/usr/include/pcl-1.7;/usr/include/eigen3;/usr/include;/usr/include/ni;/usr/include/vtk-5.8
PCL_LIBRARY_DIRS
/usr/lib
PCL_DEFINITIONS
-DEIGEN_USE_NEW_STDVECTOR;-DEIGEN_YES_I_KNOW_SPARSE_MODULE_IS_NOT_STABLE_YET;-DFLANN_STATIC;-Dqh_QHpointer
PCL_COMMON_LIBRARIES
/usr/lib/x86_64-linux-gnu/libboost_system.so;/usr/lib/x86_64-linux-gnu/libboost_filesystem.so;/usr/lib/x86_64-linux-gnu/libboost_thread.so;/usr/lib/x86_64-linux-gnu/libboost_date_time.so;/usr/lib/x86_64-linux-gnu/libboost_iostreams.so;/usr/lib/x86_64-linux-gnu/libboost_serialization.so;/usr/lib/x86_64-linux-gnu/libpthread.so;optimized;/usr/lib/libpcl_common.so;debug;/usr/lib/libpcl_common.so
-- +++ processing catkin package: 'opt_calibration'
-- ==> add_subdirectory(open_ptrack/opt_calibration)
-- Using these message generators: gencpp;genlisp;genpy
-- Boost version: 1.54.0
-- Eigen found (include: /usr/include/eigen3)
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   iostreams
--   serialization
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- checking for module 'openni-dev'
--   package 'openni-dev' not found
-- looking for PCL_COMMON
-- looking for PCL_OCTREE
-- looking for PCL_IO
-- looking for PCL_KDTREE
-- looking for PCL_SEARCH
-- looking for PCL_SAMPLE_CONSENSUS
-- looking for PCL_FILTERS
-- looking for PCL_FEATURES
-- looking for PCL_KEYPOINTS
-- looking for PCL_GEOMETRY
-- looking for PCL_SEGMENTATION
-- looking for PCL_VISUALIZATION
-- looking for PCL_OUTOFCORE
-- looking for PCL_REGISTRATION
-- looking for PCL_RECOGNITION
-- looking for PCL_SURFACE
-- looking for PCL_PEOPLE
-- looking for PCL_TRACKING
-- looking for PCL_APPS
OpenMP FOUND
-- +++ processing catkin package: 'tracking'
-- ==> add_subdirectory(open_ptrack/tracking)
-- Using these message generators: gencpp;genlisp;genpy
-- Eigen found (include: /usr/include/eigen3)
-- Configuring done
-- Generating done
-- Build files have been written to: /home/deeplearning/workspace/ros/catkin/build

Running command: "make -j8 -l8" in "/home/deeplearning/workspace/ros/catkin/build"

[  0%] Built target std_msgs_generate_messages_cpp
[  0%] [  0%] Built target std_msgs_generate_messages_lisp
Built target std_msgs_generate_messages_py
[  9%] Built target bayes
[  9%] Built target geometry_msgs_generate_messages_py
[  9%] [  9%] [  9%] Built target _calibration_msgs_generate_messages_check_deps_CheckerboardArray
Built target _calibration_msgs_generate_messages_check_deps_CheckerboardMsg
Built target sensor_msgs_generate_messages_py
[  9%] Built target _calibration_msgs_generate_messages_check_deps_OmnicameraInfo
[  9%] Built target _calibration_msgs_generate_messages_check_deps_SetOmnicameraInfo
[  9%] Built target _opt_msgs_generate_messages_check_deps_TrackArray
[  9%] Built target _opt_msgs_generate_messages_check_deps_HumanEntries
[  9%] Built target _opt_msgs_generate_messages_check_deps_DetectionArray
[  9%] [  9%] [  9%] [  9%] Built target _opt_msgs_generate_messages_check_deps_CalibrationStatus
Built target _opt_msgs_generate_messages_check_deps_Detection
Built target _opt_msgs_generate_messages_check_deps_BoundingBox2D
Built target opt_msgs_generate_messages_check_deps_RoiRect
[  9%] Built target geometry_msgs_generate_messages_cpp
[  9%] Built target opt_msgs_generate_messages_check_deps_OPTTransform
[  9%] Built target opt_msgs_generate_messages_check_deps_Rois
[  9%] Built target sensor_msgs_generate_messages_cpp
[  9%] [  9%] Built target sensor_msgs_generate_messages_lisp
[  9%] [  9%] Built target opt_msgs_generate_messages_check_deps_HumanEntry
Built target opt_msgs_generate_messages_check_deps_Track
Built target geometry_msgs_generate_messages_lisp
[  9%] [  9%] Built target opt_msgs_generate_messages_check_deps_OPTSensor
Built target opt_msgs_generate_messages_check_deps_BoundingBox3D
[ 10%] Built target roi_msgs
[ 11%] [ 11%] [ 12%] [ 15%] Built target freenect_camera_gencfg
Built target json
Built target opt_msgs_generate_messages_check_deps_IDArray
Built target udp_listener
[ 15%] Built target opt_utils
[ 16%] [ 18%] Generating dynamic reconfigure files from cfg/SwissRanger.cfg: /home/deeplearning/workspace/ros/catkin/devel/include/swissranger_camera/SwissRangerConfig.h /home/deeplearning/workspace/ros/catkin/devel/lib/python2.7/dist-packages/swissranger_camera/cfg/SwissRangerConfig.py
Built target tracking_gencfg
[ 19%] Built target detection_gencfg
[ 22%] [ 27%] Built target calibration_algorithms
Built target calibration_msgs_generate_messages_py
[ 29%] [ 32%] Built target swissranger_utility
Built target calibration_msgs_generate_messages_cpp
[ 36%] Built target calibration_common
[ 39%] [ 51%] [ 65%] [ 77%] Built target opt_msgs_generate_messages_cpp
Built target opt_msgs_generate_messages_py
Built target calibration_msgs_generate_messages_lisp
Built target opt_msgs_generate_messages_lisp
[ 78%] Built target ros2udp_converter
[ 78%] [ 79%] [ 79%] Building CXX object freenect_stack/freenect_camera/CMakeFiles/freenect_nodelet.dir/src/nodelets/driver.cpp.o
Built target calibration_msgs_generate_messages
Built target roi_viewer
[ 80%] [ 80%] [ 80%] Built target freenect_node
[ 81%] Built target opt_msgs_generate_messages
[ 83%] Built target detection
Building CXX object open_ptrack/detection/CMakeFiles/haar_disp_ada.dir/apps/haardispada_nodelet.cpp.o
Building CXX object open_ptrack/detection/CMakeFiles/haar_disp_ada.dir/src/haardispada.cpp.o
[ 84%] [ 86%] Built target ground_based_people_detector
Built target ground_based_people_detector_sr
[ 87%] Built target opt_calibration_refinement
[ 88%] Built target stereo_publisher
[ 91%] Built target opt_calibration
[ 94%] Built target tracking
[ 97%] Built target opt_define_reference_frame
[ 98%] Built target moving_average_filter
[ 98%] Built target tracker
Generating reconfiguration files for SwissRanger in swissranger_camera
[ 98%] Built target swissranger_camera_gencfg
In file included from /home/deeplearning/workspace/ros/catkin/src/freenect_stack/freenect_camera/include/freenect_camera/freenect_driver.hpp:5:0,
from /home/deeplearning/workspace/ros/catkin/src/freenect_stack/freenect_camera/src/nodelets/driver.h:54,
from /home/deeplearning/workspace/ros/catkin/src/freenect_stack/freenect_camera/src/nodelets/driver.cpp:39:
/home/deeplearning/workspace/ros/catkin/src/freenect_stack/freenect_camera/include/freenect_camera/freenect_device.hpp:11:50: fatal error: libfreenect/libfreenect_registration.h: No such file or directory
compilation terminated.
In file included from /home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:31:0:
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/include/open_ptrack/detection/haardispada.h:63:16: error: 'cv::INTER_AREA' has not been declared
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/include/open_ptrack/detection/haardispada.h:104:9: error: 'CvBoost' does not name a type
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'void open_ptrack::detection::HaarDispAdaClassifier::detect(std::vector<cv::Rect >&, std::vector&, cv::Mat&, std::vector<cv::Rect >&, std::vector&, bool)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:83:22: error: 'HDAC' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'void open_ptrack::detection::HaarDispAdaClassifier::detect(std::vector<cv::Rect >&, std::vector&, cv::Mat&, std::vector<cv::Rect >&, std::vector&, std::vector&, bool)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:123:22: error: 'HDAC' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'void open_ptrack::detection::HaarDispAdaClassifier::train(std::string)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:191:7: error: 'CvBoostParams' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:191:21: error: expected ';' before 'bparams'
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:193:7: error: 'bparams' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:212:44: error: 'CV_VAR_ORDERED' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:214:7: error: 'HDAC' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:214:29: error: 'CV_ROW_SAMPLE' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'void open_ptrack::detection::HaarDispAdaClassifier::load(std::string)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:283:7: error: 'HDAC' was not declared in this scope
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'int open_ptrack::detection::HaarDispAdaClassifier::haar_features_fast(cv::Mat&)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:415:7: error: 'resize' is not a member of 'cv'
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:416:7: error: 'resize' is not a member of 'cv'
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp: In member function 'int open_ptrack::detection::HaarDispAdaClassifier::haar_features(cv::Mat&, cv::Mat&)':
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/src/haardispada.cpp:470:90: error: 'resize' was not declared in this scope
make[2]: *** [open_ptrack/detection/CMakeFiles/haar_disp_ada.dir/src/haardispada.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/apps/haardispada_nodelet.cpp:40:0:
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/include/open_ptrack/detection/haardispada.h:63:16: error: 'cv::INTER_AREA' has not been declared
/home/deeplearning/workspace/ros/catkin/src/open_ptrack/detection/include/open_ptrack/detection/haardispada.h:104:9: error: 'CvBoost' does not name a type
make[2]: *** [freenect_stack/freenect_camera/CMakeFiles/freenect_nodelet.dir/src/nodelets/driver.cpp.o] Error 1
make[1]: *** [freenect_stack/freenect_camera/CMakeFiles/freenect_nodelet.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [open_ptrack/detection/CMakeFiles/haar_disp_ada.dir/apps/haardispada_nodelet.cpp.o] Error 1
make[1]: *** [open_ptrack/detection/CMakeFiles/haar_disp_ada.dir/all] Error 2
make: *** [all] Error 2
Invoking "make -j8 -l8" failed
Error: There already is a workspace config file .rosinstall at "/home/deeplearning/workspace/ros/rosbuild". Use rosws install/modify.

this log is very system specific, hard to debug. Please verify you're running on supported hardware, and following installation instructions explicitly. If you still have errors, please make a new issue.


Image inference results into json, but generate strange code in "counts"

Dear all,
I am using box-level segmentation inference on image ,The model was trained on coco format dataset.I followed the instructions of python ./tools/test.py configs/cascade_rcnn/cascade_rcnn_r50_fpn_1x_coco.py ./work_dirs/epoch_2.pth --format-only --options "jsonfile_prefix=./results" to generate test file in json.But the result json file generate strange code in "counts",how can I solve this problem? Thanks

@TaoshuaiZ You can use cocoapi to decode the rle format


Fix #392 - Added two new props to textarea (width and height)

This is to fix #392 , where the problem is if you set a class to <vs-textarea> today to change the height, only the <div> changes it's height, and it should also change the textarea's height.
So, to fix this and prevent the same problem from happen with the width, I added two new props to textarea, that adds an width/height style (both optional) to the <div> and the <textarea> inside of it.
Demo:

@sneko No you are not the only one seeing it, I also have the same issue.