Don't generate code coverage on pull request builds

It just takes ages, then gets discarded at the end...

This is for Scrutinizer, no?

Yeh. Our tests are taking like 30 mins to run. This is really slowing down contributions.

You know I hate Scrutinizer so, yeah, do it.

Scrutinizer doesn't even use it anyway. We have it setup to only analyse the master branch.

Got a solution.

:banana:


:fire: delete all the apt packages

Motivation
Current main build is running out of space when the build cache misses everything
Modifications
Adds in more apt-get removes
Result
🤞 more disk space

You might want to have a look at  something like https://github.com/jlumbroso/free-disk-space:
uses<EMAIL_ADDRESS>with:
  tool-cache: false

Yup, you can see the reference to the action I copied the code from in the comment. We're not allowed to use arbitrary third party github actions within the github.com/ibm org unfortunately, so we have to copy/paste


argo-server: Blank page

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
When I connect to the Ingress controller LB, I get a blank page named Argo. Page code is the following:
<!doctype html><meta charset="UTF-8"><title>Argo</title><base href="/argo/"><meta name="viewport" content="width=device-width,initial-scale=1"><meta name="robots" content="noindex"><link rel="icon" type="image/png" href="assets/favicon/favicon-32x32.png" sizes="32x32"><link rel="icon" type="image/png" href="assets/favicon/favicon-16x16.png" sizes="16x16">

main.js is properly downloaded as you can see in those screenshots.

Am I missing something?
Version
v3.4.4
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
- I deployed a fresh install using Quickstart https://argoproj.github.io/argo-workflows/quick-start/#install-argo-workflows , including patching argo-server auth.
- Configured Ingress controller as per documentation https://argoproj.github.io/argo-workflows/argo-server/#ingress
- Disabled TLS https://argoproj.github.io/argo-workflows/tls/#plain-text and patched argo-server deployment to replace HTTPS with HTTP

Logs from the workflow controller
From argo-server instead (doing multiple refreshes):
kubectl -n argo logs argo-server-5f56d69559-gjt4v
time="2022-12-29T09:17:07.135Z" level=info duration="16.58µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:07.393Z" level=info duration="9.81µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:07.537Z" level=info duration="5.86µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:07.721Z" level=info duration="10.61µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:07.887Z" level=info duration="9.38µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:08.047Z" level=info duration="9.83µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:08.250Z" level=info duration="10.12µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:08.365Z" level=info duration="9.47µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:08.546Z" level=info duration="9.3µs" method=GET path=index.html size=0 status=304
time="2022-12-29T09:17:08.711Z" level=info duration="9.77µs" method=GET path=index.html size=0 status=304

Logs from in your workflow's wait container
N/A

@dgouju , how did you solve this problem?  I am facing it now

same here

same here v3.5.8
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/download/v3.5.8/install.yaml
kubectl set env deployment/argo-server -n argo BASE_HREF=/argo/

When I curl it gives 200, but when I try to open in a Browser it gives me a blank page with Uncaught SyntaxError: Unexpected number.

My ingress:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    cert-manager.io/issuer: self-signed
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
  name: argo-server
  namespace: argo
spec:
  ingressClassName: nginx
  rules:
  - host: mykubernetes.com
    http:
      paths:
      - backend:
          service:
            name: argo-server
            port:
              number: 2746
        path: /argo(/|$)(.*)
        pathType: ImplementationSpecific

IDK where to look at it anymore.

@dgouju How did you solve this problem? I am facing it now on v3.5.8


add support for "angles" property

I'm not sure this is intentional or not, but currently the plugin doesn't check for the angles property when importing entities. Only angle and mangle are checked, but the former is just rotation around Z axis (vertical), while the latter is rotation around all axes, but in a different way from angles (pitch yaw roll vs yaw pitch roll).
I'm not being able to correctly rotate my entities using mangle. I don't suppose this has to do with using Valve format, but I could be wrong.

Ah, I guess I overlooked that.  Didn't have anything with "angles" I was testing.
Man this is confusing.
“angles” is interpreted as “pitch yaw roll” (if the entity model is a Quake MDL, pitch is inverted)
“mangle” is interpreted as “yaw pitch roll” if the entity classnames begins with “light”, otherwise it’s a synonym for “angles”

So it needs to behave differently depending on the entity, but that might be kind of ... bleh for custom entities.  Also, that list doesn't seem extensive because "mangle" pitch is inverted for the intermission as well.

Might be worth making it consistent. :)
I personally don't even see the point of mangle. I can't see a reason why one would want to rotate an entity differently if it's a light, specifically, but I could be missing something.
I don't suppose we can safely use angle for spotlights, since TB will interpret it as the angle of rotation. The manual doesn't mention any exceptions to that. I don't see where angle would be useful though. A door wouldn't want to use angle, because it might not be a regular door. It might be a trapdoor, a drawbridge, or an aperture. There might be entities that could use angle, but I can't think of one.
All that's left is angles. Just like the others, if an entity has the property angles, rotating it will update that property, so it's handy.

I would love for them to be consistent, but the problem is, they aren't in Quake, and what is displayed in Trenchbroom is (presumably) how the angles in Quake work, which is different per entity.  If people import existing maps or use the default entities in Quake, it should probably import them in the same manner. 😖

Isn't this something the developer needs to handle in their entity import code?

Ideally, it wouldn't be necessary to handle the angles in each individual entity you have, as you could have hundreds of them, so the importer should just rotate the mesh/spawner/etc. to mach what shows up in the level editor.
"angles" and "mangle" are both supported, but I'm not 100% sure they're correct in all cases.  If anybody has specific examples where it's broken, let me know, otherwise I guess I can close this.

I don't really follow. Even in vanilla Quake the monster facing direction is set in QuakeC just after they're spawned.

Isn't this something the developer needs to handle in their entity import code? Or are the properties just not imported at all?

The properties are imported, but the plugin takes care of converting them from the map editor's coordinate system into Godot's coordinate system for us. Rotation properties are always converted the same way, so it makes sense to let the plugin handle it.

"angles" and "mangle" are both supported, but I'm not 100% sure they're correct in all cases. If anybody has specific examples where it's broken, let me know, otherwise I guess I can close this.

Fine by me to close it. I've been on a long hiatus from this stuff, so I can't give any feedback on it, but I presume it's fine since this thread as been quiet for a while. If there's any problems they'll eventually pop up in another issue anyway. :)


Error: Unmatched field {"name":"routingKey","domain":"shortstr"}

Sometimes exchange.publish got  confused error. I can sure that routingKey is a string.
Error: Unmatched field {"name":"routingKey","domain":"shortstr"}

webserver-2 (err): Fri Nov 13 2015 01:21:10 GMT+0000 (UTC) [MQHD]Send message to appchat failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:12 GMT+0000 (UTC) [MQHD]Send message to appchat failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:15 GMT+0000 (UTC) [MQHD]Send message to appchat failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:15 GMT+0000 (UTC) [MQHD]Send message to devmonitor failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:20 GMT+0000 (UTC) [MQHD]Send message to wlan_clientprobe_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:21 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:30 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:31 GMT+0000 (UTC) [MQHD]Send message to wlan_nat_detect failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:39 GMT+0000 (UTC) [MQHD]Send message to wlan_clientprobe_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:39 GMT+0000 (UTC) [MQHD]Send message to wlan_dpi_app failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:39 GMT+0000 (UTC) [MQHD]Send message to wlan_dpi_url failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:41 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_ap failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:43 GMT+0000 (UTC) [MQHD]Send message to stamonitor failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:51 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:51 GMT+0000 (UTC) [MQHD]Send message to wlan_clientprobe_client failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:21:53 GMT+0000 (UTC) [MQHD]Send message to stamonitor failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:22:00 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_ap failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:22:01 GMT+0000 (UTC) [MQHD]Send message to wlan_wips_ap failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:22:01 GMT+0000 (UTC) [MQHD]Send message to appchat failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}
webserver-2 (err): Fri Nov 13 2015 01:22:03 GMT+0000 (UTC) [MQHD]Send message to stamonitor failed with error: Error: Unmatched field {"name":"routingKey","domain":"shortstr"}

some code sample for upload logs:
var serviceName = basic.serviceName.wlan_clientprobe_client;

var jsonParser = bodyParser.json();

var router = express.Router();

router.all('/', function(req, res, next) {
    console.log('access /clientprobe_client...');
    var sendMsg = {};
    sendMsg.url = req.url;
    sendMsg.method = req.method;
    sendMsg.headers = req.headers;
    sendMsg.body = req.body;
    mqhd.sendMsg(serviceName, JSON.stringify(sendMsg), function(jsondata){
            console.log('  send clientprobe_client msg...'+JSON.stringify(jsondata));
            res.send({Method: sendMsg.body.Method, Message: jsondata.message});
    });

});

the sendMsg :+1:
MqOper.prototype.sendMsg = function (pkey, msg, callback) {
    var sendExchage;

    if (3 == arguments.length) {
        var reqID = basic.setCbMap(callback);
        this.setSendOption('messageId', reqID);
    }

    var option = this.getSendOption();
    if (option.appId == cons.serviceName.webserver) {
        sendExchage = mqoper.exdirect;
    }else {
        sendExchage = mqoper.exreply;
    }

    if(sendExchage)
    {
        try {
            sendExchage.publish(pkey, msg, option);
            console.log((new Date()) + ' [MQHD]Send message to %s success by %s.', pkey, sendExchage.name);
            console.log('  message: %s', msg);
            console.log('  key/option = %s/%s.', pkey, JSON.stringify(option));
        }
        catch(err) {
            console.error((new Date()) + ' [MQHD]Send message to %s failed with error: %s', pkey, err);
        }
    }
    else
    {
        console.error("[MQHD]Exchange "+sendExchage.name+" not around now!");
    }
};

This just happened to me:
"Unmatched field {"name":"routingKey","domain":"shortstr"}"

Very confusing error message. Will update if I figure out what it means.

@jcollum  we try undo some code in the publish method, don't let message entry taskqueue, it runs ok!
Exchange.prototype.publish = function (routingKey, data, options, callback) {

var self = this;
if (this.connection._blocked) {
if (callback) {
return callback(true, new Error('Connection is blocked, server reason: ' + this.connection._blockedReason));
} else {
return;
}
}
options = _.extend({}, options || {});
options.routingKey = routingKey;
options.exchange   = self.name;
options.mandatory  = options.mandatory ? true : false;
options.immediate  = options.immediate ? true : false;
options.reserved1  = 0;
var task = {};
//var task = this._taskPush(null, function () {
//self.connection._sendMethod(self.channel, methods.basicPublish, options);
// This interface is probably not appropriate for streaming large files.
// (Of course it's arguable about whether AMQP is the appropriate
// transport for large files.) The content header wants to know the size
// of the data before sending it - so there's no point in trying to have a
// general streaming interface - streaming messages of unknown size simply
// isn't possible with AMQP. This is all to say, don't send big messages.
// If you need to stream something large, chunk it yourself.
//self.connection._sendBody(self.channel, data, options);
//});
self.connection._sendMethod(self.channel, methods.basicPublish, options);
self.connection._sendBody(self.channel, data, options);
if (self.options.confirm) self._awaitConfirm(task, callback);
return task;
}

@JunejaTung @jcollum This also happened to me with the "expiration" field. After a little digging through the code it seems there is a rather strict data type check when serializing the header. All fields are checked against definitions located in "amqp-definitions-0-9-1.js".
In my case the "expiration" field is marked as "shorstr", which seems like a type-o. I've sent a pull request with the correction #426.
Now, on the issued raised by @JunejaTung:

Sometimes exchange.publish got confused error. I can sure that routingKey is a string.

it makes sense that an apparent "random" error occurs when type checking, but most likely in some cases the value just exceeds the length of 255 characters. Look at the validation in " serializer.js"

if (typeof(param) != "string" || param.length > 0xFF) {
throw new Error("Unmatched field " + JSON.stringify(field));
}

I'm having the same issue except param's value is undefined which obviously isn't a string


Lobbying Ban - EO - ETHICS COMMITMENTS..

Citing EO  - https://www.whitehouse.gov/the-press-office/2017/01/28/executive-order-ethics-commitments-executive-branch-appointees
'whitehouse officials' aka  'every appointee in every executive agency' after January 20, 2017
Section 1 - #1 : (whitehouse officials) I will not, within 5 years after the termination of my employment as an appointee in any executive agency in which I am appointed to serve, engage in lobbying activities with respect to that agency.
Section 1 - #4 : (whitehouse officials)  I will not, at any time after the termination of my employment in the United States Government, engage in any activity on behalf of any foreign government or foreign political party which, were it undertaken on January 20, 2017, would require me to register under the Foreign Agents Registration Act of 1938, as amended.
Please follow (and edit) the guide below to expedite the pull request process.

You will be asked a few questions:
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: pull latest commits before reporting any issues.
Please look at /revamp for the newest version of the site.

[ ] I've verified and I assure that I'm looking at the latest version of Trump Tracker.
[ ] I've looked through /revamp and **I assure ** that this PR doesn't correlate to it.

Before submitting a Pull Request make sure you have:

[ ] At least skimmed through README and most notably the To Do List and CONTRIBUTING.md pages.
[ ] Searched through previous Pull Requests for similar issues including closed ones or just looking at the promises template

Description of your pull request, and other information

Updating Policies and Promises through Pull Requests
There are three variables that need to be modified when a promise gets updated, namely status, update, and citations, through data.yaml.
status has four options:

notStarted = Default status. Nothing of significance has been talked about the promise.
inProgress = Promise is in progress, backed up with news articles and/ or government documents.
broken = Promise is fully broken, backed up with news articles and/ or government documents.
achieved = Promise has been fully completed, backed up with news articles and/ or government documents.

The last modified date for the promise should be placed in the update section. This is for project maintainers to keep track of promises and - in the near future - might be plugged into the website, so it definitely needs to be kept up to date.
The format for date is YYYY-MM-DD, and is enclosed in double quotations. For example: An article about Trump in Feb 03, 2017 will be marked as "2017-02-03".
Where did you find out about the promise getting updated? These news articles should be added into the citations section. All you need to do is plug the news source into one of the provided spaces between the single quotes. The more the better, so please keep on adding news sources. We use this as a Wikipedia-style and In-Text Citations.
Note: Please try to keep the articles bias free, since we aren't trying to lean any way.
Please test after setting up to see if the promise got updated. Use the search function to check if the color got applied.
Setup instructions in Read Me.
After you're done with all of this you're ready to go! Send over the Pull Request and we will get back to you in one business day, if not sooner.
Thank you for your immense contribution, you're helping improve TrumpTracker everday.

fantastic work

Thanks!  Making sure it is okay to cite Executive orders with the proper references.  Cheers!

Definitely is, probably a better source than a news publication.


use slash commands for discord bot insetead of selfmade ones

https://support.discord.com/hc/en-us/articles/1500000368501-Slash-Commands-FAQ


request/ask: change size of map marker based on zoom level

I recall working with the Google Maps API a while back and being to make marker adjustments (show/hide) based on zoom level.
I know this is very specific, but any idea what the react way to get the markers to be aware of current zoom level?  (would i have to setup an event for each marker to listen for zoom changes?)
thanks!

Here https://github.com/istarkov/google-map-clustering-example/blob/master/src/GMap.js output depends on zoom and other param.
Example: http://istarkov.github.io/google-map-clustering-example/

wow fast response!  just what i was looking for -- thanks!


supabase start password authentication issues

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
supabase start is unable to start. FATAL 28P01 (invalid_password) password authentication failed for user "supabase_admin"
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Create a github action
Use supabase/setup-cli@v1, version: latest for supabase, ubuntu-latest for actions runner, actions/setup-node@v3 with node-version: 18
Run supabase start
See error

Expected behavior
Supabase starts and is able to be interacted with
Screenshots

System information

OS: ubuntu latest github actions runner
Browser (if applies): NA
Version of supabase-js: latest
Version of Node.js: 18

Additional context
We've tried clearing any caches on the github action which may be impacting. I saw an issue which seems to be similar here https://github.com/supabase/supabase/issues/11957 The solution there was seemingly clearing docker volumes, etc which I don't think should be an issue on gh action but I'll see if there is any cruft that exists for some reason?

Pinning the supabase/setup-cli@v1 to 1.115.5 seems to get around it. Going back to latest reintroduces the error. I'll do a bit more poking on versions, just selected a semi-recent one (since things were working on Friday) based on NPM releases. I see a few point updates to 1.123 today, but it doesn't look like I can see exactly which version is running in the gh action retroactively when using latest

Some additional version testing:

Version
Starting

1.123.3
❌

1.123.0
❌

1.122.0
❌

1.121.1
❌

1.121.0
❌

1.120.0
❌

1.119.1
✅

1.119.0
✅

1.115.5
✅

Hello, I've encounter exact same thing and reverting back to 1.119.1 helped, thank you and I'm counting that this can be fixed in the future.

Pinning the supabase/setup-cli@v1 to 1.115.5 seems to get around it. Going back to latest reintroduces the error. I'll do a bit more poking on versions, just selected a semi-recent one (since things were working on Friday) based on NPM releases. I see a few point updates to 1.123 today, but it doesn't look like I can see exactly which version is running in the gh action retroactively when using latest

in which file(s) should that be changed?

I'm running through the Self-Hosting w/Docker instructions and hitting the same issue. After changing the the default POSTGRES_PASSWORD and attempting the solutions suggested in password authentication failed for user "supabase_auth_admin" - Docker Sefl Hosting #11957, the analytics and db containers fail to start with the following errors respectively:
17:10:03.190 [error] Postgrex.Protocol (#PID<0.4729.0>) failed to connect: ** (Postgrex.Error) FATAL 28P01 (invalid_password) password authentication failed for user "supabase_admin"

<IP_ADDRESS> 2024-02-08 17:31:32.953 UTC [118] supabase_admin@postgres FATAL:  password authentication failed for user "supabase_admin"

I can then run docker compose restart to get the some of the containers to start and the Supabase GUI to load in my browser, however several of the containers are in an unhealthy state and the logs show database connections errors.
CONTAINER ID   IMAGE                              COMMAND                   CREATED          STATUS                             PORTS                                                                                NAMES
d7680ea347e4   supabase/storage-api:v0.46.4       "docker-entrypoint.s…"    7 minutes ago    Restarting (1) 27 seconds ago                                                                                supabase-storage
940ee1055630   supabase/edge-runtime:v1.33.5      "edge-runtime start …"    7 minutes ago    Up 5 minutes                                                                                supabase-edge-functions
146f42378a80   supabase/gotrue:v2.132.3           "auth"                    7 minutes ago    Restarting (1) 6 seconds ago                                                                                supabase-auth
b0b5cd543ca7   supabase/postgres-meta:v0.75.0     "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (healthy)             8080/tcp                                                                                supabase-meta
568155ff7fe9   kong:2.8.1                         "bash -c 'eval \"echo…"   7 minutes ago    Up 5 minutes (healthy)             <IP_ADDRESS>:8000->8000/tcp, :::8000->8000/tcp, 8001/tcp, <IP_ADDRESS>:8443->8443/tcp, :::8443->8443/tcp, 8444/tcp   supabase-kong
a11c661fd9a9   supabase/realtime:v2.25.50         "/usr/bin/tini -s -g…"    7 minutes ago    Up 10 seconds (health: starting)                                                                                realtime-dev.supabase-realtime
3391cbfbcb53   supabase/studio:20240101-8e4a094   "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (unhealthy)           3000/tcp                                                                                supabase-studio
a240a469f4d4   postgrest/postgrest:v12.0.1        "postgrest"               7 minutes ago    Restarting (1) 5 seconds ago                                                                                supabase-rest
47d642cdf029   supabase/logflare:1.4.0            "sh run.sh"               7 minutes ago    Up 7 seconds (health: starting)    <IP_ADDRESS>:4000->4000/tcp, :::4000->4000/tcp                                                                  supabase-analytics
4c9e82a3c0f0   supabase/postgres:<IP_ADDRESS>       "docker-entrypoint.s…"    7 minutes ago    Up 5 minutes (healthy)             <IP_ADDRESS>:5432->5432/tcp, :::5432->5432/tcp                                                                  supabase-db
3489ef40782c   darthsim/imgproxy:v3.8.0           "imgproxy"                7 minutes ago    Up 5 minutes (healthy)             8080/tcp                                                                                supabase-imgproxy
36c351ef306c   timberio/vector:0.28.1-alpine      "/usr/local/bin/vect…"    30 minutes ago   Up 4 minutes (healthy)                                                                                supabase-vector

$ docker logs 146f42378a80
[...]
{"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to `host=db user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2024-02-08T17:34:50Z"}
{"level":"info","msg":"Go runtime metrics collection started","time":"2024-02-08T17:35:50Z"}
{"args":[0.064195059],"component":"pop","level":"info","msg":"%.4f seconds","time":"2024-02-08T17:35:50Z"}
{"level":"fatal","msg":"running db migrations: Migrator: problem creating schema migrations: couldn't start a new transaction: could not create new transaction: failed to connect to `host=db user=supabase_auth_admin database=postgres`: failed SASL auth (FATAL: password authentication failed for user \"supabase_auth_admin\" (SQLSTATE 28P01))","time":"2024-02-08T17:35:50Z"}

Docker version 25.0.2, build 29cf629
Debian GNU/Linux 12


Pushing custom information to the InferenceResult

I'm looking for a way to insert "probes" into update rules such that custom information can be passed back to the InferenceResult object. This would allow for a user to inspect (and visualize) information on the rule/message level, which would be helpful when developing custom rule implementations.
I currently have two use-cases in mind:

Message statistics can be written to the probe so that the user can inspect (specific) messages;
Custom information during rule computations can be returned, for example to check for convergence when iterating within a rule computation.

In a similar way that Meta and Pipeline objects offer context for inbounds collection and rule computation, a probe might be passed to an update rule. Custom information can then be written to the probe, which is returned to the InferenceResult object (perhaps similar to how posteriors are returned).

We offer partial support for this functionality through addons, although the documentation is currently limited. In essence, addons enable the insertion of custom steps both before and after invoking the rule function. The existing use cases for addons align closely with the points you've proposed:

Debugging information can be incorporated into the messages to trace how, where, and with what arguments they were computed. An illustrative example is available here.
Addons can also be utilized to compute the log-scale of the messages, proving useful in subsequent stages of the inference process. (not documented)

@bvdmitri is this a matter of updating documentation or is there additional functionality required?

I think this is a matter of updating the documentation, because both of the use-cases provided can be covered by the addons.


Chat history in dispute is disappearing

client 2.2.3, server 0.12.0
Dispute is open, I am the mod. Vendor opened dispute and buyer is MIA.
Go to discussion and send some comments.
Server log looks ok:
23:18:06.716 [SendMessage] [DEBUG] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw, etc...
Click away to any other UI view and then back, chat history is completely blank again:

Update: today I got two additional email notifications about this same dispute. The original email was 20 hours ago, and I got the other two 4 and 8 hours ago. Upon entering the (empty) "Discussion" tab, the developer console displays this error:

ob.log:
15:44:55.167 [DEBUG] [recordAgingNotifier/PerformTask] performTask started (count 94)
15:44:55.169 [DEBUG] [recordAgingNotifier/generateSellerDisputeNotifications] created 0 vendor dispute notifications
15:44:55.169 [DEBUG] [recordAgingNotifier/generateSellerDisputeNotifications] updated lastDisputeTimeoutNotifiedAt on 0 sales
15:44:55.177 [DEBUG] [recordAgingNotifier/generateBuyerDisputeTimeoutNotifications] created 0 purchase dispute notifications
15:44:55.180 [DEBUG] [recordAgingNotifier/generateBuyerDisputeTimeoutNotifications] updated lastDisputeTimeoutNotifiedAt on 0 purchases
15:44:55.192 [DEBUG] [recordAgingNotifier/generateBuyerDisputeExpiryNotifications] created 0 buyer expiration notifications
15:44:55.193 [DEBUG] [recordAgingNotifier/generateBuyerDisputeExpiryNotifications] updated lastDisputeExpiryNotifiedAt on 0 purchases
15:44:55.295 [DEBUG] [recordAgingNotifier/generateModeratorDisputeExpiryNotifications] created 0 dispute expiration notifications
15:44:55.334 [DEBUG] [recordAgingNotifier/generateModeratorDisputeExpiryNotifications] updated lastDisputeExpiryNotifiedAt on 2 disputes
15:44:55.963 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:44:57.036 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:44:58.547 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:44:59.769 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:00.843 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:01.949 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:02.387 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:27.992 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:27.994 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:45:50.163 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:46:10.061 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyDbXhwoiU2sNTERGckHowMzHHbnxxgPVmKMp4t79gKe
15:46:11.838 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyDbXhwoiU2sNTERGckHowMzHHbnxxgPVmKMp4t79gKe
15:46:28.015 [ERROR] [core/EncryptMessage] Failed to find public key for QmWyDbXhwoiU2sNTERGckHowMzHHbnxxgPVmKMp4t79gKe
15:47:09.468 [DEBUG] [service/handleChat] Received CHAT message from QmXmpJc4P7Z3NcPtm9WGmfUFqoQExPy1ZYEna8aY1WfSxW
15:47:15.949 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:47:15.951 [DEBUG] [service/SendMessage] Sending CHAT message to QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
15:48:18.838 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmTJ1fUiqezCa2X7sR16vXprhwcVEJB2P2GS9aR6aWLzF2: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

@placer14 @tyler-smith @cpacia do the logs above give you and idea of what might be happening here?

Nothing that looks bad for QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw (the person the discussion references earlier) but it could be that the chat messages wouldn't be committed if the public key for a peer is not found. I believe the pub key for the recipient is needed to encrypt the chat message and if it's unavailable, it would just disappear. I'm not sure how the frontend handles such a case.
Though the logs only show the missing pub key issue is happening for QmWyDbXhwoiU2sNTERGckHowMzHHbnxxgPVmKMp4t79gKe.
@pinheadmz Could you post the peerIDs of the vendor and the buyer? Or would you happen to know which server version they're running? Might be useful to recreate the issue. Would you be able to upgrade your local server to the recent 0.12.2 release (making a backup of your data directory first) to see if the issue continues to persist?

vendor: QmSYkCtLM9TxeEtuiDUH93WDSomfBhtujJPzhstCcMeTMw
buyer: QmWyDbXhwoiU2sNTERGckHowMzHHbnxxgPVmKMp4t79gKe
Vendor told me in a DM he had upgraded to latest, same with me, but we might have upgraded at different times or one or both of us upgrade after the dispute was opened.
Having the exact same issue with another dispute. Same vendor but different buyer (also appears to be offline): QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
$ cat ~/.openbazaar2.0/logs/ob.log | grep QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:01.644 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:02.936 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:03.979 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:06.344 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:15.838 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:16.912 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:18.296 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:20.446 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:41.915 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:36:41.918 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
00:37:47.334 [ERROR] [core/EncryptMessage] Failed to find public key for QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:43.843 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:44.880 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:45.943 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:46.994 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:48.284 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:49.327 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:36:50.786 [DEBUG] [service/SendMessage] Sending CHAT message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
05:38:36.522 [ERROR] [core/EncryptMessage] Failed to find public key for QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
15:53:35.755 [DEBUG] [service/SendMessage] Sending DISPUTE_CLOSE message to QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs
15:53:54.133 [DEBUG] [core/SendOfflineMessage] Sending offline message to: QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs, Message Type: DISPUTE_CLOSE, PointerID: QmR5JvAm2bVxhrRnwLtuD8FUxpff7fEVjEHbrireNK82m9, Location: /ipfs/zb2rheFSXE32obcRdVB3uzd4LfGtzAVNcfUXqECPmtVVVkgKV
18:52:35.398 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
18:53:28.748 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
18:54:20.505 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
18:54:33.935 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
18:56:37.503 [ERROR] [core/IPNSResolve] Get https://gateway.ob1.io/ob/ipns/QmWyGuPgEC3KfRTMJXqTKXaAaLf6X3n4PVWyF3WKUPAPGs: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Guys, this keeps happening. I can't moderate disputes.
Going to shut off moderation until this addressed, I don't want to taint my reputation as a "verified" moderator if the communication channels are down.
Logs look fine:
20:45:40.256 [DEBUG] [service/SendMessage] Sending CHAT message to QmSg6Pn5Pfpe2y6hfEe2UooNatdG1Gf8guyEA56V5madk8
20:45:40.257 [DEBUG] [service/SendMessage] Sending CHAT message to QmXF8cmS3WNmi2om1j2XuFrUSf5RUVuDYZXnBuVKWBkNDq

when I DM the vendor (outside of the dispute channel) I get a more robust log message:
20:49:02.218 [DEBUG] [core/SendOfflineMessage] Sending offline message to: QmXF8cmS3WNmi2om1j2XuFrUSf5RUVuDYZXnBuVKWBkNDq, Message Type: CHAT, PointerID: QmZmKY3jZrCkcTHFTL3bmoGXXAGJYoJu47iwT78RdkEGaz, Location: /ipfs/zb2rhakxbBCZAnX9YL3pTbjbFhfYBVF8aBSj41TF6je7vEt3R

Update: OK the messages are still disappearing, but they do come back... after about 5 minutes. So I guess this only happens when a party is offline. The GUI doesn't even display the message until it gets an ACK or sends the message offline. Would be great to see a "pending" indicator in the chat instead of just hiding the message...?
22:23:04.635 [DEBUG] [service/SendMessage] Sending CHAT message to QmVYw52B49FoymPiXHSxzzVR1b4XcscDufd84wv9iKZoPu
22:24:50.033 [DEBUG] [service/SendMessage] Sending CHAT message to QmSg6Pn5Pfpe2y6hfEe2UooNatdG1Gf8guyEA56V5madk8
<... snip ...>
22:27:56.386 [DEBUG] [recordAgingNotifier/PerformTask] performTask started (count 418)
22:27:56.398 [DEBUG] [recordAgingNotifier/generateSellerDisputeNotifications] created 0 vendor dispute notifications
22:27:56.399 [DEBUG] [recordAgingNotifier/generateSellerDisputeNotifications] updated lastDisputeTimeoutNotifiedAt on 0 sales
22:27:56.410 [DEBUG] [recordAgingNotifier/generateBuyerDisputeTimeoutNotifications] created 0 purchase dispute notifications
22:27:56.411 [DEBUG] [recordAgingNotifier/generateBuyerDisputeTimeoutNotifications] updated lastDisputeTimeoutNotifiedAt on 0 purchases
22:27:56.419 [DEBUG] [recordAgingNotifier/generateBuyerDisputeExpiryNotifications] created 0 buyer expiration notifications
22:27:56.419 [DEBUG] [recordAgingNotifier/generateBuyerDisputeExpiryNotifications] updated lastDisputeExpiryNotifiedAt on 0 purchases
22:27:56.552 [DEBUG] [recordAgingNotifier/generateModeratorDisputeExpiryNotifications] created 0 dispute expiration notifications
22:27:56.592 [DEBUG] [recordAgingNotifier/generateModeratorDisputeExpiryNotifications] updated lastDisputeExpiryNotifiedAt on 3 disputes
22:28:12.817 [DEBUG] [service/SendRequest] Sending STORE request to QmY8puEnVx66uEet64gAf4VZRo7oUyMCwG6KdB9KM92EGQ
22:28:12.821 [DEBUG] [service/SendRequest] Sending STORE request to QmPPg2qeF3n2KvTRXRZLaTwHCw8JxzF4uZK93RfMoDvf2o
22:28:12.827 [DEBUG] [service/SendRequest] Sending STORE request to QmPPegaeM4rXfQDF3uu784d93pLEzV8A4zXU7akEgYnTFd
22:28:12.851 [DEBUG] [core/SendOfflineMessage] Sending offline message to: QmXF8cmS3WNmi2om1j2XuFrUSf5RUVuDYZXnBuVKWBkNDq, Message Type: CHAT, PointerID: QmZmKY3jZrCkcTHFTL3bmoGXXAGJYoJu47iwT78RdkEGaz, Location: /ipfs/zb2rhdMPUi1p3tg2rVrq4TRcFcGfidJunYTeo7ei3acESbqqH
22:28:13.055 [DEBUG] [service/SendRequest] Received response from QmPPg2qeF3n2KvTRXRZLaTwHCw8JxzF4uZK93RfMoDvf2o
22:28:13.055 [DEBUG] [core/SendStore] Sending 1 blocks to QmPPg2qeF3n2KvTRXRZLaTwHCw8JxzF4uZK93RfMoDvf2o
22:28:13.056 [DEBUG] [service/DisconnectFromPeer] Disconnecting from QmPPg2qeF3n2KvTRXRZLaTwHCw8JxzF4uZK93RfMoDvf2o
22:28:13.164 [DEBUG] [service/SendRequest] Received response from QmY8puEnVx66uEet64gAf4VZRo7oUyMCwG6KdB9KM92EGQ
22:28:13.165 [DEBUG] [core/SendStore] Sending 1 blocks to QmY8puEnVx66uEet64gAf4VZRo7oUyMCwG6KdB9KM92EGQ
22:28:13.167 [DEBUG] [service/DisconnectFromPeer] Disconnecting from QmY8puEnVx66uEet64gAf4VZRo7oUyMCwG6KdB9KM92EGQ

--> after these last messages displayed in the log, the chats came back in the GUI

@cpacia do you have any ideas on what would cause this to happen? It shouldn't take 5 minutes to retrieve messages.

Also seeing logs like this for user IDs involved in the weird disputes:
21:47:10.857 [ERROR] [core/EncryptMessage] Failed to find public key for QmR2xoY4TNZqCJbLjM1aTEBUsikJntzuRC8ZyUiaYYmgzy

I've had this problem as well. Possibly on a related note, when messages do get delivered, I've noticed some major lag. About 20 to 30 minutes. Recently, I resolved a dispute and then started receiving new messages about 40 minutes after closing the dispute. Also, while the vendor was logged in and chatting, it still showed that the vendor's contract had not been sent. The vendor's contract wasn't even received until about an hour after chatting with him and about 30 minutes after the dispute had been closed. Let me know if you'd like logs or if I should open a new issue. At first glance they seem related to what @pinheadmz is experiencing.

@pinheadmz The markchatasread 500 error you're getting is unrelated to the missing chat messages problem you're experiencing here. I have found a fix for that 500 error which will get delivered on the next update.
I've been testing this scenario with a 0.12.0 release and having a hard time getting it to happen locally. I'll do an audit of the message/chat handling code to see if anything jumps out at me... It's not obvious what's going wrong here, at first glance.

@cpacia this seems like a relatively new issue from within the past few months. It never used to take that long. It seems to be lagging across the board though. Not just dispute messages. Thanks for the insight. I'll watch my network traffic next time. If you have suggestions on how to check this let me know.
I would think, even if I'm behind NAT, I can take incoming connections without any modifications to my network. Not sure. I haven't blocked any ports specifically since I've started using OB.

@cpacia Handling a brand new dispute now. Messages I type disappear again, but this time they reappear once the offline message has been posted to the offline parties. (I'm watching the logs). I wonder if the reason I sometimes never see the message again is that weird no public key found error. Not sure why the UI handles it this way. Even if the message is still being delivered, it should remain in the view. Maybe you can add checkmarks in the chat window to show message receipt status the way you do in regular DM chat window.

FYI, @pinheadmz we're going to prioritize and implement this fix before continuing to troubleshoot this issue. This could fix it or not, but let's hold until we deliver https://github.com/OpenBazaar/openbazaar-go/issues/1093 to see if we need to proceed further.

@pinheadmz @webunraveling We've narrowed down this issue to a few causes.
The primary cause is currently, we show the message you've sent in the UI while it's still in a sending state, but the server doesn't record the message until it is successfully sent. If your node is unable to connect directly with the other node, sending the message can take a very long time.
If you do anything to refresh the view (such as closing the modal or reloading your app), the UI loses your pending message, and can't retrieve it because it hasn't been recorded by the server yet. This causes it to "disappear", only to reappear later if you refresh the view again after the send has completed.
We're going to fix this in #1532, but it's not scheduled to be worked on until after we complete the multi wallet work in release 2.3.
There are probably some other issues involved here with messages, which we have on our radar to fix but they'll be a pretty significant refactor of a few things. The short version is most users are behind firewalls or routers that block incoming messages, which makes them hard for other nodes to reach and communicate with.
You can make your own node easier to communicate with by forwarding your ports. You should also check any firewalls you're running to make sure they're allowing incoming messages for openbazaard.exe.
https://openbazaar.zendesk.com/hc/en-us/articles/360000282912-How-to-forward-ports-for-OpenBazaar

I'm closing this because the primary issue will be fixed in #1532


[FLINK-21577] [java] Fix instantiation error with SimpleType.simpleTypeFrom()

This was failing with an Collection is empty when attempting to copy the enum set of TypeCharacteristics.
I think the only reason we need to do a copy, is if users instantiate a SimpleType directly with the constructor (and not the simpleTypeFrom, simpleImmutableTypeFrom factory methods).
IMO, we probably can expect users to just use the factory methods, and not the constructor.
If they need to do anything more complex, they should just create a Type subclass directly.
Therefore, this PR makes the constructor private to enforce instantiation a SimpleType via the factory methods.
This would allow the constructor to be simpler and remove the EnumSet.copyOf operation.

Thanks for the review @igalshilman!
Will address your comment and merge this.


Add project pages: Fast Neutron mutants and SoyTEdb

This branch does three things:
(1) Fixes the main nav-bar PROJECTS drop-down (the code was malformed so the drop-down failed)
(2) Adds a Fast Neutron project page to give access to the main data from https://www.soybase.org/mutants/
(3) Adds a SoyTEdb project page to give access to the main data from https://www.soybase.org/soytedb/
The "mutants" and "SoyTEdb" are fairly rudimentary. The mutants page could be extended to display images and phenotype descriptions similar to http://localhost:4000/projects/SoyNAM/ -- and/or we could point to a containerized instance of the database, as @nathanweeks suggested. But both of these options would be larger development efforts.
My preference is to merge these changes to main quickly - in part, to fix the PROJECTS drop-down -- and then do another iteration if we decide there's more to be done with these project pages.

I have reviewed pull request. The fixed main nav-bar PROJECTS drop-down works well.  Both Fast Neutron project page and SoyTEdb project page look good to me and the links work for me. Just one little thing: On the Project index page for the Soybean Transposable Elements / SoyTEdb part: Characters in SoyBase ID and Project page lines are in italics which are inconsistent with the others.

Thanks for reviewing and for catching that, Wei. I have fixed the italics in the SoyTEdb project page description.


set desplayName to name by default

Description
This PR prevents a null display name on VMs (see https://github.com/apache/cloudstack/pull/8503#issuecomment-2367394302)

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@DaanHoogland
it looks like an UI issue
the API response does have the "displayname" in place. but the name/displayname is not displayed on UI.
as a simple workaround, can we revert #8503  ? @DaanHoogland

as a simple workaround, can we revert #8503 ? @DaanHoogland

yes, you are right, I'll creat another PR, reapply the changes here, and work on this later.

@blueorangutan ui

@weizhouapache a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.


npm start not working events.js174 throw er; //Unhandled 'error' event

Is this a bug report?
yes

Did you try recovering your dependencies?

yes
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

Environment Info:
System:
OS: Windows 10
CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Binaries:
Node: 10.15.3 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Not Found
Internet Explorer: Not Found
npmPackages:
react: ^16.8.6 => 16.8.6
react-dom: ^16.8.6 => 16.8.6
react-scripts: 3.0.0 => 3.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

(Write your steps here:)

cd my-app
2, npm start

create-react-app my-app

cd my-app

npm start

or

create-react-app my-app
cd my-app
npm start

Expected Behavior

Run the app in development mode
Open http://localhost:3000 to view it in the browser
Actual Behavior

when starting my react-app:

when starting a newly created react app

events.js:174
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: react-scripts start
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!      C:\Users\calde\AppData\Roaming\npm-cache_logs\2019-05-04T18_42_43_606Z-debug.log
log file:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Users\calde\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Users\calde\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\calde\Documents\Media\programming\react\maze\node_modules.bin;C:\Program Files\nodejs;C:\Users\calde\AppData\Roaming\npm;
9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\Users\calde\Documents\Media\programming\react\maze
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'react-scripts start' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
13 verbose stack Error<EMAIL_ADDRESS>start: react-scripts start
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (C:\Users\calde\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:189:13)
13 verbose stack     at ChildProcess. (C:\Users\calde\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:189:13)
13 verbose stack     at maybeClose (internal/child_process.js:970:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\Users\calde\Documents\Media\programming\react\maze
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Users\calde\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v10.15.3
19 verbose npm  v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>start: react-scripts start
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Reproducible Demo

https://github.com/NickCalderone/maze

I'm facing the same issue in Windows 64.
npm test, build, eject works fine and only npm start fails.
Node js project and old react projects using webpack ( "start": "webpack-dev-server --mode development --config webpack.dev.config.js") works fine as well.
What's the fix for this?

I am also running into the same error.

I fount the solution to my issue.  It turns out I didn't have all of my default path environmental variables for windows.  Check this link for the defaults and hope this helps someone else out there with the same problem.
https://www.computerhope.com/issues/ch000088.htm

I ran into this exact issue as well and found that it is only present with<EMAIL_ADDRESS>downgrading to<EMAIL_ADDRESS>resolved the issue without needing to mess with environment variables.
create-react-app my-app
cd my-app
npm install<EMAIL_ADDRESS>npm start

thankyou @tylerlaberge it worked for me...

I fount the solution to my issue. It turns out I didn't have all of my default path environmental variables for windows. Check this link for the defaults and hope this helps someone else out there with the same problem.
https://www.computerhope.com/issues/ch000088.htm

Hello sir. I checked out the link you pasted, but found nothing

I had this problem a few days ago and after try all the things possible, i check the that w10 has an update resolving a js bug. So i update w10 and it worked.

@JoshMatthew
the %PATH% section of the link shows the default variables in your machines PATH:
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;
any other paths can be added to the end. Remember to have the npm paths as well:
C:\Program Files\nodejs;C:\Users{yourName}\AppData\Roaming\npm

I felt in same problem. Thank you @tylerlaberge it worked for me...

thank you so much @tylerlaberge


Invalid Format Error in OSX

Problem running grobid on osx (actually macOS).
I used the installation process described in the doc :
wget https://github.com/kermitt2/grobid/archive/grobid-parent-0.4.1.zip
unzip grobid-grobid-parent-0.4.1.zip
mvn clean install

And then the tests don't pass, because "invalid format error" when loading the wapiti models. If skip the test I get the same error when I try grobid on a PDF.

Thanks @thomasopsomer for reporting this issue.
I've tried to reproduce your problem without success.
I'm running Mac OSX El Capitan. I've downloaded the zip and run the build without skipping the tests, everything was fine. Also running the service I didn't get your issues.
Could you provide me a more detailed error log and some more information about your system?
Thanks
Luca

Hello Luca,
So I'm running the new osx version: macOS Sierra v10.12. Like you it was working on El Capitan :)
I downloaded the zip and then when building with tests, here is a sample of logs:
Running org.grobid.core.test.TestFullTextParser
Loading external native CRF library
Loading Wapiti native library...
Library crfpp loaded
Loading model: /Users/thomasopsomer/grobid/grobid-home/models/fulltext/model.wapiti (size: 6685602)
[Wapiti] Loading model: "/Users/thomasopsomer/grobid/grobid-home/models/fulltext/model.wapiti"
error: invalid model format
Running org.grobid.core.test.TestHeaderParser
Loading external native CRF library
Loading Wapiti native library...
Library crfpp loaded
Loading model: /Users/thomasopsomer/grobid/grobid-home/models/header/model.wapiti (size: 36094028)
[Wapiti] Loading model: "/Users/thomasopsomer/grobid/grobid-home/models/header/model.wapiti"
error: invalid model format
Running org.grobid.core.test.TestNameParser
Loading external native CRF library
Loading Wapiti native library...
Library crfpp loaded
Loading model: /Users/thomasopsomer/grobid/grobid-home/models/name/header/model.wapiti (size: 2055704)
[Wapiti] Loading model: "/Users/thomasopsomer/grobid/grobid-home/models/name/header/model.wapiti"
error: invalid model format
Running org.grobid.core.test.TestReferencesParser
Loading external native CRF library
Loading Wapiti native library...
Library crfpp loaded
Loading model: /Users/thomasopsomer/grobid/grobid-home/models/citation/model.wapiti (size: 12972361)
[Wapiti] Loading model: "/Users/thomasopsomer/grobid/grobid-home/models/citation/model.wapiti"
error: invalid model format

....

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] grobid-parent ...................................... SUCCESS [  0.484 s]
[INFO] grobid-home ........................................ SUCCESS [ 16.847 s]
[INFO] grobid-core ........................................ FAILURE [ 55.110 s]
[INFO] grobid-trainer ..................................... SKIPPED
[INFO] grobid-service ..................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:12 min
[INFO] Finished at: 2016-10-13T12:31:04+02:00
[INFO] Final Memory: 26M/425M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project grobid-core: ExecutionException; nested exception is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? -> [Help 1]

Wow, what Apple didn't say about Sierra? :-o
Can we check that the md5sum, checksum and dimension of the models has not been changed? I doubt so.
There are mine:
Md5:
Johan:models lfoppiano$ md5 fulltext/model.wapiti
MD5 (fulltext/model.wapiti) = e7a234087a43f18daaafe41f7a1e6426
Johan:models lfoppiano$ md5 header/model.wapiti
MD5 (header/model.wapiti) = 1ae582a2abc0ad27dc8d08b9d1edbf1d

Checksum:
Johan:models lfoppiano$ shasum header/model.wapiti
b33401ac16516fff2aa7d25b9a163719032d9cbb  header/model.wapiti
Johan:models lfoppiano$ shasum fulltext/model.wapiti
02d6627b690894da5b848b119e580ed7aa0de49f  fulltext/model.wapiti

dimension:
Johan:models lfoppiano$ ls -l  fulltext/model.wapiti
-rw-r--r--  1 lfoppiano  staff  6685602 Oct  2 00:10 fulltext/model.wapiti
Johan:models lfoppiano$ ls -l  header/model.wapiti
-rw-r--r--  1 lfoppiano  staff  36094028 Oct  2 00:10 header/model.wapiti

mine :)
MD5:
md5 fulltext/model.wapiti
MD5 (fulltext/model.wapiti) = e7a234087a43f18daaafe41f7a1e6426
md5 header/model.wapiti
MD5 (header/model.wapiti) = 1ae582a2abc0ad27dc8d08b9d1edbf1d

Checksum
shasum header/model.wapiti
b33401ac16516fff2aa7d25b9a163719032d9cbb  header/model.wapiti
shasum fulltext/model.wapiti
02d6627b690894da5b848b119e580ed7aa0de49f  fulltext/model.wapiti

dimension
-rw-r--r--  1 thomasopsomer  staff  6685602  2 oct 00:10 fulltext/model.wapiti
-rw-r--r--  1 thomasopsomer  staff  36094028  2 oct 00:10 header/model.wapiti

Everything seems identical.

I'm baffled!
Let's see the termination lines. If you run this command it should compare the file with LF termination line with the original:
dos2unix < fulltext/model.wapiti | cmp -s - fulltext/model.wapiti

If this is negative... I'm out of ideas for the moment :(

the cmd doesn't return anything, I guess it's positive ?

it depends :) it means there is no difference... so the problem is somewhere else 🗡
...thinking...

Hello Thomas,
Well negative to find the problem ;)
Just another idea, what is your locale settings?

locale

Normally, the issue related to locale have been solved since ~2 years with our Wapiti fork, but who knows...

Hello Patrice,
locale gives:
LANG="fr_FR.UTF-8" LC_COLLATE="fr_FR.UTF-8" LC_CTYPE="fr_FR.UTF-8" LC_MESSAGES="fr_FR.UTF-8" LC_MONETARY="fr_FR.UTF-8" LC_NUMERIC="fr_FR.UTF-8" LC_TIME="fr_FR.UTF-8"
Anyway the good turn-around is to use Docker :)

Ah sure, Docker is the hammer solution !
What happens if you change your LOCALE in your terminal before launching GROBID? Simply try:

export LC_ALL=C

wow magic, the test passed and build completed with success :)

It means to check why the change of LOCALE integrated in our Wapiti fork (just before reading the CRF model, in order to be sure to have portable models) is not working anymore on Mac OS X 10.12 :(
The other related problem is that the architecture info changed, because Apple renamed "OS X" into "macOS", this could impact the resolution of the path to the native stuff based on the architecture.
Thanks a lot Thomas for helping us!

I've had similar problems on macOs sierra on which the workaround setting LC_ALL="C" worked.
I've managed to solve the issues by recompiling wapiti on macOS sierra. See pull request #240


Remove support for Android (comp/core changes)

What does this PR do?
This is a followup to #13699 that removes support for Android in the code in #13662, which is still pending review.
Motivation

Additional Notes
I'll rebase this PR against main once #13662 lands.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Same as #13622.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

(holding off on merging this until we hear confirmation from @derekwbrown that this is unused)

Failures look like the usual system-probe errors.

It seems that core.BundleParams#LogToFile was removed from #13662 and ended up being re-added by this PR.  I suspect that was due to some merge conflicts at some point.
It should be there (it's used in #13722), but should have been introduced in #13662 and not this PR.  So, it's fine.


Vim9: crash when referring to script-local variable deleted in legacy function

Describe the bug
In Vim9 script, referring to a script-local variable deleted in a legacy function might make Vim crash.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    var name: string
    def FuncA()
        name = 'test'
    enddef
    FuncA()
    fu FuncB() abort
        unlet! s:name
    endfu
    FuncB()
    def FuncC()
        echo name
    enddef
    FuncC()
EOF
)

Vim crashes, or an internal is raised:
E685: internal error: copy_tv(UNKNOWN)

Expected behavior
Vim doesn't crash, and no internal error is raised.
Environment

Vim version: 8.2 Included patches: 1-2148
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(362)

Additional context

backtrace
valgrind log
asan log

On my machine (Ubuntu 16.04), Vim crashes systematically.
But in a virtual machine (Ubuntu 18.04), Vim doesn't crash; instead an internal error is raised.
No idea why the difference; in both cases, I compile Vim with the same commands:
$ make clean
$ make distclean
$ git pull
$ ./configure
$ make

I wonder whether Vim should disallow the usage of legacy functions in a Vim9 script, just like it disallows the nesting of a legacy function in a Vim9 function.  I (naively?) think that "progressing" makes sense (legacy → Vim9), while "regressing" does not (Vim9 → legacy); and I suspect that allowing legacy functions in a Vim9 script will create all kind of weird issues such as this one.
What's the purpose of a legacy function in a Vim9 script anyway?
If you want the best performance, readability, reliability (thanks to type checking), you completely (re-)write your script in Vim9.
If you just want to improve the performance, readability, reliability, without (re-)writing your whole script, then you only refactor the few functions which are the slowest/ugliest in Vim9.  But your script remains largely written in Vim script legacy (and no :vim9script at the top).
It seems to me that a Vim9 script with no legacy functions, and a legacy script with optionally some Vim9 functions cover most if not all need.

Regression introduced in 8.2.1846.

I wonder whether Vim should disallow the usage of legacy functions in
a Vim9 script, just like it disallows the nesting of a legacy function
in a Vim9 function.  I (naively?) think that "progressing" makes sense
(legacy → Vim9), while "regressing" does not (Vim9 → legacy); and I
suspect that allowing legacy functions in a Vim9 script will create
all kind of weird issues such as this one.
What's the purpose of a legacy function in a Vim9 script anyway?

Legacy functions are not compiled, thus provide more flexibility.  E.g.
in tests one can do this:
func Test_some()
  CheckFeature terminal
  terminal some command
endfunc

This throws an exception at "CheckFeature" and doesn't even try to parse
the rest of the function.  When compiling the function the ":terminal"
command might not exist and compiling fails before the CheckFeature
command is executed.

If you want the best performance, readability, reliability (thanks to
type checking), you completely (re-)write your script in Vim9.
If you just want to improve the performance, readability, reliability,
without (re-)writing your whole script, then you only refactor the
few functions which are the slowest/ugliest in Vim9.  But your script
remains largely written in Vim script legacy (and no :vim9script at
the top).
It seems to me that a Vim9 script with no legacy functions, and a
legacy script with optionally some Vim9 functions cover most if not
all need.

It should work best, but in some corner cases it can be useful to use a
legacy function.  And calling a function defined in a legacy script is
probably also quite useful.
--
ARTHUR:    ... and I am your king ....
OLD WOMAN: Ooooh!  I didn't know we had a king.  I thought we were an
autonomous collective ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


make packer hangs

git @ 680349531f07406685aaa200915f064c9d926527

CPU architecture, OS, and Version:
openSUSE Tumbleweed, x86_64

Describe the bug
make packer hangs.
strace shows that it's reading from stdin

To Reproduce
make packer

Expected behavior
make packer succeeds.

Logs

Additional context
Do we need the packer target at all ?

It's calling the wrong packer:
> which packer
/usr/sbin/packer
> rpm -qf /usr/sbin/packer
cracklib-2.9.7-1.8.x86_64

:man_facepalming:


Added the new unit test case for the secret_search_command

Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status

[x] In Progress
[ ] Ready
[ ] In Hold - (Reason for hold)

Related Issues
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer
Minimum version of Cortex XSOAR

[ ] 6.0.0
[ ] 6.1.0
[ ] 6.2.0
[x] 6.5.0

Does it break backward compatibility?

[ ] Yes

Further details:

[x] No

Must have

[x] Tests
[x] Documentation

Closing this PR due CLA conflict


Consistent implementation wrt implicit select value semantics

Currently implicit select value semantics is only partly implemented, which leads to confusion. We need to either implement this consistently throughout or revert the part that is implemented.
See #2671 for more info. Needs to be discussed with @jdegoes

See here.

See here for another example of inconsistency: https://github.com/quasar-analytics/quasar/issues/2061#issuecomment-328181658


How to integrate with sonar

Hello @gmazzo
We have noticed final reports is having all the html files. But for sonar will expect executable file as input.
In general if we have the feasibility of integrate the final output from the plugin to sonar. Can you please mention the steps in the readme if it available. Thank you in Advance.
Example : <sonar.jacoco.reportPath>${project.basedir}/../target/jacoco.exec</sonar.jacoco.reportPath>

Like #63, configuring Sonar is out of scope of this plugin. This plugin is meant to fill the gap between AGP and JaCoCo Report Aggregation Plugin
Again, said that, instead of referring the .exec files (wich are single execution data generated by JaCoCo instrumentation on each Test task) you should be providing the aggregated report outcome, in XML format:
plugins {
    id("org.sonarqube") version "<IP_ADDRESS>77"
}

sonar {
    properties {
        property("sonar.coverage.jacoco.xmlReportPaths", "build/reports/jacoco/jacocoAggregatedReport/jacocoAggregatedReport.xml")
    }
}

tasks.sonar {
    dependsOn(tasks.jacocoAggregatedReport)
}

Sadly, the sonar plugin is poorly designed and you can't use Property API on it to have it linked property in a Gradle way :(


Added 3D convolution operator support

I have added the 3D convolution support for PoolBase, ConvNode and ConvTransposeNode

Hi, please provide a method to examine your node at least on one model. You can share a public model link or some onnx.helper or pytorch scripts to create such a model with Conv3D.

I've added C3D model with Conv3D to benchmark datasets. After whole datasets test, this pr will be merged.

The datasets test passed.


Azure Functions in .NET 6. Failed to load System.IO.Abstractions.

Cannot run with System.IO.Abstractions latest version
To Reproduce
Create an Azure Functions project for .NET 6.
Run it. Note the runtime error:
[2021-11-19T02:33:26.035Z] Could not load file or assembly 'System.IO.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=96bf224d23c43e59'. The system cannot find the file specified.

Expected behavior
It properly loads
Would be great if there was a way to get System.IO.Abstractions to load regardless of what version is expected. How?

I got past it! THIS fixed it for me. Add this to a <PropertyGroup> in your .csproj.
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

I got past it! THIS fixed it for me. Add this to a <PropertyGroup> in your .csproj.
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

OK, this is really weird. Any idea why this is necessary?

Not sure. Maybe @davidfowl knows?

I really have questions here 😅...

How did you people figure out that that Property value would fix the issue?
why would any build step involving the function host in fact remove assemblies that are referenced by the functions project?

Apart from that, yes, after adding that property, my .NET6 / Function Tools v4 project starts again with System.IO.Abstractions usage

@fabiocav I see you have last touched the clean-up list https://github.com/Azure/azure-functions-host/blob/dev/tools/ExtensionsMetadataGenerator/test/ExtensionsMetadataGeneratorTests/ExistingRuntimeAssemblies.txt.
Should the third-party-library System.IO.Abstractions.dll (from this repository) really be there?


Evolution of js-ipfs (Visualization)

Fonud this by accident https://www.youtube.com/watch?v=rfMk1mSobMY

Pretty cool! :D THank you

This is fascinating!

How easy is to generate these?

the video mentions Gource Visualization in the title
https://github.com/acaudwell/Gource
something like this:
gource --hide dirnames,filenames --seconds-per-day 0.1 --auto-skip-seconds 1 -1280x720 -o - | ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast -pix_fmt yuv420p -crf 1 -threads 0 -bf 0 gource.mp4

example from: http://www.fullybaked.co.uk/articles/getting-gource-running-on-osx
(I haven't tried this myself)

@lgierth would you be interested in setting this up for js-ipfs, go-ipfs, js-libp2p and go-libp2p and make them availble through, for example: gource.ipfs.io/{js-ipfs, go-ipfs, ..} ?

@lgierth would you be interested in setting this up for js-ipfs, go-ipfs, js-libp2p and go-libp2p and make them availble through, for example: gource.ipfs.io/{js-ipfs, go-ipfs, ..} ?

Nope not interested :) Gource is just a CLI tool that uses OpenGL for rendering - everything else for making this run in browsers is missing.
I'll happily set up a domain though if someone else makes it work and puts it into ipfs.


Check vc_nonSyn`` argumet in read.maf` for details

When I read multiple maf files using the following command
maf_m <- lapply(paste("~/xxx/",list.files("~/xxx/"), sep = ""), read.maf, clinicalData=meta_data, verbose = FALSE)
I got the following errors
Error in FUN(X[[i]], ...) : No non-synonymous mutations found
Check `vc_nonSyn`` argumet in `read.maf` for details

I saw from other issues it is because of no non-synonymous mutations found in some of these files and can avoid this kind of problem by change vc_nonSyn parameter.
But I will use the merged maf to compare with TCGA dataset by the function tcgaCompare, so it would be better if do not change vc_nonSyn.
Are there any other ways I can avoid these problems? Thanks.

May be you can set read.maf() in a chunk of tryCatch(), I mean bypassing the errored files.
lapply(paste("~/xxx/",list.files("~/xxx/"), sep = ""), function(x) {
  tryCatch({
    read.maf(x, clinicalData=meta_data, verbose = FALSE)
  }, error = function(e) {
    NULL
  })
})

Actually, I more recommend that you merge the data firstly, then load it with read.maf().
maf_m <- data.table::rbindlist(lapply(paste("~/xxx/",list.files("~/xxx/"), sep = ""), data.table::fread))

maf <- maftools::read.maf(maf_m)

I found PA has already shown an example for this at https://github.com/PoisonAlien/maftools/issues/943#issuecomment-1573695668


Rendering issue - File content is available but cannot view it

Attach (recommended) or Link to PDF file here:
IRS Form (v.2) (1).pdf
Configuration:

Web browser and its version: Chrome Version 100.0.4896.75 (Official Build) (x86_64)
Operating system and its version: macOs Big Sur version 11.6
PDF.js version: 1.5.188
Note latest version is giving problems with rendering every other file, this version perfectly fits our use case, just this form is an issue
Is a browser extension:

Steps to reproduce the problem:

open this file using pdf js, It shows the content when highlighted but doesn't render

What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

PDF.js version: 1.5.188

That version is no longer supported, since it's *over six years old; please find the latest releases at https://mozilla.github.io/pdf.js/getting_started/#download

Note latest version is giving problems with rendering every other file, this version perfectly fits our use case, just this form is an issue

Sorry, but such a statement unfortunately isn't actionable without any details. (And using software that's many years out of date is never a good idea, since you're missing out on lots of improvements.)

@Snuffleupagus Is there a way i can make my pdfs static using latest version? I dont want users to be able to edit the pdf in viewer itself

Given the lack of details, it's somewhat difficult to tell exactly what you want to do; hence the following is general advise:

https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/src/display/api.js#L1399 and https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/src/display/api.js#L1151-L1162
https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/web/base_viewer.js#L241 and https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/web/base_viewer.js#L118-L122
https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/web/app_options.js#L71-L75

So assuming that you're using the default viewer, simply setting the annotationMode option to 1 might do what you want.
Finally, please see http://mozilla.github.io/pdf.js/getting_started/#introduction (emphasis mine):

The viewer is built on the display layer and is the UI for PDF viewer in Firefox and the other browser extensions within the project. It can be a good starting point for building your own viewer. However, we do ask if you plan to embed the viewer in your own site, that it not just be an unmodified version. Please re-skin it or build upon it.

* PDF.js version: 1.5.188
  Note latest version is giving problems with rendering every other file, this version perfectly fits our use case, just this form is an issue

It'd be a very good idea to file some bugs about the problem you've with "other file".

I ran and built from source with few changes from previous comment
I changed this to AnnotationMode.DISABLE

https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/src/display/api.js#L1399

Set annotation value to 1

https://github.com/mozilla/pdf.js/blob/5e7eab4dd8724e8287ab24ad372f187c3c3bc725/web/app_options.js#L71-L75

I was able to get the annotation-tx*.pdf files to be non-editable. But while using the generic build in my application pdf does not load and is stuck with the default pdf compressed.tracemonkey-pldi-09.pdf

Also, is there a way to disable the blue background for the editable fields?


Indicating public preview for batch policy assignment related cmdlets

Docs Build status updates of commit 19e1533:
:clock10: Full build: the average full build time is 12 min(s) 28 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 19e1533:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md
:x:Error

Details

teams/teams-ps/teams/Get-CsUserPolicyAssignment.md
:x:Error

Details

teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md
:x:Error

Details

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md

[Error]

Unable to load file 'teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md' via processor 'AzureCliDocumentProcessor': Failed to parse this MAML markdown file due to :2:(0) '> [!NOTE]
> This cmdlet is currently in public pr...'
 Expect Heading, please use PlatyPS to do content validation

teams/teams-ps/teams/Get-CsUserPolicyAssignment.md

[Error]

Unable to load file 'teams-ps/teams/Get-CsUserPolicyAssignment.md' via processor 'AzureCliDocumentProcessor': Failed to parse this MAML markdown file due to :2:(0) '> [!NOTE]
> This cmdlet is currently in public pr...'
 Expect Heading, please use PlatyPS to do content validation

teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md

[Error]

Unable to load file 'teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md' via processor 'AzureCliDocumentProcessor': Failed to parse this MAML markdown file due to :2:(0) '> [!NOTE]
> This cmdlet is currently in public pr...'
 Expect Heading, please use PlatyPS to do content validation

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

Docs Build status updates of commit 252752b:
:clock10: Full build: the average full build time is 12 min(s) 28 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 252752b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md
:x:Error

Details

teams/teams-ps/teams/Get-CsUserPolicyAssignment.md
:x:Error

Details

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md

[Error]

Unable to load file 'teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md' via processor 'AzureCliDocumentProcessor': Failed to parse this MAML markdown file due to :2:(0) '> [!NOTE]
> This cmdlet is currently in public pr...'
 Expect Heading, please use PlatyPS to do content validation

teams/teams-ps/teams/Get-CsUserPolicyAssignment.md

[Error]

Unable to load file 'teams-ps/teams/Get-CsUserPolicyAssignment.md' via processor 'AzureCliDocumentProcessor': Failed to parse this MAML markdown file due to :2:(0) '> [!NOTE]
> This cmdlet is currently in public pr...'
 Expect Heading, please use PlatyPS to do content validation

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

Docs Build status updates of commit b3a752b:
:clock10: Full build: the average full build time is 12 min(s) 28 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b3a752b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsBatchPolicyAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/Get-CsUserPolicyAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsBatchPolicyAssignmentOperation.md
:white_check_mark:Succeeded
View (teams-ps)

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