Set up redirect URL for host terms

User story
As a fiscal host admin I am constantly having to link to our terms and conditions to reference them in user inquiries, etc, and it would be great if they were easier to access.
As a Collective admin, I want to easily access the terms for any fiscal host.
Best solution for this problem
Set up a URL like opencollective.com/host/terms that redirects to whatever hosts puts in the "terms" link box in their settings. They are already linked from the top of host pages, but having a URL would help a lot.

Hi, I'm looking to get my feet wet again, may I have a go at this?

Hi @brymut, feel free to! Host terms are stored in host.settings.tos.
I'd add to the specs above that:

If no terms have been defined, just show a message like This host didn't specify any TOS.
If it's not an URL, then just display the raw text in a MessageBox

Hi @Betree / @alanna , on the design side of things. This is what I've been able to come up with.
Clicking through would open a new tab so that redirecting doesn't have the Collective admin leave opencollective completely.
I'm using the legacy <CollectiveCover> at the top since its the only component I can find so far that fits, the newer version has tabs for "Contributions"/"Transactions" and doesn't use have a title property so that we can show that the page is the Fiscal Host's terms using a <FormattedMessage>.

If the terms are an external link

If the terms are not available/ not set by the Fiscal Host admin.

If the terms are set up as plain text by the Fiscal Host admin.

May I please get some feedback on this?

Nice work!
We should not use the legacy cover, we're looking to get rid of it soon so we can't use it in new devs.
The rest is looking great. I wonder if there's a way with NextJs to redirect by sending back a special HTTP status, so that the transitional page will not appear. Not sure if that's possible, I'm going to check.

Any suggestion/alternative to what might work in place of the legacy cover?

I just checked and NextJS in fact recommends to redirect after mount - and to avoid it during rendering (see https://github.com/zeit/next.js/issues/4931#issuecomment-512787861). So we have to go above NextJS if we want to handle this properly, in https://github.com/opencollective/opencollective-frontend/blob/05228242f3327232c2b051ed8360d53944aa1f36/server/routes.js. Check app.renderToHTML / app.render to generate the fallback page from there.

Any suggestion/alternative to what might work in place of the legacy cover?

@brymut Try this one:
<Container pt={[4, 5]} mb={4}>
  <Flex alignItems="center" flexDirection="column" mx="auto" width="100%" maxWidth={320}>
    <LinkCollective collective={collective}>
      <Logo collective={collective} className="logo" height="10rem" style={{ margin: '0 auto' }} />
      <H2 as="h1" color="black.900" textAlign="center">
        {collective.name}
      </H2>
    </LinkCollective>
  </Flex>
</Container>

Hi again @Betree, I've had some progress on this and have opened a pull request. Could you please have a look when you have a chance.
I'm having an issue with understanding what you meant on how we could go above Nextjs when handling the redirect in routes.js, could you please explain a little more on that?

The routes in /server/routes.js have priority over NextJS's routes. They are pure node endpoints.
From there we can still generate NextJS's pages (ie. by calling renderToHTML) but we can also redirect and do other kind of magic that NextJS would not allow us to do while rendering.

Bumping this again. This causes me pain consistently, and it seems like such a small thing to ask for. Can it just be done?

@Betree : I can help with this, but my thinking is it might be better to show the terms and conditions in a modal, that way de don't take the user out of the context of the page; maybe they came to check something and navigating them to a special page in my mind might be counter intuitive. So how about a simple modal with the terms and conditions and the user can just dismiss it. 😄 WDYT?

@SudharakaP The problem is that we don't really know where the link is pointing to. It can be a web page, a Google Doc, a PDF, etc. Using an iframe for this could cause many problems, I think we should stick with a redirect.
I'm a bit worried about security though. Today, when people are redirected from unverified user links, we show a warning like this one: https://opencollective.com/redirect?url=http%3A%2F%2Fwebsite.com. The goal is to prevent phishing attacks where someone would make you click on a link that redirects to a website that looks like opencollective (eg. opnecollective.com) that the attacker could use to steal users info.
With this redirect link in place, I could just bypass the redirect verification by linking to /host/terms (in my longDescription, private messages, etc.) and set my host terms URL to https://opnecollective.com/sign-in.
We must make sure that such an attack is not possible when implementing this issue.

Looks like this might never happen.... can someone just set me up a redirect from opencollective.foundation/terms to https://docs.google.com/document/u/2/d/e/2PACX-1vQ_fs7IOojAHaMBKYtaJetlTXJZLnJ7flIWkwxUSQtTkWUMtwFYC2ssb-ooBnT-Ldl6wbVhNQiCkSms/pub as a workaround?

@SudharakaP The problem is that we don't really know where the link is pointing to. It can be a web page, a Google Doc, a PDF, etc. Using an iframe for this could cause many problems, I think we should stick with a redirect.
I'm a bit worried about security though. Today, when people are redirected from unverified user links, we show a warning like this one: https://opencollective.com/redirect?url=http%3A%2F%2Fwebsite.com. The goal is to prevent phishing attacks where someone would make you click on a link that redirects to a website that looks like opencollective (eg. opnecollective.com) that the attacker could use to steal users info.
With this redirect link in place, I could just bypass the redirect verification by linking to /host/terms (in my longDescription, private messages, etc.) and set my host terms URL to https://opnecollective.com/sign-in.
We must make sure that such an attack is not possible when implementing this issue.

@Betree : I am a bit confused by this. Today we have the code,
https://github.com/opencollective/opencollective-frontend/blob/39cace1de0f2f2d7bad2119df006fb0bdff80f70/components/collective-page/hero/Hero.js#L280-L290
for the link to the terms for fiscal sponsorship which appears on the host page. This doesn't go through the external-redirect.js and thus the host can put any URL they want. My thinking is that we trust the hosts. So adding this kinda redirect doesn't quite make sense to me as only the host can set the terms url in the host settings. 🤔
In any case, I've opened a PR with the external-redirect.js so that whatever the host puts in the terms we shall treat it as an external redirect and show the user the warning (see the screen-cast there). However as I've explained above I think this might be unnecessary as we are already allowing the user to go to this url from the host page without the warning. Does that make sense? 🤔 😸

My thinking is that we trust the hosts

To create a host, all it takes is to create an organization then click a button. So no, we can't automatically trust a host just because they're a host.

This doesn't go through the external-redirect.js and thus the host can put any URL they want

This is exactly the problem here. What I tried to explain in https://github.com/opencollective/opencollective/issues/2757#issuecomment-912308225 is that someone could exploit such feature to bypass our redirect validations, since we're not going through external-redirect:

Create a new host
Set its host terms to redirect URL to https://malicious-phishing-website.com
Now paste your https://opencollective.com/my-host/terms link in long descriptions, updates, and comments. Since it's an Open Collective link, it won't be sanitized behind a redirect.
When clicking on the https://opencollective.com/my-host/terms link, users will be redirected to https://malicious-phishing-website.com without any warning, facilitating phishing attacks (eg. with a domain like https://opnecollective.com) which could result in stealing user's personal information.

@alanna I've marked foundation as a trusted host. With what @SudharakaP implemented, you can now use https://opencollective.com/foundation/terms to access the TOS.

Amazing! Thank you!


Monitor simulation and check results

Hello
I submit my jobs in unix cluster. I can do that by pyaedt. Is there any way to monitor the status of the job and if so, is it possible to get results from the simulation, like when I run simulation in GUI and check the results?

@arifroni Apart from the get_monitor_data method nothing else is implemented. You can use the Electronics Desktop Job Monitoring tool.


B 20653 mobile home shipment card

B-20653
Summary
This PR updates the mobile home shipment status to 'SUBMITTED' when the shipment is submitted by the customer.
This also removes 'Please' from the shipment option description, and updates the shipment opiton description to match the PO AC.
Any labeling for Mobile home that's user facing is now "Mobile Home".
Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

How to test

Login as a customer
Add a mobile home shipment
Confirm the labeling is "Mobile Home"
Confirm description changes described above
Complete the move and sign
Confirm in DB that the mtoshipment status for that mobile home shipment is set to 'SUBMITTED'

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Backend

[ ] Code follows the guidelines for Logging.
[ ] The requirements listed in Querying the Database Safely have been satisfied.

ANDI Screenshots
Removed location Page title

Removed Please from shipment list description

Change of dimension description

Shipment Option label change

Shipment Card label change

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 10b761b1f1ce500006e5679a2c223eacf64cf734

Some of the things I've noticed while testing the functionality - There is another remarks field on the 2nd page which can be removed. And also when I edit, the pickup address doesn't seem to populate with existing data.

Some of the things I've noticed while testing the functionality - There is a remarks field on the 1st page and another on the 2nd page which can be removed. And also when I edit, the pickup address doesn't seem to populate with existing data.

Why should they be removed?
I left those remark fields because the other shipments have them as well, and in case the customer has other comments on the move before submitting. I feel like I should change the description on them because I left the formatting the same as the boat shipment though lol
I'm working on seeing why the pickupaddress isn't populating on edit now

Some of the things I've noticed while testing the functionality - There is a remarks field on the 1st page and another on the 2nd page which can be removed. And also when I edit, the pickup address doesn't seem to populate with existing data.

Ah actually I see why they gotta go I have the remarks already on the location page, I'll get rid of those. I feel like I should change the description on them because I left the formatting the same as the boat shipment though lol
I'm working on seeing why the pickupaddress isn't populating on edit now

Yeah, sorry I could have been more clear. For boat I have the remarks on the 1st page and not on the location page. And for the description - yeah... not sure because they boat story had a mockup with those description already on it, but I don't see one for Mobile home.

"home" in "Mobile home Information" should be capitalized.

Also not sure if they need to be capitalized mid-sentence down in the remarks section here. However, I do see a typo where "signigicantly" should be "significantly"

If you think that significantly typo is out of scope for this PR, let me know and I can get an issue created. Looks like it would be a typo for both mobile and boat shipment remarks

B-20653

D

One more comment because I am also looking at Aaron's changes for the office users - can we make the destination address field match? I'm good with either Destination or Destination address, whatever you both agree on. Just would like it to be the same if it's not too big of a deal :)
Destination for customer on the left bottom vs Destination address for office user on the right bottom
cc @WeatherfordAaron

Disregard, you're meeting both meeting AC with what you have

 "home" in "Mobile home Information" should be capitalized.

ah I see I'm on it

Functionality looks good! Code looks good and meets AC. I did notice the AC is "Given a Mobile Home shipment has been created,  When a customer reviews their boat shipment," and that When should probably refer to the mobile home shipment rather than boat
Inserting myself into this PR so forgive me if any of these are supposed to be this way, but noticed a few other small things. If all instances of the words "mobile home" should be "Mobile Home" I see a few spots without that capitalization - "Mobile home Information", "Mobile home details and measurements"
Also not sure if they need to be capitalized mid-sentence down in the remarks section here. However, I do see a typo where "signigicantly" should be "significantly"

Yea that's definitely fair. I'm gonna change them all to follow "Mobile Home"

Functionality looks good! Code looks good and meets AC. I did notice the AC is "Given a Mobile Home shipment has been created,  When a customer reviews their boat shipment," and that When should probably refer to the mobile home shipment rather than boat
Inserting myself into this PR so forgive me if any of these are supposed to be this way, but noticed a few other small things. If all instances of the words "mobile home" should be "Mobile Home" I see a few spots without that capitalization - "Mobile home Information", "Mobile home details and measurements"
Also not sure if they need to be capitalized mid-sentence down in the remarks section here. However, I do see a typo where "signigicantly" should be "significantly"

Yea that's definitely fair. I'm gonna change them all to follow "Mobile Home"

If you haven't already, updating this branch might fix some of it.

Functionality looks good! Code looks good and meets AC. I did notice the AC is "Given a Mobile Home shipment has been created,  When a customer reviews their boat shipment," and that When should probably refer to the mobile home shipment rather than boat
Inserting myself into this PR so forgive me if any of these are supposed to be this way, but noticed a few other small things. If all instances of the words "mobile home" should be "Mobile Home" I see a few spots without that capitalization - "Mobile home Information", "Mobile home details and measurements"
Also not sure if they need to be capitalized mid-sentence down in the remarks section here. However, I do see a typo where "signigicantly" should be "significantly"

I agree.. it should be Mobile Home Information instead of Mobile home Information.
Anytime "mobile" and "home" are together in reference to the type of shipment, they should both be capitalized. The only caveat is when we are referring to the customer's mobile home.

Testing: Success w/1 issue (see comment) Code: lgtm

Checked update.  issue resolved.


Move to github runners for x86 jobs

Current self-hosted runners migth not be available for a couple of days
Signed-off-by: Itxaka<EMAIL_ADDRESS>

Already run correctly where the self-hosted runners would have run.


Fix issue #9

Generate 32character long hex-based filter ids.

Please restore the version number back, thank you  (I will change the version number before releasing the new version, so you don't need to change it actively. ).


NodeOS crashes on start

Built from DAWN-4.0 tag with a node running on the jungle test net NodeOS cannot be restarted unless both the shared memory files and block files are first deleted.  This seems to be the case on most nodes of this network.   We have tried restoring a block file from a previous time when the node was running properly and using --replay, this causes the same crash as a restart.
If block files and shared memory files are not deleted NodeOS crashed on startup with the following error.
1171771ms thread-0   chain_plugin.cpp:125          plugin_initialize    ] initializing chain plugin
1171773ms thread-0   block_log.cpp:120             open                 ] Log is nonempty
1171773ms thread-0   main.cpp:103                  main                 ] basic_ios::clear: iostream error

Startup script --
#!/bin/bash
NODEOS=/opt/eos-source/build/programs/nodeos/nodeos
DATADIR=/opt/JungleTestnet-ayeaye
$DATADIR/stop.sh
$NODEOS --data-dir $DATADIR --config-dir $DATADIR "$@" > $DATADIR/stdout.txt 2> $DATADIR/stderr.txt &  echo $! > $DATADIR/nodeos.pid

Config.ini --
get-transactions-time-limit = 3
genesis-json = "/opt/JungleTestnet-ayeaye/genesis.json"
block-log-dir = "/opt/JungleTestnet-ayeaye/blocks"
http-server-address = <IP_ADDRESS>:8888
p2p-listen-endpoint = <IP_ADDRESS>:9876
p2p-server-address = <IP_ADDRESS>:9876
access-control-allow-origin = *
allowed-connection = any
log-level-net-plugin = info
max-clients = 120
connection-cleanup-period = 30
network-version-match = 0
sync-fetch-span = 2000
enable-stale-production = false
required-participation = 33
mongodb-queue-size = 256
plugin = eosio::producer_plugin
plugin = eosio::chain_api_plugin
plugin = eosio::history_plugin
plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
agent-name = ayeaye
plugin = eosio::producer_plugin
private-key = ["xxxxx","xxxxx"]
producer-name = ayeaye

Version --
root@jungle1:/opt/JungleTestnet-ayeaye# /opt/eos-source/build/programs/nodeos/nodeos -v
2615709958

Having the same issue

This is probably because the new version uses a different shared_memory/logfile schema.

Did u manage to solve this? @jdkibler  @HuweyII

try adding  chain-state-db-size-mb = 8192 to config.ini, worked for me

closed as no reply


[Forwardport] v2.7: After -- upgrade, high CPU/load on nodes and database, nodes flapping between ready/unready, excessive "refresh processing" logs

Original Issue:
https://github.com/rancher/rancher/issues/39401

✅ PASSED
Reproduction Environment

Component
Version / Type

Rancher version
2.6.9

Installation option
Helm (high availability)

RKE binary version used
v1.3.15

If Helm Chart k8s cluster
v1.24.4

Cert Details
Let's Encrypt / nginx

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
n/a

Downstream K8s version
n/a

Authentication providers enabled
local

Logged in user role
Admin, Standard User

Browser type
Google Chrome

Browser version
108.0.5359.124 (Official Build) (x86_64)

🚨 Additional Reproduction Setup Details: Click to Expand
#!/bin/sh

helm repo update

kubectl create namespace cattle-system

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml

helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.7.1

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --set hostname=$URL_VAR \
  --set bootstrapPassword=$PW_VAR \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=$EMAIL_VAR  \
  --set letsEncrypt.ingress.class=nginx \
  --set rancherImageTag=$IMAGE_TAG \
  --version $VERSION

Reproduction steps

Create a k8s cluster for rancher HA. Ensure that there are 3 nodes, RKE, each node all roles, (m5.4xlarge in AWS ec2) was used in testing
Install rancher 2.6.9. Complete basic setup (provide bootstrap, set new password).
Create 6,000 tokens (script available). Tokens are used to slow down the refresh process slightly since the local provider is being used (which can complete refresh quicker than other providers)
Create 700 users and user attributes (script available). Ensure that the user attributes are sufficiently large (I used large annotations to achieve this)
Upgrade rancher to 2.7.0 (I used a helm upgrade command, see below)
Wait and observe etcd memory usage, you will run out of memory soon (you can also increase log verbosity to observe the constant user refresh messages in the logs)

helm upgrade rancher rancher-latest/rancher \
  --namespace cattle-system \
  --set hostname=$URL_VAR \
  --set bootstrapPassword=$PW_VAR \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=$EMAIL_VAR  \
  --set letsEncrypt.ingress.class=nginx \
  --set rancherImageTag=$IMAGE_TAG \
  --version $VERSION

Additional Info
RESULTS
✅ Expected
To be able to upgrade without the etcd memory usage erroring out
❌ Actual
etcd memory usage ran out shortly after upgrade ~5 minutes. Getting the warning alarm:NOSPACE. And memory went from 249 MB to ==> 2.2 GB

Validation Environment

Component
Version / Type

Rancher version
v2.7-65089ee0b7369e0d189d9f0c8da7f501b9e672ca-head

Rancher commit link
https://github.com/rancher/rancher/commit/65089ee0b7369e0d189d9f0c8da7f501b9e672ca

Installation option
Helm (high availability)

RKE binary version used
v1.3.15

If Helm Chart k8s cluster
v1.24.4

Cert Details
Let's Encrypt / nginx

Docker version
20.10.7, build f0df350

Helm version
v2.16.8-rancher2

Downstream cluster type
n/a

Downstream K8s version
n/a

Authentication providers enabled
local

Logged in user role
Admin, Standard User

Browser type
Google Chrome

Browser version
108.0.5359.124 (Official Build) (x86_64)

🚨 Additional Validation Setup Details: Click to Expand
#!/bin/sh

helm repo update

kubectl create namespace cattle-system

kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml

helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.7.1

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --set hostname=$URL_VAR \
  --set bootstrapPassword=$PW_VAR \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=$EMAIL_VAR \
  --set letsEncrypt.ingress.class=nginx \
  --set rancherImageTag=$IMAGE_TAG \
  --version $VERSION

Validation steps

Create a k8s cluster for rancher HA. Ensure that there are 3 nodes, RKE, each node all roles, (m5.4xlarge in AWS ec2) was used in testing
Install rancher 2.6.9. Complete basic setup (provide bootstrap, set new password).
Create 6,000 tokens (script available). Tokens are used to slow down the refresh process slightly since the local provider is being used (which can complete refresh quicker than other providers)
Create 700 users and user attributes (script available). Ensure that the user attributes are sufficiently large (I used large annotations to achieve this)
Upgrade rancher to 🚨 v2.7-head (I used a helm upgrade command, see below)
Wait and observe etcd memory usage

helm upgrade rancher rancher-latest/rancher \
  --namespace cattle-system \
  --set hostname=$URL_VAR \
  --set bootstrapPassword=$PW_VAR \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=$EMAIL_VAR \
  --set letsEncrypt.ingress.class=nginx \
  --set rancherImageTag=$IMAGE_TAG \
  --version $VERSION

Additional Info
RESULTS
✅ Expected
To be able to upgrade without the etcd memory usage erroring out
✅ Actual
Was able to upgrade without any errors from etcd memory, usage stayed at ~249 MB before and after upgrade

Release note: Fixed issue where handlers involving handlers would infinitely loop if a user had no tokens or only had tokens that did not the ExtraByProvider field.


Redirect blog URLs to right places.

We're going to point blog.covidactnow.org at the main website and turn off the WordPress blog.  These URL redirects were provided by Mikayla.

 Reroute blog URL to Learm


wrong editor body font-family

In some scenarios when switching to the viewports view, the font-family gets messed up.

It looks like it should be a simple fix of applying font-family: system-ui to the body.

That's weird - I can try and have a look at this over the next few days

This is something that I've noticed as well, and was introduced in #86.

Hmm, I can't seem to reproduce. What browser and OS? @johnletey @souporserious

I've seen it in Chrome and Safari. Unfortunately, it happens somewhat randomly, but almost always when switching to the viewports tab. The body font-family isn't set when I last checked which seems to be the underlying issue. Should be a good first issue for someone if they want to take it 😃

Hmm, I can't seem to reproduce. What browser and OS? @johnletey @souporserious

@jordanoverbye Sorry for the late reply, but I am using MacOS Mojave with Safari.


Updated and reformated README.md

I tried to update and reformat the README document a bit, since i was confused with the usage at first.
Also I think the Example section should be reworked.
a) I think its a bad example because it does not show hot the base images are generated. This is confusing.
b) It might be better to use a website which is publicly available (http://dygraphs.com/tests/dynamic-update.html) and not the admin dashboard which needs custom code to work.

@tairun could you please fix conflicts on this one.

@puneet0191  Sure thing. This should take care of it.

@tairun thanks it seems a lot of changes are getting reverted with this, could you please update your branch to latest master and then send your changes on top of it.

@tairun conflicts here again :)


Issue/homepage alias

This PR changes the way the home page is stored in the system by adding a dedicated alias record that can be updated to point to the route that should be the home page.
This means that the alias of the content item being pointed to by the home alias will not change when making that content item the homepage, which solves an issue described in #5504 as well as simplifies the way that we can set something to be the homepage.
This also handles the case where the user may check a content item to become the home page but saves that item as a draft. Performing this action won't update the home alias record, and yet the updated content item will persist the fact that it is promoted to become the homepage - which will happen as soon as it is published.

@sfmskywalker, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@sfmskywalker, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;


Published ColDP resource shows as not published

https://ipt.gbif-uat.org/resource?r=clements

Also says no records, maybe that's related:

I think we should just sum up all published records no matter what entity they were for a global count.

How do we count records for a ColDP resource?

I would suggest to count the total records of all data files as the default for any DP resource. There is no core any longer...

Okay, thanks. For Camtrap we take the number of observations

deployed


[WIP] IAM:System roles documentation update

IAM: system roles documentation updated:

general description of what is IAM SR
CSV tables description
links etc

Motivation and context

How has this been tested?

Checklist

[X] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[X] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

I will close the PR for now.


Changing default ports not changing

⚠ Please verify that this bug has NOT been reported before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
I am trying to add to instances of radarr, so I changed the port numbers so they didnt conflict. but it doesnt seem to do what it should and they are not accessible on the advertised port. I also had the same issue trying to install jellyfn and emby, which by default use the same ports.
👟 Reproduction steps
normal port config 7878:7878, changed to 7879:7879 in the compose file.
👀 Expected behavior
this should change the ui port to the new port
😓 Actual Behavior
cant access the url using the new port
Dockge Version
1.4.2
💻 Operating System and Arch
bookworm
🌐 Browser
edge
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Only the port before the colon needs to be changed (7879:7878). The port after the colon concerns the container and should not be changed.
7879 : 7878
host container


use gollm=>mira equation to amr pipeline

Summary
Replace latex => sympy.parse_latex => mira pipeline with latex => gollm => mira pipeline.
This is the 2nd part to: https://github.com/DARPA-ASKEM/terarium/pull/5846
This PR also clean up the mira-endpoint.
/mira/latex-to-amr => /knowledge/equations-to-model-debug
Testing
POST /knowledge/equations-to-model should return a model-id, which in turn should reflect the equations.
{
  "equations": [
  "\\frac{d S(t)}{d t} = - b_q S(t) I(t)",
  "\\frac{d E(t)}{d t} = b_q S(t) I(t) - r_X E(t)",
  "\\frac{d I(t)}{d t} = r_X E(t) - g_p_q I(t)",
  "\\frac{d R(t)}{d t} = g_p_q I(t)"
   ]
}

why the debug in equations-to-model-debug ?

@Tom-Szendrey I want to flag it as not meant to be used aside from debugging. The current pipeline is not very transparent, it has 3-4 junctions (llm-enrichment, llm-code-gen, code-eval to sympy, ode-to-amr) where things can go wrong but not really set up to report errors at each stage. Because it is also coupled with SKEMA stuff and model enrichment, and is used as a one-shot model creation process in the UI, it is just not ideal to refactor it until we agree on a more sane process. So for now we have a debugging analog.


Source Package URL is broken on chocolatey.org/packages/ChocolateyGUI

The Source Package link for the ChocolateyGUI package on chocolatey.org points to the URL below which doesn’t exist:
https://github.com/chocolatey/ChocolateyGUI/tree/develop/ChocolateyPackage
Per an email from Rob Reynolds it should point to:
https://github.com/chocolatey/ChocolateyGUI/tree/develop/nuspec/chocolatey

actually, if you look at the nuspec file in this repository you'll see that the correct url is used.
https://github.com/chocolatey/ChocolateyGUI/blob/develop/nuspec/chocolatey/ChocolateyGUI.nuspec#L11
It seems like it was fixed the day after the latest available release on chocolatey, which is why it doesn't show up there

Is there any chance of getting the package source URL updated on chocolatey.org before the next release?

that probably won't happen until a new release.
When a version is approved on chocolatey.org, they can't be changed. So a new package version would be needed to be pushed to change the package source URL.

Roger.  Should this issue be closed then?

I would say yes, as it has already been solved in the source code.
I don't have the power to close issues though.

@AdmiringWorm thanks for commenting on this.
Yes, this was fixed here: https://github.com/chocolatey/ChocolateyGUI/issues/550 which is due for release in 0.17.0.


Add support for grid tables

Is your feature request related to a problem? Please describe.
Some times you need to create a table in html because the content can't be easily prepared in MD, for example, when using breaks in table cells.
Case in point: https://docs.microsoft.com/en-us/dotnet/architecture/microservices/net-core-net-framework-containers/container-framework-choice-factors
The original html table was:

Architecture / App Type
Linux containers
Windows Containers

Microservices on containers
.NET Core
.NET Core

Monolithic app
.NET Core

.NET Framework

.NET Core

Best-in-class performance and scalability
.NET Core
.NET Core

Windows Server legacy app ("brown-field") migration to containers
--
.NET Framework

New container-based development ("green-field")
.NET Core
.NET Core

ASP.NET Core
.NET Core

.NET Core (recommended)

.NET Framework

ASP.NET 4 (MVC 5, Web API 2, and Web Forms)
--
.NET Framework

SignalR services
.NET Core 2.1 or higher version

.NET Framework

.NET Core 2.1 or higher version

...

Describe the solution you'd like
Use the grid tables extension already supported by markdig
It'd be like this with grid tables:
+---------------------------------------+---------------------------------------+---------------------------------------+
| **Architecture / App Type**           | **Linux containers**                  | **Windows Containers**                |
+=======================================+=======================================+=======================================+
| Microservices on containers           | .NET Core                             | .NET Core                             |
+---------------------------------------+---------------------------------------+---------------------------------------+
| Monolithic app                        | .NET Core                             | .NET Framework                        |
|                                       |                                       |                                       |
|                                       |                                       | .NET Core                             |
+---------------------------------------+---------------------------------------+---------------------------------------+
| Best-in-class performance and         | .NET Core                             | .NET Core                             |
| scalability                           |                                       |                                       |
+---------------------------------------+---------------------------------------+---------------------------------------+
| Windows Server legacy app             | \--                                   | .NET Framework                        |
| (\"brown-field\") migration to        |                                       |                                       |
| containers                            |                                       |                                       |
+---------------------------------------+---------------------------------------+---------------------------------------+
| New container-based development       | .NET Core                             | .NET Core                             |
| (\"green-field\")                     |                                       |                                       |
+---------------------------------------+---------------------------------------+---------------------------------------+
| ASP.NET Core                          | .NET Core                             | .NET Core (recommended)               |
|                                       |                                       |                                       |
|                                       |                                       | .NET Framework                        |
+---------------------------------------+---------------------------------------+---------------------------------------+
| ASP.NET 4 (MVC 5, Web API 2, and Web  | \--                                   | .NET Framework                        |
| Forms)                                |                                       |                                       |
+---------------------------------------+---------------------------------------+---------------------------------------+
| SignalR services                      | .NET Core 2.1 or higher version       | .NET Framework                        |
|                                       |                                       |                                       |
|                                       |                                       | .NET Core 2.1 or higher version       |
+---------------------------------------+---------------------------------------+---------------------------------------+
| WCF, WF, and other legacy frameworks  | WCF in .NET Core (only the WCF client | .NET Framework                        |
|                                       | library)                              |                                       |
|                                       |                                       | WCF in .NET Core (only the WCF client |
|                                       |                                       | library)                              |
+---------------------------------------+---------------------------------------+---------------------------------------+
| Consumption of Azure services         | .NET Core                             | .NET Framework                        |
|                                       |                                       |                                       |
|                                       | (eventually all Azure services will   | .NET Core                             |
|                                       | provide client SDKs for .NET Core)    |                                       |
|                                       |                                       | (eventually all Azure services will   |
|                                       |                                       | provide client SDKs for .NET Core)    |
+---------------------------------------+---------------------------------------+---------------------------------------+

As for authoring a Grid Table, this VS Code extension could help: https://marketplace.visualstudio.com/items?itemName=shuworks.vscode-table-formatter
Describe alternatives you've considered
Using standard, more readable (🤔?) md that still needs some html:
| Architecture / App Type | Linux containers | Windows Containers |
|-------------------------|------------------|--------------------|
| Microservices on containers | .NET Core | .NET Core |
| Monolithic app | .NET Core | .NET Framework
 .NET Core |
| Best-in-class performance and scalability | .NET Core | .NET Core |
| Windows Server legacy app ("brown-field") migration to containers | -- | .NET Framework |
| New container-based development ("green-field") | .NET Core | .NET Core |
| ASP.NET Core | .NET Core | .NET Core (recommended)
 .NET Framework |
| ASP.NET 4 (MVC 5, Web API 2, and Web Forms) | -- | .NET Framework |
| SignalR services | .NET Core 2.1 or higher version | .NET Framework
 .NET Core 2.1 or higher version |
| WCF, WF, and other legacy frameworks | WCF in .NET Core (client library only) | .NET Framework
 WCF in .NET Core (client library only) |
| Consumption of Azure services | .NET Core
 (eventually all Azure services will provide client SDKs for .NET Core) | .NET Framework
 .NET Core
 (eventually all Azure services will provide client SDKs for .NET Core) |

Additional context
Nothing else.
Thanks 😊

Thanks @mvelosop for filing this issue. @SyntaxC4 @meganbradley would you be the right folks to discuss this customer suggestion with?

@mairaw @mvelosop @SyntaxC4 we aren't likely to implement support for Markdown grid tables, but are planning to create a new Docs Markdown extension for tables to address various issues. I've added a link to this request in the iternal feature so we can consider these requirements when we create the new extension.
https://ceapex.visualstudio.com/Engineering/_workitems/edit/119502

Thanks @meganbradley.
Just let me know in case you need some help in whatever form.
I'm also an indirect stakeholder here, because I developed a docx+pdf generator, that generates e-books from the docs repo, that's currently used to generate five e-books for the .NET Architecture Guides site.
Since I'll have to adapt to the new table format, I'd like to get started as soon as there's something to work on.
Thanks a lot!


Add Command Suggestions and Tab Completion

Description
Add command tab completion and visual suggestions

Testing

observed suggestions in game
added "pumpkin test client_side_arg_parsers" command to test all client side parsers (maybe this should be hidden behind a feature flag, but it proved very useful while debugging parser ids that are outdated on wiki.vg, so it probably should be kept for future version updates)

Checklist
Things need to be done before this Pull Request can be merged.

[x] add packet for client-side suggestions
[x] add packets for server-side suggestions
[x] test a bit more

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

Limitations
Target selectors are rejected on the client side. I'm not sure why that happens or what to do about that, but I might revisit this after digging through vanilla source code more thoroughly.

I was waiting for this :smile:

@Snowiiii Not sure whether you got a notification already, but this pr is ready for review now 🚀

Currently testing this. I wonder why on every command there is "execute" ?

Currently testing this. I wonder why on every command there is "execute" ?

What version of Minecraft are you using? I'm not seeing this at all

Currently testing this. I wonder why on every command there is "execute" ?

What version of Minecraft are you using? I'm not seeing this at all

I sue 1.21.3. I still see "execute" on every Command, It goes away when pressing ESC

Currently testing this. I wonder why on every command there is "execute" ?

What version of Minecraft are you using? I'm not seeing this at all

I sue 1.21.3. I still see "execute" on every Command, It goes away when pressing ESC

That's extremely weird, but I can't reproduce it. Maybe I could try running pumpkin on windows, but I don't really know what could cause this

When I run on windows it works fine aswell

When I run on windows it works fine aswell

Im on Linux

I usually develop on ubuntu using wsl2 and it works there. Ill ask on discord whether someone else could try to reproduce this

When I run on windows it works fine aswell

Im on Linux

@Snowiiii could you try again using the latest commit? Every suggestions the server sends should be printed to the console

LGTM.
Big Thanks @user622628252416 :heart:


Internal error: calling StringValue::Get on a NULL value

What happens?
Reporting an internal error as directed.  The code below produces the error
InternalException: INTERNAL Error: Calling StringValue::Get on a NULL value

To Reproduce
import duckdb
conn = duckdb.connect()
conn.sql('''
INSTALL spatial;
LOAD spatial;
COPY (SELECT * from read_parquet('https://huggingface.co/datasets/boettiger-lab/ca-30x30/resolve/main/ca2024.parquet') )
TO 'ca2024.fgb' WITH (FORMAT GDAL, DRIVER 'flatgeobuf');
''')

OS:
Ubuntu
DuckDB Version:
1.1.1
DuckDB Client:
python
Hardware:
No response
Full Name:
Carl Boettiger
Affiliation:
UC Berkeley
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?

[X] Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

[X] Yes, I have

So, I had a look at this and indeed there's an issue on our end where we don't check for NULL geometries properly. I have a fix in progress, but even with it applied the query still fails because unfortunately there is an underlying issue in that flatgeobuf does not support writing FGB spatial indexes when some geometries are NULL. This is a known limitation documented by GDAL, also discussed here
Once my fix is merged you can work around it by adding the SPATIAL_INDEX=NO layer creation option, e.g.
COPY (SELECT * from read_parquet('https://huggingface.co/datasets/boettiger-lab/ca-30x30/resolve/main/ca2024.parquet') )
  TO 'ca2024.fgb' WITH (FORMAT GDAL, DRIVER 'flatgeobuf', LAYER_CREATION_OPTIONS ('SPATIAL_INDEX=NO'));


fix: repair CI pipeline

Description
trying to fix failing CI

Thanks for your contribution!
https://github.com/hasadna/open-bus-map-search/pull/94
I did the same thing, sorry for the duplication, I didn't notice your PR until it was too late


eks-fargate cluster creation failing with coredns patch request

Logs
Test Report.txt
What happened?
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
import * as eks from "@pulumi/eks";
import * as k8s from "@pulumi/kubernetes";
//Create a VPC with private and public subnets in all AZ's of the region
const vpc = new awsx.ec2.Vpc("my-vpc",{
cidrBlock: "<IP_ADDRESS>/16",
numberOfAvailabilityZones: "all",
});
//Create an EKS cluster with the fargate configuration
const cluster = new eks.Cluster("my-eks-cluster",{
vpcId: vpc.id,
privateSubnetIds: vpc.privateSubnetIds,
fargate:true,
});
//Export the cluster kubeconfig
export const kubeconfig= cluster.kubeconfig
It is creating all the resource , but "coredns connection refused error while setting up kubernetes cluster"
Steps to reproduce
pulumi-eks.zip
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
import * as eks from "@pulumi/eks";
import * as k8s from "@pulumi/kubernetes";
//Create a VPC with private and public subnets in all AZ's of the region
const vpc = new awsx.ec2.Vpc("my-vpc",{
cidrBlock: "<IP_ADDRESS>/16",
numberOfAvailabilityZones: "all",
});
//Create an EKS cluster with the fargate configuration
const cluster = new eks.Cluster("my-eks-cluster",{
vpcId: vpc.id,
privateSubnetIds: vpc.privateSubnetIds,
fargate:true,
});
//Export the cluster kubeconfig
export const kubeconfig= cluster.kubeconfig
Expected Behavior
To create a EKS-fargate cluster with coredns .
Actual Behavior
coredns connection refused error while setting up kubernetes cluster
error: Error: Command failed: kubectl patch deployment coredns -n kube-system --type json -p='[{"op":"replace","path":"/spec/template/metadata/annotations/eks.amazonaws.com~1compute-type","value":"fargate"}]'
Unable to connect to the server: net/http: TLS handshake timeout
Output of pulumi about
CLI
Version      3.50.2
Go Version   go1.19.4
Go Compiler  gc
Plugins
NAME        VERSION
aws         5.25.0
aws         5.16.2
docker      3.6.1
eks         1.0.1
kubernetes  3.23.1
nodejs      unknown
Host
OS       Microsoft Windows 10 Pro
Arch     x86_64
This project is written in nodejs: executable='C:\nodejs\node.exe' version='v18.12.1'
Additional context
Hoping to solve this issue as soon as possible.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

duplicate of pulumi/pulumi-eks#843


sfSymbol in react-native-bottom-tabs always displays as fill

Before submitting a new issue

[X] I tested using the latest version of the library, as the bug might be already fixed.
[X] I tested using a supported version of react native.
[X] I checked for possible duplicate issues, with possible answers.

Bug summary
I encountered an issue where the sfSymbol in the native-bottom-tab component always displays as a filled icon, rather than as an outline as expected.
Library version
0.7.6
Environment info
System:
  OS: macOS 15.3
  CPU: (8) arm64 Apple M3
  Memory: 119.64 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.2
      - iOS 18.2
      - macOS 15.2
      - tvOS 18.2
      - visionOS 2.2
      - watchOS 11.2
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 16.2/16C5023f
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 23.0.1
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.0
    wanted: 15.0.0
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.5
    wanted: 0.76.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: false

Steps to reproduce
create tab

Reproducible sample code
import HomeNavigator from './tab/home-navigator';
import type React from 'react';
import { createNativeBottomTabNavigator } from '@bottom-tabs/react-navigation';

const Tab = createNativeBottomTabNavigator();

const TabNavigator = (): React.ReactElement => {
  return (
    <Tab.Navigator>
      <Tab.Screen
        name="HomeNavigator"
        component={HomeNavigator}
        options={{
          tabBarLabel: 'Home',
          tabBarIcon: () => ({ sfSymbol: 'house' }),
        }}
      />
      <Tab.Screen
        name="HomeFillNavigator1"
        component={HomeNavigator}
        options={{
          tabBarLabel: 'Home Fill',
          tabBarIcon: () => ({ sfSymbol: 'house.fill' }),
        }}
      />
    </Tab.Navigator>
  );
};

export default TabNavigator;

display correct
import { SFSymbol } from 'react-native-sfsymbols';

  <SFSymbol
        name="house"
        size={16}
        resizeMode="center"
        color={'white'}
        style={{ width: 32, height: 32, marginTop: 384, marginLeft: 16 }}
      />

Hey! Thanks for opening the issue.
Can you check if this also happens on iOS? I will check a native visionOS App because Im not sure whether this is a limitation of visionOS to have always filled icons

@okwasniewski I just tested it on iOS, and it works perfectly fine there.

@kanapan I've tested it in both bottom tabs and my Native SwiftUI App and no matter what I do it's always filled. So it's probably something with visionOS that doesn't allow for non filled variants

I'm closing this since there is nothing we can do about it, sorry!


Use an updated image to speed up the tests

Is this okay? https://github.com/VirtusLab/intellij-pants-plugin-tests/pull/16/checks#step:5:292

Please update pants.conf to use pants from master of the original repo to see if it actually works.


Output transition matrix

The current version of episimlab doesn't save the transition matrix, which contains the information on incident infections, hospitalizations, deaths, etc.
Feature request is for addition of the tm attribute of ComptModel to the xarray output. https://github.com/UT-Covid/episimlab/blob/3ead2e8f0934094a829004d61a4314ed88e5c217/episimlab/compt_model.py#L26
@ethho I can take a stab at this if you can point me to the best way to add this to the xarray without breaking the application of edge weights.

Hi, @kellypierce, hope you're doing well!
If I understand your feature request correctly, this is already supported. You just need to specify tm as an output variable in the model:
https://github.com/UT-Covid/episimlab/blob/dbef34b8c4c92b3df898ee62e0f01b16f57b6bf1/examples/example_sir.py#L84-L86
and then you can access the tm at every timestep (this is the matrix just before it's added to the current state):
https://github.com/UT-Covid/episimlab/blob/dbef34b8c4c92b3df898ee62e0f01b16f57b6bf1/examples/example_sir.py#L110-L111
If you want to take snapshots of tm less frequently than every step, you could define another clock: https://xarray-simlab.readthedocs.io/en/latest/run_model.html?highlight=clock#create-a-new-setup-from-scratch

Perfect -- thanks @ethho !


[stable/mysqldump] Add subpath to mysqldump persistence

Signed-off-by: Kevin O'Neal<EMAIL_ADDRESS>
What this PR does / why we need it:
I'm storing backups from several databases to the same nfs volume. I'd like to be able to organize those by creating subPaths.
Which issue this PR fixes

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

@paulczar merge conflicts fixed!


Lack of indicators to track progress when installing extensions

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.91.1 (Universal)
OS Version: Darwin arm64 22.5.0

Steps to Reproduce:

Choose a new extension that has not been installed under Extensions.
Observe the lack of a progress tracker or loading bar that does not show how far the extensions has loaded.

Previously discussed in #76189

/duplicate


Updated launcher icons

@XuemingRocks I have updated ic_launcher-web.png

https://github.com/ArcGIS/runtime-example-apps/issues/84


Speed up candidate extraction on ORM branch

Latest update from @stephenbach : it seems like this might indeed be the SQLAlchemy constructor at the CandidateSpace stage... however, the whole point of the CandidateSpace is to never fully materialize all of the candidates.  So, we can just create temporary (non-ORM) objects here and then instantiate the actual ORM objects once they've passed through the matchers


Unable to add custom driver and Page crash

Hello @wow-blacksheep
Please provide more info about your OS.

This link can be helpful: https://stackoverflow.com/questions/2018553/swt-no-more-handles


Fix ucd-generate lazy_static dep

This updates the ucd-generate third party crate to use mainline lazy_static since it's no longer in third-party.

Oh! My fault. Thanks @nhynes !!


DLTdv: Minimum number of points for calibration

Dear Tyson,
Thank you very much for this great piece of code.
I’m trying to calibrate 3 cameras using 5 points only. I manage to initialize the calibration with a 5point calibration CSV file, I get the message ‘Loaded 5 point calibration object specification file’, but once I’m finished with the selection of the 5 points on the first camera, I cannot add the other camera images. The button ‘Initialize’ remains grey and does not change to “Add a camera” as when I have a 11 point calibration file instead.
Is there any reason for not allowing a calibration with 5 points only?
Do you see any  issue in making CSV file which points are duplicated in order to have (artificially) 11 points, e.g. {pt1, pt1, pt2, p2, p3, p3, p4, p4, p5, p5, p5} instead of {p1, p2, p3, p4, p5} ?
Version: Application for Mac (DLTdv8a_v8p2p3).
Kind regards,
Lionel

Hi Lionel,
5 points is actually not enough to compute the 11 DLT coefficients; you
need a minimum of 6 points. Duplicating some of the points to bring the
count up to 11 won't solve the underlying issue, though you may get a
more interesting error message! Probably the best option is to add 2 to
3 additional points that are at the midpoint of the line between some of
the pre-existing points, since you can probably identify that location
even if there is no marker. I'll see about adding a more informative
error message in a future version!
Does that make sense, or did I mis-interpret your issue?
Cheers,
Ty Hedrick
On 2/9/2022 11:51 AM, Lionel Feugère wrote:

Dear Tyson,
Thank you very much for this great piece of code.
I’m trying to calibrate 3 cameras using 5 points only. I manage to
initialize the calibration with a 5point calibration CSV file, I get
the message ‘Loaded 5 point calibration object specification file’,
but once I’m finished with the selection of the 5 points on the first
camera, I cannot add the other camera images. The button ‘Initialize’
remains grey and does not change to “Add a camera” as when I have a 11
point calibration file instead.
Is there any reason for not allowing a calibration with 5 points only?
Do you see any issue in making CSV file which points are duplicated in
order to have (artificially) 11 points, e.g. {pt1, pt1, pt2, p2, p3,
p3, p4, p4, p5, p5, p5} instead of {p1, p2, p3, p4, p5} ?
Version: Application for Mac (DLTdv8a_v8p2p3).
Kind regards,
Lionel
—
Reply to this email directly, view it on GitHub
https://github.com/tlhedrick/dltdv/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/APPXBCJ6HGXXCBHDIRLYQ4TU2KLRNANCNFSM5N6BYAPA.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this
thread.Message ID: @.***>


make GPU check fix

Per #705, an image with lots of bad masks will attempt to call torch.cuda.get_device_properties(0) in dynamics.remove_bad_flow_masks() without regard for the GPU status set by the use_gpu flag. @alix-simon 's fix is to check the flag in line 580.

Codecov Report

Merging #706 (de61b8b) into main (b709064) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #706      +/-   ##
==========================================
- Coverage   37.40%   37.38%   -0.02%
==========================================
  Files          20       20
  Lines        5355     5355
==========================================
- Hits         2003     2002       -1
- Misses       3352     3353       +1

Impacted Files
Coverage Δ

cellpose/dynamics.py
54.09% <100.00%> (ø)

... and 1 file with indirect coverage changes


fixes signal handling bug

Signed-off-by: Chuck Ha<EMAIL_ADDRESS>What this PR does / why we need it:
Fixes a signal handling bug.
Which issue(s) this PR fixes
No issue created
Special notes for your reviewer:
This is what I wanted to do originally.
When the worker gets a shutdown signal, it waits for $GRACEFUL_SHUTDOWN_PERIOD and then actually cleans up.
What it did before was simply sleep and block the main thread then exit.
Release note:
release-note

logs showing this works:
$ docker logs -f 6ba4c22e23ab
time="2018-03-14T16:10:20Z" level=info msg="Waiting for waitfile" waitfile=/tmp/results/done
time="2018-03-14T16:12:17Z" level=info msg="got a signal, waiting then sending the real shutdown signal" signal=terminated
time="2018-03-14T16:12:24Z" level=info msg="Detected done file, transmitting result file" resultFile=/tmp/results/e2e.tar.gz


feat: add optional filter input to component:select

Proposed changes
In case of long list of options in select field, it might be easier to quickly filter items by text. While current v1-dev branch does contain some filtering, it's not as helpful visually for users.
This change adds optional (available only when data-filtered="placeholder text" attribute is set on select element) input field, that allows user to see what he or she enters while trying to filter the list of items.
Additionally, items that do not match the text become hidden (class hide is added on li elements).
Changes were sponsored by Egmont Group.
Screenshots (if appropriate) or codepen:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[x] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Hi, quick question do i actually have to make the feature i want to request?

No
On Sat, May 26, 2018 at 2:39 PM Charbel Sarkis<EMAIL_ADDRESS>wrote:

Hi, quick question do i actually have to make the feature i want to
request?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Dogfalo/materialize/pull/5943#issuecomment-392289733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpax_VTn5cU0HzteXajlE01UgO4wuP0ks5t2cudgaJpZM4UMDjn
.

--
Doggy sends his greetings from Mars.

Great. Can you add custom validation. Exactly like the validation class but
the user can supply an attribute data-regex to tell it when to succeed and fail.

@Dogfalo hi, now that totally off topic stuff has been resolved, is there any chance for a comment about the pull request :)? Does it need more changes in code to be accepted, or maybe it won't be accepted because it adds too big of a change, or complicates component a bit, or... ?

We're not adding any more features since we're in release candidate build

@Dogfalo thanks for the answer. Do you think this feature could be merged post-1.0 release?

Yes, it seems useful and code is organized

Great! Thanks.

@Dogfalo i updated to latest dev branch and fixed test. Any chance it could be merged now?

@Dogfalo @acburst any chance this could be merged? If not, i can just close this and stop wasting your time :).

Hmm if you want, you can send your pull request to the forked one instead https://github.com/materializecss/materialize 😉


Crash Code<PHONE_NUMBER>  on starting Nodejs project

VSCode Version: Latest VS Code (1.18.1) and Insider Release 1.19.0 (tested with both)
OS Version: Win 10

Steps to Reproduce:

Open Nodejs project
2.Start with F5
Crash

The project worked until yesterday perfectly in VS...changed nothing in launch config or installed/uninstalled any extensions since then
launch config
    {
          "type": "node",
          "request": "launch",
          "name": "Launch Program",
          "program": "${workspaceFolder}\\bin\\www"
      },

Reproduces without extensions: Yes/No => disabled all extensions. Clean install of insider release (without any extension). Both crash on starting the nodejs project
Insider Release

VS Code 1.18.1

Does it help if you restart your computer?

3221225477 shown in HEX is 0xC0000005 which is a STATUS_ACCESS_VIOLATION code on Windows.
@alexandrudima @jrieken does this ring a bell?

@weinand
Restart didn't change anything. Still error occurs

I have another project (Angular 5 with Anuglar Cli). If I try to start this one directly from VS Code the same error occurs.
So it seems that it does not depend on the project type. In Angular Cli there is a nodejs script implemented, but the error immediately hits after pressing F5 in VS Code, no console output or anything but the error messages from dev console I've already posted. If I can do anything (providing logs or anything else let me know)

@Skuriles Can you try adding this "git.decorations.enabled": false, to your settings file?

Will try it as soon as I'm back home

@jrieken
Tried it in both (insider and normal VS Code) without success (restarted PC => tried again).
Still get exact the same error

Ok... Next try: Please start from the command line with the --inspect-brk-extensions=9334 option. Then open Developer Tools and check the console for a chrome-dev-tools URL. Open that in Chrome and it should be the extension host process in debug mode. Enable break on errors/uncaught error and  resume the process. If it's a problem in JS-land you should now see it.

Hm.. I've started it like you said. It breaks on some promise rejects (git not found) but no exceptions as far as I can see.
If I start it in this mode and press F5 to run the application it works!!
If I re-start it "normal" it still rejects launch.
I've already updated Git to latest version and even tried to ""git.enabled": false," but still same problem.. really strange
I will attach all errors the debugger breaks on

There are a few more (think this are following errors, if you need more, I will add everything)

Just remark: I used Git before without any problems in this project.

I used Git before without any problems in this project.

A rejected promise doesn't mean git doesn't work. It's part of the discovery and more a bug in the debugger as those errors are usually handled. @Skuriles Please continue the break on error walk until the last error before crashing

As I said: The problem is that the debugger stops at this rejected promises on startup. But then Visual Studio Code works as long as I start it with --inspect-brk-extensions=9334 parameters.
So there are no errors if I press F5 to launch the project.
I will try to re-do my tests this afternoon and check if there are any breaks on launching the projects.
Feels a little bit like a caching/timing problem which is resolved by open the dev tools in a web app :-)
If I start VS Code without these parameters I can't start the project with F5

Also try with latest insiders please. thanks

@Skuriles to avoid stopping on rejected promises just uncheck the exception options in the Breakpoints view:

Tried with latest insider version:
If I start it with --inspect-brk-extensions=9334 parameters it works, same as in 1.18.1. The only thing is a warning in dev tools if I start the app ("Message Debugging with inspector protocol because Node.js {0} was detected. didn't get externalized correctly...").
As you can see it is running.:

The dev tools I've opened in Chrome show nothing and don't break on any exception
In 1.18.1 it is exactly the same behavior (works with parameters, crashes without):

Dev Tools show this warning. Dev Tools opened in Chrome show nothing
Starting without parameters shows this

Funky... @bpasero You had crash insights and how they are logged on windows, right?

@jrieken yeah lately I had some luck in getting core dumps when installing Debug Diagnostic Tool: https://www.microsoft.com/en-us/download/details.aspx?id=49924
When started it allows to stop on exception on a process (you can pick it). If you are lucky, a core dump is being produced with more data.
Alternatively you could also try to attach to the process with VS which should basically do the same thing when it crashes. But for users it may be easier to go with the debug diagnostic tools.

@Skuriles See https://github.com/Microsoft/vscode/issues/39818#issuecomment-350286739. Thanks

@bpasero
As I never used this tool: Is there a step-by-step manual how to use it with VS Code?
I found some old ones, but not for the latest 2.0 or I just don't get it. I can only analyse dmp files, but how to get them for VS Code?

@Skuriles see https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues#windows

Oh my bad. I searched for the tool in windows search and just found the analyser :-b
Report file created form the analyser tool:
report.zip
I can also provide the complete dump file but it is 83 mb. Shall I upload it anywhere?

@Skuriles that file has a weird ending, are you sure you attached the right thing? It looks like a multi part message.

This is the report file extracted from the created dump files with MS Debug Tool analyser.
I can perfectly read it in browser.
As I said, I can upload the whole dump file, but Git threw errors (think 83 MB were too big) so I can't upload it here

@Skuriles yeah I see it now.
The stack seems to be this:
ntdll!RtlDispatchException+104
ntdll!KiUserExceptionDispatch+2e
ucrtbase!wcsncpy+3c
node!uv_tty_set_mode+247d
node!uv_tty_set_mode+1fe0
node!uv_tty_set_mode+230e
node!uv_spawn+278
node!v8::HeapStatistics::total_physical_size+76b7
node!v8::HeapStatistics::total_physical_size+7340
node!v8::HeapStatistics::total_physical_size+7471
node!v8::internal::AllocationSpaceName+12cf0
node!v8::internal::Builtins::WasmStackGuard+27f2
node!v8::internal::Builtins::WasmStackGuard+2be1
node!v8::internal::Builtins::WasmStackGuard+2a2b

I cannot remember seeing something like that before though.

Looks like it crashes when spawning a process... (uv_spawn)

Let me know if you need more information about my system or any other information

@Skuriles are you able to reproduce with this insiders build that is using a new node.js version: https://az764295.vo.msecnd.net/exploration/395608d787740e20d207d278c4d1494995a719a9/VSCode-win32-x64-1.22.0-exploration.zip ?

@bpasero There were some minor issues with the 1.21 (or a late 1.20) but since then everything seems to work again (with stable and insider). Sorry, forgot to mention that here!
I will try the new insider version today at home but I've working with 1.21 for the few last days/weeks without any issues concerning this bug.
So I think we can close it!


Add cordova as an environment

Add Cordova (http://cordova.apache.org/docs/en/3.4.0/)
http://www.jshint.com/docs/options/#environments

This would be really helpful!


Offscreen demo appears to have reversed reflection

When the lit side of the dragon is visible, the reflection is very dark.
When the dark side of the dragon is visible, the reflection is very bright.

Thx for pointing this out. Looks like I forgot (or accidentally removed) the line to switch cull mode (only a comment is there, but no code).


replacing MoveToMap hardcoded min time config for chasing pokemon w…

Short Description:

replacing MoveToMap hardcoded min time config for chasing pokemon with more sophisticated decision whether the destination is reachable with current walk speed in time

thanks will check and debug


Argument 1 passed to craft\elements\db\ElementQuery::enabledForSite() must be of the type bool, null given

As of Craft CMS v<IP_ADDRESS> while using the current version of the plugin available through this repo, I am seeing an error returned when attempting to add an entry to a Many to Many field.
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
/index.php?p=admin/actions/element-indexes/get-elements&v=1582172064925:1

error: "Argument 1 passed to craft\elements\db\ElementQuery::enabledForSite() must be of the type bool, null given, called in ~/vendor/craftcms/cms/src/elements/db/ElementQuery.php on line 516"

Application Info
PHP version	7.3.14
OS version	Linux 3.10.0-957.27.2.el7.x86_64
Database driver & version	MySQL 5.7.29
Image driver & version	GD 7.3.14
Craft edition & version	Craft Pro <IP_ADDRESS>

Updated because I was clicking through and the error I saw before was incorrect due to direct access of the endpoint.

This can be corrected by updating line 10 in input.js to:
criteria: {status: null, localeEnabled: false},

localeEnabled is actually deprecated so it should be:
criteria: {status: null, enabledForSite: false},

Fixed in 2.0.0


strings.pad

Pads string on the left and right sides if it's shorter than length. Padding characters are truncated if they can't be evenly divided by length.
Checklist

[x] implementation
[x] tests
[x] jsdoc

Details

console.log(strings.pad('abcabc', 9));
> ' abcabc  '

console.log(strings.pad('abcabc', 15, '_-+'));
> ' _-+_abcabc_-+_-'

References

_.pad

Added in 0.71


mullvad-browser: 12.5.5 -> 12.5.6

Description of changes
Equivalent Tor Browser release (#258116):
https://blog.torproject.org/new-release-tor-browser-1256/
Security update:

Bug tor-browser#42135: Backport security fixes from Firefox 115.3.1 to 102.15.1
Bug tor-browser-build#40957: Update subkey expiration date for Tor Browser gpg key

Adding some new mirrors to the list of source urls.
The newly added torproject.org sources actually have the 12.5.6 release already before the Mulvlad website & GitHub releases:
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] 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.

@mweinelt that was quick 😅


Add Proxy functionality via Traefik lib

Proposal
We should have our own proxy command that allows us to run Traefik via library.
Background
Running our own Traefik instance can give us a lot of flexibility and customization options

I have heard tales that this is the file that makes the magic happen:
https://github.com/containous/traefik/blob/master/cmd/traefik/traefik.go


Provision to set Log Dir

An additional method to set log Directory (instead of setting via log_dir flag)

@googlebot  I signed it!


[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: FormatException: Unexpected end of input (at character 1)

In the provided example code, i am getting following error:
E/flutter ( 9562): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: FormatException: Unexpected end of input (at character 1)
E/flutter ( 9562):
E/flutter ( 9562): ^
E/flutter ( 9562):
E/flutter ( 9562): #0      _ChunkedJsonParser.fail (dart:convert-patch/convert_patch.dart:1465:5)
E/flutter ( 9562): #1      _ChunkedJsonParser.close (dart:convert-patch/convert_patch.dart:499:7)
E/flutter ( 9562): #2      _parseJson (dart:convert-patch/convert_patch.dart:37:10)
E/flutter ( 9562): #3      JsonDecoder.convert (dart:convert/json.dart:610:36)
E/flutter ( 9562): #4      JsonCodec.decode (dart:convert/json.dart:216:41)
E/flutter ( 9562): #5      PaylinkAPI.addInvoice (package:paylink_payment/api/paylink_api.dart:161:33)
E/flutter ( 9562):
E/flutter ( 9562): #6      _PaylinkTestPageState.addPendingInvoiceForTesting. (package:example/presentation/pages/paylink_test_page.dart:186:11)
E/flutter ( 9562):
E/flutter ( 9562):
This error occurs when following line of code executed:
paylink.addInvoice(
amount: 180.0,
clientMobile: '0512345678',
clientName: 'Mohammed',
orderNumber: '1234567899',
callBackUrl: 'https://example.com',
products: [],
).then(
(invoiceDetails) => addInvoiceToList(invoiceDetails, false),
);
and the "PaylinkAPI.addInvoice (package:paylink_payment/api/paylink_api.dart:161:33)" points to
final orderDetails = json.decode(response.body);

The issue does not lie within the package itself; however, to handle additional cases, we’ve implemented some improvements in the new version (2.0.2):

Removed the late keyword from idToken to address initialization issues.
Added a check for empty responses to ensure proper handling when response.body is empty.

These changes should help resolve the issue you’re encountering.


upgrade to getdown 1.6.2

support for two digest files.

@rockfireredmoon Are you going to update the maven repo (the mvn branch)? Thanks!

Hi Renato, sorry for the long wait. Version 0.0.2-SNAPSHOT is now there with this fix. I am actively using this project again so it's likely to get slightly timelier updates in the future.


[ComplexImageView] setVisualizationMode should accept string

Only an object is accepted now what makes things cumbersome. One has to call getSupportedVisualizationModes and select the appropriate index (4 in case of willing 'Amplitude and Phase' instead of just passing the string)

Looking at it, the Mode are available in the ComplexImageView class, so there is no need to import them from the complex image item module.
Sample code:
from silx.gui.plot.ComplexImageView import ComplexImageView

widget = ComplexImageView()
widget.setVisualizationMode(widget.Mode.AMPLITUDE_PHASE)
# or
widget.setVisualizationMode(ComplexImageView.Mode.AMPLITUDE_PHASE)
widget.show()

We can update the documentation of setVisualizationMode with sample code, but I would leave it as it is.

OK. Waiting for the tests to finish.

closed by #2423


FeatureRequest: Close a tab

Just an X on the end of the tab so it can be closed from an overview.

Interesting, thanks

Will be in next release


crevice derive macro: fix path to render_resource when importing from bevy

Objective

Fix #3436

Solution

Do not add twice render_resource when coming from bevy

bors r+