Array parameters with default values

There seems to be an issue with default parameters when used in combination with arrays. I've added the following to the test-case swagger:
  /hello_w_default_array:
    x-swagger-router-controller: hello_world
    get:
      description: Returns 'Hello' to the caller
      operationId: hello_array
      parameters:
        - name: names
          in: query
          description: The names of the people to whom to say hello
          default: ["Tom", "Maria"]
          type: array
          items:
            type: string
          collectionFormat: csv

The test code in /tests/lib/common.js:
    it('should execute with default names', function(done) {
      request(this.app)
        .get('/hello_w_default_array')
        .set('Accept', 'application/json')
        .expect(200)
        .expect('Content-Type', /json/)
        .end(function(err, res) {
          should.not.exist(err);
          res.body.should.eql('Hello, Tom and Maria');
          done();
        });
    });

and the added function to the hello_world.js is:
...
  hello_array: hello_array,
...

function hello_array(req, res) {
  var hello = 'Hello';
  console.log(req.swagger)
  var names = req.swagger.params.names.value
  for (let n =0; n < names.length; n ++) {
    if (names.hasOwnProperty(n)) {
      if ((n + 1) === names.length){
        hello += " and "
      }else {
        hello += ", "
      }
      hello += names[n]
    }
  }
  res.json(hello);
}

And mocha test/lib/connect_middleware.js -g "with default names" fails with:
  1) connect_middleware standard controllers should execute with default names:
     Uncaught AssertionError: expected Error { message: 'expected 200 "OK", got 400 "Bad Request"' } to not exist
      at Test.<anonymous> (test/lib/common.js:72:22)
      at Test.assert (node_modules/supertest/lib/test.js:156:6)
      at Server.assert (node_modules/supertest/lib/test.js:127:12)
      at emitCloseNT (net.js:1521:8)

If I add a required: false the hello_array is properly identified but the names property is empty as if the default parameters are ignored. This could possibly be a upstream bug in sway as there seems to be an issue with how default arrays are passed. I think the package should have tests for default values so I've added them (see pull request) and therefore started reporting the issue here.

Thanks, @gforge! I appreciate the detailed report and test case!

I found an additional related annoyance, the swagger editor used to set parameters to hello_world?param1=&param2=value. I'm not sure if the param1= should be an acceptable query spec but it behaves different depending on the variable type and this probably not intentional. When param1 is a string it will pass an empty string to the function while if it is defined as an integer there will be a Bad Request issued. Here's the yaml section illustrating the issue:
    get:
      description: Returns 'Hello' to the caller
      operationId: hello
      parameters:
        - name: name
          in: query
          description: The name of the person to whom to say hello
          default: "no stranger"
          type: string
        - name: id
          in: query
          description: The ID of a person
          default: 0
          type: integer

The tests to cause the issue to trigger are:
    it('if a parameter is specified as param= then is should go to default for a string', function(done) {
      request(this.app)
        .get('/hello_w_default?name=&id=1')
        .set('Accept', 'application/json')
        .expect(200)
        .expect('Content-Type', /json/)
        .end(function(err, res) {
          should.not.exist(err);
          res.body.should.eql('Hello, no stranger!');
          done();
        });
    });

    it('if a parameter is specified as param= then is should go to default for an integer', function(done) {
      request(this.app)
        .get('/hello_w_default?name=Mary&id=')
        .set('Accept', 'application/json')
        .expect(200)
        .expect('Content-Type', /json/)
        .end(function(err, res) {
          should.not.exist(err);
          res.body.should.eql('Hello, Mary!');
          done();
        });
    });

And the errors that these cause are:
 1) express_middleware standard controllers if a parameter is specified as param= then is should go to default for a string:

      Uncaught AssertionError: expected 'Hello, stranger!' to equal 'Hello, no stranger!'
      + expected - actual

      -Hello, stranger!
      +Hello, no stranger!

      at Assertion.fail (node_modules/should/lib/assertion.js:180:17)
      at Assertion.prop.value (node_modules/should/lib/assertion.js:65:17)
      at Test.<anonymous> (test/lib/common.js:60:27)
      at Test.assert (node_modules/supertest/lib/test.js:156:6)
      at Server.assert (node_modules/supertest/lib/test.js:127:12)
      at emitCloseNT (net.js:1524:8)

  2) express_middleware standard controllers if a parameter is specified as param= then is should go to default for a string:
     Uncaught AssertionError: expected Error { message: 'expected 200 "OK", got 400 "Bad Request"' } to not exist
      at Test.<anonymous> (test/lib/common.js:72:22)
      at Test.assert (node_modules/supertest/lib/test.js:156:6)
      at Server.assert (node_modules/supertest/lib/test.js:127:12)
      at emitCloseNT (net.js:1524:8)

Again this could be an issue residing outside the swagger-node-runner, after some node-inspector debugging I think the problem is that when sway does its ParameterValue the default value isn't available at the validation since the value isn't found to be undefined. Not sure how to best solve this as ignoring empty query variables will inhibit the option of passing an empty string. Interfering at the params parser feels generally like a bad idea.


pyAutomagic for automatic EEG preprocessing and quality assessment

What does this implement/fix?
There is a need for automatic and replicable preprocessing and evaluation of data quality in EEG to increase transparency in the field. A package for this purpose, Automagic, was developed in Matlab (https://github.com/methlabUZH/automagic) by @nickilanger. It provides the user an easy way to set preprocessing and quality evaluation parameters for an entire project, and automatically execute. The quality metrics used are all based on variance of some type in the data, and these metrics are used to give each recording a rating of "good", "ok", or "bad". All results, figures, and log files, are then saved.
Proposed solution
The suggested solution, pyAutomagic, is the movement of Automagic's functionality to python, specifically compatible with mne-python and mne-bids. The outcome would be a repository in mne-tools.
In addition, a solution would include:

some documentation for reference on what functions do, and meta-summary of the pipeline
some tutorials on how to run full pipeline, sub-parts of the pipeline, and then example analysis at the end
design change(s) summary compared to Automagic.
The package would be tested to the same validation dataset used for the original Automagic package (https://osf.io/5e74x/files/).

Additional information
More info on the original (MATLAB) package functionality can be found in the paper published (https://www.biorxiv.org/content/10.1101/460469v3.full).
@adam2392

A good first step would be to create a separate repo (maybe owned by methlabUZH?) for this, similar to autoreject. Once it's up and running and working, we can figure out when/how to port over to MNE, but in the meantime people can try it out for example with pip install pyAutomagic or so.


Support partitioned checkpoint

To improve our checkpoint strategy, we decide to support checkpoint in MView granularity with configurable consistency. In other words, each MView can complete its checkpoint independently.

[ ] Introduce hummock group in hummock manager to track MaxCommittedEpoch (MCE) of each MView
[ ] Support reads/writes with hummock group
[ ] Support group based barrier injection/collection and epoch commit
[ ] Support group based failover

Discussion:

How to ensure query consistency after failover (rollback MCE or not? If not, frontend waits or storage waits?)

Tracked by https://github.com/risingwavelabs/risingwave/issues/14041


Proposed ProGuard keep rules are extremely broad (== bad)

The article mentions "the most basic example of ensuring your library classes are exported" as including
-keep public class * {
    public protected *;
}

... these are very imprecise keep rules which will undermine the effectiveness of ProGuard across the rest of any app that includes this library. Even presenting the rules here as a viable option may be doing harm for library developers and the consumers of those libraries.

Helpful feedback Ken, thanks for raising this issue here. Would appreciate if anyone seeing this issue is interested in helping contribute changes to the guide that makes it more accurate. All of the content is community-driven.


Errors with Banner style image

Imported a medium-large size banner image, with mask.
On exporting as PlusMask format, data is totally garbled. Exporting as ExternalMask mask is offset to the right by 1-2px. Edit: Human error. The exported data is fine.
After exporting, on clicking into the editor area- crash! Unhandled exception:
System.ArgumentOutOfRangeException: Parameter must be positive and < Height.
Parameter name: y

Note: The editor window isn't scaling up the pixels to fill the viewable area.

I believe the problem you are describing is the one that #11 has just fixed.
I can't tell for definite without the full stack frame (the one that would have been dumped in the log file), but the error message is similar so I suspect it's likely.

I'm going to go out on a limb and assume #11 fixes this.
If v0.1.2 doesn't fix this, I'll reopen the issue.

Seems fixed in current version. Thanks 👍


bug in purchase bills

[x] not able to create purchase bill (it showing date field may not be null)
[x] while creating new bill ,bill number showing "NEW"
[x] while select supplier name place of supply is not filled by default
[x] edit not working fine
[x] clone not functioning
[x] approve button not functioning
[x] reject not functioning
[x] convert bill to create purchase return not functioning and purchase return credit number not populated
[x] record payment
[x] create vendor credit/purchase return
[x] sort not working -name
[x]  sort not working - due date ,created time ,last modified time
[x] advance search is not functioning
[x] search using date not working
[x] response message for crud
[x] while creating bill it showing(paid amount a valid number is required) -actually user can create bill without input amount
[x] in edit page data not auto populated - reference , terms and notes
[ ]

issue closed


netbird up fails after netbird down

Describe the problem
Ran netbird down followed by netbird up on a RasPi running Linux/Debian 12.  the up command failed with the errors:
$ netbird up
2024-02-23T16:01:09Z WARN client/cmd/root.go:195: retrying Login to the Management service in 1.127617486s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
2024-02-23T16:01:20Z WARN client/cmd/root.go:195: retrying Login to the Management service in 2.043948863s due to error rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

I diagnosed the root cause for this as being netbird up modified the /etc/resolv.conf file, but netbird down did not restore the original list of nameserver entries.  Basically, the NetBird DNS server is not available when NetBird is down and so DNS resolution is failing.  Manually editing the file and commenting out the line reading nameserver <IP_ADDRESS> fixed the issue.
To Reproduce
See above.
Expected behavior
netbird up succeeds
Are you using NetBird Cloud?
Yes.
NetBird version
0.25.7
NetBird status -d output:
If applicable, add the `netbird status -d' command output.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi, could you run some tests, please? While you are connected to management can you run the following commands and send me the output:

sudo ls -l /var/lib/netbird
sudo cat /var/lib/netbird/manager
sudo ls -l /var/lib/netbird/resolv.conf
sudo ls -l /etc/resolv*

Thanks!

root@raspi-blue:~# ls -l /var/lib/netbird
total 8
-rw-r--r-- 1 root root 19 Feb 28 01:33 manager
-rw-r--r-- 1 root root 79 Feb 28 01:33 resolv.conf
root@raspi-blue:~#
root@raspi-blue:~#
root@raspi-blue:~# cat /var/lib/netbird/manager
file,<IP_ADDRESS>root@raspi-blue:~#
root@raspi-blue:~#
root@raspi-blue:~# ls -l /var/lib/netbird/resolv.conf
-rw-r--r-- 1 root root 79 Feb 28 01:33 /var/lib/netbird/resolv.conf
root@raspi-blue:~#
root@raspi-blue:~#
root@raspi-blue:~# ls -l /etc/resolv*
-rw-r--r-- 1 root root 217 Feb 28 01:33 /etc/resolv.conf
-rw-r--r-- 1 root root  79 Feb 28 01:25 /etc/resolv.conf.original.netbird

I'm currently having the exact same error on Linux machines when i try to use a Setup Key.
Windows PCs can login with SSO, but takes a while and a couple of reconnects.
I'm running self-hosted version where everything but the Reverse-Proxy runs in docker containers.
I Use nginx as reverse-proxy:
upstream dashboard {
  server <IP_ADDRESS>:8180;
  keepalive 10;
}

upstream signal {
  server <IP_ADDRESS>:8100;
}

upstream api {
  server <IP_ADDRESS>:8443;
}

upstream management {
  server <IP_ADDRESS>:8443;
}

server {
    listen 80;
    server_name _;

  # 301 redirect to HTTPS
    location / {
      return 301 https://$host$request_uri;
    }

}

server {
    # HTTPS server config
    listen 443 ssl http2;
    server_name _;
    access_log /var/log/nginx/access.log;
    client_header_timeout 1d;
    client_body_timeout 1d;

    proxy_set_header        X-Real-IP $remote_addr;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Scheme $scheme;
    proxy_set_header        X-Forwarded-Proto https;
    proxy_set_header        X-Forwarded-Host $host;

    # Proxy dashboard
    location / {
        proxy_pass http://dashboard;
    }

    # Proxy Signal
    location /signalexchange.SignalExchange/ {
        grpc_pass grpc://signal;
        #grpc_ssl_verify off;
        grpc_read_timeout 1d;
        grpc_send_timeout 1d;
        grpc_socket_keepalive on;
    }
    # Proxy Management http endpoint
    location /api {
        proxy_pass http://api;
        proxy_set_header        X-Real-IP $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Scheme $scheme;
        proxy_set_header        X-Forwarded-Proto https;
        proxy_set_header        X-Forwarded-Host $host;
        proxy_http_version 1.1;
    }
    # Proxy Management grpc endpoint
    location /management.ManagementService/ {
        grpc_pass grpc://management;
        #grpc_ssl_verify off;
        grpc_read_timeout 1d;
        grpc_send_timeout 1d;
        grpc_socket_keepalive on;
    }

    ssl_certificate /etc/nginx/certs/cert.crt;
    ssl_certificate_key /etc/nginx/certs/cert.key;
    ```

I doubt that it matters, but my device is also using a setup key and not SSO.

Mine does not come up at all (new client) so it's not the exact same scenario, but I'm thinking it has something to do with Linux Client and Setup Keys.
Windows Clients seems to be working as normal, the take a good time to connect which I'm also investigating.

$ curl -o /dev/null -s -w "Time Connect: %{time_connect}s\nTime Start Transfer: %{time_starttransfer}s\nTotal Time: %{time_total}s\n" https://api.netbird.io/api/users
Time Connect: 0.084451s
Time Start Transfer: 0.426194s
Total Time: 0.426519s

Hello @synfinatic @teoder, The context deadline error indicates some timeout when communicating with the management service. The client have a timeout of 5 seconds which will be increased to 10 seconds with the next release (0.26.3).
Can you send the output from:
curl -o /dev/null -s -w "Time Connect: %{time_connect}s\nTime Start Transfer: %{time_starttransfer}s\nTotal Time: %{time_total}s\n" https://api.netbird.io/api/users

@teoder, replace https://api.netbird.io with your self-hosted management URL.
Also, can you please send us the logs from the daemon process? see https://docs.netbird.io/how-to/troubleshooting-client#getting-client-logs for reference.

So I think I've narrowed my problem down to the /api part of the nginx reverse-proxy, that section is not getting any access-requests...
Do you think this could be related to me using the same fqdn for the API and Management section? I mean, I could always move this to another fqdn like api.domain.nu

Can you share your nginx configuration?

No, the management service is the API. Often we see some configs missing grpc_pass parameters for the management protocol.
Can you share your nginx configuration?

Here it is:
upstream dashboard {
  server <IP_ADDRESS>:8180;
  keepalive 10;
}

upstream signal {
  server <IP_ADDRESS>:8100;
}

upstream api {
  server <IP_ADDRESS>:8443;
}

upstream management {
  server <IP_ADDRESS>:8443;
}

server {
    listen 80;
    server_name _;

  # 301 redirect to HTTPS
    location / {
      return 301 https://$host$request_uri;
    }

}

server {
    listen 80;
    server_name _;

  # 301 redirect to HTTPS
    location / {
      return 301 https://$host$request_uri;
    }

}

server {
    # HTTPS server config
    listen 443 ssl http2;
    server_name _;
    access_log /var/log/nginx/access.log;
    client_header_timeout 1d;
    client_body_timeout 1d;

    proxy_set_header        X-Real-IP $remote_addr;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Scheme $scheme;
    proxy_set_header        X-Forwarded-Proto https;
    proxy_set_header        X-Forwarded-Host $host;

    # Proxy dashboard
    location / {
        proxy_pass http://dashboard;
    }

    # Proxy Signal
    location /signalexchange.SignalExchange/ {
        grpc_pass grpc://signal;
        #grpc_ssl_verify off;
        grpc_read_timeout 1d;
        grpc_send_timeout 1d;
        grpc_socket_keepalive on;
    }
    # Proxy Management http endpoint
    location /api {
        proxy_pass http://api;
        proxy_set_header        X-Real-IP $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Scheme $scheme;
        proxy_set_header        X-Forwarded-Proto https;
        proxy_set_header        X-Forwarded-Host $host;
        proxy_http_version 1.1;
    }
    # Proxy Management grpc endpoint
    location /management.ManagementService/ {
        grpc_pass grpc://management;
        #grpc_ssl_verify off;
        grpc_read_timeout 1d;
        grpc_send_timeout 1d;
        grpc_socket_keepalive on;
    }

    ssl_certificate /etc/nginx/certs/cert.crt;
    ssl_certificate_key /etc/nginx/certs/cert.key;

So, In my case this problem was due to untrusted Let's Encrypt root certificate on the Linux host.
I added the certificates to /etc/ssl/certs/ca-certificates.crt and I could connect without issues.


User/shayaksarkar/reorderlvcreation

Problem
Merge the code for <IP_ADDRESS> release in sdaf. This release contains a fix that plagues single server installations due to the faulty order of the lv creation within vg_sap. lv_usrsapinstall was being created before the other lvs which was resulting in the entire space allocated to the vg_sap being allocated to the lv_usrsapinstall. This was failing the other lv creations.
Solution
lv_usrsapinstall creation is now made the last lv created so that all remaining space is allocated to it post the creation of lv_sapmnt and lv_usrsap.
Tests
Deploy single server systems using by the sdaf release <IP_ADDRESS> from ACSS portal. The create infra procedure should succeed.
Proof of Testing
Query to view the results for createinfra test:
https://waasservices.eastus.kusto.windows.net/WaaSKustoDB?query=H4sIAAAAAAAEAG2RTUsDQQyG7%2FsrwpwqbGFZQUGpILXCHvzAFXoQD2kmtaO7M0sm21Lwxzur0A8qzCFD3id5k8wR6wdWcTRbs9fsGzYrFoZnYXKRX13LtWLbwQ1YVNb0H5VFeT4uLsblJRTF1e8724F1v4gkrlMXfGXBeRhVXlk8NoepuCdeOIZeiJOagld0PoJBuwpkdpq71NfHgXsz8yBfyyZsHrFl8w6TCZipcDJX%2BaVgVOlJe%2BH%2F4aeOBQcDaSod8MGgqXsiZsvW5GDu0TUpGgx2Ej6Z9GQb%2BVHNmUiQabD85yiHmmXtiG9J3drptrL5wZBD%2FJHAHPb51CqIZYHF9kh5cgWMdJ1lP74BzVW1AQAA&web=0
WaaSMetricEvent
| where PreciseTimeStamp > datetime(2023-06-27 00:00:00)
| where SubscriptionId in (InternalSubscriptions)
| where ResourceId contains "adhoc"
| where Dimensions["WorkflowName"] == "CreateInfrastructure"
| where Dimensions["OperationState"] in ("Succeeded", "Failed")
| project PreciseTimeStamp, Dimensions["ErrorCodeName"], ServiceActivityId, ResourceId, Region, ActivityId
| order by ResourceId, PreciseTimeStamp asc;
Query to view the results for install test:
https://waasservices.eastus.kusto.windows.net/WaaSKustoDB?query=H4sIAAAAAAAEAG2RTUsDMRCG7%2FsrhpwqbGFZQUGpIFphD37gCj2Ih2ky2mg2WSazWwr%2BeBOFflAhhwnv%2B%2BSdmSwQ23sStno%2BkpfiG9YrYoInJm0jvdiOWsGuhyswKCTpPqmr%2BnRanU3rc6iqi99zsgXbYRk1215s8I0B62HSeCH26PaluCOeKYaBNSW3Dl7Q%2BggKzSpotfXcplwfM%2FeqFoG%2F3l1YP2BH6g1mM1CNj4LOZcUFNP9zjz0x5uw0kGQy96baQWsiQ0aVoO7QulTl3noOn6TlaBHlwZtz5sA3wdBfMyW0xKPVdK3FjlY2jSn35sv1RwJL2OkpKrAhhuXmwHn0ARj1ZVH8AGqZJGKwAQAA&web=0
WaaSMetricEvent
| where PreciseTimeStamp > datetime(2023-06-27 00:00:00)
| where SubscriptionId in (InternalSubscriptions)
| where ResourceId contains "adhoc"
| where Dimensions["WorkflowName"] == "InstallWorkload"
| where Dimensions["OperationState"] in ("Succeeded", "Failed")
| project PreciseTimeStamp, Dimensions["ErrorCodeName"], ServiceActivityId, ResourceId, Region, ActivityId
| order by ResourceId, PreciseTimeStamp asc;
1 SCS failure observed which was transient and succeeded on retry
These are the other errors observed which are not related to ansible:
InstallHostUnreachable
InstallServiceError
AzureVMIsNotInSupportedProvisioningState

Closing this PR since this change does not fix the issue. The sapinstall logical volume creation needs to be done at the very end for robust volume group setup. Will raise a PR for this shortly.


Force latest version of worker-farm

Summary
This ensures compatibility with the incoming node@9 (expected today or tomorrow).
See #4731 and linked issues

Test plan
Still green CI, can test with node rc locally as well.

yap.


Windows installer refuses to use XAMPP's PHP 7.4.5

I have a portable installation of XAMPP set up. Its php.exe is in my PATH. When I attempted to run Composer-Setup.exe, it correctly found php.exe, but then gave this error:

As far as I can tell, php.exe is fine - most of Composer's manual installation instructions worked, as I described in composer/composer#8883, and I got this output from running php.exe --version:
PHP 7.4.5 (cli) (built: Apr 14 2020 16:17:34) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

@PixievoltNo1 Could you supply a log file please, as per the instructions here: https://github.com/composer/windows-setup/issues/new
Thanks.

Here it is: Setup Log 2020-05-08 #001.txt

Thanks for the log. I downloaded xampp and was able to reproduce the error.
But when I ran ... \xampp\php\php.exe -v from cmd, I got a whole bunch of error output, so you must have been running a different php, probably  ... \xampp\php\windowsXamppPhp\php
Sorry, I don't know enough about xampp to know which php you should be running for CLI, but ... \xampp\php\php.exe is configured incorrectly and results in a fatal error when it is run. Its configuration file at ... \xampp\php\php.ini needs the following changes:

extension_dir = "\xampp\php\ext" should be "ext"
browscap = "xampp\php\extras\browscap.ini" should be "extras\browscap.ini" This is one that causes the fatal error.
All other "\xampp..." references should be suitably adjusted.
The folks at xampp probably need telling about this mess.

The ... \xampp\php\windowsXamppPhp\php doesn't have a php.ini (from a fresh download) so it won't have the required extensions enabled for Composer to work properly. ComposerSetup.exe will fix this as part of the installation.

I have most certainly been using \xampp\php\php.exe to attempt all commands I have previously attempted. The default XAMPP configuration seems to be making the assumption it was placed at the root folder of a drive; I've been using it from the root folder of my USB drive. Perhaps since Composer's runphp.exe runs from a temp folder on C:\, it might somehow be causing driveless absolute paths to resolve to C paths, but the log file doesn't include enough information to conclude that's definitely the problem. I'll try some things in the near future to diagnose the problem further.

ComposerSetup.exe runphp works fine running across drives. All it does is a CreateProcess using the full file path to php.exe
Perhaps PHP itself doesn't understand driveless absolute paths?

@PixievoltNo1  You were correct - it was a problem running across drives and also because I hadn't realized that certain php.ini directives can cause a fatal error (failing to find browscap.ini in this instance).
So runphp.exe now invokes php without an ini file, so that it will correctly detect missing VC redistributables or other weirdness, as intended. Additionally, php is now executed from its containing folder and all scripts now use the full path from the temp directory.
Thanks for the report.


Bug using Error in the return data strucutre

Describe the feature / bug 📝:
Bug using Error in the return data strucutre of a promise.
While there is no error raise, the toast take the error branch with the following message HTTP error! status: undefined
Steps to reproduce the bug 🔁:
promise data structure return
export type Result<T, E = Error> =
  | { ok: true; value: T }
  | { ok: false; error: E };

export function Ok<T, E>(value: T): Result<T, E> {
  return { ok: true, value };
}
export function Err<T, E>(error: E): Result<T, E> {
  return { ok: false, error };
}

Code to reproduce the bug
async function whatWillHappen(): Promise<Result<null, Error>> {
  return Err(new Error("Not implemented"));
}

export function useSaveProject() {
  const handle = async () => {
    toast.promise(whatWillHappen, {
    loading: "Saving project...",
    success: (result) => {
      if (result.ok) {
        return "Project saved";
      } else {
        return `Result Error: ${result.error}`;
      }
    },
    error: (e) => `Error Raise: ${e}`,
    });
  };

  return (handle);
}

This return:
Error Raise: HTTP error! status: undefined

There is a miss understanding. The library infer that all data structure with .ok and .error is a http request:
problem here

We catch errors in our backend and return a structured response with an error key to indicate an error. It'd be great to be able to escape hatch by throwing an error and propagating the specific message to the error toast.
toast.promise(response, {
	loading: messages.saveLoading,
	success: (response) => {
		if ('errorKey' in response) {
			const errorMessage = getTranslatedError(response.errorKey, lang);
			throw new Error(errorMessage ?? messages.fallbackErrorMessage);
		} else {
			return selectedEntity === ''
				? messages.successRemovedDescription
				: messages.successDescription;
		}
	},
        // catch error and deconstruct the message
	error: (e) => e.message ?? messages.fallbackErrorMessage
});

That works but I've noticed that we lose subtle on-mount animations during the transition process.
toast.promise(sleep(1000), {
    loading: "Loading..",
    success: "Success!",
  })

const id = toast.loading("Loading...")

  await sleep(1000)

  toast.success("Success!", {
    id,
  })

https://github.com/emilkowalski/sonner/assets/24833827/b86571f5-a6bb-484b-95b6-f4031e86d113

Found the culprit:
:where([data-sonner-toast][data-promise='true']) :where([data-icon]) > svg {
  opacity: 0;
  transform: scale(0.8);
  transform-origin: center;
  animation: sonner-fade-in 300ms ease forwards;
}

Animation only applies when the element also contains data-promise='true'.
It makes sense not to apply it to normal toast calls, since the slight scale animation wouldn't be visible due to on-mount opacity animation applied to the parent (and thus to children as well).
Easy workaround is adding a custom class, something like:
.sonner-toast-promise-flow [data-icon] > svg {
  opacity: 0;
  transform: scale(0.8);
  transform-origin: center;
  animation: sonner-fade-in 300ms ease forwards;
}

And applying it like so:
toast.success("Success", {
  id,
  duration: 1000,
  className: "sonner-toast-promise-flow",
  })


Support EKS/K8S Only IPv6

Hello,
I'm getting some errors when deploying K8Ssandra via HELM on an IPv6 only EKS.
I noticed in the logs that cassadra uses <IP_ADDRESS>, but I didn't find it in the ConfigMap where I can change it.
I found something related to these parameters:
JAVA_OPTS="value: -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true"
listen_interface_prefer_ipv6

Is there support for K8S IPv6?

Hi @nuvme-devops, can you let us know what version you are trying to deploy and give us a copy of the manifests you're using?


Upgrade set-output in cd (close #294)

This PR updates the soon to be deprecated set-output command, described here

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

@snowplowcla check this


Projective Point Addition

Need to check if  P == 0 or Q == 0, or P == Q before performing the arithmetic.

If P == Q, then need a separate double algorithm: https://hyperelliptic.org/EFD/g1p/auto-shortw-projective.html


Missing support for passing an Azure AD token

When using the Azure OpenAI models, there is also the case where a user needs to authenticate using an Azure AD token, obtained elsewhere. The Python langchain version already supports this like this:
client = AzureOpenAI(
    azure_ad_token=token_to_use,
    azure_deployment="...",
    api_version="...",
    azure_endpoint="https://..."
)

However, I couldn't find support for this in the documentation, or in the code.
I am creating a PR to add support for this, as this is something that is required by large organizations under certain security scenarios.

PR here: https://github.com/quarkiverse/quarkus-langchain4j/pull/467


Out of order interface error while creating new router

Getting out of order iface error from routing.New. I can see that the error is coming from this line. But I don't understand why the interface index needs to match with for-loop index.
On my machine the interfaces are listed non-sequentially
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether dc:a6:32:6a:e3:b0 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/29 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::dea6:32ff:fe6a:e3b0/64 scope link
       valid_lft forever preferred_lft forever
5: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue qlen 1000
    link/[65534]
    inet <IP_ADDRESS>/32 scope global wg0
       valid_lft forever preferred_lft forever

Can someone explain why the implementation expects interface index to be sequential?

@gconnell ^

Possible duplicate of issue #222.

I get this as well when running in a docker container, where the index 3 interface has an internal index of 5.

Long time no fix ? What's wrong with the patch ?

Long time no fix ? What's wrong with the patch ?

Thx :)

Thx :)

This would warrant a new release, for now I'm using github.com/google/gopacket v1.1.20-0.20220810144506-32ee38206866


WIP feat: add switch to suppress reporting of test failure causes

Summary
As requested in #5358, this PR adds a --noErrorDetails switch that suppresses information on why tests failed, instead showing only what and how many tests failed.
@SimenB
Test plan
Integration test added.
When intentionally breaking one test of Jest and running with --noErrorDetails, the failing test is now displayed in a single line:

as opposed to displaying the full details without the switch:

TODO

[ ] is --noErrorDetails a reasonable name for the switch?
[ ] update doc
[ ] update changelog
[ ] Summary of all failing tests

Summary of all failing tests

This is not pretty.
Should we just omit the "Summary of all failing tests" section if this switch is enabled?
Might also be annoying to test, because we would need to run summary_reporter.TEST_SUMMARY_THRESHOLD + 1 (21) tests to verify this behavior.

I think we should either do this, or somehow allow users to customize the output as it goes.
Might make sense to put in --silent, but I think that's quite a big change.

@jeysal mind fixing the test on windows?

I think the purpose is similar to that of --silent — avoiding pollution of the test results so that it is easier to get an overview of what succeeded and what failed - not on CI, but during development in watch mode. When I am in the middle of refactoring something or have a full test suite for a new feature to implement, I know that a certain group of tests cannot currently work, but I want to make sure that I'm not breaking anything else. Without the switch, the expected test failures can take up more than half the terminal height each, so this becomes really difficult. With the switch, the results will even be on one page if the project has like 30 test suites.

@SimenB will do.

Yeah, as said, I don't think the output of this is useful and it requires to re-run tests to understand what is going on. If you have a flaky test, this may be really confusing to people who are not experts with Jest. I think it's best to implement this as a custom reporter so you can use Jest to your liking without possibly impacting every other user of Jest. Thank you for submitting a PR, though.

Was this PR not accepted?
There's clearly a need for this feature. I don't mind re-running tests if I choose to suppress it via a CLI option. It's not a big deal. If I want details, I shouldn't suppress the output details. It's really that simple.

@theoutlander I imagine what @cpojer is worried about is a bad experience for users who are not knowingly applying the flag (e.g. because someone mindlessly put it into a npm script) and wonder why they do not see the reason for test failures.

bump. this is one of the most frustrating aspects of jest for me. I am running like 300 tests, 90% of which fail, and I just want to see which ones actually succeeded so I can build on those. I have to scroll up through hundreds of terminal lines to see the summary. And then when I add more tests, inevitably I run out of terminal lines and i have to adjust the line limit. I am not smart enough to make my own custom reporter. And the packages I've found from similar people are not useful. This should be a common enough issue to make it a feature, no?


Enhance Pubsub Certification Tests  for negative assertion in Package watcher

Package watcher being used here (also in kafka) ignores the messages which are not part of expected strings.
Introduce notion of 'unExpected' array to store the messages as they are received and are not part of expected array.
This container can be leveraged to test for absence of unwanted message received by subscribers.
Originally posted by @surenderssm in https://github.com/dapr/components-contrib/pull/1623#discussion_r847023600

cc @dapr/maintainers-components-contrib thoughts?


Any chance of adding 10.14 support?

Looks like a nice plugin but not worth "upgrading" to Catalina for it.

Thanks, @mikemcduffie! Glance uses the new Quick Look API that was introduced in 10.15, so it unfortunately won't work with earlier versions of macOS.


Added ignore option when adding new components

Description
Added ignore option when adding new components.
I was frustrated by the need to create a component and then add an ignore option to it afterward. This change introduces the ignore option by default, without modifying the existing template. If ignore is no longer the default in the future, you can simply change the default from Yes to No.

Current behavior (updates)

New behavior

Is this a breaking change (Yes/No):
No.

Additional Information

You may reject this change as it is just a suggestion

I think the default should be "No". Although we may be making almost all components ignore: true, our goal should be making components that we can publicly release.

You're absolutely right. I've made the revisions, so I would appreciate it if you could review it again


Add optional amount to receive

make reusable component for amount fields (token / fiat)
use in receive screen
same behavior in receive & send screens for the fields (since it's the same component)

This is how it works:

Resovles: #39

Great!


[Doc] [NextJS] Add documentation for getting-started/options

Description

Motivation

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update (non-breaking change; modified files are limited to the /docs directory)

Checklist:

[ ] I have read the Contributing guide.
[ ] My code follows the code style of this project.
[ ] My code/comments/docs fully adhere to the Code of Conduct.
[ ] My change is a code change and it requires an update to the documentation.
[ ] My change is a documentation change and it requires an update to the navigation.

Straightforward and to the point!

@nickwesselman - should we recommend which approach is best? The content can be adapted from https://github.com/Sitecore/jss/blob/guides/docs/data/routes/guides/thinking-in-jss/developer-workflows/en.md

@anastasiya29 If there are bits you think would be helpful here for sure. Once we have that content integrated we should link to it. But I also think this article should get a developer routed to an option as quickly as possible.


Cannot query custom prebuilt image deployment

/kind bug
When deploying an inference service based on the pre-built sample, the service is successfully deployed on Kubernetes.
However, when querying the /model/predict route, the resulting HTTP code is a 404 status code. As well, the request doesn't produce any log entry among the running containers.
This is the result of the curl command:
*   Trying ----...
* TCP_NODELAY set
* Connected to --- (---) port 80 (#0)
> POST /models/predict HTTP/1.1
> Host: ----
> User-Agent: curl/7.68.0
> Accept: */*
> Content-Length: 125759
> Content-Type: multipart/form-data; boundary=------------------------4f7797926bd65df9
> Expect: 100-continue
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
* Mark bundle as not supporting multiuse
< HTTP/1.1 302 Found
< Date: Mon, 02 May 2022 14:21:34 GMT
< Content-Length: 0
< Connection: keep-alive
< location: /dex/auth?client_id=kubeflow-oidc-authservice&redirect_uri=%2Flogin%2Foidc&response_type=code&scope=openid+profile+email+groups+openid&state=MTY1MTUwMTI5NHxFd3dBRUZkeE9FbzFPRTlPWlVSaVowZGlWamM9fGKQFkkREIIn3_TRE5AaRgKhBgdplAYC4rofBH_P-3cN
< x-envoy-upstream-service-time: 1
< server: istio-envoy
<
* Connection #0 to host --- left intact

Environment:

KFServing Version: 0.7.0
Kubeflow version: 1.4
Kfdef:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Kubernetes version: (use kubectl version): 1.21.9

Follow this tutorial to authenticate with dex.


cond expr: can't use boolean in IF expression when targeting string target type

If I reference a boolean in an IF cond expr the runtime fails becuase of no converter when the boolean is not part of the mapping.

Works as expected now.


Error "Couldn't connect to API server, check logs" though mizu pods are running in mizu namespace

Describe the bug
I installed mizu 0.12.2 in Macbook. Ran mizu tap "^eric-mesh-gateways*". Got error Couldn't connect to API server, check logs though I could see mizu pods, service and daemonset running successfully in mizu namespace
eechens@EMB-Q6BUMD6N Bin % mizu tap "^eric-mesh-gateways*"
Mizu will store up to 200MB of traffic, old traffic will be cleared once the limit is reached.
Tapping pods in namespaces "mxe-senthil"
+eric-mesh-gateways-65d7667954-6x6wp
+eric-mesh-gateways-65d7667954-fkn5d
Couldn't connect to API server, check logs

Removing mizu resources
eechens@EMB-Q6BUMD6N Bin %

eechens@EMB-Q6BUMD6N ~ % kubectl get all -n mizu
NAME                               READY   STATUS    RESTARTS   AGE
pod/mizu-api-server                1/1     Running   0          6s
pod/mizu-tapper-daemon-set-bwk57   1/1     Running   0          5s
pod/mizu-tapper-daemon-set-zc4ws   1/1     Running   0          5s

NAME                      TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
service/mizu-api-server   ClusterIP   <IP_ADDRESS>   <none>        80/TCP    6s

NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
daemonset.apps/mizu-tapper-daemon-set   2         2         2       2            2           <none>          6s
eechens@EMB-Q6BUMD6N ~ %

To Reproduce
Steps to reproduce the behavior:

Run mizu tap "^eric-mesh-gateways*"

Expected behavior
Expected mizu GUI to open in browser
Logs
mizu_logs_2021_08_31__10_48_41.zip
Screenshots
None
Desktop (please complete the following information):

OS: MacOS Catalina
Browser: Chrome

Additional context

The cluster connectivity is over VPN.
kubectl access to the cluster works fine

Hi @senthilrch,
Thanks for reaching out.
After initial investigation, looking at the logs, it looks like the proxy is running but the mizu route doesn’t exist.
In order to continue the investigation and identify the problem, we’ve added more logs which will give us the needed information.
From your side please do the following steps, this should provide us with the data we need:

Install pre-release 0.12.5 (https://github.com/up9inc/mizu/releases/tag/0.12.5)
Run the command API_SERVER_RETRIES=100 mizu tap "^eric-mesh-gateways*” --set dump-logs=true (We’ve added the option to extend the retries count in order to give more time to debug the problem)
Try to reach the following url: http://localhost:8899/api/v1/namespaces/mizu/services/mizu-api-server/proxy/, do you see Mizu UI?
If not, do you see api server service in http://localhost:8899/api/v1/namespaces/mizu/services
If not, do you see mizu namespace in http://localhost:8899/api/v1/namespaces
If not, is the proxy working? navigate to http://localhost:8899/ and check if you see the endpoint list
if not, run with cli “kubectl proxy” do you see any errors? can you navigare now to http://localhost:8899/ and see list of all endpoints?
Provide us with the logs zip

Thanks!

Hi  @senthilrch,
we recently released new version.
I'm closing this issue and and you are welcome to try the new version to see if your problem are still happening.
If needed, you can open new issue (with reference to this one) or re-open this.
Thanks.


Настроить Travis CI

Partically completed, but we need to change options with OS on windows, made Utest and Ftest, maybe Ltest

Need to write tests


[2] Upgrade to kubernetes v1.18

With 1.20 coming up we should support 1.18
Maybe we already do. So this task will be to investigate what needs to be changed to support 1.18 and create new issues if there are any bigger changes that is needed.
Relevant info:
https://v1-18.docs.kubernetes.io/docs/setup/release/notes/
Acceptance criteria

Test to deploy onto a kubernetes 1.18 cluster
Fix the things that doesn't work
Create issues if there are any bigger changes needed

As this involves testing and deployment of the ck8s cluster with the Kubernetes version v1.18.10, No PR for this issue is linked for closure, certain tests and results are mentioned below -

The image used to test the upgrade on Exoscale was "ck8s-v1.18.10+ck8s0" (was already present), the only change with respect to code required for the upgrade is the replacement of the image in tfvars file.
Deployed the ck8s cluster with version 0.6 (Nodes having the above image and Kubernetes version v1.18.10):
- No issues with respect to API's or deprecation was noticed.
- ck8s cluster was deployed with all the apps and the automated tests were successful, only opendistro-es-curator
pods were failing (which was expected behavior when compared to older Kubernetes versions)
Deployed the ck8s cluster with version 0.7 (Nodes having the above image and Kubernetes version v1.18.10):
- No Issues with respect to the API's or any deprecation was noticed.
- ck8s cluster deployed with all the apps and the automated tests were successful (which was expected behavior
when compared to older Kubernetes versions).
- Some basic tests in the form of UI logins (Grafana and Kibana) and Harbor image push/pull image were
successful.
- These tests were made with 'letsencrypt-prod' as value for both (wc|sc) config files to make sure Dex works.

**Note : To avoid warning for the Fluentd tolerations in the ck8s-version >= 0.7, I tried to update the 'node-role.kubernetes.io/master' and the 'value' component which passed the validation without warning but later error(ed) out. (keep the default settings with warnings)


Headers not converting correctly

When converting headers, such as this h3:
This Is A Header
They convert to this:

**This Is A Header**

Expected outcome:
This Is A Header

Can you share a doc where you see this problem? If I convert a Heading 3, I'm seeing this (in Markdown):
### Heading 3


Improved error messages

fixes #86

@Stephen-Gates
Could you please take a look? I've improved some error messages (syncing some with Data Quality Spec). But still it's not exactly the same in high-level because various reasons like:

fields-headers mismatch is just on error though DQS uses extra/missing-header
not enough information for field.castRow to say on which row number is error
unlike goodtables we handle constraints here together not one-by-one (still solvable)
foreign key message requires some internal refactoring to requested message data
etc

So here is a question how far we should improve it. Is it a real blocker for data-curator. Problem here that error messages here is a exceptional situation messages. It's not intended to be user-facing in general (e.g. app on top should catch it). Unlike to goodtables where all error messages are intended to be user-facing.
So looking forward to your comments. We still have some reserves to improve some messages more (investing more time). Just looking forward to hear what's blockers/priorities. We could handle it in this PR or open individual issue for every new requested improvement.
cc @pwalsh

List of all data related exceptions:

[field.js]
The value "${value}" in column "${this.name}" is not type "${this.type}" and format "${this.format}"
Field "${this.name}" has constraint "${name}" which is not satisfied for value "{value}"
[schema.js]
Row length ${row.length} doesn't match fields count ${this.fields.length}
[table.js]
Table headers don\'t match schema field names
Row ${rowNumber} has unique constraint violation in column "${cache.name}"
Foreign key "${foreignKey.fields}" violation in row ${rowNumber}

@roll I will have a good look over the weekend.

@roll
Ideally the row and column for each error would be reported. This would enable Data Curator to:

highlight the cells where errors are found
support a workflow where users validate a column at a time

If this is not possible, then returning the row in error would enable the row to be highlighted.
In terms of priority:

Type and Format
Constraint
Foreign Key
Structure

I'll add a feature request and comment separately on error message wording.

@Stephen-Gates
That's what I was thinking for. Error messages may be are not the best thing to rely on. But the lib could provide an API for error context when possible e.g:

error.row
error.column
error.code
etc
Than it could be re-used in the higher-level app. I think it could be more reliable way to achieve the same goal.

Sounds like a good approach @roll

@roll sorry for the delay. Assuming no other variables are available for use in the error messages, then...
Type or Format Error
The value "${value}" in column "${this.name}" is not type "${this.type}" and format "${this.format}" appears to be as close as you can get to the Type or Format DQS error message in DQS.
Constraint Error
To better match the format of most constraint error messages in DQS, I suggest
Field "${this.name}" has constraint "${name}" which is not satisfied for value "{value}"
is rewritten to,
The value "{value}" does not conform to the "${name}" constraint for field "${this.name}"
Extra / Missing Value
There's no equivalent message in DQS. The closest is the extra/missing value error messages in DQS that compares the row length to the header row. This error appears to be comparing the row length to the number of fields in the schema.
I suggest
Row length ${row.length} doesn't match fields count ${this.fields.length}
is rewritten to,
The row with ${row.length} columns does not match the ${this.fields.length} fields in the schema
Perhaps columns should be values?
Non-matching Header
To better match the format of most non-matching header error message in DQS, I suggest
Table headers don\'t match schema field names
is rewritten to,
The column header names do not match the field names in the schema
Unique constraint
Row ${rowNumber} has unique constraint violation in column "${cache.name}"
edit that should be applied to DQS and here,
Row ${rowNumber} has a unique constraint violation in column "${cache.name}"
Foreign key
Not implemented in DQS (although there is a suggestion). I don't think I can improve
Foreign key "${foreignKey.fields}" violation in row ${rowNumber}
I did consider:

The foreign key "${foreignKey.fields}" in row ${rowNumber} has a foreign key violation
The foreign key "${foreignKey.fields}" in row ${rowNumber} does not have a matching primary key value

@Stephen-Gates
Thanks. It's just great help.

@Stephen-Gates
Please take a look. I've:

updated error messages based on your feedback
added error.rowNumber/columnNumber properties (if available)

@roll will review this week. thanks.

@Stephen-Gates
Thanks! I've fixes the last one.


Competitive Programming Tricks

Can someone add important Competitive Programming Tricks?

I want to work on this, please assign me this issue.


Feat: adding similar hovering effect on items of drop down list as it is in nav bar items

Describe the feature
i will be adding hovering effect on buttons of drop down list just as the hovering effect present in nav bar items .
Add ScreenShots
as we hover there is nothing happening .
https://github.com/mdazfar2/HelpOps-Hub/assets/159682348/9fcabfbb-4d6c-46b1-93d6-d6cc201e87ae
i wil add hovering effect like shown below .
https://github.com/mdazfar2/HelpOps-Hub/assets/159682348/0a94b50d-3649-4b4b-afac-ce2319462800
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSoC'24 contributor
[X] I want to work on this issue

@mdazfar2 please assign me this issue under gssoc labels

@ANKeshri You are assigned.

Please try to add comments about where and what type of changes you made.
Please don't add unnecessary code if there is no need! Thanks :)

@mdazfar2 as shown in the video i want to add similar hovering effect to the team card and also contributor card as the hovering is present in resources in both mode .
If you want please let me know . thank you

@mdazfar2 should i work on that


Add restore key to _freeze cache key

This PR makes a tiny change to both preview and publish workflows:
https://github.com/TuringLang/docs/blob/d7dd920038893dee8fc9f29d552f397ec53ececd/.github/workflows/publish.yml#L40-L49
The main cache key itself will now be determined by both the Manifest as well as the contents of the notebooks (**/index.qmd). However, if the contents of the notebooks have changed, it will use the restore key to load the latest version of _freeze that was run with the same Manifest.
The aim is to let each CI run access the most recently cached _freeze folder, to avoid re-rendering the same docs page on successive CI runs.
Closes #536

Sadly, not until it's merged 🙃


Upgrade styleguidist v9

Resolves #420
Impact: minor
Type: docs

Component
Upgraded react-styleguidist to 9.1.11
Upgraded webpack to 4.35.3 (4.x is dependency for latest styleguidist)
Moved font, Stripe script, and meta tags from deprecated HTML template into styleguidist.config.js template JSON area.
As of v9 in Styleguidist, all components (other than the one currently under discussion) are no longer available in the global (window) context in the .md files, hence new requires to pull the components in manually.

🚀 Preview deployed
Built with commit d84c7aff2557075d2343c129f5c8ee5c4169d834
https://deploy-preview-421--stoic-hodgkin-c0179e.netlify.com

Almost forgot how 🆒 😎 🆒  it is to have Netlify branch deploys!

🚀 Preview deployed
Built with commit d994243985a4e12a91c3a6973160fa9897424f36
https://deploy-preview-421--stoic-hodgkin-c0179e.netlify.com

After some dependency-wrangling, I did finally come up against one (apparently) intractable snyk issue arising from<EMAIL_ADDRESS>Since 'snyk wizard' indicated there was no available mitigation, I added a .snyk file to the repo to ignore the issue for now.

:tada: This PR is included in version 0.66.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Multline function declarations?

In the documentation:
https://prql-lang.org/book/queries/functions.html
I only see very simple single-line functions.
Is it possible to have function declared over multiple lines?

It's possible to have whole pipelines in functions!
That said, I'm seeing some odd behavior. I admittedly haven't used these much, so I'm not surprised they're not the most robust things in the lang.
This works:
func foobar -> (
  filter x == 5
  aggregate [
    sum foo,
    count bar,
  ]
)

from y
foobar asdf  # note this `asdf`

SELECT
  SUM(foo),
  COUNT(*)
FROM
  y
WHERE
  x = 5

-- Generated by PRQL compiler version:0.5.0 (https://prql-lang.org)

Weirdly it requires the random asdf! Without that word, we get an error:
Error:
    ╭─[:10:1]
    │
 10 │ foobar
    · ───┬──
    ·    ╰──── expected pipeline that resolves to a table, but found `<closure over `<closure over `aggregate [
  sum foo,
  count bar,
] <closure over `null` with 2/2 args>` with 0/0 args>` with 0/1 args>`
    ·
    · Help: are you missing `from` statement?
────╯


Register encoder

In rails 4/5 integration tests, you can do something like
get foo_path,
  params: {...},
  as: :json

there's only one inbuilt option to the as: param, :json - to get xml working in a similar you have to register the encoder something like this:
ActionDispatch::IntegrationTest.register_encoder :xml,
  param_encoder: -> params { params.to_xml },
  response_parser: -> body { body }

I'd say that xml_parser plugin should do this for you..?

:as was added in Rails 5.
You'd need to wrap it in an on_load hook for the integration tests and a respond_to?(:register_encoder) as well.
The response parser probably needs more help than just return the xml string. Given this library has an XML parser we should be able to parse the contents.
Looking forward to your PR!


Received AttributeError on DISPLAY with magtag_simpletest.py

This is the magtag that came with adabox017
It worked when I first plugged it in but I haven't been successful at loading any other program on it.
This is with the latest library:
adafruit-circuitpython-bundle-6.x-mpy-20210101.zip
code.py
SPDX-FileCopyrightText: 2017 Scott Shawcroft, written for Adafruit Industries

SPDX-License-Identifier: Unlicense
import time
from adafruit_magtag.magtag import MagTag
magtag = MagTag()
magtag.add_text(
text_position=(
50,
(magtag.graphics.display.height // 2) - 1,
),
text_scale=3,
)
magtag.set_text("Hello World")
button_colors = ((255, 0, 0), (255, 150, 0), (0, 255, 255), (180, 0, 255))
button_tones = (1047, 1318, 1568, 2093)
while True:
for i, b in enumerate(magtag.peripherals.buttons):
if not b.value:
print("Button %c pressed" % chr((ord("A") + i)))
magtag.peripherals.neopixel_disable = False
magtag.peripherals.neopixels.fill(button_colors[i])
magtag.peripherals.play_tone(button_tones[i], 0.25)
break
else:
magtag.peripherals.neopixel_disable = True
time.sleep(0.01)
Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Traceback (most recent call last):
File "code.py", line 7, in
File "adafruit_magtag/magtag.py", line 84, in init
File "adafruit_magtag/graphics.py", line 56, in init
AttributeError: 'module' object has no attribute 'DISPLAY'
Press any key to enter the REPL. Use CTRL-D to reload.
Adafruit CircuitPython 6.0.1 on 2020-12-28; Metro ESP32S2 with ESP32S2

import board
dir(board)
['class', 'A0', 'A1', 'A2', 'A3', 'A4', 'A5', 'D0', 'D1', 'D10', 'D11', 'D12', 'D13', 'D2', 'D3', 'D4', 'D5', 'D6', 'D7', 'D8', 'D9', 'DEBUG_RX', 'DEBUG_TX', 'I2C', 'MISO', 'MOSI', 'NEOPIXEL', 'RX', 'SCK', 'SCL', 'SDA', 'SPI', 'TX', 'UART']

It looks like circuitpython for the wrong device is loaded onto it (Metro ESP32S2). Did you update circuitpython with a new .bin or .uf2 file?
Here's the correct link for circuitpython for MagTag: https://circuitpython.org/board/adafruit_magtag_2.9_grayscale/. Main learn guide is here: https://learn.adafruit.com/adafruit-magtag

It looks like circuitpython for the wrong device is loaded onto it (Metro ESP32S2). Did you update circuitpython with a new .bin or .uf2 file?
Here's the correct link for circuitpython for MagTag: https://circuitpython.org/board/adafruit_magtag_2.9_grayscale/. Main learn guide is here: https://learn.adafruit.com/adafruit-magtag

hi @ljmwaugh happy new year. yeah please try deleting the  on the magtag CIRCUITPY drive and starting at this step to install the latest and greatest circuitpy
https://learn.adafruit.com/adafruit-magtag/circuitpython
if you're still having issues, please post on forums.adafruit.com we have a team there that can help you!
https://forums.adafruit.com/viewforum.php?f=59

hi @ljmwaugh happy new year. yeah please try deleting the  on the magtag CIRCUITPY drive and starting at this step to install the latest and greatest circuitpy
https://learn.adafruit.com/adafruit-magtag/circuitpython
if you're still having issues, please post on forums.adafruit.com we have a team there that can help you!
https://forums.adafruit.com/viewforum.php?f=59


Documentation for offline use

Hello.
I think, it may be useful for anycad.rapid.net to have a documentation available for offline use.
I mean, all materials in an archive from http://anycad.cn/api

May you publish it please?


Migrate from findDOMNode to refs

React team just finally announced deprecating findDOMNode.
https://github.com/facebook/react/pull/13841
Would be good to start providing better refs in each component to get rid from RootRef.
Edit @eps1lon: Hijacking OP to document progress.
If we need the DOM node we still use findDOMNode but we call it with refs. If the refs are attached to host components you won't get a strict mode warning. Only if they are attached to class components.

Strict-mode ready findDOMNode

[x] Slider
[x] ButtonBase
[x] ClickAwayListener
[x] MenuList
[x] Modal
[x] Popover
[x] Portal
~[ ] RootRef~ compat module
[x] Slide
[x] SwipeableDrawer
[x] TextField

This is such a big move from React. For a long time, I thought they weren't going to execute on this. From what I understand, the motivation is around simplifying React internal core. This makes sense. Let's see how we can fulfill this new constraint.

React 16.6 will log deprecation warnings in strict mode about this. Will be good way to gauge the impact of this change

This is also important because React recommends passing StrictMode before enabling concurrent React. It is unstable right now but should be finalized this year.

This is also important because React recommends passing StrictMode before enabling concurrent React. It is unstable right now but should be finalized this year.

This is the actual driving factor for us. We've made some progress but react-transition-group will probably be the last remaining blocker. Unless we fork it but it's quite a bit of bundle bloat we would introduce if react-transition-group is used in other parts of the app bundle.

findDOMNode remains in the codebase for backwards compatibility with class components. If you forward refs to host instances where necessary you should get no more deprecation warnings in StrictMode.
For more details see https://material-ui.com/guides/composition/#caveat-with-refs

@eps1lon

you should get no more deprecation warnings

Is that because findDOMNode(validElementRef) is safe?

backwards compatibility with class components

Can't class components be wrapped in forwardRef as well? Or do you mean that you don't want yet another breaking change and for existing class components that do not correctly forward refs to work?

Or do you mean that you don't want yet another breaking change and for existing class components (that do not correctly forward refs) to work?

Yes. Just reducing the amount of breaking changes.

Is that because findDOMNode(validElementRef) is safe?

At least for now. We're still waiting for an official confirmation but so far findDOMNode doesn't throw if called with host instances.


Bookmarks changing chapter to unread

Steps to reproduce

Read chapter from updates tab
After closing reader, quickly bookmark read chapter before chapter is changed to read

Expected behavior
The chapter should be bookmarked, but is still marked as read
Actual behavior
Chapter is bookmarked as usual, but stays as unread
Crash logs
No response
Tachiyomi version
1.7.0
Android version
Android 12
Device
Google Pixel 3a
Other details
Seems to be caused by chapter "status" still being considered as unread when it is bookmarked, giving it a "status" of unread and bookmarked, and preventing it from being updated to read properly, though this is just my assumption from what I have seen.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version 1.7.0.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Try on the preview

I tried on the preview as well. I've also figured out that it happens specifically when you bookmark the chapter before it changes to read

Probably addressed by https://github.com/jobobby04/TachiyomiSY/commit/992679e470843a2fd1539dc44b96db133565d442

I can still reproduce the bug easily on the newest preview, though it is a bit tighter timing. Might be related to worse phone performance


Question about the "route" in measurements file

Hi, Thanks for your great work. I'd like to use the code to save the hd_map data. I notice that the route in measurements seems like to be the map information. Can you give me some details. Thanks a lot!

The route as well as the bev segmentation are created using HD-Map information.
We don't save the entire HD-map in the dataset.
If you just want to store the whole HD-map on disk you could just store the string you get from the HD-map sensor in a .txt file and run that code for every map.
You can see how to make a carla.Map object from the HD-map string here (e.g. you can load the string later once you need it).

Thanks a lot. I will try it.
发自我的iPhone
------------------ Original ------------------
From: Bernhard Jaeger @.>
Date: Tue,Jan 9,2024 10:26 PM
To: autonomousvision/carla_garage @.>
Cc: raozhongyu @.>, Author @.>
Subject: Re: [autonomousvision/carla_garage] Question about the "route" inmeasurements file (Issue #24)

Hello, thank you for your great work first. I'd like to ask the following question about your latest paper transfuser++:
In table6 and table7 you mentioned that the longset6 is used as training towns and LAV is used as validation. Does that mean that you collected the expert data (for imitation) in routes of longest6?
Also, in appendix C I see that 'we test our additions to TransFuser by repeating the experiments on the training towns (Longest6) while training with all data. ' I wonder what does 'all data' mean here, comparing to the dada you used before.
Shortly, I am kind of confused by the category of the data you used (By town or by route?). I would be greatful if you can make it clearer to me. : )

Hi, I have collect the surrounding hd map information based on the exsiting dataset. I  meet a little problem, where I only want to collect the front information of ego-car. I'd like to konw how to get the yaw and roation  based on the exsiting information in your dataset such as the ego matrix, the theta.

https://github.com/autonomousvision/carla_garage/blob/fb4b180332e465c53095ad6de29429442664882c/team_code/autopilot.py#L359 The global yaw of the ego vehicle is stored in the measurement file as theta.


Bagdes don't handle 4+ digits numbers

Hi,
There is an issue with badges' text overflow when they contain more than 4 characters :

I'm expecting more something like that :

I can't find something in MD specs about badges...

+1 good find, I think the size should most likely work this way

This is something I did for myself : http://codepen.io/jfily/pen/dYgPwG
Don't know if you can reuse it.

In my opinio a badge should display a number from 1 to 99: any value greater than 99 displays "99+" (many apps with material approach use this role).
In same way, a value of 0 should clear the badge.
This is my opinion and i don't found any suggestion in material spec.

In your codepen sample, we can see the bad effect: no more control on ui flow with increasing of width of icon place

That's because the badge is absolute positioned... Hard to do something better (but i'm not really a web dev so I'm sure someone will find a better solution)

I'd rather we not make it expanding automatically. Urging a limit of characters to show seems best to me. Otherwise badges can become unexpectedly large which is an issue onto itself.

What are the downsides to automatically expanding in your mind @Garbee ? How do they stack up to the pros?

Handling 2 digits is enough I think... You (and most apps do the same) can show something like "99+" if there are too many notifications. The real number doesn't matter past a certain amount.

Growing the badge means potentially covering other content or even buttons. The “99+” solution is the most generic one imo and is being used by other MD-styled apps. However, the spec should be extended to cover this. We should bring this up with the team.

:bow: @surma

Oh whoops, sorry @samccone Missed your question to me here. Surma just covered it perfectly though.


android bundler apk failed

Compile and run without problems, packaging error，Log as follows：
FAILURE: Build completed with 10 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsDtest'.

Could not resolve all files for configuration ':app:dtestRuntimeClasspath'.
Could not resolve app.cash.sqldelight:android-driver:2.0.0.
Required by:
project :app > com.walletconnect:android-core:1.31.2
project :app > com.walletconnect:auth:1.28.2
No matching variant of app.cash.sqldelight:android-driver:2.0.0 was found. The consumer was configured to find a runtime of a component, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest', attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '7.1.2', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- Variant 'debugVariantMavenApiPublication' capability app.cash.sqldelight:android-driver:2.0.0:
- Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'debugVariantMavenJavaDocPublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'debugVariantMavenRuntimePublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'debugVariantMavenSourcePublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'releaseVariantMavenApiPublication' capability app.cash.sqldelight:android-driver:2.0.0:
- Incompatible because this component declares an API of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a runtime of a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'releaseVariantMavenJavaDocPublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'releaseVariantMavenRuntimePublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')
- Variant 'releaseVariantMavenSourcePublication' capability app.cash.sqldelight:android-driver:2.0.0 declares a runtime of a component:
- Incompatible because this component declares a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release' and the consumer needed a component, as well as attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'dtest'
- Other compatible attributes:
- Doesn't say anything about com.android.build.api.attributes.AgpVersionAttr (required '7.1.2')
- Doesn't say anything about its target Java environment (preferred optimized for Android)
- Doesn't say anything about org.jetbrains.kotlin.platform.type (required 'androidJvm')

@jakubuid Adding dtest packaging in buildType will cause errors, removing web3Model will not. How to solve this problem?

After many times of debugging, it is determined that it is caused by custom buildTypes, because the dtest name in the packaging of custom buildTypes will appear above problems, and there is no problem in packaging debug and release packages。
At present, buildType has been restored, only debug and release are retained, and productFlavors channel types are added。


⚠ GitLab Server has degraded performance

In 0211801, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6031 ms

Resolved: GitLab Server performance has improved in 0532d01.


Pj/explore/post model

Changed some naming details and structure. This is not how to do it but what was in my head. TS makes it so much more complicated!
A lot of the naming changes were to differentiate really clearly between post, comment and reply users and the same for the text body.
All are open for change but this gives a working model to work from. The single data seed became really complicated and large right away! Most of the work will be done for us in actual usage though. In fact, all of it!
To not mess with existing data, I did all of this in the test db. You can run the app in test mode, npm run start:test

Approved based on what I have seen!


hugo scaffolding inconsistent with theme

When publishing to the /docs directory there is an inconsitency in files changed.
To recreate:

Add a markdown file in content directory
Run hugo command
Files changed in /docs director
Commit changes
Run hugo again
Git shows new changes

Visually the navigation menu breaks when clicking through your folders and files.
I have to run hugo many times and recheck the menu by clicking each link and making sure the menu doesn't collapse.
I expect that when I run the hugo command for it to publish to the docs directory all files would be updated on one run. It seems like some files are missed. I have to run the hugo command about 3-4 times and then check the files structure locally before commiting.
Not sure if others are experiencing this issue. Can't tell if it is a theme issue or a hugo issue

May be you can use Chrome in dev mode and do "reset all and relaod". Often the is some cache (css and al) involved

Hi @jonsgreene,
Probably I can repeat it too. Can you let exactly what version Hugo are you using?
And what is your dockdock theme version (checkout last commit)? Is it latest-latest?

@Pilskalns Hugo version v0.49.2, docDock is the latest as well. @divinerites That may fix the navigation issue via chrome, but doesn't fix the git changes I see when running the hugo command again. I expect that if I commit my changes and run the hugo command that I should not see any files changed. It should look just like the remote. Sometimes I run the command and see 5 files changes, other times i'll see 3 files changed. So it seems like something that generates the files in the /docs folder is not making it all the way down the tree the first time.

Hi @jonsgreene,
Currently, only unwanted behavior what can I repeat is if children shortcode is used on root _index.md file. If it is on sub-pages, then everything works correctly. (this I meant also in my comment above).
Could you list what kind of files are changing with each run? Maybe you have them in some commit publicly available?

@Pilskalns This is not a public repo unfortunately. I have noticed that if I delete the browsers cache the navigation section will update and start to function. @divinerites also mentioned that it could be cache. Still haven't been able to figure out why git sees changes after running hugo after a fresh push. I'll keep testing, thanks for the help.

So today I ran a few more test. I noticed that the while using the submodule it would only update to this sha b667496cb368fa3336c5b2ef310abb74c2f365da
I updated hugo to v0.52/extended
I then ran git submodule update --remote to be on your latest commit
It seems to have fixed the issue with the navigation problem. I do however notice that the changes when running hugo after a good commit changes this meta data on each page
-<meta name="revised" content="2018-12-05T12:15:11 EST">
+<meta name="revised" content="2018-12-05T12:17:20 EST">
This isn't a big deal. I'm going to keep poking around to see if the issue was resolved by recent updates.

@jonsgreene great find!
Yes, revised tag was added around month ago. It is just the build time of the site.
If you need to completely the same output between two builds, you can add your custom head.html and remove that line.


NeoForge and Multiloader Template

This PR ports AstralBot to NeoForge and reorganizes the build scripts to not use Architectury anymore.
There's still a few things left to do:

[ ] Get Forge and NeoForge servers to run in dev mode (From within Intellij)
[x] Wait for an updated version of the sqlite-jdbc "Mod", see https://github.com/kosmolot-mods/minecraft-sqlite-jdbc/issues/3
[x] Adjust build/publishing pipeline to include new dependencies and the NeoForge release

I've decided to nuke Forge support, because a lot of other mods did too and the Gradle configuration for jarJar and shadow was unconquerable.

The NeoForge server not running in the development environment is related to this issue: https://github.com/thedarkcolour/KotlinForForge/issues/86. Since I can test the mod with Fabric for 1.20.4 I will merge this and just live with the fact I can't test the Neo server.


Changing name of resource

Trying to change resource name, but it updates only on reopening scene. I think better to update it instantly.

I think it updates instantly if you save it manually via the use of the little save icon and give it a name there.
But yes, perhaps having it update instantly there would be nice.

this screen will probably change in 1.2 (resources dock will most likely be replaced by a history dock)

Wow, history/undo-redo dock like in photoshop? I thing in 1.2 will be cool to be a tab like in browsers, so user can choose scene to work. In 1.1 no too fast to open and change scene.
Another problem with resources i have. Build-ins resources sometimes reset they name to default when i reorder my tree. That begin visible only after saving and reload scene.
So, i just save my scripts in folder and problem gone..

yes 1.2 will have scene tabs on top
On Wed, Apr 8, 2015 at 11:32 AM, honix<EMAIL_ADDRESS>wrote:

Wow, history/undo-redo dock like in photoshop? I thing in 1.2 will be cool
to be a tab like in browsers, so user can choose scene to work. In 1.1 no
too fast to open and change scene.
Another problem with resources i have. Build-ins resources sometimes reset
they name to default when i reorder my tree. That begin visible only after
saving and reload scene.
So, i just save my scripts in folder and problem gone..
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1645#issuecomment-90933840.

The resource dock has been removed for 2.0, so this issue is not relevant anymore.

(resources dock will most likely be replaced by a history dock)

@reduz Is it still on the roadmap? That sounds like a very nice feature! (and I miss a 4th dock now that we have easily customisable dockable panels :D)


No lens appear until we leave and reenter into the thumb.

fix : When large full image is lately loaded (into a pop-up), no lens will appear until we leave and reenter into the thumbnail.
Due to isReady === false when we pass into zoomOn function and display = 'block' is never set until mouseLeave and mouseEnter again.

Thank you for the pull request. Unfortunately I'll be traveling for next few weeks and won't have a chance to look into testing, merging and releasing this for a bit. Looks like a legit bugfix from a glance though!

No problem, take your time to check that there is no side effects.
We have a plan B to use my fork until it is fixed.
I think it's typically due to our use of the module into a pop-up.

Super late coming back to this, but I've had a chance to try this out now and this fix is not working for me. It probably solves your problem, but setting 'display = block' when images are loaded means the zoom will look enabled even if the mouse isn't over the image. Or if the image hasn't been clicked in the click-mode. So this issue will need a different approach, feel free to either update the PR or I'll try looking into a solution myself at a later point.


Fix:(XFS-Quota) xfs_quota support by mounting /dev from host

Signed-off-by: Chuck Schweizer<EMAIL_ADDRESS>Pull Request template
Why is this PR required? What issue does it fix?:
xfs_quota is not currently working on LVM volumes because /dev is not mounted from the host
What this PR does?:
Updates the helper container creation to include /dev from the host
Does this PR require any upgrade changes?:
no
If the changes in this PR are manually verified, list down the scenarios covered::
Created a LVM for the openebs local xfs filesystem
Provisioned a PVC and POD to verify quota was working
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[x] Fixes #129
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

PLEASE REMOVE BELOW INFORMATION BEFORE SUBMITTING
The PR title message must follow convention:
<type>(<scope>): <subject>.
Where:
Most common types are:
* feat        - for new features, not a new feature for build script
* fix         - for bug fixes or improvements, not a fix for build script
* chore       - changes not related to production code
* docs        - changes related to documentation
* style       - formatting, missing semi colons, linting fix etc; no significant production code changes
* test        - adding missing tests, refactoring tests; no production code change
* refactor    - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
* cherry-pick - if PR is merged in master branch and raised to release branch(like v0.4.x)
IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.

pushed gofmt update for cmd/provisioner-localpv/app/helper_hostpath.go


Updated  join-us.module.scss

changed the color of join us section
Issue that this pull request solves
Closes: #813
Proposed changes
Brief description of what is fixed or changed
Types of changes
Put an x in the boxes that apply

[ ] Bugfix (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 not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Put an x in the boxes that apply

[x ] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ x] I have made corresponding changes to the documentation
[ x] My changes generate no new warnings
[x ] My changes does not break the current system and it passes all the current test cases.

Screenshots
Please attach the screenshots of the changes made in case of change in user interface
Other information
Any other information that is important to this pull request

@kashi-verma  i would like to understand what updation u are intended to make?

I've changed background color of join us section
On Sat, 18 May 2024, 11:10 kajol, @.***> wrote:

@kashi-verma https://github.com/kashi-verma i would like to understand
what updation u are intended to make?
—
Reply to this email directly, view it on GitHub
https://github.com/HITK-TECH-Community/Community-Website/pull/913#issuecomment-2118650963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BETIMCC6D5525VFLSLFBT2TZC3SU7AVCNFSM6AAAAABH4ZASA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGY2TAOJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

can you provide a better color in dark mode as well?

Ohk , i do it

Yes, I can.
On Sat, 18 May 2024, 13:16 kajol, @.***> wrote:

@.**** requested changes on this pull request.
can you provide a better color in dark mode as well?
—
Reply to this email directly, view it on GitHub
https://github.com/HITK-TECH-Community/Community-Website/pull/913#pullrequestreview-2064633393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BETIMCADKD76EBW53F3ZRDDZC4BL3AVCNFSM6AAAAABH4ZASA2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDANRUGYZTGMZZGM
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

closing this as duplicate


Security:  Tighten Security Measures for Communication

AS AN Architect
I WANT TO Ensure that Communications are as Secure as possible by using recommended standards and versions
SO THAT the opportunity for exploit is reduced
Acceptance Criteria

[ ]  Ensure HTTPS is used wherever possible
[ ] TLS 1.2 as a bare minimum
[ ] User APIs implement CORS
[ ] Look at AKS control plane access, is this secure enough.

We may want to reconsider this ticket (or maybe part of it).

Acceptance Criteria
Comment

Ensure HTTPS is used wherever possible
1. Ingress for all the applications already force HTTPS.  2. NGINX ingress controller on AKS also redirects to HTTPS.  3. The dotnet apps should ideally communicate of HTTP as HTTPS is not necessary for communications between apps within the cluster

TLS 1.2 as a bare minimum
Our cluster supports TLS 1.3. See the SSL Server Test report showing this: byk-dev-aks-ingress.westeurope.cloudapp.azure.com

Look at AKS control plane access
At the moment, the AKS control plane is protected with RBAC and AAD and any Contributor on the Byrokratt subscription can access the control plan. We could try creating a specific security group and control who has access. Otherwise, the next step would be to wrap the cluster in a vNET

User APIs implement CORS
This needs to be implemented on CentOps API


[Main Map] Add map type icons for Road, Terrain, Satellite

Use something similar to Google Maps icons

I've decided to generate our own res images instead of pulling from Google Maps. Should be fairly straightforward

I also discovered this tool which lets you create different map styles.

For e.g. I'll use the following style to remove all labels from the basemap and then generate images using that.
[
  {
    "elementType": "labels",
    "stylers": [
      {
        "visibility": "off"
      }
    ]
  },
  {
    "featureType": "administrative.land_parcel",
    "stylers": [
      {
        "visibility": "off"
      }
    ]
  },
  {
    "featureType": "administrative.neighborhood",
    "stylers": [
      {
        "visibility": "off"
      }
    ]
  }
]


Discuss throttling rate for each API endpoint

We have 7 API endpoints currently, we need to discuss throttling rate for each endpoint

/packages

/packages/all
/packages/bulk_search

/vulnerabilities
/alias
/cpes

/cpe/bulk_search

Here are the proposed throttling rate for basic user for each endpoint

/packages - 10/min

/packages/all - 1/hour
/packages/bulk_search - 5/hour

/vulnerabilities - 10/min
/alias - 5/min
/cpes - 5/min

/cpe/bulk_search - 5/hour

Done in https://github.com/nexB/vulnerablecode/pull/993


The text is recognized in reverse (iOS 15.5)

When the text is recognized by the front camera, the text is read in reverse.(e.g." >>>>wOaHMMO3Ya>>")
Isn't there any way to make text recognizable as human readable? (e.g. "PMKORJU<<BYEON<<<")

Check this https://www.youtube.com/watch?v=kOYP2Xun_6o&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=77


About ERROR: Could not find all groups

Dear all,
I'm trying your package.
I decided to start with a famous molecule, Penicillin G. So I got its SMILES at:
https://pubchem.ncbi.nlm.nih.gov/compound/Penicillin-G#section=Canonical-SMILES
Canonical SMILES = CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C
But I got error:
julia> (component,groups) = get_groups_from_smiles("CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C", UNIFACGroups)
ERROR: Could not find all groups for CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C
Stacktrace:
 [1] error(s::String)
   @ Base .\error.jl:35
 [2] get_groups_from_smiles(smiles::String, groups::Vector{GCPair}; connectivity::Bool, check::Bool)
   @ GCIdentifier C:\Users\admin\.julia\packages\GCIdentifier\V6P7e\src\group_search.jl:126
 [3] get_groups_from_smiles(smiles::String, groups::Vector{GCPair})
   @ GCIdentifier C:\Users\admin\.julia\packages\GCIdentifier\V6P7e\src\group_search.jl:111
 [4] top-level scope
   @ REPL[3]:1

Is it a bug or some limitation?
thanks,

Hi Felipe,
This isn't really an error. It just means that UNIFAC doesnt have all the groups necessary to model Penicilin G. unfortunately... You can see which groups UNIFAC does have by adding check=false:
(component,groups) = get_groups_from_smiles("CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C", UNIFACGroups; check=false)
("CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C", ["COOH" => 1, "CH3" => 2, "ACH" => 5, "CY-CH" => 2, "CY-C" => 2, "CH2CO" => 1, "CHNH" => 1, "AC" => 1])

To see which groups are missing, you can use our find_missing_groups_from_smiles function:
groups = find_missing_groups_from_smiles("CC1(C(N2C(S1)C(C2=O)NC(=O)CC3=CC=CC=C3)C(=O)O)C", UNIFACGroups)
3-element Vector{GCPair}:
 GCPair("[NX3;H0;R]", "cN")
 GCPair("[SX2;H0;R]", "cS")
 GCPair("[OX1;H0;!R]", "O=")

Indeed, it looks like the cyclic sulfur and cyclic nitrogen groups haven't been fitted. The ketone oxygen is mainly due to the fact that there is a cyclic carbon which is double bonded to that oxygen.
Hope this helps!
Best regards,
Pierre

Hi Pierre,
Thank you for your attention and response.
Do you think about expanding support to other groups?
My best regards,

Hi Felipe,
We aren't the developers of UNIFAC so we don't really have much motivation / interest to expand the approach to other groups. This is something you could do yourself, however, using Clapeyron.
Feel free to raise an issue there if you'd like some guidance.
Best regards,
Pierre

Hi,
ok, thank you very much!
my best,


Instagram Clone[SSOC'23]

Describe the project
Hello Sir/Ma'am👨💻 ,I am Arpan Chowdhury, a aspiring Web developer.🤖 Here is the project of the front-end Web Development. We all use the most famous social media platform INSTAGRAM. So, here is the frontend clone of the landing page👆🏻 .
Issue Type:

[] Bug Report
[] Feature Request
[] Documentation
[X] New Project

Additional context
It is made using HTML , CSS & JS.
Screenshots

Please assign me the issue under SSOC 2.0

@TusharKesarwani @siddhi-244 @Arun9739 Please assign me the issue under SSOC 2.0

@TusharKesarwani could you plz assign me this

Can u please assign me this issue

@TusharKesarwani @siddhi-244 @Arun9739 Please assign me this issue

Already present in the repo


This and that

Chore: Update Ruff configuration to match more recent versions
Update README

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.39%. Comparing base (2d6db0d) to head (cf4faae).

Additional details and impacted files
@@             Coverage Diff              @@
##           mlflow-2.11     #126   +/-   ##
============================================
  Coverage        93.39%   93.39%
============================================
  Files               14       14
  Lines              227      227
============================================
  Hits               212      212
  Misses              15       15

Flag
Coverage Δ

unittests
93.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Can't change photo for channel

Trying to change photo on channel.

http://localhost/c/channel/mod/settings

Please leave the exact error response you get (you're in the console tab of chrome. open network instead; and track the ajax request)

exception:"Symfony\Component\Debug\Exception\FatalErrorException"
file:"/var/www/html/vendor/laravel/framework/src/Illuminate/Http/JsonResponse.php"
line:71
message:"Uncaught InvalidArgumentException: Malformed UTF-8 characters, possibly incorrectly encoded in /var/www/html/vendor/laravel/framework/src/Illuminate/Http/JsonResponse.php:71↵Stack trace:↵#0 /var/www/html/vendor/symfony/http-foundation/JsonResponse.php(50): Illuminate\Http\JsonResponse->setData(Array)↵#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Http/JsonResponse.php(27): Symfony\Component\HttpFoundation\JsonResponse->__construct(Array, 500, Array)↵#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(435): Illuminate\Http\JsonResponse->__construct(Array, 500, Array, 192)↵#3 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(186): Illuminate\Foundation\Exceptions\Handler->prepareJsonResponse(Object(Illuminate\Http\Request), Object(InvalidArgumentException))↵#4 /var/www/html/app/Exceptions/Handler.php(76): Illuminate\Foundation\Exceptions\Handler->render(Object(Illuminate\Http\Request), Object(InvalidArgumentException))↵#5 /va"

This again isn't the exact response I asked for.

you're in the console tab of chrome. open network instead; and track the ajax request

Do you have your working FTP setup ready?

Yes vsftpd.
CDN must be sure?

what?! Please write better English.

He is using vsftpd.


Implement matrix testing against different spring boot versions, fix config for spring boot 3.1

Hi!
This PR adds github workflow configuration to run tests automatically against latest major releases of spring boot (2.7, 3.0, 3.1) and fixes issue with PropertiesMongoConnectionDetails bean added in spring boot 3.1 (MongoProperties were injected before they were modified by EmbeddedMongoAutoConfiguration).
This also completes some tasks from https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo.spring/issues/33

@chillb0nes thanks:)


Error 3 While decompressing data: incorrect data check. How can i get rid this error?

I was able to create a new wallet with my seed.   All coins have been restored.


Syntax highlighting

Highlight all the things.  Especially grey comments...

On close inspection this as quite complex as it means moving away from a text area as input for source code

This would be quite cool if we implement using something like https://github.com/microsoft/monaco-editor


Carousel not displaying on API 28/ Pie

Not sure why but all works on < API 28.

So the problem was actually from Picasso and Glide themselves when loading network images.
And adding android:usesCleartextTraffic="true" to the manifest solved this issue.


Fix Luau number constant handling

Leading _ is allowed in exponent part: "0.5e_3".

Leading _ is allowed in hex constants: "0x_DECAFBAD".

Binary constants now handled: "0b10101100".

Removed hex floats: "0xAB.CDpEF", they are not allowed in Luau.

Not sure whether the Chinese translation is correct, at least Google Translate agrees.

Thanks you!


Missions

Create basic structure for missions

@Buyaki01 I will proceed merging the data so i can pull on my end :+1: