Notification Manager (Qt-independent)

Description
Here is rough sketch of what I've been imagining for our notification model.  (see also discussion at #794, #1511 and #2167)
The basic idea is that we have a NotificationManager singleton.  On creation, the notification manager overrides sys.excepthook and warnings.showwarning with its own receive_error and receive_warning methods.  When it receives an error/warning/info message, it creates a Notification instance (which is a subclass of events.Event), adds that instance to NotificationManager.record (this provides the persistence layer) and emits a notification_ready event.  Any front end (such as a QApplication, IPython, etc) can connect itself to that event, and show a message (so the presentation of the notification is decoupled from the collection and emission of them).  For Qt, I have deleted the _qt/exceptions.py file (and our previous sys.excepthook override there), and just added this line when we create the QApp:
notification_manager.notification_ready.connect(NapariNotification.show_notification)

Here's an example of showing an error (with traceback), showing a warning, and accessing the full log of notifications (note, in this movie, I made the add points button raise an exception, and the add shapes button creates a warning):
https://user-images.githubusercontent.com/1609449/105860810-fb071300-5fbb-11eb-9d0d-78872212638d.mov
styles and naming and all that stuff can obviously change.  curious to get thoughts on the general pattern. @sofroniewn, @jni, @Carreau

Thanks for starting this, I am happy to take over if you have other area that you have stronger thoughts about.
I'm not a huge fan of singletons; if ever we want to not have this be a singleton anymore it's hard to disentangle as now every creator of notification Manager need to update their code;
I would much prefer passing the single instance of notification manger around to plugins/ where necessary.
I'm happy to have guardrails to ensure only one instance exists, but IMHO creating a second one should fail and not return the singleton.
It might be also easier to test in isolation; We've been beaten by this in IPython where we assume config ans shell  is a singleton, but some people have embeded IPython in Django or other they start from within IPython and can't have different config. That would also alleviate us from changing the except hook at creation time, which means imports would have side effect; and may conflicts with things like IPython, or trio that also install their own.

Thanks for starting this, I am happy to take over if you have other area that you have stronger thoughts about.
I'm not a huge fan of singletons; if ever we want to not have this be a singleton anymore it's hard to disentangle as now every creator of notification Manager need to update their code;
I would much prefer passing the single instance of notification manger around to plugins/ where necessary.
I'm happy to have guardrails to ensure only one instance exists, but IMHO creating a second one should fail and not return the singleton.
It might be also easier to test in isolation; We've been beaten by this in IPython where we assume config ans shell  is a singleton, but some people have embeded IPython in Django or other they start from within IPython and can't have different config. That would also alleviate us from changing the except hook at creation time, which means imports would have side effect; and may conflicts with things like IPython, or trio that also install their own.

For example, with current install of excepthook at creation time you can loose startup tracebacks like import error.
Like I think the except hook should be installed only once napari gui is running,

For example, with current install of excepthook at creation time you can loose startup tracebacks like import error.
Like I think the except hook should be installed only once napari gui is running,

sure, sounds good.  Feel free to run with it.

sure, sounds good.  Feel free to run with it.

@Carreau, I wanted to elaborate on my answer about where best to start the notification manager.  I said that currently we override sys.excepthook in _qt/qt_event_loop.py which is true ... but note that we will likely be moving away from the gui_qt context manager pattern soon.
So, backing up a couple steps, most people will probably "enter" into napari by instantiating a napari.Viewer; and, if we aren't running headless, the QtApp will then be created when Viewer.__init__ creates a Window()... which will then call get_app() in the Window.__init__, (which creates the app).  So if we were looking for a good place to create the notifications manager in a qt independent way... I guess it would be in the Viewer.__init__?

@Carreau, I wanted to elaborate on my answer about where best to start the notification manager.  I said that currently we override sys.excepthook in _qt/qt_event_loop.py which is true ... but note that we will likely be moving away from the gui_qt context manager pattern soon.
So, backing up a couple steps, most people will probably "enter" into napari by instantiating a napari.Viewer; and, if we aren't running headless, the QtApp will then be created when Viewer.__init__ creates a Window()... which will then call get_app() in the Window.__init__, (which creates the app).  So if we were looking for a good place to create the notifications manager in a qt independent way... I guess it would be in the Viewer.__init__?

superseded by #2205


fixed exporting issues

Sorry for making this so late, was busy. This fixes the issue in #6.

No problem at all, I'm busy too. Thanks for the help on this.


Fixes #2780 - NTR- subpleural fibroblast

Fixes #2780 Added a new term from Lung Atlas Jamboree

#gogoeditdiff

Not all subpleural fibroblasts are in direct contact with the visceral pleura. I recommend adding a new Uberon term 'subpleural parenchyma' that is 'adjacent to' some 'visceral pleura'. Discussed in a call: since this term is quite urgent, it can be added without EA and it will be added once the Uberon term is created and imported.


Nightly releases shouldn't be out of date with stable

Right now the nightly auto-update channel can't be used because the nightly is out of date. Right now, including auto-update, 3 of the features/fixes in the changelog were merged after the last nightly release, and this this could be a weekly problem where nightly users are a day out of step with (newly released) stable ones, depending on when stuff is merged.
I propose that either a new nightly be released when a stable is, separate from the normal daily schedule, or a more recent stable be considered "nightly" for auto-update purposes

Yeah, ideally a weekly release should be just an upgraded nightly. The problem is that (due to vscode marketplace not supporting channels and proposed features for published extensions) the relases for nighlies and stable differ, so we can't just do an upgrade.
Doing the reverse, and publishing nightly when we publish stable should in theory work, but it practice it will run afoul of our versioning scheme (we use date as a version). We probably need to look into using build counter as a version...

Just making nightlies to be published the same (hour:minute) or at least close to weekly release time will alleviate the problem by shortening the gap.
The workaround of publishing the weekly release as nightly will break our 25 hours heuristics :sweat_smile:
Anyway, I believe that the perfect solution is artifacts promotion. Maybe we should not build the weekly release from the fresh master but instead copy the current nightly (though this is not how it is done in real life ;0)?

We've switch from hacky date based versions to build number based versions, so now we can build nightlies faster than once per day.

I think this can be closed with #3875?


New custom field not accessible

Please avoid duplicates

[X] I checked all open bugs and none of them matched my problem.

Reproducible test case
No response
Please select the environment(s) that are relevant to your bug report

[ ] Browsers
[X] Node
[ ] Deno

Versions
NodeJs: v18.18.2
github-project: 5.4.0
What happened?
I have a weird issue: Some of the newly created custom fields cannot be found. I created different fields with different types but nothing works. Interestingly old custom fields that I created a while back work fine.
const options = {
  owner: "xxx",
  number: 2,
  token: "xxx",
  fields: {
    priority: "Priority",
    milestone: "Milestone",
    Estimate: { name: "Estimate", optional: true },
    lastUpdate: { name: "Last Update", optional: true },
  },
};
const project = new GitHubProject(options);
const data = await project.items.list();
console.log(data[0]);

results in getting the right object, but the Estimate custom field is missing.
Running this:
const data = await octokit.graphql(`
query {
  node(id: "PVT_kwDOAYW1RM4AAzYZ") {
    ... on ProjectV2 {
      items(first: 20) {
        nodes {
          id
          fieldValues(first: 20) {
            nodes {
              ... on ProjectV2ItemFieldNumberValue {
                field {
                  ... on ProjectV2Field {
                    name
                  }
                }
                number
                id
                updatedAt
                creator {
                  url
                }
              }
            }
          }
        }
      }
    }
  }
}
`);

console.log(data.node.items.nodes[0].fieldValues.nodes);

results in
[
  {},
  {},
  {},
  {},
  {},
  {},
  {},
  {},
  {
    field: { name: 'Estimate' },
    number: 15,
    id: 'PVTFNV_lQDOAYW1RM4AAzYczgJ_92DOB0nF8A',
    updatedAt: '2023-11-05T00:20:25Z',
    creator: { url: 'https://github.com/bobinrinder' }
  },
  {}
]

So looks like the name is set correctly. Any ideas? 🧐
Would you be interested in contributing a fix?

[x] yes

Hmm not out of hand, I'd have to investigate myself. I have not seen this happening before


[Feature] add OnPress props

Please add OnPress on whole Toast to run an action without button 🙏🏻

This is not something Sonner for web supports, so this won't get a high priority.
I encourage you to contribute with a PR.

I don't have permission to push

You have to fork the repo and make a PR from yours.


Make compilers more robust

Some refactoring, but most significantly, I've added a test to make it harder to add calls to yield to the ERB without them being supported in the other languages and fixed some bugs around that.

Looks good apart from https://travis-ci.org/alphagov/govuk_template/builds/62537279 failures.

I think there's one more thing to solve - checking that the PlayProcessor top_of_page key is (vaguely) correct - I think the best way is to test that every other key appears at least once in it.

@bradleywright I think this is now good to merge.

Code looks good - as discussed IRL it'd be nice to give the compiled templates a once over vs master to see if they differ much (mostly for Scala).

Checked the diff for the Scala/Play template when built on master versus on this branch and it looks valid in my Scala syntax highlighter.


Compile questions

Regarding the controller firmware, we encountered a problem when compiling "project_config.c"  mentioning the macro defenition #ifdef REV1 has to be defined but couldn't seen from any of the files. According to the REV number on the PCB board is 3 rather than 1. Is this a versioning problem or can anyone help? Thanks. The files are downloaded offline directly from the repository. Thanks.

This is a structure we used to allow for changes in pinouts or connected components as a PCB is revised, but it isn't really necessary for this project, so it didn't get updated with different rev numbers.
You can just add the following:
-DREV1 in the compiler flags for your project.
-You must be using a different build environment since the .ebp project file does have a -DREV1 compiler flag in it.


Fix crash on systems with pointer authentication.

hashStringForType() needed updating to deal with ExistentialType.
rdar://87717024

@swift-ci Please smoke test

@swift-ci Please smoke test


configure network environment falken service

Hi,
I would like to configure Falken Service on an independent server with it own ip instead of localhost. Do I just change the IP address in the service json file only? how bout the environment key in the json that currently only show "local" is there any other value that i can use?. tried looking into the generate sdk config file, but there is only local config (_LOCAL_CONNECTION_CONFIG)

I believe for the SDK side the json should be sufficient. Since doing our open source migration, we haven't tested running the service non-locally, so we'll see.
For launching the service, make sure to update the launcher -- probably obvious, but making sure that's what you mean.

I believe for the SDK side the json should be sufficient. Since doing our open source migration, we haven't tested running the service non-locally, so we'll see.
For launching the service, make sure to update the launcher -- probably obvious, but making sure that's what you mean.

awesome, so that's where the port was defined, thank you.


Unknown Windows/connect-mongo bug

When running the gulp command, the browser launches and I get an error:

500 Error: Error getting collection: sessions
at \freecodecamp\node_modules\connect-mongo\lib\connect-mongo.js:160:19

Refreshing "fixes" the problem. If gulp auto reloads the project it's also fine. If I rerun the "gulp" command the error happens again.
What it looks like is happening is the browser is being launched before the following is actually ready:
app.use(session({
    resave: true,
    saveUninitialized: true,
    secret: secrets.sessionSecret,
    store: new MongoStore({
        url: secrets.db,
        'auto_reconnect': true
    })
}));

MongoStore has a callback and If I move the following code into it, the problem is fixed:
/**
 * Start Express server.
 */
app.listen(app.get('port'), function () {
    console.log(
        'FreeCodeCamp server listening on port %d in %s mode',
        app.get('port'),
        app.get('env')
    );
});

I have updated the title to better describe the issue. We have a good assumption that the issue stems from windows systems. It might be an issue with connect-mongo and windows or windows and mongodb driver. More investigation will need to be conducted to better understand the problem.

What version of connect-mongo do you guys have?

0.7.0

npm install is giving me "0.4.2". The package.json says "^0.4.1". How did you get 0.7.0?
But that's the fix. To update to 0.7.0.

I updated. Haven't committed.


Add density profile plot

Add plot that shows mean density along r

Implemented in 79963686b7f2d974dba4ab0d1d78f66f08ae7ac0.
Though it is not density profile but rather mass profile.


Community

I'm incredibly excited to see this editor grow, do you have any thoughts about a place where people can discuss?  Maybe an IRC channel or mailing list?
I've thrown together an unofficial subreddit: https://www.reddit.com/r/xi_editor/
I also idle a bit on #xi on freenode (irc://irc.freenode.net/xi)

gitter.im?

It's an excellent question. I've thought about it a little and don't have a clear preference. I'd kinda lean toward a Discourse instance because it seems explicitly designed for this kind of thing, and the ones I know (CommonMark and the Rust ones) seem to function pretty well. Mailing lists seem pretty clunky and need care and feeding to keep them from rotting. IRC I think would not be ideal because my attention is bursty, I'd like to easily be able to catch up on activity (I know there are solutions such as logs, but I never read the #rust ones).
So, basically, suggestions welcome. What has worked well for similar needs?

Another consideration: I've got a bunch of long-form content queued up (I call it my "rope science" series) so ideally the community platform would either be a good place to host that, or I post those as static github pages and link to a conversation. IRC and IRC-like approaches don't seem like they would work well for that.

Why not create google group, it works as web forum and also as mailing list, plus I suppose google filter spam for them.

Mailman3/Hyperkitty is fine, Discourse is good, but some projects now use Github Issues as a forum ;) eg https://github.com/ipfs/faq

GitHub pages for long form (and could potentially serve as a web page one day) and Discourse for discussion seems like a nice combo.
IRC channels are trivial to spin up so I think they're usually worth it for technical subjects, I'm sure we've got more than a handful of Freenode idlers here.

I've created an unofficial subreddit at https://www.reddit.com/r/xi_editor/ (/r/xi was too short unfortunately.)

I would also be interested in an IRC channel for Xi Editor - it'd be a good place for technical and support discussions.
@beefsack, is the IRC channel still active? I just popped in, and couldn't see anyone there, but it looks like the channel is registered though. Thanks.

@shymega I idled in there for a while but I'm not always on IRC.  Was thinking about chucking a bot in there so it wasn't empty but haven't gotten around to anything yet.

The advantage of Gitter is the asynchrony (without the complexities of setting up bouncers). A bunch of Rust projects use it too - Diesel, Gfx, Gluon...

Hello,
Michael Alexander<EMAIL_ADDRESS>writes:

@shymega I idled in there for a while but I'm not always on IRC.  Was
thinking about chucking a bot in there so it wasn't empty but haven't
gotten around to anything yet.

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/google/xi-editor/issues/35#issuecomment-238112451

Yeah, you came in for a while yesterday, I think - I was asleep then, so
I missed you coming in at all.
Just a suggestion, the #xi channel on FN appears to have been registered
in 2009.
Perhaps to avoid conflicts with the owner (?), we should emulate our
reddit approach and register #xi-editor instead.
This also has the added advantage of keeping a uniform identifier for
our various social outlets.
Alternatively, we could host an IRC channel on the Mozilla network
instead.
--
Best regards,
Dom Rodriguez

Hello,
Brendan Zabarauskas<EMAIL_ADDRESS>writes:

The advantage of Gitter is the asynchrony (without the complexities of
setting up bouncers). A bunch of Rust projects use it too - Diesel,
Gfx, Gluon...

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/google/xi-editor/issues/35#issuecomment-238153433

It's worth mentioning that IRC has tools such as botbot.me,
iirc.
We could also setup our own bot to log as well as other channel
utilities.
Bouncers aren't always necessary for the logging aspect.
--
Best regards,
Dom Rodriguez

I think we've mostly settled on irc.mozilla.org#xi for community stuff, although we may wish to revisit at some point.


Don't check for config file to list components and services

What is the purpose of this change? What does it change?

This PR excludes the commands odo catalog list components and odo catalog list services from config file check so that they can be executed from a directory that doesn't have .odo/config.yaml file.
Was the change discussed in an issue?
fixes #1599

How to test changes?

Build the binary, login to the OpenShift cluster, and execute aforementioned commands from a directory that doesn't have .odo/config.yaml file.

/retest
+ make configure-installer-tests-cluster
make[1]: Entering directory `/go/src/github.com/openshift/odo'
. ./scripts/configure-installer-tests-cluster.sh
Adding password for user developer
Adding password for user odonoprojectattemptscreate
Adding password for user odosingleprojectattemptscreate
Adding password for user odologinnoproject
Adding password for user odologinsingleproject1
imagestream.image.openshift.io/wildfly created
secret/htpasswd-secret created
Warning: oc apply should be used on resource created by either oc create --save-config or oc apply
oauth.config.openshift.io/cluster configured
error: You must be logged in to the server (Unauthorized)
Client Version: version.Info{Major:"4", Minor:"0+", GitVersion:"v4.0.0-alpha.0+b93a8e6-2141-dirty", GitCommit:"b93a8e6", GitTreeState:"", BuildDate:"2019-04-23T21:16:33Z", GoVersion:"", Compiler:"", Platform:""}
error: You must be logged in to the server (the server has asked for the client to provide credentials)
make[1]: *** [configure-installer-tests-cluster] Error 1
make[1]: Leaving directory `/go/src/github.com/openshift/odo'
make: *** [openshiftci-presubmit-e2e] Error 2
2019/05/10 08:51:29 Container test in pod e2e-core failed, exit code 2, reason Error
2019/05/10 08:56:28 Copied 41.78Mi of artifacts from e2e-core to /logs/artifacts/e2e-core
2019/05/10 08:56:32 Ran for 39m27s
error: could not run steps: step e2e-core failed: template pod "e2e-core" failed: the pod ci-op-wd8j5jjn/e2e-core failed after 36m25s (failed containers: test): ContainerFailed one or more containers exited

Container test exited with code 2, reason Error
---
clusterversion.config.openshift.io/version condition met
./scripts/openshiftci-presubmit-e2e.sh
+ export CI=openshift
+ CI=openshift
+ export TIMEOUT=30m
+ TIMEOUT=30m
+ make configure-installer-tests-cluster
make[1]: Entering directory `/go/src/github.com/openshift/odo'
. ./scripts/configure-installer-tests-cluster.sh
Adding password for user developer
Adding password for user odonoprojectattemptscreate
Adding password for user odosingleprojectattemptscreate
Adding password for user odologinnoproject
Adding password for user odologinsingleproject1
imagestream.image.openshift.io/wildfly created
secret/htpasswd-secret created
Warning: oc apply should be used on resource created by either oc create --save-config or oc apply
oauth.config.openshift.io/cluster configured
error: You must be logged in to the server (Unauthorized)
Client Version: version.Info{Major:"4", Minor:"0+", GitVersion:"v4.0.0-alpha.0+b93a8e6-2141-dirty", GitCommit:"b93a8e6", GitTreeState:"", BuildDate:"2019-04-23T21:16:33Z", GoVersion:"", Compiler:"", Platform:""}
error: You must be logged in to the server (the server has asked for the client to provide credentials)
make[1]: *** [configure-installer-tests-cluster] Error 1
make[1]: Leaving directory `/go/src/github.com/openshift/odo'
make: *** [openshiftci-presubmit-e2e] Error 2

I dont think this error is related to the current PR
Running odo with args: [component create nodejs --project sykpbhqytx ixmrli --ref master --git https://github.com/openshift/nodejs-ex]
[odo]  •  Checking component  ...
[odo]  ✓  Checking component
[odo]  •  Checking component version  ...
[odo]  ✓  Checking component version
[odo] Please use `odo push` command to create the component with source deployed
Running odo with args: [push]
[odo]  ✓  Creating project sykpbhqytx
[odo]  ✗  Failed creating project sykpbhqytx
[odo]  ✗  project.project.openshift.io "sykpbhqytx" already exists

creating a component without an application should create one [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:37

still just wanna document it

------------------------------
odoCmpSubE2e odo component creation without application
  creating a component without an application should create one
  /go/src/github.com/openshift/odo/tests/integration/component.go:37
Creating a new project: sykpbhqytx
Running odo with args: [project create sykpbhqytx -w]
[odo]  •  Waiting for project to come up  ...
[odo]  ✓  Waiting for project to come up
[odo]  ✓  Project 'sykpbhqytx' is ready for use
[odo]  ✓  New project created and now using project : sykpbhqytx
Running odo with args: [component create nodejs --project sykpbhqytx ixmrli --ref master --git https://github.com/openshift/nodejs-ex]
[odo]  •  Checking component  ...
[odo]  ✓  Checking component
[odo]  •  Checking component version  ...
[odo]  ✓  Checking component version
[odo] Please use `odo push` command to create the component with source deployed
Running odo with args: [push]
[odo]  ✓  Creating project sykpbhqytx
[odo]  ✗  Failed creating project sykpbhqytx
[odo]  ✗  project.project.openshift.io "sykpbhqytx" already exists
Deleting project: sykpbhqytx
Running odo with args: [project delete sykpbhqytx -f]
[odo]  •  Deleting project sykpbhqytx  ...
[odo]  ✓  Deleting project sykpbhqytx
[odo] Deleted project : sykpbhqytx

• Failure [7.751 seconds]
odoCmpSubE2e
/go/src/github.com/openshift/odo/tests/integration/cmp_sub_test.go:13
  odo component creation without application
  /go/src/github.com/openshift/odo/tests/integration/component.go:29
    creating a component without an application should create one [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:37

    No future change is possible.  Bailing out early after 0.245s.
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

    /go/src/github.com/openshift/odo/tests/helper/helper_run.go:29

/test e2e-core

Deleting project: hxdssfrihf
Running odo with args: [project delete hxdssfrihf -f]
[odo]  ✗  The project hxdssfrihf does not exist. Please check the list of projects using `odo project list`
Setting current dir to: /go/src/github.com/openshift/odo/tests/integration

• Failure [1.320 seconds]
odo generic
/go/src/github.com/openshift/odo/tests/integration/generic_test.go:16
  project deletion
  /go/src/github.com/openshift/odo/tests/integration/generic_test.go:158
    be able to delete two project one after the other [It]
    /go/src/github.com/openshift/odo/tests/integration/generic_test.go:171

this seems doesn't look like flake to me anymore

/retest

Deleting project: hxdssfrihf
Running odo with args: [project delete hxdssfrihf -f]
[odo]  ✗  The project hxdssfrihf does not exist. Please check the list of projects using `odo project list`
Setting current dir to: /go/src/github.com/openshift/odo/tests/integration

�[91m�[1m• Failure [1.320 seconds]�[0m
odo generic
�[90m/go/src/github.com/openshift/odo/tests/integration/generic_test.go:16�[0m
  project deletion
  �[90m/go/src/github.com/openshift/odo/tests/integration/generic_test.go:158�[0m
    �[91m�[1mbe able to delete two project one after the other [It]�[0m
    �[90m/go/src/github.com/openshift/odo/tests/integration/generic_test.go:171�[0m

this seems doesn't look like flake to me anymore

@girishramnani This is not a first failure.
The first test that failed is
odo generic project deletion
  be able to delete two project one after the other
  /go/src/github.com/openshift/odo/tests/integration/generic_test.go:171
Created dir: /tmp/348256326
Current working dir: /go/src/github.com/openshift/odo/tests/integration
Setting current dir to: /tmp/348256326
Creating a new project: dpvhbbqzbb
Running odo with args: [project create dpvhbbqzbb -w]
[odo]  •  Waiting for project to come up  ...
[odo]  ✓  Waiting for project to come up
[odo]  ✓  Project 'dpvhbbqzbb' is ready for use
[odo]  ✓  New project created and now using project : dpvhbbqzbb
Creating a new project: hxdssfrihf
Running odo with args: [project create hxdssfrihf -w]
[odo]  •  Waiting for project to come up  ...
[odo]  ✓  Waiting for project to come up
[odo]  ✓  Project 'hxdssfrihf' is ready for use
[odo]  ✓  New project created and now using project : hxdssfrihf
Deleting project: hxdssfrihf
Running odo with args: [project delete hxdssfrihf -f]
[odo]  ✗  The project hxdssfrihf does not exist. Please check the list of projects using `odo project list`
Setting current dir to: /go/src/github.com/openshift/odo/tests/integration

• Failure [1.320 seconds]
odo generic
/go/src/github.com/openshift/odo/tests/integration/generic_test.go:16
  project deletion
  /go/src/github.com/openshift/odo/tests/integration/generic_test.go:158
    be able to delete two project one after the other [It]
    /go/src/github.com/openshift/odo/tests/integration/generic_test.go:171

    No future change is possible.  Bailing out early after 0.214s.
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

    /go/src/github.com/openshift/odo/tests/helper/helper_run.go:29

This is something that was added in your PR https://github.com/openshift/odo/pull/1710
It looks like something is not right there.

/lgtm


question

hello. i have vpn app for my client. and wanna block torrent traffic and sites.
could you explain what exactly do this script ?

This script blocks torrent clients that only download and do not seeding, not for VPN blocking


llama-cpp: fix cuda support

Description of changes
this fixes cuda support.
an attempt at addressing https://github.com/NixOS/nixpkgs/issues/272569
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@SomeoneSerge thank you for the detailed feedback, I think I integrated everything you pointed out.
let me know if anything else!

Result of nixpkgs-review pr 277709 run on x86_64-linux 1

I've switched a system with cudaSupport to this PR and tested ollama works

@SomeoneSerge gave it another round of changes. Let me know.

if all the settings are exclusive, one solution could be to replace the booleans with a string target  and check the string with   checkListOfEnum "GPU target" [ "cuda" "rocm "openblas" ] ;

if all the settings are exclusive, one solution could be to replace the booleans with a string target and check the string with   checkListOfEnum "GPU target" [ "cuda" "rocm "openblas" ] ;

I'm not sure what exactly is the situation upstream wrt the interaction of these options, so in a way the bool flags might be justified. They let the end-user try the cursed things out, and we do communicate the supported variants using broken. Otherwise, I like the suggestion

Result of nixpkgs-review pr 277709 run on x86_64-linux 1

I've tested ollama on a system with cudaSupport with this PR.


[MacOS] Latest v1.2.5 MacOS build is ARM-only.

Title says it all.  I can't quite tell if that's an intentional choice, but ARM-Only excludes Intel (hackintosh) users like me.
1.2.4 still works great for me.

Hi, can you specify which specific version of macOS you are using? The build should work from Mac OSX version 10.12 onwards, I use a Mac Air M1 to build the application, maybe for this reason it is built for ARM only, I will investigate it.
If possible, contact me by email<EMAIL_ADDRESS>to test the Intel version before publishing the possible fix.
Thank you.

I'm running Monterey 12.3.1
On the 1.2.5 build the .dmg is labeled "ReelSteady Joiner 1.2.5-arm64"
My mac shows the app with the crossed out icon.
Get info shows its Kind as "Application (Apple Silicon)"
And if I try to run it I just get an error:
You can't open this application "ReelSteady Joiner" because this application is not supported on this Mac.


[Bug]: llama pack StreamlitChat: RuntimeError

Bug Description
After correcting the error from ticket #656 and starting the application, an error appears after entering the first question in the chat:
RuntimeError: There is no current event loop in thread 'ScriptRunner.scriptThread'
Looking for answers, I came across this thread: llama_index issue 7244
after applying the advice from dosubot (using asyncio) the problem disappears, the chat starts to work correctly.
Version
0.9.7
Steps to Reproduce

download the llama pack StreamlitChat, run, enter the query in the chat field and run.

Relevant Logs/Tracbacks
2023-11-25 18:35:21.904 Uncaught app exception
Traceback (most recent call last):
  File "/home/piotr/ihpan/gpt-4-turbo/venv/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 534, in _run_script
    exec(code, module.__dict__)
  File "/home/piotr/ihpan/llamaindex_test/streamlit_chatbot/base.py", line 136, in <module>
    StreamlitChatPack(run_from_main=True).run()
  File "/home/piotr/ihpan/llamaindex_test/streamlit_chatbot/base.py", line 108, in run
    response = st.session_state["chat_engine"].stream_chat(selected)
  File "/home/piotr/ihpan/gpt-4-turbo/venv/lib/python3.8/site-packages/llama_index/callbacks/utils.py", line 39, in wrapper
    return func(self, *args, **kwargs)
  File "/home/piotr/ihpan/gpt-4-turbo/venv/lib/python3.8/site-packages/llama_index/chat_engine/context.py", line 201, in stream_chat
    chat_response = StreamingAgentChatResponse(
  File "<string>", line 10, in __init__
  File "/usr/lib/python3.8/asyncio/queues.py", line 35, in __init__
    self._loop = events.get_event_loop()
  File "/usr/lib/python3.8/asyncio/events.py", line 639, in get_event_loop
    raise RuntimeError('There is no current event loop in thread %r.'
RuntimeError: There is no current event loop in thread 'ScriptRunner.scriptThread'.

Hey @pjaskulski, thanks for sharing this! What version of Streamlit are you using?

Hey @pjaskulski, I am submitting a PR to fix this atm. In the meantime,  add the asyncio event loop at the top like so:
from typing import Dict, Any
import asyncio

# Create a new event loop
loop = asyncio.new_event_loop()

# Set the event loop as the current event loop
asyncio.set_event_loop(loop)

from llama_index import (
    VectorStoreIndex,
    ServiceContext,
    download_loader,
)
from llama_index.llama_pack.base import BaseLlamaPack
from llama_index.llms import OpenAI

Hey @pjaskulski, thanks for sharing this! What version of Streamlit are you using?

1.20

Hey @pjaskulski, I am submitting a PR to fix this atm. In the meantime, add the asyncio event loop at the top like so:

Thanks!

@pjaskulski, let me know if you're still seing the error.

@tonykipkemboi it's ok now, after adding asyncio it starts working properly.

Great! The PR is merged as well so this issue should be good to close.


seata在oracle批量更新采用in的方式，会报：maximum number of expressions in a list is 1000

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

Ⅰ. Issue Description
seata在oracle批量更新采用in的方式，会报：maximum number of expressions in a list is 1000
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version : 1.8.0_171
OS : centos 7.5
Others: seata 1.2

That s look like a oracle driver error.

@l81893521 这个其实是seata的bug，在jdbc上可以通过in的条件分组来突破1000的限制；
https://stackoverflow.com/questions/17842453/is-there-a-workaround-for-ora-01795-maximum-number-of-expressions-in-a-list-is
请问这个需要怎么取修改源码了？

can you submit pr resolve it?

modify UpdateExecutor#buildWhereConditionByPKs

@jsbxyyx 正在内部测试修改后的功能，测试通过后提交PR

@easonjim Welcome to contribute PR to the Seata community.

#2973


[Runtime] Add support of deepObject style in query params

Motivation
The runtime changes for:
https://github.com/apple/swift-openapi-generator/issues/259
Modifications
Added deepObject style to serializer & parser in order to support nested keys on query parameters.
Result
Support nested keys on query parameters.
Test Plan
These are just the runtime changes, tested together with generated changes.

Hello, looks like all the test cases except for the dictionary are wrong since the behavior of non-deep objects is undefined. Am I missing something?
Seems like undefined behavior from deepObjectExplode is falling back to formDataExplode, is that intentional?

@alephao yes these were called out in the review, see the code comments and expand the resolved ones (they don't seem to actually be updated in code yet).

@czechboy0 Oh, sorry, I got a bit lost in the comments and missed that one!
@kstefanou52 since this been stuck for a few weeks, I sent a PR to your fork addressing most of the requested changes (not sure if it's all there cuz I got a bit lost in the comments) https://github.com/kstefanou52/swift-openapi-runtime/pull/1
This is a summary of the changes:

fix URISerializer for deepObject and its tests (following the spec and not handling undefined behavior)
add deepObject tests to URIParser (there were no tests here)
fix URICodingRoundtrip tests (I ended up ignoring the cases for deepObject when the behavior is undefined since roundtrip doesn't make much sense to me in those cases)
remove parseBetweenCharacters function (I used parseUpToCharacterOrEnd twice instead)
add preconditionFailure to code that should not be reachable (serializeArray with deepObject)

@czechboy0 @alephao Sorry I was away from keyboard the last 2 weeks due to vacations. I have fixed the majority of the comments and I'll push it at the of the day.

Hi @kstefanou52, I'm sorry that I'm being annoying but I really want this change in the upstream and the PR seem to be stuck, I updated my PR to your fork with your new changes, it already addresses all the requested changes by @czechboy0, please have a look there or if you don't have time to keep working on this I'm happy to open another PR and I can put my focus on it and finish the work you've been doing.
Again, sorry to push, I just want this feature merged soon!

@alephao I'll push my changes until the end of day.

Hello @simonjbeaumont @czechboy0 ! I just pushed my changes. the only thing that I'm still missing are the comments you left about Test_URiParser with the square brackets. I think that the tests are correct because it tests the nested parsing. Am I missing something ? thank you so much for the guidance and sorry for the delay. cheers!

@kstefanou52 thanks for the updates! I'm going to try to explain @czechboy0's points since I do agree with the changes he has requested.
Following the matrix here, the spec doesn't define the behavior of "empty", "string" or "array" unless the document is using a spec extension.
My interpretation of it is that primitives like "foo=bar", "foo=1", should throw an error or at least be ignored and the runtime should not attempt to parse them, here is my reasoning:
Imagine the following concrete example:
I have an endpoint to update user's first and last name, I like to model my sever using the deepObject style, so the decoders on my server work on inputs like user[first_name]=string&user[last_name]. My server will not handle first_name=string&last_name=string and I specify this to the users of my api by writing on my openapi spec that the endpoint accepts only deepObject structures. So if you try to send anything other than a deepObject, my server will return an error.
Now imagine a mocked server generated by this library, if it accepts first_name=foo&last_name=bar, it is falling to correctly mock the server, since I specifically told in my openapi spec that I only accept deepObject structures. Once I finish development and plug my code to the real server, I'll have a surprise: my code doesn't work on the live server, only on the mock server, because the mock server successfully parses inputs that I specifically told I do not accept.
Now what that means in terms of code that needs to be changed here is that all the URIParser's tests should stop handling the "primitive=value" case, there should be an assertion that an empty dictionary was generated (meaning that the incorrect input was ignored) or it should assert that an error was thrown.
When looking at the empty test case of the style = simple, I'm deducing that we should do the first option: just ignore the invalid input and return an empty dictionary.
Please let me know if this makes any sense or if I'm completely wrong

@alephao if I'm not wrong @czechboy0 requested to oarse using square braces and not ignore them. But to be honest I'm not completely sure. Let's wait for his response.

Yeah @alephao is exactly right here - unsupported types of objects need to throw an error, but should not parse as if they were simple/form.

Hello @czechboy0 and @alephao, could you please take a look at Test_URICodingRoundtrip? I'm not entirely confident that all the test scenarios are correct, especially those involving a struct with a custom Codable implementation that forwards, and handling AnyOf cases. Thanks!

Thank you @alephao for reviewing it. I completely agree with your comment. However, since we are only supporting encoding dictionaries and not primitive values, I thought it would be appropriate to throw the necessary error and test this behavior. Let's wait for @czechboy0 to confirm how we should proceed.

@czechboy0, are there any further changes needed? I apologize for being a bit lost with all these conversations. Thank you!

@swift-server-bot test this please

The API breakage failure is expected:

💔 API breakage: enumelement ParameterStyle.deepObject has been added as a new enum case

It's in the SPI that only generated code uses, so it's okay to allow this "breakage" (it's not really, it was designed to be extended).

Ok soundness failed, please run this locally and check in the changes:

./scripts/run-swift-format.sh --fix

@swift-server-bot test this please

@swift-server-bot test this please

@czechboy0, I think the soundness check must be green now.

@swift-server-bot test this please


Glyphicons

The example site @ http://angular-ui.github.io/bootstrap/ is attempting to load the glyphicons from the bootstrapcdn which is not loading due to Cross-Origin Resource policy
Error Message in Chrome console
Redirect at origin 'http://netdna.bootstrapcdn.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://angular-ui.github.io' is therefore not allowed access.
Examples

Browser Infos

I have no relationship with this project, but I thought I would jump in here.  This seems like a temporary issue and likely isn't the fault of angular-ui.
@pcnate is this still occurring?  I just tried with my machine and the icons were visible.  I also verified that netdna.bootstrapcdn.com is correctly setting the Access-Control-Allow-Origin header.
This is unlikely a problem with this site.  I suspect either netdna.bootstrapcdn.com wasn't setting the Access-Control-Allow-Origin header correctly, or the beta version of Chrome you are running wasn't interpreting it correctly.  You can check for the header by looking in the network tab in developer tools, finding the line for the glyphicons, and selecting the "Header" tab. In the "Response Headers", you should see a line that says: Access-Control-Allow-Origin:*.
You may also want to try a different browser or a non-beta Chrome.

@VoltiSubito I have had this issue for quite some time. I tried in Firefox 36.0.1 and it does the same thing. Funny thing, IE 11 works. Check this out...
IE 11 request headers

IE 11 response headers

Firefox 36
http://netdna.bootstrapcdn.com/bootstrap/3.1.1/fonts/glyphicons-halflings-regular.woff

http://netdna.bootstrapcdn.com/bootstrap/3.1.1/fonts/glyphicons-halflings-regular.ttf

Chrome provides a useless output as it is being canceled due to the policy and doesn't provide the headers sent and received (grrr).

So, it would seem the proxy is dropping the Access-Control-Allow-Origin * header, but only for the ttf and woff files. It is probably misconfigured or not smart enough to cache content for cross domain access.
Unless I am missing something else.

I'm closing this as resolved, as I am not seeing this issue anymore.
This appears to have been a temporary issue with the Bootstrap CDN.


Built-in ad-block for Treccani website

We could implement an ad-block to remove ads from Treccani website and reduce the number of unnecessary web requests to third-party domains. This will result in cleaner web pages and faster load times.
This feature will be active by default, but there will be an option to turn it on/off.

Speaking of load times, we did some basic tests to figure out whether it is worth implementing this feature. The tests led to these results:

Metrics
Average value without ad-block
Average value with ad-block (%)
Difference (%)

Number of web requests
217,2
46.7 (21,50)
-170,5 (-78.5)

Data transferred (MB)
8.321
4.877 (58.61)
-3,444 (-41.39)

Completed (s)
22.946
3.93 (17.13)
-19,016 (-82.87)

DOMContentLoaded (s)
2.033
2.732 (134.38)
+0,699 (+34.38)

Load (s)
12.398
2.741 (22.11)
-9,657 (-77.89)

As we can see, DOMContentLoaded is the only parameter negatively affected by the ad-block, but time increases slightly compared to other values.


Detect Safe wallet contracts outside of connected apps

Safe contracts are detected when a user connects via a connected app in their frontend. But if she uses WalletConnect and their mobile app, no banner is displayed indicating that opting-in is necessary to receive yield.
https://www.loom.com/share/293b59d5f321478f8db5cccd5964a5d0

this feature has been migrated to new origin-defi repo where the Safe wallet is properly detected


Download a file

How can I create a link inside a route that downloads a file?
I want to do...
PDF
But the router is handling it.
In a sort of related request... it would be really great if I could add something like a data-no-router attribute to any link I'd like the router to ignore.

Use the download attribute of the links https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a?retiredLocale=it#attr-download

Thanks! For reference on anyone landing here my link looks like this now...
PDF


Is project active

Is this project still active?
I mean I was using the old one and the active development is being pushed here, but  I can not find any docs how to start to connect web with flogo
Thank you for the amazing project.
I am a golang developer and can contribute.
Please let me know how  I can contribute.
On the links provided on readme.md there are no open issues.

Found it
This tool needs proper documentation
It has a lot of potential.
Thank you.

Same here, I saw some minimal activity several months ago.

yes, the project is still active. https://github.com/project-flogo has a number of repos related to various different components.


➕ [RESOURCE] -

Idea Contribution

[X] I have read all the resource request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Where do you want to add the resource? Specify the category and section.
i want to ADD Create an NFT Gallery project using Blockchain in project section of web 3
Provide the URLs of the resources you are adding
https://youtu.be/y6JfVdcJh1k?si=Vp8KimEBzUUu4RPD
In this Projrct Build your own you will learn how to develop an NFT gallery that displays NFTs by wallet address and smart contract address.
Any alternative approaches/features
No response
Additional Context
No response
Code of Conduct

[X] I follow the CONTRIBUTING GUIDELINE of this project.

https://github.com/jfmartinz/ResourceHub/pull/1439 @jfmartinz  plz review


body.getReader() method missing (node 14.x)

There seems to be a problem using web-streams-polyfill on nodejs 14.x
I ran into the issue where, given some code like described in the documentation:
const ky = require('ky-universal');

(async () => {
	const {body} = await ky('https://httpbin.org/bytes/16');
	const {value} = await body.getReader().read();
	const result = new TextDecoder('utf-8').decode(value);

	// …
})();

I would get a runtime error:
TypeError: _a.getReader is not a function

at the 'body.getReader() call.
I read the docs to install web-streams-polyfill which I did (3.0.0) but still get the error.
I took stepped through the ky-universal code and see
//index.js
if (!global.ReadableStream) {
	try {
		global.ReadableStream = require('web-streams-polyfill/ponyfill/es2018');
	} catch (_) {}
}

This seems to be a problem because the require('web-streams-polyfill/ponyfill/es2018') returns an object, so the following fails:
//ky/umd.js
const supportsStreams = typeof globals.ReadableStream === 'function';

so....   clever me, I thought I would pre-shim the globals.ReadableStream to hot-patch the problem by adding this to my app code:
if ( !global.ReadableStream ) {
  global.ReadableStream = require( 'web-streams-polyfill/ponyfill/es2018' ).ReadableStream
}

but still, the body.getReader() function doesn't exist.  Unfortunately the ky code is too fancy for me to follow, so here I am, filing this issue!
fyi, I also tried<EMAIL_ADDRESS>but same error.

Indeed, I am able to reproduce this. Smells like a problem with node-fetch to me. For some reason, body ends up being a Node PassThrough stream, instead of a web compliant stream, even when web streams have been polyfilled.

Well if you read node-fetch's Known differences from client documentation it is clearly specified there that they expose Node's Readable stream and not WHATWG's stream, so I don't think this is node-fetch problem but ky-universal...

It doesn't really make sense for Ky to handle any other stream implementation besides web streams. But I'll agree with you in the sense that it's our fault for assuming that node-fetch would comply, or at least try to comply, with the specification. We're clearly going to have to switch to a better polyfill that properly implements the spec. See: https://github.com/sindresorhus/ky-universal/issues/34

This package is no longer needed if you target Node.js 18 or later: https://github.com/sindresorhus/ky/releases/tag/v1.0.0


The mouse is not aligned correctly

The mouse does not align correctly in pixel-streaming, which makes some operations, such as moving the axis of rotation difficult. Is there any way to align it correctly?
It's true in the middle, it's cheaper as you go around.

Any help would be greatly appreciated.

If I set the resolution of the Unreal pixel streaming to the same as the browser resolution, I can get the correct result, what else can I do?  Especially zoom in on the browser

@AAaronMack
Try to update pixel streaming module.
yarn add<EMAIL_ADDRESS>
Make changes from the documentation

I set connectOnStart: true and the pixel streaming disappears, I am using React v17.0.2

@aaronmack 2.3.9 =)

Still doesn't seem to work correctly and gets some errors.

@aaronmack
Please provide a link to your repo =)

https://github.com/WinsingAaron/my-app    I didn't succeed in this simple project

https://github.com/WinsingAaron/my-app I didn't succeed in this simple project

Where src/Player.js is pixel Streaming

@aaronmack
yarn add<EMAIL_ADDRESS>refPixelStreaming.current.connector.initConnection()

If I set connectOnStart: true, I  will get some same errors as before. If I set connectOnStart: false, and make a button to call refPixelStreaming.current.connector.initConnection() when clicked. I can get the pictures from Pixel Streaming, But the mouse seems even more incorrect.

@aaronmack
Looks like you haven't updated the version to 2.4.1
Mouse positioning should work. At startup, we send console commands to Unreal Engine:
client.emitConsole(`PixelStreaming.Capturer.UseBackBufferSize 0`)
client.emitConsole(`PixelStreaming.Capturer.CaptureSize ${width}x${height}`)
client.emitConsole(`r.SetRes ${width}x${height}f`)

I updated it to 2.4.3. and using the emitConsole method, and got some errors.

import React, {useEffect} from "react";

// libs
import PixelStreaming, { usePS, DebugData } from 'pixel-streaming'

export default function Player(props) {
    const refPixelStreaming = React.useRef(null);
    const PS = usePS();

    const handleConnection = () => {
        refPixelStreaming.current.connector.initConnection()
    }

    useEffect(() => {
        window.addEventListener('resize', handleResize);
    }, []);

    const handleResize = () => {
        console.log('resized to ', window.innerWidth, 'x', window.innerHeight)

        const width = window.innerWidth
        const height = window.innerHeight

        //const emitConsole = refPixelStreaming.current.cls.client.emitConsole
        const emitConsole = PS.cls.client.emitConsole

        emitConsole(`PixelStreaming.Capturer.UseBackBufferSize 0`)
        emitConsole(`PixelStreaming.Capturer.CaptureSize ${width}x${height}`)
        emitConsole(`r.SetRes ${width}x${height}f`)
    }

    return (

            <button onClick={handleConnection}>Connect</button>
            <PixelStreaming
                ref={refPixelStreaming}
                onLoad={(payload) => {
                    // console.warn('loaded', payload);
                }}
                onConnect={() => {
                    // console.warn('connected');
                }}
                onRestart={() => {
                    // console.warn('onRestart');
                }}
                onError={(payload) => {
                    // console.error('error', payload);
                }}
                onClose={(payload) => {
                    // console.error('closed', payload);
                }}
                onProgress={(payload) => {
                    // console.warn('progress', payload);
                }}
                settings={{
                    volume: 1,
                    quality: 1,
                    connectOnStart: false,

                    host: 'http://<IP_ADDRESS>',
                    port: 80,

                    pixelStreaming: {
                        warnTimeout: 120,
                        closeTimeout: 10,
                        lockMouse: false,
                        fakeMouseWithTouches: false,
                    }
                }}
                metaSettings={{
                    isDev: true,
                    showDevTools: true,
                    notifyCommands: true,
                    notifyCallbacks: true,
                }}
            >
                {(payload) =>
{props.children}
}
            </PixelStreaming>

    );
}

I used both methods refPixelStreaming and PS, but I seem to get the same error.
https://github.com/WinsingAaron/my-app    I updated this repository.

@aaronmack
v2.4.4
Try player.cls.setConnection({ host, port })
=)

Like this?

But it still seems to be the wrong result.

@aaronmack I need time for investigation.

Be deeply grateful.

@aaronmack
I tried implement this methods in your repo and that works!
pixel-streaming 2.4.5
const handleConnection = () => {
        refPixelStreaming.current.cls.initConnection({
            host: 'http://<IP_ADDRESS>',
            port: 80,
        })
    }

It is ok to add -ResX and -ResY parameters that is consistent with the browser resolution when starting Unreal, like this.

e.g. -ResX=601 -ResY=496
but when the browser size changes, The position deviation of the mouse is very serious.
    const handleResize = () => {
        console.log('resized to ', window.innerWidth, 'x', window.innerHeight)

        const width = window.innerWidth
        const height = window.innerHeight

        //const emitConsole = refPixelStreaming.current.cls.client.emitConsole
        const emitConsole = PS.cls.client.emitConsole

        emitConsole(`PixelStreaming.Capturer.UseBackBufferSize 0`)
        emitConsole(`PixelStreaming.Capturer.CaptureSize ${width}x${height}`)
        emitConsole(`r.SetRes ${width}x${height}f`)
    }

and I tried handleResize, but got an error, it doesn't seem to work properly.
I tried one solution, which was to get the browser resolution each time and then start Unreal as a parameter, but required the user not to enlarge or decrease the size of the browser.
But they may change the size without knowing it.

@aaronmack works?

@aaronmack
try const emitConsole = (payload) => refPixelStreaming.current.cls.client.emitConsole(payload)


Upload Annotation Data

Hello @nmanovic .
I have an existing postgres db that maintains annotation data of all images. I wish to upload this data dynamically to 'upload annotation'. Where can i find the source code that parses the json/xml and uploads it to the cvat_ui.
Regards
Clyde

Hi @clydebailey ,
https://github.com/opencv/cvat/tree/develop/cvat/apps/annotation
Look at TFRecord/COCO/CVAT/... annotation formats. You can upload any file and parse it.
Please ask questions on our gitter channel next time. I will close the issue.

Hello @nmanovic
Thank you for the fast reply.
I am sorry if I phrased by question wrongly.
Suppose I have a coco.json file residing in my pc and I want to upload it to the cvat job without the need to use the "upload annotation" radio button. How can i achieve this?
I am finding it difficult to debug the source  code since it is installed with docker.
Any guidance would be appreciated.
Thanks

No worries, I figured it out. Thanks

https://github.com/opencv/cvat/tree/develop/cvat/apps/annotation

This link is dead

@burnzzz , please look here https://github.com/openvinotoolkit/cvat/tree/develop/cvat/apps/dataset_manager


Environment section no longer does environment variable expansion

We have an environment section that contains things like this:
  environment:
    - APP_PATH=$DRONE_DIR/..
    - PYTHONPATH=$APP_PATH

These variables in turn get used later in the build section. From my testing, APP_PATH (for example) is being set as a string literal ("$DRONE_DIR/..") as opposed to the corresponding path. As such, later commands that use the variable fail. Was this behaviour changed in 0.4?
Thanks!

@stevenpall these environment variables are injected at the Docker daemon level (vie -e) and therefore do not expand. If you want to expand the variables you'll need to create the environment variables as part of the build command:
build:
  commands:
    - export APP_PATH=$DRONE_DIR/..
    - export PYTHONPATH=$APP_PATH

Ah, I see. That works. Thanks!

great, I'll be sure to update the docs as well


Update models.py

added print statements

Pull Request Test Coverage Report for Build 216

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.102%

Totals

Change from base Build 205:
0.0%

Covered Lines:
194

Relevant Lines:
472

💛  - Coveralls


Error trying to upload Salmon Run jobs with new specials

Error trying to upload Salmon Run jobs with new specials
Error uploading job. (ID: Q29vcEhpc3RvcnlEZXRhaWwtdS1hNWg2ZGltYW9wcnFjaWFuZ25tbToyMDIzMTEzMFQwNjIwMjVfNDVjMGNhYTMtODVjNS00Yzg5LTlmM2EtY2QyYWUyMmY4MTcx)
Message from server:
{
"error": {
"waves": "special_uses: Special Uses is invalid. unknown special unknown"
}
}

I'll merge the PR into s3s tonight. Thanks!


[Label, Step] problem with pointing basic labels in rtl version

Hi.
There is a problem with pointing basic labels in newer versions of Semantic-UI rtl build. Semantic UI version is 2.1.8.

    نام
    <input id="id_contact_name" maxlength="100" name="contact_name" type="text">

این فیلد لازم است.

JSFiddle: https://jsfiddle.net/ty6j8ee5/

This problem also appears in "step" module:

Hi,
I rechecked this and it's caused by RTLCSS not flipping multiple transforms, a fix will be published soon.
Thanks!

Fix released, update your packages and rebuild!

Yes, it is fixed. Thanks!


bug fixes in SmartAPI spec yaml

Correct code in spec YAMLs for ubkg-api and data distillery re:

sources endpoint
sabs endpoint

This no longer appears to be an issue. It may have been that the SmartAPI had not been refreshed when I saw the errors.


AttributeCompression.js DeveloperError to Check Refactor

Replaced DeveloperError checks with Check.definedchecks for #4794 and added myself (William Ho) to CONTRIBUTORS.md

Great @WilliamKHo, thanks!


Laboratory work #1, Vyahireva Sasha - 19FPL1

Unfortunately, the deadline is not that far. Please, push changes so that we can review them.

do not forget about start.py

target score should be 10

Do not put "Review required" if you haven't corrected all the issues

correct the issue about start.py

correct the issue about start.py

correct the issue about start.py

what kind of issue?

I've written them earlier
write
assert RESULT == [expected result]
put there concordance or sorted one, whatever

Open another PR with the second lab


geos: 3.11.2 -> 3.12.1

Description of changes
Update GEOS to the latest version.
List of changes: https://github.com/libgeos/geos/releases/tag/3.12.1
This PR was successfully tested with current Shapely version (2.0.2).

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build geos python3Packages.shapely

@NixOS/geospatial , this PR I good to go. Would you please review ? Thanks.

I am running nixpkgs-review now ...

nixpkgs-review is still running ... Building tensorflow.

After many hours, nixpkgs-review crashed. I am not sure why.
From logs, I see following packages having problems with GEOS 3.12.1:

pygeos

error: builder for '/nix/store/jnkmix0v53dpyizzvbyai7vdr8xvfi5c-python3.10-pygeos-0.14.drv' failed with exit code 1;
       last 10 log lines:
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_134-geom_234] - Failed: DID NOT RAISE <class 'pygeos.GEOSException'>
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_135-geom_235] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_136-geom_236] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_137-geom_237] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_138-geom_238] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_139-geom_239] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_140-geom_240] - AssertionError: Regex pattern did not match.
       > FAILED pygeos/tests/test_set_operations.py::test_coverage_union_non_polygon_inputs[geom_141-geom_241] - AssertionError: Regex pattern did not match.

psycopg

       last 10 log lines:
       >
       > >       assert n[0] == n[1] == n[2], f"objects leaked: {n[1] - n[0]}, {n[2] - n[1]}"
       > E       AssertionError: objects leaked: -1, 1
       > E       assert 222934 == 222933
       >
       > tests/test_copy_async.py:790: AssertionError
       > =========================== short test summary info ============================
       > FAILED tests/test_copy_async.py::test_copy_from_leaks[asyncio-Format.TEXT-False] - AssertionError: objects leaked: -1, 1

kikit with shapely 1.8.4

       last 10 log lines:
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[MULTIPOINT (1 1 1, 2 2)-MULTIPOINT Z (1 1 1, 2 2 0)] - shapely.errors.WKTReadingError: Could not create geometry because of errors...
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[MULTIPOINT (1 1, 2 2 2)-MULTIPOINT Z (1 1 0, 2 2 2)] - shapely.errors.WKTReadingError: Could not create geometry because of errors...
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[LINESTRING (1 1 1, 2 2)-LINESTRING Z (1 1 1, 2 2 0)] - shapely.errors.WKTReadingError: Could not create geometry because of errors...
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[POLYGON ((0 0 0, 1 0 0, 1 1, 0 1 0, 0 0 0))-POLYGON Z ((0 0 0, 1 0 0, 1 1 0, 0 1 0, 0 0 0))] - shapely.errors.WKTReadingError: Could not create geometry
because of errors...
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[LINESTRING (1 1, 2 2 2)-LINESTRING (1 1, 2 2)] - shapely.errors.WKTReadingError: Could not create geometry because of errors...
       > FAILED tests/test_create_inconsistent_dimensionality.py::test_create_from_wkt[POLYGON ((0 0, 1 0 1, 1 1, 0 1, 0 0))-POLYGON ((0 0, 1 0, 1 1, 0 1, 0 0))] - shapely.errors.WKTReadingError: Could not create geometry because of errors.
..
       > FAILED tests/test_parallel_offset.py::OperationsTestCase::test_parallel_offset_linestring - AssertionError: <shapely.geometry.linestring.LineString object at 0x7fff729...
       > FAILED tests/test_voronoi_diagram.py::test_edges - assert False

Error in psycopg is related to flaky tests, they sometimes fail, sometimes not. Fix in progress: https://github.com/psycopg/psycopg/pull/693 & https://github.com/NixOS/nixpkgs/issues/271926

I will take a look at pygeos

Errors in pygeos are mostly related to this change in the changelog of geos:
  - CoverageUnion now requires valid inputs to produce valid outputs
    and may return invalid outputs silently when fed invalid inputs.

pygeos expects in the tests that invalid inputs result in an exception. After the change invalid outputs are given rather than an exception is raised.
But there are other errors as well:
       > FAILED pygeos/tests/test_constructive.py::test_oriented_envelope[geometry0-expected0] - assert False
       > FAILED pygeos/tests/test_constructive.py::test_oriented_envelope[geometry2-expected2] - assert False
       > FAILED pygeos/tests/test_constructive.py::test_minimum_rotated_rectangle[geometry0-expected0] - assert False
       > FAILED pygeos/tests/test_constructive.py::test_minimum_rotated_rectangle[geometry2-expected2] - assert False
       > FAILED pygeos/tests/test_io.py::test_to_wkt_multipoint_with_point_empty - AssertionError: assert 'MULTIPOINT (EMPTY, (2 3))' == 'MULTIPOINT (EMPTY, 2...

which are starting to look like ones that are not worth patching in nixpkgs. And a pull request to pygeos is not a good option as upstream has continued development in shapely and pygeos is nearing archive status.
I am wondering if this is the point at which either

pygeosis deprecated
The offending tests are just skipped with skipif and GEOS version condition

Feedback appreciated...

Result of nixpkgs-review pr 268130 run on x86_64-linux 1

11 packages marked as broken and skipped:

python310Packages.paddleocr
python310Packages.paddleocr.dist
python310Packages.unstructured-inference
python310Packages.unstructured-inference.dist
python310Packages.worldengine
python310Packages.worldengine.dist
python311Packages.worldengine
python311Packages.worldengine.dist
t-rex
worldengine-cli
worldengine-cli.dist

20 packages failed to build:

kicadAddons.kikit
kicadAddons.kikit-library
kikit
kikit.dist
python310Packages.bsuite
python310Packages.bsuite.dist
python310Packages.opensfm
python310Packages.opensfm.dist
python310Packages.plotnine
python310Packages.plotnine.dist
python310Packages.pygeos
python310Packages.pygeos.dist
python311Packages.bsuite
python311Packages.bsuite.dist
python311Packages.opensfm
python311Packages.opensfm.dist
python311Packages.plotnine
python311Packages.plotnine.dist
python311Packages.pygeos
python311Packages.pygeos.dist

216 packages built:

apacheHttpdPackages.mod_tile (apacheHttpdPackages_2_4.mod_tile)
cloudcompare
cura
easyocr (python311Packages.easyocr)
easyocr.dist (python311Packages.easyocr.dist)
entwine
gdal (python311Packages.gdal)
gdalMinimal
geos
gmt
gplates
grass
haskellPackages.hgdal
haskellPackages.hgdal.doc
haskellPackages.hgeos
haskellPackages.hgeos.data
haskellPackages.hgeos.doc
librasterlite2
librttopo
librttopo.dev
libspatialite
libspatialite.dev
mapcache
mapnik
mapproxy
mapproxy.dist
mapserver
merkaartor
moonraker
mysql-workbench
octavePackages.mapping
openorienteering-mapper
osm2pgsql
osmscout-server
paraview
pdal
perl536Packages.Tirex
perl536Packages.Tirex.devdoc
perl538Packages.Tirex
perl538Packages.Tirex.devdoc
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
pgcli (python311Packages.pgcli)
pgcli.dist (python311Packages.pgcli.dist)
postgresql12JitPackages.postgis
postgresql12JitPackages.postgis.doc
postgresql12Packages.postgis
postgresql12Packages.postgis.doc
postgresql13JitPackages.postgis
postgresql13JitPackages.postgis.doc
postgresql13Packages.postgis
postgresql13Packages.postgis.doc
postgresql14JitPackages.postgis
postgresql14JitPackages.postgis.doc
postgresql14Packages.postgis
postgresql14Packages.postgis.doc
postgresqlJitPackages.postgis (postgresql15JitPackages.postgis)
postgresqlJitPackages.postgis.doc (postgresql15JitPackages.postgis.doc)
postgresqlPackages.postgis (postgresql15Packages.postgis)
postgresqlPackages.postgis.doc (postgresql15Packages.postgis.doc)
postgresql16JitPackages.postgis
postgresql16JitPackages.postgis.doc
postgresql16Packages.postgis
postgresql16Packages.postgis.doc
python310Packages.aplpy
python310Packages.aplpy.dist
python310Packages.asf-search
python310Packages.asf-search.dist
python310Packages.basemap
python310Packages.basemap.dist
python310Packages.cartopy
python310Packages.cartopy.dist
python310Packages.cf-xarray
python310Packages.cf-xarray.dist
python310Packages.django-bootstrap4
python310Packages.django-bootstrap4.dist
python310Packages.easyocr
python310Packages.easyocr.dist
python310Packages.fiona
python310Packages.fiona.dist
python310Packages.flask-admin
python310Packages.flask-admin.dist
python310Packages.folium
python310Packages.folium.dist
python310Packages.gdal
python310Packages.geoalchemy2
python310Packages.geoalchemy2.dist
python310Packages.geopandas
python310Packages.geopandas.dist
python310Packages.glueviz
python310Packages.glueviz.dist
python310Packages.labelbox
python310Packages.labelbox.dist
python310Packages.osmnx
python310Packages.osmnx.dist
python310Packages.owslib
python310Packages.owslib.dist
python310Packages.pgcli
python310Packages.pgcli.dist
python310Packages.pgspecial
python310Packages.pgspecial.dist
python310Packages.pgvector
python310Packages.pgvector.dist
python310Packages.preprocess-cancellation
python310Packages.preprocess-cancellation.dist
python310Packages.psycopg
python310Packages.psycopg.dist
python310Packages.psycopg.doc
python310Packages.pvextractor
python310Packages.pvextractor.dist
python310Packages.pygmt
python310Packages.pygmt.dist
python310Packages.pyosmium
python310Packages.pyosmium.dist
python310Packages.pyproj
python310Packages.pyproj.dist
python310Packages.pytest-postgresql
python310Packages.pytest-postgresql.dist
python310Packages.python-mapnik
python310Packages.python-mapnik.dist
python310Packages.qcodes
python310Packages.qcodes-contrib-drivers
python310Packages.qcodes-contrib-drivers.dist
python310Packages.qcodes.dist
python310Packages.rasterio
python310Packages.rasterio.dist
python310Packages.shapely
python310Packages.shapely.dist
python310Packages.spectral-cube
python310Packages.spectral-cube.dist
python310Packages.uranium
python310Packages.wktutils
python310Packages.wktutils.dist
python310Packages.wrf-python
python310Packages.wrf-python.dist
python311Packages.aplpy
python311Packages.aplpy.dist
python311Packages.asf-search
python311Packages.asf-search.dist
python311Packages.basemap
python311Packages.basemap.dist
python311Packages.cartopy
python311Packages.cartopy.dist
python311Packages.cf-xarray
python311Packages.cf-xarray.dist
python311Packages.django-bootstrap4
python311Packages.django-bootstrap4.dist
python311Packages.fiona
python311Packages.fiona.dist
python311Packages.flask-admin
python311Packages.flask-admin.dist
python311Packages.folium
python311Packages.folium.dist
python311Packages.geoalchemy2
python311Packages.geoalchemy2.dist
python311Packages.geopandas
python311Packages.geopandas.dist
python311Packages.glueviz
python311Packages.glueviz.dist
python311Packages.labelbox
python311Packages.labelbox.dist
python311Packages.osmnx
python311Packages.osmnx.dist
python311Packages.owslib
python311Packages.owslib.dist
python311Packages.pgspecial
python311Packages.pgspecial.dist
python311Packages.pgvector
python311Packages.pgvector.dist
python311Packages.preprocess-cancellation
python311Packages.preprocess-cancellation.dist
python311Packages.psycopg
python311Packages.psycopg.dist
python311Packages.psycopg.doc
python311Packages.pvextractor
python311Packages.pvextractor.dist
python311Packages.pygmt
python311Packages.pygmt.dist
python311Packages.pyosmium
python311Packages.pyosmium.dist
python311Packages.pyproj
python311Packages.pyproj.dist
python311Packages.pytest-postgresql
python311Packages.pytest-postgresql.dist
python311Packages.python-mapnik
python311Packages.python-mapnik.dist
python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python311Packages.qcodes-contrib-drivers.dist
python311Packages.qcodes.dist
python311Packages.rasterio
python311Packages.rasterio.dist
python311Packages.shapely
python311Packages.shapely.dist
python311Packages.spectral-cube
python311Packages.spectral-cube.dist
python311Packages.uranium
python311Packages.wktutils
python311Packages.wktutils.dist
python311Packages.wrf-python
python311Packages.wrf-python.dist
pytrainer
pytrainer.dist
qgis
qgis-ltr
qmapshack
saga
spatialite_gui
spatialite_tools
sumo
tests.pkg-config.defaultPkgConfigPackages.geos
udig
valhalla
vpv

I would suggest adding a new derivation for GEOS 3.11 (much like 3.9 for other legacy uses: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/geos/3.9.nix) and shifting pygeos to use that as a dependency (and perhaps note either in top-level or the 3.11 derivation that this is being maintained solely for pygeos). That way pygeos can keep living for users who can't migrate to shapely, but we don't have to hold up the version bump for everyone else.

pygeosis deprecated
The offending tests are just skipped with skipif and GEOS version condition

Feedback appreciated...

@nialov , thank you very much for this investigation. As I said in previous comment, we can keep GEOS 3.11 for some time.

Error in psycopg is related to flaky tests, they sometimes fail, sometimes not. Fix in progress: psycopg/psycopg#693 & #271926

Great thanks for psycopg patch.

@ofborg build kikit python3Packages.pygeos

Thanks for the responses, keeping pygeos alive for now sounds good to me :+1:

psycopg fix is merged to master.

@ofborg build kikit python3Packages.pygeos

Result of nixpkgs-review pr 268130 run on x86_64-linux 1

5 packages marked as broken and skipped:

python310Packages.worldengine
python310Packages.worldengine.dist
python311Packages.worldengine
python311Packages.worldengine.dist
t-rex

8 packages failed to build:

python310Packages.plotnine
python310Packages.plotnine.dist
python311Packages.plotnine
python311Packages.plotnine.dist
python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python311Packages.qcodes-contrib-drivers.dist
python311Packages.qcodes.dist

215 packages built:

apacheHttpdPackages.mod_tile
cloudcompare
cura
easyocr (python311Packages.easyocr)
easyocr.dist (python311Packages.easyocr.dist)
entwine
gdal (python311Packages.gdal)
gdalMinimal
geos
geos311
gmt
gplates
grass
kicadAddons.kikit
kicadAddons.kikit-library
kikit
kikit.dist
librasterlite2
librttopo
librttopo.dev
libspatialite
libspatialite.dev
mapcache
mapnik
mapproxy
mapproxy.dist
mapserver
merkaartor
moonraker
mysql-workbench
octavePackages.mapping
openorienteering-mapper
osm2pgsql
osmscout-server
paraview
pdal
perl536Packages.Tirex
perl536Packages.Tirex.devdoc
perl538Packages.Tirex
perl538Packages.Tirex.devdoc
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
pgcli (python311Packages.pgcli)
pgcli.dist (python311Packages.pgcli.dist)
postgresql12JitPackages.postgis
postgresql12JitPackages.postgis.doc
postgresql12Packages.postgis
postgresql12Packages.postgis.doc
postgresql13JitPackages.postgis
postgresql13JitPackages.postgis.doc
postgresql13Packages.postgis
postgresql13Packages.postgis.doc
postgresql14JitPackages.postgis
postgresql14JitPackages.postgis.doc
postgresql14Packages.postgis
postgresql14Packages.postgis.doc
postgresqlJitPackages.postgis (postgresql15JitPackages.postgis)
postgresqlJitPackages.postgis.doc (postgresql15JitPackages.postgis.doc)
postgresql15Packages.postgis
postgresql15Packages.postgis.doc
postgresql16JitPackages.postgis
postgresql16JitPackages.postgis.doc
postgresql16Packages.postgis
postgresql16Packages.postgis.doc
python310Packages.aplpy
python310Packages.aplpy.dist
python310Packages.asf-search
python310Packages.asf-search.dist
python310Packages.basemap
python310Packages.basemap.dist
python310Packages.cartopy
python310Packages.cartopy.dist
python310Packages.cf-xarray
python310Packages.cf-xarray.dist
python310Packages.django-bootstrap4
python310Packages.django-bootstrap4.dist
python310Packages.easyocr
python310Packages.easyocr.dist
python310Packages.fiona
python310Packages.fiona.dist
python310Packages.flask-admin
python310Packages.flask-admin.dist
python310Packages.folium
python310Packages.folium.dist
python310Packages.gdal
python310Packages.geoalchemy2
python310Packages.geoalchemy2.dist
python310Packages.geopandas
python310Packages.geopandas.dist
python310Packages.glueviz
python310Packages.glueviz.dist
python310Packages.labelbox
python310Packages.labelbox.dist
python310Packages.osmnx
python310Packages.osmnx.dist
python310Packages.owslib
python310Packages.owslib.dist
python310Packages.pgcli
python310Packages.pgcli.dist
python310Packages.pgspecial
python310Packages.pgspecial.dist
python310Packages.pgvector
python310Packages.pgvector.dist
python310Packages.preprocess-cancellation
python310Packages.preprocess-cancellation.dist
python310Packages.psycopg
python310Packages.psycopg.dist
python310Packages.psycopg.doc
python310Packages.pvextractor
python310Packages.pvextractor.dist
python310Packages.pygmt
python310Packages.pygmt.dist
python310Packages.pyosmium
python310Packages.pyosmium.dist
python310Packages.pyproj
python310Packages.pyproj.dist
python310Packages.pytest-postgresql
python310Packages.pytest-postgresql.dist
python310Packages.python-mapnik
python310Packages.python-mapnik.dist
python310Packages.qcodes
python310Packages.qcodes-contrib-drivers
python310Packages.qcodes-contrib-drivers.dist
python310Packages.qcodes.dist
python310Packages.rasterio
python310Packages.rasterio.dist
python310Packages.shapely
python310Packages.shapely.dist
python310Packages.shapely18
python310Packages.shapely18.dist
python310Packages.spectral-cube
python310Packages.spectral-cube.dist
python310Packages.uranium
python310Packages.wktutils
python310Packages.wktutils.dist
python310Packages.wrf-python
python310Packages.wrf-python.dist
python311Packages.aplpy
python311Packages.aplpy.dist
python311Packages.asf-search
python311Packages.asf-search.dist
python311Packages.basemap
python311Packages.basemap.dist
python311Packages.cartopy
python311Packages.cartopy.dist
python311Packages.cf-xarray
python311Packages.cf-xarray.dist
python311Packages.django-bootstrap4
python311Packages.django-bootstrap4.dist
python311Packages.fiona
python311Packages.fiona.dist
python311Packages.flask-admin
python311Packages.flask-admin.dist
python311Packages.folium
python311Packages.folium.dist
python311Packages.geoalchemy2
python311Packages.geoalchemy2.dist
python311Packages.geopandas
python311Packages.geopandas.dist
python311Packages.glueviz
python311Packages.glueviz.dist
python311Packages.labelbox
python311Packages.labelbox.dist
python311Packages.osmnx
python311Packages.osmnx.dist
python311Packages.owslib
python311Packages.owslib.dist
python311Packages.pgspecial
python311Packages.pgspecial.dist
python311Packages.pgvector
python311Packages.pgvector.dist
python311Packages.preprocess-cancellation
python311Packages.preprocess-cancellation.dist
python311Packages.psycopg
python311Packages.psycopg.dist
python311Packages.psycopg.doc
python311Packages.pvextractor
python311Packages.pvextractor.dist
python311Packages.pygmt
python311Packages.pygmt.dist
python311Packages.pyosmium
python311Packages.pyosmium.dist
python311Packages.pyproj
python311Packages.pyproj.dist
python311Packages.pytest-postgresql
python311Packages.pytest-postgresql.dist
python311Packages.python-mapnik
python311Packages.python-mapnik.dist
python311Packages.rasterio
python311Packages.rasterio.dist
python311Packages.shapely
python311Packages.shapely.dist
python311Packages.shapely18
python311Packages.shapely18.dist
python311Packages.spectral-cube
python311Packages.spectral-cube.dist
python311Packages.uranium
python311Packages.wktutils
python311Packages.wktutils.dist
python311Packages.wrf-python
python311Packages.wrf-python.dist
pytrainer
pytrainer.dist
qgis
qgis-ltr
qmapshack
saga
spatialite_gui
spatialite_tools
sumo
udig
valhalla
vpv

@NixOS/geospatial , PR finally looks good now. Please review. Thanks.

 Thank you.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/week-in-geospatial-team-11-17-dec-2023/37035/1


Default arguments with string values should have strings in the output documentation

lsf = drivers_parser.add_parser('lsf', help='Flock your jobs to lsf', usage=baseUsageStr.format('lsf'), formatter_class=lambda prog: CustomFormatter(prog, max_help_position=30))
lsf.add_argument('--optLSFConf', metavar='', type=str, required=False, default='-q short')
lsf.add_argument('--optLSFNFilesPerJob', metavar='', type=int, required=False, default=1)

As you can see, it looks like it suggests people should write --optLSFConf=-q short instead of --optLSFConf="-q short".

My preferred solution would be to only put the defaults in quotes in cases where it includes a space. Would that suffice to you or do you have any other thoughts there?

BTW, I have a branch (feature/quote_help_strings_fix36) that implements my suggestion. Please feel free to give it a try!

@dpryan79 I think it should always include quotes.

Fine by me, that's what I'll implement then :)

This is now implemented as requested in the develop branch.


Type parameters with constraints should be reconstructable

TypeScript Version:  3.6.0-dev.20190619

Search Terms: type parameter generic constraint assignable instantiated subtype reconstruct
Code
interface AConstraint {
  x: boolean;
}

function fn<A extends AConstraint>(arg: A): A {
  const { x, ...rest } = arg;
  return { x, ...rest };
}

Expected behavior:
pass
Actual behavior:
test.ts:7:3 - error TS2322: Type '{ x: boolean; } & Pick<A, Exclude<keyof A, "x">>' is not assignable to type 'A'.
  '{ x: boolean; } & Pick<A, Exclude<keyof A, "x">>' is assignable to the constraint of type 'A', but 'A' could be instantiated with a different subtype of constraint 'AConstraint'.

It seems like this should work, since { x, ...rest } should be assignable to A regardless of how A is instantiated.
On a related note, I've found that the following does not throw an error:
interface AConstraint {
  x: boolean;
  y: boolean;
}

function fn <A extends { x: boolean; y: boolean }> (arg: A): A['x'] {
  return arg.y;
}

This also seems like a bug, since A['x'] may not be the same type as A['y'] after A is instantiated (e.g., if A is instantiated as { x: true; y: false }).
Playground Link:
https://www.typescriptlang.org/play/#src=interface AConstraint {
  x%3A boolean%3B
}

function fn<A extends AConstraint>(arg%3A A)%3A A {
  const { x%2C ...rest } %3D arg%3B
  return { x%2C ...rest }%3B
}

Related Issues:
https://github.com/Microsoft/TypeScript/issues/29049

The error seems correct: you have a constraint on A that it's at least AConstraint so you can work with the value you have as though it's an AConstraint, but you can't actually produce a value of type A because you don't know how specific A actually is.  There's no lower bound, so it could be any subtype at all.
For example:
function fn<A extends Animal>(arg: A): A
{
    return new Giraffe("Jeff");  // Giraffe is assignable to Animal, but...
}

let cat = new Cat("Mittens");
let newCat = fn(cat);  // ...we just wanted a cat. :-(

As you point out, in your case you capture ...rest which should cover all the bases in practice--but I think TS is just assuming the worst: A might be never.  Then nothing at all would be assignable to it.

That could be. After further digging, I suspect this might be related to #28884. I will leave this open for now in case my second code example is a distinct issue.


Bring back the metricsFeeder while keeping it in sync w/ metrics-on-canvas.

Continuing from #1310

The ws data maps onto the canvas. It is more raw data than view.
The /api/details data maps onto the details panel. It is more view data than raw.

We Now want to try and keep these things in sync.
Options

Break the isolated mapping, info from /api/details used to render parts of the canvas.
Have a common data struct that is used to render both of these.

Tricky as /api/details is view than data.

Keep the versions of each of these calls in sync. E.g. peek inside both responses for a ts, wait until they line up before updating the view.
Some variation of the above but w/ wss. ts each message and wait until they're in sync before updating the view.

Copied from #1310:
David:
Brainstorm:

even though details and canvas metrics are are requested at different times, the samples' dates should be the same, there is potential to sync them
maybe remove metrics feeder HOC, to get the sync right between details and canvas, then re-add feeder
central metrics object for that stores metrics by node id, can be queried with a timestamp, feeder HOC feeds that timestamp
global metrics timestamp clock, dynamically adjusted based on what sample ranges are available, keeps all metrics in sync


[FIX-340] Added exclusion for FlywayAutoConfiguration

Issue #340

Thanks, integration tests are seem to be running now.


NPE in ScanBaseActivity.onClick()

Crash log -
Fatal Exception: java.lang.NullPointerException
Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference
keyboard_arrow_up
arrow_right
com.getbouncer.cardscan.base.ScanBaseActivity.onClick (ScanBaseActivity.java:354)

As per Android docs here -  Camera.Parameters.getFlashMode() can be null.
current flash mode. null if flash mode setting is not supported.

We are using com.getbouncer:cardscan:1.0.5001 version but this crash can happen on the latest version as well because the master branch don't have a null-check here
Let me know if you need more details.

Thanks for finding this, I'm working on fixing it now.

A fix has been released as part of 1.0.5122. Thank you for reporting!


Integration Candidate 20191030

Describe the contribution
Fixes #361, fixes #373, fixes #374, fixes #381
Testing performed
Steps taken to test the contribution:

Checked out bundle with OSAL and cFE ic-20191030 branches
make ENABLE_UNIT_TESTS=TRUE SIMULATION=native prep
make
make install
make test
Built without warnings, all tests passed except osal_timer_UT (nominal result on linux)
executed cfe, successful startup with no warnings

Expected behavior changes
Resolved potential lockup bug
Resolved anomalous messages produced during app delete
System(s) tested on:

cFS dev server
OS: Ubuntu 16.04
Versions: bundle with OSAL and cFE ic-20191030 branches

Additional context
None
Contributor Info
Jacob Hageman - NASA/GSFC

CCB 20191106 - approved for merge to master


Polygon2D and Polygon3D

Need interface polygon objects for 2D and 3D mesh handling.

At the moment this doesn't seem necessary. Polygon data structures will live in the user domain, see ticket #154. Will re-open at a later date if we decide to expand mesh handling at a later date.


Add a new shape field to ColumnSchema

This creates a place to store shape information for all dimensions of the data across both array/tensor and dataframe formats. In contrast to the existing "value_count" property (which only records the value counts of the lists in list field, this attribute is intended to capture the size of all dimensions of the data (the batch dimension, the list lengths, embedding sizes, etc.)
A few significant design elements:

Defining a Shape dataclass allows us to make them immutable, which we wouldn't get if we sub-classed tuple like some other frameworks do. For compatibility with those other frameworks (and just general ease of use), the Shape constructor accepts a tuple of dimensions, so it should be relatively straightforward to (for example) create a Merlin shape from a Tensorflow shape.
Shapes are stored in dtypes, since shape information is how we know a particular column is a list, and several frameworks we use (e.g. cuDF, Feast) have either a general List dtype or specific list dtypes like int32_list for each element type. The API has been designed to hide this from calling code as much as possible, but it does influence how shapes work to some extent.
The is_list and is_ragged flags are now computed from the shape and can no longer be set by providing them as constructor args. We tried to find a way to maintain that, but it's not possible to use dataclass init vars with the same name as a defined property. The best workaround for this we could come up with was to allow is_list and is_ragged to be set from the properties dictionary, in which case we do our best to infer a shape from the values of these flags.

I reviewed the code. It seems good to me/makes sense - however, I haven't worked in that deep level of Merlin/core to confident approve it

@oliverholworthy I updated this PR to keep is_list and is_ragged as properties that are set in the __post_init__ to match the shape, which really does clean things up quite a bit. I think it still ends up being a breaking change that requires coordination with the other repos though, because validating that the provided flags are consistent with the shape turns up places where that isn't currently true.

I think it still ends up being a breaking change that requires coordination with the other repos though, because validating that the provided flags are consistent with the shape turns up places where that isn't currently true.

Looks like we'll be setting a requirement for the shape to be specified if is_ragged=False is specified, the fixed dimension will be required to be passed. Would it be possible or helpful with the migration to loosen that restriction further and only check the shape if it's used explictly (either with the dims passed to the ColumnSchema constructor or with_shape)

Would it be possible or helpful with the migration to loosen that restriction further and only check the shape if it's used explictly?

I shifted the validation in this general direction, so that only information that's explicitly provided gets validated. I'm not sure about lifting the restriction that some kind of shape info has to be provided (through the dtype's shape, the dims, or the value counts) when is_ragged=False because that will put us in a position where we sometimes don't have a shape. That may complicate the downstream changes as we try to migrate over. 🤔

because that will put us in a position where we sometimes don't have a shape. That may complicate the downstream changes as we try to migrate over

I suppose we're already in the position where we sometimes don't have a shape, since there's nothing in here currently to enforce having a value count when is_ragged=False. Adding this requirement in this PR forces us to address that now. I support that choice if we're commited to making the changes to the downstream libs right now. If it's mostly a question of how we'll identify which parts of the code need to change, we could achieve that with an optional strict mode or something along those lines.
And closely related to this: to what extent will this change make to loading previously saved schemas (e.g. from an NVTabular workflow and saved schema file). Will we be able to load schemas saved with a prior version after merging this? We'd presumably prefer to be backwards compatible if possible, however if it's a necessary breaking change across the saved file format, then we might need some extra docs about this when we release the next version.

Adding this requirement in this PR forces us to address that now. I support that choice if we're commited to making the changes to the downstream libs right now. If it's mostly a question of how we'll identify which parts of the code need to change, we could achieve that with an optional strict mode or something along those lines.

We're thinking along similar lines then; we've disabled the is_ragged=False without shape info validation for now, and will use it to identify the places where changes are needed in further dev work. 👍🏻

to what extent will this change make to loading previously saved schemas (e.g. from an NVTabular workflow and saved schema file). Will we be able to load schemas saved with a prior version after merging this? We'd presumably prefer to be backwards compatible if possible, however if it's a necessary breaking change across the saved file format, then we might need some extra docs about this when we release the next version.

I believe the change is backward but maybe not forward compatible, since the allowed values of value counts are slightly different in a more permissive direction after this change.


:construction_worker: feat(cd): Only release snapshot releases on workflow_dispatch

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #145   👈

This comment was auto-generated by Graphite.


Unable to run tests compiled with Babel

I'm trying to set up some tests for a package I'm compiling with Babel (in order to use Stage 3 decorators). Babel is compiling files from src into dist with sourcemaps.

This extension only sees the original decorators.test.js in the src directory. If I configure it to only look in dist with "nodejs-testing.include": ["./dist"] it won't see any tests.
I've tried a bunch of permutations trying to get it to see the compiled tests. The only thing that seems to make it run the compiled test, is to copy/paste the compiled version into the original file. Obviously that's not a solution and breaks imports and such, but it will see that file as a test file at least.
I've tried refreshing the test explorer, reloading the VS Code window, using inline sourcemaps, outputting the compiled code in the same directory as the source, etc. Nothing I do seems to convince it to see anything but the original copy of the test file.
I thought for a second that maybe it was being magical and smart, and listing the the source files but actually running the compiled versions via the source maps. But that's not the case, running the test immediately fails due to Invalid or unexpected token because of the decorators.
I also thought maybe it was trying to do something like that, so I tried removing the sourcemaps and comments from the output file but that doesn't change anything.
Babel is only transforming the decorators themselves, so all the important lines like import { test } from "node:test"; are still there for the extension to detect.
I even checked if the extension was respecting my .gitignore or something silly like that, but nope.
Finally, when I run the compiled file with node it runs correctly.
Minimal reproducible example: https://gist.github.com/zeel01/6c183f2ce1c62c4602208ca7ad618fe6

It looks like I'm getting this error in the Extension Host: [error] Error: Unknown node type StaticBlock.
It looks like Babel sometimes outputs static initializer blocks, and the test runner doesn't like them.

Ah, yes, I forgot I still used the abondoned estraverse in this library. Need to drop it like in https://github.com/microsoft/vscode-js-debug/pull/1868