Token-Deny List as runtime argument

Some tokens behave badly and don't work with our infrastructure even though they might be tradable in AMM pools. Such tokens are currently blocking our services over extended periods of time while orders containing misbehaving tokens (as buy or sell token) are valid and being passed onto solvers.
This issue proposes a token deny list which is passed into the services at runtime and will be handled in the following parts of the code

OrderCreation -> Deny creation of orders containing denied tokens
fee estimation -> Skip fee estimation for denied tokens
Exclude orders containing denied tokens in the solvable_orders filter (so not to pass these orders onto the solver).

@fleupold - may be able to provide some additional context along token examples.

https://dashboard.tenderly.co/gp-v2/staging/simulator/78e7b41b-4caa-4ca8-bab2-90d7d6766db1 is an example of a bad transaction. The token is Rare Coin which is unfortunately not verified, yet part of the default Honeyswap Token List (https://tokens.honeyswap.org/)


IBM Power9 (ppc64le) support

Hi,
Has anyone been able to install bcbio-nextgen on IBM ppc64le?  Is there an installation script compatible with ppc64le?
I'm trying to modify the bcbio_nextgen_install.py to run on ppc64le.
Best,
Pedro

I have not heard that anybody ran it on Power9,
however, if the server is Linux based, why not?


Map method. Should Daru::Vector return an Array?

Daru's vector returns an array when you call the map method.
v = Daru::Vector[1,2,3,4]
v.map {|i| i}
# => [1, 2, 3, 4]

If you use module Enumerable, the map method returns an array.
However, in Ruby, there is no rule that the map method must return an array.
For example,
require 'numo/narray'
a = Numo::SFloat.new(10).seq
a.map{|i| i}
#=> Numo::SFloat#shape=[10]
#[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

Daru has prepared recode as a method to return a Vector.
v = Daru::Vector[1,2,3,4]
v.recode {|i| i}
#=> #<Daru::Vector(4)>
#   0   1
#   1   2
#   2   3
#   3   4

This practice is not so common.
I think map should return Daru :: Vector.
If there is room to change the API from now, please consider.

looking into this

Thank you for your work. @him666
But what I suggested was to change the behavior of the map method.
Currently, the map method returns an Array, but I suggested changing it to return Daru::Vector.
This is not a technical issue but a user consensus issue.
map_to_vector is similar to recode.
So I think we don't need a new method.

I too, think that map on Daru::Vector should return Daru::Vector and not Array.


Arrow-6180: [C++] Create InputStream that references a RandomAccessFile

-1. Please do not make any changes to BufferedInputStream
I described the solution that I'm looking for in https://issues.apache.org/jira/browse/ARROW-6180. I will respond to Antoine's comment there so the issue is more clear

I've got a patch that implements the threadsafe stream that we need (and tests for it). We don't have any unit tests for the buffered stream case which is why this problem was not caught during the refactor -- I'll try to write one that reproduces the issue.

Closing in favor of https://github.com/apache/arrow/pull/5085


Migration and model changes to synchronize the data model

CATEGORY
Choose one

[X] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

Generating a new migration in Superset currently outputs a large number of changes in the migration due to the tables created by example import and some schema drift that has happened over time. This PR ignores the tables created by the example import, applies a small number of database changes, and updates a number of models to resolve the situation. After merging this PR, generating a new Alembic migration should result in an empty file, or one with only the intended changes after a model update.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

No UI changes.
TEST PLAN

[ ] Run unit tests

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[X] Requires DB Migration.
[X] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@betodealmeida @mistercrunch

Codecov Report

Merging #8737 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8737   +/-   ##
=======================================
  Coverage   58.88%   58.88%
=======================================
  Files         359      359
  Lines       11328    11328
  Branches     2783     2783
=======================================
  Hits         6671     6671
  Misses       4479     4479
  Partials      178      178

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 025b31c...6c2f497. Read the comment docs.

@john-bodley and @mistercrunch - I've looked closely at the constraint in question, and I can find where it is added to the database (https://github.com/apache/incubator-superset/blob/master/superset/migrations/versions/b4456560d4f3_change_table_unique_constraint.py) but cannot find any migration that removes that constraint. It's possible that it was never applied to your MySQL database, but that constraint does exist in postgres. We have two options here:

Not going to get back to this in time to make it fully actionable. Will make another attempt at a later date.


TypeError: e.getCondition is not a function

I could only get these on windows when jump to a job that created by volcano.
Component stack:
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at I (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1396458)
at b (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:9663813)
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at I (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1396458)
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)
at re (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:2:855769)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:12355780
at div
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10459272
at t (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:5455435)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:12355780
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:9903851
at l (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1402964)

Error stack:
TypeError: e.getCondition is not a function
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10083578
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10082508
at ct (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1450747)
at t.computeValue_ (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1448204)
at t.trackAndCompute (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1448049)
at t.get (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1447295)
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10319892
at Array.filter ()
at https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:10319871
at ct (https://7653916574ca72bf71bc867fbd1fd928.lens.app:59440/build/lens.js?a4d206b170f2c4d92ccd:8:1450747)

May we know in which version of Lens are you currently on? @bingwork

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:
Lens: 2024.10.171859-latest Electron: 31.6.0 Chrome: 126.0.6478.234 Node: 20.17.0 © 2024 Mirantis, lnc.

Would you mind giving a try to our latest version 2024.11.131815-latest? Currently only available through direct download from our Website.
If the problem persist, could you please provide a dummy job for us to replicate the issue? is it something like https://volcano.sh/en/docs/vcjob ?
And, does this happen when:

opening the list of jobs
opening the details panel of the aforementioned job
opening the details panel of the pod created by the job?

Just trying to narrow down how to best reproduce the issue, so we can quickly fix it on engineering as there are a couple of places where the getCondition could be triggering this...

Can you paste the kubectl describe of this job?

May we know in which version of Lens are you currently on? @bingwork

hi, @dechegaray , the information is below:
Lens: 2024.10.171859-latest Electron: 31.6.0 Chrome: 126.0.6478.234 Node: 20.17.0 © 2024 Mirantis, lnc.

Would you mind giving a try to our latest version 2024.11.131815-latest? Currently only available through direct download from our Website.
If the problem persist, could you please provide a dummy job for us to replicate the issue? is it something like https://volcano.sh/en/docs/vcjob ?
And, does this happen when:

opening the list of jobs
opening the details panel of the aforementioned job
opening the details panel of the pod created by the job?

Just trying to narrow down how to best reproduce the issue, so we can quickly fix it on engineering as there are a couple of places where the getCondition could be triggering this...

@dechegaray Thank you for your reply, and sorry, I can't reproduce this issue at the moment because we are using vcluster, and Volcano has been uninstalled. It might have been due to our previous vcluster not supporting CRD.


Transaction management

I'm a big fun of try-with-resource and propose this pattern for transaction management for new release
try(Transaction tr= cn.beginTran(TransactionIsolation.REPEATABLEREAD){
    // some actions
    tr.commit();
} // rollback if not commited in close()

"Transaction in transaction" would be great for testing
Scenario:

you want the test to open a transaction
the tested object opens an internal transaction and commits/rolls back,
in the test you assert and finally roll back.

A


Sails mongo reconnect MongoError: Topology was destroyed

Node version: 8.11.3
Sails version: 1.1.0
ORM hook version: 2.1.1
Sockets hook version: 1.5.5
DB adapter & version<EMAIL_ADDRESS>
I'm facing the same problem of Stack overflow/sails-mongo-reconnect and i didn't find any solution in all docs. Is there some datastore adapter config option that can be included to reconnect?

When sails is lifted, if mongo db server is up and running, everything is okay. If mongo db goes down, and the node.js tries to access the mongo db as part of a functionality and it times out, an internal server error is shown to the user. This is all okay. However, when mongo comes back up, sails no longer reconnects to it and throws out this error:
" AdapterError: Unexpected error from database adapter: fn called its error exit with:{ MongoError: Topology was destroyed } "

Hi @muriloqr after some digging I noticed there is currently a pull request under review that may have the key to fixing this issue.
@luislobo do you think this issue could be fixed by that pull request?

@raqem Probably, yes. @muriloqr Could you try this branch and see if this fixes your issue? It will also help test it on another real world use case.

Also @muriloqr, check the README.md as some options were added. Still figuring out if we will keep both autoReconnect and auto_reconnect, or just keep the one that matches MongoDB official supported configuration.

@luislobo unfortunately, it doesn't solve the problem. By the way i'm able to describe more specific the steps to the bug:

Start MongoDB locally and connect sails to it
Start NODE_ENV=production sails lift
Stop MongoDB systemctl stop mongod
Call a route that consumes mongo
After 30 seconds, will appear this: AdapterError: Unexpected error from database adapter: failed to reconnect after 30 attempts with interval 1000 ms
Call again any route that consumes mongo and the result will be 500 forever AdapterError: Unexpected error from database adapter: Topology was destroyed

Finnaly, I was able to resolve by passing these settings:
  default: {
    adapter: 'sails-mongo',
    url: 'mongodb://admin:admin123@<IP_ADDRESS>:27017/datastore?authSource=admin',
    reconnectTries: Number.MAX_VALUE,
    reconnectInterval: 1000
  },

Thank you very much!

@muriloqr, I tried your solution, but it still does not reconnect :(


stickers aren't working

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #general.

Fixed


Consider using angular2-template-loader in templates/Angular2Spa

Hi guys,
I just stumbled upon angular2-template-loader, and thought it's worth considering for this template (I'll definitely use it in my project from now on).
If you see some component's code like this you'll notice the template and styles are required. This is nice because we don't make as many requests compared to using templateUrl and styleUrls.
But there's a drawback: we're tying our code into Webpack. And that brings some issues like not being able to run the ngc compiler on our code. Surely someone's going to make it work at some point, but it's not working at the moment.
Using the mentioned loader, we're able to write plain Angular code like templateUrl: './app.component.html', while retaining all the benefits from bundling and transparency that Webpack provides.
I tested it and I can even require scss like styleUrls: ['./app.component.scss'], but as a side note, this probably won't work with ngc.
Thanks for your great support!

This is a good idea. Do you know how close this gets us to having ngc support with full AoT compilation and proper tree shaking? Once we can demonstrate all of that working, it will be a big step forwards. Or if that's not all doable yet, then this change might not be so useful.

@tinchou I can look into this and whether it'll work with ngc. I know as of right now, the AoT support is a little shakey, but hopefully soon it'll be working 100% :)

Awesome!
I suggested this change because the errors you see when you try to use ngc
is that you can't use require. From the Angular docs, it seems that they
want to run the compiler directly, and not using webpack or other tools.
Anyway, I stopped trying when I saw every guide was using rollup and not
webpack. And they were transpiling es6 code into ts and back to es5. And
the build process was not easy. Not a one-day task, at least for me :/.
On Tue, Oct 4, 2016, 09:53 Mark Pieszak<EMAIL_ADDRESS>wrote:

@tinchou https://github.com/tinchou I can look into this and whether
it'll work with ngc. I know as of right now, the AoT support is a little
shakey, but hopefully soon it'll be working 100% :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/JavaScriptServices/issues/356#issuecomment-251379283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeg9H5D7LfZ9TozN06XjIv7f0wqM6sGks5qwkxfgaJpZM4KNKVf
.

This looks promising! http://www.michaelbromley.co.uk/blog/551/some-notes-on-angular-2-aot-mode-with-webpack-sass-ngtools.  Are we ready to upgrade to Webpack 2 in order to support AoT?
I was right suggesting this after all :).

I don't know if Steves aspnet webpack is ready for 2?
We are close to finishing AoT support from a Universal point of view so hopefully soon we can integrate all these amazing things 😃 don't forget AoT is super new and shakey itself! It'll take time for it to mature.

I made it work in the Angular template with a few tweaks. I think he was
planning to upgrade when they released the final version.
On Sun, Oct 9, 2016, 17:21 Mark Pieszak<EMAIL_ADDRESS>wrote:

I don't know if Steves aspnet webpack is ready for 2?
We are close to finishing AoT support from a Universal point of view so
hopefully soon we can integrate all these amazing things 😃 don't forget
AoT is super new and shakey itself! It'll take time for it to mature.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/JavaScriptServices/issues/356#issuecomment-252510077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeg9MUVVPk1DQm_hyPM5NUIovi2mq5Cks5qyUzCgaJpZM4KNKVf
.

Webpack is pretty easy for us to update, because it doesn't really tie into any other tooling (e.g., unlike TypeScript, which your IDE needs to know about).
So we could technically go to Webpack 2 beta now. We haven't done just because there wasn't a sufficiently compelling benefit to justify the risk that they make breaking changes before the Webpack 2 final release. I'd say that if we got easy and clean AoT/tree shaking, then that would be worth considering. Otherwise it would be beneficial to stay on Webpack 1 until the final stable version of Webpack 2 ships.

I made it work :). I completely removed server-side prerendering since I wasn't using it, so I don't know if that's working.
Once it's configured it's pretty transparent, I like it. If anyone tries to tackle this let me know and I'll try to help overcoming some quirks. For example this the only configuration that worked for me:
        new ngToolsWebpack.AotPlugin({
            tsConfigPath: "./tsconfig.aot.json",
            entryModule: path.resolve(__dirname, "ClientApp", "components", "main.aot") + "#MainModule",
            typeChecking: true,
        })

@tinchou Can you please explain steps to enable AoT ?  It would be really helpful

@kjartanvalur please refer to this gist with my configuration.
In simple words:

use @ngtools/webpack loader for AoT, and remove all calls to require()
use the angular2-template-loader for your dev configuration if you want to avoid AoT
write the AoT tsconfig and bootstrap files
ignore the error in the AoT bootstrap file, as it will be handled by the @ngtools/webpack loader

I'd be interested to know if anyone's managed to achieve any substantial bundle size reductions via AoT/tree-shaking.
The best I've managed - following roughly @tinchou's approach - is to reduce the production build from about 1.1MB to about 0.8MB (even after going through rollup) which is not really significant enough to warrant the extra complexity in the build system.
Can anyone improve on that?

@SteveSandersonMS  my understanding is you wont see the big size reductions until AoT compiler is using the closure compiler. It is used internally by Google but is not ready for public consumption.
You can also use Source Map Explorer to get a breakdown of where your bloat is coming from and what is getting shaken out.

Or use this new cool thing :) https://github.com/th0r/webpack-bundle-analyzer

The Angular2Spa template now uses angular2-template-loader. Thanks for suggesting this!


Node launch 'program' parsed incorrectly

I'm trying to launch Mocha tests in debug mode with TypeScript and ts-node, this should work (and used to work I believe):
{
    "type": "node",
    "request": "launch",
    "program": "${workspaceRoot}/node_modules/.bin/_mocha",
    ...
}

but I'm getting:
Cannot launch program 'c:\Temp\vscode-ts-node-debugging\node_modules\.bin_mocha'; setting the 'outDir or outFiles' attribute might help.

Note that there is a backslash missing in that message (\.bin_mocha should be \.bin\_mocha) so that leads me to think that the program value is parsed incorrectly. If I change my launch.json to contain:
"program": "${workspaceRoot}/node_modules/mocha/bin/_mocha"

all works fine (but it's more correct and most tutorials use node_modules/.bin/_mocha).

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:09.760Z)
OS Version: Windows_NT ia32 10.0.15063

@borekb can you reproduce this with vscode insiders?
https://code.visualstudio.com/insiders
Can you reproduce if you add
"protocol": "inspector"

to you launch.json configuration?
How about if you do
"protocol": "legacy"

I tried reproducing your issue but could not. Could you share a repository on GitHub for which you can always reproduce this issue?

Same problem in insiders:

Good repository to try to reproduce it is https://github.com/EnterpriseJSTutorial/vscode-ts-node-debugging/. I can reproduce at ca02121, all is OK in master (dbf4d8b).

I can reproduce this only on Windows.
@weinand forwarding to you after our discussion

@borekb I cannot reproduce with the given repository in VS Code 1.17 (Insiders) on Windows.
What node.js version are you using?

Just tried on the most recent insiders and the issues is still there:

VSCode Version: Code - Insiders 1.17.0-insider (f7962f0682a76516df51de4856f8ccc5d8ad578a, 2017-09-20T05:24:33.599Z)
OS Version: Windows_NT x64 10.0.15063
Extensions: none

Make sure you try on this specific commit, ca021213cf7393ee56351d581f89b92c4c1f057c.
My Node is 8.4.0.

@borekb ok, then this is a problem of the "inspector" protocol of the node debugger.

@borekb the path ${workspaceRoot}/node_modules/.bin/_mocha points to a shell script, not to anything that node.js can use. The program attribute expects a path to a JavaScript file (or any other source that can be translated to JavaScript).
If you want to run the mocha JavaScript, then you'll have to use this path:
"program": "${workspaceRoot}/node_modules/mocha/bin/_mocha"

(this is actually what you get when loading MASTER from the repository).
Or you can run the "mocha" executable by using the runtimeExecutable:
"program": "${workspaceRoot}/node_modules/.bin/_mocha"

The fact that the error message shows \.bin_mocha instead of \.bin\_mocha is a bug in the error notification (and there is already a bug for it; @isidorn might know which)

@weinand Thanks, that explains it nicely.


ComposableParametersOrdering: Ignore trailing lambda parameters

Currently this rule does not take in consideration the  trailing lambda syntax like, for example, in this composable:
@Composable
fun DatePicker(
    show: Boolean,
    selection: Long? = null,
    calendarConstraints: CalendarConstraints? = null,
    title: String? = null,
    @MaterialDatePicker.InputMode inputMode: Int = MaterialDatePicker.INPUT_MODE_CALENDAR,
    fragmentTag: String = "MaterialDatePicker",
    onNegativeButtonClick: (() -> Unit)? = null,
    onCancel: (() -> Unit)? = null,
    onDismiss: (() -> Unit)? = null,
    onPositiveButtonClick: (Long) -> Unit,
) {}

The parameter onPositiveButtonClick not optional but it's the final parameter of the function to be able to pass the lambda outside of the function call parentheses.

This rule detects such cases when the trailing lambda is a @Composable function — in this case it doesn't check such functions (no sane way to do that), but it doesn't skip non-composable trailing labmdas, because that's what Compose seems to do too: material components always have their onClick, onValueChange, to follow this rule: they always go with the required parameters at the top.
@Composable
fun Button(
    onClick: () -> Unit,
    modifier: Modifier = Modifier,
    enabled: Boolean = true,
    ...
)

@Composable
fun Slider(
    value: Float,
    onValueChange: (Float) -> Unit,
    modifier: Modifier = Modifier,
    enabled: Boolean = true,
    ...
)

etc.
I'm not sure this rule should be changed to always allow required trailing lambdas to come last.
Perhaps a config option could be added for that.
But this also raises the question: what if there are multiple required lambdas? Only one of them should be allowed to come last, the rest are checked as though it wasn't there?

Yeah good point, may I should just move onPositiveButtonClick up.
Btw, thanks for the plugin, these rules are very useful :+1:

Thank you!
If this starts to come up in your (and others') codebases very often, maybe we should revisit this!

Oh, and you can also put @Suppress("ComposableParametersOrdering") on this individual function if this particular case seems like an exception to the general rule :)


Checkbox in TableHead shows checked if data is empty which is confusing on load

Fixes #1301

Coverage increased (+1.6%) to 76.957% when pulling 56f26d87224e89eeff9b2cb04aab59b06bfa5166 on mattcorner:bugfix/unselect-checkbox-when-no-data into 22c462f4f284683a921a3c1050902c0f9f9ab41a on gregnb:v3.

#1301

I agree, and I think your proposed fix would probably solve it. If you put in a PR I can get it into the v3 branch that's currently being worked on.

I think you should meger at v3 branch.

Thanks! Merged into v3 (which should release later this month).


Posts are not shown.

Posts are not shown. Is it still WIP?

It's just a  one-pager template and not suitable for blogs atm. Original template https://html5up.net/stellar and most of the other ports of html5up templates are like that.

I see. Thanks for reply. Showing blog posts is in the roadmap of this theme, right?

I'm trying to make https://github.com/gcushen/hugo-academic theme/framework and stellar to work together for my personal page. Eventually the results of that would propagate here


Clk2clock - rename the implicit "clk" module input "clock"

This applies the chisel naming scheme to firrtl tests.
NOTE - This is implemented as two commits: rename "clk" to "clock" in:

top.cpp and tests that use .fir resource files,
"self-contained" tests that incorporate firrtl source as Strings.

In both cases, memory clock enables are left as "clk", and .fir files in the regress directory are not changed.
There should be no functional firrtl changes.

Can this PR be squashed and merged or should the two commits be preserved?

They could be squashed and merged. I wan't to have the option to do the first (externally visible uses of "clk"), and I wasn't sure if the second should be augment to deal with memory "clk"s.


Prevent adding a trailing slash in a registry URL, as it prevents pulling or

Is your feature request related to a problem? Please describe.
Portainer allows entry of a registry with a trailing slash

However this prevents pulling from it or deploying a stack, service or container that reference it, with an invalid reference format error

Describe the solution you'd like
Omit the trailing slash when we save the registry
Describe alternatives you've considered
Prevent entry of registries with a trailing slash

Greetings @itsconquest ,
Is this issue open to be worked on? I'd love to have a go at it if it is available.
Thank you!

@DarkAEther feel free to work on this one :-)

As per the linked issue, we need to consider whether protocol should be stripped on save. From testing it looks like setting registry.portainer.io without port 443 works so stripping protocol should be fine


fix: compatibility issue with Node.js 12

🔗 Linked issue

#70
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Compatible with lower versions of Node.js
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Hi thanks for PR but i am not sure if we can do it. import.meta is not available in ES2015 and will be entirely removed from dist/index.mjs:
(esbuild plugin) [esbuild] (src/env.ts:7:2) "import.meta" is not available in the configured target environment ("es2015") and will be empty
(esbuild plugin) [esbuild] (src/env.ts:7:2) "import.meta" is not available in the configured target environment ("es2015") and will be empty

Please consider upgrading to a maintained Node.js version.

Hi thanks for PR but i am not sure if we can do it. import.meta is not available in ES2015 and will be entirely removed from dist/index.mjs:
(esbuild plugin) [esbuild] (src/env.ts:7:2) "import.meta" is not available in the configured target environment ("es2015") and will be empty
(esbuild plugin) [esbuild] (src/env.ts:7:2) "import.meta" is not available in the configured target environment ("es2015") and will be empty

Please consider upgrading to a maintained Node.js version.

Thanks for your reply, If we modify the build target "es6" to "node10.4.0" should be able to preserve import.meta and be compatible with more environments.

I think we can keep with es6 for CJS compat 👍🏼  https://github.com/unjs/std-env/pull/74


Allow attaching TTYs to containers

This exposes a new passthrough parameter titusParameter.agent.ttyEnabled, which causes the container to be created with a tty (same as doing a docker run --tty).

Pull Request Test Coverage Report for Build 2223

6 of 20 (30.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 22.851%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

executor/runtime/types/types.go
6
10
60.0%

executor/mock/jobrunner.go
0
5
0.0%

executor/runtime/docker/docker.go
0
5
0.0%

Totals

Change from base Build 2197:
0.02%

Covered Lines:
2456

Relevant Lines:
10748

💛  - Coveralls


WIP: Initial check-in

TODO

[X] - Remote command

[X] - cwd support

[X] - Arbitrary ssh port support

[ ] - https://www.linkedin.com/in/kulathep wants ~/.ssh/config support [Not this round.]

[X] - sudo support

[X] - timeout support

[X] - Password auth support

[X] -  Remote script

[X] - Simple script without libs

[X] - Script with libs

[X] - Arbitrary user creds support

[X] - Remove unused code from paramiko_ssh file (Don't need ShellOutSSHClient)
[X] - Refactor code in RemoteScriptRunner
[X] - Acceptance testing using st2tests [https://gist.github.com/lakshmi-kannan/7e416f7f48c069ea2cc9]
[X] - Make paramiko ssh runner default in dev env
[ ] - Unit tests
[ ] - Documentation
[ ] - Changelog

Examples
General better reporting on connect issues
....
id: 55c2913f32ed35476f1e35ed
status: failed
result:
{
    "localhost": {
        "failed": true,
        "traceback": "  File "/mnt/src/storm/st2/st2common/st2common/ssh/parallel_ssh.py", line 58, in connect
    client.connect()
  File "/mnt/src/storm/st2/st2common/st2common/ssh/paramiko_ssh.py", line 268, in connect
    self.client.connect(**conninfo)
  File "/mnt/src/storm/st2/virtualenv/local/lib/python2.7/site-packages/paramiko/client.py", line 307, in connect
    look_for_keys, gss_auth, gss_kex, gss_deleg_creds, gss_host)
  File "/mnt/src/storm/st2/virtualenv/local/lib/python2.7/site-packages/paramiko/client.py", line 519, in _auth
    raise saved_exception
",
        "succeeded": false,
        "error": "Cannot connect to host. Authentication failed."
    },
    "shit": {
        "failed": true,
        "traceback": "  File "/mnt/src/storm/st2/st2common/st2common/ssh/parallel_ssh.py", line 58, in connect
    client.connect()
  File "/mnt/src/storm/st2/st2common/st2common/ssh/paramiko_ssh.py", line 268, in connect
    self.client.connect(**conninfo)
  File "/mnt/src/storm/st2/virtualenv/local/lib/python2.7/site-packages/paramiko/client.py", line 237, in connect
    for (family, socktype, proto, canonname, sockaddr) in socket.getaddrinfo(hostname, port, socket.AF_UNSPEC, socket.SOCK_STREAM):
",
        "succeeded": false,
        "error": "Cannot connect to host. [Errno -2] Name or service not known"
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Stand alone SSH client tester
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2common/bin/paramiko_ssh_evenlets_tester.py --hosts=localhost,<IP_ADDRESS>,st2build001,st2ops001 --user=lakshmi --private-key="/home/vagrant/.ssh/id_rsa"
{   '<IP_ADDRESS>': [u'/home/lakshmi\n', '', 0],
    'localhost': [u'/home/lakshmi\n', '', 0],
    'st2build001': [u'/home/lakshmi\n', '', 0],
    'st2ops001': [u'/home/lakshmi\n', '', 0]}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Remote command runner
Failure case
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2 run core.remote hosts=localhost,<IP_ADDRESS>,st2build001,st2ops001,cassy1 cmd=date                                                                                ⏎ ✭ ✖ ✱ ◼
...
id: 55c12a6932ed35680b97fed5
status: failed
result:
{
    "st2ops001": {
        "failed": true,
        "succeeded": false,
        "error": "Failed connecting to host."
    },
    "cassy1": {
        "failed": true,
        "succeeded": false,
        "error": "Failed connecting to host."
    },
    "localhost": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 14:11:11 PDT 2015
"
    },
    "<IP_ADDRESS>": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 14:11:10 PDT 2015
"
    },
    "st2build001": {
        "failed": true,
        "succeeded": false,
        "error": "Failed connecting to host."
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Success case
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2 run core.remote hosts=localhost,<IP_ADDRESS>,st2build001.uswest2.stackstorm.net,st2ops001.uswest2.stackstorm.net,cassy1.uswest2.stackstorm.net  cmd=date                                           ✭ ◼
.........
id: 55c13f9b32ed350c78677852
status: succeeded
result:
{
    "st2build001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 22:43:03 UTC 2015
"
    },
    "localhost": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 15:41:46 PDT 2015
"
    },
    "<IP_ADDRESS>": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 15:41:45 PDT 2015
"
    },
    "cassy1.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 22:41:43 UTC 2015
"
    },
    "st2ops001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 22:37:43 UTC 2015
"
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Connecting as specific user and private key for ssh.
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2 run core.remote hosts=localhost,<IP_ADDRESS>,st2build001.uswest2.stackstorm.net,st2ops001.uswest2.stackstorm.net,cassy1.uswest2.stackstorm.net  cmd=date private_key=/home/vagrant/.ssh/id_rsa username=lakshmi
.......
id: 55c143a732ed3512ad468820
status: succeeded
result:
{
    "st2build001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 23:00:16 UTC 2015
"
    },
    "localhost": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 15:58:58 PDT 2015
"
    },
    "<IP_ADDRESS>": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 15:58:58 PDT 2015
"
    },
    "cassy1.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 22:58:57 UTC 2015
"
    },
    "st2ops001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 22:54:55 UTC 2015
"
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ grep "Connecting to host" logs/st2actionrunner.4784.log                                                                                ✭ ✱ ◼
2015-08-04 15:58:47,794<PHONE_NUMBER>69968 INFO log [-] Connecting to host: localhost as user: lakshmi and key: /home/vagrant/.ssh/id_rsa
2015-08-04 15:58:48,069<PHONE_NUMBER>69968 INFO log [-] Connecting to host: <IP_ADDRESS> as user: lakshmi and key: /home/vagrant/.ssh/id_rsa
2015-08-04 15:58:48,365<PHONE_NUMBER>69968 INFO log [-] Connecting to host: st2build001.uswest2.stackstorm.net as user: lakshmi and key: /home/vagrant/.ssh/id_rsa
2015-08-04 15:58:54,159<PHONE_NUMBER>69968 INFO log [-] Connecting to host: st2ops001.uswest2.stackstorm.net as user: lakshmi and key: /home/vagrant/.ssh/id_rsa
2015-08-04 15:58:54,828<PHONE_NUMBER>69968 INFO log [-] Connecting to host: cassy1.uswest2.stackstorm.net as user: lakshmi and key: /home/vagrant/.ssh/id_rsa
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Connecting to remote host with user and password
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2common/bin/paramiko_ssh_evenlets_tester.py --hosts=localhost --user=lakshmi --password=<redacted> --cmd=pwd
"cmd results: \n{'localhost': {'succeeded': True, 'failed': False, 'exit_code': 0, 'stderr': '', 'stdout': u'/home/lakshmi\\n'}}"
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Running remote command as sudo
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2 run core.remote_sudo hosts=localhost,<IP_ADDRESS>,st2build001.uswest2.stackstorm.net,st2ops001.uswest2.stackstorm.net,cassy1.uswest2.stackstorm.net  cmd=date private_key=/home/vagrant/.ssh/id_rsa username=lakshmi
........
id: 55c14edb32ed351f7f0102c5
status: succeeded
result:
{
    "st2build001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 23:48:04 UTC 2015
"
    },
    "localhost": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 16:46:48 PDT 2015
"
    },
    "<IP_ADDRESS>": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 16:46:47 PDT 2015
"
    },
    "cassy1.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 23:46:45 UTC 2015
"
    },
    "st2ops001.uswest2.stackstorm.net": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "Tue Aug  4 23:42:46 UTC 2015
"
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ grep "Running command" logs/st2actionrunner.8065.log                                                                                ⏎ ✭ ✱ ◼
2015-08-04 16:46:43,793<PHONE_NUMBER>79376 INFO log [-] Running command: sudo -E -- bash -c date on host: st2build001.uswest2.stackstorm.net.
2015-08-04 16:46:45,399<PHONE_NUMBER>79376 INFO log [-] Running command: sudo -E -- bash -c date on host: cassy1.uswest2.stackstorm.net.
2015-08-04 16:46:47,006<PHONE_NUMBER>79376 INFO log [-] Running command: sudo -E -- bash -c date on host: <IP_ADDRESS>.
2015-08-04 16:46:48,514<PHONE_NUMBER>79376 INFO log [-] Running command: sudo -E -- bash -c date on host: localhost.
2015-08-04 16:46:50,120<PHONE_NUMBER>79376 INFO log [-] Running command: sudo -E -- bash -c date on host: st2ops001.uswest2.stackstorm.net.
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Specify current working directory -  success and error cases
https://gist.github.com/lakshmi-kannan/c038a9ca5d3521c3d730
Specify arbitrary SSH port - success and error cases
https://gist.github.com/lakshmi-kannan/95a569a0bbc66cdbe843
=============================
Remote script runner
Simple script with no libs
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯ st2 run examples.remote-fib hosts=localhost,shit start=1 end=5  ⏎ ✭ ✱ ◼
.....
id: 55c2837d32ed3520b2ab5dab
status: failed
result:
{
    "localhost": {
        "succeeded": true,
        "failed": false,
        "exit_code": 0,
        "stderr": "",
        "stdout": "1 1 2 3
"
    },
    "shit": {
        "failed": true,
        "succeeded": false,
        "error": "Failed connecting to host."
    }
}
(virtualenv)/m/s/s/st2 git:paramiko_parallel_ssh ❯❯❯

Closing and opening PR against main repo.


md-icon-button hover has no change

Bug
What is the expected behavior?
When hovering an md-icon-button, there should be a circular background around the icon
What is the current behavior?
There is no background change
Which versions of Angular, Material, OS, browsers are affected?
Im using master, on Angular 4

Icon buttons don't have hover state: https://material.io/guidelines/components/buttons.html#buttons-toggle-buttons

weird, they use to and it seemed a bit more user friendly.

It was removed in #3208, presumably to match the spec.

It's is indeed intentional- the spec shows no hover behavior for icon buttons.

That's a shame, it looked really nice.

Google apps like Gmail all use hover state for Icon button lol
https://apps.google.com/u/1/user/hub

You can apply a global style to your application to hover all the mat-icon button.
I did it using Angular theming.
$background: map-get($my-theme, background);

// add hover for mat-icon butttons
.mat-icon-button:hover {
   background-color: mat-color($background, hover);
 }


Bump: Sentry Cocoa & Android

:scroll: Description
Once again, bump Sentry SDKs
:bulb: Motivation and Context
:green_heart: How did you test it?
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #566 (f78028e) into main (c58a920) will increase coverage by 0.60%.
The diff coverage is n/a.

:exclamation: Current head f78028e differs from pull request most recent head 3ecf8a4. Consider uploading reports for the commit 3ecf8a4 to get more accurate results

@@            Coverage Diff             @@
##             main     #566      +/-   ##
==========================================
+ Coverage   91.42%   92.03%   +0.60%
==========================================
  Files          75        7      -68
  Lines        2472      251    -2221
==========================================
- Hits         2260      231    -2029
+ Misses        212       20     -192

Impacted Files
Coverage Δ

dart/lib/src/protocol/sentry_app.dart

dart/lib/src/protocol/sdk_version.dart

dart/lib/src/sentry.dart

dart/lib/src/protocol/sentry_culture.dart

dart/lib/src/sentry_stack_trace_factory.dart

dart/lib/src/utils.dart

dart/lib/src/isolate_error_integration.dart

...t/lib/src/sentry_attachment/sentry_attachment.dart

dart/lib/src/integration.dart

dart/lib/src/sentry_envelope.dart

... and 58 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 c58a920...3ecf8a4. Read the comment docs.


Add benchmarks for endpoint headerfile write

Add some basic testing/benchmarks for writing of the endpoint headerfile. Unlike the real write in runtime environments, these only write into memory rather than the filesystem.
$ make bench TESTPKGS=pkg/endpoint
can't load package: package github.com/cilium/cilium/test/bpf: C source files not allowed when not using cgo or SWIG: bpf-event-test.c elf-demo.c unit-test.c
Starting key-value store containers...
a8a55ad236995b7b9b2591e04404eaf83ffc3a25aec0e5a47a85661871e35ae9
ef0361cd42b30a504183c1936bb2a83300015dc2c5b0f9b0a83dd3c9c96d6c21
goos: linux
goarch: amd64
pkg: github.com/cilium/cilium/pkg/endpoint
BenchmarkWriteInformationalComments-4              50000             25666 ns/op
BenchmarkWriteEndpointConfig-4                    200000             12052 ns/op
PASS
ok      github.com/cilium/cilium/pkg/endpoint   4.287s
can't load package: package github.com/cilium/cilium/test/bpf: C source files not allowed when not using cgo or SWIG: bpf-event-test.c elf-demo.c unit-test.c
cilium-etcd-test-container
cilium-consul-test-container

This change is

test-me-please

Coverage decreased (-0.02%) to 41.882% when pulling f42e2719e5364aec22662ec75921ecb39e10a5b8 on joestringer:submit/improve-ep-write into 3ee527a66ab3be682de8ad9c58c9d6d2ae8af4d4 on cilium:master.

test-me-please


can you add delete method like Get()

I need to delete the field, can you  add a new function To solve this problem
eg :

const json = `{
    "ipinfo": {
        "<IP_ADDRESS>": {
            "info": {
                "admin_code": "330001",
                "city": "",
                "city_name": "",
                "continent_code": "AP",
                "country": "",
            }
        },
        "<IP_ADDRESS>": {
            "info": {
                "admin_code": "330002",
                "city": "",
                "city_name": "",
                "continent_code": "AP",
                "country": "",
            }
        }
    }
}`

json.Del("ipinfo.*.info.admin_code")
// or
json.Del("ipinfo.'<IP_ADDRESS>'.info.admin_code")

Please check out the sjson package. It allows for an easy way to modify json.

thanks


Keys.LAST_DATE_PLAYED is empty, while JoinData is present

I am currently running

SpongeVanilla version: 1.12.2-7.1.0-BETA-121
Java version: 1.8.0_121
Operating System: Windows 10

When getting the last played instant from a user by using user.get(Keys.LAST_DATE_PLAYED), the returned optional is empty, but when getting via the JoinData, via user.get(JoinData.class).get().lastPlayed().get() both are present.
                    User user = UserStorageService#get(uuid).orElse(null);
                    if (user != null) {
                        JoinData data = user.get(JoinData.class).orElse(null);
                        if (data != null) {
                            ...
                        }
                    }

I would have expected Last_Date_Played to be the previous date played. not now. but maybe my memory is rusty.


Clicking a collection in the sidenav on search results page doesn't clear the search term

When on a search results page, if you select one of the navigate away to a collection in the side nav the search term isn't cleared in the searchbox

Selecting a category should clear the search term in the search box

Fixed!


No visualization on Ubuntu 20

Hello! Thanks a lot for your great work.
I tried installing this project on Ubuntu 20.0.4 with ros noetic and met no problems with building the code. However when I tried to play rosbag, it failed to display proper visualization of the map built (yet robot movement could be seen). I tried on an old computer with Ubuntu 18 and ros melodic, and it worked out pretty good. I did see that you have mentioned that test passed on Ubuntu 16 and 18, and I am wondering why it doesn't work on Ubuntu 20?

Sorry for the late reply. Sorry I haven't tried on 20 yet. We will try soon and see if a similar problem occurs.
Btw, is there any error reported? Did you try 'rostopic echo /glb_edt_map' and see if there is data?

It has been found out that a problem of visualization not the code itself is the case. In ROS noetic, it seems that rviz cannot parse frame id "/map" correctly, change it to "map" simply and the problem is solved.
Do something like this:
change _occ_pnt_cld->header.frame_id = "/map";
to _occ_pnt_cld->header.frame_id = "map";

Thanks a lot for your detailed explanation! I will add it to Readme in the next update.

I encontered the same problem. Same with ubuntu 20.04 Noetic.
As @setchin menstioned, I change _occ_pnt_cld->header.frame_id = "/map"; in src/volumetric_mapper.cpp file. (I also changed similar lines, for example _edt_pnt_cld->header.frame_id.) And then run catkin_make. It seems problem still exists.
Then I tried UGV-corridor and UAV-3DLiDAR datasets respectively. The first has no visualization. The second has only the wave of lidar but no mapping.
When the bag is playing, I tried rostopic echo /glb_edt_map but got
WARNING: no messages received and simulated time is active.
Is /clock being published?

So I am wondering whether I changed the right file.

I encontered the same problem. Same with ubuntu 20.04 Noetic.
As @setchin menstioned, I change _occ_pnt_cld->header.frame_id = "/map"; in src/volumetric_mapper.cpp file. (I also changed similar lines, for example _edt_pnt_cld->header.frame_id.) And then run catkin_make. It seems problem still exists.
Then I tried UGV-corridor and UAV-3DLiDAR datasets respectively. The first has no visualization. The second has only the wave of lidar but no mapping.
When the bag is playing, I tried rostopic echo /glb_edt_map but got
WARNING: no messages received and simulated time is active.
Is /clock being published?

So I am wondering whether I changed the right file.

I suppose I did exactly what you have done, changing all the /map to map, no other amendment is made. I only tested uav-depth and uav-2dlidar and both work out fine.

I encontered the same problem. Same with ubuntu 20.04 Noetic.
As @setchin menstioned, I change _occ_pnt_cld->header.frame_id = "/map"; in src/volumetric_mapper.cpp file. (I also changed similar lines, for example _edt_pnt_cld->header.frame_id.) And then run catkin_make. It seems problem still exists.
Then I tried UGV-corridor and UAV-3DLiDAR datasets respectively. The first has no visualization. The second has only the wave of lidar but no mapping.
When the bag is playing, I tried rostopic echo /glb_edt_map but got
WARNING: no messages received and simulated time is active.
Is /clock being published?

So I am wondering whether I changed the right file.

Did you add --clock parameter when you play rosbag?

Yes I run exactly rosbag play ugv-cut-filter.bag --clock __name:=profile_bag to play the bag.
Also, I have some new findings. When I launch the nodes by running roslaunch GIE ugv_dataset.launch, I always receive an error like this:
the provided PTX was compiled with an unsupported toolchain

That is caused by the mismatch between the GPU driver and toolbox versions. So I updated the driver. I did everything again, including compiling cuTT, then this error disappeared. But it still has no visualization.
I notice there is still a warning when I launch the nodes, which may cause the problem.
Local Map initialized
*** stack smashing detected ***: terminated
[GIE_mapping-2] process has died [pid 5723, exit code -6, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2*.log

I am not sure how to take a deeper look on this error. Do you have any suggestions?

I encontered the same problem. Same with ubuntu 20.04 Noetic.
As @setchin menstioned, I change _occ_pnt_cld->header.frame_id = "/map"; in src/volumetric_mapper.cpp file. (I also changed similar lines, for example _edt_pnt_cld->header.frame_id.) And then run catkin_make. It seems problem still exists.
Then I tried UGV-corridor and UAV-3DLiDAR datasets respectively. The first has no visualization. The second has only the wave of lidar but no mapping.
When the bag is playing, I tried rostopic echo /glb_edt_map but got
WARNING: no messages received and simulated time is active.
Is /clock being published?

So I am wondering whether I changed the right file.

I suppose I did exactly what you have done, changing all the /map to map, no other amendment is made. I only tested uav-depth and uav-2dlidar and both work out fine.

Also, I tried uav-depth and uav-2dlidar. Same problem.
Only axes are moving on the screen, with no mapping.
If --clock is removed from the command, even the axes disappear.

In this case, I believe you are having a problem with the code, not visualization. Very likely the problem with GPU. You may try removing CUDA, cleaning envs related to CUDAand resinstall a stable version (11.3 in my case) and compile again. If you are using RTX 30XX. always use CUDA>=11.

Yes I run exactly rosbag play ugv-cut-filter.bag --clock __name:=profile_bag to play the bag.
Also, I have some new findings. When I launch the nodes by running roslaunch GIE ugv_dataset.launch, I always receive an error like this:
the provided PTX was compiled with an unsupported toolchain

That is caused by the mismatch between the GPU driver and toolbox versions. So I updated the driver. I did everything again, including compiling cuTT, then this error disappeared. But it still has no visualization.
I notice there is still a warning when I launch the nodes, which may cause the problem.
Local Map initialized
*** stack smashing detected ***: terminated
[GIE_mapping-2] process has died [pid 5723, exit code -6, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2*.log

I am not sure how to take a deeper look on this error. Do you have any suggestions?

Hi Hao, it seems to be a problem with the software. May I ask if this error (stack smashed) occurs before or after you play the rosbag?

Yes I run exactly rosbag play ugv-cut-filter.bag --clock __name:=profile_bag to play the bag.
Also, I have some new findings. When I launch the nodes by running roslaunch GIE ugv_dataset.launch, I always receive an error like this:
the provided PTX was compiled with an unsupported toolchain

That is caused by the mismatch between the GPU driver and toolbox versions. So I updated the driver. I did everything again, including compiling cuTT, then this error disappeared. But it still has no visualization.
I notice there is still a warning when I launch the nodes, which may cause the problem.
Local Map initialized
*** stack smashing detected ***: terminated
[GIE_mapping-2] process has died [pid 5723, exit code -6, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2*.log

I am not sure how to take a deeper look on this error. Do you have any suggestions?

Hi Hao, it seems to be a problem with the software. May I ask if this error (stack smashed) occurs before or after you play the rosbag?

Before playing the bag, after launching the nodes.

I guess it is because the development environment....  Can you locate which sentence causes the trouble?

I guess it is because the development environment.... Can you locate which sentence causes the trouble?

Yes I run exactly rosbag play ugv-cut-filter.bag --clock __name:=profile_bag to play the bag.
Also, I have some new findings. When I launch the nodes by running roslaunch GIE ugv_dataset.launch, I always receive an error like this:
the provided PTX was compiled with an unsupported toolchain

That is caused by the mismatch between the GPU driver and toolbox versions. So I updated the driver. I did everything again, including compiling cuTT, then this error disappeared. But it still has no visualization.
I notice there is still a warning when I launch the nodes, which may cause the problem.
Local Map initialized
*** stack smashing detected ***: terminated
[GIE_mapping-2] process has died [pid 5723, exit code -6, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2*.log

I am not sure how to take a deeper look on this error. Do you have any suggestions?

Hi Hao, it seems to be a problem with the software. May I ask if this error (stack smashed) occurs before or after you play the rosbag?

Before playing the bag, after launching the nodes.

I guess it is because of the development environment... Can you locate which sentence causes the trouble?

Yes I run exactly rosbag play ugv-cut-filter.bag --clock __name:=profile_bag to play the bag.
Also, I have some new findings. When I launch the nodes by running roslaunch GIE ugv_dataset.launch, I always receive an error like this:
the provided PTX was compiled with an unsupported toolchain

That is caused by the mismatch between the GPU driver and toolbox versions. So I updated the driver. I did everything again, including compiling cuTT, then this error disappeared. But it still has no visualization.
I notice there is still a warning when I launch the nodes, which may cause the problem.
Local Map initialized
*** stack smashing detected ***: terminated
[GIE_mapping-2] process has died [pid 5723, exit code -6, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/29ea4ed6-41b4-11ed-9213-c3ff5c59be87/GIE_mapping-2*.log

I am not sure how to take a deeper look on this error. Do you have any suggestions?

Hi Hao, it seems to be a problem with the software. May I ask if this error (stack smashed) occurs before or after you play the rosbag?

Before playing the bag, after launching the nodes.

I guess it is because of the development environment... Can you locate which sentence causes the trouble?

Well... Do you have any idea on how to locate that?
I am also trying to set the CUDA environment again, but it may take some time.

Problem solved yesterday. Here is the record of process and what happened. It make be helpful who suffer from the same problem. Getting detailed ways to do so should refer to blogs on google.
First when installing unbuntu 20.04, the driver of GPU is already been installed to the computer, but not the newest version. So it seems we only need to install the cuda toolkits. Actually this usually causes error.
There are two ways to do so. The one is installing cuda toolkit from ubuntu repository by simply run the command sudo apt install nvidia-cuda-toolkit. But it cannot install the newest version. Until 2022 October, it can only install 10.1 version. The other way is visiting the website of Nvidia and download a .run file at https://developer.nvidia.com/cuda-11-7-0-download-archive. It provides the newest version. So the second way is recommended.
There are 2 different things may cause the final errors, so do neither of them.
1 Installing from ubuntu repository and official website at the same time. Please only use the second one. Remove the nvidia-cuda-toolkit if it has been installed from command line.
2 Install the drive and toolkits separately. It will probably cause the incompatibility for the driver and toolkits. Please install them together, by simply follow the instruction of that .run file downloaded from the website. If the driver has been installed before (like most of ubuntu 20.04), there will be an error. So the driver needs to be removed first. Unfortunately, some processes may occupy the current driver, for example, Nouveau, making it unsuccessful to remove the current driver. Terminate or disable them first.
The reason why driver and toolkits should be installed together is, there is a requirement for the versions compatibility.
The version of driver should be newer than the version of cuda toolkits.
The version of cuda toolkits should be newer than the computation ability of real GPU.
For example, driver version 515.43 can support toolkits version 11.7. If toolkits version is 10.1, it is ok. If driver version is 435.43, not ok.
Note that nvidia-smi will gives current version of driver, and the version of toolkits that it MAX SUPPORTS (very misleading message here!). nvcc -V can gives the information on current toolkits.
Currently, my version is driver 515.43.04, toolkits 11.7, GPU 1660Ti. The system is ubuntu 20.04, ROS noetic. It succeeds.

Report a solved bug again:
When I run the GIE several days later, the vitalization disappear again.
This time there is error message.
CUDA error at: /home/haostarrr/GIE_ws/src/GIE-mapping/include/map_structure/local_batch.h : 64
no CUDA-capable device is detected cudaMalloc(&_ray_count,_map_volume*sizeof(int))
[GIE_mapping-2] process has died [pid 8702, exit code 1, cmd /home/haostarrr/GIE_ws/devel/lib/GIE/GIE_node __name:=GIE_mapping __log:=/home/haostarrr/.ros/log/f2703b9c-5413-11ed-aa7e-73707b48acb5/GIE_mapping-2.log].
log file: /home/haostarrr/.ros/log/f2703b9c-5413-11ed-aa7e-73707b48acb5/GIE_mapping-2*.log
[ WARN] [1666668508.639461318,<PHONE_NUMBER>.970285238]: Detected jump back in time of 257.106s. Clearing TF buffer.

So i ran nvidia-smi to see the driver.
Luckily I found:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver.
Make sure that the latest NVIDIA driver is installed and running.

See the CUDA by nvcc -V:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Tue_May__3_18:49:52_PDT_2022
Cuda compilation tools, release 11.7, V11.7.64
Build cuda_11.7.r11.7/compiler.31294372_0

So the problem is on the driver.
See the driver version:
ls /usr/src | grep nvidia

I got
nvidia-515.43.04

Then I ran
sudo apt-get install dkms
sudo dkms install -m nvidia -v 515.43.04

Ran nvidia-smi to see the driver again:
Tue Oct 25 11:49:44 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.43.04    Driver Version: 515.43.04    CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   55C    P0    30W /  N/A |      0MiB /  6144MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

Great!!
The problem is probably caused be the linux kernel. When the linux update, the driver cannot adapt to it.
Doing what I did can fix it.

The issue is solved. Thank you.


Use thread context class loader instead to avoid presto exception

Background:
For each connector (e.g. hive-hadoop2), Presto uses an independent PluginClassLoader to load its classes. However, in our dora's client, it also use an ExtensionsClassloader to load the classes for each UFS implementation. Moreover, it breaks the parent delegation and uses ClassLoader.getSystemClassLoader()
as its parent's class loader. So only when the new class loader cannot load the classes, it calls its parent's class loader (ClassLoader.getSystemClassLoader()) to load the classes. However, the classes in ${PRESTO_HOME}/plugin/hive-hadoop2/alluxio-shaded-client-2.10.0-SNAPSHOT.jar is loaded by the PluginClassLoader, but not the ClassLoaders$AppClassLoader. Therefore, Presto throws No under file system factory found exception during the time we are querying with presto-cli.
Solution:
Use Thread.currentThread().getContextClassLoader() instead to set the PluginClassLoader as the parent class loader.

alluxio-bot, merge this please


Support for video tags

Hi there,
I know it's called docusaurus-plugin-image-zoom, but is there a possibility to make this work on video tags as well?
I use mp4 files on my website because gifs are just so darn large and unoptimized, and I would love to have them zoomable.
I tried adding video to my selector config, but it just did not work, unfortunately.
Thanks in advance and thanks again for building this library. (I think I wrote you an email once, mentioning how much i appreaciate this and that it is exactly what I needed.)

Looks like an upstream requirement: https://github.com/francoischalifour/medium-zoom/issues/154


how can I use iis and kestrel same time?

My website delpoy in iis 7.5,,but I need to use WebSocket,so I want to use IIS and kestrel same time,,,normal http request use IIS 80 port,,and WebSocket use kestrel......so,,I want to get kestrel runtime port from iis, it like , when my websocket client application start, send a http request to iis website to get the kestrel port,and use WebSocket Client to connect kestrel to use WebSocket

so....how the IIS know the kestrel server runtme port?

My website delpoy in iis 7.5,,but I need to use WebSocket,so I want to use IIS and kestrel same time

You want browser clients to be able to connect through IIS and directly to Kestrel? This isn't possible since only one of them can use port 80. If you want to use WebSockets when running with IIS, the only supported scenario is to use IIS 8.0 or higher.

When running in the reverse proxy configuration we actively block requests to Kestrel that did not come from IIS.

I saw the Kestrel's log,,,In IIS mode ,Kestrel  only bind <IP_ADDRESS>........so...it can't work...so.....I use SignalR instead it,,,,,,thanks every one

When running in the reverse proxy configuration we actively block requests to Kestrel that did not come from IIS.

https://docs.microsoft.com/tr-tr/dotnet/api/microsoft.aspnetcore.hosting.webhostbuilderiisextensions.useiisintegration?view=aspnetcore-2.2