Feature: DNS Lookup

added automatic resolving of domain names in place of IP addresses (e.g. "google.com" instead of "<IP_ADDRESS>").
unreal's built in function for this also enables the usage of "localhost" instead of "<IP_ADDRESS>".
some things to note:

DNS lookup is (in the tests i've done) significantly slower than plain IP addresses; this will not change anything if you just input a normal IP address, but if you input a domain name expect a 1-2 second pause on your current thread.
my implementation may not be the best; i put this together quickly just as a quality of life enhancement for a project i'm working on, feel free to reject this pull request if code quality is not up to standard with the rest of the project
this feature may not be desired; as stated earlier, this will add lag if you enter in a domain name instead of an IP address (once again, no change if you use it with a normal IP address) and this may cause undesirable effects for users.

Just saw this pull request, must've slipped by in notifications.
Working around the performance lag, might be relevant in some cases, but if it doesn't impact IP based connection, that's good enough for initial feature addition. I'll go ahead an merge it
Thanks for adding this!


KOL-3516 Fr enhancements

Linked issue(s): https://linear.app/kolena/issue/KOL-3516/enhancements-to-results-page
What change does this PR introduce and why?
Enhancements to results page of FR 1:1 example integration
Please check if the PR fulfills these requirements

[ ] Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Relevant tests for the changes have been added
[ ] Relevant docs have been added / updated

Merged with #229


Fix footer svg bug and upgrade WET

There is currently a bug on the site that downloads the wmms-blk.svg file when loading pages on the ORE. (All pages)
To reproduce, open https://code.open.canada.ca/en/index.html using Chromium, Chrome or Edge browsers.
Firefox does not download the image, but it does not appear on pages.
Looking at the new footer on canada.ca and the design guides, I noticed that the footer image causing the issues went from an <object> to an <img>.

Replaced objects with images (the Canada logo now appears in the footer and on the splash page)
Removed code supporting IE8 (was also removed from canada.ca)
Upgraded to latest version of WET (<IP_ADDRESS>) and set it to always use latest version.

Removed WET version from config file

Added jQuery version to config file

Getting a few things in the console, but seems to be working
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. code.open.canada.ca
The loading of “https://www.canada.ca/etc/designs/canada/wet-boew/js/i18n/en.min.js” in a frame is denied by “X-Frame-Options“ directive set to “SAMEORIGIN“.
en.min.js
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. open-source-codes.html
The loading of “https://www.canada.ca/etc/designs/canada/wet-boew/js/i18n/en.min.js” in a frame is denied by “X-Frame-Options“ directive set to “SAMEORIGIN“.
en.min.js
The loading of “https://www.canada.ca/etc/designs/canada/wet-boew/js/deps/jquery.dataTables.min.js” in a frame is denied by “X-Frame-Options“ directive set to “SAMEORIGIN“.
jquery.dataTables.min.js
The loading of “https://www.canada.ca/etc/designs/canada/wet-boew/js/deps/jquery.magnific-popup.min.js” in a frame is denied by “X-Frame-Options“ directive set to “SAMEORIGIN“.

Thanks @smellems!

Sorry about that
Could be I did'nt use the right CDTS link.
I will try to fix it
I see that This page uses the non standard property “zoom” is also on canada.ca..

Yeah, I think your change is good, I believe CDTS still just has some bad server config 😄 that is causing the CORS (?) messages. Everything seems to be loading OK for me


change version.oh to h_version.txt, update getinfo for v3 fixes

this is due to synapse 3.0 having a whitelist on file types. the name isn't very good but can be changed.

I remember Louka being aware of esoteric file extensions and speaking on the matter so I don't know why they would add a whitelist, but if this is the case, I'll talk to 3ds and Louka about whitelisting the "oh" extension. Until then though, I'll leave this open so you can remove the name changes in your commits & only leave the getinfo fix

oops lol

this probably will never be changed. i feel like it would be easier to change the file to .txt instead of trying to get the .oh file whitelisted. not only that but having this fix implemented would allow people to use hydroxide on v3 instead of having to use a fork.

does synapse v3 have any globals we can use instead of calling identifyexecutor? i don't think a majority of freesploits have that func

I don't think it has anything besides its new custom functions. I can update this to make sure that identifyexecutor exists and if so check.

synapse is gone


100% CPU usage [after sending message] on Swift ARM

Expected behavior
When there's not much going on, little CPU usage. Increase in CPU while there's activity.
Actual behavior
Continuously high CPU usage, even when there's no network traffic.
Steps to reproduce
I'm not sure what exactly triggers the problem in my application, but I've observed the same problem with the chat client. So including those steps here:

Install SwiftARM on a Raspberry Pi (https://swift-arm.com/install-swift/)
Run both chat server and client (swift run NIOChat(Server|Client))
Notice 100% cpu usage on NIOChatClient

SwiftNIO version/commit hash
Tested against version 2.12.0 and master (f44fe0b2042924e3f0392febd8716bbcfc8f36a6).
Swift & OS version (output of swift --version && uname -a)
$ swift --version
Swift version 5.1.3 (swift-5.1.3-RELEASE)
Target: armv6-unknown-linux-gnueabihf

$ uname -a
Linux pi3.local 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux

Flame graph
Some symbols are missing due to perf version mismatch (I think). Both the chat client and my application ("my-home") are included. Attached are the zoomable flame graphs: flame-graphs.zip.

The common cause for this is that we’re spinning in epoll_wait, which implies there’s some I/O event we haven’t processed. This is usually EPOLL_RDHUP. I will do my best to see if I can reproduce this tomorrow, though the fact that this affects a raspberry pi makes life moderately awkward: I’ll see if we can reproduce it in another system.

@Bouke Thanks for the detailed report! As @Lukasa points out, this points to us not properly processing some event so epoll_wait constantly returns again, telling us about the same event again.
If you can, would you mind to attach a few lines of the output of
strace -ff -e trace=epoll_ctl,epoll_wait -p PID_OF_PROCESS

whilst in the 100% CPU spin loop? Also, is this 32 or 64 bit?

 Official builds don't target ARM, nor 32 bit. See also: https://github.com/uraimo/buildSwiftOnARM and https://swift-arm.com)

@Bouke thanks for the fast response. Interestingly, this is the EPOLLIN event which means that we're looking for data to be readable. Could you give us another few lines with this command?
strace -ff -e trace=epoll_ctl,epoll_wait,read -p PID_OF_PROCESS

(the only difference to the previous one is the ,read)

Sure, that would be:
[pid 11841] epoll_wait(5, [{EPOLLIN, {u32=7, u64=7}}], 64, -1) = 1
[pid 11841] read(7, 0x7493f550, 4)      = -1 EINVAL (Invalid argument)

Thank you as well.

einval is a baffling response, why isn’t that causing us to error out?

@Bouke wow, that's read returning EINVAL which as of the docs is
EINVAL
fd is attached to an object which is unsuitable for reading; or the file was opened with the O_DIRECT flag, and either the address specified in buf, the value specified in count, or the current file offset is not suitably aligned.
EINVAL
fd was created via a call to timerfd_create(2) and the wrong size buffer was given to read(); see timerfd_create(2) for further information.

could we have
lsof -p PID

alongside the same strace command? Need to see what fd the one is where read is returning EINVAL.

I think this is what you're asking for?
[pid 12153] read(7, 0x74928550, 4)      = -1 EINVAL (Invalid argument)

COMMAND     PID USER   FD      TYPE DEVICE SIZE/OFF   NODE NAME
NIOChatCl 12133   pi    7u  a_inode   0,11        0   5804 [timerfd]

why isn’t that causing us to error out?

it's this guy: https://github.com/apple/swift-nio/blob/master/Sources/NIO/Selector.swift#L552

thank you @Bouke ! this should allow us to debug it, clearly we're doing the timerfd wrong :)

oooh I think timerfd needs to be 64bit always

yes, this line
_ = Glibc.read(self.timerFD, &val, MemoryLayout<UInt>.size)

must be
_ = Glibc.read(self.timerFD, &val, MemoryLayout<UInt64>.size)

@Bouke if you want, you could make this fix yourself, I think you literally just need to add 64 to this line: https://github.com/apple/swift-nio/blob/master/Sources/NIO/Selector.swift#L552

docs are here:

The file descriptor returned by timerfd_create() supports the following operations:
read(2)
If the timer has already expired one or more times since its settings were last modified using timerfd_settime(), or since the last successful read(2), then the buffer given to read(2) returns an unsigned 8-byte integer (uint64_t) containing the number of expirations that have occurred. (The returned value is in host byte order, i.e., the native byte order for integers on the host machine.)
If no timer expirations have occurred at the time of the read(2), then the call either blocks until the next timer expiration, or fails with the error EAGAIN if the file descriptor has been made nonblocking (via the use of the fcntl(2) F_SETFL operation to set the O_NONBLOCK flag).
A read(2) will fail with the error EINVAL if the size of the supplied buffer is less than 8 bytes.

https://linux.die.net/man/2/timerfd_create

Hmm yeah that makes sense! (Although I haven't the faintest clue what this does)
       read(2)
              If the timer has already expired one or more times since its settings were  last  modified
              using  timerfd_settime(),  or  since the last successful read(2), then the buffer given to
              read(2) returns an unsigned 8-byte integer (uint64_t) containing the number of expirations
              that  have  occurred.   (The returned value is in host byte order—that is, the native byte
              order for integers on the host machine.)

              If no timer expirations have occurred at the time of the read(2),  then  the  call  either
              blocks  until  the  next  timer  expiration,  or  fails  with the error EAGAIN if the file
              descriptor has been made nonblocking (via the use of the fcntl(2) F_SETFL operation to set
              the O_NONBLOCK flag).

              A  read(2) will fail with the error EINVAL if the size of the supplied buffer is less than
              8 bytes.

That fixed the issue for the chat client. I'm now going to test against my own application.

@Bouke by reading 64 bits from the "timerfd" you just tell the kernel "ok, thanks, I have processed the timer you woke me up for". But we didn't read enough and therefore the kernel thought we hadn't processed the timer and told us about the same timer again, straight away, in a loop...

After compiling for what feels like an eternity (the raspberry's not that fast), I can confirm that this is also the fix for my application. Thanks so much everyone!


How do I control whether import in Typescript is counted as a statement?

When I generate a coverage report with Jest for my Typescript project, the import statements at the top of each Typescript file do not count toward the total number of statements in the file.
I'm in the process of setting up a second coverage report for backend code that is exercised by Cypress tests, and have successfully instrumented code using their @cypress/code-coverage module. However, the reports that I get count import statements.
The line that starts up the backend code (source) is:
nyc --silent ts-node --swc scripts/serve_dev.ts

For example, in Jest, the file below has 4 statements. In Cypress, it has 10, because the 5 imports and the final export are counted.
I know this issue involves a number of other libraries besides nyc, so this may not be the right place to ask the question, but I'm hoping there's a way to configure nyc so that the two behaviors match.
import type { VercelRequest, VercelResponse } from '@vercel/node';

import { authCircleAdminMiddleware } from '../../../../api-lib/circleAdmin';
import { ENTRANCE } from '../../../../src/common-lib/constants';
import {
  createUserSchemaInput,
  composeHasuraActionRequestBody,
} from '../../../../src/lib/zod';

import { createUserMutation } from './createUserMutation';

async function handler(req: VercelRequest, res: VercelResponse) {
  const {
    input: { payload: input },
  } = composeHasuraActionRequestBody(createUserSchemaInput).parse(req.body);

  // External Constraint Validation
  // It might be preferable to add this uniqueness constraint into the database
  const { circle_id, address } = input;

  const mutationResult = await createUserMutation(
    address,
    circle_id,
    input,
    ENTRANCE.LINK
  );
  return res
    .status(200)
    .json(mutationResult.insert_users_one ?? mutationResult.update_users_by_pk);
}

export default authCircleAdminMiddleware(handler);

same issue


[1238] Bump govuk frontend to 5.0

Context
Version 5.0.0 of the ruby govuk-components gem supports version 5.0.0 of the govuk-frontend npm package. Both contain breaking changes, and are dependent on each other – so both are being updated at the same time in this PR.
Changes proposed in this pull request
See commits
Guidance to review

Link to Trello card
https://trello.com/c/bjuwB2xq/1238-govuk-logo-update-👑
Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault

 GOVUK logo update 👑

 Apply: Bump Govuk frontend and govuk components to 5.0


test/bpf: Minor Makefile improvements for "make clean"

This PR contains two trivial changes for test/Makefile and test/bpf/Makefile, refer to individual commits for details.

Fix for Travis failures in https://github.com/cilium/cilium/pull/20716

Travis failure is because this branch was not rebased recently. LGTM.


cluster update fails in 3.10.0, 3.9.3

If you have an active AWS support contract, please open a case with AWS Premium Support team using the below documentation to report the issue:
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Before submitting a new issue, please search through open GitHub Issues and check out the troubleshooting documentation.
Please make sure to add the following data in order to facilitate the root cause detection.
Required Info:

AWS ParallelCluster version [e.g. 3.1.1]: 3.10.0
Full cluster configuration without any credentials or personal data.
Cluster name: A2AiClustertesting
Output of pcluster describe-cluster command.

 pcluster describe-cluster -n A2AiClustertesting -r us-east-2
{
  "creationTime": "2024-07-09T18:49:23.141Z",
  "headNode": {
    "launchTime": "2024-07-09T18:53:32.000Z",
    "instanceId": "i-0976556062851f6ca",
    "instanceType": "r6i.xlarge",
    "state": "running",
    "privateIpAddress": "<IP_ADDRESS>"
  },
  "version": "3.10.0",
  "clusterConfiguration": {
    "url": "https://parallelcluster-97a8b56da16cbe1e-v1-do-not-delete.s3.us-east-2.amazonaws.com/parallelcluster/3.10.0/clusters/a2aiclustertesting-3vtysbdo94ne39ev/configs/cluster-config.yaml?versionId=rhu_16ixsYqMF2ctGyWRVVtNGS.jwCQI&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=ASIAZQUXECJHGFFWWCDI%2F20240709%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20240709T212526Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEG0aCXVzLWVhc3QtMiJHMEUCIFlopqMIbJ6IffFlaCwfCvGgUh0RIeHnnlInHBRnLECNAiEAnl07d3CZ39jLquycKjIjGyDcuvvzOR%2FiJ7vAVG%2FBRDAq%2FgIINxAAGgw2NTQyMjU3MDc1OTgiDNQTAke7TLCxmdDjFirbAlrYusjjQ3oD4XjjeNPyzpzxeX6as8JfiomXPRwmzsHOJl7ttg11miKNZ1h4h%2Fgt2MN%2FVucaVJoc%2BnWfHiXHQ8PTfWqjisZ698iw2QrMzLYzatufZSuwpfumz93eH1E8UCtNctjCvUdIqsr6vwTXFKoPqXhKm5KgZ5pfgqK381VNQmFP1xxPqnflpyL0pRnIRBC76XWdaD1zNAZluzp0Zxce75MiXjPT1NPqqu%2Fcux3VSTHgvPbuJfF2yri5pfRpp7n7KiLHgBus8OAfM%2FEwFMLvtnNPP61Hk%2BU0YvWZvuuXF6lLisxqxw4wZYNB0zR7zF3GecXDvuW4ZS%2Bapdme8hzOCk4xh4XG271G1p6Ch%2FG%2BvIWF4roQGgJBu3mOWrOEERzihvgeEDCZUsyIhJnUrJjSPuYsfAlf7aDDvEgru4sW2tKjCsShGpph%2F3cQa2hw4Y1k0DaUSCHPVZ5GMMXVtrQGOqcBeG9WoHb5rdd%2FG0uUI3pfUDWLVFC%2FyswoY22gb0Rkk8GIb3bBSm9SrYZOmxXw5lz%2FOP8X446KfcLMzInE2WeSZ9cijK5RT%2FAywuCQm4yXCglbra%2B0OG0r%2BWc%2BX0MkFDrtepKJRKeMH7pesvzqm8MWkqWpUUC59r9u%2BKa58HZQ6jjx0Icl00MUxa17OqYzQ0vUZqADUxggW9QddoJcdcpKLSlKUkEfjSY%3D&X-Amz-Signature=63e0e16188b1f9e6c696e5b980610f33e775c3fd801df5c1b4d618362eba722a"
  },
  "tags": [
    {
      "value": "branch/release-v4.0",
      "key": "A2AI:a2ai-cloud-version"
    },
    {
      "value": "mig8KP4B19EMB",
      "key": "map-migrated"
    },
    {
      "value": "3.10.0",
      "key": "parallelcluster:version"
    },
    {
      "value": "A2AiClustertesting",
      "key": "parallelcluster:cluster-name"
    },
    {
      "value": "sergey",
      "key": "A2AI:creator"
    },
    {
      "value": "dev",
      "key": "A2AI:a2ai-cloud-env"
    }
  ],
  "cloudFormationStackStatus": "UPDATE_ROLLBACK_COMPLETE",
  "clusterName": "A2AiClustertesting",
  "computeFleetStatus": "RUNNING",
  "cloudformationStackArn": "arn:aws:cloudformation:us-east-2:654225707598:stack/A2AiClustertesting/f531bdf0-3e23-11ef-997c-06835d7b2d0f",
  "lastUpdatedTime": "2024-07-09T19:32:18.912Z",
  "region": "us-east-2",
  "clusterStatus": "UPDATE_FAILED",
  "scheduler": {
    "type": "slurm"
  }
}

[Optional] Arn of the cluster CloudFormation main stack:

Bug description and how to reproduce:
A clear and concise description of what the bug is and the steps to reproduce the behavior.
Cluster repeatedly fails to update and from cloud-formation point of view goes to "rollback complete" . (custom routines do not appear even to get called)
If you are reporting issues about scaling or job failure:
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
For issues with Slurm scheduler, please attach the following logs:

From Head node: /var/log/parallelcluster/clustermgtd, /var/log/parallelcluster/clusterstatusmgtd (if version >= 3.2.0), /var/log/parallelcluster/slurm_resume.log, /var/log/parallelcluster/slurm_suspend.log, /var/log/parallelcluster/slurm_fleet_status_manager.log (if version >= 3.2.0) and/var/log/slurmctld.log.
From Compute node:  /var/log/parallelcluster/computemgtd.log and /var/log/slurmd.log.

If you are reporting issues about cluster creation failure or node failure:
If the cluster fails creation, please re-execute create-cluster action using --rollback-on-failure false option.
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
Please be sure to attach the following logs:

From Head node: /var/log/cloud-init.log, /var/log/cfn-init.log and /var/log/chef-client.log
(attached)
From Compute node:  /var/log/cloud-init-output.log.
NA
logs.tgz <-headnode logs

Additional context:
Any other context about the problem. E.g.:

CLI logs: ~/.parallelcluster/pcluster-cli.log
Custom bootstrap scripts, if any
Screenshots, if useful.

might be related to https://github.com/aws/aws-parallelcluster/issues/6329

a bit of update: i rolled back very same cluster config to PC3.9.3 and tried very same 'pcluster update' successfully.  The issue is clearly PC 3.10.? specific

Hi snemir2,
Can you share your pcluster configuration yaml file? That could help us to reproduce the error.

might be related to https://github.com/aws/aws-parallelcluster/issues/6329

Seems not related.
Best regards,
Xuanqi He

Hi snemir2,
We have been investigating the issue with the failed update of your AWS ParallelCluster. Our initial findings from the cfn-init.log file suggest that a critical point of failure might be related to the portkey.service. The log shows:
              + systemctl restart portkey
              Warning: The unit file, source configuration file, or drop-ins of portkey.service changed on disk. Run 'systemctl daemon-reload' to reload units.
              Job for portkey.service failed because the control process exited with error code.
              See "systemctl status portkey.service" and "journalctl -xeu portkey.service" for details.
              + echo 'skipping portkey restart'
              skipping portkey restart

The failure to restart portkey.service could have impacted subsequent operations, such as accessing the S3 bucket, as seen in the error message below:
Error executing action `run` on resource 'bash[configure_portkey]'
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of "bash"  ----
STDOUT:
STDERR: + mkdir -p /etc/portkey
+ aws s3 ls s3://a2ai-cluster-provision-artifacts-dev-654225707598-us-east-2/a2ai/branch/release-v4.0/portkey/
---- End output of "bash"  ----
Ran "bash"  returned 1

This error might stem from:

S3 Bucket Path or Permissions: The path might be incorrect, or the IAM role might not have the necessary permissions to access the S3 bucket.
Network Configuration Issues: These might involve the ENI (Elastic Network Interface), which could prevent S3 bucket access.

The sequence of events suggests that the portkey.service restart failure may have been the root cause, leading to issues with accessing the S3 bucket. We recommend running systemctl daemon-reload to reload the unit files and then retrying the update process.
To assist us in further diagnosing the problem and providing a resolution, we kindly request the following:

Chef Client Log: Please provide the chef-client.log file from the affected instances for more detailed insights.
ParallelCluster Configuration Files:

The original parallelcluster configuration YAML file before the update.
The updated parallelcluster configuration YAML file used during the failed update.

These details will help us better understand the configuration and environment. We will continue our investigation and keep you informed of any progress.
Best regards,
Xuanqi He

Hi  @hehe7318  -
Thank you for looking into the issue. I am almost sure that the error above you are referring to is a consequence and not the source of the problem. As you can see from the cloud formation/cloud trail, it (for some strange reason) tries to do "runInstances" api call, fails to re-provision ENI on the head node and fails. That causes networking problems on the instance that you are seeing.
FYI -- also seeing this problem on 3.9.3

This is the failed api call from cloudtrail.
{
    "eventVersion": "1.09",
    "userIdentity": {
        "type": "AssumedRole",
        "principalId"<EMAIL_ADDRESS>        "arn"<EMAIL_ADDRESS>        "accountId": "654225707598",
        "sessionContext": {
            "sessionIssuer": {
                "type": "Role",
                "principalId": "AROAZQUXECJHPLP3U6GDM",
                "arn": "arn:aws:iam::654225707598:role/aws-reserved/sso.amazonaws.com/us-east-2/AWSReservedSSO_AWSAdministratorAccess_6cb29b3b61ef9620",
                "accountId": "654225707598",
                "userName": "AWSReservedSSO_AWSAdministratorAccess_6cb29b3b61ef9620"
            },
            "attributes": {
                "creationDate": "2024-08-05T11:03:25Z",
                "mfaAuthenticated": "false"
            }
        },
        "invokedBy": "cloudformation.amazonaws.com"
    },
    "eventTime": "2024-08-05T11:04:28Z",
    "eventSource": "ec2.amazonaws.com",
    "eventName": "RunInstances",
    "awsRegion": "us-east-2",
    "sourceIPAddress": "cloudformation.amazonaws.com",
    "userAgent": "cloudformation.amazonaws.com",
    "errorCode": "Client.InvalidNetworkInterface.InUse",
    "errorMessage": "Interface: [eni-07c94d1a9cd037f2f] in use.",
    "requestParameters": {
        "instancesSet": {
            "items": [
                {
                    "minCount": 1,
                    "maxCount": 1
                }
            ]
        },
        "blockDeviceMapping": {},
        "monitoring": {
            "enabled": false
        },
        "disableApiTermination": false,
        "disableApiStop": false,
        "clientToken": "14c7a9db-2c7d-217d-48d5-262ade2651c6",
        "ebsOptimized": false,
        "tagSpecificationSet": {
            "items": [
                {
                    "resourceType": "instance",
                    "tags": [
                        {
                            "key": "parallelcluster:version",
                            "value": "3.9.3"
                        },
                        {
                            "key": "aws:cloudformation:stack-name",
                            "value": "A2AiClustertesting"
                        },
                        {
                            "key": "aws:cloudformation:stack-id",
                            "value": "arn:aws:cloudformation:us-east-2:654225707598:stack/A2AiClustertesting/4a6dc1c0-50e3-11ef-9498-021a39b766eb"
                        },
                        {
                            "key": "A2AI:creator",
                            "value": "sergey"
                        },
                        {
                            "key": "parallelcluster:networking",
                            "value": "EFA=NONE"
                        },
                        {
                            "key": "parallelcluster:filesystem",
                            "value": "efs=1, multiebs=1, raid=0, fsx=0"
                        },
                        {
                            "key": "Name",
                            "value": "HeadNode"
                        },
                        {
                            "key": "map-migrated",
                            "value": "mig8KP4B19EMB"
                        },
                        {
                            "key": "A2AI:a2ai-cloud-version",
                            "value": "branch/release-v4.0"
                        },
                        {
                            "key": "parallelcluster:cluster-name",
                            "value": "A2AiClustertesting"
                        },
                        {
                            "key": "aws:cloudformation:logical-id",
                            "value": "HeadNode"
                        },
                        {
                            "key": "parallelcluster:node-type",
                            "value": "HeadNode"
                        },
                        {
                            "key": "parallelcluster:attributes",
                            "value": "ubuntu2204, slurm, 3.9.3, x86_64"
                        },
                        {
                            "key": "A2AI:a2ai-cloud-env",
                            "value": "dev"
                        }
                    ]
                }
            ]
        },
        "launchTemplate": {
            "launchTemplateId": "lt-093388f1a2c21ab1a",
            "version": "2"
        }
    },
    "responseElements": null,
    "requestID": "9ea4e084-bdb9-4d8c-a268-f388506ee1ea",
    "eventID": "3a98e509-4f97-4b03-a55f-704a1303439d",
    "readOnly": false,
    "eventType": "AwsApiCall",
    "managementEvent": true,
    "recipientAccountId": "654225707598",
    "eventCategory": "Management"
}

Wow got this issue as well. simply adding a new instanceType for a slurm cluster queue triggers the creation of a new HeadNode in cloudformation.

Apologies for the late reply.
Can you share your original and updated cluster configuration YAML file? That could help us to reproduce the error. I tried to add a new InstanceType and successfully updated my cluster.

Hello! I'm seeing this issue as well when trying to update our customAMI. Have their been any updates here? I'm happy to share our before and after configuration if that would be helpful?

Hello! I'm seeing this issue as well when trying to update our customAMI. Have their been any updates here? I'm happy to share our before and after configuration if that would be helpful?
This is on cluster version 3.9.3
HeadNode:
  CustomActions:
    OnNodeConfigured:
      Script: "s3://OBSCURED/install-pwb-config.sh"
  Iam:
    S3Access:
      - BucketName: OBSCURED
    AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
      - Policy: arn:aws:iam::637485797898:policy/elbaccess-c5f9897
  InstanceType: t3.xlarge
  Networking:
    SubnetId: subnet-0a937bc9f0c04ad8b
    AdditionalSecurityGroups:
      - sg-09e341de4a0f2773e
  LocalStorage:
    RootVolume:
      Size: 120
  SharedStorageType: Efs
  Ssh:
    KeyName: OBSCURED
Image:
  Os: ubuntu2004
  CustomAmi: ami-043eba58b4b8131c6
Region: eu-west-1
Scheduling:
  Scheduler: slurm
  SlurmSettings:
    EnableMemoryBasedScheduling: true
    Database:
      Uri: slurm-OBSCURED.eu-west-1.rds.amazonaws.com:3306
      UserName: slurm_db_admin
      PasswordSecretArn: arn:aws:secretsmanager:eu-west-1:637485797898:secret:OBSCURED
      DatabaseName: slurm
  SlurmQueues:

    - Name: interactive
      ComputeResources:
        - Name: rstudio
          InstanceType: t3.xlarge
          MaxCount: 20
          MinCount: 1
          Efa:
            Enabled: FALSE
      CustomSlurmSettings:
        OverSubscribe: FORCE:2
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

    - Name: all
      ComputeResources:
        - Name: rstudio
          InstanceType: t3.xlarge
          MaxCount: 10
          MinCount: 0
          Efa:
            Enabled: FALSE
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

    - Name: gpu
      ComputeResources:
        - Name: large
          InstanceType: p3.2xlarge
          MaxCount: 1
          MinCount: 0
          Efa:
            Enabled: FALSE
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

LoginNodes:
  Pools:
    - Name: login
      Count: 2
      InstanceType: t3.xlarge
      Networking:
        AdditionalSecurityGroups:
          - sg-09ca531e5331195f1
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b
      Ssh:
        KeyName: OBSCURED

DevSettings:
  Timeouts:
    HeadNodeBootstrapTimeout: 7200  # timeout in seconds
    ComputeNodeBootstrapTimeout: 7200  # timeout in seconds

SharedStorage:
  - MountDir: /home
    Name: home
    StorageType: FsxLustre
    FsxLustreSettings:
      StorageCapacity: 1200
      DeploymentType: SCRATCH_2
  - MountDir: /opt/rstudio
    Name: rstudio
    StorageType: Efs
  - MountDir: /opt/apps
    Name: appstack
    StorageType: Efs
    EfsSettings:
      FileSystemId: fs-OBSCURED

DirectoryService:
  DomainName: OBSCURED
  DomainAddr: ldap://OBSCURED
  PasswordSecretArn: arn:aws:secretsmanager:eu-west-1:637485797898:secret:OBSCURED
  DomainReadOnlyUser: cn=Administrator,cn=Users,dc=pwb,dc=posit,dc=co
  GenerateSshKeysForUsers: true
  AdditionalSssdConfigs:
    override_homedir : /home/%u
    ldap_id_use_start_tls : false
    ldap_tls_reqcert : never
    ldap_auth_disable_tls_never_use_in_production : true

Tags:
  - Key: rs:environment
    Value: development
  - Key: rs:owner
    Value: OBSCURED
  - Key: rs:project
    Value: solutions
  - Key: rs:subsystem
    Value: ukhsa

After Update:
HeadNode:
  CustomActions:
    OnNodeConfigured:
      Script: "s3://OBSCURED/install-pwb-config.sh"
  Iam:
    S3Access:
      - BucketName: OBSCURED
    AdditionalIamPolicies:
      - Policy: arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
      - Policy: arn:aws:iam::637485797898:policy/elbaccess-c5f9897
  InstanceType: t3.xlarge
  Networking:
    SubnetId: subnet-0a937bc9f0c04ad8b
    AdditionalSecurityGroups:
      - sg-09e341de4a0f2773e
  LocalStorage:
    RootVolume:
      Size: 120
  SharedStorageType: Efs
  Ssh:
    KeyName: OBSCURED
Image:
  Os: ubuntu2004
  CustomAmi: ami-092b5633346d89b54
Region: eu-west-1
Scheduling:
  Scheduler: slurm
  SlurmSettings:
    EnableMemoryBasedScheduling: true
    Database:
      Uri: slurm-OBSCURED.eu-west-1.rds.amazonaws.com:3306
      UserName: slurm_db_admin
      PasswordSecretArn: arn:aws:secretsmanager:eu-west-1:637485797898:secret:OBSCURED
      DatabaseName: slurm
  SlurmQueues:

    - Name: interactive
      ComputeResources:
        - Name: rstudio
          InstanceType: t3.xlarge
          MaxCount: 20
          MinCount: 1
          Efa:
            Enabled: FALSE
      CustomSlurmSettings:
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

    - Name: all
      ComputeResources:
        - Name: rstudio
          InstanceType: t3.xlarge
          MaxCount: 10
          MinCount: 0
          Efa:
            Enabled: FALSE
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

    - Name: gpu
      ComputeResources:
        - Name: large
          InstanceType: p3.2xlarge
          MaxCount: 1
          MinCount: 0
          Efa:
            Enabled: FALSE
      CustomActions:
        OnNodeConfigured:
          Script: "s3://OBSCURED/config-compute.sh"
      Iam:
        S3Access:
          - BucketName: OBSCURED
      Networking:
        PlacementGroup:
          Enabled: FALSE
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b

LoginNodes:
  Pools:
    - Name: login
      Count: 2
      InstanceType: t3.xlarge
      Networking:
        AdditionalSecurityGroups:
          - sg-09ca531e5331195f1
        SubnetIds:
          - subnet-0a937bc9f0c04ad8b
      Ssh:
        KeyName: OBSCURED

DevSettings:
  Timeouts:
    HeadNodeBootstrapTimeout: 7200  # timeout in seconds
    ComputeNodeBootstrapTimeout: 7200  # timeout in seconds

SharedStorage:
  - MountDir: /home
    Name: home
    StorageType: FsxLustre
    FsxLustreSettings:
      StorageCapacity: 1200
      DeploymentType: SCRATCH_2
  - MountDir: /opt/rstudio
    Name: rstudio
    StorageType: Efs
  - MountDir: /opt/apps
    Name: appstack
    StorageType: Efs
    EfsSettings:
      FileSystemId: fs-OBSCURED

DirectoryService:
  DomainName: OBSCURED
  DomainAddr: ldap://OBSCURED
  PasswordSecretArn: arn:aws:secretsmanager:eu-west-1:637485797898:secret:OBSCURED
  DomainReadOnlyUser: cn=Administrator,cn=Users,dc=pwb,dc=posit,dc=co
  GenerateSshKeysForUsers: true
  AdditionalSssdConfigs:
    override_homedir : /home/%u
    ldap_id_use_start_tls : false
    ldap_tls_reqcert : never
    ldap_auth_disable_tls_never_use_in_production : true

Tags:
  - Key: rs:environment
    Value: development
  - Key: rs:owner
    Value: OBSCURED
  - Key: rs:project
    Value: solutions
  - Key: rs:subsystem
    Value: ukhsa


Reload takes > 60 seconds

Hi everyone!
Since I updated werkzeug to 0.10.1 this morning reloader stopped working. Is any specific configuration required besides installing watchdog?
I run with:
run_simple(
        hostname='<IP_ADDRESS>',
        port=5000,
        application=app,
        use_reloader=True,
        use_debugger=True,
        reloader_type='watchdog'
    )

# * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
# * Restarting with inotify reloader

I'm under vagrant and tried both with and without NFS to no success.

Ok, I did some research and can say that reload is actually happening. The thing is it watchdog-reload won't work under vagrant, virtualbox, and probably docker as well. This is not the reloader's fault, just how the underlying inotify works.
For reload to work under guest os you need to use stat reloader. It actually takes about 90 seconds to do a single reload with stat reloader. That is for us and our project. The exact time will depend on the number of files in your project.
There is this pull request mitsuhiko/werkzeug#669 that will allow you to regulate what files are being watched. Not yet on PyPi though.
Right now we are rolling or own reload solution will poke.

Please continue in https://github.com/mitsuhiko/werkzeug/issues/682, we did some major changes to the reloader which could have caused serious regressions.


feat: Tuples

Resolves #5

Bundle size comparison

size comparison

browser
uncompressed 5 kB -- gzipped 1.84 kB --

main
uncompressed 4.87 kB -- gzipped 1.77 kB --

module
uncompressed 4.77 kB -- gzipped 1.77 kB --

Speed comparison
PR

library
relative speed
operations per second
avg. operation time

@typeofweb/schema@pr-branch
+8.01%
(1,584,144 rps)
(avg: 631ns)

@typeofweb/schema@base-branch
0%
(1,466,603 rps)
(avg: 681ns)

<EMAIL_ADDRESS>-92.94%
(103,584 rps)
(avg: 9μs)

<EMAIL_ADDRESS>-96.69%
(48,506 rps)
(avg: 20μs)

<EMAIL_ADDRESS>-96.7%
(48,427 rps)
(avg: 20μs)

<EMAIL_ADDRESS>-98.71%
(18,912 rps)
(avg: 52μs)

Bundle size comparison

size comparison

browser
uncompressed 5 kB -- gzipped 1.84 kB --

main
uncompressed 4.87 kB -- gzipped 1.77 kB --

module
uncompressed 4.77 kB -- gzipped 1.77 kB --

Speed comparison
PR

library
relative speed
operations per second
avg. operation time

@typeofweb/schema@pr-branch
+8.01%
(1,584,144 rps)
(avg: 631ns)

@typeofweb/schema@base-branch
0%
(1,466,603 rps)
(avg: 681ns)

<EMAIL_ADDRESS>-92.94%
(103,584 rps)
(avg: 9μs)

<EMAIL_ADDRESS>-96.69%
(48,506 rps)
(avg: 20μs)

<EMAIL_ADDRESS>-96.7%
(48,427 rps)
(avg: 20μs)

<EMAIL_ADDRESS>-98.71%
(18,912 rps)
(avg: 52μs)


feat: move dataplane list and config into overviews

Changes
refactor(dataplanes): use AppCollection in list view directly
refactor(dataplanes): drop unnecessary /of/:type
feat(delegated-gateways): move dataplane list into overview
feat(services): move dataplane list and config into overview
feat(external-services): move config into overview
chore(dataplanes): remove DataPlaneList
Signed-off-by: Philipp Rudloff<EMAIL_ADDRESS>Resolves #2209.
Notes

Since none of the views showing Dataplane lists do so without being in context of a single service type, the /of/:type bit for the corresponding data source isn’t necessary anymore. Consequently, the filter widget has also been removed from those views. Also, the Type and Services columns were removed from those views.
Generally, since we show the Dataplane lists with a varying columns, I decided to inline the AppCollection abstraction DataPlaneList here.

Shouldn't I be able to see the [Internal/External] services toggle on here?

Shouldn't I be able to see the [Internal/External] services toggle on here?

You’re right. This regressed with https://github.com/kumahq/kuma-gui/pull/2186. I’m working on a fix.

@johncowen This was rebased now after merging both #2186 and #2215 and can be re-reviewed.


Set up Ruby

Repetition stinks. Currently, every user has to repeat the call to ruby/setup-ruby; we should do that for them.
Once https://github.com/ruby/setup-ruby/issues/58 is done, adopt the solution here.

After a promising PoC #612, I'm now watching #646 to see when we can "properly" sub-call setup-ruby.


Layout issue in concert with ZSH theme

I'm experiencing a layout issue using OhMyZSH w/ ZSH_THEME="bureau".

In Hyperterm the cursor appears before rather than after $. Appearance in iTerm 2 & Terminal.app:

@jameswomack Do you still have this issue? I just tried it and here is the result.

Closing this for inactivity. If it comes back feel free :)

@ppot thanks. It's fixed now!


Use antigen for zsh

Use antigen for zsh to manage plugins instead of oh-my-zsh, seems to be a better solution for managing plugins.
https://github.com/zsh-users/antigen

take care about the theme I'm using when not using oh my zsh anymore.

change to antigen seemed to work


[Bug]: TypeCastError when using symbols defined in outer query action in an inner query action

Description
TypeCastError when using symbols defined in outer query action in an inner query action.
Steps to Reproduce
public function main() {
   int[] arr = [];
    from var j in 1 ... 5
    do {
        from var k in 5 ... 7
        do {
            var x = from var t in 3 ... 4 select k; //works with 'j' instead of 'k'
        };
    };
}

error: {ballerina}TypeCastError {"message":"incompatible types: '()' cannot be cast to 'int'"}
        at ballerina.lang.query.0._DoFunction:process(types.bal:691)
           ballerina.lang.query.0:$anon$method$delegate$_StreamFunction.process$0(types.bal:93)

Affected Version(s)
2201.4.0
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
#32710
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

cc @poorna2152


<EMAIL_ADDRESS>Update autoupdate hash

[x] I have read the Contributing Guide.

Add hash source.

/verify


chore(libs): apply code formatting

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version
/area build
/area CI
/area driver-kmod
/area driver-bpf
/area driver-modern-bpf
/area libscap-engine-bpf
/area libscap-engine-gvisor
/area libscap-engine-kmod
/area libscap-engine-modern-bpf
/area libscap-engine-nodriver
/area libscap-engine-noop
/area libscap-engine-source-plugin
/area libscap-engine-savefile
/area libscap
/area libpman
/area libsinsp
/area tests
/area proposals

Does this PR require a change in the driver versions?
No

What this PR does / why we need it:
This applies code linting/formatting to the entire codebase of the libs
Which issue(s) this PR fixes:

Fixes #381
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

LGTM label has been added.  Git tree hash: 112ee3ebfbaf6151e8f670d65dd46d7fecf48b28

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, poiana
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@falcosecurity/libs-maintainers please note that from now on all the PRs will need a rebase on master.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, poiana
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

For every one using vs code i suggest the following:

install clang-format and cmake-format extensions (https://marketplace.visualstudio.com/items?itemName=xaver.clang-format and https://marketplace.visualstudio.com/items?itemName=cheshirekow.cmake-format)
create a file .vscode/settings.json or update it with the following

	"editor.formatOnSave": true,
	"cmakeFormat.exePath": "<your-path>",
	"clang-format.executable": "<your-path>"

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, Molter73, poiana
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,Molter73]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold
Let's go!


Build info in status panel shows 'Release' instead of 'URL' install

May have something to do with #246

Will be fixed by #249

Fixed by #249


Branch should check for truthy values

The branch function should accept any truthy value instead of only true.

Fixed in v0.12.1


Set end bar to end of static data

1.618 is approximately the golden ratio, which is allegedly meant to produce a pleasingly sized rectangle. The choice is relatively arbitrary for now.

1.618 is approximately the golden ratio, which is allegedly meant to produce a pleasingly sized rectangle. The choice is relatively arbitrary for now.

Nice idea. I think it would be worth assigning the value to a var with an appropriate name, so it doesn't seem so arbitrary (at least to me!), or possibly add a comment.


[HOLD for payment 2023-08-28] [$1000] [Custom Status] Display status emojis in chats

Part of the Custom Status project
Main issue: https://github.com/Expensify/App/issues/16350
Doc: https://docs.google.com/document/d/1uPS24aoRWE45piaTvr0XvrgV1lK3lSjieG3sD5ZPfQg/edit#bookmark=id.dm0yu67h9vq8
Project: https://github.com/orgs/Expensify/projects/59/views/1
Display status emojis in chats
This issue will cover showing a user's status in chats. When a user has a status set, their chosen emoji will show up next to their name. On web/desktop this will be hoverable and have a tooltip.

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0101ef684f004accb9
Upwork Job ID:<PHONE_NUMBER>692476928
Last Price Increase: 2023-08-16

No update here, but work has started on the base PR!

Base PR is in review!

@stitesExpensify Assign me issue when you get a chance thanks!

Okay so this isn't a typical issue - looks like Margelo implementation and an internally created issue. Only payment that needs to be done would be fore @Santhosh-Sellavel for reviewing. You can make a request in NewDot for the standard $1k afaict.

Leaving this for @JmillsExpensify to confirm for payment then we can close

Requested on ND

Reviewed the details for @Santhosh-Sellavel. $1,000 payment approved via NewDot based on BZ summary.


routerrpc: pass in probability source

Fixes  #4594.
When using routerrpc.EstimateRouteFee, the routing algorithm is invoked without setting a probability source which results in a crash in the router.

Hm, so this never worked? 🤔

Hm, so this never worked? 🤔

No it worked in the past, but updates to the mission control system didn't also update this call as there're no integration tests for tis call as is.


Create 1.25.1 release with omnisharp-roslyn updated to 1.39.2

There hasn't been an update in almost half a year, and my razor/blazor work is painful... so I'm looking forward to upgrading. When is this planned to be released as non-beta?

I expect in the next week or two.  We're currently waiting on new Razor bits (to hopefully reduce some of the pain!) before we publish a non-beta release.


0.50.0-rc.2 not working with axios in release build

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment

Environment:
OS:  macOS High Sierra 10.13
Node:  8.8.1
Yarn:  1.2.1
npm:  5.4.2
Watchman:  4.9.0
Xcode:  Xcode 9.0.1 Build version 9A1004
Android Studio:  2.3 AI-162.4069837
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.50.0-rc.2 => 0.50.0-rc.2
Steps to Reproduce

After upgrading my project to RN 0.50.0-rc.2, all axios call stopped working in release build (they work well in development build and RN 0.49.5).
    try {
      const res = await axios.get('/news', {
        params: { limit: 20, offset: 0 }
      })
      console.log(res)
    } catch (error) {
      window.alert(error)
    }

I got this exception:

This only happens on RN 0.50.0-rc.2 & production build.
After I changed this line in axios to if (true) { then it works again in production build. I don't know why the assertion failed in production build. When I use window.alert(typeof XMLHttpRequest) in my own code it outputs 'function', but it outputs 'undefined' in axios code.

Here is a workaround if you face the same problem.
axios.defaults.adapter = require('axios/lib/adapters/xhr') // Force set to xhr adapter

I don't know if this is a bug of axios or React Native, but everything was working properly in previous version of React Native.

+1 same problem here

Setting the metro-bundler version to 0.20.1 like seems to fix this issue for me
"resolutions": {
    "react-native/metro-bundler": "0.20.1"
}

@vtrrsl where is setting

@Manweill in package.json. Anyway you can try update RN to version 0.50.3, they are saying that its fixed, but haven't tried it yet.

@alimek Yes, it's ok in rn 0.50.3。


"pool name missing" error results in HTTP 500 response

A zync community user operating a lake service with Zed v1.5.0 shared the following partial log message.
:"warn","ts":1679410513.6617484,"logger":"core","msg":"Error","request_id":"2NKQtkFgSEzB6QiH4D8SWDaPEeS","status":500,"error":"pool name missing","stacktrace":"
github.com/brimdata/zed/service.(*ResponseWriter).Error\n\t/go/pkg/mod/github.com/brimdata/zed@v1.5.0/service/request.go:250\ngithub.com/brimdata/zed/service.ha
ndleQuery\n\t/go/pkg/mod/github.com/brimdata/zed@v1.5.0/service/handlers.go:58\ngithub.com/brimdata/zed/service.(*Core).handler.func1\n\t/go/pkg/mod/github.com/
brimdata/zed@v1.5.0/service/core.go:182\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2109\ngithub.com/rs/cors.(*Cors).Handler.func1\n
\t/go/pkg/mod/github.com/rs/cors@v1.8.0/cors.go:219\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2109\ngithub.com/brimdata/zed/servic
e.panicCatchMiddleware.func1.1\n\t/go/pkg/mod/github.com/brimdata/zed@v1.5.0/service/middleware.go:92\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/h
ttp/server.go:2109\ngithub.com/brimdata/zed/service.accessLogMiddleware.func1.1\n\t/go/pkg/mod/github.com/brimdata/zed@v1.5.0/service/middleware.go:72\nnet/http
.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2109\ngithub.com/brimdata/zed/service.requestIDMiddleware.func1.1\n\t/go/pkg/mod/github.com/brimd
ata/zed@v1.5.0/service/middleware.go:28\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2109\ngithub.com/gorilla/mux.(*Router).ServeHTTP
\n\t/go/pkg/mod/github.com/gorilla/mux@v1.7.5-0.20200711200521-98cb6bf42e08/mux.go:210\ngithub.com/brimdata/zed/service.(*Core).ServeHTTP\n\t/go/pkg/mod/github.
com/brimdata/zed@v1.5.0/service/core.go:228\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2947\nnet/http.(*conn).serve\n\t/usr/local
/go/src/net/http/server.go:1991"}

This "pool name missing" error should elicit an HTTP 400 response rather than a 500 response.

See #4616 for a related issue that might make this kind of error easier to debug in the field.

Verified in Zed commit 4bebb84.
At commit 0190366 that was right before the changes landed in the linked PR:
$ zed -version
Version: v1.8.0-9-g01903666

$ zed query '*'
status code 500: pool name missing

Now at commit 4bebb84 we see:
$ zed -version
Version: v1.8.0-10-g4bebb845

$ zed query '*'
status code 400: pool name missing

This also turns down the severity of the log message in the Zed service log from the previous warn to info.
{"level":"info","ts":1685724333.797872,"logger":"http.access","msg":"Request completed","request_id":"2QeqKoUK9wjTjpkaZGf6YAwoatr","host":"localhost:9867","method":"POST","proto":"HTTP/1.1","remote_addr":"[::1]:51542","request_content_length":-1,"url":"/query?ctrl=T","elapsed":0.00144359,"response_content_length":72,"status_code":400}

Thanks @nwt!


Robustificate MAL imports

So this is solving a few different problems with MAL imports:

Anime titles which have ampersands ("Panty & Stocking with Garterbelt" for example) are apparently sometimes not escaped by MAL exports.  This is fixed using a gsub to escape them.
Lists without any entries would result in an "Invalid list type" error in the sidekiq worker.  This is fixed by detecting that case in the controller.
Users could upload random non-MAL XML files and it would break in the sidekiq worker.  This is fixed by checking for <myanimelist> in the XML, which should sniff out all but the weirdest cases.

In all of these cases, the error message will now be passed back to the user to remedy.

:100: lgtm


[match] refactor match to use keychain_path 2/3

This series of PR tries to solve following issue:

https://github.com/fastlane/fastlane/pull/7048

This is PR 2/3
as described the path is to move keychain_path to fastlane_core:

PR 1/3 -> move keychain_path to fastlane_core #7075
PR 2/3 -> refactor match to use fastlane_core keychain_path #7076
PR 3/3 -> refactor unlock_keychain to use fastlane_core keychain_path #7077

needs to be merged in the right order

Linking back here to the original issue: #7046

@hjanuschka fastlane_core 0.57.0 has been released. Can you rebase this on master so that CI will pass?

@asfalcone done, tests should pass now ☮


boards: stm32: Remove useless CONFIG_BOARD_FOO from _defconfig files

CONFIG_BOARD_FOO is enabled in a number of board *_defconfig files
although it is useless as set by cmake.
Clean it from STM32 impacted boards.
Signed-off-by: Erwan Gouriou<EMAIL_ADDRESS>

Mergeing by hand as this will always timeout.


Demonstrate Fault Tolerance feature

Conference app needs to demonstrate Fault Tolerance feature

Andy Guibert is working on updating vote service to demonstrate FT on WebSphere Liberty.


[Feature-Request] Support IMX378 and 2x AR0234 Color Sensors

Start with the why:
I've designed a robot that uses a FFC-3P board with two AR0234 color cameras with wide angle lenses to generate a depth map, and an IMX378 as a centre camera with a narrow FOV for more detailed imagery for object recognition. This means I can generate a coloured 3d point cloud of the wider area rather than being limited to the narrow field from the centre camera. Currently this is flagged as an unsupported combination as there is no model defined for it.
As per this post.
This is a product prototype that I'm intending to make commercially available and hope to use the FFC-3P, or possible RVC4 powered successor, at it's core.
Move to the what:
I would like a model generated from this camera combination, as I understand it this requires access to proprietary tools which aren't public.
Move to the how:
As above, the tools are proprietary so I've not knowledge of how they work. If there was an option to share them, I'd be happy to help with this however.

Hi @kneave - please reachout to our support directly for this enabling this custom tuning combination

Ah, ok, I was told to open a feature request on the forums. Want me to leave this open or close it?

Feel free to leave open for the time being

Thanks, fingers crossed as it'd be handy having the IMX378 in the centre spot rather than needed to get a third AR0234!


build(docs): serve docs from docs folder

This PR changes serving documentation from the repo root folder to the ./docs folder.
Closes #32

Replaced with https://github.com/ametnes/nesis/pull/37


Feat: Forgot Backend

Describe the feature
@SUGAM-ARORA I want to set up the backend of Forgot Page. Kindly assign me this issue.
Add ScreenShots

Record

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

@Ojas-Arora Issue assigned to you


Feature 11 sphinx doc

Pull Request Testing

[x] Describe testing already performed for these changes:

Viewed Sphinx pages on temporary hosting site:
https://ral.ucar.edu/staff/jpresto/work/METexpress_jpresto/index.html

[x] Recommend testing for the reviewer to perform, including the location of input datasets:

View Sphinx pages on temporary hosting site:
https://ral.ucar.edu/staff/jpresto/work/METexpress_jpresto/index.html

[x] Will this PR result in changes to the test suite? [No]

[x] After merging, should the reviewer DELETE the feature branch from GitHub? [Yes]

Pull Request Checklist
See the METplus Workflow for details.

[x] Complete the PR definition above.
[x] Ensure the PR title matches the feature or bugfix branch name.
[x] Define the PR metadata, as permissions allow.
Select: Reviewer(s), Project(s), and Milestone (No applicable Project available)
[x] After submitting the PR, select Linked Issues with the original issue number.

@randytpierce @mollybsmith-noaa I've done the review & merge to the development branch. Would one of you like to do the review and merge to the master branch?

The documentation has been merged to the master branch.


fix: updatedAt -> modifiedAt

Proposed changes
This pr fixes the invalid column name for the CSV parser in Chapter 8. The author is using updatedAt property. However, throughout the chapter, we only use the modifiedAt field

According to issue #53


Show N last added bookmarks by default

Instead of blank screen retrieve last N added bookmarks

Fixed in #42


Naming "spectral"

At the moment we have the within the GeoSpectral struct a SpectralTransform struct called spectral such that one can do
@unpack spectral = model_setup.geospectral

as well as the function spectral that does a spectral transform, i.e. double naming. @unpacking the spectral overwrites the available function in local scope. In most cases this isn't an issue as we only use the in-place function spectral! within the code hence no conflict, but for clarity and bug prevention, we should resolve that.

One way could be to change
struct GeoSpectral{NF<:AbstractFloat}
    geometry::Geometry{NF}
    spectral::SpectralTransform{NF}
end

to
struct GeoSpectral{NF<:AbstractFloat}
    geometry::Geometry{NF}
    spectral_trans::SpectralTransform{NF}
end


Fix typo in Setspn command

Fix typo in command according to docs
Fixes #19790

@JunTaoLuo probably has a better idea of whats correct

@JunTaoLuo quick review please.

I'm inclined to not make this change. I don't think the user name has to be the same as the server name, even if that is usually the case.

@JunTaoLuo
Then, please, close issue #19790 with explonation


dnf_helper.py in Dnf provider fails to run due to SIGCHLD hander

Description
When the Dnf provider runs the python helper script dnf_helper.py it exits right after the call the base.fill_sack().  Removing the SIGCHLD handler fixes the problem.
https://github.com/chef/chef/blob/0764bf5de8f21de13fb8e25373af5667b7c22771/lib/chef/provider/package/dnf/dnf_helper.py#L75
Found on Fedora 26
Chef Version
12.19.36
Platform Version
Fedora 26 x86_64
Replication Case
compile time recipe exposed this for me.
50:  if node.linux? # ~FC019, ~FC023
51:    # The Linux plugins require dmidecode
52:    package 'dmidecode' do
53:      action :nothing
54>>   end.run_action(:upgrade)
55:  end
Client Output
https://gist.github.com/nemith/cc6e53e5713cc7c147cc7e1c6197263e

Also why is the signal handler exit with an exit code of 0 and not a non-zero value?

it probably should exit -1 or something, but the only thing that talks to it is the dnf package provider which doesn't care.

so offhand this morning i don't understand what the SIGCHLD handler has to do with the EOFError the chef run spits out.

I am guessing the dnf package is starting a child process during the fill_sack() call.  The child process ends and a SIGCHLD is sent to the dnf_helper python process, it is caught in the signal handler and the exits without any output.
I have no idea why SIGCHLD is being handled at all here, it makes no sense to exit on that call in any use case that I can think of.
Since my rule is forced to run at compile time i am getting the EOFError.  If it was properly running at runtime i am sure the error would be more appropriate.
This showed up after a system upgrade or something else that caused dnf to start a child process.  I am not sure exactly the trigger.

oh the default is to ignore it, right...


chore: Image source for image

This PR
Adds the image source content of the PR https://github.com/open-feature/flagd/pull/310. Source can be used with excalidraw

Force-merging since this is just source for an already-reviewed png.


Make log message more obvious

Cron Jobs - add job with name: seemed like a warning that some action needs to be taken ¯\_(ツ)_/¯

Coverage decreased (-0.2%) to 91.294% when pulling 26dbc7c52a008a8fffbba7fd49d952db11390c9b on arrrnas:patch-1 into 6a0aeff6c900f3b7246734282f6869c61e1d5b4e on ondrejbartas:master.

@ondrejbartas @honzasterba what do you think about this one?
I understand @mathieujobin's concern, but consistency is also good!

Looks good to me.
I don't think log messages should be treated as API.


Error [ERR_REQUIRE_ESM]: require() of ES Module NodeJS

I am getting the following error when using NodeJS:
Error [ERR_REQUIRE_ESM]: require() of ES Module path\node_modules\mongo-object\dist\index.js from path\node_modules\simpl-schema\dist\cjs\clean.js not supported.
This happens when I try to pass SimpleSchema as a class constructor property:
...
import type SimpleSchema from 'simpl-schema';
...

class Myclass {
  private simpleschema: typeof SimpleSchema;
  ...
  contructor({ schema: typeof SimpleSchema }){
    this.simpleschema = schema;
  }
  ...
}

somewhere in my code:
...
import SimpleSchema from 'simpl-schema';
...

const do = new MyClass({
  schema: SimpleSchema // <- here is where the error occurs
});

same issue here in a meteor project where I use the native mongo driver in parallel to the meteor one.

I also have this issue in a Meteor project.

In the issue description, it seems like you would not want to do both import type and typeof. Did you try with just import SimpleSchema?
That problem may be unrelated to the error, though. It seems as though all reports are in Meteor apps? Maybe there is some extra config necessary to tell Meteor how to import this properly (commonjs vs ESM)

While debugging another issue, I think I have more insight into this one. simpl-schema is published with support for either esm or cjs, but mongo-object is esm-only. So this error happens when Node.js tries to go from cjs in simpl-schema to esm in mongo-object. Since I also maintain mongo-object, I'll resolve this by publishing that package with support for both, same as this package.

Should be fixed in 3.4.1


Unable to add multiple endpoint_groups from different region in global-accelerator's listener

Description
I am unable to add multiple endpoint_groups from different region in my global-accelerator module.
Currently it only support adding one single region and there is no documentation specify way to configure multiple endpoint groups.
The result shows resources are created successfully but endpoint groups didn't get added into the listener.
Versions

Module version [Required]:
1.1.0
Terraform version:
1.3.0
Provider version(s):
4.31.0

Reproduction Code [Required]
module "us-west-2-mods" {
source = "./us-west-2"
}
module "eu-west-2-mods" {
source = "./eu-west-2"
}
module "global-accelerator" {
source  = "terraform-aws-modules/global-accelerator/aws"
version = "1.1.0"
name =  "${var.business_divsion}-${var.environment}-GlobalAccelerator-1"
flow_logs_enabled = false
listeners = {
    listener_1 = {
    client_affinity = "NONE"

    endpoint_group = {
        health_check_port             = 53
        health_check_protocol         = "TCP"
        health_check_path             = "/"
        health_check_interval_seconds = 30
        health_check_timeout_seconds  = 5
        healthy_threshold_count       = 3
        unhealthy_threshold_count     = 3
        traffic_dial_percentage       = 100
        endpoint_group_region         = var.aws_region

        # Health checks will show as unhealthy in this example because there
        # are obviously no healthy instances in the target group
        endpoint_configuration = [{
        client_ip_preservation_enabled = false
        endpoint_id                    = module.us-west-2-mods.udp_nlb_arn
        weight                         = 128
        }
        ]
    }

    endpoint_group = {
        health_check_port             = 53
        health_check_protocol         = "TCP"
        health_check_path             = "/"
        health_check_interval_seconds = 30
        health_check_timeout_seconds  = 5
        healthy_threshold_count       = 3
        unhealthy_threshold_count     = 3
        traffic_dial_percentage       = 100
        endpoint_group_region         = var.aws_region_2

        # Health checks will show as unhealthy in this example because there
        # are obviously no healthy instances in the target group
        endpoint_configuration = [{
        client_ip_preservation_enabled = false
        endpoint_id                    = module.eu-west-2-mods.udp_nlb_arn
        weight                         = 128
        }
        ]
    }

    port_ranges = [
        {
        from_port = 53
        to_port   = 53
        }
    ]
    protocol = "UDP"
    }

    listener_2 = {
        client_affinity = "NONE"

        endpoint_group = {
            health_check_port             = 53
            health_check_protocol         = "TCP"
            health_check_path             = "/"
            health_check_interval_seconds = 30
            health_check_timeout_seconds  = 5
            healthy_threshold_count       = 3
            unhealthy_threshold_count     = 3
            traffic_dial_percentage       = 100
            endpoint_group_region         = var.aws_region

            # Health checks will show as unhealthy in this example because there
            # are obviously no healthy instances in the target group
            endpoint_configuration = [{
            client_ip_preservation_enabled = false
            endpoint_id                    = module.us-west-2-mods.tcp_nlb_arn
            weight                         = 128
            }
            ]
        }

        endpoint_group = {
            health_check_port             = 53
            health_check_protocol         = "TCP"
            health_check_path             = "/"
            health_check_interval_seconds = 30
            health_check_timeout_seconds  = 5
            healthy_threshold_count       = 3
            unhealthy_threshold_count     = 3
            traffic_dial_percentage       = 100
            endpoint_group_region         = var.aws_region_2

            # Health checks will show as unhealthy in this example because there
            # are obviously no healthy instances in the target group
            endpoint_configuration = [{
            client_ip_preservation_enabled = false
            endpoint_id                    = module.eu-west-2-mods.tcp_nlb_arn
            weight                         = 128
            }
            ]
        }

        port_ranges = [
            {
            from_port = 53
            to_port   = 53
            }
        ]
        protocol = "TCP"
    }
}

}
Steps to reproduce the behavior:
I am deploying it following regular Terraform deployment steps.
Expected behavior
I am expecting my global accelerator can add multiple endpoint groups from different region, which is a behavior can be configured on AWS GUI.
Actual behavior
Unable to add more than one endpoint groups into listener.
 Resources: 1 added, 1 changed, 0 destroyed.
Additional context

Hi @ antonbabenko, this is really a useful feature, I can help for this.
I had forked and implemented the feature. It can need to be polished more, but it is working for my case.
SEE: https://github.com/chrisduong/terraform-aws-global-accelerator/blob/support-multiple-endpoints/examples/multiple-endpoints/main.tf#L135-L182

thanks @chrisduong - let me take a look today


fix: renamed font color attribute in Track.java

@iamareebjamal @Shailesh351
In Track.java I just found out that we were using "font-color" instead of "font_color".

@arp95 Your local.properties not included in the commit

@iamareebjamal
just saw that. sorry removing it.


More axis support

Hello!
While I was trying to emulate an XBOX 360 Controller with the help of VJoy, I stumbled upon a problem - not enough Axises. It seems that XBOX 360 controller uses Axises 9 and 10 for the separate Left and Right Trigger alongside of using the Axis 3 (Z axis) for both of them. Using only Axis 3 is not enough because when both triggers are simultaneously pressed the axis can't have two states at the same time.
Is it possible to implement into VJoy support for 2 more axises?

I'm not involved in this project, but can speak from experience as a user. There's a separate xbox-specific branch and set releases for use with Xbox controllers. They emulate XInput devices, which is the same as normal Xbox controllers; using standard vJoy probably wouldn't get you what you want, because it emulates DirectInput devices instead (as most joystick drivers do). That branch works, but it's worth noting that it hasn't been updated in a while and can be a bit buggy. Also, the methods are terribly named, so good luck guessing which is which (hint: If it seems obvious, it isn't).

Please take a look at the common vJoy/vXbox API - vGen.


sip.js 0.11.4 has not been published to npmjs.com

The latest version on npmjs.com is 0.11.3

Sorry about that. It has been resolved.


Add option to hide property label

When the property editor is shown in an overlay, the label to the left might take up space that could be used for the table editor, so an option for hiding the label could make sense.

Implemented and will be part of the v1.1.0 release 😎


AC5: Account Settings xPub

Upgrade script to ensure all old apps get a xPub added to their UI subAccount.
Change account creation code to ensure an xPub property with value at account initialization.

This is done.

This is done, tested on upgraded app


Help needed adding new columns to Impact matrix

I am trying to add effective date columns for old and new change controlled items in the impact matrix.
I added a row in the table  grid initiation and then defined a new class for it. However I get empty cells in the matrix even though the items in the list do have effective dates. Any help on this?

Summary tab is basically a TGV based on the TGV demo by Aras, which shows child parts, linked cad and docs, AML parts & alternates, and process plans where the part is the producedpart or a consumedpart.
MBOM tab is also a TGV that shows the MBOM of the part (i.e in the process plan for the part, all the consumed parts in that PP are listed in the TGV)
Finally, Since PP has a hard fixed relation with part (mpp_ProcessPlanProducedPart), I added a new relationship from Part to its linked processes (with a float relation), so that the PP can appear in teh Impact matrix to indicate that if i modify teh Part, I might have to update the PP (depending on the ECO details) (Background, I have added mpp_processplan to Change controlled item and change controlled relationship to make it appear on the Impact matrix)

Have you already tried to write efffective_date without three f?

Yup.
It works just fine when used for new version item (i.e new effective date)

Ok, it´s too late for me today for ImpactMatrix questions. But maybe it´s related to the properties in Affected Items. I remember that I use foreign properties to display certain informations.
var customprop = this.grid.getProperty(this.row.data.affectedItem, "customprop");

One last comment for today. What behavior do you see, when you perform multible Express ECOs at the same Part? For example if you change the Major REvision 5 times. Is your previous Item in older Express ECO floating to the latest verison of the Part or does it stick to the original generation?
This one was making me quite a headache in the past, as it was acutally impossible to track changes with the Express ECO.

It floats to the latest version

Also we learnt to bunch our changes in Express ECOs in a careful way that we tried to limit parallel changes on teh same part. Our Product is extremely systematically complex, with way too many interaction between subsystems, that if we touch one, we will have to change a lot of parts. So we are using the ECO just as a documenting board for the impact and final recording of the actual changes. THe PMO handles the complete workflow and not the designers


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.93

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.93


您好，请教一个关于few-shot实验的细节问题。

在您的论文中，将整个实体集划分成了三个部分，用作训练、验证和测试，并且进行了实体的替换以防止信息泄露。论文中是这么描述的：To avoid the observation of new entity types in the training phase, we replace the labels of entities that belong to Etest with O in the training set. Similarly, in the test set, entities that belongs to Etrain and Edev are also replaced by O. 根据这一描述，训练集只将属于测试集的实体替换成了O，属于验证集的实体似乎是没有被替换的，并且也没有提到验证集的处理方法。我下载了您公开的intra数据集并写了脚本统计了一下，发现训练集中属于验证集的实体也被替换成了O，而且三个数据集的实体是互不相交的。
所以我现在有点困惑，论文的描述和实际的做法是不一致的，是我对您论文中的描述理解错误了吗？

Hi, sorry for the confusion. As you have found out, under inter and intra mode, for all the three datasets, we do replace the entity types in the other two datasets with O, i.e. we ensure that the entity types have no overlap among the train, dev, and test split. The description in the paper should be modified.


Adds Google Cloud Build example.

Preview at https://github.com/GoogleContainerTools/jib/tree/cloud-build-example/examples/google-cloud-build

This ad-hoc example works, but I'm wary of spreading the practice of overriding the Java system property user.home as a workaround to make Jib pick up .docker/config.json that happens to be under /builder/home. Changing the user home to an arbitrary location (/builder/home is just a random directory considering that the actual home is /root) may affect various tools and programs; obviously, Maven and Jib are such examples here. Particularly, Maven will not make use of the .m2 repository in the actual user home (I mean /root/.m2), which GCB might decide to auto-cache in the future. I think we should wait until GCB fixes this issue.

Should we make the docker config.json location be configurable?

@chanseokoh Maybe I should just add a step that links the docker config to /root/.docker/config.json first.

@coollog that's another way to make it work, but my point is that, looks like GCB will fix the issue and people won't need to do it themselves. If we put up an "official" doc here to do that, people will think copying/linking the file will be a necessary step for GCB, and making it kind of part of "official" instructions is what I'd like to avoid. At least we should add a comment saying linking the file is just a temporary workaround until GCB fixes it.

(Linking the file seems better than overriding user.home, which will affect everyone on the JVM.)

Moving this to a separate repo for now. Will add official Jib example once GCB updates to remove the need for the workarounds here.


Empty lines disappear

My Setup

Operating System: Arch Linux
App Version: 3.2.3
Installation type: package manager (from AUR)

[X] I have tested with the latest version
[x] I can simulate the issue easily

Description
Empty lines don't appear. They are there in code blocks, and also there in the editor box, if I edit the message, but does not render in the message window. It also happens on Windows, on macOS and in the webclient, but works perfectly on Android.

Current Behavior
Shift+Enter produce a CR/LF in the editor box, but it disappears from the message
Expected Behavior
Shift+Enter produce a CR/LF and in the message there should be an empty line

I believe it's a new parser behavior.
So, that issue related to https://github.com/RocketChat/Rocket.Chat/issues/22280
It's not duplicate, it's additional information about new parser problems.


replace 'Now' with a data structure

Now as an attribute modifier can be replaced with a more efficient (to operate, and to read) data structure call.

closing to reduce total number of issues


[BEAM-7926] Visualize PCollection

Added pcoll_visualization module to visualize materialized
PCollection data.
A visualization mainly consists of 3 parts: facets-dive,
facets-overview and data-table.
The visualization is always async. It has 2 modes: one-shot and
dynamical plotting.
One-shot visualization renders the visualization as HTML statically.
Dynamical plotting polls materialized data, initializes a
visualization and then updates the visualization continuously.
It's the pipeline state, i.e., whether the PCollection
materialization is being updated that decides if the visualization is
dynamical plotting or one-shot. It's not the boundedness of PCollection
that decides the visualization mode. However, when engineering for
Interactive Beam, it's alright to always use the dynamical plotting
mode as long as the InteractiveRunner(s) manages jobs and tracks the
pipeline(job) results correctly. Failing to terminate a visualization
job might cause resource leak.
The materialized PCollection data goes through the following process
flow: cache -> element list -> normalization -> dataframe ->
HTMLs/scripts.
A visualization is always self-contained. Meaning it controls when
the visualization starts and ends by itself. Once visualized, the
visualization is anchored within the notebook cell's output area. Code
in other cells can affect the visualization in the cell but will not
change the existing visualization's position in the notebook. Multiple
visualize(pcoll) calls will render multiple independent distinct
visualization instances/jobs. Each visualization runs in its own thread
outside of the notebook main thread.
Unittest added focusing on the above visualization logic other than
the visualization UI (those should belong to Facets, pandas and jQuery,
we'll trust them work as intended). Integration tests can be added
later.
Each visualization job regularly queries interactive environment for
running pipeline(job) results implicitly to determine the default
visualization end condition. It's based on the limitation that within
current interactive environment, at a time, at most one job is in
non-terminated state for an end user defined pipeline instance (in
whatever state). The end user could also use the handle returned by
visualize() to stop() the visualization job manually.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R:rohdesamuel
PTAL. Will fix the precommit checks once they are done add aaltay@ later.

R: @aaltay
R: @rohdesamuel
PTAL, thanks!

I will wait for @rohdesamuel to make the first review pass. Could you also check the failing tests please?

Hi @pabloem , thanks for volunteering to review this PR!
I've fixed most of the test related issues.
There is a Python fatal stack overflow error that I couldn't really make sense of. It seems that the error exists before my change but past Jenkins tests skipped it due to some execution ordering reason? I've asked the question to the dev mail list: https://mail.google.com/mail/u/0?ui=2&ik=64050edf4e&view=lg&permmsgid=msg-f%3A1647143158414277283&ser=1

Any updates @rohdesamuel @KevinGG ?

retest this please.

retest this please.

retest this please.

FYI you don't need to retest the whole thing. You just need to rerun the specific tests that are failing (e.g. Run Portable_Python PreCommit / Run Python PreCommit / Run PythonLint PreCommit / ....)

FYI you don't need to retest the whole thing. You just need to rerun the specific tests that are failing (e.g. Run Portable_Python PreCommit / Run Python PreCommit / Run PythonLint PreCommit / ....)

Got it. Thanks!
Now the tests have passed, we can start reviewing it.

isort and pylint are crazy and contradicting about where you should put import apache_beam as beam. And the order suggested changes over time.

Run Python PreCommit

lgtm

R: @aaltay
The tests have passed and Sam has completed his review. Do you have any other comments for this PR?

I've added two tox env and corresponding Py36 and Py37 test suite. Removed [interactive] from test required packages. Added it to py2:docs env.
I'll add [interactive] for other specific envs defined in tox.ini if any of the gradle task needs it.
I've also added check and warnings in interactive_environment.InteractiveEnvironment to check prerequisites for interactive beam (didn't put them in the global scope because global scoped warning level logging will fail gradle tasks in pre-commit):

If Python is above 3.5.3;
If [interactive] dependencies are fully available;
If current runtime is within an interactive environment, i.e., within an ipython kernel.

For the time.sleep() and pcoll_visualization NOOP strategy when dependencies are not fully installed, please let me know your preference, @aaltay. Personally I'm fine with either approaches, and I'll make change if needed.

Thank you.
Could you add your changes in new commits, instead of force pushing. Reviewing incremental changes that way is easier.

Yes, I'll do that from now on. Thanks!

Looks cleaner. Could you ping once all open comments are resolved.
(I will be OOO most of next week but @pabloem can finish the review.)

Looks cleaner. Could you ping once all open comments are resolved.
(I will be OOO most of next week but @pabloem can finish the review.)

Sure, thanks! I think all the open comments are marked as resolved. I'll let Pablo go over it once more next week. Have a nice weekend~

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

Run Python PreCommit

Squashed and merged after Ahmet LGTMd, and myself as well.


Resolve conflicts on next branch

The webpack 4 documentation PR #1856 currently has conflicts with master branch.

This PR contains the auto-merge change as well as conflicts resolution.

cc @montogeek

Thanks!


Merge master into multiapi

(merging master into multiapi)

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java


Support azure blob

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Didn't create this PR and branch correctly.


use latest ruby version in CI

Coverage increased (+2.5%) to 100.0% when pulling 961d4e44b10756bf26676c9e95013e90fc3ee0a9 on takkanm:use_latest_ruby_version_in_ci into a6c1e725992a2cad54f7bd21774ad18e651d777a on ruby-grape:master.

Coverage increased (+2.5%) to 100.0% when pulling 961d4e44b10756bf26676c9e95013e90fc3ee0a9 on takkanm:use_latest_ruby_version_in_ci into a6c1e725992a2cad54f7bd21774ad18e651d777a on ruby-grape:master.

thanks @takkanm … please run bundle exec rubocop -a to fix the rubocop offences

@LeFnord Thank you for your response.
This error is due to a change in rubocop default.
https://github.com/bbatsov/rubocop/pull/4231
Should I fix this error with this pull request? Or should I fix with another pull request?

@takkanm … yes please fix it with this PR, as I suggested above 😉

Thanks for your advice. I updated this pull request.

Coverage increased (+2.5%) to 100.0% when pulling 9ad6efc9a5d9903efb7158940ea9a00f12ef2a65 on takkanm:use_latest_ruby_version_in_ci into a6c1e725992a2cad54f7bd21774ad18e651d777a on ruby-grape:master.

Coverage increased (+2.5%) to 100.0% when pulling 9ad6efc9a5d9903efb7158940ea9a00f12ef2a65 on takkanm:use_latest_ruby_version_in_ci into a6c1e725992a2cad54f7bd21774ad18e651d777a on ruby-grape:master.

Coverage increased (+2.5%) to 100.0% when pulling 852a6a10594fbc30dc106360e31111619cab9e73 on takkanm:use_latest_ruby_version_in_ci into a6c1e725992a2cad54f7bd21774ad18e651d777a on ruby-grape:master.


grappler swap_to_host bug fix

I have already solved the problem mentioned in the following issue:
https://github.com/tensorflow/tensorflow/issues/11163
This fix actually is trivial and could please take a look at it to see whether it is ready to be merged?

Can one of the admins verify this patch?

Jenkins, test this please.


Serialiser trait update

Would need this change for handling different serialisers during runtime. See here and here
But this would most likely break your benchmarks, that is, your serialiser structs need to derive clone. I could continue to use my own branch rather than master if you wanna avoid potential issues.

Why is this needed? Wouldn't it be sufficient for all the Arcon serialisers to require Sync+Clone instead of all possible serialisers?

I needed this because I can't clone Arcon's serialisers as the they implement Kompact's "Serialiser" trait that is not cloneable.

Seems like I did a woopsy. Closing down.


Question about mnist siamese example

In the mnist siamese example, two mnist images are mapped onto a vector. The two vectors are merged using euclidian distance. The distance should be low if the images belong to the same number and be high if the two images represent different images.
Questions: In line 59, the labels are set for positive and negative examples. If the euclidian distance for the same numbers should be low, why is the target 1 and why is it 0 for the negative examples? Also, the vectors are created using relu which normally does not have a max_value. How is the euclidian distance kept between 0 and 1?

There is a margin in contrastive_loss implementation and K.maximum(margin - y_pred, 0) remains positive even when y_pred is larger than margin.
Intuitively the whole expression K.mean(y_true * K.square(y_pred) + (1 - y_true) * K.square(K.maximum(margin - y_pred, 0))) means you want y_pred to be close to 0 when y_true is 1 (for positive pairs) and y_pred close or bigger than 1 when y_true is 0 (for negative pairs).


Decals don't show when fusion is on...

Objects with impact properties don't show decals and such unless they're a rigid object.

Fixed in 7a7c05f


New package: MyExample v0.1.0

Registering package: MyExample
Repository: https://github.com/xzma/MyExample.jl
Created by: @xzma
Version: v0.1.0
Commit: ba924b1342644ede0dff4edc4e454c24bba0f50b
Reviewed by: @xzma
Reference: https://github.com/xzma/MyExample.jl/issues/1
Description: This is an example Julia package!

@xzma why are you trying to register an example Julia package?


Resolves #3

add changes for issue #3

This pull request includes documentation improvements and a minor adjustment to the validation logic for the Message class in the RazorPagesTestSample project. The most important changes include adding XML documentation comments and updating the maximum length for the Text property.
Documentation improvements:

src/Application/src/RazorPagesTestSample/Data/Message.cs: Added XML documentation comments to the Message class and its properties to enhance code readability and maintainability.

Validation logic adjustment:

src/Application/src/RazorPagesTestSample/Data/Message.cs: Updated the StringLength attribute for the Text property to increase the maximum length from 200 to 250 characters.


[stable/datadog] Fix daemonset generation if datadog.securityContext==nil

Is this a new chart
no
What this PR does / why we need it:
If the datadog.securityContext value is set to nil instead of {}
when a user want to remove the default securityContext, helm is not
able to generate the Daemonset manifest.
To support this configuration we have change how we test the value.
With the new {{ if ...}} check we don't check the second comparison
if the first already return false.
Which issue this PR fixes

fixes #23084

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

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm

After this PR, my Helm is failing with:
Error: template: datadog/templates/daemonset.yaml:44:13: executing "datadog/templates/daemonset.yaml" at <(.Values.datadog.securityContext) and .Values.datadog.securityContext.seLinuxOptions>: can't give argument to non-function .Values.datadog.securityContext


Add option for self-signed certs

Proxies with self-signed certs won't work.  See https://github.com/opsdisk/pagodo/issues/60#issuecomment-911032991

Might be a bug with urllib3
https://github.com/urllib3/urllib3/issues/2400#issuecomment-910350477

https://github.com/opsdisk/yagooglesearch/pull/4


Possible bug or feature not supported in the dynamic load of gltfs

When I try to download a glTF that has the binary data in the file itself it fails. i.e:
{
....
"buffers": [
"byteLength": 102312,
"uri":data:application/octet-stream,base64, (binary information)
]
CompletionException: java.io.FileNotFoundException: data:application/octet-stream,base64, (binary information)
Is it an error or an unsupported feature?

More things:
I also tried:
1. Load a glTF from the cache folder and always give me a FileNotFound error.
  2. Load a glTF from the assets folder and always give me a FileNotFound error.
  3. Load a glTF from the resource android raw folder and always give me a FileNotFound error.
1. CACHE FOLDER
Steps:

Download a file to app cache's folder.

Checked that file exist.
File file = new File(path_to_file);
file.exist() == true ---> OK

Call ModelRenderable like this:

{
File file = new File(path_to_file);
Uri uri = Uri.fromFile(file);
ModelRenderable.builder()
    .setSource(this, RenderableSource.builder().setSource(
        this,
         uri,
        RenderableSource.SourceType.GLTF2)
        .setScale(0.5f)  // Scale the original model to 50%.
        .setRecenterMode(RenderableSource.RecenterMode.ROOT)
        .build())
  .setRegistryId(GLTF_ASSET)
  .build()
  .thenAccept(renderable -> duckRenderable = renderable)
  .exceptionally(
    throwable -> {
      // Show throwable
      return null;
    });

}
2. ASSETS FOLDER
Steps:

Create an assets folder in main app
Put in a file geometry.gltf
Call ModelRenderable like this:

I tried path_file

"/geometry.gltf"
"geometry.gltf"
"/android_asset/geometry.gltf"
"android_asset/geometry.gltf"

{
File file = new File(path_file);
Uri uri = Uri.fromFile(file);
ModelRenderable.builder()
    .setSource(this, RenderableSource.builder().setSource(
        this,
         uri,
        RenderableSource.SourceType.GLTF2)
        .setScale(0.5f)  // Scale the original model to 50%.
        .setRecenterMode(RenderableSource.RecenterMode.ROOT)
        .build())
  .setRegistryId(GLTF_ASSET)
  .build()
  .thenAccept(renderable -> duckRenderable = renderable)
  .exceptionally(
    throwable -> {
      // Show throwable
      return null;
    });

}
3. ANDROID RESOURCE RAW FOLDER
Steps:

Create a raw folder in app
Put in a file geometry
Call ModelRenderable like this:

{
String path_to_file = "android.resource://"+getPackgeName()+"/"+R.raw.geometry;
Uri uri = Uri.parse(path_to_file);
ModelRenderable.builder()
    .setSource(this, RenderableSource.builder().setSource(
        this,
         uri,
        RenderableSource.SourceType.GLTF2)
        .setScale(0.5f)  // Scale the original model to 50%.
        .setRecenterMode(RenderableSource.RecenterMode.ROOT)
        .build())
  .setRegistryId(GLTF_ASSET)
  .build()
  .thenAccept(renderable -> duckRenderable = renderable)
  .exceptionally(
    throwable -> {
      // Show throwable
      return null;
    });

}
How i have to create Uri to access in each case?
Thank you.


[Remove] Type mapping param from REST end-points

Remove type param from REST end-points

[ ] #1999
[x] #2003
[ ] #2002
[ ] #2004
[ ] RestUpdateByQueryAction
[ ] RestGetFieldMappingAction
[ ] RestGetMappingAction
[ ] RestPutMappingAction
[ ] RestValidateQueryAction
[ ] RestBulkAction
[ ] RestDeleteAction
[ ] RestGetAction
[ ] RestGetSourceAction
[x] #2010
[ ] #2014
[ ] #1997
[ ] RestMultiTermVectorsAction
[ ] RestTermVectorsAction
[ ] #2028
[ ] search/RestCountAction
[ ] RestExplainAction
[ ] RestMultiSearchAction
[ ] RestSearchAction

Additional context
Parent: https://github.com/opensearch-project/opensearch/issues/1940

Let's not create individual issues for each one of these, it's hard to grok from the issue what needs to be done. The parent is plenty to track progress and PRs can just link back to it and we can check [x] boxes here once they are merged?

Closing this issue, as meta (#1940 ) is already tracking each rest action.


Reverse debug specific check.

debug_flag && diags->on() is almost an atomic operation,
while is_debug_tag_set requires Diags to run a regular expression.
When debug_flag is set to 1, we always want to print the debug log,
regardless of whether the tag is set or not, which makes the
is_debug_tag_set check useless, and expensive.
This change flips the conditional to check if debug_flag is 1 first,
skipping the tag check if it is.

[approve ci]

Cherry-picked to v9.0.x branch.


Cannot multi-select, Add to Recommended Extensions

Testing https://github.com/Microsoft/vscode/issues/52850
I can multi select extensions in the extension viewlet, but the command Extensions: Add to recommended Extensions (...) only adds the extension that is open in the editor.

There is no action on the extensions that is supported in the multi-selection mode at the moment.
That's why we resorted to making all the recommendation related actions act on the extension that is opened in the editor.
Ideally actions Disable/Enable/Uninstall/Install could be supported in the multi-select mode.
@sandy081 @isidorn Is that something we want to do?

Multi-select is not yet supported in Extensions viewlet - https://github.com/Microsoft/vscode/issues/44508

Since none of the actions in the extensions viewlet are mutli select aware I would disable multi select there - it is just confusing now.
If we want to do this for the future - imho not really needed, most of the time users operate on one extension, and we allready have some mass actions - like disable all extensions

It is still possible to select multiple items in the extensions view by using the keyboard.
 I would expect this is disable as well -> reopening

I set multipleSelectionSupport option to false while creating the list and I expect list disable it completely.
@joaomoreno FYI

Please file issue! 👍


Passing --python-platform flag to uv

Related to #717 and #1053, now that uv is the default backend would it be possible to pass the --python-platform flag either as configuration or its flag for sync/add etc? This would get us 95% of the way for platform agnostic lockfiles as we only really care about locking down dependencies for Linux.

Are there plans to expose the --universal flag that came to uv recently?


Question: Command Bar Borders - Are these correct?

The borders which appear around the edge of the CommandBars as they expand/pop-over - should they appear so bright and solid?

When comparing to the similar CommandBarFlyout controls - the borders for the CommandBars look garish

CommandBarFlyouts use a darker Acrylic and don't feature prominent borders
I am sure they look more subtle when used on the default Light or Dark themed backgrounds, but with the Rainbow background on the testing page, but maybe something with lower opacity may be better, like the CardStrokeColorDefault

Examples on solid "expected" backgrounds

@chigy thoughts?


DMR: Setup PR gate integration tests

same as https://github.com/buerokratt/Mock-Bot/issues/22

I think this was accidentally pulled into the sprint and given the wrong priority. It depends on https://github.com/orgs/buerokratt/projects/3/views/1 so I'll update it to come after that one.


Clarify Common Variable Identity

The question boils down to:
Is my love the same variable as your love?
Thought I would say that they aren't, it isn't abundantly clear from the spec.

They are not. The prefixes "my" or "your" are part of the variable name.

This should probably be reopened as this still needs to be clarified in the spec.