refuting https://github.com/natpen/awesome-wayland/issues/101

For some reason I'm blocked from commenting on that issue directly?
Wayland support in wezterm does work, but there are some combinations of compositor and wezterm versions that have some issues.
There have been recent changes in nightly builds that improve compatibility with more compositors.
The author of #101 does not represent wezterm and is IMO overstepping in suggesting removal.

I'm rolling around cllsing tabs and just saw this.

For some reason I'm blocked from commenting on that issue directly?

That's a bit unfair you're being directly quoted there. FWIW, it wasn't me!

Wayland support in wezterm does work,

I mean.... you literally said to turn it off, and that meets this list's own criteria for removal, so I'm definitely not overstepping anything by suggesting it.

but there are some combinations of compositor and wezterm versions that have some issues.

Right, maybe like I suggested ITT, if not a removal, a warning is in order. Y'know, some kind of action to avoid a bad experience for users. You want to avoid people having a bad experience, right?

There have been recent changes in nightly builds that improve compatibility with more compositors.

As I said, per haps it should be removed "for the time being". When those changes are released, perhaps things will be different. As the app stands at it's current release, not so much. When you can tell people in issues on your repo that they can fix it by doing X, and it's a rare thing, things might be different. When your official response is 'disable wayland', it's not really "awesome wayland", is it?

The author of https://github.com/natpen/awesome-wayland/issues/101 does not represent wezterm

No, I represent a user of this list who tried wezterm because it's on this list and got his PC all messed up.
That's not what you want for people, right? So some measure should be taken to avoid it, right? "perhaps" a removal "for the time being" or "Perhaps, the app should stay on the list, but with a note added to warn users that Wayland is not officially supported and they may experience bugs?" is hardly overstepping such measures.
Like I said to the other guy, perhaps you'll be more reasonable, let's talk about how to avoid problems for users of this list, rather than how to defend wezterm's removal - those two things aren't mutually exclusive. You don't need to defend wezterm. I said myself, it's the best terminal app out there because it has the best featureset, as far as I'm concerned. But it broke my machine. Let's act like we care when people's machine gets broken, more than we care about an app being on a list.
The other guy provided a grand total of zero suggestions to avoid problems for other people. I like to hope you can beat that record :) I'm all argued out on this one, but I thought you deserved a response, so I'll just unsub and leave it up to you and this list's maintainers to do the right thing by others.

There's a difference between recommending a course of action and something not being supported.
Just because I recommend not using wayland to folks that want a simpler experience overall does not mean that wayland is unsupported.
I think it is a bit strong for you to open an issue petitioning for removal of a project when your experience does not represent the experience of the majority of its userbase, and to block me from commenting on that issue.
You're taking my words out of their complete context, and that is what led me to open this issue.

But it broke my machine. Let's act like we care when people's machine gets broken, more than we care about an app being on a list.

wezterm cannot break your machine.  I do care about the experience of my users, but if their response is to not to engage with the community on their issues and instead petition against the project, what am I to do?
This forum is not the appropriate place to discuss wezterm issues. If you'd like to open an issue in the wezterm repo we can follow up specifically on what you encountered; I'm sure the owner of this repo would appreciate not having so much drama here.

There's a difference between recommending a course of action and something not being supported.

When that recommendation is to not support it and is the only resolution, no, there's not a difference.

I think it is a bit strong for you to open an issue petitioning for removal of a project when your experience does not represent the experience of the majority of its userbase

This isn't about your userbase, it's about this project's userbase. It doesn't matter how many people are dong just fine, if there's a real risk that you will have problems, which there clearly is given all the cases about it (you said yourself they are "numerous") and all the commenters (keep in mind how many people are reading it because they had the same problem and NOT commenting because it would be redundant/spamming/nagging, like I was) then something should be done to avoid that happening to someone.

to block me from commenting on that issue.

I literally just told you that I didn't do that and I thought it was unfair. It's literally the first thing I said to you. I try to do you the respect of having the conversation you were blocked from, and you don't even do me the respect of reading what I wrote.

You're taking my words out of their complete context

I literally linked to them, there couldn't be any more context.

wezterm cannot break your machine

It can and did. I had to kill it from a TTY to get my system to respond.

I do care about the experience of my users

And what of the users of this list? This isn't about wezterm, you gotta stop being so defensive and think about other people, you're doing the same thing the other guy did.

if their response is to not to engage with the community on their issues

You want me to create a dupe of a case you already directly responded to with a conclusion? There was no engagement necessary, in fact, it'd only have been spamming/nagging if I had. Others who did engage with you on the topic had their cases closed as dupes, and rightly so.

and instead petition against the project, what am I to do?

I'm not petitioning against that project, I'm petitioning FOR users of THIS one. Not a single thing said by any of you has been anything that would be a change to provide a better experience for people here. All you care about it wezterm and think this is all about wezterm. It's not, it's about people who read this list.

I'm sure the owner of this repo would appreciate not having so much drama here.

And so would I.
So stop making it and come up with a solution for users of this repo to not have a bad experience trying something that is known not to work. All you guys do is argue and defend wezterm and you do zero to come up with an actual helpful solution. I understand you care about your project. It's bloody amazing and obviously still getting better, you have surely worked incredibly hard on it, and defending your 'baby' it is the right and admirable thing to do. But not to the point that it comes at the expense of others. You should be very proud of it, but your pride is so excessive that it's getting in the way of you being considerate. I had hoped that unlike the other guy you'd try and be productive in finding a way for others to avoid a bad experience, such as the numerous alternatives I've come up with, but again all I'm getting is arguments that clearly come from massive bias.

This forum is not the appropriate place to discuss wezterm issues

It's not, and I'm not. I don't need to, since that discussion already occurred, several times, I linked to it. I'm discussing an issue with this list, which is that it gave advice that caused me a problem. You're so busy trying to defend wezterm that you're incapable of considering other people and it's not cool. You can change that if you like. It starts with something like"
"Wow bro that sucks I'm sorry you had a bad time and I wouldn't want that to happen to someone else either, because I care about you and them. I'd really like wezterm to stay on this list though, I've worked really hard on it and it's place on this list means a lot to me, and like you say, it could be good for some people - but I recognise there's a problem, so instead of removing it from this list, how about we (fill in this blank with something that isn't about saving wezterm from a short vacation from this list and is about saving some random internet person from having a bad time)"
You could do that. You could care about other people as much as your project and find a mutually beneficial solution instead of making "drama". In theory.

Hi 👋  I've just finished reading through both this and the other thread. First of all, thank you for the thorough and thoughtful discussion. It's obvious that the discussion is getting a bit "frayed around the edges" in spite of the fact that many good points are being made all around. I think the fraying around the edges is because it touches on a fundamental challenge of maintaining a list like this - it's intended to be useful and helpful to people, but it's hard to objectively define and quantify "useful" and "helpful". I've personally grappled with this over the years, and often end up just trying to make reasonable inclusion/exclusion calls, rather than put a ton of effort towards codifying the criteria. Sorry you all had to get pulled into that dilemma with me this time!  And @wez sorry you couldn't comment on the other issue - I'll double check commenting permissions right after I finish this comment.
Questions I'm thinking through...
Does Wezterm support Wayland? I think the answer is yes - it says so in the official docs, and there is a large body of work in the code that appears to have gone into Wayland support. I realize there's a quote floating around here of @wez saying he personally recommends not using Wayland, but it's fine to have a personal stance and advice at odds with the Repo's stance.
Does Wezterm "work" for a reasonable enough amount of users? This is really hard to answer, even for @wez I'm guessing. (WARNING: wild hand-wavy math incoming! :) It has over 10k stars, so it's a popular project and I'm guessing thousands of users. Looking at issues labelled wayland I definitely see some "it doesn't even start" kinds of ones, but just comparing the number of them to the number of Wayland users I'm speculating exist, I am guessing that severity of issue is affecting a minority of users (though it does look like it has an uphill battle due to the SCTK upgrade that isn't able to be worked on).
Possible solutions...

We could remove Wezterm from this list entirely. That feels... not good to me, and unfair to @wez and team, given the above answers.

We could put a warning/disclaimer next to Wezterm on this list. That could work, but isn't really an approach I want or precedent I want to set for the sake of maintaining this list.

Lastly, here's my idea, taking a step back from Wezterm specifically. Looking at the two other GPU-accelerated ones on the list, I see some similar issues (ref: alacritty issues & kitty issues). I could add a somewhat more general blurb at the top of the Terminal Emulators section that notes that GPU-accelerated terminals are often more bleeding edge or ambitious endeavors, so take care when going down that route and be ready to potentially troubleshoot your way through getting things working.

Thank you again for all the discussion so far! Please feel free to let me know it you're opposed to solution (3) or have other ideas. I'll think through this some more today and let it percolate, to see if any other good ideas come to mind.

've just finished reading through both this and the other thread.

Appreciated, and apologies for all the 'frayed edges' you've waded though.

Possible solutions...
1. We could remove Wezterm from this list entirely. That feels... not good to me, and unfair to @wez and team, given the above answers.

Agreed.

2. We could put a warning/disclaimer next to Wezterm on this list. That could work, but isn't really an approach I want or precedent I want to set for the sake of maintaining this list.

Smart move.

3. Lastly, here's my idea, taking a step back from Wezterm specifically. Looking at the two other GPU-accelerated ones on the list, I see some similar issues (ref: [alacritty issues](https://github.com/search?q=repo%3Aalacritty%2Falacritty+wayland&type=issues&s=created&o=desc) & [kitty issues](https://github.com/search?q=repo%3Akovidgoyal%2Fkitty+wayland&type=issues&s=created&o=desc)). I could add a somewhat more general blurb at the top of the [Terminal Emulators](https://github.com/natpen/awesome-wayland#terminal-emulators) section that notes that GPU-accelerated terminals are often more bleeding edge or ambitious endeavors, so take care when going down that route and be ready to potentially troubleshoot your way through getting things working.

That ought to do the trick! I hope @wez would find that agreeable. If not, I'm sure we can find some other solution if we work together toward it.

Thank you again for all the discussion so far! Please feel free to let me know it you're opposed to solution (3) or have other ideas. I'll think through this some more today and let it percolate, to see if any other good ideas come to mind.

No, thank you. I just wanted to solve a problem for random interwebs user #6480 and you ended up having to read a novella. I do appreciate the effort.

Thanks @natpen, I think option 3 is reasonable.
The other options are undesirable because the reality is that so much about software is ephemeral as various dependencies are changed and updated.  For example, for much of the past month I've been unable to run a video call more than once per reboot due to some weirdness after running a routing software update on Fedora 38.  Does it mean that Fedora should be removed from a hypothetical list of systems that can be used to make video calls? I don't think so.
Furthermore, if you single out a piece of software it is then a burden on someone to identify/track and update and maintain that listing, and I think we can agree that no one really has time for that.

There are no outstanding Wayland issues in kitty and haven't been for a
long time. And not a single report of it not starting.
The ONLY Wayland specific issue it has is CSD on GNOME.
There is nothing about GPU based terminal emulators that makes them
Wayland antagonistic, and it is pretty absurd to label a whole category
of software as not ready for Wayland because of one example of it.
Not to mention completely unfair to those of us who have sunk countless
hours of our time into supporting the ongoing trainwreck that is
Wayland. If you want to maintain a list of software that works on
Wayland, I suggest putting in some actual work to verify and curate that
list or maybe stick a big disclaimer on top of the entire list that
states you have no idea how well or if any of the software currently
works in Wayland.

It seems as though, in a search for a solution, we've fallen afoul of tarring one project with another project's brush. Sorry @kovidgoyal, I've been using kitty without any technical problems at all on Wayland for some months. It's only the no scrollbar design that has made me leave it. So I don't like to see kitty being unfairly labelled. It's good, working software, as evident from my own experience, and also from your short issues list.

3. taking a step back from Wezterm specifically. Looking at the two other GPU-accelerated ones on the list, I see some similar issues (ref: alacritty issues & kitty issues).

I must confess that I read this and took it on face value but didn't click the links, when I agreed to the proposed solution. If we filter those lists by open cases it's clear that Kitty is not really worthy of a warning blurb. Likewise I looked at foot, another GPU-accelerated terminal I've decided to use (so far without problem) and the issue list contains only one open wayland-related case, which has a workaround in place and seems moments from being resolved.
Given this new (to me) information I no longer feel that the blanket warning for all GPU-accelerated projects is appropriate. Having looked a little deeper, I really think it's unfair to label all the GPU-accelerated terminals with the same warning, when it appears that warning is only really appropriate for two of them.
But, as Kovid put it, to "verify and curate" the list might be something which would cause excessive load on @natpen. It's good to have a list like this, good for the whole community, and it would be a shame to have the list become an excessive load on its maintainer.
Perhaps the best thing here is to spread that load across a wide base - by delegating confirmation of the functionality of the software, to the users of the list. In other words, as Kovid put it, "maybe stick a big disclaimer on top of the entire list", that users of the list (ie, people like me) should check the issues list of any software they intend to try, to confirm that it will suit their requirements, before they install it. This achieves the goal I have in mind of avoiding a bad time for users of the list, without specifically pointing out any individual apps as being problematic, which avoids the problem that @wez and other software developers would have of being deemed unworthy of being on the list, and avoids an excessive load on @natpen so that his list can stay here for the benefit of the community.

Thanks, everyone. I like the suggestion to just add a bolder disclaimer to the top of the list, and have just done so!


Replace deprecated functions

Since Erlang 24 deprecates crypto:hmac/3 I guess it's time to replace it with the new api.
Added bxor/2 as a bonus.

Thank you!

Hi everyone,
This is great,
Do you know when is gonna be release?
Thank you!

Let me think about it, because not everyone can use OTP 24. Maybe we use a conditional guard for compiling OTP 23.x and OTP 24.

New release for OTP 24: https://hex.pm/packages/mongodb_driver


Make iterall a runtime dependency

Fixes #625
Iterall is used in runtime code (e.g. https://github.com/apollographql/graphql-tools/blob/2868fe26266623dcb4a906c6450ccedbd10d62dc/src/stitching/observableToAsyncIterable.ts) but isn't a dependency. That means unless you happen to have it installed for some other reason, graphql-tools is unusable right now.

Thanks!


Systems without apt or rpm can't manually say "yes I have wmctrl"

I'm trying to add a check for pacman that mirrors the RPM check as we speak, but running into build issues with node and such; seems newer node and whatever version of nan is used are incompatible for some reason.  If I get it sorted I'll PR the pacman check, but I'm not familiar with this ecosystem so I won't be able to add some sort of a check box the user can tick to say "I have wmctrl even though you don't know how to check for it on my system".

Turns out I can install nodejs-lts-carbon on Arch and that fixes the build issues; now to see if my hacky copypasta fixes the issue at hand.

If it works, feel free to contribute this.
That being said, if wmctrl is installed it should work regardless of whether the dependency check shows an error in the GUI or not.

Indeed, I'm on Arch and while there is a warning about missing wmctrl - it works.

It didn't, so I just hacked around it in a different (and totally not ok to PR) manner.
At some point I should figure out why it won't display over top of PoE though; it does fine over top of everything else, but fullscreen and windowed-fullscreen apps it doesn't seem to want to go over top of.  That's a separate issue (if it's an issue with this and not my setup) though.
I suppose since it works despite the dependency warning then it's probably fine to close this issue, so I shall.

I'm reopening this issue as I think adding a dependency check for Arch would be a good addition in order to avoid confusion.
Now, I don't use Arch and never have, would someone be able to execute the command with wmctrl installed and uninstalled and let me know the outputs?
pacman -Qi wmctrl
Thanks!

pacman -Qi wmctrl
Name            : wmctrl
Version         : 1.07-5
Description     : Control your EWMH compliant window manager from command line
Architecture    : x86_64
URL             : http://tripie.sweb.cz/utils/wmctrl/
Licenses        : GPL
Groups          : None
Provides        : None
Depends On      : glib2  libxmu
Optional Deps   : None
Required By     : None
Optional For    : inxi
Conflicts With  : None
Replaces        : None
Installed Size  : 38.00 KiB
Packager        : Felix Yan<EMAIL_ADDRESS>Build Date      :
Install Date    :
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

pacman -Q wmctrl
wmctrl 1.07-5
pacman -Q wmctrl
pacman -Qi wmctrl
error: package 'wmctrl' was not found

I think a better solution (because whack-a-mole with package managers will be annoying I'm sure) would be to have a config panel where the user can specify "yes I have  installed and optionally the path to it is </path/to/blank>".

I will probably add an option that simply lets you disable showing dependency warnings overall. You're absolutely right, I definitely can't add a check for every package manager out there. But I feel like Arch Linux is big enough to justify adding a check for that specifically.

I mean...if you're calling wmctrl (or other deps) using the binary anyway
and assuming it's in $PATH then just do which wmctrl and check the output
of that.
On Sun, Sep 16, 2018 at 4:28 PM Tobias Hoffmann<EMAIL_ADDRESS>wrote:

I will probably add an option that simply lets you disable showing
dependency warnings overall. You're absolutely right, I definitely can't
add a check for every package manager out there. But I feel like Arch Linux
is big enough to justify adding a check for that specifically.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/klayveR/xenontrade/issues/7#issuecomment-421827305,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE3k5kZlmPWzMGtOZBe9Q6K7do-nKv0kks5ubrSLgaJpZM4WqFpn
.

--
Thomas Winget

I can't believe I didn't think about that. Definitely the best solution, thanks!

This is implemented in v0.3.5. Feel free to reopen this issue if the problem wasn't fixed for you. Thanks for all the help!


[Bug] [Seatunnel-web] HiveJDBC should not be used as a sink datasource

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
HiveJDBC is available sink datasource. It should not be available as sink datasource.
SeaTunnel Version
2.3.7
SeaTunnel Config
NA

Running Command
NA

Error Exception
NA

Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

PR is merged
https://github.com/apache/seatunnel-web/commit/2c09444ce3255bcaf5abf06916ab779fac131a82


chore(main): release 2.7.0

:robot: I have created a release beep boop
2.7.0 (2024-08-21)
Features

cli: use of preset account if cloud info missing (#278) (84293bf)

Bug Fixes

cloud: meiju cloud download_lua appliance_type error (#281) (54f1bf4)

This PR was generated with Release Please. See documentation.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 37.78%. Comparing base (84293bf) to head (99a536b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #279   +/-   ##
=======================================
  Coverage   37.78%   37.78%
=======================================
  Files          84       84
  Lines        7472     7472
=======================================
  Hits         2823     2823
  Misses       4649     4649

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:robot: Created releases:

v2.7.0
:sunflower:


FlowRouterMeta is not defined

I initialised FlowRouterMeta and FlowRouterTitle like this:
new FlowRouterMeta(FlowRouter);
new FlowRouterTitle(FlowRouter);
at the end of my routes.js but still get a error log:
W20161019-03:57:57.510(2)? (STDERR)
W20161019-03:57:57.511(2)? (STDERR) ReferenceError: FlowRouterTitle is not defined
W20161019-03:57:57.511(2)? (STDERR)     at meteorInstall.lib.routes.js (lib/routes.js:96:5)
W20161019-03:57:57.511(2)? (STDERR)     at fileEvaluate (packages/modules-runtime/.npm/package/node_modules/install/install.js:153:1)

Packages:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>aldeed:simple-schema
<EMAIL_ADDRESS>meteortoys:allthings
<EMAIL_ADDRESS>ostrio:files
ostrio:flow-router-extra
ostrio:flow-router-title
ostrio:flow-router-meta
kadira:blaze-layout
<EMAIL_ADDRESS><EMAIL_ADDRESS>

It should be done on Client only. It's Client only libs

Please, support this project by:

Star on GitHub
Star on Atmosphere


404 on miniorange Rest API

I had tested the miniorange REST API concept before.
but it stopped working. the xmlrpc is functional
I use version 2.4.0 on miniorange and 0.5.0 on Wordpress publish.
It did work before. So i am not sure what happened.
app.js:1 Uncaught (in promise) Error: Request failed, status 404
at new t (app.js:1:1454507)
at VN (app.js:1:1454662)
at app.js:1:1455339
at app.js:1:235078
at Object.next (app.js:1:235183)
at s (app.js:1:233922)
t @ app.js:1
VN @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
s @ app.js:1
Promise.then (async)
step @ plugin:obsidian-wordpress:65
fulfilled @ plugin:obsidian-wordpress:53
Promise.then (async)
step @ plugin:obsidian-wordpress:65
eval @ plugin:obsidian-wordpress:66
__async @ plugin:obsidian-wordpress:50
eval @ plugin:obsidian-wordpress:23994
eval @ plugin:obsidian-wordpress:21949
(anonymous) @ app.js:1
the link the in console looks like the URL ist both API endpoint put together
like
wp-jason/wp/v2/postswp-jason/wp/v2/categories
hope this helps in understanding the probem

404 means the URL not found.
It seems you set wrong WordPress URL in settings dialog. The URL should be something like "https://blog.example.com/" but yours seems to be "https://blog.example.com/wp-json/wp/v2/posts" thus "wp-json/wp/v2/categories" append to the incorrect URL result as "wp-json/wp/v2/postswp-json/wp/v2/categories".


make 'headers' key in event optional

as in some case (especially right after a new release ?) api gateway does not seem to send the header key in the event

Worth noting: there are still a couple of places calling event[key] rather than event.get(key, fallback).  We should consider making assertions about the keys on event where specific keys are crucial and using event.get elsewhere.

Looks good, thanks.

thanks a lot to you for this library:)


Handle the error when user selects non-existing columns in the table

Fixes #70
Tests with unit-tests and psql as below.
psql (12.1, server 0.0.0)
Type "help" for help.

asongala=> create schema schema_name;
CREATE SCHEMA
asongala=> create table schema_name.table_name (column_in_table smallint);
CREATE TABLE
asongala=> select column_not_in_table from schema_name.table_name;
ERROR:  column "column_not_in_table" does not exist

@alex-dukhno Please help review the code. Thanks.

Hi @alex-dukhno , I could fix to let thiserror format the error message as below.
pub enum QueryError {
...
    #[error("column {0:?} does not exist")]
    ColumnDoesNotExist(Vec<String>),
...

The interaction error message will be:
xxx=> select column_not_in_table from schema_name.table_name;
ERROR:  column "["column_not_in_table"]" does not exist

I think it is not the right message you expected. Could you help give the template message of this error? Thanks.

Seems like I misunderstand again 😅
thiserror formatting is used only in tests in sql_engine and user facing message is formatted here https://github.com/alex-dukhno/database/pull/74/files#diff-13fa0b4f67547213dbcccde5cd778787R165 🤦  😄
so can you adjust user facing message

if single column to

ERROR:  column column_not_in_table does not exist

if more than one

ERROR:  columns column_1_not_in_table, column_1_not_in_table does not exist

thanks

You don't need to change latest changes for QueryError
    #[error("column {0:?} does not exist")]
    ColumnDoesNotExist(Vec<String>),

it is good for debugging in tests, Thanks

Hi @alex-dukhno , the CI has passed, please help review the latest code. Thanks.

Hi @alex-dukhno , sorry for my bad understanding. I fixed the code according to your suggestions. Please help review the code. Thanks.

I added small suggestions and applied to PR and merged. Thanks for contribution


Fix accept loop exception handling

bors r+

bors r-

@coot Cancelled bors because the tests seem to loop with this PR, causing Hydra to time out and bors to stall all other PRs. Sorry.

bors r+


internal/providers/oracleoci: initial implementation

Adds an initial implementation for the oracle-oci provider.
Tested attributes, ssh keys, and hostname manually on an oracle VM.
Fixes https://coreosdev.atlassian.net/projects/OST/issues/OST-40?filter=allopenissues
cc @bgilbert

This will eventually need an -sshkeys unit added to Ignition's oem.go.
Do we plan to parse IP addresses out of the lease data?

I've got the code written to do that if we want, the information isn't available on the metadata server.
@crawford do you have thoughts on which is better: parsing lease data for IP addresses, or not including the information?

I would not include it unless we know for certain. It sounds like we won't be able to know which interfaces are which and what the public IPs are going to be, which makes me think we should hold off for now and add the functionality once the platform supports it.

After talking with @crawford we're going to not set the hostname here and just leave it as localhost as a result. If the information ever becomes available via DHCP or the metadata server, then we can set it.

I've also added a couple more things that seemed like they could be useful to the attributes.


Wiki Page

Create a Wiki Page for the project.
Anyone who wants to work on this issue under GSSOC21, comment here and I'll assign it to you.
You can refer : https://guides.github.com/features/wikis/ for getting more info on Wiki Pages.

Create a Wiki Page for the project.
Anyone who wants to work on this issue under GSSOC21, comment here and I'll assign it to you.
You can refer : https://guides.github.com/features/wikis/ for getting more info on Wiki Pages.

Hello @HimeshNayak , I want to work with it..... Can you give me a sample idea, how I can design Wiki page for that project...I already gathered knowledge on github wiki.... Thanks

Hey @SamarpanCoder2002
Create a Wiki Page for this project describing:

What this Project is?
Purpose of this Project
Issues it would solve
Short and Precise description of all Features, this app currently has.

You can check the guide material:

Writing and Formatting on GitHub
Wiki page

I have created the wiki page. Here is the link
https://github.com/avinashkranjan/Friday/wiki
@SamarpanCoder2002 you can add content to it as described by @avinashkranjan

Hey @SamarpanCoder2002
Create a Wiki Page for this project describing:

What this Project is?
Purpose of this Project
Issues it would solve
Short and Precise description of all Features, this app currently has.

You can check the guide material:

Writing and Formatting on GitHub
Wiki page

Thanks @HimeshNayak  @avinashkranjan for give me that sample.... I will start work on it soon

Hello @avinashkranjan @HimeshNayak , I already made Wiki pages for this project.... But I don't understand how to make a pull request about this wiki pages..... Should I put the md file as one of project file and then make pull request or not???? Please let me know.... Here's my wiki pages: https://github.com/SamarpanCoder2002/Friday.wiki.git
Thanks  u @HimeshNayak @avinashkranjan

Yes, add it in a md file and submit the PR mentioning this issue.

Yes, add it in a md file and submit the PR mentioning this issue.

sure


Force creation of symbolic link

What problems does this PR solve?
The create_lims_integration_links task would fail if a link already existed, this PR will solve this issue.
How has the changes been tested?
No, but will be tested in the staging environment.
Reasons for careful code review
If any of the boxes below are checked, extra careful code review should be inititated.

[ ] This PR contains code that could remove data

Looks good.
Just to make sure: what if the link exists, but pointed somewhere else? That is not a scenario we have to worry about, right?

Looks good.
Just to make sure: what if the link exists, but pointed somewhere else? That is not a scenario we have to worry about, right?

I would say that our general "policy" in this workflow is that the most recent run should be the valid one, so I don't see any problem with overwriting, even if the former link pointed somewhere else (which should be very unlikely).

Right, that's what I thought.


Using dfs endpoint

For my ADLS2 blob I only have a dfs endpoint configured as a private endpoint.
When trying to list folder/files in a blob I get a HttpResponseError.
HttpResponseError: This request is not authorized to perform this operation.
RequestId:00f7171a-201e-0039-6842-f5ecb8000000
Time:2021-01-28T06:54:33.4368226Z
ErrorCode:AuthorizationFailure
Error:None
Trying to set fs.account_url = "https://{}.dfs.core.windows.net".format(os.environ['AZURE_ACCOUNT_NAME']) also does not result in communication via the dfs endpoint.
If I allow access from all networks on my storage account I'm able to connect.
I'm making the connection via a service principal.
fs = AzureBlobFileSystem(account_name=xxxx,                                           tenant_id=xxxx,                                           client_id=xxxx,                                            client_secret=xxxx)

Any thoughts?

@wielrenner How did you solve this or did you create a workaround?


Move time to outer loop in result flattening

Hello!
Consider this example code, which should be copy-pasteable once the package registration process is completed.
It solves a PDE advection equation, using a wind fields pulled from an external file. However, there are a couple of issues.
The first issue is that—in use many cases—the data being loaded won't fit in memory, so the data loader uses a caching system that assumes an integrator that takes sequential steps in time (i.e. it's assume time is in the outer loop). This works fine until the integrator finishes and starts calculating the observables (here). In that function, time ends up being the inner loop, resulting in the data loader making a large number of unnecessary reads from disk. The result of this is that the integration process in the example above takes 30 seconds or so and then it takes 30 minutes or so to calculate the observables.
To solve this first issue, the first commit moves time to the outer loop in the observable calculating function. This improves the situation for the example above and also makes things more consistent for other data loaders and interpolators which will in general be assuming that data is accessed with time in the outer loop.
However, a second issue remains, which is that for the system above solve still spends the vast majority of the time calculating observables, but now it's mainly doing compilation here and (especially) type inference here.
The second commit below tries to improve this situation by using broadcasting instead map. It doesn't help with the speed at all, but I thought it at least makes the code a little more clear.
Let me know your thoughts!

This looks like an acceptable change, how does it affect performance for other cases? could you run an AB benchmark for a few cases just to see how this stacks up?

That issue you posted is the reason I decided to batch calls to the observed to get the whole time slice at once, as they are optimised for this kind of call

Thanks for your response!
For my use case, it is currently too slow to be useable without this PR, but it's also too slow to be useable with this PR, so I'm not too attached to this particular PR getting adopted. I'm still trying to wrap my head around everything that's going on here, but so far it seems the issues might be:

The time step is in the inner loop in the observables, which doesn't work well with data loaders optimized for time being in the outer loop (which is the focus of this PR)
(It seems like) Observables aren't calculated in the order of dependency, so the data loader gets called multiple times for the same variable when calculating the observables.
Observables are calculated eagerly, which results in wasted time if there are many or computationally intensive observables that the user isn't ultimately interested in (e.g. something from a data loader or variables that only serve as connections between subsystems)
Theres a custom function generated for every observed variable at every grid point, with compilation time that adds up when there are a lot of observables
The observed function isn't statically typed, which requires type inference that adds up when there are a lot of observables and/or grid points.

Let me know if you think these may be actual issues going on here, or if I'm misunderstanding something. Thanks!

No, that's a pretty good summary of the current issues with observables. I'm currently working on an ability to save only subregions of the domain, with requested observables saving only their dependencies. I hope this will lead to better observable handling overall. This handles 2 and 3. It may also speed generation and compilation to build the observed functions with only their dependencies, which should put a dent in 4 with any luck.
With handling for array variables in MTK which may be coming soon, there may be some improvements since observables often have patterns and occur in patterned subregions of the domain for PDEs. We should be able to take advantage of this fact to generate single functions that calculate a whole region of observables, putting a dent in 4 if all goes well.

Thanks!
With regard to 1, just so I understand, I thought that how the ODE solvers work is that they solve for all variables at t=1, then they solve again for all variables at t=2, then they solve again for all variables at t=3, and so on, so the native way to store the results would be time-major, or having time in the outer loop.
For example, when I look at the output (e.g., sol.u where sol is the name of the result of solve) it is in the form of a vector of vectors, where the outer vector has an element for each time step, and each inner vector has an element for each state variable. So time is in the outer loop, and the variables are in the inner loop.
Am I understanding that incorrectly? Thanks for your help!

I'm a bit torn on whether this is necessary. The working that MTK will do is not necessarily the same as the ordering generated by the stenciling code, since it can re-order at will (and will for some transformations). I think it is still a good idea though, since this gives "the right" ordering by default for a column major structure. It will not necessarily have a trangible effect unless preserved through, and the structure preservation of course is a (the) ongoing project.


NuGet

Do you have plans to put this library on NuGet? Thanks.

This is generator. Better not this project, but chrome-dev-tools-sample, please.
And maybe change names: chrome-dev-tools => chrome-dev-tools-generator, chrome-dev-tools-sample => chrome-dev-tools. ChromeDevTools is used in MasterDevs/ChromeDevTools . It would be great. Your project is more usefull for me.

Yes, I was thinking about the sample / generated project. I also agree on the name, but that's a decision for @Oceanswave
I looked at  MasterDevs/ChromeDevTools as well, but I needed version 1.2 so I went with this one.

Great ideas! The name change will clear up some confusion too I think.
I kinda wanted folks to be able to generate their own wrapper, but if the easier path is to have a nuget library, I'm totally with that.
Let me find some time and knock some of these out.

I use chrome-dev-tools-sample in AsyncChromeDriver and have NuGet. You can get all functionality. Thanks to @Oceanswave
But it is for .NET Framework. I think, I'll wait for .NETStandard 2.0.

So thanks to your ideas @ToCSharp I've renamed this project to chrome-dev-tools-generator and the sample project to chrome-dev-tools-runtime, will work on putting that project on github.

I've published the runtime library to nuget at the location below. It should show up after the package is indexed.
https://www.nuget.org/packages/BaristaLabs.ChromeDevTools.Runtime/
Thanks all!


Don't curtail X509 proxy lifetime in DAGs

This closes #179, implementing the JDF classad attribute needed to not curtail X509 proxy lifetime in DAGs.  We already did this for regular jobs in #186.
@marcmengel - could you please test this on a dataset DAG?  I did already for a regular DAG, but I'd like to make sure this doesn't break more complex stuff.  Thanks!

Thanks Marc!


Update the readme

@sduskis please review
@hegemonic please review

Looks fine aside from my minor comment.

I'm going to merge based on Jeff's comment - I fixed the button.
Solomon -- please give feedback.


CAPT 1638/migrate sign in or continue to journey session

Migrate sign in or continue form to write to the journey session
Updates the sign in or continue form to write it's answers to the journey session.
The sign in or continue form sets the teacher_id_user_info attributes and the dqt_teacher_status attributes. These attributes are used through out the app and so, unfortunately, there wasn't a good way to break this PR up.
High level overview of the changes:

Retrieving the DqtRecord is now the responsibility of the SessionAnswers and we now need to be specific about which policy we want to access the DqtRecord for.
Accessing the TPS data is now the responsibility of the JourneySession¹
The methods TeachersPensionsService.has_recent_tps_school? and TeachersPensionsService.has_tps_school_for_student_loan_in_previous_financial_year? have been removed. It's now up to callers of TeachersPensionsService.has_recent_tps_school and TeachersPensionsService.has_tps_school_for_student_loan_in_previous_financial_year to check the presence of the result, which allows us to cache the answer and avoid an extra query.
The sign in or continue form still writes the personal details attributes to the current claim, as well as the journey session. This is called out with a FIXME comment but is just a temporary fix, until we tackle the personal details form, to avoid having to change even more in this commit.²
We've added a temporary hack to the qualification details initialiser, again called out with a FIXME, to avoid having to change that form too.²
There's a few other FIXME comments added where I think we can simplify the current implementation but they've been left as comments at the minute to avoid introducing any risk

¹ - This would be a better fit on the SessionAnswers model but we need access to the created_at time stamp.
² - I'll tackle these two tickets next

A note on the implementation of JourneySession and SessionAnswers: There's quite a few places where you just want to work with the answers only but have to go through the journey session in order to be able to save changes, additionally not having a created_at timestamp on the SessionAnswers means some methods that naturally belong on there need to be on the JourneySession instead. Once we've migrated all the forms over to write answers to the JourneySession I think we should take a look at storing the answers in a table rather than a json column and removing the JourneySession instead having something like Journeys::JourneyName::AnswerSet which has a column for each answer, and something like a delegated_type if we want to share the claim fields between the journey models. Hopefully the active model attributes should make it relatively straightforward to switch out how we're persisting the data. Not one for this PR just something to consider in the future!

I appreciate there's a lot of changes here so I you want to walk though any of this on a call just ping me on slack 👍

@felixclack @kenfodder couple of things from this PR might be relevant for you guy's work

You can specify whether or not a question is considered as answered by the SessionAnswers. This is useful for controlling whether to get attributes from SessionAnswers or from CurrentClaim when setting attributes on a form. By default any attributes change on SessionAnswers will be passed into the answers has, but now you can explicitly pass an array to answered when updating attributes to only count the attributes you want to as having been answered by the SessionAnswers. See Form#load_current_value and the changes to the Journeys::Session#before_save callback

We now use the SessionAnswers to check if personal details have been changed from those pulled from teacher id. In CAPT-1659 we'll be removing the claim parameter to this method

Some factories have been set up for populating JourneySession. Can use them like

create(
  :additional_payments_session,
  answers: attributes_for(
    :additional_payments_answers,
    :with_personal_details,
    email<EMAIL_ADDRESS>  )
)

Not too bad to use though if we eventually switch to backing the answers with it's own table we can clean this up a bit more

Changed some bits of the slug sequences to refer to the session answers

The dqt record and tps changes I don't think should be relevant to your work


Use Helm values reference when referencing secret keys

I would like to use the zalando postgres operator to set up a postgresql database that will be referenced by camunda.
This operator already creates secrets for specific db users. The secret keys are "username" and "password" (Not DB_USERNAME and DB_PASSWORD).
Is it possible for you to update the following lines and reference an entry of the .Values file so that I can overwrite it and reuse the generated zalando operator secret?
https://github.com/camunda-community-hub/camunda-helm/blob/f71314c5d89ed808a107048341bcd7641f3177ed/charts/camunda-bpm-platform/templates/deployment.yaml#L56
https://github.com/camunda-community-hub/camunda-helm/blob/f71314c5d89ed808a107048341bcd7641f3177ed/charts/camunda-bpm-platform/templates/deployment.yaml#L61

works as expected. Thanks for the quick update


[dwarf] Remove defunct D extensions

DWARF4 re-purposes these values for something else, so it's unlikely that any debug would support it now.

Auto-merge toggled on

Once I rebase it...

Auto-merge toggled off

Yeah

@WalterBright - thanks, do you mind having a quick glance over at https://github.com/D-Programming-Language/dmd/pull/4732 (which is the documentation aspect of this change)

That should have been https://github.com/D-Programming-Language/dlang.org/pull/1022


npm start error

I'm having a bit of a bad day. sigh
On Mac with NPM 5.8
NodeJS v9.4.0
Let me know if you need more info, thanks in advance.
RBAINDOU-M-4116:react-codemirror robert$ sudo npm install
Password:
npm WARN deprecated<EMAIL_ADDRESS>Please use gulp-clean-css
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>connect 2.x series is deprecated
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js

><EMAIL_ADDRESS>install /Users/robert/projects/react-codemirror/node_modules/fsevents
> node install

[fsevents] Success: "/Users/robert/projects/react-codemirror/node_modules/fsevents/lib/binding/Release/node-v59-darwin-x64/fse.node" is installed via remote
npm notice created a lockfile as package-lock.json. You should commit this file.
added 1176 packages from 1298 contributors in 31.572s
RBAINDOU-M-4116:react-codemirror robert$ npm start

><EMAIL_ADDRESS>start /Users/robert/projects/react-codemirror
> gulp dev

/Users/robert/projects/react-codemirror/node_modules/require-dir/index.js:93
            if (!require.extensions.hasOwnProperty(ext)) {
                                    ^

TypeError: require.extensions.hasOwnProperty is not a function
    at requireDir (/Users/robert/projects/react-codemirror/node_modules/require-dir/index.js:93:37)
    at Object.<anonymous> (/Users/robert/projects/react-codemirror/node_modules/gulp-git/index.js:4:18)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)
    at Function.Module._load (module.js:505:3)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/robert/projects/react-codemirror/node_modules/react-component-gulp-tasks/tasks/release.js:1:73)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `gulp dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/robert/.npm/_logs/2018-04-05T19_01_47_360Z-debug.log
RBAINDOU-M-4116:react-codemirror robert$

@WinWinHost This lib is pretty much abandoned. Check out react-codemirror2. Check out gulp-clean-css while you're at it 😉

npm WARN deprecated<EMAIL_ADDRESS>Please use gulp-clean-css


Feature: multiple permit RedissonPermitExpirableSemaphore

Add ability to acquire/release multiple permits for RedissonPermitExpirableSemaphore.

added bunch of sync/async acquire methods
added bunch of sync/async release methods
added tests

Yeah, I've also thought about such approach, but checking existing code I've found out that now it uses single permit id for multiple permits, e.g. in tryAcquireAsync function.
And to be blunt to me such API looks better, than passing bunch of permit ids to release method. And imagine if someone acquired 10 permits, and wants to release all of them, but one was released meanwhile. It should throw an IllegalArgumentException (like in releaseAsync function).
If you sure that such multi-permits methods should return list of IDs I'll need help to implement them, 'cause I'm not such familiar with Redis API and Lua :(

Yeah, I've also thought about such approach, but checking existing code I've found out that now it uses single permit id for multiple permits, e.g. in tryAcquireAsync function.

It's internal method which is always used with permits = 1.
tryAcquireAsync should be extended for this case: accept multiple ids and added in lua script using zadd method.

Thank you for the review. Sorry for a bunch of unnecessary changes. Removed them

Also don't forget corresponding methods to RPermitExpirableSemaphoreRx and RPermitExpirableSemaphoreReactive

Also don't forget to add new methods to RPermitExpirableSemaphoreRx and RPermitExpirableSemaphoreReactive

@ikss
Can you do that?

Thank you for the contribution.

Thank you for review and suggestions


Fix SAM Attribute parser for numeric array tags

Page 6 of the SAMv1 specs allow for numeric array tags (TYPE="B"), with values matching:
[cCsSiIf](,[-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-9]+)?)+

This update of org.bdgenomics.adam.util.AttributeUtils.typedStringToValue skips the first character (a numeric type specifier) plus the leading comma, before trying to convert to a numeric array. This bug was breaking loadAlignments for BAM files generated by the STAR RNA-Seq aligner, which creates type "B" tags by default.

Can one of the admins verify this patch?

Jenkins, add to whitelist.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/ADAM-prb/847/
Test PASSed.

Thanks @jfeala! I have merged this manually.


Why the new version not on pypi?

Ask a question
Why the new version is not on pypi? I'm trying to upgrade to django 3 and I can't for this reason, unfortunately.

Why the new version is not on pypi? I'm trying to upgrade to django 3 and I can't for this reason, unfortunately.

https://github.com/pinax/pinax-messages/issues/50
Apparently it's coming "soon".

@PeterMarchev thank you very much

please close if your issue is resolved.

Hello, @tiagoarasilva, @PeterMarchev, @morenoh149... I've published a release earlier today. Hope this helps! https://pypi.org/project/pinax-messages/


Gaussian Noise Model

Not sure why the definition def approximate(self, z: Tensor, t: Tensor, hat: Tensor) in Gaussian noise does not consider two different parameters x and epsilon.  The forged approximate distribution is the case with epsilon parameter.
Could you please have a look?

Hi @jbgao! Thanks for your issue. I'm sorry I didn't get to it sooner :). In Modular Diffusion, the hat Tensor is the parameter being predicted. This could be $x$ or $\epsilon$ or something else, depending how the rest of your model is setup. For instance, if you want to predict $\epsilon$ set the parameter argument of the Gaussian noise module to epsilon and it will do the necessary calculations. Also, if you're using the Simple loss function, be sure to also set its parameter to epsilon so that everything works.

Thank you very much for the answer.  That was clear regarding using either noise or data approximation network.
However, my question was about sampling method. The sampling distribution (aka p_{theta}) defined in approximate function is for the case of epsilon-parameter, that is  eqn (125) in https://arxiv.org/pdf/2208.11970.pdf.  Or it was mentioned in Noise Type section in https://cabralpinto.github.io/modular-diffusion/guides/custom-modules/.
However in the case of x-parameter, the network hat is the approximation to the data x_0, that is \hat{x}(x_t, t) \approx x_0.  The approximated distribution p_{theta} should be eqn (94) in  https://arxiv.org/pdf/2208.11970.pdf.    Now sure whether this is right.
Thank you

Hi @jbgao, can you please point to the piece code that is giving you trouble? That might help me assist you better. By the way, I will be afk for the next 9 hours. Good luck!

Thanks again.  Here is the screen shots of noise.py

As you can see the return N is the one with mean in (125) in https://arxiv.org/pdf/2208.11970.pdf.    This is the case for epsilon network (hat)
There should be a if statement for self.parameter = 'x', such as according to (94)  in https://arxiv.org/pdf/2208.11970.pdf, to define the mean of N as
self.q3[t] * z + self.q4[t] * hat[0]
or
if self.parameter == "x":
N(self.q3[t] * z + self.q4[t] * hat[0],
self.q5[t]
if self.variance == "fixed"
else torch.exp(hat[1] * self.p3[t] + (1 - hat[1]) * self.p4[t])
if self.variance == "range"
else hat[1],
)

If you take a look at the schedule method, you'll see that self.p1 and self.p2 are conditioned based on self.parameter:
def schedule(self, alpha: Tensor) -> None:
    ...
    if self.parameter == "x":
        self.p1, self.p2 = self.q3, self.q4
    elif self.parameter == "epsilon":
        self.p1 = 1 / alpha.sqrt()
        self.p2 = (alpha - 1) / ((1 - delta).sqrt() * alpha.sqrt())

So self.p1[t] * z + self.p2[t] * hat[0] does equal self.q3[t] * z + self.q4[t] * hat[0] when self.parameter == "x". Does this make sense?
PS: Thanks for bringing that commented code to my attention. I was debugging the library before the release and forgot to delete them. I have now erased it.

Thank you for this.  I overlooked that part.    Now this is clear to me. :-)

No worries man. In the future, if you have any more questions, contact me on our Discord where I usually respond faster.


Cannot install on chrome

"Apps, extensions and user scripts cannot be installed from this website"

https://stackoverflow.com/questions/5258989/manually-adding-a-userscript-to-google-chrome#5259212


Drop support for iOS 8

When installing your library Xcode 12 informs about a warning:

The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.0.99.

The warning is for Pulsator library. I'm installing it via SPM, so no possibility to change it on the fly. With cocoapods people can add post-install script.
Can you bump the minimal target? iOS 8 is a very old system, a tiny percentage, probably not more than 0.5, is still using it.

@natalia-osa  Thank you for letting me know that! I've pushed a commit to update the target version.


Allow different models in replicate.ai interface

@CJWBW  Thanks again for providing an interface to the model in replicate.ai. I would like now to allow the user to select between different models. I modified predict.py and download-weights.sh accordingly.
I would like to update the image on https://replicate.ai/mehdidc/feed_forward_vqgan_clip/ ,  is cog push r8.im/mehdidc/feed_forward_vqgan_clip  the correct way to do it ? or it should be done on your side ? I tried the command but I got "docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]]." since I don't have an nvidia GPU on my local machine (assuming that's the reason it failed).

Hi @mehdidc,
Yes, that is the way, but you do need to push from a GPU machine when in cog.yaml file it specifies gpu: true.
Also, it is recommended to load all the models in setup() if possible, because it runs setup() the first time, and the consecutive runs are just calling predict().
I could adapt the code and push from my side?

Hey @CJWBW, thanks  for your answer.  I did load all the models on setup and put them in nets but maybe I am missing something else,  yes please adapt the code and push from your side then, thanks a lot!

Hi @mehdidc, yes just looked closely that models are loaded in setup() actually you were right. Just tested with the new models, "cc12m_32x1024_vitgan_v0.1.th" and "cc12m_32x1024_vitgan_v0.2.th" works, but "cc12m_32x1024_mlp_mixer_v0.2.th" will complain AttributeError: 'Rearrange' object has no attribute '_recipe'

Super cool, thanks!  cc12m_32x1024_mlp_mixer_v0.2.th, it's cause by einops newest version (0.3.2), I had to use an older one (0.3.0) in the requirements. I will change cog.yaml now to use einops 0.3.2.

I have pushed the model to the server now :) just need to change line 35 in predict.py to
def predict(self, prompt, model=DEFAULT_MODEL):

Cool :) Oh yes indeed, done for predict

Thanks a lot @CJWBW, everything works fine, merging.

@mehdidc These new models are so cool. :D
We haven't added support to change examples yet, but we can do it manually in the database for you if you'd like. Would you like to change the example that's displayed by default on the form? Maybe one using v0.2?

@bfirsh Glad tout you like the new models :) thanks for all the support, the service/web interface makes it so easy to test the models.
Actually yes I was wondering about that, yes thanks please change the default to v0.2 vitgan with the prompt "At my feet the white-petalled daisies display the small suns of their center piece".

Done! Let me know if there are any you want to delete/reorder too. We're working on a user interface... sorry about this... 😅

Very nice thanks! sure will let you know :)

Hi @bfirsh, asking the following because someone was interested, is it possible to access the models  using an API ? I mentioned the possibility to use Docker + any HTTP client such as curl as already mentioned in the page, but that will  of course launch the web service locally.


BakedLightMap causes unbaked meshes to disappear in 3.2.4 RC 1

Godot version:
3.2.4 RC 1
OS/device including version:
Debian Bullseye with open-source AMD drivers and the GLES2 backend. I'm running an RX570 but I don't think that'll end up mattering.
Issue description:
Adding a lightmap to the scene and baking it causes non-lightmapped meshes to disappear. I'm not super familiar with 3d game dev but my understanding is they should be lit dynamically instead of disappearing. The symptoms seem identical to #24550
Steps to reproduce:
Create a new scene and add a light and a camera. Import a mesh, and perform the UV2 unwrap. Add the mesh to two different MeshInstances, and mark only one of them as "use in baked light". Add a BakedLightMap node and bake its lightmap. Export the project with the official HTML5 template for 3.2.4 RC1, host it somewhere and observe the results in both firefox and chromium.

It works fine in the editor though

Minimal reproduction project:
lightmap_bug_repro.zip
Additional Info
The logs point to an issue with shader compilation. I managed to track this one down. It appears that the logic deciding whether or not to enable the lightmap baking code (with the cone tracing and all that) doesn't look at whether or not it's in the editor, so it compiles the cone tracing into the shader even in the HTML5 export. This ends up being an issue because it seems like there might be another array-related issue with the lightmapping code. Either that or the old one resurfaced.
**ERROR**: SceneShaderGLES2: Fragment shader compilation failed: index.js:9:17349
ERROR: 0:721: 'first-class array' : not supported index.js:9:17349
<empty string> index.js:9:17349
   At: drivers/gles2/shader_gles2.cpp:130:_display_error_with_code() - SceneShaderGLES2: Fragment shader compilation failed: index.js:9:17349
ERROR: 0:721: 'first-class array' : not supported index.js:9:

And here's one potential fix that seems to work on my hardware. It makes sense to me. I don't ever want to capture lightmap data unless I'm in the editor.
diff --git a/drivers/gles2/rasterizer_scene_gles2.cpp b/drivers/gles2/rasterizer_scene_gles2.cpp
index ff27f11333..a67e7367a9 100644
--- a/drivers/gles2/rasterizer_scene_gles2.cpp
+++ b/drivers/gles2/rasterizer_scene_gles2.cpp
@@ -2400,7 +2400,7 @@ void RasterizerSceneGLES2::_render_render_list(RenderList::Element **p_elements,
                                rebind_reflection = true;
                        }

-                       use_lightmap_capture = !unshaded && !accum_pass && !e->instance->lightmap_capture_data.empty();
+                       use_lightmap_capture = !unshaded && !accum_pass && !e->instance->lightmap_capture_data.empty() && Engine::get_singleton()->is_editor_hint();

                        if (use_lightmap_capture != prev_use_lightmap_capture) {

Related to #45574.

Related to #45574.

If you apply the change you've described, this means dynamic objects will no longer be correctly lit in an exported project.

Interesting. It definitely is still lighting dynamic objects. I compiled a custom HTML5 export template with the patch I provided to export a game of mine to itch.io yesterday. The exported game runs on both my chromebook and my desktop, along with a number of friends computers. Now I'm not sure why it works...

If you apply the change you've described, this means dynamic objects will no longer be correctly lit in an exported project.

Interesting. It definitely is still lighting dynamic objects. I compiled a custom HTML5 export template with the patch I provided to export a game of mine to itch.io yesterday. The exported game runs on both my chromebook and my desktop, along with a number of friends computers. Now I'm not sure why it works...

It's possible I completely disabled lightmapping outside of the editor, looking at that patch. I'm not sure. I'll wait for an upstream fix though, since this area of the engine is completely foreign to me.

It's possible I completely disabled lightmapping outside of the editor, looking at that patch. I'm not sure. I'll wait for an upstream fix though, since this area of the engine is completely foreign to me.

I had similar issue. Fixed with this PR:
https://github.com/godotengine/godot/pull/45622

Some before and after images:

Fixed by #45622.


HCCDOC-1750 cost and hcs LR tile link updates

https://issues.redhat.com/browse/HCCDOC-1750
Edit Learning Resources Documentation tiles for Sources to Integrations and version updates.

/ok-to-test


bp3, voedger: Describe ACL using VSQL and check it in runtime

Requirements

Use ACL from VSQL, currently it is hardcoded (pkg/iauthnzimpl/impl_acl.go)

Technical design: Principles

IsAllowed(appart...)

Separate resulting policies for Resource and Fields
If all policies are Allow return true

IAppPartition.????  uses something like pkg/acl
Deny policy is not allowed yet

Otherwise VSQL ACL rules must have unambiguous ordering

Context

Design concepts
vsql example
pkg/acl
pkg/iauthnzimpl/impl.go
pkg/iauthnzimpl/impl_acl.go

GRANT/REVOKE

    -- sys
    ROLE System;
    ROLE Admin;
    ROLE LocationUser;
    ROLE LocationManager;
    ROLE Application; -- Projector is executed with this role

    -- Grants declared only within workspace

    GRANT ALL ON ALL TABLES WITH TAG BackofficeTag TO LocationManager;
    GRANT INSERT,UPDATE ON ALL TABLES WITH TAG BackofficeTag TO LocationUser;
    GRANT SELECT ON TABLE Orders TO LocationUser;
    GRANT UPDATE (CloseDatetime, Client) ON TABLE Bill TO LocationUser;
    GRANT EXECUTE ON COMMAND Orders TO LocationUser;
    GRANT EXECUTE ON QUERY Query1 TO LocationUser;
    GRANT EXECUTE ON ALL QUERIES WITH TAG PosTag TO LocationUser;

    GRANT INSERT ON WORKSPACE Workspace1 TO Role1;

See #928
REVOKE INHERITED

Roles

Currently not registered in the app structs
System roles: Public, WorkspaceOwner, etc

Grants

Current

### Tasks
- [ ] https://github.com/voedger/voedger/issues/864
- [x] https://github.com/voedger/voedger/issues/949
- [ ] https://github.com/voedger/voedger/issues/395
- [ ] https://github.com/voedger/voedger/issues/396
- [ ] https://github.com/voedger/voedger/issues/1955
- [ ] https://github.com/voedger/voedger/issues/1961
- [ ] https://github.com/voedger/voedger/issues/2516
- [ ] ———————————
- [ ] https://github.com/voedger/voedger/issues/2509
- [ ] https://github.com/voedger/voedger/issues/2521
- [ ] voedger: use ACL
- [ ] bp3: use ACL

@maxim-ge, describe how SELECT permissions should work:

grant execute on q.sys.Collection + revoke select on Table1 -> could any field of the Table1 be selected?
are we need permission control on Field level? e.g. grant execute on q.sys.Collection + revoke select on Table1.Field1 - select of Table1.Field1 denied?


[Question] - Is it possible to implement it in page

Hi there,
Would you please let me know if the picker can be implemented in page e.g. in this datetime picker? The reason I would go with yours is the number of supported locales.
Thanks!

sorry, it can't, but you can abstract some codes in this package to achieve that, thanks


Error when exporting the graph

Any idea on the following error when trying to export the graph?
[File "//anaconda/lib/python3.5/site-packages/bitcoingraph-0.3.2.dev0-py3.5.egg/bitcoingraph/bitcoind.py", line 92, in _execute
bitcoingraph.bitcoind.BitcoindException: RPC connection failure: 405 Method Not Allowed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "//anaconda/bin/bcgraph-export", line 4, in <module>
    __import__('pkg_resources').run_script('bitcoingraph==0.3.2.dev0', 'bcgraph-export')
  File "//anaconda/lib/python3.5/site-packages/setuptools-23.0.0-py3.5.egg/pkg_resources/__init__.py", line 719, in run_script
  File "//anaconda/lib/python3.5/site-packages/setuptools-23.0.0-py3.5.egg/pkg_resources/__init__.py", line 1511, in run_script
  File "//anaconda/lib/python3.5/site-packages/bitcoingraph-0.3.2.dev0-py3.5.egg/EGG-INFO/scripts/bcgraph-export", line 41, in <module>
  File "//anaconda/lib/python3.5/site-packages/bitcoingraph-0.3.2.dev0-py3.5.egg/bitcoingraph/bitcoingraph.py", line 40, in __init__
  File "//anaconda/lib/python3.5/site-packages/bitcoingraph-0.3.2.dev0-py3.5.egg/bitcoingraph/bitcoingraph.py", line 58, in __get_blockchain
bitcoingraph.bitcoingraph.BitcoingraphException: Couldn't connect to localhost.
](url)

This code is currently not in use and the development was done with Bitcoin Core 11. I've made a quick fix for Bitcoin Core 12 now. You can try the latest version.


SVG shapes show up all-black when generated with certain Adobe Illustrator settings

Greetings! Thank you very much for authoring the excellent JSVG library. In https://github.com/apache/netbeans/pull/7941, we are in the process of switching the NetBeans IDE from Batik to JSVG for icon rendering.
I encountered one problem that was easy to work around; I thought I would document it here in case anyone else encounters it. Feel free to close the issue if it's not worth fixing.
Bug:
SVG files generated by Adobe Illustrator using the "Style Attributes (Entity References)" option show up with correct shapes, but all-black, when rendered with JSVG.

Now as it turns out, in recent versions of Adobe Illustrator, the Entity References option is now explicitly labeled as deprecated. So it may not really be necessary to support these kinds of SVGs. The problem could occur when trying to load older SVG files, though.

Workaround:
The easy workaround is to simply use another setting when generating the SVG file from Illustrator. The two other settings available are "Style Elements" and "Style Attributes", and they both seem to be working fine with JSVG.
I have attached SVGs generated using each of the three options in case it is useful. The three files were all generated with the same recent version of Adobe Illustrator (version 28.7.2). The "findDropdown_styleattentityrefs.svg" file is the one that does not work with JSVG.
findDropdown_styleattentityrefs.svg:
findDropdown_styleattributes.svg:
findDropdown_styleelements.svg:

I don't think that entity references are something I like to support. They won't be part of the newer SVG 2.0 specification. The only "addition" they give is being able to import external definitions, which has been a security risk with other implementations in the past.
Will leave this open for now just to make it more discoverable (until Adobe has removed the option).

Yeah, makes sense! Agree wrt. loading of external resources too... I always disable anything like that when parsing XML formats.


Syntax error in train.py ?

Windows 10 64 Bit
Python 3.6.5 64 bit
grabbed all requirements except tensorflor 1.5.0 because pip couldn't find 1.4.1 for some reason
Wanted to train the GAN using the linkedin leak, so using
python train.py --output-dir output --training-data data/in.txt
And it throws me a syntax error:
File "D:\PassGAN\train.py", line 144
print " print "validation set JSD for n={}: {}".format(i+1, true_char_ngram_lms[i].js_with(validation_char_ngram_lms[i]))
Syntax Error: invalid syntax. The error is specified to be at the end of the "" encapsulated string. I have little knowledge of Python as I never got in contact with it, so I can't solve it myself..?

I have encounted the same question~

try this one, https://pastebin.com/raw/JxsnSFCE

I updated the source code for Python 3 / TensorFlow 1.13. https://github.com/d4ichi/PassGAN

try this one, https://pastebin.com/raw/JxsnSFCE

I tried and i meet this
also the numpy's version should be 1.14.1~
Traceback (most recent call last):
File "JxsnSFCE", line 10, in
import utils
File "/root/PassGAN-master/utils.py", line 133
print "loaded {} lines in dataset".format(len(lines))
^
SyntaxError: invalid syntax


T-shirt sizing for Combobox (sub-component references)

Part of DNA v6.0.0-beta.21
synced to jira: https://jira.corp.adobe.com/browse/SDS-7576

hey @GarthDB this might be closed? Beta 6 went out a while ago?


update ruby

bundle needs atleast ruby 2.3.
Current error is:

ruby-2.6.3 - #adjusting #shebangs for (gem irb erb ri rdoc testrb rake).
--
  | Install of ruby-2.6.3 - #complete
  | Ruby was built without documentation, to build it run: rvm docs generate-ri
  | /usr/local/rvm/scripts/functions/support: line 516: cat: command not found
  | /usr/local/rvm/scripts/functions/support: line 277: date: command not found
  | /usr/local/rvm/scripts/functions/support: line 277: awk: command not found
  | /usr/local/rvm/scripts/functions/utility_logging: line 96: mkdir: command not found
  | /usr/local/rvm/scripts/functions/utility_logging: line 97: rm: command not found
  | /usr/local/rvm/scripts/functions/utility_logging: line 99: tee: command not found
  | /usr/local/rvm/scripts/functions/logging: line 226: cat: command not found
  | /usr/local/rvm/scripts/functions/support: line 277: date: command not found
  | Creating alias default for ruby-2.6.3Error running 'alias_create_execute',
  | please read /usr/local/rvm/log/_ruby-2.6.3/alias_create.log
  | ERROR:  Error installing bundler:
  | bundler requires Ruby version >= 2.3.0.
  | Installation is completed now that was easy :)
  | ---> 88d25d1670f8
  | Removing intermediate container 4c7d2dca4a3f
  | Step 11/23 : RUN ruby --version
  | ---> Running in 807e9f29581d
  | ruby 2.0.0p648 (2015-12-16) [x86_64-linux]

Now it compiles.
But in Jenkins it fails with:
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Prepare)
[Pipeline] sh
[priceinsight-develop] Running shell script
+ gem install bundle
ERROR:  While executing gem ... (Gem::FilePermissionError)
    You don't have write permissions for the /usr/local/lib/ruby/gems/2.6.0 directory.
[Pipeline] }
[Pipeline] // stage


Some Format Character dosen't work without an end char.

e.g, if the format string is written as :
G y/MMM/d(E/'W'w/'Q'Q) z#hh:mm:ss B
the tailed 'B' will not work.
but if it's written:
G y/MMM/d(E/'W'w/'Q'Q) z#hh:mm:ss B/
or
G y/MMM/d(E/'W'w/'Q'Q) z#hh:mm:ss B.
it will be good.

Here is what I get when I paste in the first pattern with the trailing B. It looks ok?

if the formating string ends with 'B.', it'll be ok in my mac; if it ends with 'B' without '.', there will not be 'in the morning' displayed.

it works this time.
i don't know what happened last time, but the 'in the morning' string really didn't show then.
i'll keep testing it.

the problem got more and more interesting this time lol
look!

On my end, when I enable the 24-Hour Time, the B does nothing. If I disable 24-Hour Time, it says 'in the morning'. It doesn't require a trailing character after the B for it to work.
I think according to the Unicode standard, B isn't supported for 24-Hour Time, so this behavior is correct. I don't have control over how these characters are interpreted. I pass them to an Apple API that creates the time string from the format pattern. I think Apple is adhering to the standard.
From https://unicode.org/reports/tr35/tr35-dates.html:
Patterns and skeletons for 24-hour-cycle time formats (using H or k) currently should not include fields with day period characters (a, b, or B); these pattern characters should be ignored if they appear in skeletons.

So Itsycal only transfers the string to an API and receive the interpreted result, this issue should not be tagged to 'BUG'.
Thank you very much for creating so practical and useful software, it helps me much!

PS.
At the beginning I thought this was only a tiny insignificant probelm of processing some ambiguous format string. But after reading the UNICODE LDML doc's relating sectors, and then I did some further test of the strings, I think this is a little complex but very interesting now!
Test case combinations:
although it's meaning less to do the test if the 24-hour mode is activated according to the UNICODE LDML doc, the test cases could be recorded for refering if needed...
Uh…
Am I making simple things complex...
...
in 24-hour enabled mode, it's a little hard to predict the result by cerebrum, which is like to predict a regex's matching...
according to the doc, the result depends on the order of the patterns, too...

MacOS's system Preferences' 24-Hour option enabled?

display the hour in expected way?

zone char(z)?

zone char before or after the clock field(z hh:mm , or  hh:mm z)?

skeleton char?

a/b/B

hour pattern is lower cased or upper cased(hh / HH)?
trailing with a end char or not?
other switches ...

Ok, I will remove the bug label and close this issue. Yes, Itsycal just passes the string to the framework to interpret the pattern. That way it is done how the system would do it and I can't mess it up. :) I think it is working the way it is supposed to work, but that is a complex topic and isn't always intuitive.


Keep Inventory

I turned keep inventory off and it is not dropping the other players items on the floor. It is deleting the items. Is there a way to fix this.

It is likely Essentials. Turn Essentials.keepinv off in your permissions.

It is likely Essentials. Turn Essentials.keepinv off in your permissions.


[FEATURE REQ]: - Need documentation to understand how to use APIOps with AKS

Please describe the feature.
Hi,
We are using the below Az CLI command and pass in Open API JSON specification file and the AKS service IP to import the APIs in Azure API management and add its backend.
az apim api import --api-id "${{ parameters.apiName }}" --display-name "${{ parameters.apiDisplayName }}" --resource-group "${{ parameters.clusterRG }}" --service-name "${{ parameters.apimName }}" --api-type "http"  --protocols "https" --path "${{ parameters.releaseName }}" --specification-format "OpenApi" --subscription-required false --specification-path "${{ parameters.apimJsonPath }}" --service-url "http://$(serviceIp)/";

We query the service IP by using the below command.
export SERVICE_IP=$(kubectl get svc -n ${{ parameters.clusterNamespace }} ${{ parameters.releaseName }} --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}")

The problem with approach is we couldn't find an option to add the policies in the JSON file and are forced to use the Bicep for adding APIM policies. We heard about the APIOps from community and would like to know how this can be utilized for our scenario. The example is provided with a FQDN backend whereas we have an IP address as a backend. Please help us with the suitable deployment pattern.
@waelkdouh - FYI.

APIOPS doesn't generate any policy for you. You either have to use the Azure portal or manually populate the policy yourself. What Apiops can do is allow you to promote that policy across different apim instances.
Keep in mind that apiops does't allow you to provide a separate policy file to override the existing one, but rather it supports overriding namedvalues inside thise policy files by utilizing the configuration override feature in apiops which is discussed here.


Is it possible to allow MenuLinks to be added under the Home nav item in the navbar?

I would like to move some MenuLinks out of the navbar and add them as a dropdown under the Home link in the navbar. However, I don't believe this is currently possible (after reviewing the code) since Home doesn't belong to a category; therefore, items can't be associated to it. Am I missing something or are my findings correct? If so, how difficult would it be to add the ability to add items under the Home link in the navbar?

Actually just realized all I need to do is override the is_visible function in the IndexView and create an artificial Home category.


gxss

update the gxss script. now it supports post method as well.

Thanks for the suggestion, but for the moment, the xss module only supports GET method


Add search engine name to the printed parsed output

@starlord1311 Would you be interested to work on this one?
I'm submitting a ...

[ ] bug report
[X] feature request

Current behavior:

Current printed output is usually parsed[{“title”: ...
Expected behavior:

Desired printed output could be Google parsed: [{“title”: ...
Steps to reproduce:

Run a Quora search to see the right kind of output.
Run a Google search to see the wrong kind of output.

https://github.com/fossasia/query-server/blob/master/app/scrapers/quora.py#L21
Does it right and the other search engines should be modified to do things the same way.
https://github.com/fossasia/query-server/blob/master/app/scrapers/google.py#L27
This change would make it easier to find and fix bugs like #271

yes i would like to take this up.

can you please tell what i have to do?


checklist for STAR to generate Leafcutter result

The example STAR command provided by the leafcutter is shown as follows.
IN THEORY, they should be the same, as the specified parameter are identical.
STAR

[x] --genomeDir hg19index/  (Input )
[x] --twopassMode Basic  (default in py script)
[x] --outSAMstrandField intronMotif (default parameter value)
[x] --readFilesCommand zcat (default in py script)  \
[x] --outSAMtype BAM Unsorted (default in py script)

However, there are two cautions:

In leafcutter example, no fastq reads were input in the star program
Other parameters not specified in the above command but specified in run_STAR.py may/may not have an impact on the analysis.

That said, it should be safe to proceed with what we have before proven otherwise.

get√

That said, it should be safe to proceed with what we have before proven otherwise.

@hsun3163 agreed!


Use storage when creating with a schema

When creating a table with a schema and setting the format to parquet, the table is created as text (the impala default) since stored as parquet is never inserted.
Added a _storage call to insert the stored as parquet similar to other tables.
Thoughts?
db.create_table(table_name, schema=schema, format='parquet')

Sorry I'm a little slow to respond!
Can you add a unit test? I will need you to send me a ICLA to merge your patch (http://docs.ibis-project.org/developer.html#contributor-license-agreements)

Fixed this in https://github.com/cloudera/ibis/commit/05943aee942121115103d1bc2c21483db5e2f3ce. Thank you!


[fed] Provide the initial federated plugin interface.

Extracted from https://github.com/dmlc/xgboost/pull/10534 . See the https://github.com/dmlc/xgboost/pull/10410 for existing limitations. The most outstanding issue of the interface is the lack of support for multi-class. To enable this, we need to further refactor the tree methods, which is out of scope for the initial implementation.
We will be targeting the feature branch for now. The merge into the master branch will start once the feature branch is complete.

cc @rongou .


locked file in Visual Studio : sick_scan_xd\build\sick_scan.sln

Hi,
It's urgent, I'm stuck
I'm currently using the LMS511-10100 scanner, on Windows and without ROS. I was able to generate executables, now I want to retrieve the data from my scanner in a CSV file. now i want to retrieve the data from my scanner in a CSV file., the problem I'm having is that when I try to load sln solutions such as sick_scan, I find that this solution is locked and I can't debug it.
My question is : will i be able to retrieve the data without using the debeug part?
Thank you for your help.

Thanks for your report and screenshot. Target "ALL_BUILD" is a cmake target and cannot be executed. Please select target sick_scan_xd_api_test (usually by right mouse click) and click Set as startup project or Debug -> New Instance in the menu to run sick_scan_xd_api_test.

Hi;
thank you for the feedback, this is what I get when I launch the run.

Please provide a launchfile like sick_lms_5xx.launch by your commandline arguments. Select sick_scan_xd_api_test, open the Properties menu, select Debugging under the Configuration Properties, goto Command Arguments and insert the arguments e.g. ./launch/sick_lms_5xx.launch hostname:=<IP_ADDRESS> (replace <IP_ADDRESS> by the IP address of your scanner, if different).
See https://github.com/SICKAG/sick_scan_xd/blob/master/doc/sick_scan_api/sick_scan_api.md for further informations about the API usage.

good morning,
Thank you very much for your feedback. Here is what I get :

Thank you for your help.

The relative path of a launchfile like ./launch/sick_lms_5xx.launch depends on your current working directory, i.e. the directory the executable is started from. Please use a path to sick_lms_5xx.launch relative to your working directory, or use an absolute path to the launchfile like "/_SICK_DEV/sick_scan_ws_1/sick_scan_xd/launch/sick_lms_5xx.launch" hostname:=<IP_ADDRESS>
Before starting the debugger, try to run sick_scan_xd_api_test.exe in a command shell (cmd.exe), e.g.:
cd D:\_SICK_DEV\sick_scan_ws_1\sick_scan_xd\build
.\Debug\sick_scan_xd_api_test ../launch/sick_lms_5xx.launch hostname:=<IP_ADDRESS>

Adapt the paths of the command to your system if required. If sick_scan_xd_api_test works, you can run the same in the debugger by providing the same commandline arguments (just without .\Debug\sick_scan_xd_api_test).

Hello again,
Thank you so much, it's great. Now I would like to have the CSV file corresponding to my scanner. Could I have some leads. Thank you.
Here is what I get :

Great to see that sick_scan_xd_api_test works. You can export the scan data to a csv-file within the callback (i.e. function apiTestCartesianPointCloudMsgCallback). File https://github.com/SICKAG/sick_scan_xd/blob/master/test/src/sick_scan_xd_api/sick_scan_xd_api_test.cpp provides an example (function plotPointcloudToJpeg), which converts the scan data to a jpg file. You can e.g. modify function plotPointcloudToJpeg to export the scan data to a csv file, see https://github.com/SICKAG/sick_scan_xd/blob/68259608b11820367bf1bc5b8e0e0c412928a5a0/test/src/sick_scan_xd_api/sick_scan_xd_api_test.cpp#L34C10-L34C10.
See also https://github.com/SICKAG/sick_scan_xd/blob/master/doc/sick_scan_api/sick_scan_api.md for further information about the API examples, their callbacks and the point cloud memory layout.

Thank you very much, that was my idea too.


Extend IDS-EDC Domain Object Transformation infrastructure

At the time of writing there is just one way covered for mapping data from the EDC domain model to IDS objects using our  object transformation infrastructure.
For the purpose of enabling communication of one connector to another using the IDS multipart protocol the set of transformers needs to be extended to be capable of vice versa transformation.
Following transformers are (possibly) needed

(IDS) Action to (EDC) Action
(IDS) Artifact to (EDC) Asset
(IDS) Representation to (EDC) Asset
(IDS) Resource to (EDC) Asset
(IDS) Constraint to (EDC) Constraint
(IDS) ContractOffer to (EDC) ContractOffer
(IDS) Duty to (EDC) Duty
(IDS) LeftOperand to (EDC) Expression
IDS RdfResource to (EDC) Expression
(IDS) BinaryOperator to (EDC) Operator
(IDS) Permission to (EDC) Permission
(IDS) Prohibition to (EDC) Prohibition

Since the transformers can be conveniently worked on in a disjointed manner one Pull Request can be filed per transformer.
 Denis Neuling<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

@denisneuling Can we skip the RdfResource one? Does anyone have an idea of what that is?

@jimmarino Sure, IMO for a first version we can skip this until we know how whether it is really used and how to express this. Will cross it out.

I assume we need the RdfResource to create a contract, that limits the usage of the data to a specific purpose. Without RdfResource we won't be able to create a Constraint.
This would make the following transformer unnecessary, too

Constraint
LeftOperand
BinaryOperator

I assume we need the RdfResource to create a contract, that limits the usage of the data to a specific purpose. Without RdfResource we won't be able to create a Constraint. This would make the following transformer unnecessary, too

Constraint
LeftOperand
BinaryOperator

@DominikPinsel I'm not sure I follow. Why can't a transformer just support TypedLiteral with an XML Schema string to set the right operand of a Constraint?
This is probably another thing IDS needs to fix/specify if they want interoperability.

@DominikPinsel I'm not sure I follow. Why can't a transformer just support TypedLiteral with an XML Schema string to set the right operand of a Constraint?
This is probably another thing IDS needs to fix/specify if they want interoperability.

@jimmarino Yea, the problem here is that in IDS the right operand is always an RdfResource. It looks like this

/**
 * The class of Constraints that restrict a Rule.
 */
@JsonTypeInfo(use = JsonTypeInfo.Id.NAME, property = "@type")
@JsonSubTypes({
    @JsonSubTypes.Type(value = ConstraintImpl.class)
})
public interface Constraint extends AbstractConstraint {

    @NotNull
    @JsonProperty("ids:leftOperand")
    LeftOperand getLeftOperand();

    @NotNull
    @JsonProperty("ids:operator")
    BinaryOperator getOperator();

    @JsonProperty("ids:rightOperand")
    RdfResource getRightOperand();

   // more code

}

If we really need it, I think it is sufficient to assume a RdfResource is directly representable as a LiteralExpression for now. All other more complex cases should yield some error messages to the TransformerContext and should lead to retruning a nulled Expression.
This is a compromise between completely leaving the RdfResource out and fully implement it's transformation to Expression.
Will add the RdfResource back to the list together with some comments.

If we really need it, I think it is sufficient to assume a RdfResource is directly representable as a LiteralExpression for now. All other more complex cases should lead to some error messages passed to the TransformerContext and should yield a nulled Expression.
This is a compromise between completely leaving the RdfResource out and fully implement it's transformation to Expression. Will add the RdfResource back to the list together with some comments.

+1. I think we can check for the subtype TypedLiteral and support that since it is declared as an XML Schema string type, which would be valid to do. Otherwise, an error sounds good.

@denisneuling also looping in @ronjaquensel and @juliapampus  on this...
When deserializing policy expressions, we need to also account for complex types in the right operands of atomic constraint expressions.
For example:
"ids:constraint": [{     	"@type":"ids:Constraint",   	"ids:leftOperand": { "@id": "idsc:CONNECTOR"},   	"ids:operator": { "@id": "idsc:IN"},   	"ids:rightOperand": [{  		"@value": "?connector1URI",  		"@type": "xsd:AnyURI" 	},{  		"@value": "?connector2URI",  		"@type": "xsd:AnyURI" 	}],  	....... omitted ..... }]
This comes from: https://github.com/International-Data-Spaces-Association/IDS-G-pre/tree/usage-control-terms/UsageControl/contract
In the above, the right operand contains JSON-LD metadata in a serialized JSON array that defines element types using XML Schema string types. The policy engine supports complex types for operand literals, so that is fine. However, I don't think we need to push the complexity of interpreting JSON-LD metadata onto policy functions that evaluate those literals. Instead, we should define a set of types we want to handle out-of-the-box with IDS (users can always add support for more). For example, we would support deserialization into strings or arrays of strings. That way, type complexity is not pushed down to lower levels of the EDC.
So my initial questions are:

How are policy expressions (not the entire message) currently deserialized from the multipart messages? Are they strings or complex types? The transformation from initial form to the limited type set can be done in the transformer (and vice versa)

Does IDS now declare that policy expressions be JSON-LD types? Or, is it open?

Let's discuss.

I should have added that the use of JSON-LD partly explains why right operands can be RdfResource. However, JSON-LD extends RDF and the RdfResource InfoModel type looks like it may be incorrectly implemented since property values can only be Strings and JSON-LD allows for native JSON types and tagged strings.
As I mentioned, I think these structures should be unwrapped and the corresponding Java types instantiated by the transformers on ingress; Likewise, on egress, the opposite transformation from Java types to JSON-LD can happen in the transformers.

FYI: I will start working on this issue


[VS CODE] Direct connect guest unable to connect

Issue Type: Bug

Port foward, ports 5990-5999
Allow vsls-agent on firewall
Set connection mode to direct
Start a live share session
Invite participants using either contact invite or link

Actual Results
Participant gets "Joining collaboration session: Unable to connect to the host in "Direct" mode. Verify you and the host are online. If so, switch to "Auto" or "Relay" mode and retry."
We don't want to use "Auto" or "Relay" because performance has been very poor.
Expected Results
Participant successfully joins the "direct" connection session.
Extension version: 1.0.3629
VS Code version: Code 1.53.1 (5d424b828ada08e1eb9f95d6cb41120234ef57c7, 2021-02-08T23:29:42.785Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (8 x 4000)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.45GB (7.08GB free)

Process Argv
--crash-reporter-id 4784cfdf-abd2-4387-8097-c2eac57ec9d1

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspyt653:30253241
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30211402
vstry914:30250197
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt600cf:30251589

I have the same issue, even without the port forward, even when opening the Live Share link on my own pc. It's like, why do I even need to be online in this situation?
How can I solve this?
VSCode info

Version: 1.68.1 (user setup)
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-14T12:48:58.283Z
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044

Apologies for the delay here. As is, this issue doesn’t have enough information to be reproduced. Please also see our documentation on the "direct" connection mode - https://learn.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#requirements-for-connection-modes.


Update Dropshare Extension

Description
Updating the existing Dropshare extension to add a new "URL shortener" action that helps accessing the configured Dropshare URL shortener.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

I oriented myself on comparable integrations (like Dub), but sure, I'll happily update it.

For me, it just feels like an annoying extra step. If you want to keep it as it is, that's also okay with me 🙂

If the extension was a no-view, the user had no chance up update or replace the URL that might have been read from the clipboard before shortening, right? If so, then I'd personally prefer it the way it is.

One solution could maybe be that if you enters an argument you'll early popToRoot() and shorten in the script, that might be possible 🙂

One solution could maybe be that if you enters an argument you'll early popToRoot() and shorten in the script, that might be possible 🙂

I was rather thinking about it from a UX point of view. The current flow is:
User selects "Shorten URL" action in Raycast, and can either directly provide a URL as argument, or just hit "return" and go into the action's view. There, the input field will either be pre-filled with a URL that the extension reads from the user's clipboard, or be empty, so that the user can enter a URL manually or copy & paste it from somewhere else. That way, it's always very clear what is about to happen, and the user will never be wondering where the URL has been read from when the action was triggered.


Update user password functionality.

Implement (actually it is all Devise) the user password change and view.

Enabling the sending of email when the user changed their password (new ENV variable).

Link in the header.

https://www.pivotaltracker.com/story/show/143048897

Jesus, could you give me the production value for the new template ID, please? Just create a placeholder in Notify, if necessary.