Server profile - sasLogicalJBOD where id must start at 1

Scenario/Intent
Create logical disks in server profile
Environment Details
Module Version: current master - v5.1.1
**Ansible Version:**2.64
OneView Appliance Version: 4.10.03-364293
OneView Client API Version: 600
Python Version: 2.710
python-hpOneView SDK Version: v4.7
Platform: Ubuntu 18
Steps to Reproduce
when creating logical disks in server profile, the SAS logical JBOD ID must start with 1. If not, it generates an error ( see output)
Expected Result
I do not understand the rational behind starting with id=1. In the logical drive attributes, you have an attribute called  sasLogicalJBODId that points to the index of JBOD in sasLogicalJBOD. we should be able to index JBOD with index of any value and use sasLogicalJOBID in logical drive to match.
Let's take a scenario where you have a profile with logical disks. All good as it starts in sequence.
Now later on, an administrator decides to remove logical disks in profile. As a result the IDs will be out of sequence. Re-run the playbook will result in error
Actual Result
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: HPOneViewTaskError: The specified SAS logical JBOD ID for JBOD [JBOD] is not in sequence.
fatal: [localhost -> localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n  File "/home/dung/.ansible/tmp/ansible-tmp-1546544599.53-192311710288365/AnsiballZ_oneview_server_profile_template.py", line 113, in \n    _ansiballz_main()\n  File "/home/dung/.ansible/tmp/ansible-tmp-1546544599.53-192311710288365/AnsiballZ_oneview_server_profile_template.py", line 105, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File "/home/dung/.ansible/tmp/ansible-tmp-1546544599.53-192311710288365/AnsiballZ_oneview_server_profile_template.py", line 48, in invoke_module\n    imp.load_module('main', mod, module, MOD_DESC)\n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/main.py", line 228, in \n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/main.py", line 224, in main\n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/ansible_oneview_server_profile_template_payload.zip/ansible/module_utils/oneview.py", line 430, in run\n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/main.py", line 155, in execute_module\n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/main.py", line 168, in __present\n  File "/tmp/ansible_oneview_server_profile_template_payload_5gRiPP/main.py", line 191, in __create\n  File "build/bdist.linux-x86_64/egg/hpOneView/resources/servers/server_profile_templates.py", line 148, in create\n    default_values=self.DEFAULT_VALUES)\n  File "build/bdist.linux-x86_64/egg/hpOneView/resources/resource.py", line 450, in create\n    return self.__do_post(uri, resource, timeout, custom_headers)\n  File "build/bdist.linux-x86_64/egg/hpOneView/resources/resource.py", line 764, in __do_post\n    return self._task_monitor.wait_for_task(task, timeout)\n  File "build/bdist.linux-x86_64/egg/hpOneView/resources/task_monitor.py", line 88, in wait_for_task\n    task_response = self.__get_task_response(task)\n  File "build/bdist.linux-x86_64/egg/hpOneView/resources/task_monitor.py", line 147, in __get_task_response\n    raise HPOneViewTaskError(msg, error_code)\nHPOneViewTaskError: The specified SAS logical JBOD ID for JBOD [JBOD] is not in sequence.\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
[What actually happens after the steps above? Include error output or a link to a gist.]

Also if you create a JBOD first and later add logical drives, the IDs for logical disks will be out of sequence

Going forward, all the enhancement requests will be addressed in the NEW HPE OneView Ansible Collection. Please consider migration to the Ansible Collection.
Migration support material can be found in the Migration Support folder.
We have added this resource in our ansible collections backlog.
https://github.com/HewlettPackard/oneview-ansible-collection


C5 BLE device_id response and name incorrect

The C5 BLE device doesn't respond to device_id with the correct MAC. The device name (OpenXC_C5_BTLE) also needs to get updated to OPENXC-VI-XXXX.
The device DOES advertise the correct MAC over BLE.

Fixed with #378.


Set a serialVersionUID to all serializable classes

Ehcache embeds tc-mangement model, and there are some serial version issues with the provided jar when we do some changes (uids differs since 2 jars on the classpath, built with different uis versions)
So by the time Ehcache solves issue ehcache/ehcache3#1128 we need this workaround.

@anthonydahanne : FYI


mocking a module with relative path alias is not working

Describe the bug
Description
Create a path alias with relative path in vitest.config.ts:
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    alias: {
      '~': './src',
    },
  },
});

and mocking a module with path alias:
src/module.ts
export default function () {
  // do something
}

test/basic.test.ts
import { vi, assert, expect, test, Mock } from 'vitest';

import mod from '~/module';

// Mock the module. This will be hoisted to the top and `import mod from '~/module' will return a `Mock` object.
vi.mock('~/module');

test('Calling mocked function', () => {
  (mod as Mock).mockImplementation(() => {
    return 'success!';
  });
  expect(mod()).toBe('success!');
});

Then run the test, which will result in the following error:
 FAIL  test/basic.test.ts > Calling mocked function
TypeError: default.mockImplementation is not a function
 ❯ eval test/basic.test.ts:9:17
      7|
      8| test('Calling mocked function', () => {
      9|   (mod as Mock).mockImplementation(() => {
       |                 ^
     10|     return 'success!';
     11|   });

Resolution
I struggled for a couple of hours and found that changing the alias to '~': '/src' solves this problem.
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    alias: {
-     '~': './src',
+     '~': '/src',
    },
  },
});

Why this occurs
It seems that the id of aliased module is calculated differently in requestWithMock and mockPath when using relative path.
Confirm this by inserting some debugging code in node_modules/vitest/dist/chunk-runtime-mocker.344fec90.js:
  async requestWithMock(url, callstack) {
    if (_VitestMocker.pendingIds.length) await this.resolveMocks();
    const id = this.normalizePath(url);
+   console.log(id, this.getMocks());

and run the Stackblitz, then get output like this:
stdout | unknown test
/home/projects/vitest-dev-vitest-vakjkb/node_modules/vitest/dist/index.js {}

stdout | unknown test
/home/projects/vitest-dev-vitest-vakjkb/src/module.ts { 'src/module': null }

Here, getting null as a mock value is just fine. The problem is that the id calculated in requestWithMock (/home/projects/vitest-dev-vitest-vakjkb/src/module.ts) does not match the id calculated in mockPath (src/module).
I don't know if this is an expected behavior or not, but it is definitely the root cause of this problem.
Reproduction
Stackblitz (relative module alias, not working)
Stackblitz (module alias with / prefix, working)
System Info
System:
    OS: Linux 6.2 Arch Linux
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900KS
    Memory: 21.05 GB / 31.05 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 16.15.0 - ~/.nodenv/versions/16.15.0/bin/node
    Yarn: 1.22.19 - ~/WorkDir/worx-hr/labor-frontend/node_modules/.bin/yarn
    npm: 8.5.5 - ~/.nodenv/versions/16.15.0/bin/npm
  Browsers:
    Chromium: 110.0.5481.177
    Firefox: 110.0.1
  npmPackages:
    @vitejs/plugin-react: ^3.1.0 => 3.1.0
    vite: ^4.2.1 => 4.2.1
    vitest: ^0.29.7 => 0.29.7

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

As described above, we can avoid this problem by not using relative path for path alias.
But since this is really confusing, this behavior should be either documented or corrected.

"module.ts" is not located in the same directory where your test is. If path is relative, it's relative to the current path, so everything works correctly.

OK, so if you say that the module needs to be placed "relative" to the test file, why the module resolution itself succeeds?
Even if in the not working reproduction, module is resolved to the <projectRoot>/src/module (since we don't get any "module not found" error.)
It means that the relative path ./src in the config is resolved based on the project root directory.
The module resolution is obviously inconsistent between the import and the mocking.
This is why I say it "confusing". (The path resolves successfuly in import, but not in the mocking.)

@sheremet-va
Have you checked the above? Please reopen this.

The fact that import works is a bug and a side effect of how Vite SSR works, not the other way around. Don't use relative paths in aliases, it's a common sense, the are just replaced and resolved to the current file, not the file they are defined in.

OK, I get what you want to say, but I think that you should explicitly document how to use the alias option correctly.
Similar functionalities in the world, like jest or typescript, includes at least an example configuration in their documentation.
In vitest, there is neither any explanation nor example configuration.


Array of String contains null, it returns nil in mapping

JSON looks like.
"benefits": [
                "package benefits 1",
                null,
                null
            ],

If this is JSON, ObjectMapper returns nil, on
benefits <- map["benefits"]

I am facing same issue! @chatarveer
Does anyone have Any solution? @tristanhimmelman


aliases not working on declaration files in dist/

Describe the bug

I'm using vite-tsconfig-paths for resolving aliases from the tsconfig.json file and vite-plugin-dts for generating .d.ts files and they work fine inside my project, but after I run build (in lib mode) and check the dist folder the imports aliases are not resolved. They point to the src folder, not the dist folder. Adding a relative path works though. Shouldn't the aliases be resolved on build?
Shouldn't .types.ts .d.ts files be prefixed with declare so they can be accessed outside the project?

Reproduction
https://stackblitz.com/edit/vitejs-vite-b6n9u5?file=package.json
Steps to reproduce
run npm install then npm run build
System Info
System:
    OS: macOS 13.4
    CPU: (10) x64 Apple M1 Pro
    Memory: 37.96 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 12.22.12 - ~/.nvm/versions/node/v12.22.12/bin/node
    Yarn: 1.17.3 - /usr/local/bin/yarn
    npm: 6.14.16 - ~/.nvm/versions/node/v12.22.12/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 114.0.5735.106
    Firefox: 112.0.2
    Safari: 16.5
  npmPackages:
    @vitejs/plugin-react: 3.1.0 => 3.1.0
    vite: 4.3.7 => 4.3.7
    vite-plugin-dts: ^2.3.0 => 2.3.0

Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Why is this one "completed"?
I am facing the same problem, so I think this is an unresolved issue
@qmhc Could you please take a look?

@everdimension Currently you can use pathsToAliases option of the plugin.
If you think the issue still exists, you can create a new issue and provode a reproduction with the latest plugin version.

@qmhc

Currently you can use pathsToAliases option of the plugin

The docs say it's true by default. I tried setting it to both and the result is the same. Currently I had to rewrite all types imports to relative paths

@everdimension You can make a reproduction and create a new issue for it.


oci360_run.sh: line 124: syntax error near unexpected token `>'

Hi Rodrigo,
I'm trying you toll and I'm facing a small issue when running it, if I use "sh" I got a error on line 124 regarding "exec" redirect, but if I change to "bash" no issue found.
[oci360@oel8ora199 oci360_tool]$ /usr/bin/sh /u01/oci360/oci360_tool/scripts/oci360_run.sh
From this point, all the output will also be redirected to "/u01/oci360/oci360_tool/log/run.20210305151303.log".
[oci360@oel8ora199 oci360_tool]$ cd /u01/oci360/oci360_tool/log/
[oci360@oel8ora199 log]$ ls -l run.20210305151303*
-rw-r--r--. 1 oci360 users 96 Mar  5 15:13 run.20210305151303.trc
[oci360@oel8ora199 log]$ cat run.20210305151303.trc
/u01/oci360/oci360_tool/scripts/oci360_run.sh: line 124: syntax error near unexpected token `>'
[oci360@oel8ora199 log]$

Hi @jomamimo. Are you running this from inside the container or from the server?
You should run this way from the server:
docker exec -it --user oci360 oci360-tool bash /u01/oci360_tool/scripts/oci360_run.sh
What is the OS full version (cat /etc/oracle-release) of your server? I will try to simulate the issue.
Thanks

Sorry, I think I read your message too fast. Now I saw that the issue was solved when running as bash (expected). I will put a check on the next release to ensure the oci360_run.sh gets executed with bash instead of any other shell.


feat(manager): add global message on site list page

We should probably have the functionality to put a message on the site listing page. Addresses a concern in #5.
This adds that functionality as GLOBAL_MESSAGE in the Django settings.

I just added something similar in 8b158e676329007602f8e9cf045be939837498a9. Sorry.


make gpr a shared library, add installation target and fix a few build errors on mac and linux

make gpr a shared library, add installation target and fix a few build errors on mac and linux

Looks good. Thanks!


Zipformer Model Training Error

We are trying to train the zipformer model on our own data using the Librispeech recipe, the model trains without any error for a small subset of data, but after giving more data to the model for training we are encountering this error,
Traceback (most recent call last):
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 1337, in <module>
    main()
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 1330, in main
    run(rank=0, world_size=1, args=args)
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 1208, in run
    train_one_epoch(
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 1013, in train_one_epoc
    valid_info = compute_validation_loss(
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 813, in compute_validation_loss
    loss, loss_info = compute_loss(
  File "/home/ubuntu/STT/icefall/egs/sb/s5/./zipformer/train.py", line 760, in compute_loss
    simple_loss, pruned_loss = model(
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ubuntu/STT/icefall/egs/sb/s5/zipformer/model.py", line 136, in forward
    assert torch.all(x_lens > 0)
AssertionError

can someone please help me resolving this
Thanks in Advance

It looks like one of your input data has zero length. Could you please check you experiment directory and see if any data is stored? The script should automatically save the batch that is causing the training to crash. Then, could you print out the shape of x when throwing out this error?

It seems the error happens in compute_validation_loss. This could just be because you haven't applied the filter to remove_long_and_short cuts on the validation set.

Applying the filter to the validation set worked and the model started training without any errors. Thank you all.


update (buyer/seller contract, rNFT etc) contracts and help section in create product flow for offers with no expiration

@albertfolch-redeemeum help text: https://docs.google.com/document/d/12YMB_GtW7I_oN4H9srArFitOZf2E4lL24GxSoJI3H3k/edit#heading=h.6x6yvavklx79

dApp Terms & Conditions:

**Please noted one minor correction needed in the live version of the Privacy Policy:
Under 3.1.2, delete the comma and the word “and”, and replace them with a period.**
information about your use of the Services.


Discord Link on Github and Official Pages Does Not Work

What happened?
Hi,
Your discord link found on the readme doc and your hosted docs results in an invalid invitation.
Thank you,
Inayet
How can we reproduce this?
Click on the discord link
cxcli version
NA

Search

[X] I did search for other open and closed issues before opening this.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Additional context
No response

should be good now! thanks for reporting it!


Fix project compile error 'Unable to Resolve .NET SDK version as specified in the global.json...'

This occurs if you have a newer version of the SDK installed.  global.json specifes version 6.0.101
{
  "sdk": {
    "version": "6.0.101",
    "rollForward": "disable"
  }
}

This file was added for issue #42
Recently this issue occurred following installing Windows updates where it appears that the SDK was upgraded to 6.0.203 (removing 6.0.101 in the process).  To fix the issue you need to remove 6.0.203 to allow the installation of 6.0.101.  This is painful and potentially frustrating for any new users that want to work on this project.
The only problem building with a newer version of the .NET framework is that it won't have compatibility with the older versions of the NET 6 runtime and will fail silently.  This will be less of an issue as more people upgrade their .NET runtime versions.
Also, the github action that builds the project for public release specifies the version of the .NET SDK to use:
      - name: Setup .NET Core
        uses: actions/setup-dotnet@v2
        with:
          dotnet-version: 6.0.101
          include-prerelease: true

Removing the global.json file should improve the developer experience while the public build from the github action will still use version 6.0.101 for the widest compatibility.

Confirmed compatibility with 6.0.0 runtime is still maintained with the removal of global.json when project is built from github action.


FEAT: User should be notified of an update pending on the My Content Page and have the ability to update the installed release

Given a user is on the my content page
When an update is present
Then they should be notified visually and can update accordingly

In the old pile of code, I wrote some functionality on the UI side to highlight apps that are out of date and do individual and mass updates. We may be able to recover that.

@john681611 I'm going to get a naive impl of this working so we can move towards an alpha release

Resolved by #22


admin/org settings: under default streams-> cannot scroll streams

In organization Settings-> "Default streams", the list of streams are not scrollable and admin is forced is to use the scrollbar to access other streams. Also, it seems that instead of getting the list scrolled, its parent gets scrolled.

This issue is somewhere similar to #6351.

Same issue exists for Users and Bots list in organization settings. Those should also be fixed as a part of fixing this.

Tagging this as a high priority so we don't miss fixing it or reverting the change before the next release.

Fixing this and possible update issues with the other scrollbar implementation on the settings page!

@brockwhittaker @timabbott It was reported that the same issues were being observed in the Users/Bots pages, and I don't think the merged commit fixes those issues?

Can you reproduce that on chat.zulip.org?  Scrolling works fine for me on those pages.

Ahh, I see, it's a vertically narrow window (I think the perfectScrollbar area inside has a fixed height); I feel like for those, the bug might be that we should just have the one scrollable area.  @brockwhittaker thoughts?

Yeah I’ll just fix the table height to be less tall!
On Tue, Sep 19, 2017 at 20:08 Tim Abbott<EMAIL_ADDRESS>wrote:

Ahh, I see, it's a vertically narrow window (I think the perfectScrollbar
area inside has a fixed height); I feel like for those, the bug might be
that we should just have the one scrollable area. @brockwhittaker
https://github.com/brockwhittaker thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/issues/6391#issuecomment-330732630, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJ199xCD1EZsDSQCE5nRpx87qqqsmA95ks5skIGXgaJpZM4PLSLn
.


[SECURITY] Releases are built/executed/released in the context of insecure/untrusted code

CWE-829: Inclusion of Functionality from Untrusted Control Sphere
CWE-494: Download of Code Without Integrity Check
The build files indicate that this project is resolving dependencies over HTTP instead of HTTPS. Any of these artifacts could have been MITM to maliciously compromise them and infect the build artifacts that were produced. Additionally, if any of these JARs or other dependencies were compromised, any developers using these could continue to be infected past updating to fix this.
This vulnerability has a CVSS v3.0 Base Score of 8.1/10
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
This isn't just theoretical
POC code has existed since 2014 to maliciously compromise a JAR file inflight.
See:

https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/
https://github.com/mveytsman/dilettante

MITM Attacks Increasingly Common
See:

https://serverfault.com/a/153065
https://security.stackexchange.com/a/12050
Comcast continues to inject its own code into websites you visit (over HTTP)

Source Locations

https://github.com/uber/uReplicator/blob/9078f9e4fcb826f6effa1c9a769e69d8fd29aa50/uReplicator-Worker/pom.xml#L44-L50
https://github.com/uber/uReplicator/blob/9078f9e4fcb826f6effa1c9a769e69d8fd29aa50/pom.xml#L89-L95

Original Report to Uber Security Team
When originally reported, this issue was closed as 'Informative'
https://hackerone.com/reports/569347
Public Disclosure
Option 1: File for a CVE
A project maintainer for this project should probably file for a CVE number to inform the public about this vulnerability in the build for this project. The goal is to inform the public that there was a potential for published build artifacts to have been maliciously compromised in earlier releases.
If a maintainer on this project works for or is associated with a CNA, please have them file it with them:
cve.mitre.org/cve/request_id.html
Otherwise, an open source CVE should be filed for here:
iwantacve.org
Option 2: Manually validate the release artifacts
If this project's build is fully reproducible. An alternative to filing for a CVE is to go back and build the earlier releases (with the HTTPS patch applied) to confirm the artifacts were not tampered when they were built. This can be done by comparing the hashes of the artifacts built locally with the ones published. If the hashes of all previous artifacts match those that are published, you can safely assume that the releases were not tampered with.
Again, this assumes that the build if fully reproducible and will require significantly more work.

This research is now publicly disclosed here:

Want to take over the Java ecosystem? All you need is a MITM!

Also, this isn't fixed:
https://github.com/uber/uReplicator/blob/7ea1aafa3be0305dfff9eda48fea8b4ce6f35149/pom.xml#L94


Packet length error

I tried to use an Wemos D1 with a logic shifter and this is what I get as an result. Seem to be a wrong seperation of the raw string.
How to fix this?

Regards
Kevin

Managed to get the states to work by increasing the delay on the ESP side. Now I only get:

How to filter them out?

Managed to get the states to work by increasing the delay on the ESP side. Now I only get:

How to filter them out?

You just need to adjust the code to fit your needs.
For example:
if (Serial.available()) {
    //size_t len = Serial.available();
    uint8_t sbuf[37];
    Serial.readBytes(sbuf, 37);
    //push UART data to all connected telnet clients
    for (i = 0; i < MAX_SRV_CLIENTS; i++) {
      if (clients[i] && clients[i].connected()) {
        clients[i].write(sbuf, 37);
        delay(1);
      }
    }
  }

OR
  uint8_t sbuf[100];
  uint8_t len = 0;
  if(Serial.available() > 0){
    len = 0;
    while (Serial.available() > 0) {
      sbuf[len] = (byte)Serial.read();
      len++;
      delay(5);
    }
    //push UART data to all connected telnet clients
    for(i = 0; i < MAX_SRV_CLIENTS; i++){
      if (clients[i] && clients[i].connected()){
        clients[i].write(sbuf, len);
        delay(1);
      }
    }
  }

You just need to adjust the code to fit your needs.
For example:
if (Serial.available()) {
    //size_t len = Serial.available();
    uint8_t sbuf[37];
    Serial.readBytes(sbuf, 37);
    //push UART data to all connected telnet clients
    for (i = 0; i < MAX_SRV_CLIENTS; i++) {
      if (clients[i] && clients[i].connected()) {
        clients[i].write(sbuf, 37);
        delay(1);
      }
    }
  }

OR
  uint8_t sbuf[100];
  uint8_t len = 0;
  if(Serial.available() > 0){
    len = 0;
    while (Serial.available() > 0) {
      sbuf[len] = (byte)Serial.read();
      len++;
      delay(5);
    }
    //push UART data to all connected telnet clients
    for(i = 0; i < MAX_SRV_CLIENTS; i++){
      if (clients[i] && clients[i].connected()){
        clients[i].write(sbuf, len);
        delay(1);
      }
    }
  }

Thank you very much! Solved my issue!

Thank you very much! Solved my issue!


PBS  Error allocating memory for add_verify_resources

After i submit my scrips on the PBS, it tips that Error allocating memory for add_verify_resources.
what can i do for that?

I don't know what this function is so it's probably unique to the PBS
system. You can change memory requirements within the script or talk to
your cluster IT person.
On Fri, Jul 9, 2021 at 3:58 AM phil622 @.***> wrote:

After i submit my scrips on the PBS, it tips that Error allocating memory
for add_verify_resources.
what can i do for that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aidenlab/juicer/issues/229, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK2EW4BZHF2ZWINZPNTMZTTW2TZHANCNFSM5ACICOAA
.

--
Neva Cherniavsky Durand, Ph.D. | she, her, hers
Assistant Professor |  Molecular and Human Genetics
Aiden Lab | Baylor College of Medicine
www.aidenlab.org

I just use the 'juicer.sh' script and add some necessary parameters on PBS, but it till tip the same error.Do you mean that i have to change some things in the 'juicer.sh' script?

Yes, you might have to change the memory requirements depending on your
cluster set up. We set the parameters based on our (SLURM) system. You
might have to use less memory, which will take more time. It's impossible
for us to say without knowing your system, and moreover, the PBS branch is
not tested by us since we do not have access to a PBS system.
On Fri, Jul 9, 2021 at 7:58 AM phil622 @.***> wrote:

I just use the 'juicer.sh' script and add some necessary parameters on
PBS, but it till tip the same error.Do you mean that i have to change some
things in the 'juicer.sh' script?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aidenlab/juicer/issues/229#issuecomment-877133578,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK2EW5CS6VK7KMRJ4CAZGLTW3P6RANCNFSM5ACICOAA
.

--
Neva Cherniavsky Durand, Ph.D. | she, her, hers
Assistant Professor |  Molecular and Human Genetics
Aiden Lab | Baylor College of Medicine
www.aidenlab.org

But i see the PBS version in the latest juicer package, and i think if it is specialized for the PBS system. Do you mean the PBS version in the juicer package is just a test version which is no be tested, so i have to change some things in this version depending on my cluster?

well, now i just use the 'juicer.sh' script of the CPU version and put it in my own script about the PBS system.My script can be run now , but i am not sure if it can get a right result.

We don’t have a PBS system. Someone else created the PBS script and we
pulled it in but we have no way to debug or test.
CPU is fine.
On Sat, Jul 10, 2021 at 2:07 AM phil622 @.***> wrote:

well, now i just use the 'juicer.sh' script of the CPU version and put it
in my own script about the PBS system.My script can be run now , but i am
not sure if it can get a right result.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aidenlab/juicer/issues/229#issuecomment-877576163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK2EW5YUF62QJG72MA37SDTW7PRJANCNFSM5ACICOAA
.

--
Neva Cherniavsky Durand, Ph.D. | she, her, hers
Assistant Professor |  Molecular and Human Genetics
Aiden Lab | Baylor College of Medicine
www.aidenlab.org

thank you


Events in OIOUBL app

Hi,
We would like to extend some of the functionality in the OIOUBL app.
Bu the app is not available in the repo right now.

Good news! OIOUBL extension was added to the repo:
https://github.com/Microsoft/ALAppExtensions/tree/master/OIOUBL
Looking forward to seeing your pull request :)

Hehe I did just that as soon as I saw it :)
https://github.com/Microsoft/ALAppExtensions/pull/1247


[FEATURE] Can't use Font Awesome in the [params.home.profile].subtitle

I enable the fontawesome, It can be used in the [params.home.profile].title, but it can't be used in the [params.home.profile].subtitle.
title = "" #it can be shown correctly
subtitle = "" # nothing

I also tried the shortcode , It just show a string :(fas fa-dharmachakra):
It's wired, I don't know why.
and fontawesome alse can't be used in the [params.header.title].logo and [params.header.title].name

I enable the fontawesome, It can be used in the [params.home.profile].title, but it can't be used in the [params.home.profile].subtitle.
title = "" #it can be shown correctly
subtitle = "" # nothing

Make sure typeit is disable, if you wanna use html phrase on the subtitle.
[params.home.profile]
  typeit = false

OK thank u!


Improvement on the note search

Currently the note search filter out notes, which match on the title or the content.
However, it seems unnatural to me at the first glance:
I thought the search box was only for searching note title, but eventually some other notes came out because the content contains the keyword. Let's imagine when there are some notes contain thousands of words, then they have a high chance to be filtered out every time because of the content match!
So, would it be better if we separate into several types of search:

Title search (just keep it in current search box)
Content search on current active note (perhaps when the cursor is on the note, trigger by ctrl+f)
Full text search across all the notes (maybe ctrl+shift+f)

These are some my opinions, open to discussion. 😃

I totally understand your point, but I know how unorganized I am, and I don’t end up knowing what I title my notes. I just know I had some phrase somewhere in some note. So for me, filtering the whole store is more useful. I can already search the active note with the default browser search.

Highlighting the search term might be a good idea though.


Switch back Yarn root to Rails root

See rails/rails#28093
Documentation and example app probably needs to be updated for this.

Still need to update example & test apps.


Office.context.mailbox.Item.start giving wrong value in Outlook for Mac

I am fetching the start date of Meeting recurrence in outlook WebAddin using office.js API
"Office.context.mailbox.item.Start".
I am getting wrong start date value in case of "Outlook App for Mac".
The value is showing up correctly everywhere else :

Outlook App for window
Outlook webApp
O365
Outlook WebApp in Safari.

For an instance, If there is a meeting recurrence which is set up for 09/20/2018 to 03/20/2019
If I open any single meeting of that recurrence (let us say 12/25/2018), Below are the results for Start Date :

Outlook App for window : 12/25/2018
Outlook webApp : 12/25/2018
O365 : 12/25/2018
Outlook WebApp in Safari : 12/25/2018
Outlook App for Mac : 09/20/2018

@macOutlookExtensibility can you provide input about this issue?  Also please note that this same error report has been posted to Stack Overflow, so please add the answer/resolution to that Stack Overflow thread as well, as you resolve this issue.


include SourceRepositoryTypeContract class name

Codecov Report

Merging #47 into master will decrease coverage by 1.52%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #47      +/-   ##
============================================
- Coverage     32.48%   30.95%   -1.53%
- Complexity      104      109       +5
============================================
  Files            13       13
  Lines           274      294      +20
============================================
+ Hits             89       91       +2
- Misses          185      203      +18

Impacted Files
Coverage Δ
Complexity Δ

src/Events/HasWrongPermissions.php
0% <ø> (ø)
1 <0> (ø)
:arrow_down:

src/UpdaterServiceProvider.php
82.14% <0%> (-17.86%)
8% <0%> (+3%)

src/SourceRepositoryTypes/GithubRepositoryType.php
59.49% <0%> (-7.65%)
27% <0%> (+1%)

src/AbstractRepositoryType.php
15.9% <0%> (-1.17%)
20% <0%> (ø)

src/SourceRepository.php
0% <0%> (ø)
13% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84d08a9...9739c5a. Read the comment docs.


Allow changing the dimensionality of Melodic for AROMA.

Ready for review

Basically, if I didn't get this wrong, this is limiting the number of components that MELODIC can find?

Per https://github.com/poldracklab/fmriprep/issues/1051#issuecomment-380880940, it specifies rather than limits. There isn't currently a way to merely place an upper bound on the automatic dimensionality estimate.

An upper bound would be ideal. If only one could submit a PR upstream...
In any case, I've described the option in the general workflow documentation.

Hey, @dangom, I think this is your first contribution. Do you want to add your name to the zenodo file? (https://github.com/poldracklab/fmriprep/blob/master/.zenodo.json).

Pinging @dangom . Once you add your name to the zenodo file (or state you want to drop out) I can merge this contribution :)
Thanks!


Great performance degradation when increasing 'eval_freq'

Hi,
thanks for the repo! I'm trying it out, and I love that I can run experiments on complex environments in less than 10x the time than other non-jax libraries! Also, I love that it's a bit more modular than other jax-libraries!
Today, I was testing quick experiments on different environments such as 'Cartpole' and 'Halhcheetah,' and I noticed that when I increase the eval_freq the performance goes down a lot. For example, I wanted to collect more data than every 32768 steps in halfcheetah using PPO, and I set it to around one tenth, like 3000 steps, but it was much much slower!
I did some tests on Halfcheetah and Cartpole and I found the following:
For Hafcheetah

Total_steps
eval_freq
Time (s)

50_000
25_000
134

50_000
2_500
404

For Cartpole

Total_steps
eval_freq
Time (s)

50_000
500
12

50_000
50
22

I understand that I may incur in some overhead by evaluating more frequently so I tried changing the number of seeds in the evaluation (from 200 to 20) and also the number of environments and steps per environment but nothing changed.
Is there a way to mitigate this overhead? Is it due to how jax.jit work?
Thanks for the great repo!

Hi @e-zorzi! I'm glad that you're enjoying Rejax ❤
Since I don't know your exact setup, I don't think I can perfectly point out the reason for your issue. However, I strongly believe the slow-down you are experiencing is due to the increased number of steps that must be simulated for evaluation.
Why does this happen?
Let's look at HalfCheetah as an example, and assume that you're evaluating on a single seed only. You're training for 50k time steps, and evaluating for 50_000 / eval_freq * episode_length time steps. For an eval_freq of 2k / 25k, this will come out to be 2k / 20k steps. Your times for halfcheetah seem to imply a stronger slow-down, this might be because your GPU needs more time to load from memory for 200 environments.
To confirm this, I've run some experiments for CartPole, using the configuration in the configs folder:

eval_freq
max_steps_in_episode (eval)
num_seeds (eval)
total eval steps
Time (s)

500
500
200
100.000
70

500
50
200
10.000
34

500
0
200
0
30

5000
500
200
10.000
35

5000
50
200
1.000
3.5

As you can see, the training takes 30 seconds, and over the course of training, 5s / 10k * steps seconds are used for evaluation. This is pretty consistent if I plug in other values.
Another reason this could happen is that you actually train for more than total_timesteps steps, because of some weird hparams. You can easily exclude this by looking at the train_state after training.
How can you avoid it?
This is the hard part. Currently, the evaluation logic is set up in this way because it's convenient, and it's slow because it's sequential.  We can address both of these points, with some caveats.
Method 1: Evaluation during training
Other frameworks, such as cleanRL log returns of the episodes used in training. This means no additional environment simulations! However, it's non-trivial to set up using Gymnax. We would like to implement an environment wrapper that keeps track of the current episode's return and stores the final return after it has finished. However, Gymnax implements an auto-reset that does not carry over state (in which we would store the return), which makes this hard. There are two ways to address this:

Overwrite  gymnax.environments.environment.step to carry over state from the terminated environment. This is probably the cleanest option currently.
Track current return within the train_state on an algorithmic level. This will become much easier in v0.1.0 (releasing soon), where this could be implemented as a mixin.

Method 2: Parallel evaluation after training
Instead of the current return, your eval_callback could return a snapshot of model, and you can vmap evaluation across model parameters after training. This might be a very bad idea if you have larger networks or evaluate often since this quickly fills up memory.
Final words
So, what should you do? This depends on your requirements. Why do you need such a high resolution of your training curve? How much GPU memory do you have? How much effort do you want to put into making it work? Unfortunately, there is no easy solution.
Quick final note: if you jit the train function, your eval_callback will be jitted alongside it. You should actually not jit it individually, since it gives the compiler a little less room to optimize.
Let me know if you have any more questions! 🤗

Thanks for the answer, very thorough!
Evaluation is a very important topic in RL, but I understand that every library does it differently. I don't have particular reasons for collecting more frequent data, I was just surprised by the time difference! I will reduce the maximum length if I need it.
The way evaluation is carried out right now seems reasonable; the only question that I have is if, across different training seeds, the evaluation environments are the same. For example, I used the standard 200 environments for ppo eval, when training over 5 different seeds. Are the 200 environments used to evaluate the run with seed 1 different than those used to evaluate the training run with seed 2, let's say? Looking at the code, it seems so to me. Wouldn't it be better, for consistency's sake, to always use the same seeds for the eval environments, independently of the training run's rng? In that case, it would be like having always the same 200 environments, just different policies due to the training seeds. To be honest, I don't think it would change too much. By using 200 environments we already reduce variance a lot, but this would be noticeable when using fewer testing environments.
Also, have you considered writing a small wrapper / eval callback that collects data in the right shape for rliable ? It's a nice way to do evaluations the right way, and reviewers do like these kind of plots!
Ps. Btw yes, the larger slowdown might be due to some incompatibility between my CUDA and my JAX installations. I always get warnings that parallel compilation is disabled. I also use five seeds instead of one, tho I don't think it changes anything.

Using the same evaluation seed in each vmapped run can easily be implemented by overwriting the eval callback. E.g.
def eval_callback(algo, ts, rng):
    rng = jax.random.PRNGKey(ts.global_step)  # or some hardcoded value
    ...

Keep in mind that reducing the length of evaluation essentially changes the task. For example in CartPole, it's much easier to balance for 200 steps than it is for 500, because when approaching 500 steps you're much more likely to terminate by reaching the boundaries. This is why the default evaluation length was actually changed  in CartPole-v1.
I'm not sure if I understand your suggestion related to rliable. The input format for rliable is num_runs x num_games x frames (where frames refers to total_timesteps / eval_freq). Since we cannot vmap across different environments, this would leave us with num_runs x frames, which is already the shape of the evaluation that is returned. Could you elaborate on the format you were thinking of?

I hope I could help! I'll close the issue for now, feel free to reopen it if anything was unclear :-)


SDWebImage class name conflict if app includes SDWebImage

The Applozic framework includes the SDWebImage source files. If an app includes SDWebImage as well (as I do via CocoaPods), this results in runtime errors like the following:
"Class SDImageCache is implemented in both [Applozic framework] and [my app]. One of the two will be used. Which one is undefined."

Now you can use our cocoapod dependency.
https://cocoapods.org/?q=Apploz
-Thanks


Test for parseError using WITH and UNION ALL operators

@Agirish please review

One minor clarification needed. Can merge after that

Fixed the query workspace. @Agirish could you please review the changes?


Materials do not fire changed signal when any of its properties change

Godot version
4.0.beta7
System information
Irelevant
Issue description
Any Material Node Resource does not emit the changed signal when its properties change (Properties of base Resources still emit the signal)
Steps to reproduce
Copy-paste this script to any node
@tool
extends Node

@export var x: Resource:
	set(value):
		print("set")
		x = value
		x.changed.connect(foo)

func foo():
	print("changed")

Try different Resources and change their properties and watch when the changed signal is emmited.
When testing any Material derivate, any of its properties changing did not emitted the signal.
Minimal reproduction project
See above

I did some digging and there is no emit_changed() function call is made from Material except when changing shaders. Is this by design? Shouldn't the signal be fired every time any property of the Resource is changed?

I did not find any other Resource apart from Material that does this. Hope I didn't miss anythig...

The docs for changed and emit_changed() appear to indicate that change will be emitted for any change in a user facing property.
That being said, from working with the codebase for awhile, that definitely is not the case in practice. Many property setters do not have emit_changed() in them. I have always thought this was for performance reasons. In other words, only where the engine requires the changed signal will a property.
it looks like the docs were updated relatively recently by Mickeon in https://github.com/godotengine/godot/pull/67072. @Mickeon Do you have any additional insight as to whether emit_changed should be called from every property of a resource-inheriting class?

But wait, Material is not a Node, it is a Resource.

Ooops. I meant Resource

The docs for changed and emit_changed() appear to indicate that change will be emitted for any change in a user facing property.

That's why I expect to receive the signal on any change.
I am using a @tool script to scale and distort a Mesh based on the Material's albedo_texture and other stuff in the editor so that artists in my team can have easier life.
If this is how it is with other Resources, there should be a better consistency on when the signal is or isn't emmited.

I encountered this problem as well, but ended up using "property_list_changed" signal.
I'm making a terrain editor which uses individual ORM Materials and had to know when those change so I can update the texture arrays.

We discussed this on rocketchat with a few core contributors and the consensus is that the documentation should be changed to no longer say that changed will be emitted when any user-facing property is changed. The current state is that changed is emitted on a case-by-case basis in setters where users have requested it and shown a need for it.
The documentation for emit changed should be changed from:
Emits the [changed](https://docs.godotengine.org/en/latest/classes/class_resource.html#class-resource-signal-changed) signal. This method is called automatically for built-in resources.

to
Emits the [changed](https://docs.godotengine.org/en/latest/classes/class_resource.html#class-resource-signal-changed) signal. This method is called automatically for some built-in resources.

Then we should strive to note in the documentation for which properties changed will be emitted.

Going through all members of all resources will be a feat in itself, however if somebody wants to do it, we should have a reusable text to add in appropriate places. How about:
Setting [member x] will emit [signal Resource.changed] signal.

I also wrote a small tool script to test if changing certain properties will trigger changed.
@tool
extends Node

@export var resource : Resource:
	set(value):
		resource = value
		resource.changed.connect(func(): print("Resource changed"))

This may be automated further by iterating through property list and setting values, however I'm not sure how to handle all types in reasonable manner.

I think it would be more reasonable to note when changed is NOT automatically emitted, instead.

Material does really seem to be the odd one here, so far in my sporadical testing most resources do emit changed. There's some quirky ones as well, like SpriteFrames, which emits the signal when editing frames, but doesn't when adding/removing a whole animation.

I'm taking the update for the docs project.

Then we should strive to note in the documentation for which properties changed will be emitted.

Just for clarification, this details should be added in the Material class docs, right? Not in the Resource class docs.

It is not, sorry been a PR open and just linking it

It is not, sorry been a PR open and just linking it

Ah, it's fine, I'll just look for another issue!


UI Test: EditProfileView: Fix Test Caused due to #42 + #43

Fixes the failure of UI Tests in mainline master branch caused due to merging #42 and #43 together. #43 switched Country and Institute Field to CVTypeAheadField due to which the tests failed.

@Nitish145


Delete entity data for removed subgraphs

We need some kind of way to let graph-node users clear out entity data from subgraphs they have removed. Might be another json-rpc method

We have a script for that. 😁

Where is it?  Because it sure ain't the script frolm lutter.


use separate metrics per volume

Codecov Report

Merging #2253 (8d8939c) into main (16adb08) will increase coverage by 0.18%.
The diff coverage is 91.38%.

@@            Coverage Diff             @@
##             main    #2253      +/-   ##
==========================================
+ Coverage   61.77%   61.95%   +0.18%
==========================================
  Files         138      137       -1
  Lines       25052    25184     +132
==========================================
+ Hits        15477    15604     +127
- Misses       7771     7775       +4
- Partials     1804     1805       +1

Impacted Files
Coverage Δ

cmd/mdtest.go
28.48% <0.00%> (-0.18%)
:arrow_down:

pkg/meta/interface.go
54.92% <ø> (-0.63%)
:arrow_down:

pkg/metric/metrics.go
22.72% <ø> (-9.28%)
:arrow_down:

cmd/gateway.go
86.25% <75.00%> (-1.15%)
:arrow_down:

pkg/chunk/mem_cache.go
86.20% <80.00%> (-2.53%)
:arrow_down:

pkg/meta/sql.go
65.88% <80.00%> (-0.02%)
:arrow_down:

pkg/chunk/cached_store.go
77.39% <93.05%> (+1.01%)
:arrow_up:

pkg/meta/base.go
71.44% <96.15%> (+1.41%)
:arrow_up:

pkg/chunk/disk_cache.go
81.63% <98.14%> (+1.68%)
:arrow_up:

cmd/mount.go
61.95% <100.00%> (ø)

... and 11 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16adb08...8d8939c. Read the comment docs.


KAONRO1000-534 : Fix for build failure due to rdkshell_git.bb:do_patc…

…h error.
Reason for change: Due to recent changes on rdkcompositor.cpp, rdkcompositor.h files, SWRDKV-2949_rdkshell_checking_dirty_to_draw.patch was resulting in hunk errors.
Added the changes from the patch file to the code directly in order to avoid similar issues in the future.
Test Procedure: Build should be successful. Details updated in individual tickets.
Risks: Low/None.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Honey Gupta seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/8967/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-rdk-next-platform/19535/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/14103/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/47739/ started.

build-rpi-hybrid-refapp2-rdk-next Console Log uploaded to Gist URL: https://gist.github.com/5012b97fc5c32d490870a83d19c5f563

build-rpi-mc-wpe-rdk-next Console Log uploaded to Gist URL: https://gist.github.com/ac11a5852b5b66ccb3497ecb1a3ed2b4

build-brcm-refboard Console Log uploaded to Gist URL: https://gist.github.com/daddb6310157f0728e235203fb92137d

build-rpi-hybrid-wpe-rdk-next Console Log uploaded to Gist URL: https://gist.github.com/f66575a59c6da8a9cd1b1265187c3353


better configuration options

What about making the symfony bridge more configurable (similarly to the zf2 bridge)? People wouldn't need to write the whole container initialization. I suggest creating a proper PhpDiBundle for Symfony, with a Container factory and with support for the Symfony configuration files.
I already started with the implementation, you can see the work in progress in my fork:
https://github.com/Rastusik/Symfony2-Bridge
Also I'd like to create a console command to be able to clear the php-di (similarly as in the zf2 bridge).

I'm not sure how it would work because currently we create the PHP-DI container when the Kernel is created. Maybe it's possible.
However I'm not a huge fan of the idea. Having to implement, document and (for users) learn a different API for configuring the container doesn't sound really useful. I hate when I have to use a Symfony bundle that integrates a library and I can't use the official library's documentation because the bundle offers custom configuration keys.
For example a problem with the ZF2 bridge is that I can't use all the features of PHP-DI. E.g. I can't use all the caches available.

well, all the features can be implemented (also in zf2 bridge) if somebody requests them.
I didn't want to change the process of the PHP-DI container creation, I just wanted to wrap the code into a factory and create configuration options for it. It works perfectly by the way, I have a demo. My point is that the container creation process messes up the AppKernel class and there might be use cases, where you can't configure your cache in the AppKernel because of various dev and prod environments. Also cache clearing would be united in the console command and would be able to use the cache configuration for the given environment.
I think that when some basic work is done, it would be really easy to implement all the possible configuration options afterwards, after people request them.
It's just an idea, I can maintain my own fork, I just wanted to let you know.
In the worst case, nobody can force the user to use the factory, since it would be called from the extended appKernel, current way of integration would be still possible.

btw the same case is with the zf2 bridge, I can update the docs with former usage info, which is still possible to use

all the features can be implemented (also in zf2 bridge) if somebody requests them

(emphasis mine) That's the point. Users are dependent on the maintainer willing and having time to support such features. And they have to wait for it. It doesn't really matter if it's easy to add after all, if it's not there it's not there and users are stuck. Most users wouldn't bother opening an issue btw, they would just realize it's limited when they try out the project and drop it.
It also introduces coupling with a specific version. If some new options are added (e.g. php-di/php-di#299) then every framework bridge needs to be updated to support this new option (and it usually takes time). Same goes if some options are removed in major versions.
I'm not totally closed to it though, especially if you think there are benefits.

Well the decision is up to you :) I have mentioned the benefits (especially the clear cache command, and custom configuration for different environments).
Current usage can be applied as well, if it's always mentioned in the docs, so I think it's a win-win :)
Maybe some of the users will go with the current way and will find limitations and will open a feature request after all, since they won't find a better DI container elsewhere.
I think I would be able to implement such feature requests since most of them would be only about being able to configure the container. But even if not always, there will be ways to fallback to the current solution for some time.

I'll close this. I want bridges to be as simple as possible: users should be able to configure PHP-DI the same way whatever the framework is. It also avoids having to implement options and document everything twice.


Gateway broken on K3d

Steps to reproduce

Run the project as a Dev Container, using a prepared k3d Kubernetes environment. (or a Codespace)

There's a DevContainer in the provided repo.

Deploy this file
Use curl to fetch resources at port 80 from the nginx Service (works):

Use curl to try and fetch resources from one of the api services (does not work)curl http://localhost/blue/api/color/

<title>404 Not Found</title>

404 Not Found

nginx/1.25.5

curl http://localhost/api/color/

<title>404 Not Found</title>

404 Not Found

nginx/1.25.5

The nginx Service receives the request, not the blue or green API.

Observed behavior
Gateway does not work.
Desired behavior
Gateway resource should work in the recommended way of Getting Started.
Workaround
Use docker desktop K8s or AKS. Gateway does work over there.
Docker Desktop:
curl  http://localhost/api/color
green

curl  http://localhost/blue/api/color/
blue

 curl  http://localhost
<!DOCTYPE html>

<title>Welcome to nginx!</title>
...

rad Version
RELEASE   VERSION   BICEP     COMMIT
0.34.0    v0.34.0   0.34.0    0fd82e7eaa9388fead4ea76cb9137ba2a225a236

Operating system
Windows11 running WSL Dev Container based on mcr.microsoft.com/devcontainers/base:bullseye
Additional context
No response
Would you like to support us?

[ ] Yes, I would like to support you

AB#12414

Noticed that in docker-desktop, I get responses from Envoy, not Nginx.
Created the cluster without the default ingress: k3d cluster create -p '8081:80@loadbalancer' --k3s-arg '--disable=traefik@server:0'

/assign @brooke-hamilton

@loekd thank you for opening this issue! 🚀
I can reproduce this on radius version 0.36.0 and k3d version v5.7.3 (current versions).
Steps to reproduce

Clone the repo, launch VS Code and open the root folder of the repo, and run the dev container.
When the container is running, open a new terminal window.
Install radius (or build radius from source): wget -q "https://raw.githubusercontent.com/radius-project/radius/main/deploy/install.sh" -O - | /bin/bash
Install k3d: wget -q -O - https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | bash
Create a new k3d cluster: k3d cluster create -p "8081:80@loadbalancer" --k3s-arg "--disable=traefik@server:0"
Install Radius on Kubernetes: rad install kubernetes --set rp.publicEndpointOverride=localhost:8081
Run the kubectl command to list all pods: kubectl get pods -A

Expected result
All pods are running
Actual result
The contour-envoy pod is stuck in pending state.
$ kubectl get pods -A
NAMESPACE       NAME                                      READY   STATUS    RESTARTS   AGE
kube-system     coredns-576bfc4dc7-5xcwh                  1/1     Running   0          2m53s
kube-system     local-path-provisioner-6795b5f9d8-h9qxz   1/1     Running   0          2m53s
kube-system     metrics-server-557ff575fb-qnhdp           1/1     Running   0          2m53s
kube-system     svclb-contour-envoy-e3d65e8f-mkx54        2/2     Running   0          113s
radius-system   applications-rp-5847558fc6-ffdzm          1/1     Running   0          2m32s
radius-system   bicep-de-6d9654cd69-gkg82                 1/1     Running   0          2m32s
radius-system   contour-contour-6978b48f5d-fhndb          1/1     Running   0          113s
radius-system   contour-envoy-f88bx                       0/2     Pending   0          113s
radius-system   controller-7948677468-gk6ck               1/1     Running   0          2m32s
radius-system   dashboard-65cb99dbd4-nwbn9                1/1     Running   0          2m32s
radius-system   ucp-86b4fc44cd-7w7fs                      1/1     Running   0          2m32s

I'm working on a fix.

The root cause is that k3d by default includes servicelb as a feature using klipper-lb, which conflicts with the load balancer deployed by Radius.
The fix is to disable servicelb when creating the k3d cluster, which will allow the load balancer deployed by Radius to manage traffic.
k3d cluster create -p "8081:80@loadbalancer" --k3s-arg "--disable=traefik@server:*" --k3s-arg "--disable=servicelb@server:*"

The Radius docs need to be updated with this information. I will submit a PR to the docs repo and close this issue when the PR is merged.
Additional information
Radius uses contour as a load balancer. You can see this by examining the deployments in the radius-system namespace.
$ kubectl get deployments -n radius-system
NAME              READY   UP-TO-DATE   AVAILABLE   AGE
applications-rp   1/1     1            1           77s
bicep-de          1/1     1            1           77s
contour-contour   1/1     1            1           35s
controller        1/1     1            1           77s
dashboard         1/1     1            1           77s
ucp               1/1     1            1           77s

@loekd thanks again for creating this issue.
@willdavsmith thank you for pointing me to servicelb.


Data fitting bootstrapping

Add support for more straightforward bootstrapping of fit errors in data_fitting_functions; rework bootstrapping to be amenable to bootstrapping of fit-based statistics, including adding error handling and returning a covariance matrix.

Need to rebase onto main first; accidentally based off of other branch


Add social link support for LinkedIn, Threads, and Twitch

What kind of changes does this PR include?

Changes to Starlight code

Description

Closes #329
Adds icons and config options for social links to LinkedIn, Threads, and Twitch

size-limit report 📦

Path
Size

/index.html
13.15 KB (0%)

/_astro/*.js
16.21 KB (0%)

/_astro/*.css
8.53 KB (0%)

Thanks!


PDF Output Produces Malformed PDF

<EMAIL_ADDRESS>commented:

Which version of PhantomJS are you using? Tip: run 'phantomjs --version'.
1.8.1
What steps will reproduce the problem?

Export any webpage as pdf like so:

var system = require('system');
if (system.args.length !== 2) {
phantom.exit();
} else {
var url = system.args[1];
}
var page = require('webpage').create();
//page.viewportSize = { width: 240, height: 320 };
page.paperSize = { format: 'Letter', orientation: 'portrait', margin: '.5in' };
page.open(url, function () {
var random = Math.floor(Math.random()*11234724357);
var filename = 'temp' + random + '.pdf';
page.render(filename);
console.log(filename);
phantom.exit();
});
What is the expected output? What do you see instead?
PDF opens but in acrobat, document properties such as page size show blank, and pdf is not able to be saved again from acrobat pro. The following error shows: The document could not be saved. There was a problem reading this document (135).
Which operating system are you using?
Centos 6.3
Did you use binary PhantomJS or did you compile it from source?
Binary
Please provide any additional information below.
All other non-phantomjs pdf's work fine. Behavior is also present on windows 7 64-bit.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #1069.
:star2:   2 people had starred this issue at the time of migration.

Duplicate.


add all props that are available in email template

This was created in regard to #2125
Additional info can surely be added but this should give users a quick overview over what can be used in what template without having to dig through the templates first.
Categorization is subject to change but I thought this was fitting because it is a) configuration of an existing instance and b) done after deployment.
Open for any changes as always :)

Thanks @amyblais for the review! Resolved all changes :)

Added some more text that might be useful for anyone seeking info about the email templates.

Thanks @lieut-data and @wiersgallak for reviews. Should be good to merge now :)


Websocket Server Interface not passed downwards to agent

The websocket server seems to have some issue
in line 52, self.interface.register_client(websocket) it doesn't seem to pass down to the underlying agent's  interface

@CUexter sorry websocks is no longer supported - could you please use the REST API (https://memgpt.readme.io/reference/api) or Python client instead?


change namespace style

change namespace style  with CamelCase
for  example  Yii\Base\Model       not   yii\base\Model
maybe change in next version ???

huh, why?

Technically we can do that but I see no reason.


All iterations of templated tests should be executed even if one is skipped

In the documentation, it is written that :

Templated tests are also special so that all the rounds are executed even if one or more of them fails. It is possible to use this kind of continue on failure mode with normal tests too, but with the templated tests the mode is on automatically.

In particular : all the rounds are executed even if one or more of them fails
However, if one is skipped, none the following rounds are not executed.
I don't know if it was intended or not but it caused some problems on my tests.
Example:
*** Test Cases ***
Eat yellow fruits
    [Documentation]    Eat only yellow fruits, Fails if item given is a fruit which is not yellow and skip if item is not a fruit
    [Template]    Check fruit and eat it
    red_apple       # FAIL
    banana          # PASS
    plane           # SKIP => not a fruit
    lemon           # should be PASS but is not executed

The documentation is from the time when the SKIP status didn't exist. I believe we didn't really think about this when implementing SKIP, but I have a vague feeling this has been discussed at least once afterwards. I kind of agree it would make sense to run all iterations in this case, but then again explicitly skipping an iteration can be considered to mean "skip remaining iterations".
If we agree to run all iterations also after SKIP, we need to decide what status the test should have if some iterations FAIL. Nowadays an iteration ending with SKIP after an iteration with FAIL gives the test the SKIP status. I believe FAIL after SKIP should behave the same way, but we could also consider changing the overall logic so that any failed iteration gives the test the FAIL status. That would match how any failed test gives a suite the FAIL status regardless of the status of the other tests. Then again, SKIP in test teardown overrides possible earlier FAIL.
I think it would be good to hear opinions from others regarding to these semantics. I'll start a thread about this on the #robotframework channel on our Slack.

If we'd change semantics so that tests get the FAIL status if any iteration fails, regardless are some iterations skipped or not, we should also decided how to handle a case where some iterations pass and some are skipped. I think logically then the test status should be PASS. The test would then get the SKIP status only if all iterations are skipped. This is the same logic we use when deciding the suite status.

Hi,
Is there any update on this?
Is this going to be implemented in the near future?
Thanks!

@pekkaklarck How can I ask any of the maintainers to check the pull request I created on this enhancement? (https://github.com/robotframework/robotframework/pull/5244)

PR #5244 by @olesz looks so promising that I added this to RF 7.2 scope. The change is backwards incompatible, because earlier a SKIP in an iteration after a failed iteration causes the test to be skipped, but after the change the test will fail. I don't think this is so severe that the change needed to wait for a major release, though. Although this issue is now labeled as an enhancement, the current behavior where iteration failures are masked by skips could also be considered a bug.

Implemented in PR #5244 by @olesz. Big thanks for the contribution!

I tested how this works with templates using IF and FOR. To my small surprise everything mostly worked well, but there were problems at least with error reporting when using FOR. I'll reopen this, investigate problems and fix them.

Do you want me to do the debugging? If you share what you've found maybe I can help finding the root cause.

I already found the root cause and I'm working with the fix. I just noticed another issue (#5276) and fix that first.

This example demonstrates the problem:
Example
    [Template]    Run Keyword
    FOR    ${x}    IN    a    b    c
        Skip    ${x}
    END

The following changes seem to fix the issue. I'm not sure is this the best fix yet, but I'll think about that more after lunch.
--- a/src/robot/running/bodyrunner.py
+++ b/src/robot/running/bodyrunner.py
@@ -56,18 +56,19 @@ class BodyRunner:
                 self._run = exception.can_continue(self._context, self._templated)
         if passed:
             raise passed
-        if errors and self._templated:
+        if errors and self._templated and any(e.skip for e in errors):
             errors = self._handle_skip_with_templates(errors, result)
         if errors:
             raise ExecutionFailures(errors)

     def _handle_skip_with_templates(self, errors, result):
-        if len(result.body) == 1 or not any(e.skip for e in errors):
+        if len(result.body) == 1 and not result.body[0].type == 'FOR':
             return errors
         if all(item.skipped for item in result.body):
             raise ExecutionFailed('All iterations skipped.', skip=True)
         return [e for e in errors if not e.skip]

+
 class KeywordRunner:

Hello @pekkaklarck, i just noticed that on a template if i want to skip a specific input case it skips the whole test and does not continue with the other input cases.
Example of what i am talking about below,
*** Test Cases ***
Eat yellow fruits
    [Documentation]    Eat only yellow fruits, Fails if item given is a fruit which is not yellow and skip if item is not a fruit
    [Template]    Check fruit and eat it
    plane             # SKIP
    banana          # should be PASS but is not executed
    lemon            # should be PASS but is not executed

It seems that the issue with FOR loops is best handled with ForRunner. It's even simpler than what I proposed earlier. I created plenty of new tests that all now pass. I'll run all acceptance tests locally and commit changes if there are no regressions.


chore(main): release zeta-icons 0.7.0

:robot: I have created a release beep boop
0.7.0 (2024-10-18)
✨ New Features

Created script to generate Android icons (4154878)
Icon updates 18-Oct-2024 (3423869)

🪲 Bug Fixes

Fixed code connect script (abe548d)
fixed import path for script (cb7501d)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

zeta-icons-v0.7.0
:sunflower:


frontend: fix crash on service list page

This fixes #2027 where the service list page crashes when there is at least one service without port.

Thank you so much @msuret for this change, I have tested with a dummy service with no port specified and it works 🎉


Celery requeue tasks

Ref: #2442

@nooraangelva when everything is passing could you please rename the commit message?  What about cases where the task actually can't succeed due to various reasons (as happens often during ORCID push or HAL push). Wouldn't that be a problem?

That's actually a good point. there is a warning in the documentation about the infinite loop.
I was thinking, that instead of Reject()  we could use Retry() instead. That can have max_retries so there is no infinite loop.

So what would be the best solution for this? Any thoughts @drjova?

We are already retrying the tasks, I think we should keep doing that instead of a global solution.

Okay, so this PR and issue can be closed then?


Update windows-10-subscription-activation.md

Changed enterprise app name Universal Store Service APIs and Web Application, to Windows Store for Business to reflect name changes.

<!--
## Description
Universal Store Service APIs and Web Application was renamed to Windows Store for Business
## Why

Searching Conditional Access for Universal Store Service APIs and Web Application yields no results. Instead, you need to use the new name Windows Store for Business

Thanks @v-aweber - I'm no expert on this topic, but I did some hunting, and looking in one Azure tenant, the name there is "Universal Store Service APIs and Web Application":

So I think the doc is accurate. Given the retirement of "Store for Business" I'm assuming we shouldn't be using that term anymore. So I'm inclined to close this PR and leave the doc as-is...but let me know if you have other thoughts/justification for the change. Or if I need to dig deeper with others.

It's possible that this varies by a tenant's creation date, but in many of my customers tenants this app is only searchable in conditional access as Windows Store for Business. I'll try to provide examples

I had multiple peers confirm this behavior in conditional access

This is likely because of how the rename is only reflected in the home tenant
https://learn.microsoft.com/en-us/entra/identity-platform/app-objects-and-service-principals?tabs=browser#consequences-of-modifying-and-deleting-applications

I'm going to go ahead and close this and open an issue as I'm discovering this is a more complex issue.


App not working when upgrading from angular beta to angular rc-1

Are there any special requirements for this kind of upgrade? Is the problem related to npm package (angular is now distributed as @angular)?

@vdest, the rc-1 release has several changes that are incompatible with the beta releases. I have decided not to upgrade angular2-seed-sass to rc-1, because I have personally switched to angular-cli. While it is still in beta, the tool has the official support from the Angular team and has the best minds working on it. I would highly recommend that you switch over too and help the angular-cli team make that tool better.


Fixing unit tests covarage

Codecov Report

Merging #86 into dev will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev      #86      +/-   ##
==========================================
+ Coverage   89.03%   89.04%   +<.01%
==========================================
  Files          41       41
  Lines        1122     1123       +1
  Branches      130      131       +1
==========================================
+ Hits          999     1000       +1
  Misses         84       84
  Partials       39       39

Impacted Files
Coverage Δ

...n/jira/authorization/JiraAuthorizationManager.java
73.71% <100%> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update abe6094...3488bf8. Read the comment docs.


Add missing image filename to system_path sensor

Proposed change

Add missing image filename to system_path sensor
Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:

Codecov Report

Merging #343 (f387550) into 0.3.0 (92bda11) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            0.3.0     #343   +/-   ##
=======================================
  Coverage   96.87%   96.87%
=======================================
  Files           3        3
  Lines         769      769
=======================================
  Hits          745      745
  Misses         24       24

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
96.39% <100.00%> (ø)

Codecov Report

Merging #343 (f387550) into 0.3.0 (92bda11) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            0.3.0     #343   +/-   ##
=======================================
  Coverage   96.87%   96.87%
=======================================
  Files           3        3
  Lines         769      769
=======================================
  Hits          745      745
  Misses         24       24

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
96.39% <100.00%> (ø)

Codecov Report

Merging #343 (f387550) into 0.3.0 (92bda11) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            0.3.0     #343   +/-   ##
=======================================
  Coverage   96.87%   96.87%
=======================================
  Files           3        3
  Lines         769      769
=======================================
  Hits          745      745
  Misses         24       24

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
96.39% <100.00%> (ø)

Codecov Report

Merging #343 (f387550) into 0.3.0 (92bda11) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            0.3.0     #343   +/-   ##
=======================================
  Coverage   96.87%   96.87%
=======================================
  Files           3        3
  Lines         769      769
=======================================
  Hits          745      745
  Misses         24       24

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
96.39% <100.00%> (ø)


Fix nuget package no strong name issue

The strong name check is mandatory for commercial software, as references to nuget packages without strong names will result in compilation errors.

@chsakell Sorry to bother you, but this fix affects whether or not our team uses this lib, and we hope you'll take care of it as soon as possible, either by working around it or by rejecting the pull request.


Suggest (new and senior) editors to provide a meaningful edit summary

As iD went live lots of people appearig out of nowhere and making (mostly useful) edits. What I have observer was that the edits with (empty) summary skyrocketed. This is pretty bad for QA work as we cannot even guess sometimes what the editor wanted to do.
It would be nice to suggest editors to provide a few words about what they were thinking they were doing.
Right now it says "Brief description of your contributions".
I'd suggest something along the lines of ``Please briefly describe your contribution to help fellow editors to easily browse and verify your edits (like "adding POIs around Whateverland",  "adding new roads from satellite imagery" or "fixing road geometry using gps tracks").''

Please make changeset comments mandatory. Good practice should be baked into all software, especially those used by new users most of whom will not be bothered to read the wiki.
This is a critical issue that's eating up time and resources for mappers that could be doing more productive things.

This problem is not going away. Like JOSM, iD should pester users to input something so at least they realize their behavior is contrary to community standards. Instead, many new users are treating empty comments as the norm. I appreciate how accessible iD has made OSM, but the defaults really need to be more beneficial to the community.
Here are just a few examples.
https://www.openstreetmap.org/user/thisishap/history
https://www.openstreetmap.org/user/RVA_101/history
https://www.openstreetmap.org/user/JudeD/history
https://www.openstreetmap.org/user/llee4PRI/history
https://www.openstreetmap.org/user/mtblocal1/history
https://www.openstreetmap.org/user/Hobgoblin3/history
https://www.openstreetmap.org/user/formula155/history
https://www.openstreetmap.org/user/crshortt/history
There's also the problem of creating too many changesets per editing session, but that's another issue.

@fred702 Have you tried reaching out to any of those users with a friendly note explaining how the community uses edit summaries and what a good one looks like?

@jfirebaugh I have, but that approach doesn't scale given the size of the globe and rate of new users. Perhaps Mapbox could hire some more employees to handle that task.

Given what a distraction this issue has become, I've decided to just add the code so that the save button is disabled if there is no comment and enabled if there is some text in the comment.


Add the configuration of whether to print SQL. The default value is f…

Add the configuration of whether to print SQL. The default value is false

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

fix: Add the configuration of whether to print SQL. The default value is false

Replaced by: https://github.com/casdoor/casdoor/pull/429


Fix misplaced ripple effect

Fixes misplaced ripple effect, while touching element.
Source: https://github.com/facebook/react-native/issues/6139

Before
After

P.S. Unfortunately, I failed to move changes to only one place, so @xotahal, let me know if I can improve this PR.

Codecov Report

Merging #195 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #195   +/-   ##
=======================================
  Coverage   79.48%   79.48%
=======================================
  Files          19       19
  Lines         731      731
  Branches      107      107
=======================================
  Hits          581      581
  Misses        123      123
  Partials       27       27

@xvonabur Like it man :) will take a look .. thx

Is this change already on npm? :)

I don't believe these changes are there on npm. Any idea when it will be released.

@riteshmalav @jaulz I think it was broken with some recent changes. See #311
Unfortunately I do not have time to provide demo for it.


Add travis support

Travis is a continuous integration server which offers a free service to allow you to run build tests and have the ability to reflect its state in the repository. For reference see https://github.com/suhailshergill/extensible-effects (note the  badge).
below is an outline of a possible plan:

[ ] add a build file which captures all the tests/checks we want to run on the CI system. For reference see https://github.com/suhailshergill/extensible-effects/blob/develop/Makefile#L66. Note: this step is optional and is not strictly necessary
[ ] add a .travis.yml file which configures environment and invokes the tests which need to be run (either by directly specifying or referencing build file if one exists). For reference see https://github.com/suhailshergill/extensible-effects/blob/develop/.travis.yml
[ ] enable build in travis-ci
[ ] Profit! ;)

let me know if the above makes sense, and i would be happy to contribute and lend a hand.

This sounds like a good idea. I want to get our test suite hooked up and I think we should do this.

@zaxtax If you want to do this, take a look at the .travis.yml files in my other Haskell projects (e.g., the one for bytestring-lexing). They include stuff for how to simultaneously build against multiple different versions of GHC. The biggest trick is getting the total build time for all the dependencies down to something reasonable.
If you want pointers, I'll be around this week; though I won't have time to work on it myself until a couple weeks out.

So, one concern I have is how do we specify conditional testing. For example, we have tests that only pass if a version of maple is installed. What's the standard way to disable those from cabal?

depends on where you're doing the check to ensure that maple is/isn't
installed, but you could use flags in cabal to selectively enable/disable
portions. these flags could be passed in via the invocations in travis
On Thu, Feb 18, 2016 at 11:20 PM, zaxtax<EMAIL_ADDRESS>wrote:

So, one concern I have is how do we specify conditional testing. For
example, we have tests that only pass if a version of maple is installed.
What's the standard way to disable those from cabal?
—
Reply to this email directly or view it on GitHub
https://github.com/hakaru-dev/hakaru/issues/9#issuecomment-186043540.

--
Suhail


Testing NbtdocHelper

Testing #332

[x] Navigation
[x] Completion
[x] Validation

[x] Boolean
[x] ByteArray
[x] Byte
[x] Compound
[x] Double
[x] Enum
[x] Float
[x] Id
[x] Index
[x] IntArray
[x] Int
[x] List
[x] LongArray
[x] Long
[x] Or
[x] Short
[x] String

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Error while accessing V1.14.0 - Error invoking remote method 'send-http-request': Error: connect ETIMEDOUT <IP_ADDRESS>:443

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
While accessing our services thru bruno i am getting the below error : Error invoking remote method 'send-http-request': Error: connect ETIMEDOUT <IP_ADDRESS>:443. Any recommendation on how to solve this.
.bru file to reproduce the bug
No response
Screenshots/Live demo link

Hey @Praveena-Jayabalan, will you be able to provide more details on this issue with a .bru file? Are you behind a proxy?

I've same issue, it works well with postman.


failed to build workspace

Hi,

What
Version

OS
16.04

branch
kinetic

Java verison
8

Clean workspace, clean checkout of the repo, up to date Ubuntu (latest updates installed),  I am getting this error

[100%] Gradling tasks for knowrob_common
cd /home/ferenc/work/kr_ws/src/knowrob/knowrob_common && ROS_MAVEN_REPOSITORY=https://github.com/rosjava/rosjava_mvn_repo/raw/master /home/ferenc/work/kr_ws/build/knowrob_common/catkin_generated/env_cached.sh /home/ferenc/work/kr_ws/src/knowrob/knowrob_common/gradlew -q installApp publishMavenJavaPublicationToMavenRepository writeClasspath

FAILURE: Build failed with an exception.

* Where:
Script 'https://github.com/rosjava/rosjava_bootstrap/raw/kinetic/buildscript.gradle' line: 44

* What went wrong:
A problem occurred evaluating script.
> Could not find method google() for arguments [] on repository container.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Any ideas? It seems to be some gradle issue; the one with rosjava is too old or something; Did anyone else have this error?

could be that they have changed the build file upstream.
at least the google() statement looks new to me, and I don't what it is supposed to do.

Thx @daniel86  for the quick reply ....it is new...they changed things 9 dayst ago and released only part of it ...rosjava is a piece of<EMAIL_ADDRESS>let me know if you ever want to rewrite everything in C++, I volunteer for helping; Anyway...I had to recompile rosjava from source (!@$$).  I changed all the gradlew files and content of the gradle folders in the ros packages (is there no automatic way of doing this?); This is needed because  the new gradlew is version 4.10+ the one in knowrob packages is 2.10; This fixes the google() issue.
Using ./gradlew build in the local folders now works, but, using catkin make I get:
Task 'installApp' not found in root project 'knowrob_common'. Some candidates are: 'install'.

any clues?

https://github.com/rosjava/rosjava_build_tools/pull/35


Fix JSONSchema for Embedded Objects

When embedding objects within a JSON Schema their Required field should
not be embedded within the "properties" field, but one level above with
the type information.

add unit tests to test object and array with embedded object schema
required fields generation has always been in wrong location

move it outside of properties

move object notation outside of schemaToJSONSchema into higher level
public method to make it re-usable

OK, third time's the charm. This one takes @smyrman's advice and removes the extra flag and also fixes the required array. It's always been in the wrong place, embedded in properties.

beefed up the unit test to check for required field at the correct level in schema


[ENH]: Enhance error messages to include actual type information

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Enhanced error messages to include actual type information in api/types.py validations

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

None

@tazarov Can you please review it again? In the initial CI run, PR name condition was failing. I have made the necessary changes to  rectify that


clone! macro doesn't execute closure

I have a weird case, where the callback closure doesn't gets executed. After playing a bit with the code, I was able to found out that the clone! macro is the issue.
This is the code which doesn't work. No clicked message.
        // save_button
        get_widget!(self.builder, gtk::Button, save_button);
        save_button.connect_clicked(
            clone!(@weak self.widget as widget, @weak self.builder as builder, @strong self.song as song, @strong self.sender as sender => move |_| {
                debug!("clicked");
            }),
        );

After removing @weak self.builder as builder, the closure works, and the message gets printed.
        // save_button
        get_widget!(self.builder, gtk::Button, save_button);
        save_button.connect_clicked(
            clone!(@weak self.widget as widget, @strong self.song as song, @strong self.sender as sender => move |_| {
                debug!("clicked");
            }),
        );

Affected source code: https://gitlab.gnome.org/World/Shortwave/blob/master/src/ui/song_row.rs#L61

The origin of the problem is very likely because self.builder is destroyed which makes it impossible to get retrieved and therefore it is returned before even calling your closure.
I think we should print messages in such cases in debug builds by default. Like I proposed in https://github.com/gtk-rs/glib/pull/596
cc @sdroege @EPashkin

Yes this is a case of using weak references wrong. You need to ensure that your objects stay alive or otherwise they would be None inside the closure and it directly returns.

I think we should print messages in such cases in debug builds by default.

I disagree with that. This is the expected behaviour of weak references. If there's anything printed I'm ok with having a separate, non-default feature for that.

This doesn't make much sense for me. self.builder shouldn't get destroyed.
https://gitlab.gnome.org/World/Shortwave/blob/master/src/ui/song_row.rs
Can anyone help me to understand it? :thinking:

@sdroege: And that's where I don't agree with you: for the clone macro users, it won't be obvious at all where the issue comes from since it's difficult to find it by just reading the source code since they very likely won't be aware of how it actually works (well, that's not great but it should definitely be taken into account).
Therefore, when running in debug mode, I think it'd be better to enable the feature to have those error messages.

I fixed the issue with this commit:
https://gitlab.gnome.org/World/Shortwave/-/commit/f19eb7b0226c0d223b8127452679c2c84301734b
Though I'm still not sure what caused issue.

@GuillaumeGomez In that case that either means that the clone macro is not to be recommended in this form, or our documentation for weak references has to be improved, or people don't read documentation :)
We could maybe make use of the log crate for this, then it can be enabled/disabled in downstream code as needed? I don't know what the overhead of that is if it's unused, so that needs to be investigated.

Can anyone help me to understand it? :thinking:

Taking a look after dinner :)

@haecker-felix Can you check expansion of wrong version? Ex. with cargo expand

also seems you can just move button_stack without adding it to clone!

@haecker-felix The reason is that the SongRow you create in SongListBox::add_song() is directly dropped at the end of the function. Nothing is keeping it alive. So that then also drops the builder, of which the only strong reference is stored in the SongRow.
I think that hints at a bigger conceptual problem here.
Also, moving a strong reference to the builder into that closure will create a reference cycle between the builder, the button, the closure and again the builder.

We could maybe make use of the log crate for this, then it can be enabled/disabled in downstream code as needed? I don't know what the overhead of that is if it's unused, so that needs to be investigated.

I don't see the point of adding the log crate for that. Also, you can just disable the feature if you don't want it on debug mode. :)

I don't see the point of adding the log crate for that. Also, you can just disable the feature if you don't want it on debug mode. :)

If you make it a non-default feature then I'm fine with that

I never wanted it as a default feature (except on debug).

I don't want it as default feature, at all :) That would make the clone macro useless for me as it's going to print stuff in perfectly valid situations.

@haecker-felix The reason is that the SongRow you create in SongListBox::add_song() is directly dropped at the end of the function. Nothing is keeping it alive. So that then also drops the builder, of which the only strong reference is stored in the SongRow.

Ooh... Damn. That makes sense. Thanks for the help.
A feature (doesn't matter if default or not) which prints warning messages in those cases would be helpful to prevent this in future.

I don't want it as default feature, at all :) That would make the clone macro useless for me as it's going to print stuff in perfectly valid situations.

What prevents you from disabling it if it's enabled by default on debug? :)

What prevents you from disabling it if it's enabled by default on debug? :)

Every crate that depends on glib would have to have default-features = false in its Cargo.toml for that to work, otherwise the feature would be enabled.
So if I have a crate that depends on gio, and gio does not have default-features = false in its own Cargo.toml then I wouldn't be able to disable the feature.

But if it's only on debug, who cares? :-/
Anyway, at the minimum, we should add the feature and discuss about making it default later on (and of course make it obvious in the documentation).

But if it's only on debug, who cares? :-/

It will produce a lot of noise when I'm developing, so I care :)

Ok... I guess it won't be a default feature then. I need to think about how making it obvious not to miss it...

Maybe use "env!(GTK_RS_DISABLE)" to disable ?

As discussed on IRC we would go with using the GLib logging system: https://github.com/gtk-rs/glib/issues/610
That can be enabled/disabled with environment variables btw.


uLimit should not need root password removal for system-wide softwares (without shell access).

Windows Build Number
Microsoft Windows [version 10.0.19043.1165]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.4.72
Distro Version
Ubuntu 20.04
Other Software
VSCode 1.59.0 with remote-wsl v0.58.2
Repro Steps
Use a lot of extension and/or open a workspace with a lot of file
Expected Behavior
All extensions are loaded correctly
Actual Behavior
Extensions fail to load due to EMFILE (too many open files)
Not always the same extension.
More information
As stated here by @JohnSully

It's crazy that this is somehow marked closed and fixed. The sudo su workaround works for me, but that really shouldn't be necessary. Needing to disable sudo passwords is a security risk.

Also, the actual workaround remove WSL_* env vars which not viable in some cases, stated here by @pecigonzalo

It actually does not even work, as doing sudo su - username removes all the WSL_ vars.

I see people around me still downgrading to WSL1, but it's clearly not a good option given the drawbacks.
Even here people do the same by @rbabayoff
The existing workaround from within the terminal does not work (like this, this and more) and can't be used with VSCode with remote WSL as when the soft start it's already "logged in" to the WSL VM.
In the current state, the only solution is to remove the root password, which is not a viable solution when working with sensible data.
Diagnostic Logs
Not needed.

Related to #1688

And even by using the "remove root password", it doesn't work

FYI, I do this now with https://github.com/pecigonzalo/dotFiles/blob/master/wsl/wsllogin.sh#L25 and a sudoers config that allows me to call that command without a password.

Well thanks for the tips, even if it does not solve the initial issue.

@pecigonzalo
End of ~/.profile:
sudo prlimit -p "$$" --nofile=10000:10000
exec sudo su storm --shell $SHELL

I shutdown WSL, then restarted VSCode:

And in output of extensions I'm still getting EMFILE errors.

I dont undersand that output. In any case sudo prlimit -p "$$" --nofile=10000:10000 works without exec info the shell again, as it changes it for the current process.
Regarding VSCode, I load this in my .zshrc file, not in .profile so YMMV. I believe .profile is only loaded for login shells, which VSCode is likely not. Additionally, I believe .profile is not hit if you have .bash_profile or .bash_login FYI.

I don't have any .bash_* files
Moved the given lines onto .zshrc
Same results, I need exec ... command to see the new limit


Add model file name

@xenova here's the promised PR for #594.
I'll try to expand the solution to encoder-decoder models once I begin working with them.

In the PR, you'll see my system trimmed white spaces, and the only change is:

Thanks for the PR! Just to keep the diff small, can you remove any whitespace formatting applied by your editor? There definitely are valid changes, but it will make the diff large for the PR. 🤗

The PR is merged with 2.16.1 and is ready to go :)

@xenova Those changes are already in v3. This PR should be merge into main, or close until v3 arrives

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

I'll try to expand the solution to encoder-decoder models once I begin working with them.

I'll make the necessary changes in v3 myself. For now, this is okay (and will work for all single-file models, like encoder-only and decoder-only models).


[FEATURE REQUEST] Make a new type of issue called Branding issue

Please confirm these before moving forward

[X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template

Describe the new feature
Make a new type of issue called Branding issue.
Describe how this new feature could help users.
This new issue type can be used for branding purposes, for example, #2004

This is a one-time issue, therefore it does not make sense to create a new issue type


the location of fair-software.yml is wrong

I think the fair-software.yml file should be in .github folder.

Fixed by #39.


Formatting Error in Json not reported

Using the Embed = true if the json supplied is not formatted correctly the configurator errors out but nothing is reported in the console and an error report is not generated.

Hello Justin, I logged this issue to our tracking system. We will let you know when it will be reviewed or fixed. Thank you for your feedback.

Hello Justin, I logged this issue to our tracking system. We will let you know when it will be reviewed or fixed. Thank you for your feedback.

It's supposed to have been fixed.