Keep track of "f-contiguous" status

f-contiguous can be reshaped into other f-order arrays.

#40 runs into some interesting problems — we can represent f-order matrices well as rblas-compatible views, having the right RowMajor/ ColMajor order defined, but rblas operations don't take an ordering per matrix, but rather per operation. All matrices in the same operation need the same ordering, so we can't enforce correctness in our wrapper type scheme.

This is #63


elan does not start, complaining about error: couldn't find value of ELAN_HOME

I have built elan  3.0.0 using cargo, according to the AUR's script: https://aur.archlinux.org/packages/elan-lean
I had to update the version.
Now, the command elan , or elan --help produces the following output:
error: couldn't find value of ELAN_HOME
info: caused by: No such file or directory (os error 2)

Would it be possible to make the error more verbose, or, just make it work by default?

This might be hard to do anything about if we can't reproduce. What exactly do you mean by "I had to update the version"?


DirectView doesn't allow u:view attr

Long story short: DirectView does not allow the abbreviated u:view attribute, only unicorn:view. To be consistent, this should be allowed IMHO...
https://github.com/adamghill/django-unicorn/blob/127add9040706db9c8ff21d3084ee5f3089963b6/django_unicorn/components/unicorn_template_response.py#L210

Thanks for the PR. Any chance you can add a test for this as well? Otherwise, I will!

Sorry, I'm tied up with work ATM..., and don't have Unicorn's testing framework at hand... war just a quick idea, even low prio...


Rename UnitQuaternion to QuatRotation and fixes

Codecov Report

Merging #65 (1a218ef) into master (8e6592d) will decrease coverage by 0.21%.
The diff coverage is 76.05%.

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
- Coverage   71.86%   71.65%   -0.22%
==========================================
  Files          41       40       -1
  Lines        3586     3605      +19
==========================================
+ Hits         2577     2583       +6
- Misses       1009     1022      +13

Impacted Files
Coverage Δ

src/bounds/impact.jl
58.33% <ø> (ø)

src/discretization/quadratic/integrator.jl
0.00% <0.00%> (ø)

src/main_components/mechanism_struct.jl
90.19% <ø> (ø)

src/optional_components/shapes.jl
77.77% <ø> (ø)

src/solver/initconstraints.jl
0.00% <0.00%> (ø)

src/solver/system.jl
92.12% <0.00%> (ø)

src/joints/rotational.jl
65.47% <65.21%> (ø)

src/util/quaternion.jl
80.00% <68.29%> (-16.37%)
:arrow_down:

src/joints/translational.jl
69.68% <75.00%> (ø)

src/ui/urdf.jl
65.00% <75.00%> (ø)

... and 11 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 cdb7492...1a218ef. Read the comment docs.


Use explicit path to phpcs.

Makes sure that we use the local install of phpcs, which should also
ensure that we use the local installed copy of the standards.
Fixes #11.

@leewillis77 thanks for the pull request. I'm trying out a "put new releases into a release/{version} branch" workflow from 0.4.0 onwards (to make sure the changelog is getting updated regularly and people are getting their props), so I'm closing the PR as your branch has been merged into release/0.4.0.


consider dropping python 3.7 support

see https://github.com/ApeWorX/evm-trace/issues/11 for the rationale

Agreed, 3.7 is Ubuntu 19.04's version, and it is missing quite a bit of support for many packages.

We will be able to upgrade ipython to the 8.0 range once we do this

Plan 3.7 deprecation for v0.5.0?

Done


Setting up SSL with this module fails out of the box with keystore-related errors

Module version: elastic-elasticsearch (v6.3.3)
Puppet version: 4.10.12
OS and version: CentOS Linux release 7.5.1804

Bug description
The module fails to install SSL out of the box.
A minimal example:
include java

class { 'elasticsearch':
  version         => '6.6.0',
  license         => file('license.json'),
  security_plugin => 'x-pack',
}
elasticsearch::instance { $hostname:
  ssl               => true,
  certificate       => 'elasticsearch.crt',
  private_key       => 'elasticsearch.key',
  keystore_password => '123456',
}

Save the above as "test.pp" and run it with puppet apply test.pp. This results in the following error:
Notice: /Stage[main]/Main/Elasticsearch::Instance[es-2-dev]/File[/etc/elasticsearch/es-2-dev/x-pack]/ensure: created
Error: Execution of 'keytool -importcert -noprompt -alias elasticsearch_instance_es-2-dev_keystore_ca -file  -keystore /etc/elasticsearch/es-2-dev/x-pack/es-2-dev.ks -trustcacerts' returned 1: Enter keystore password:  Re-enter new password: keytool error: java.io.FileNotFoundException:  (No such file or directory)
Error: /Stage[main]/Main/Elasticsearch::Instance[es-2-dev]/Java_ks[elasticsearch_instance_es-2-dev_keystore_ca]/ensure: change from absent to latest failed: Execution of 'keytool -importcert -noprompt -alias elasticsearch_instance_es-2-dev_keystore_ca -file  -keystore /etc/elasticsearch/es-2-dev/x-pack/es-2-dev.ks -trustcacerts' returned 1: Enter keystore password:  Re-enter new password: keytool error: java.io.FileNotFoundException:  (No such file or directory)
Notice: /Stage[main]/Main/Elasticsearch::Instance[es-2-dev]/Java_ks[elasticsearch_instance_es-2-dev_keystore_node]/ensure: created

Any tips?

More info:
For kicks, I tried upgrading to the latest version of Puppet, 6.2.0. I still get the exact same error, so that is unlikely to be related.

I believe the reason for the error is elasticsearch::ca_certificate isn't defined.
The resource you're failing on is:
 java_ks { "elasticsearch_instance_${name}_keystore_ca":
  ensure       => 'latest',
  certificate  => $ca_certificate,
  target       => $_keystore_path,
  password     => $keystore_password,
  trustcacerts => true,
}

$ca_certificate isn't defined in elasticsearch::instance so it fails with No such file or directory
There is a fail resource if keystore password isn't defined but nothing for certificate, ca_certificate or private_key.


Create Clap component and use gun.js database

In this update, mo.js is used for motion graphics, and gun.js is used for database.
https://codepen.io/ohansemmanuel/pen/zEJpYy


Fix imported models

We were only exporting data that was actually referenced in the model to Stan.  This causes a problem with imported models since we don't know which values are referenced.  So this makes it so we export everything that was specified (which is the way it used to work at some point).  This also adds an integration test to make sure we can run imported models.
Note that the check that used to be performed to ensure we output everything the program referenced still exists in CompiledModel.run (the check here was a duplicate).

This fix is in response to this post: http://discourse.mc-stan.org/t/scalastan-with-existing-stan-models/4634


Insert client's created body text on the site

[x] Get texts from OneDrive and insert in the assigned places on the page.
[x] Rolesurvey page texts
[x] Fact quiz page texts

rolesurvey updated, updated cypress tests

Adding to this that client's body text has been added to front page as part of #453

Role Survey page texts added in https://github.com/Ilmastokompassi/Ilmastokompassi/pull/484
Fact quiz page texts added in https://github.com/Ilmastokompassi/Ilmastokompassi/pull/493


Remove http scheme from Datalake storage

In DataLake Storage Swagger, two schemes are mentioned: http and https.  Because of this Autorest(V2) ignores the https and uses only http. The default auth mechanism used in our SDK is the Token Credentials which uses only https scheme. So, the requests are failing in our SDKs(irrespective of the language). So, this PR has been created to remove the http scheme

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@sarangan12 Hello. Does Autorest(v2) depend on the order to choose the https or http? @junhuagu I don't know the context for this. Could you please review this PR?


I.seeInField is not asserting value

I am trying to use I.seeInField to check the value of an input element, however regardless of what the value argument is, the assertion passes as long as the selector is valid.
I.seeInField('#supplierName', 'this can be anything')

Thanks. I wil work to get it fixed and tested propely )


Optimisation assertion error for Pydantic library

Hi, I'm getting the following assertion error around optimizer while compiling a project that uses Pydantic
The System
MacOS Catalina
Python 3.7.6 (default, Jan  6 2020, 14:21:53) [Clang 7.1.0 (tags/RELEASE_710/final)] on darwin

Nuitka build:
0.6.7
Python: 3.7.6 (default, Jan  6 2020, 14:21:53)
Executable: /Users/project/.venv/bin/python
OS: Darwin
Arch: x86_64

The environment with Python is created by the following Nix shell:
with (import (builtins.fetchGit {
    # https://nixos.wiki/wiki/FAQ/Pinning_Nixpkgs
    name = "nuitka-python37";
    url = https://github.com/nixos/nixpkgs/;
    ref = "refs/heads/master";
    rev = "6f545410b593a0d1b78806aa878f95ee3f3d4a4a";
}) {});

mkShell {
    name = "nuitka-python37-python37";
    buildInputs = [
        # see https://nixos.org/nixos/packages.html
        # Python distribution
        python37Full
        python37Packages.virtualenv
        poetry
        # usually required as python runtime dependencies
        ncurses
        libxml2
        libxslt
        libzip
        zlib
        # root CA certificates
        cacert
        gnumake
        which
    ];
    shellHook = ''
        # Set SOURCE_DATE_EPOCH so that we can use python wheels.
        # This compromises immutability, but is what we need
        # to allow package installs from PyPI
        export SOURCE_DATE_EPOCH=$(date +%s)

        VENV_DIR=$PWD/.venv

        export PATH=$VENV_DIR/bin:$PATH
        export PYTHONPATH=""
        export LANG=en_US.UTF-8

        # https://python-poetry.org/docs/configuration/
        export POETRY_VIRTUALENVS_CREATE=true
        export POETRY_VIRTUALENVS_IN_PROJECT=true
        export PIP_CACHE_DIR=$PWD/.local/pip-cache

        # Setup virtualenv
        if [ ! -d $VENV_DIR ]; then
            virtualenv $VENV_DIR
        fi

        # Dirty fix for Linux systems
        # https://nixos.wiki/wiki/Packaging/Quirks_and_Caveats
        export LD_LIBRARY_PATH=${stdenv.cc.cc.lib}/lib/:$LD_LIBRARY_PATH
    '';
}

The traceback is:
Nuitka:INFO:Optimizing module 'pydantic', 13 more modules to go after that.
Nuitka:INFO:Doing module local optimizations for 'pydantic'.
Traceback (most recent call last):
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/__main__.py", line 182, in <module>
    main()
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/__main__.py", line 175, in main
    MainControl.main()
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/MainControl.py", line 736, in main
    main_module = createNodeTree(filename=filename)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/MainControl.py", line 142, in createNodeTree
    Optimization.optimize(main_module.getOutputFilename())
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/optimizations/Optimization.py", line 619, in optimize
    finished = makeOptimizationPass(initial_pass=False)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/optimizations/Optimization.py", line 530, in makeOptimizationPass
    changed = optimizeModule(current_module)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/optimizations/Optimization.py", line 168, in optimizeModule
    changed = optimizeCompiledPythonModule(module)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/optimizations/Optimization.py", line 127, in optimizeCompiledPythonModule
    Plugins.considerImplicitImports(module=module, signal_change=signalChange)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/plugins/Plugins.py", line 141, in considerImplicitImports
    plugin.considerImplicitImports(module, signal_change)
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/plugins/PluginBase.py", line 207, in considerImplicitImports
    signal_change=signal_change,
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/plugins/PluginBase.py", line 498, in recurseTo
    reason=reason,
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/importing/Recursion.py", line 167, in recurseTo
    reason=reason,
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/importing/Recursion.py", line 83, in _recurseTo
    is_shlib=module_kind == "shlib",
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/tree/Building.py", line 924, in decideModuleTree
    source_ref=source_ref,
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/nodes/ModuleNodes.py", line 264, in __init__
    setLocalsDictType(self.module_dict_name, "module_dict")
  File "/Users/project/.venv/lib/python3.7/site-packages/nuitka/nodes/LocalsScopes.py", line 31, in setLocalsDictType
    assert locals_dict_name not in locals_dict_handles, locals_dict_name
AssertionError: globals_pydantic$__init__

The application:
import pydantic

if __name__ == "__main__":
    print('Hello world!')

Build script:
python -m nuitka --show-progress --follow-imports ./nuitka-app.py

I am getting the similar import error for these ones as in #689 and I think pydantic has worked before, so there must also be a regression in that.

So, my bisect has lead to me to the point, where I moved the assignment as the Nuitka meta path loader as responsible to sooner. Before it was FileFinder until being replaced.
Somebody has decided to compile all of pydantic into extension modules, which is why nothing is compiled except the top level package. The extension modules win over .py files in scan, so there is of course a question, wether to make an exception for these ones. I appreciate the pure Python source code being present.
In order to reproduce your problem, I will need to get that addressed, and to be compatible, the new loader is still the best idea, and not really a regression in that sense.

So, I am just pushing the solution for the non-compilation to factory, and when I re-compile everything it works, and I believe there are no possible changes since last release that may have caused a change for the optimization error you saw.
Can you give me the pydantic version from python -m pip freeze that you were using at the time, then I could try that one out.
However, with current factory, it soon ought to work.

Hi @kayhayen, thanks for looking at this. The pydantic version I tried was pydantic==1.4

So this one also is all extension modules on me now, too, leading to no compilation at all. With the ```--prefer-source-code`` option we are getting also no error anymore.
And now I recall it was a problem with imports not being understood properly, leading to some form of duplication and this was solved in #618 long time ago, and with 0.6.8 was released.


Docker deployment doesn't work

I faced two main issues while trying to run this project locally using docker compose during a workshop. The two issues where:

goof would fail to start complaining about not being able to connect to mysql at localhost
I wasn't able to create a new todo, it would fail with the following error: TypeError: Busboy is not a constructor

I have modified the Dockerfile not to run npm update anymore.

I have opened this https://github.com/snyk-labs/nodejs-goof/pull/1254 to fix both.

Can confirm, same for me:
goof        | failed connecting and seeding users to the MySQL database
goof        | Error: connect ECONNREFUSED <IP_ADDRESS>:3306
goof        |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1142:16)
goof        |     --------------------
goof        |     at Protocol._enqueue (/usr/src/goof/node_modules/mysql/lib/protocol/Protocol.js:144:48)
goof        |     at Protocol.handshake (/usr/src/goof/node_modules/mysql/lib/protocol/Protocol.js:51:23)
goof        |     at PoolConnection.connect (/usr/src/goof/node_modules/mysql/lib/Connection.js:116:18)
goof        |     at Pool.getConnection (/usr/src/goof/node_modules/mysql/lib/Pool.js:48:16)
goof        |     at /usr/src/goof/node_modules/typeorm/driver/mysql/MysqlDriver.js:903:18
goof        |     at new Promise (<anonymous>)
goof        |     at MysqlDriver.createPool (/usr/src/goof/node_modules/typeorm/driver/mysql/MysqlDriver.js:900:16)
goof        |     at MysqlDriver.<anonymous> (/usr/src/goof/node_modules/typeorm/driver/mysql/MysqlDriver.js:301:51)
goof        |     at step (/usr/src/goof/node_modules/tslib/tslib.js:144:27)
goof        |     at Object.next (/usr/src/goof/node_modules/tslib/tslib.js:125:57)
goof        |     at /usr/src/goof/node_modules/tslib/tslib.js:118:75
goof        |     at new Promise (<anonymous>)
goof        |     at __awaiter (/usr/src/goof/node_modules/tslib/tslib.js:114:16)
goof        |     at MysqlDriver.connect (/usr/src/goof/node_modules/typeorm/driver/mysql/MysqlDriver.js:286:38)
goof        |     at Connection.<anonymous> (/usr/src/goof/node_modules/typeorm/connection/Connection.js:112:58)
goof        |     at step (/usr/src/goof/node_modules/tslib/tslib.js:144:27) {
goof        |   errno: -111,
goof        |   code: 'ECONNREFUSED',
goof        |   syscall: 'connect',
goof        |   address: '<IP_ADDRESS>',
goof        |   port: 3306,
goof        |   fatal: true
goof        | }

Wondering why there is a dependency on Mysql in the first place if the project uses Mongo (only)? Or is there also a particular Mysql vuln do exploit?


Update base when dependency is merged

If a pull request has a base that is the branch of a dependency pull request, then watch for that dependency to be merged, and update the dependent's base branch to be the branch that the dependency pull request was merged into.
This would effectively allow for pull request chaining, mentioned at isaacs/github#867. Because the dependent pull request would be made as if it were to the dependency, the diff will be clean.
Because pull requests can only have a base on the same repository / fork as the pull request is on, this inherently requires that pull request chains be all on the same repository (except for the leaf, though that's small consolation).

Hi @ryanhiebert, thank you for opening this :sparkles:
Honestly, I had no idea how pull requests chaining, but it sounds interesting to me. I will need some time to figure how things work, then I may give it a shot (if somebody didn't take it already)
Suggestions from anybody are welcome!

I was trying to figure it out yesterday, but I haven't been able to get my local clone to even notice the dependencies correctly. Do you have any tips on that? If I can get the current project working, I want PR chaining bad enough that I'm willing to write it.

What exactly the issue?
P.S. I'm also available on gitter (username: ahmed-taj , you can reach out there at anytime :)

AFA what it takes, I think it's just a call to the UPDATE pull request API to change the base to the base that the dependancy pull request was merged into: https://developer.github.com/v3/pulls/#update-a-pull-request.

Would it be better if, instead of being based on explicitly declared dependencies, that it were instead based on just the branches? That way, for this feature, the dependency stuff wouldn't even be needed. It could arguably be made into a separate app entirely, since they would be disjoint features.

I don't think it would be wise to base it on branches of pull requests alone. I can imagine a git flow-like situation where you have a development branch that you merge to master on a schedule. If you do that with pull requests you certainly wouldn't want pull requests that are based on your develop branch being automatically being changed to merge into your master branch.
So, using the explicit dependencies still seems like the best idea to me, and thus belongs in this app, I think.

This feature would probably be turned off by default (for compatibility with existing users) and that can be changed through e.g a configuration in .github/config.yml?

@ryanhiebert correct me if I'm wrong, AFAIK here is what needs to be done (Assuming PR chaining is enabled):

When a PR e.g. A has been (re)opened/edited on branch M (as a source branch), we need to look for other open PRs where the target branch is M and set A as a dependency, right?
When A has been merged into branch e.g T, then we need to look for all dependents and change their target branch to be T.
If A has been closed, then we change nothing!

Also, do you think it would be useful to write a comment per dependencies update? e.g: Listing the current dependencies and the cause of change (either user command or PR chaining)

When a PR e.g. A has been (re)opened/edited on branch M (as a source branch), we need to look for other open PRs where the target branch is M and set A as a dependency, right?
Also, do you think it would be useful to write a comment per dependencies update? e.g: Listing the current dependencies and the cause of change (either user command or PR chaining)

No, I don't think we should automatically determine any dependencies based on the branches, at least not for this feature. It could be useful as a separate feature, perhaps, but I think the trade-offs are ones that will need to be considered more fully later, and I'm actually skeptical that it's what we really want at all.
Here's what I want:

Create pull request A to merge branch a  into master.
Create a chained pull request B to merge branch b into a. Use the normal slash command to set A as a dependency of B.
When A is merged, notice that (1) B is a dependent of A, (2) B has a base of the branch that B just merged into master, so (3) set the base of B to be master.

Oh, OK that makes sense, thanks for the explanation 😄

I can imagine there being a case where someone wanted to have a pull request depend on another pull request, but did not want the chaining to happen. For example, consider a git-flow workflow:

Create a pull request to merge develop into master. This might happen periodically to make a release.
Create a second pull request based on develop, as most would be in git flow.
Add a dependency to PR 2 on PR 1, because you decide that you don't want to merge the second pull request into develop until after the first PR is merged. In this example, because you don't want this new feature to get into the release.
Merge PR 1, and be annoyed that it automatically changed the base branch of PR 2 to master, since that's not where you intended for it to go.

I'm not sure if this is an edge case to really worry about or not, but if it is, then the only solution I see is to  make the chaining declarations independent of the dependency declarations. If we're making it possible to depend without chaining, I don't see any reason why we'd want to enforce dependency when we are chaining, though I don't see a case where it would be a problem to do so in practice.
A possible approach would be to make another command, say /chain #7, that takes care of the chaining. I think that this likely makes sense as a decent approach. Since it's completely separated from the normal dependencies in this package, though, the argument that it should be a separate installable app resurfaces again.
What do you think, @ahmed-taj ? Should it re-use the dependencies specified already, despite the edge-case? If it should not, should I make this a separate GitHub app, to keep these features separated?

Well, I never used PRs chaining before or even thought about it when I started this app.

Should it re-use the dependencies specified already, despite the edge-case?

I'm not sure yet when do people need to use PRs chaining in the first place. So, if the chaining isn't something people do frequently in a predictable manner, I think your suggested approach (/chain command) could work well whether or not the case you mentioned is an edge-case.

should I make this a separate GitHub app, to keep these features separated?

AFAIK both features could work together perfectly well, but it really depends on how people actually use the features, PRs chaining especially.

I use PR chaining in all kinds of bad ways when I am working furiously to implement a bunch of new features, but the review is backlogged a bit, or I'm just delayed in getting things from the first PR fixed. It's a small case, I'll admit, but I do find it to be useful, and I think relatively intuitive once you come across the need.

So, @ryanhiebert do you think the additional command approach fits your needs?

Yes, it does. Given that the chaining feature at this point seems entirely disjoint from the primary feature of this app, though, do you think that it would be best to keep the feature in this app, or put it in a separate app so that people can decide which features they want to use? I guess I'm a bit inclined toward the latter.

do you think that it would be best to keep the feature in this app, or put it in a separate app so that people can decide which features they want to use? I guess I'm a bit inclined toward the latter.

You're better aware of the problem we are trying to solve, so, It's totally fine if you think it should be in a separated app, and I would still help you if you need anything!

Sounds good! I'll follow your lead and use the project as a way to create a couple of hopefully interesting blog posts ;-) I'm using your blog post to help me get started, so thanks for that. I'll be sure to follow up here with whatever I come up with.

Hey @ryanhiebert I built a silly package to fix #3 and I think you might find it useful.
It works similar to probot-commands in some ways, but it only useful if the command parameters are issue references. An example could be:
const commands = require('probot-issue-commands)

// Type `closes #1, and owner/repo#2`
commands(robot, /clos(es|ing)/, (context, issues) => {
	console.log(issues)
	// ['#1','owner/repo#2', ...]
})

So, I actually don't want to use that because

I found that the probot-commands only worked on comments, and didn't work with the PR description. It's possible that I was doing something wrong, but it seems like this package may fall prey to the same issue.
I only want it to consider references made in the pull request's description, not follow-up comments. This is because it mirrors the way that GitHub's issue keywords for closing works, and it also allows me to avoid storing issue metadata because I only need to check for those keywords when another pull request is closed (that has a matching head for this PRs base).

Yes, my package only meant to be working with issue (PR)  comments
https://github.com/ahmed-taj/probot-issue-commands/blob/29b0d114ad436800d80568dc333be6b2cf05ac5d/index.ts#L44

Yeah, I suspect that may not be the most desirable way to do it, and that it would be better to match issue keywords only in the description, which the issue comments seem to not even support, since no comment notification is sent when when the issue is opened with a description.

From reading through the thread it seems this wasn't solved. Should we reopen it to track this suggestion?

I created https://github.com/apps/chain (repo at https://github.com/ryanhiebert/probot-chain) that watches for closed PRs, and then goes through and updates related branches. That's been enough for what I wanted. Its running on a free dyno on Heroku right now, so if it gets too much usage we might have to pay for hosting or find another free host, but feel free to try it out!


Filling a form using JQuery fails validation

So I am in the process of attempting to use some simple code injection to populate a form and submit it, in most cases, I am able to have the textbox revalidate by firing the blur event, but in the case of a react form build on redux, it does not validate in the same manner.
I tried using the following code, but it does not work:
top.jQuery('input#last-name-\\[0\\]').val('Smith').attr('value','Smith').trigger('blur');
Is there an event that I should be firing instead of the input event?
The values are not detected as firing the click event on the submit fails validation, as though no data has been entered in the form.
I tried a number of triggers including keyup, keydown, keypress, focus, blur, and changed.
Please note that using default values are not an option, because I am injecting the form data into a website that is not my own.
This is the code that react is using to build the component:
function LastNameComponent(_ref) {
    var index = _ref.index,
        isFirstField = _ref.isFirstField,
        formatValue = _ref.formatValue;

    var minLength = 2;
    var maxLength = 80;
    return _react2.default.createElement(
        'div',
        { className: 'form--item span3' },
        _react2.default.createElement(
            'label',
            { className: 'search-label small field__icon_group' },
            _react2.default.createElement(
                'span',
                null,
                '*'
            ),
            'Last Name',
            _react2.default.createElement(_TextInput2.default, {
                id: "last-name-[" + index + "]",
                model: "searchParams.searches[" + index + "].fields.lastName",
                validators: { required: function required(value) {
                        return !value || value.length < minLength || value.length > maxLength;
                    } },
                formatValue: formatValue
            }),
            _react2.default.createElement(_ErrorMessage2.default, {
                model: "searchParams.searches[" + index + "].fields.lastName",
                messages: { required: "Please enter the member's Last Name" }
            })
        )
    );
}

In the past I was able to  use .trigger('blur') and .trigger('change') but neither work anymore.
Here is a use case: https://codesandbox.io/s/VOxrnZPYX
As you can see, it is populated by the data, but it is never fired (ie) The event that should fire to revalidate does not because it does not detect the texboxes being filled.

Working example: https://codesandbox.io/s/E9xxPjBYg
Refer to https://github.com/facebook/react/issues/3249

That works! Seems like IE support still is a bit bonkers, but that solves my issue for Chrome, which is fine.


discord rpc

Describe the feature
discord rpc integration, i am going to open a pr later today but wanted to open this so i dont forget
casper if you can look over discord rpc docs and maybe get some options in cad as i have no idea how to do any of that front end stuff, then ill get them from there
Additional Context
No response

I'm going to close this since it's not possible. I'm pretty sure you need to a proxy since Discord doesn't allow requests from third-party domains

However, feel free to still try it out.


Sync humble with rolling

Merge commit this PR instead of squash merge to keep 0.1.4 tag on humble too.
This will also keep main and humble in sync after we merge #39

Closing this. I think a better strategy would be to sync main with rolling and then cherry pick any changes we want to back port into humble followed by bumping version on humble


test failed with fuels-core-lib 0.18.0

I created a new project via forc new and update the fuel-core-lib to 0.18 in Cargo.toml as it suggested
test failed with this version

Hi!
Can you please give us:

Your Cargo.toml
Your Forc.toml
The output of:
forc --version

Hi! So I have indeed been able to repro with the following Cargo.toml (notice that it is fuels set to 0.18 and not fuel-core-lib):
[project]
name = "bimbam"
version = "0.1.0"
authors = ["xxxxx"]
edition = "2021"
license = "Apache-2.0"

[dependencies]
fuels = { version = "0.18", features = ["fuel-core-lib"] }
tokio = { version = "1.12", features = ["rt", "macros"] }

[[test]]
harness = true
name = "integration_tests"
path = "tests/harness.rs"

Then, running forc test fails. It does not fail when setting fuels=v0.17.

yeah. it fails when version is 0.18

The solution for you is simply, for the harness, to do:
use fuels::{prelude::*, tx::ContractId};

// Load abi from json
abigen!(MyContract, "out/debug/bimbam-abi.json");

async fn get_contract_instance() -> (mycontract_mod::MyContract, ContractId) {
    // Launch a local network and deploy the contract
    let wallet = launch_provider_and_get_wallet().await;

    let id = Contract::deploy(
        "./out/debug/bimbam.bin",
        &wallet,
        TxParameters::default(),
        StorageConfiguration::with_storage_path(Some(
            "./out/debug/bimbam-storage_slots.json".to_string(),
        )),
    )
    .await
    .unwrap();

    let instance = MyContractBuilder::new(id.to_string(), wallet).build();

    (instance, id)
}

#[tokio::test]
async fn can_get_contract_id() {
    let (_instance, _id) = get_contract_instance().await;

    // Now you have an instance of your contract you can use to test each function
}

The fix has to be done directly on the Sway repo (we're generating a wrong harness with forc new, will update when merged/released.


Effect properties should be callable

Currently you can only access effect parameters with the .param() syntax. You should be able to call them directly, as you can in Ae:
let highlightLine = thisComp.layer("control").effect("line to hilite")("Slider").value;

Looks like we should be able to fix this by adding an interface defintion (as well as the class) to add a call signature to Effect.
interface Effect {
	(effectName: string): Property<any>
}


[NEW]: Fake press release dupes media outlets into reporting that Walmart will begin accepting Litecoin

Date
2021-09-13
Description
Press release distributed via GlobeNewswire claimed Walmart was announcing a partnership with Litecoin to begin accepting the cryptocurrency as a payment method. The value of Litecoin spiked before tumbling after Walmart said the announcement was fake.
Links
https://mashable.com/article/litecoin-walmart-fake-news
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
Joseph
Personal link
https://github.com/VerifiedJoseph

Added, thank you!


Error when compiling aihwkit on mac: fail to find pybind11

Description
When I was trying to compile the aihwkit following the guide in Development setup on mac, an error occurred.
(analog) (base) MrFive@MrFive-Mac-mini build % mkdir build
(analog) (base) MrFive@MrFive-Mac-mini build % build
(analog) (base) MrFive@MrFive-Mac-mini build % cmake ..
(analog) (base) MrFive@MrFive-Mac-mini build % make
(analog) (base) MrFive@MrFive-Mac-mini build % cmake ..
-- OpenMP could not be found. Disabling OpenMP support.
-- The BLAS backend of choice:OpenBLAS
-- Found OpenBLAS libraries: ~/anaconda3/envs/analog/lib/libopenblas.dylib
-- Found OpenBLAS include: ~/anaconda3/envs/analog/include
CMake Error at cmake/dependencies.cmake:98 (find_package):
  Could not find a package configuration file provided by "pybind11" with any
  of the following names:

    pybind11Config.cmake
    pybind11-config.cmake

  Add the installation prefix of "pybind11" to CMAKE_PREFIX_PATH or set
  "pybind11_DIR" to a directory containing one of the above files.  If
  "pybind11" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  CMakeLists.txt:39 (include)

How to reproduce
I have installed all the required packages, by using
conda install scikit-build
brew install llvm
brew install libomp

brew install openblas
export LDFLAGS="-L/opt/homebrew/opt/openblas/lib"
export CPPFLAGS="-I/opt/homebrew/opt/openblas/include"

pip install cmake scikit-build torch pybind11
conda install openblas

pip install -r requirements.txt
pip install -r requirements-dev.txt
pip install -r requirements-examples.txt

Bug Pinpoint
Following the prompt, I pinpointed the bug. It happens on line 91 in file cmake/dependencies.cmake
# Find pybind11Config.cmake
execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "import pybind11; print(pybind11.get_cmake_dir())"
    OUTPUT_VARIABLE CUSTOM_PYTHON_PYBIND11_PATH
    OUTPUT_STRIP_TRAILING_WHITESPACE
    ERROR_QUIET)
set(pybind11_DIR ${CUSTOM_PYTHON_PYBIND11_PATH})

It seems that ${CUSTOM_PYTHON_PYBIND11_PATH} can not find the path correctly. Replacing it with the absolute path as follows, I compiled it successfully.,
set(pybind11_DIR ~/anaconda3/envs/analog/lib/python3.11/site-packages/pybind11/share/cmake/pybind11)
find_package(pybind11 REQUIRED CONFIG)

Therefore, I guess there is some bug in the cmake file.
Other information

Pytorch version: 3.11.5
Package version: 0.8.0
OS: macOS Ventura 13.5.2
Python version:3.11.5
Pip version: 23.2.1
Conda version (or N/A): No

Hi @Zhaoxian-Wu, maybe thanks tor raising the issue.
For the cmake code to work, you need to ensure that the python environment where pybind11 is installed is activated and accessible. You could test the command:  python -c import pybind11; print(pybind11.get_cmake_dir()) and see whether the path is correct. It works as expected for my environment.
However, maybe it has something to do with MAC OS? Do you get the correct path with that above command?

Thanks for your reply @maljoras.
I have tested the command and it returned the correct path
(analog) (base) MrFive@MrFive-Mac-mini 2023.09.05 analog % python -c "import pybind11; print(pybind11.get_cmake_dir())"
/Users/MrFive/anaconda3/envs/analog/lib/python3.11/site-packages/pybind11/share/cmake/pybind11

However, when running the cmake .. command, the same thing happens
(analog) (base) MrFive@MrFive-Mac-mini build % cmake ..
-- OpenMP could not be found. Disabling OpenMP support.
-- The BLAS backend of choice:OpenBLAS
-- Found OpenBLAS libraries: /Users/MrFive/anaconda3/envs/analog/lib/libopenblas.dylib
-- Found OpenBLAS include: /Users/MrFive/anaconda3/envs/analog/include
CMake Error at cmake/dependencies.cmake:105 (find_package):
  Could not find a package configuration file provided by "pybind11" with any
  of the following names:

    pybind11Config.cmake
    pybind11-config.cmake

  Add the installation prefix of "pybind11" to CMAKE_PREFIX_PATH or set
  "pybind11_DIR" to a directory containing one of the above files.  If
  "pybind11" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  CMakeLists.txt:39 (include)

I guess one possible reason is that I installed the pybind11 on the virtual environment analog. But when using cmake, the environment is not correctly activated. I'm afraid it happens only on mac os

Thanks, we will try to reproduce on a MAC OS.

Thanks for your attention @maljoras! If any help is needed, I'll be happy to do that.

Hi @Zhaoxian-Wu these are the steps to successfully install aihwkit on Mac. Note that I created a new conda env for this example. Feel free to skip this.
conda create -n test python=3.10 -y
conda activate test
conda install pytorch::pytorch torchvision torchaudio -c pytorch -y
git clone git@github.com:IBM/aihwkit.git ; cd aihwkit
pip install -r requirements.txt
conda install openblas -y
pip install mypy
pip install -e .

This installs it in editable mode. This way you can open aihwkit and nicely step through some code to better understand some things.
After the installation, make sure to add the src of the aihwkit to the PYTHONPATH. Open ~/.zshrc and append export PYTHONPATH=$HOME/aihwkit/src then do source ~/.zshrc ; cd ~.
Finally, try running a simple example:
python aihwkit/examples/01_simple_layer.py
If this runs, then it should work. Let me know how it goes.

Thanks for your instruction @jubueche ! The code runs extraordinarily smoothly. I can now compile it successfully. I appreciate your help. The only change is I replace
git clone git@github.com:IBM/aihwkit.git

with
git clone https://github.com/IBM/aihwkit.git

which is the default option of Github.

Besides, recently I would like to compile a CUDA version on Linux. Do you have any idea on how to modify the commands accordingly? How should I change the torch setting (torch>=1.9) in requirements.txt?

Hi,
the above steps are now
conda create -n test python=3.10 -y
conda activate test
<Install torch with your correct CUDA version>
git clone git@github.com:IBM/aihwkit.git ; cd aihwkit
pip install -r requirements.txt
conda install mkl mkl-include -y
pip install mypy

Then, when you have aihwkit in your home directory, put the following in a .sh file in your home directory and execute it:
export CXX=/usr/bin/g++
export CC=/usr/bin/gcc
export MKLROOT=$CONDA_PREFIX
export CMAKE_PREFIX_PATH=$CONDA_PREFIX/lib
export CUDA_VERSION=12.1
export CUDA_HOME=/usr/local/cuda-${CUDA_VERSION}
export CUDA_TOOLKIT_ROOT_DIR=${CUDA_HOME}
export CUDA_LIB_PATH=${CUDA_HOME}/lib
export CUDA_INCLUDE_DIRS=${CUDA_HOME}/include
export PATH=${CUDA_HOME}/bin:$COMPILER/bin:${PATH}
export CMAKE_ROOT=~/anaconda3/envs/aihwkit/lib/
cd ~/aihwkit
make build_inplace_cuda

Note that you might have to adapt the paths and the CUDA version. Make sure the paths are correct. This is important.
After the installation, make sure to add the src of the aihwkit to the PYTHONPATH. Open ~/.zshrc (or ~/.bashrc) and append export PYTHONPATH=$HOME/aihwkit/src then do source ~/.zshrc ; cd ~ (or bashrc).

Please let me know it it works so that I can close the issue. Note that we are working on making it easier to install using conda.

I tried it and it worked successfully! Thank you very much :D!
I modify three places of the .sh file:

(Line 8) export CUDA_LIB_PATH=${CUDA_HOME}/lib64: In my server, there is no ${CUDA_HOME}/lib but only ${CUDA_HOME}/lib64
(Line 10): The $COMPILER is an empty string in my server. But it seems the compiling process never uses it.
(Line 11): export CMAKE_ROOT=~/anaconda3/envs/test/lib/: The environment is test instead of aihwkit. I guess it's only a typo.

Please let me know it it works so that I can close the issue. Note that we are working on making it easier to install using conda.

Thanks for your time and effort on that matter! To be honest I always got confused by the endless errors appearing in the compiling process, especially when I tried to deal with all kinds of dependencies and install the CUDA version. I would be excited to see an official instruction in the future.

Hi,
Note that if you have CUDA 11.8 installed, using conda for the installation works fine. See this this issue.
You can then install it using conda install -c conda-forge aihwkit-gpu.


can not crop well in my video

Hi,
I run the project to test my own video, but it can not achieve the cropped video i wanted. The original video is simple scene that only one actress dance in front of the camera. However, in my cropped video, that person does not exist.
my video is in
https://drive.google.com/file/d/1DC1AyOyExcXXUGs1osmBRO6r8OcRz9eQ/view?usp=sharing
The running code
GLOG_logtostderr=1 bazel-bin/mediapipe/examples/desktop/autoflip/run_autoflip \ --calculator_graph_config_file=mediapipe/examples/desktop/autoflip/autoflip_graph.pbtxt \ --input_side_packets=input_video_path=/absolute/path/to/the/local/video/file,output_video_path=/absolute/path/to/save/the/output/video/file,aspect_ratio=9:16
thank you

Hi, thank you for filing this issue with us.  We agree that the autoflip result is not ideal on the video sample you provided.  We have internally done some testing and have discovered the low-quality result is due to a false positive face detection on your video.
We have updated the internal version of autoflip to use a new face detection model.  We hope to release this update next week that will improve the autoflip results on your video.  Thank you for your patients.

We are closing this issue as we see the above resolution answered your query. Thanks!


Accept GITTO_PORT as env var for port to listen on

could this be just PORT instead of GITTO_PORT?

could this be just PORT instead of GITTO_PORT?

I guess it is fine for now. We'll revisit again, if required. Merging it.


Command handling and version conflicts

The current command handling flow looks like this:

Load the aggregate
Call the model
Persist new events

When the last step fails due to an optimistic concurrency exception, an external policy can retry the operation because the domain models to retry blindly. However, the stream is loaded again, because the retry happens on the outside. Also, we need to read the stream to get new events that caused the conflict.
However, it's possible to react to the optimistic concurrency exception by reading the stream tail from the last known event version. For shorter streams, the difference would be marginal, but for streams longer than a hundred events it would presumably be faster as we'd only need the stream tail, which most probably only has one event that caused the concurrency exception.
A prerequisite for this would be that the aggregate object contains the list of original events in addition to the list of new events as it does today. Opening up the list of original events for access has other benefits that I would be describing here.
I guess that the optimistic concurrency retry needs to be optional as it's not always the desired default behaviour of the model. The question would be if it should be the default or not...

Basically, the list of original events is already there, added for a different purpose. So, I have more information than I even need.
Avoiding deserialization only helps in scenarios when the domain logic only uses the state for decision-making, and today it's possible to use original events for that purpose without folding events. It, of course, makes using things like Spyglass hard, as the state isn't there... I guess it's up to the developer to decide which way to go.
Btw, I just realised that #157 might be useful for this issue. But, as I plan to make caching optional, there must be something in place to work without caching too. I guess the code would be similar - there's an instance, but it's obsolete, and need new events to get up-to-date.

Regarding this version conflict, is there any plan to disable optimistic concurrency checking on a handler?
Some streams/aggregates wouldn't care if there are concurrency exceptions when persisting certain domain events. I noticed EventStoredDB supports this but I see Eventuous exposing it when appending events but not making the ExpectedStreamVersion configurable when using the fluent mechanism for both services with aggregate and services with state.


Update editable.css

Updated to fix the color issue of the in-line editing form. If color of text being edited is white, text comes through the form white, making it appear empty.
Issue explained with images here: https://github.com/stephenmcd/mezzanine/issues/1814
You can also test this issue on the demo site using the chrome dev tools.
I simply added an explicit color (#000) to the form text, ensuring consistency no matter what color the text being edited is.

Thanks


Remove unused variables

This adds the no-unused-vars linting rule to remove unused variables.

CI tests are failing. Looking into it.

Fixed.


newlog infra changes on EVE

commit for newlog infra changes
commit for vendor files in pkg/newlog
change LOGGING.md to modify some tuned numbers
run newlog scheme by default, cloud side code was already in

This is very exciting @naiming-zededa ! I'll give it a much more thorough review tomorrow, but for now just a few quick comments inline and one observation: it appears that some yetus golintci complaints are pretty legit. Do you want to take a look into that?

I'll work on that yetus, mostly not check return values, which I followed most usages in EVE.

@rvs @eriknordmark the three yetus errors on sync.Mutex, this is because I'm reuse the api like log.LogBundle so the device and cloud side don't have to redefine them for the newlog. When the api generated the go functions and structures, it probably has the sync in them. But i'm here doing the json.Marshal() for the structure to format the string output of json, we don't use the sync here for any purpose. they can be ignored

Design question: aren't dnsmasq, dhcpcd, radvd etc sending their log messages to the syslog UDP port on localhost? Or how does newlogd pick them up?

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current log pipeline.

Design question: aren't dnsmasq, dhcpcd, radvd etc sending their log messages to the syslog UDP port on localhost? Or how does newlogd pick them up?

@eriknordmark -- at this point we don't have any freestanding daemons left -- everything gets plumbed through individual containers->containerd->memlogd

I have tried this newlogd image on Dell 3003 device and running for 15 hours, the memory condition is no worse than the normal image.

I have tried this newlogd image on Dell 3003 device and running for 15 hours, the memory condition is no worse than the normal image.

Great @naiming-zededa -- thanks for checking this. In that case, let me do one more pass through this on Wed and I think it can be merged (@eriknordmark -- anything else aside from the feedback you already provided)?

Hey @naiming-zededa -- looks like Eden tests are failing on this one -- this will have to be investigated

Hey @naiming-zededa -- looks like Eden tests are failing on this one -- this will have to be investigated

@rvs the ouput is below, is it possible that the eden is expect the log which will not get in this newlog? (since the api has changed)
=== RUN   TestLog
lim_test.go:143: Wait for log of default number=1 timewait=600
testContext.go:252: WaitForProc terminated by timeout 10m0s
--- FAIL: TestLog (600.00s)
FAIL
[exit status 1]

I think that's exactly the issue @naiming-zededa -- lets fix that before this can be merged.

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current logging pipeline. The syslog UDP port is between rsyslogd -> logmanager, as a way for logmanager to be the 'server' of this rsyslog.

I don't think so. @gkodali-zededa don't we depend on rsyslogd listening on the syslog UDP port?
@naiming-zededa you should see some dnsmasq logs in the backend. Do you see those with newlog?

all those i think handled from contain

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current logging pipeline. The syslog UDP port is between rsyslogd -> logmanager, as a way for logmanager to be the 'server' of this rsyslog.

I don't think so. @gkodali-zededa don't we depend on rsyslogd listening on the syslog UDP port?
@naiming-zededa you should see some dnsmasq logs in the backend. Do you see those with newlog?

Yes, newlog will have to read from unix socket for logs from dnsmasq, dhcpcd etc.
module(load="imuxsock" SysSock.Name="/dev/log")
This is what rsyslogd does.

all those i think handled from contain

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current logging pipeline. The syslog UDP port is between rsyslogd -> logmanager, as a way for logmanager to be the 'server' of this rsyslog.

I don't think so. @gkodali-zededa don't we depend on rsyslogd listening on the syslog UDP port?
@naiming-zededa you should see some dnsmasq logs in the backend. Do you see those with newlog?

Yes, newlog will have to read from unix socket for logs from dnsmasq, dhcpcd etc.
module(load="imuxsock" SysSock.Name="/dev/log")
This is what rsyslogd does.

@gkodali-zededa ok, this 'newlogd' used to have read from the /dev/log, but i monitored that and didn't see anything, I thought it was not needed. I'll put it back.

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current logging pipeline. The syslog UDP port is between rsyslogd -> logmanager, as a way for logmanager to be the 'server' of this rsyslog.

I don't think so. @gkodali-zededa don't we depend on rsyslogd listening on the syslog UDP port?
@naiming-zededa you should see some dnsmasq logs in the backend. Do you see those with newlog?

let me recheck on this., the rsyslogd did have a "/dev/log" in configure, I didn't see things from that channel and i removed that. I'll put it back to see then.

@naiming-zededa I can see in Adam, that there is no devID inside Comment of gzip:
2020/11/30 08:50:00 {"image":"IMGA","eveVersion":"0.0.0-naiming-newlog-infra-f5db03d6-kvm-amd64"}
2020/11/30 08:50:00 Failed to write logbundle message: unable to retrieve valid device UUID from message as : uuid: incorrect UUID length:

Is it expected behavior? Should I calculate devID from the certificate of request?

@naiming-zededa I can see in Adam, that there is no devID inside Comment of gzip:
2020/11/30 08:50:00 {"image":"IMGA","eveVersion":"0.0.0-naiming-newlog-infra-f5db03d6-kvm-amd64"}
2020/11/30 08:50:00 Failed to write logbundle message: unable to retrieve valid device UUID from message as : uuid: incorrect UUID length:

Is it expected behavior? Should I calculate devID from the certificate of request?

@giggsoff No, this is not expected behavior, it should be there.

all those i think handled from containerd which takes the stdout/stderr and converting them into memlogd input. this is the same for current logging pipeline. The syslog UDP port is between rsyslogd -> logmanager, as a way for logmanager to be the 'server' of this rsyslog.

I don't think so. @gkodali-zededa don't we depend on rsyslogd listening on the syslog UDP port?
@naiming-zededa you should see some dnsmasq logs in the backend. Do you see those with newlog?

let me recheck on this., the rsyslogd did have a "/dev/log" in configure, I didn't see things from that channel and i removed that. I'll put it back to see then.

@eriknordmark good catch on this. the system's syslog socket is defined as "/dev/log", somehow I had the code but didn't see anything came out, thus I removed this code thinking everything is now into memlogd. added in this commit. I do see 'dnsmasq' and 'dncpcd' log outputs in this socket.

@eriknordmark good catch on this. the system's syslog socket is defined as "/dev/log", somehow I had the code but didn't see anything came out, thus I removed this code thinking everything is now into memlogd. added in this commit. I do see 'dnsmasq' and 'dncpcd' log outputs in this socket.

Well, actually.... ;-) @naiming-zededa could we use this as an opportunity to streamline that part of logging as well? I mean there's no reason anything should be using syslog-style logging (also /dev/log) since it creates all these additional dataflows in the system that we would then have to control.
I mean -- reading out of that socket is not a big deal (and the right thing to do for now) but should we also commit to a bigger story around streamlining then?

@eriknordmark good catch on this. the system's syslog socket is defined as "/dev/log", somehow I had the code but didn't see anything came out, thus I removed this code thinking everything is now into memlogd. added in this commit. I do see 'dnsmasq' and 'dncpcd' log outputs in this socket.

Well, actually.... ;-) @naiming-zededa could we use this as an opportunity to streamline that part of logging as well? I mean there's no reason anything should be using syslog-style logging (also /dev/log) since it creates all these additional dataflows in the system that we would then have to control.
I mean -- reading out of that socket is not a big deal (and the right thing to do for now) but should we also commit to a bigger story around streamlining then?

Roman maybe this steamlining can happen together with your kernel based logging system :-)

Roman maybe this steamlining can happen together with your kernel based logging system :-)

I'd be +1 to that -- for sure! Just curious as to what @naiming-zededa thinks of doing the streamlining vs. leaving everything as is.

Roman maybe this steamlining can happen together with your kernel based logging system :-)

I'd be +1 to that -- for sure! Just curious as to what @naiming-zededa thinks of doing the streamlining vs. leaving everything as is.

I suspect those daemons don't offer command line options to switch the logging to different places, so we need to have someone reading this socket from, then use newlogd to read this socket is also fine.

I suspect those daemons don't offer command line options to switch the logging to different places

actually IIRC at least dnsmasq and dncpcd do have that option out of the box. The bigger question is that IF (to @eriknordmark point) we ever want this in-kernel memlogd replacement to happen (hopefully this year) we will need to route everything into that location anyway.
Choices are: handle it now (not as part of this PR of course) or handle it later (when we do in-kernel memlogd equivalent).

@eriknordmark -- at this point we don't have any freestanding daemons left -- everything gets plumbed through individual containers->containerd->memlogd

@rvs are you sure dnsmasq, radvd and dhcpcd work that way?
It should be easy to check by booting a device with this PR and verifying that dnsmasq and dhcpcd log entries appear at the controller.

@giggsoff just committed, the config item is "newlog.allow.fastupload" boolean, if enabled, the log uploading should be similar the the original logging.

@giggsoff just committed, the config item is "newlog.allow.fastupload" boolean, if enabled, the log uploading should be similar the the original logging.

Awesome @naiming-zededa !
@giggsoff -- when do you think you can try this with Adam/Eden and see if this passes?

Hey @giggsoff with yours and @deitch PRs on the Adam side approved, any chance we can do our weekly release of Eden on Fri (tomorrow) that ties all of this together?
That way, when it comes to our Fri here I can hook it up to EVE's PR checks and make sure that this PR passes Eden and then can (finally!) be merged.

Actually, it is ready and I wait for the new tag of Adam: https://github.com/itmo-eve/eden/tree/newlogs (and some refactoring maybe).

Sad, but true: Eden indicates problems with reboot.
I test it with my own and what I see: after onboarding of my device (it works well), I connect to it via console and fire reboot now. And I see, that zedbox crashes after restarting of EVE:
55fa13b6-0e38-476a-8582-918f259a9442:~# cat /var/persist/log/reboot-stack.log
goroutine 1 [running]:
github.com/lf-edge/eve/pkg/pillar/agentlog.getStacks(0x0, 0x0, 0x0)
        /pillar/agentlog/agentlog.go:454 +0x78
github.com/lf-edge/eve/pkg/pillar/agentlog.printStack(0xc000390020, 0x7ffffdb38f53, 0xa, 0x2bcf)
        /pillar/agentlog/agentlog.go:212 +0x38
github.com/lf-edge/eve/pkg/pillar/agentlog.initImpl.func1()
        /pillar/agentlog/agentlog.go:636 +0x45
github.com/sirupsen/logrus.runHandler(0xc00044a120)
        /pillar/vendor/github.com/sirupsen/logrus/alt_exit.go:39 +0x49
github.com/sirupsen/logrus.runHandlers()
        /pillar/vendor/github.com/sirupsen/logrus/alt_exit.go:44 +0x4b
github.com/sirupsen/logrus.(*Logger).Exit(0xc0003e2000, 0x1)
        /pillar/vendor/github.com/sirupsen/logrus/logger.go:337 +0x25
github.com/sirupsen/logrus.(*Entry).Fatalf(0xc00026c8c0, 0xc000024160, 0xa4, 0x0, 0x0, 0x0)
        /pillar/vendor/github.com/sirupsen/logrus/entry.go:363 +0x7f
github.com/lf-edge/eve/pkg/pillar/base.(*LogObject).Fatalf(0xc000390020, 0xc000024160, 0xa4, 0x0, 0x0, 0x0)
        /pillar/base/log.go:115 +0x85
main.runService(0x7ffffdb38f53, 0xa, 0x19c6688, 0xc0003e2000, 0xc000390000, 0x1589501)
        /pillar/zedbox/zedbox.go:158 +0x47b
main.main()
        /pillar/zedbox/zedbox.go:125 +0x194

55fa13b6-0e38-476a-8582-918f259a9442:~# cat /var/persist/log/reboot-reason.log
Reboot from agent zedmanager[11215] in partition IMGA EVE version 0.0.0-naiming-newlog-infra-54d628b2-kvm-amd64 at 2020-12-04T11:35:39.756973879Z: fatal: agent zedmanager[11215]: publish(/var/run/zedbox/ServiceInitStatus.sock): exception while dialing socket. dial unixpacket /var/run/zedbox/ServiceInitStatus.sock: connect: connection refused

I will take a look.

@naiming-zededa seems, that we try to call Stop on nil
{"severity":"info","source":"pillar","content":"panic: runtime error: invalid memory address or nil pointer dereference\n","msgid":917,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x130ff3f]\n","msgid":918,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\n","msgid":919,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"goroutine 1120 [running]:\n","msgid":920,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"time.(*Timer).Stop(...)\n","msgid":921,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/usr/local/go/src/time/sleep.go:76\n","msgid":922,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/cmd/loguploader.handleGlobalConfigImp(0x1632900, 0xc0009b0c40, 0xc000c5b4ed, 0x6, 0x178d320, 0xc0003d1490)\n","msgid":923,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/cmd/loguploader/loguploader.go:434 +0x23f\n","msgid":924,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/cmd/loguploader.handleGlobalConfigCreate(0x1632900, 0xc0009b0c40, 0xc000c5b4ed, 0x6, 0x178d320, 0xc0003d1490)\n","msgid":925,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/cmd/loguploader/loguploader.go:410 +0x5d\n","msgid":926,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/pubsub.handleModify(0x187d360, 0xc000678000, 0xc000c5b4ed, 0x6, 0xc0004cb800, 0x156d, 0x176d)\n","msgid":927,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/pubsub/subscribe.go:244 +0x67d\n","msgid":928,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/pubsub.(*SubscriptionImpl).populate(0xc000678000)\n","msgid":929,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/pubsub/subscribe.go:96 +0x2a5\n","msgid":930,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/pubsub.(*SubscriptionImpl).Activate(0xc000678000, 0x19c7d70, 0x19c7d80)\n","msgid":931,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/pubsub/subscribe.go:53 +0x6a\n","msgid":932,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"github.com/lf-edge/eve/pkg/pillar/cmd/loguploader.Run(0xc00068cf60, 0xc0001d01c0, 0xc000480b80, 0x0)\n","msgid":933,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/cmd/loguploader/loguploader.go:148 +0x6f5\n","msgid":934,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"main.startAgentAndDone(0x19c7d50, 0xc00007b900, 0xc000302ea0, 0xb, 0xc00068cf60, 0xc0001d01c0, 0xc000480b80)\n","msgid":935,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/zedbox/zedbox.go:234 +0x62\n","msgid":936,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"created by main.handleService\n","msgid":937,"timestamp":{"seconds":1607083500}}
{"severity":"info","source":"pillar","content":"\t/pillar/zedbox/zedbox.go:224 +0x38a\n","msgid":938,"timestamp":{"seconds":1607083500}}

So, please do something like:
diff --git a/pkg/pillar/cmd/loguploader/loguploader.go b/pkg/pillar/cmd/loguploader/loguploader.go
index 5c98188f3..848fc39cd 100644
--- a/pkg/pillar/cmd/loguploader/loguploader.go
+++ b/pkg/pillar/cmd/loguploader/loguploader.go
@@ -431,7 +431,9 @@ func handleGlobalConfigImp(ctxArg interface{}, key string, statusArg interface{}
                enabled := gcp.GlobalValueBool(types.AllowLogFastupload)
                if enabled != ctx.enableFastUpload {
                        // reset the schedule for next 30 minutes
-                       ctx.scheduleTimer.Stop()
+                       if ctx.scheduleTimer != nil {
+                               ctx.scheduleTimer.Stop()
+                       }
                        ctx.scheduleTimer = time.NewTimer(1 * time.Second)
                }
                ctx.enableFastUpload = enabled

@giggsoff good catch, will fix.

@giggsoff committed the fix

It works now, thank you.

added the search for panic stacks for files /persist/reboot-reason and /persist/reboot-stack. although newlog files will get into controller side, for development purpose, it's much easy to ssh into the device to see the stacks. this commit add a new directory /persist/newlog/panicStacks, to keep the last 100 pillar stack files with meta-data, something like:
b9da544a-47c3-4b7c-8c6c-81eb658aa708:/persist# cat newlog/panicStacks/pillar-panic-stack.1607136915
{"devID":"b9da544a-47c3-4b7c-8c6c-81eb658aa708","image":"IMGA","eveVersion":"0.0.0-naiming-newlog-infra-40835cb6-dirty-2020-12-05.02.04-xen-amd64"}
2020-12-05T02:55:15Z,pillar;panic: runtime error: invalid memory address or nil pointer dereference
2020-12-05T02:55:15Z,pillar;[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x131ec47]
2020-12-05T02:55:15Z,pillar;
2020-12-05T02:55:15Z,pillar;goroutine 183 [running]:
2020-12-05T02:55:15Z,pillar;time.(*Timer).Stop(...)
2020-12-05T02:55:15Z,pillar;    /usr/local/go/src/time/sleep.go:76
2020-12-05T02:55:15Z,pillar;github.com/lf-edge/eve/pkg/pillar/cmd/nim.Run(0xc000628420, 0xc00046b030, 0xc000656d80, 0x0)
2020-12-05T02:55:15Z,pillar;    /pillar/cmd/nim/nim.go:769 +0x4be7
2020-12-05T02:55:15Z,pillar;main.startAgentAndDone(0x19c7dc0, 0xc00006b800, 0xc000654b58, 0x3, 0xc000628420, 0xc00046b030, 0xc000656d80)
2020-12-05T02:55:15Z,pillar;    /pillar/zedbox/zedbox.go:234 +0x62
2020-12-05T02:55:15Z,pillar;created by main.handleService
2020-12-05T02:55:15Z,pillar;    /pillar/zedbox/zedbox.go:224 +0x38a
b9da544a-47c3-4b7c-8c6c-81eb658aa708:/persist#

It is the same error (Eden/Adam side). Actually, we are waiting for new image of Adam in docker hub to modify Eden. Today, we solved some inconsistency inside Adam (https://github.com/lf-edge/adam/pull/55), but, I thing, only @rvs can publish it.

It is the same error (Eden/Adam side). Actually, we are waiting for new image of Adam in docker hub to modify Eden. Today, we solved some inconsistency inside Adam (lf-edge/adam#55), but, I thing, only @rvs can publish it.

got it. thanks.


add -Dsonar.projectName and -Dsonar.projectKey STO-7377

Preview link: Additional CLI flags
PRs must meet these requirements to be merged:

[x] Successful preview build.
[ ] Code owner review.
[x] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6615d51950609f5a40c235af--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6616c90d61d7e91c4c9337e3--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6616c97c244b4a1b2195f36e--harness-developer.netlify.app


frontend can't be deployed on subpath

probably fixed in upstream, see https://github.com/DSpace/dspace-angular/issues/1488 https://github.com/DSpace/dspace-angular/pull/1642

@milanmajchrak
14305  nvm use v18
14306  source .env-yarn-dev
14307  cat .env-yarn-dev

export NODE_OPTIONS=--max-old-space-size=4096
#export DSPACE_REST_HOST=localhost
#export DSPACE_REST_PORT=8080
export DSPACE_REST_HOST=dspace-dev.ufal.mff.cuni.cz
export DSPACE_REST_PORT=443
export DSPACE_REST_SSL=true
export DSPACE_REST_NAMESPACE=/server
export DSPACE_UI_NAMESPACE=/repository/ui

14308  yarn start:dev

https://github.com/ufal/clarin-dspace/assets/1842385/d6f5665c-1488-4359-b364-b782d3c3be99

@kosarko

I will create a PR to the customer/lindat branch for the docker updates
I see that assets are correctly retrieved from the /repository path. Does this mean it is working properly? I assume you had to configure this in Nginx, which is likely the most efficient fix.

I've written down the steps required to change the namespace here: https://github.com/dataquest-dev/DSpace/wiki/Custom-namespace

works 👍

Tested with:
BE
Git hash:  https://github.com/ufal/clarin-dspace/commit/3486d2da1c304f1d1c374cd100fae42d21f01698 Date of commit: 2024-11-29 11:08:36 +0100
FE
Git hash:
https://github.com/ufal/dspace-angular/commit/e7e15778a8a7f4fe93f392afe49288698f3148ce
Date of commit:
2024-11-29 11:08:02 +0100

fixed in https://github.com/ufal/dspace-angular/commit/ea056b26f1605fdc5d540500cdb061ab594679fb


Logging multiple attributes on the same record

Hi there,
Nice lib.
Question: I want to log a few attributes on the same log entry. So for example,
One record would be:
{
"name": "orcaman",
"age: 29
}
Another record would be:
{
"name": "sally",
"age: 49
}
So that in Loggly I could create a pie chart for example by "name".
Thing is, with current logging mechanism, I can only log key/value per log entry. If I use JSON as the value, it gets nested, and then Loggly would not index it (so if I go
key = "something"
value = "
{
"name": "sally",
"age: 49
}
"
Loggly would not index by age as it's an "inner" JSON.
Just in case I'm missing this - is it possible using the current code?
Cheers

Hi,
Well, there's no support for more than one key/value pair per log entry using the regular Loggly.i(key ,value) but a workaround could be to use the stickyInfo feature that lets you add additional key/value pairs that persist between log messages: Check out appendStickyInfo and setStickyInfo,
Cheers!

It isn't very practical to use appendStickyInfo for the above issue. Loggly is designed to log JSON data. I'm planning to fork your repo and will issue a pull request for a change that will support taking a JSONObject as a parameter and merging its properties into the Loggly message.

please do make a PR out of https://github.com/smacbeth/loggliest/commit/a9eb78abbc6ba59083c12f998e0b673fb60c18b8 as i would like the same functionality

Sorry for the slow reply. I see the need to address this and the smacbeth/loggliest fork looks ok, just need to make sure there are no regression issues. Go ahead and create a pull request and I'll attend to it.

I'm having a look at this again and it looks to me that Loggly indexes nested json data correctly, perhaps this wasn't the case when the issue was raised? Just log with a JSONObject as value and it should work just fine.


Api changed for beta.9, please update document for Button

It seems the Button is no longer lives in material-ui/Button for v1.0.0-beta.9

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

Expected Behavior

In document Buttons
import Button from 'material-ui/Buttons'

now have changed into
import FlatButton from 'material-ui/FlatButton'
import RaisedButton from 'material-ui/RaisedButton'

Current Behavior

when import from material-ui/Button, will report Module not found
Steps to Reproduce (for bugs)

import Button from 'material-ui/Button';
Webpack will complain cannot find module.

Context

n/a
Your Environment

Tech
Version

Material-UI
^0.19.1

React
^15.6.1

browser
n/a

etc
n/a

Sorry, My fault, I meant to use beta.9 but installed 0.19.1. will close this issue now.


Zeus v0.15.5

Please push v015.5 to rubygems. Thank you.

It does not build currently.

@latortuga I figured there was a reason it wasn't pushed. Thanks for the info.


Themes - Round, Plate Dark - single result does not have top border

Please add this css code to your css file,
.easy-autocomplete-container ul li:only-child {   border-radius: 10px;   border-width: 2px; }


Improve the "About Us" Page:

@Priyaaa1
**The "About Us" page is crucial for conveying the mission, vision, values, and story of StartConnect Hub.
**Benifit:

Clearly articulate the long-term vision and core values that guide the platform's operations and decision-making processes.
Provide a compelling backstory of how and why the platform was founded. Include insights into the founder’s inspiration and journey.
Basic or missing team information.
Encourage visitors to take the next step, whether it’s signing up, contacting the team, or exploring the platform.

Additional context
By enhancing the "About Us" page with detailed, engaging content, we can effectively communicate the value and uniqueness of StartConnect Hub,  and interest among potential users.
Please assign me this issue and add gssoc label , i will work on it...

@RishabhDhawad  can you please assign me this issue

@Priyaaa1 Thank you mam for assigning me this issue , I'll give you update after few days.

@Priyaaa1 can i work on this?


Test fix empty expected files

Right now Generate/JavaScript.hs has a lot of errors. So if you run:
ELM_WRITE_NEW_EXPECTED=1 cabal test
It will write empty files for all the examples with errors.
But there are several other test cases which do compile and do need to be updated, and you don't want to have to pick through which ones to commit.
@evancz

I don't fully understand, but this seems like an okay thing to add.


Additional imports from the Relations Ontology

Description of the issue
This issue collects additional imports we need from Relations Ontology:

causally related to and/or subproperties (from #973 and #1023)
realised in (from #1054)

Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Working on this now.


[Doc] Update to tutorial 1

I've read through the wiki's tutorial 1 and made some adjustments:

Fixed some mistakes
Removed repetitive passages
Updated CMakeLists.txt to use target_include_directories()

https://gist.github.com/MajorBreakfast/b92c82ad1701e604f788
Note: I can't provide a PR unfortunately because github doesn't support PRs for wiki repos.
BTW cmake-js worked great for me so far (on all three platforms). So, thanks for that!

Hi,
Thanks for contribute.
I've opened up the wiki, so you can push your changes with GIT from now on:
https://github.com/unbornchikken/cmake-js.wiki.git
BR,unbornchikken
Date: Wed, 11 Nov 2015 02:02:29 -0800
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Subject: [cmake-js] [Doc] Update to tutorial 1 (#30)
I've read through the wiki's tutorial 1 and made some adjustments:
Fixed some mistakes
Removed repetitive passages
Updated CMakeLists.txt to use target_include_directories()
https://gist.github.com/MajorBreakfast/b92c82ad1701e604f788
Note: I can't provide a PR unfortunately because github doesn't support PRs for wiki repos.
BTW cmake-js worked great for me so far (on all three platforms). So, thanks for that!
—
Reply to this email directly or view it on GitHub.

Updated, thanks!

Nice. Thx. :)


[3.1] Refresh button is invisible

After a fresh install on Godot 3.1, the button is functional but invisible.

@lleaff I think this has something to do with the way the icon is being imported. When I downloaded the AssetLib version, the icon was missing as you portrayed. When I opened up the actual plugin refresher scene, changed the icon to something else, and then changed it back, everything was fixed. Furthermore, after I deleted the files from my project, I tried re-downloading first from GitHub directly (which worked), and then again from the AssetLib (which worked).
I noticed that some of the .import files properties were different the very first time I installed the plugin, so my suggestion would just be to try re-importing the icon. I can't reproduce the error anymore.
Let me know if you continue to have any more occurrences of this issue.

Have you continued to have problems with this?

Still relevant in Godot 3.2-dev.

I think this has something to do with the way the icon is being imported.

Yeah, I think this has something to do with the engine itself, plugins might be registered before anything else and SVG importer fails to import icon in timely manner to update icon path.


Clarification on Testing Results for SpatialBot-3B Model

Hi @RussRobin,
Thank you for your great work! I found it very interesting and decided to test the models using SpatialBench. However, I noticed that the performance of your proposed model, SpatialBot-3B, shows almost no improvement compared to Bunny-v1_0-3B in my tests, which doesn’t seem to align with the results in TABLE I of your paper.
I’m wondering if I might have selected the wrong version of the Bunny model, or if there is something I’m missing in the evaluation process.
Could you kindly provide some clarification?
Looking forward to your response!
Best regards

Hi @robotlab2024 , thank you for your interest in our work.
For Table 1 in paper: I trained Bunny with Bunny695k, in multi-image version so it can be tested with RGBD (the data is essentially the same with Bunny v1.0 & Bunny695k). I just tested with Bunny v1.0 3B:
Bunny RGB
positional get  17  out of  34   50.0 %
existence get  15  out of  20   75.0 %
counting get  92.41071428571429  out of 100.
reach get 20  out of  60   33.333333333333336 %
size, get 15  out of  60   25.0 %

The Bunny results are almost the same with my version of Bunny (as in Tabel 1), and reach is even lower.
I also tested with the newest version of SpatialBot-3B:
SpatialBot RGBD newest
positional, get  17  out of  34   50.0 %
existence get  13  out of  20   65.0 %
counting get  87.41071428571429  out of 100.
reach, get 30  out of  60   50.0 %
size, get 16  out of  60   26.666666666666668 %

SpatialBot RGB newest
positional get  21  out of  34   61.76470588235294 %
existence get  16  out of  20   80.0 %
counting get  87.41071428571429  out of 100.
reach, get 33  out of  60   55.0 %
size, get 14  out of  60   23.333333333333332 %

And an old version of SpatialBot, which you can download with: huggingface-cli download --resume-download RussRobin/SpatialBot-3B --local-dir /root/autodl-tmp/SpatialBot-3B-old --revision 0f9fb9330440c262f68da699524236df6f8ebef7:
SpatialBot RGBD old version:
positional get  20  out of  34   58.8235294117647 %
existence get  12  out of  20   60.0 %
counting get  93.125  out of 100.
reach, get 30  out of  60   50.0 %
size, get 19  out of  60   31.666666666666668 %

SpatialBot RGB old version:
positional: get  21  out of  34   61.76470588235294 %
existence get  15  out of  20   75.0 %
counting get  92.41071428571429  out of 100.
reach, get 31  out of  60   51.666666666666664 %
size, get 17  out of  60   28.333333333333332 %

The test code i'm using:
#!/bin/bash
MODEL_TYPE=phi-2
python -m bunny.eval.eval_spatialbench \
    --model-path ... \
    --model-type $MODEL_TYPE\
    --data-path ./eval/spatial_bench \
    --conv-mode bunny \
    --question size.json \
    --depth # or comment out for RGB input

I believe the results are consistent with the paper, with a little bit fluctuation. And there are improvements of SpatialBot in comparasion to Bunny. Please share your test results and codes and let's dive in it deeper. Again, thanks a lot for your interest and experiments in SpatialBot.
ps. The eval code was changed 3 weeks ago in this commit and a small bug fix in this commit, please ensure that you are up to date.

Quick comparasion chart:

Hi @RussRobin ,
Thank you for your detailed response!
I noticed that in your test set, the number of questions for the four categories—existence, counting, reach, and size—are 20, 100, 60, and 60, respectively. However, in the publicly available SpatialBench dataset, the numbers for these categories are 40, 20, 40, and 40, respectively. I wonder if this discrepancy might be the cause of the issue.

Thank you very much for your response. I sincerely apologize for not reading the model evaluation section of the paper carefully. I really appreciate you taking the time to address my questions.
Hope you have a good night, @RussRobin.

No worries. Great thanks for your interest in our work! I will close this issue then.


We should have a table / document for docker-compose to k8s / openshift conversion

It'll be helpful for developers and users to have such docs.

We can probably auto-generate this.

@janetkuo You should talk to @kadel I remember him doing something similar for henge.

so @kadel can you help ?

I started this for Henge, but I just had rough draft, you can see it in Henge's wiki https://github.com/redhat-developer/henge/wiki/Mappings We also had some internal document describing this with more details. I will try to find it and see if we can use that.
I really like @janetkuo idea of auto-generating this. How would you like to do that?

I'm thinking that we can use yaml tags of each field of different struct (libcompose, kobject, and kubernetes objects) and create map[string]string that maps one yaml tag to another (e.g. libcompose ServiceConfig's image maps to kobject's image which maps to k8s Container image). We can use that in code for conversion as well as auto-generate the table by printing the map. WDYT?

I never thought about using tags like this. It sounds cool.

@kadel as we have conversion table at http://kompose.io/conversion/, we can close this issue.

@surajnarwade :+1: Closin'


Add fill_value support for series comparisons

This PR adds support for fill_value for dask Series comparison methods
Fixes #4249

[ ] Tests added / passed
[ ] Passes flake8 dask

Thanks @jrbourbeau !


Add a build and a test run to travis for --no-default-features

This PR is in reference to https://github.com/purpliminal/rust-dotenv/issues/107#issuecomment-402331015 to add a build and a test run for --no-default-features.

Thank you!


ERROR: state.out.json is not a valid terraform plan json output. (Child modules support)

State output file
  "format_version": "0.1",
  "terraform_version": "0.14.3",
  "values": {
    "root_module": {
      "child_modules": [
        {
          "resources": [
            {

I get
terraform-compliance v1.3.15 initiated

ERROR: state.out.json is not a valid terraform plan json output.

It seems the issue is in this code where it's not considering "child_modules" tag.
# Check if this is a state file
if 'values' in data:
     assert data['values']['root_module']['resources']

Code: https://github.com/terraform-compliance/cli/blob/ac843f3cda214b9c0d32be459fb623ccc18a9525/terraform_compliance/common/readable_plan.py#L76

#497

This feature released in 1.3.16, closing this issue.
Please do not hesitate to open a new one if the problem still occurs


transcript sync

Pre-Flight checklist

[ ] Screenshots and design review for any changes that affect layout or styling

[ ] Desktop screenshots
[ ] Mobile width screenshots

[ ] Migrations

[ ] Migration is backwards-compatible with current production code

[ ] Testing

[ ] Code is tested
[ ] Changes have been manually tested

[ ] Settings

[ ] New settings are documented and present in app.json
[ ] New settings have reasonable development defaults, if applicable
[ ] Opened issue for DevOps regarding necessary configuration changes to deployed environments

What are the relevant tickets?
(Required)
What's this PR do?
(Required)
How should this be manually tested?
(Required)
Where should the reviewer start?
(Optional)
Any background context you want to provide?
(Optional)
Screenshots (if appropriate)
(Optional)
What GIF best describes this PR or how it makes you feel?
(Optional)

Codecov Report

Merging #552 (2a31a9d) into master (951095b) will increase coverage by 4.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #552      +/-   ##
==========================================
+ Coverage   90.52%   94.96%   +4.43%
==========================================
  Files         169       77      -92
  Lines        5816     2183    -3633
  Branches      857      441     -416
==========================================
- Hits         5265     2073    -3192
+ Misses        492      108     -384
+ Partials       59        2      -57

Impacted Files
Coverage Δ

...dev/management/commands/populate_local_starters.py

websites/signals.py

main/views.py

main/utils.py

news/views.py

repl.py

ocw_import/api.py

content_sync/backends/base.py

main/apps.py

websites/config_schema/validators.py

... and 79 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 951095b...2a31a9d. Read the comment docs.


Extended DNS_PING documentation

Hey!
I extended a few bits on DNS_PING docs. Please have a look and tell me what do you think about it.
Thanks,
Seb
//cc @pferraro @rhusar @luck3y

@slaskawi Thanks for this, every bit of extra info helps :)


The APP react slowly and weird after running couple of hours.

Description
I like "continue from where you left", and I open the app all the time to keep commonly used folders avaliable, though win11 reboot. But the APP may react slowly and weird after running couple of hours, , for example, I cannot rename a file, the focus often run to the upper folder; I cannot move or clip file easily, which may lead to much lag; clicking on a tab will most likely move it to a new window; sometimes the focus just quickly jump from two adjacent folder and I cannot do anything but forcefully close it.
Besides, clicking file(not folder) in list view may instantly destroy all subfolders already opened on the right side, and everything flash to right, but right click won't trigger that. It is difficult to adapt the content flash on screen. Destroying that is reasonable, but I think it's better to keep the horizontal position.
Anyway, the list view and "continue from where you left" option is 2 reason I give up the default file manager in win11, you guys did really good thing.
Steps To Reproduce
Use the APP in normal way but never close it, opening multiple tabs is required.
Steps to fix
Restart can fix the problem, but restarting it everyday may not a good idea.
Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.1265
Log file

Can you please upload the debug.log file directly to GitHub (email attachments don't work) . You can get it in Files settings > About > Open log folder.

This is a result of some memory leaks, we recommend reopening the app every now and then to work around this issue until it's fixed. We're tracking this in #4180

Can you please upload (Do not copy and paste content) the debug.log file directly to GitHub (email attachments don't work) . You can get it in Files settings > About > Open log folder.

Alright, sorry for inconvenience.
debug.log


fb/python/lib.so: undefined symbol: _ZN6google4base21CheckOpMessageBuilder9NewStringEv

[root@localhost vrn]# ./run.sh
/root/torch/install/bin/luajit: /root/torch/install/share/lua/5.1/trepl/init.lua:389: /root/torch/install/share/lua/5.1/trepl/init.lua:389: /root/torch/install/share/lua/5.1/trepl/init.lua:389: error loading module 'fb.python.lib' from file '/home/liyilun/torch/install/lib/lua/5.1/fb/python/lib.so':
/home/liyilun/torch/install/lib/lua/5.1/fb/python/lib.so: undefined symbol: _ZN6google4base21CheckOpMessageBuilder9NewStringEv
stack traceback:
[C]: in function 'error'
/root/torch/install/share/lua/5.1/trepl/init.lua:389: in function 'require'
main.lua:8: in main chunk
[C]: in function 'dofile'
/root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:150: in main chunk
[C]: at 0x004064f0
ls: cannot access *.txt: No such file or directory
ls: cannot access *.raw: No such file or directory

The same error！How to solve？

@shubaozhang @AaronJackson Same mistake! How?

You both have different errors but try what I suggested here: https://github.com/AaronJackson/vrn/issues/39

@AaronJackson  It's not a segmentation fault error, but more like a linking error -- fp-python.

@shubaozhang which distribution and version of Linux are you using?


Gradle 4.10 release notes/features

Context
This is just the preamble for the notes and the release-features.
Reordering and polishing the detailed notes content will come in a separate PR.
@eskatos please add but about kotlin-dsl when you can.
Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

LGTM. I left few comments.


cmd/api: recognize vendor packages as not contributing to public API

Right now running all.bash gives:
##### API check
...
+pkg golang.org/x/net/http2/hpack, func AppendHuffmanString([]uint8, string) []uint8

This appears to be coming from $GOROOT/src/vendor/golang.org/x/net/http2/hpack.

I can take this.


Support for asymmetric public-private key encrpytion

Hey there!
I found this awesome project while looking for cross platform apps that support libsodium file encryption/decryption.
It's so great to see things like this coming to the browser so people do not have to worry about installing any tools and using the command line etc. Great job!
Because I could not find any reference to public-private key support: Do you plan on adding something like that?
Of course not asking you to do it for free but just generally asking for a statement whether you would be willing to have support for it in hat.sh :)
That would enable us to get rid of sending the secret alltogether.
I imagine the process something like this:

Allow to generate a new key pair and download the files. Maybe the public key can be shown in ASCII format to copy right away.
I can then send the public key to the person I want to receive the file from
That person can encrypt the file using the public key (so we need another option besides entering a symmetric password)
The receiving person can select the private key file (so another option here too) while decrypting
Done :-)

Or did you not add support for it for any specific reason?
Thanks and keep up the great work!

Great job!

Thanks! glad you like it.
Thank you for your suggestion. It is definitely something we thought about many times. This is not yet implemented due to multiple reasons. Mainly because it takes away from the vision of this web app, which is a simple single file encryption with a password. I hope in the future this will be implemented eventually, what do you think?

Or did you not add support for it for any specific reason?

Yes, sender authentication, which plays a crucial part in this scenario.

I can then send the public key to the person I want to receive the file from

The recipient must be sure that the file was encrypted and sent to them from the person (who shared keys with) they intended them to be. for example if i receive a file encrypted with my public key that i have shared with someone, i can't be sure that they are the one who encrypted the file and sent it to me, it could be anyone (middle man) who used my public key to encrypt the file.
This could be solved by implementing hybrid encryption where the sender encrypts the file with their own private key and the receiver public key. And then the recipient decrypts the file with their own private key and the sender public key. that way you can be sure that the encrypted file came from the sender you shared public keys with.

I see! To me, that's yet another level on top of the basic sealing. Right now, if I'm using hat.sh to encrypt and send the data elsewhere, there's no way to know that it came from me either. But on top of that, I also have to send the secret.
With basic sealing functionality at least that problem would be solved.
The reason why I'm asking is basically that I could not find any good GUI for libsodium. As developers, we have a variety of options to choose from to work on CLI but regular users are mostly lost.
And with hat.sh they would not even have to install any additional software!
I could get the public key from a customer once and whenever I send them stuff, I can sign it with their public key and they can decrypt it. No need to share any passwords anymore.
Yes, that does not solve the problem of authenticated encryption but again, to me that's just yet another level on top :)

I understand, this should be implemented in hat.sh in the future for sure. For now, if you are looking for a GUI that may satisfy your needs (not libsodium), you should be looking for something like openpgp

Asymmetric public key cryptography is coming in the next version. If you like to test it out go here. Would love to hear your feedback as soon as you try it.

Oh wow!!! This is awesome, it works like a charm and looks absolutely gorgeous!
What would be great is if one could link to the decrypt page with the public key prepouplated already. Something like dev.sh?tab=decrypt&public_key=.... Would make it easer for the user as they do not have to copy the sender public key manually then :)
So you decided to only support authenticated asymmetric encryption and decription. No plans to support anonymous ones too then?

Thank!

What would be great is if one could link to the decrypt page with the public key prepouplated already. Something like dev.sh?tab=decrypt&public_key=.... Would make it easer for the user as they do not have to copy the sender public key manually then :)

Sure, it is something currently in development too.

So you decided to only support authenticated asymmetric encryption and decryption. No plans to support anonymous ones too then?

No plans for now, and i don't think it's gonna happen too. It takes away from the vision of the app.

Sure, it is something currently in development too.

So you decided to only support authenticated asymmetric encryption and decryption. No plans to support anonymous ones too then?

this is live now in dev. let me know how the user experience is like.

Works nicely when encrypting decrypting with hat.sh! Great job!
However, I cannot seem to get it working when the encryption happened with libsodium in another programming language which is supposed to be one of the key advantages of libsodium.
Maybe it's because of the different formats of the respective keys which is currently undocumented so it's hard to find out, what's expected by hat.sh :)

thanks. Maybe it's not using the same algorithms + Hat.sh adds a unique encryption signature to the encrypted file.


Is is possible to show a message in px-overlay component

Hi,
I am using  px-overlay component to block the UI for users till a process completes. Meanwhile the process is running, i want to show a message like 'Loading data...' in the center of the overlay. Please suggest if it is possible using px-overlay or in some other way i can achieve this.
See below screenshot for example:

Thanks,
Rajiv

Is there any reason for not allowing content inside overlay?


Chrome 48 and 49: Nested flex-direction column elements cause incorrect heights

I'm noticing a number of issues in Chrome 48 and 49 on OSX, Windows, and Android when you nest multiple elements with 'flex-direction: column' and 'flex: 1 1 auto'.
Failure to reduce height of elements when you reduce window height:
http://s.codepen.io/chrisboon27/full/wMqwMB
If you expand the height of your window both inner divs (blue and brown) will expand. However reducing the window height will cause them to stay large and overflow. Adjusting the width of the window causes then to jump back to the height that would fit.
Unexpected (and wrong) recalculation of height when a repaint occurs
http://codepen.io/chrisboon27/full/BjdBqL
In this pen clicking the blue or brown boxes will simply use jquery to adjust its inner orange divs opacity. This causes a repaint at which point Chrome also adjusts the height of the clicked div.
Note that again adjusting the width of the window will fix the problem.
I've viewed the pens in Chrome 48 and 49 on iOS, Windows 10, and Android and the problems occur.
The issues don't appear in the current stable channel (47), only beta, dev, and canary builds, so maybe they'll never appear in stable?

btw I've filed bugs for this:
https://code.google.com/p/chromium/issues/detail?id=576859
https://code.google.com/p/chromium/issues/detail?id=576855

Thanks for filing the bugs @ChrisBoon. Since this seems to be a Chrome re-layout/paint issue, it's unlikely a good cross-browser workaround exists for it, so I'm going to close this issue.
If anyone else finds this thread, please watch the bugs linked above for fix status.