CC2652RB does not start with CC2652RB_coordinator_20210120

Hello,
I've flashed the latest coordinator firmware and my zigbee2mqtt is failing to start now.  I've followed the checks and recommendations from : https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start and still didn't find a solution. I've been showing to slaesh my issue and we haven't figured out yet what is wrong.
Version
I am using zigbee2mqtt version 1.17.1 and Home Assistant core 2021.2.1

Logs:
~ $ ls -la /dev/serial/by-id/
total 0
drwxr-xr-x    2 root     root            60 Feb  6 14:30 .
drwxr-xr-x    3 root     root            60 Feb  6 14:30 ..
crw-rw----    1 root     audio     188,   0 Feb  6 14:30 usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_42_0D-if00-port0

I have tried to connect it directly to my pi3 with hass.io and via usb hub (mains powered), below are the logs of the usb hub:
[ 3385.662763] usb 1-1.5.2: new full-speed USB device number 12 using dwc_otg
[ 3385.800743] usb 1-1.5.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 3385.800756] usb 1-1.5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3385.800764] usb 1-1.5.2: Product: slae.sh cc2652rb stick - slaesh's iot stuff
[ 3385.800771] usb 1-1.5.2: Manufacturer: Silicon Labs
[ 3385.800778] usb 1-1.5.2: SerialNumber: 00_12_4B_00_21_CC_42_0D
[ 3385.803836] cp210x 1-1.5.2:1.0: cp210x converter detected
[ 3385.807527] usb 1-1.5.2: cp210x converter now attached to ttyUSB0

Below you can find my configuration for zigbee2mqtt:
data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: XXXXXXXXXXX
  password: XXXXXXXXX
serial:
  port: /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_42_0D-if00-port0
advanced:
  log_level: info
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

Error Logs
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
./run.sh: line 17: [Info] Configuration backup found in /share/zigbee2mqtt/.configuration.yaml.bk. Skipping config backup.: No such file or directory
[Info] Socat is DISABLED and not started
2021-02-06T15:37:55: PM2 log: Launching in no daemon mode
2021-02-06T15:37:55: PM2 log: App [npm:0] starting in -fork mode-
2021-02-06T15:37:56: PM2 log: App [npm:0] online
><EMAIL_ADDRESS>start /zigbee2mqtt-1.17.1
> node index.js
Zigbee2MQTT:info  2021-02-06 15:38:05: Logging to console and directory: '/share/zigbee2mqtt/log/2021-02-06.15-38-01' filename: log.txt
Zigbee2MQTT:info  2021-02-06 15:38:05: Starting Zigbee2MQTT version 1.17.1 (commit #1.17.1)
Zigbee2MQTT:info  2021-02-06 15:38:05: Starting zigbee-herdsman (0.13.59)
Zigbee2MQTT:error 2021-02-06 15:38:28: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2021-02-06 15:38:28: Failed to start zigbee
Zigbee2MQTT:error 2021-02-06 15:38:28: Exiting...
Zigbee2MQTT:error 2021-02-06 15:38:28: Error: SRSP - SYS - osalNvRead after 6000ms
    at Timeout._onTimeout (/zigbee2mqtt-1.17.1/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1

Sorry for not giving more information but I really don't know what else to share or do.

i had the same problem - unplug the cc2652 -> remove the antenna and plug the cc2652 without antenna in the usb port.
then it was starting! after that you can gave the antenna on the stick.
i dont know why, but here it works.

I also i had the same problem of cc2652p(E72).

Guys, is it save to flash slaesh CC2652 with CC2652RB_coordinator_20210120?
Want to pair/bind a new device and it doesn't work. Some recommend to reflash the CC2652 but based on above info I'm a bit sceptic ;-)

Flash done, it work well for me with ZigPy

I spend many hours to find out how to upgrade the firmware but I have a basic education in these things. Can someone please help me? I really have no idea how and where to start... Apologies if this is not the right place to ask support but I don't know where else.


Some special characters in metadata are truncated

Describe the bug
Metadata is incorrectly read from the MHA file: some characters are removed.
To Reproduce
Steps to reproduce the behavior:

Operating system, version, and architecture

OS: Fedora
Architecture: x86

Programming language: Python 3.12
Version of SimpleITK: 2.3.1
How was SimpleITK installed? pip
A minimal working example which causes the error.

rom pathlib import Path

import SimpleITK as sitk
import numpy as np

path = Path("/tmp/test.mha")

img = sitk.GetImageFromArray(np.zeros((2,2,2)))
img.SetMetaData("test1", "des caractères spéciaux")
img.SetMetaData("test2", "des caractères spéciö")
sitk.WriteImage(img, str(path))

img2 = sitk.ReadImage(str(path))
print(img2.GetMetaData("test1"))  # output: "des caractères spéciaux"
print(img2.GetMetaData("test2"))  # output: "des caractères spéci"

for line in path.open("r"):
    if line.startswith("test"):
        print(line)

# output:
# test1 = des caractères spéciaux
# test2 = des caractères spéciö
# which shows that the content of the MHA is correctly written, but not correctly read

Expected behavior
img2.GetMetaData("test2") should return "des caractères spéciö" instead of "des caractères spéci"
I suspect some unicode black magic is at work here.

Created test to reproduce the issue here:  #2083
It appears it is likely an issue with ITK or the MetaImage library.

The strings are UNICODE. MetaIO does not handle unicode, nor does it sanitize the input.


fatal error: Python.h: No such file or directory

when i run
make build
shows
mining/utils/_pandas.c:4:20: fatal error: Python.h: No such file or directory
 #include "Python.h"
                    ^
compilation terminated.
error: command 'gcc' failed with exit status 1
make: *** [environment] Error 1

what  is meaning?

Have you installed python-dev? What OS?

@avelino CentOS 7, Ah, I did not  install the software, thank you for your help!


[Eco news] Status 403 instead of 200 when try to get information about comment by id.

Environment: OS: Windows 10 Pro 64-bit, Chrome Version 131.0.6778.71
Reproducible: always
Build found: commit be310e97bf1078850130b5d08f1e7d9927466f2a
Preconditions

You should be authorized as a User on https://www.greencity.cx.ua/.

Steps to reproduce

Do endpoint: https://greencity.greencity.cx.ua/eco-news/comments/8180

Actual result
The system returns status 403 and doesn't give information about comment.
{
"timestamp": "2024-11-22T15:29:09.985+00:00",
"status": 403,
"error": "Forbidden",
"path": "/eco-news/comments/8180"
}
Expected result
The system returns status 200 and gives information about comment.
Postconditions
_
User story and test case links
User story #1723

Fixed with:
https://github.com/ita-social-projects/GreenCity/pull/7813


Review NOTICE file for incubator-openwhisk-runtime-nodejs

File link: NOTICE
Merged PRs:

PR Update NOTICE file #34

Close in favor of tracking with LICENSE issues here: https://github.com/apache/incubator-openwhisk-release/issues/99


Added joint overlay

Joint overlay added with "J"

Added Wireframe rendering with "W"

COM:

INERTIA:

Looks good, thanks for the PR!

Assuming, mjVIS_CONTACTFORCE was removed inadvertently, I'll add that line again manually.

mjVIS_CONTACTFORCE was written twice, so I reduced it

mjVIS_CONTACTFORCE was written twice, so I reduced it

The first line was for mjVIS_CONTACTPOINT followed by the line for mjVIS_CONTACTFORCE. Their purpose is different.

I wanted to add convex hull as well, but didn't really know how to work with the documentation in C.

Let me see if I can get it working.


git not respecting automation profile

Issue Type: Bug
There are tools to isolate development environments, such as toolbx or nix-shell.
VSCode is supposed to let us configure that with the terminal.integrated.automationProfile.linux setting.
In my case, I use pre-commit with some system or script hooks, as it is easier to just track the dependency versions in the outer tools (toolbx, nix-shell).
When issuing a commit from VSCode UI, it tries to run pre-commit but fails to find it because the underlying git command is ignoring the automation profile.
I tried setting git.path setting, but VSCode seems to ignore it also.
AFAICS, git should leverage the automation profile, so everything integrates properly.
VS Code version: Code 1.63.0 (7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e, 2021-12-07T05:16:45.441Z)
OS version: Linux x64 5.15.10-200.fc35.x86_64
Restricted Mode: Yes

System Info

Item
Value

CPUs
AMD Ryzen 7 4800H with Radeon Graphics (16 x 2900)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 1, 1

Memory (System)
15.10GB (0.21GB free)

Process Argv
--extensions-dir=/var/home/yajo/.var/app/com.visualstudio.code/data/vscode/extensions /app/share/vscode/flatpak-warning.txt

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome-xorg

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome-xorg

XDG_SESSION_TYPE
x11

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythontb:30283811
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vscop804:30404766
vscop453:30404998
vsrem710:30416614
vscexrecpromp3c:30407761

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


New project system & Cargo based build system

The Good:

The build system has been rewritten to be based on Cargo (requires a Cargo.toml and calls cargo build internally).
You can now directly open Cargo.toml files and the solution explorer will show all the files in the respective directory (except for some filtered things, such as the target folder). VS will still create a .rsproj file, but it only contains some user settings.
Project System is based on CPS and mirrors the file system. No need for fragile module parsing to find included source files. CPS has many advantages over the old project system: Most of the code is shipped and updated with VS; it is "designed from the ground up to be performant, scalable, and responsive"; documentation is a bit lacking, but going to improve, since CPS is used by the C# and VB project system in VS "15". The project Microsoft.VisualStudio.ProjectSystem.FileSystemMirroring together with its dependency Microsoft.Common.Core has been imported from RTVS.
This fixes #223, #232, #195, #119, #118, #113, #214 and #215

The Bad:

Support for VS2013 is dropped, because the new project system doesn't support it
Many old tests have been removed, and I have not yet written new tests (but integration tests were disabled on CI anyway and should probably be redesigned to work on AppVeyor)
Error markers (squiggly lines) are currently not shown. I haven't been able to figure out why.
The parsing of compiler messages is based on https://github.com/rust-lang/cargo/pull/3000 and requires a recent nightly, which will hit stable in December (but this is the only way that cargo build output which includes dependencies can be reliably captured and parsed)
.rsproj projects created with previous versions of VisualRust are completely incompatible with this new version

The Rest:

Updated to require .NET 4.6 (allows us to use C# 6 features and was necessary because RTVS uses it)
Updated most projects to use project.json for NuGet packages (easier to maintain)

This is a great change for the project and outweighs the loss of VS2013 support.
Great job to those involved.

@vosen: It would be nice if you could comment what you think about this.
Otherwise, if no one has any objections, I'm going to merge in a few days.

Is visit_toml.dll and all Manifest stuff from Cargo project still needed?

No, it's currently unused. What's implemented in the PR is only reading the manifest using cargo manifest. As soon as we want to edit the manifest from the UI, we will need some way to parse and edit the TOML file directly, without reformatting everything (i.e. preserving comments and whitespace, etc). That's what vist_toml.dll is built for, but it's unfinished and not really documented. We need to decide what will be done there, but it's out of scope for this PR.

The idea of moving us to CPS is sound and is something that I wanted to do.
The problem was always that would have required a lot of effort to port: redoing stuff with MEF and .xaml rules is time consuming and even things like .pkgdef are extremely fiddly.
This commit pretty forces my hand in this regard.
While I'm not 100% enthusiast of removing tests and I see that some thing are broken (.rsproj loading, probably due to aforementioned pkgdef, tested on a clean machine) I'm Ok with the commit. Someone had to do it, sooner or later.


resolver API should return not found for unmatched prefixes

info or resolve for a non-existent or longer than existing naan is returning the default info response. Should adjust to return 404 Not Found.
Example (actual naan is 59512):
curl https://arks-stg.cdlib.org/ark:595122?info
...
< HTTP/2 200
...
<
{
  "pid": "ark:595122",
  "scheme": "ark",
  "content": "595122",
  "prefix": "595122",
  "value": null,
  "suffix": "95122",
  "target": "/.info/ark:595122",
  "canonical": "ark:/595122/",
  "status_code": 302,
  "properties": {
    "what": "ark",
    "name": "Archival Resource Key"
  },
  "definition": {
    "uniq": "ark:",
    "scheme": "ark",
    "prefix": "",
    "value": "",
    "target": "/.info/{pid}",
    "canonical": "ark:/{prefix}/{value}",
    "synonym_for": null,
    "values": []
  }
}

Resolved.


nvALT autolinking

Not sure if it was something I did or not, but I was just trying away and my autolinking stopped working. It used to try to finish the link title when i would start a link. When a link was started with [[th it would automatically try to finish the link and suggest previously created links like [[this]] or [[that]] or [[the]]. Something I did?

Same issue here. I find it occasionally works, then stops working again. I find that the editor is often slow to update when switching notes as well. I suspect that nvAlt is finally beginning to show its age...


Mutability in subscribers and related objects

Moving from #82:
All of the mentioned objects are mutable and I wonder if they really should be. Once a subscriber is passed to the event dispatcher it really shouldn't be changed. And I can hardly think of a use case where there is a mutator layer between the subscriber and the dispatcher. This is all true for the related objects (BasicAuth etc.)
Speaking of related objects: are they really necessary? I mean, I can't think of a use case, do you have any? For example in case of a simple basic auth it is rather an overkill, since we are talking about two simple data and a mutator logic which is probably the same in every possible implementation.

The mutability in the event listeners/subscribers are not needed. So, I agree for removing them. For the related objects, I have designed it this way in order to allows to use them in an other event dispatcher library without having to duplicate the whole logic. So, for this part, I'm for keeping them.

OK. May I open a separate PR from #85, or I can send the two in one (as event dispatching improvement)?

Less PR to review, better it is :) And as you pointed out, everything is related to event dispatching, so :+1: for putting everything in a single PR.

Great, thanks. Will send it in a few days.


[stable/redis] Show correct secret name

Signed-off-by: Alejandro Moreno<EMAIL_ADDRESS>What this PR does / why we need it:
This PR shows the correct secret when the user has specified its own secret using the existingSecret parameter.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/lgtm


General Issue: Action to synch main/pre-release branch to patch branch

Background Information
To keep the patch branch up to date with the main/pre-release branch we should use a GH action to automate this step.
The patch branch will hopefully be used infrequently, but we want it to be ready  if needed in a pinch.  Having to trouble shoot and update the patch branch might get tedious as it could be severely outdated.  To remedy this an action should be created that will automatically create a PR for merging main into patch with reviewers assigned when main is updated.
A possible candidate is here https://github.com/marketplace/actions/sync-branches
Definition of Done
Action created that automatically merges main into patch whenever main is updated.

Hi @bms63, could you verify the logic behind https://github.com/pharmaverse/admiral/pull/1801 if we still need this action?

Action created that automatically merges main into patch whenever main is updated.

I think we only need one PR to be created for main > patch when we make do a proper release.
This way we can be ready for a hotfix and not interrupt development work in devel if the hotfix/pathch is needed.
We are removing pre-release branch as it is overly complicated, but we need to update CI workflow for building website to only to that when we do a release.

oh but i guess if we do a hotfix and merge to main then we also need a auto-PR for main with hotfix/patch to devel branch

I think this can get closed out as we are going to move to the more modern approach.
@cicdguy Still good for July 25th demo at IDR meeting to brings us from 2008 to 2023?
@pharmaverse/admiral just for everyone's awareness - we are most likely removing the devel and patch branches from our admiral lives. :( they served us well!  This brings us more in-line with how everyone else does thing in their development processes.


Set up redux

Description
Setup redux and redux-thunk for state management
Checklist

[x] I have performed a self-review of my own code
[x] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works .
[ ] New and existing unit tests pass locally with my changes

Good job John!
Is there a way to check the env for production or development before declaring
window.REDUX_DEVTOOLS_EXTENSION &&
window.REDUX_DEVTOOLS_EXTENSION()
because in production without these dev tools the app will not start
I stole this from melqui's github - so it should work
window.REDUX_DEVTOOLS_EXTENSION ? window.REDUX_DEVTOOLS_EXTENSION() : (a) => a

I think logically they are just the same, personally felt the ternary operator was a bit longer so decided to make use of &&'s short circuiting feature. Both versions just check whether window.redux_dev_tools is true/false


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:06:29 on 2023.04.28
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 0, errors out: 0
Original problem ID: 20129
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=20129

Problem has been resolved in 3m 0s at 10:09:29 on 2023.04.28
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 20129


Resync workflow paths

GitHub actions create-catalogue script failed when trying to make updates #205 which puts almost all tools and workflows out of sync.
Use the following script to update all tools and workflows on ICA to be 'in-sync' again with the following script.

Script is as follows:
tools_and_workflows_to_update_by_project_obj="$( \
  yq \
    --output-format=json config/project.yaml | \
  jq \
    --compact-output --raw-output \
    '
      .projects |
      # Remove the production projects from the list
      # Updated by GH actions only and wont be out of sync anyway
      map(
        select(
          .production | not
        )
      ) |
      map(
        # We collect the project name and a list of all tool paths
        {
          "project_name": .project_name,
          "tool_paths": (
            .tools |
            map(
              .name as $name |
              .versions |
              map(
                "\($name)/\(.path)"
              )
            ) |
            flatten |
            unique
          ),
          "workflow_paths": (
            .workflows |
            map(
              .name as $name |
              .versions |
              map(
                "\($name)/\(.path)"
              )
            ) |
            flatten |
            unique
          )
        }
      )
    '
)"

for project_obj_b64_encoded in $(jq -r 'map(@base64) | .[]' <<< "${tools_and_workflows_to_update_by_project_obj}"); do
  project_obj="$(base64 -d <<< "${project_obj_b64_encoded}")";
  project_name="$(jq --raw-output '.project_name' <<< "${project_obj}")";
  for tool_path in $(jq -r '.tool_paths | .[]' <<< "${project_obj}"); do
    cwl-ica tool-sync \
      --projects "$project_name" \
      --tool-path "$tool_path" \
      --force;
  done;
  for workflow_path in $(jq -r '.workflow_paths | .[]' <<< "${project_obj}"); do
    cwl-ica workflow-sync \
        --projects "$project_name" \
        --workflow-path "$workflow_path" \
        --force;
  done;
done

Will add to wiki as a useful resource


Eflow machine running inside Azure VM can't ping <IP_ADDRESS> with static ip allocation

Setup

Azure VM running Windows Server 2019 Datacenter (Build 19044.2364).

Windows Firewall disabled

Virtual Switch of type Internal created using the official documentation
https://learn.microsoft.com/en-us/azure/iot-edge/how-to-create-virtual-switch?view=iotedge-1.4
without following the DHCP section because I needed a static ip configuration.

Hyper V install, AzureIoTEdge.msi install and eflow deployment and provisioning using
https://learn.microsoft.com/en-us/azure/iot-edge/quickstart?view=iotedge-1.4
Deploy command:
Deploy-Eflow -vSwitchType "Internal" -vSwitchName "InternalSw" -ip4Address "<IP_ADDRESS>" -ip4GatewayAddress "<IP_ADDRESS>" -ip4PrefixLength "24"

Resulted configuration
PS C:\Users\azureadmin> Get-VMSwitch
Name       SwitchType NetAdapterInterfaceDescription
----       ---------- ------------------------------
InternalSw Internal
PS C:\Users\azureadmin> Get-NetAdapter -Name "vEthernet (InternalSw)"
Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
vEthernet (InternalSw)    Hyper-V Virtual Ethernet Adapter              8 Up           00-15-5D-00-04-00        10 Gbps
PS C:\Users\azureadmin> Get-NetIPAddress -AddressFamily IPv4  -InterfaceIndex 8
IPAddress         : <IP_ADDRESS>
InterfaceIndex    : 8
InterfaceAlias    : vEthernet (InternalSw)
AddressFamily     : IPv4
Type              : Unicast
PrefixLength      : 24
PrefixOrigin      : Manual
SuffixOrigin      : Manual
AddressState      : Preferred
ValidLifetime     : Infinite ([TimeSpan]::MaxValue)
PreferredLifetime : Infinite ([TimeSpan]::MaxValue)
SkipAsSource      : False
PolicyStore       : ActiveStore
PS C:\Users\azureadmin> Get-NetNat
Name                             : InternalSw
ExternalIPInterfaceAddressPrefix :
InternalIPInterfaceAddressPrefix : <IP_ADDRESS>/24
IcmpQueryTimeout                 : 30
TcpEstablishedConnectionTimeout  : 1800
TcpTransientConnectionTimeout    : 120
TcpFilteringBehavior             : AddressDependentFiltering
UdpFilteringBehavior             : AddressDependentFiltering
UdpIdleSessionTimeout            : 120
UdpInboundRefresh                : False
Store                            : Local
Active                           : True
iotedge-user@Windows-EFLOW [ ~ ]$ ifconfig eth0
ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
    inet6 fe80::215:5dff:fe00:404  prefixlen 64  scopeid 0x20<link>
    ether 00:15:5d:00:04:04  txqueuelen 1000  (Ethernet)
    RX packets 34  bytes 13392 (13.0 KiB)
    RX errors 0  dropped 0  overruns 0  frame 0
    TX packets 26  bytes 1768 (1.7 KiB)
    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Expected behaviour
Eflow vm should not give any errors and should connect successfully to internet.
Current behaviour
iotedge-user@Windows-EFLOW [ ~ ]$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8187ms
iotedge-user@Windows-EFLOW [ ~ ]$ sudo iotedge list
NAME             STATUS           DESCRIPTION      Config
iotedge-user@Windows-EFLOW [ ~ ]$ sudo iotedge check
Configuration checks (aziot-identity-service)
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
× aziot-identity-service package is up-to-date - Error
could not query https://aka.ms/latest-aziot-identity-service for latest available version
‼ host time is close to reference time - Warning
Could not query NTP server
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
√ read all preloaded certificates from the Certificates Service - OK
√ read all preloaded key pairs from the Keys Service - OK
√ check all EST server URLs utilize HTTPS - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK
Connectivity checks (aziot-identity-service)
× host can connect to and perform TLS handshake with iothub AMQP port - Error
Could not connect to iot-hub-leafpoint-poc.azure-devices.net : could not complete TLS handshake
× host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - Error
Could not connect to iot-hub-leafpoint-poc.azure-devices.net : could not complete TLS handshake
× host can connect to and perform TLS handshake with iothub MQTT port - Error
Could not connect to iot-hub-leafpoint-poc.azure-devices.net : could not complete TLS handshake
Configuration checks
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
× configuration has correct URIs for daemon mgmt endpoint - Error
Unable to find image 'mcr.microsoft.com/azureiotedge-diagnostics:1.4.2' locally
docker: Error response from daemon: Get "https://mcr.microsoft.com/v2/": dial tcp: lookup mcr.microsoft.com: Temporary failure in name resolution.
See 'docker run --help'.
× aziot-edge package is up-to-date - Error
Error while fetching latest versions of edge components: could not send HTTP request
× container time is close to host time - Error
Could not query local time inside container
‼ DNS server - Warning
Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: logs policy - Warning
Container engine is not configured to rotate module logs which may cause it run out of disk space.
Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
You can ignore this warning if you are setting log policy per module in the Edge deployment.
× production readiness: Edge Agent's storage directory is persisted on the host filesystem - Error
Could not check current state of edgeAgent container
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
Could not check current state of edgeHub container
× Agent image is valid and can be pulled from upstream - Error
Failed to get edge Agent image
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK
Connectivity checks
× container on the default network can connect to upstream AMQP port - Error
Container on the default network could not connect to iot-hub-leafpoint-poc.azure-devices.net:5671
× container on the default network can connect to upstream HTTPS / WebSockets port - Error
Container on the default network could not connect to iot-hub-leafpoint-poc.azure-devices.net:443
× container on the IoT Edge module network can connect to upstream AMQP port - Error
Container on the azure-iot-edge network could not connect to iot-hub-leafpoint-poc.azure-devices.net:5671
× container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - Error
Container on the azure-iot-edge network could not connect to iot-hub-leafpoint-poc.azure-devices.net:443
18 check(s) succeeded.
3 check(s) raised warnings. Re-run with --verbose for more details.
14 check(s) raised errors. Re-run with --verbose for more details.
2 check(s) were skipped due to errors from other checks. Re-run with --verbose for more details.

Hi @hututuiandrei,
Thanks for sharing your detailed information. We are seeing some issues with Server 2019 and an Internal virtual switch with 169.X IP address family. Could you please try changing the address family to 172.20.X.Y instead?
To further clarify, when creating the internal virtual switch, generally a 169.X.Y.Z address is assigned to the switch. The next step in the guide after creating the switch is to create the “gateway” address, which is assigning the 169.X.Y.1 address to the internal virtual switch. In the EFLOW scenario, the Windows host OS internal switch interface has the “gateway” address.
So, instead of assigning the 169.X.Y.1 address, you can completely change the address.
New-NetIPAddress -IPAddress <IP_ADDRESS> -PrefixLength 24 -InterfaceIndex {interfaceIndex}
This command will assign the <IP_ADDRESS> to the virtual switch that has the {interfaceIndex}, in our case, the internal virtual switch (virtual switches can be identified by name or by index). Once executed, you can use the ipconfig parameter, and check the Int Switch interface and the configuration, you should see the new address.
Finally, change your deployment parameters, to use the new IP address family. Please let met know if that helps.
Thanks,
Francisco

Hello @fcabrera23,
Indeed changing the address family was the solution. Now iotedge check doesn't return any errors (except "production readiness") and the device is able to connect to internet and pull the edgeAgent docker image.
iotedge-user@Windows-EFLOW [ ~ ]$ sudo iotedge check
...
...
...
30 check(s) succeeded.
4 check(s) raised warnings. Re-run with --verbose for more details.
1 check(s) raised errors. Re-run with --verbose for more details.
2 check(s) were skipped due to errors from other checks. Re-run with --verbose for more details.
iotedge-user@Windows-EFLOW [ ~ ]$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=114 time=2.64 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=114 time=2.73 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=114 time=3.11 ms
iotedge-user@Windows-EFLOW [ ~ ]$ sudo iotedge list
NAME             STATUS           DESCRIPTION      Config
edgeAgent        running          Up 8 minutes     mcr.microsoft.com/azureiotedge-agent:1.4
Thank you for your help!


Redo design of title and subtitle on case page

On each case page, instead of listing the subtitle as "City, State. Date", rearrange to be like this:
Name, Age
Location
Date.

This page looks like this on dev.

Would it be possible to remove the period after the location?

Pushing that period removal to Staging.

Looks good!

This is in production


Update to ArrayInterface v4

I still need to figure out versioning for tests but I think this is all that needs to change.

ArrayInterface 4 requires Julia >= 1.6. So Julia 1.5 can be updated to 1.6, so we test on 1.6, the latest release ("1" => currently 1.7) and nightly.
But the Julia 1 and nightly failures look real.

Also:
   MethodError: no method matching eachop(::typeof(ArrayInterface._known_size), ::Tuple{}, ::Type{Tuple{}})
  Closest candidates are:
    eachop(::F, ::Tuple{I}, ::Any...) where {F, I, K} at ~/.julia/packages/Static/ARZ1c/src/tuples.jl:40
    eachop(::F, ::Tuple{I1, I2, Vararg}, ::Any...) where {F, I1, I2, K} at ~/.julia/packages/Static/ARZ1c/src/tuples.jl:37

https://github.com/JuliaSIMD/LoopVectorization.jl/runs/5186578238?check_suite_focus=true

Also:
  MethodError: no method matching eachop(::typeof(ArrayInterface._known_size), ::Tuple{}, ::Type{Tuple{}})
  Closest candidates are:
    eachop(::F, ::Tuple{I}, ::Any...) where {F, I, K} at ~/.julia/packages/Static/ARZ1c/src/tuples.jl:40
    eachop(::F, ::Tuple{I1, I2, Vararg}, ::Any...) where {F, I1, I2, K} at ~/.julia/packages/Static/ARZ1c/src/tuples.jl:37
  Stacktrace:
    [1] _maybe_known_size(#unused#::Base.HasShape{0}, #unused#::Type{CartesianIndices{0, Tuple{}}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/size.jl:112
    [2] known_size(#unused#::Type{CartesianIndices{0, Tuple{}}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/size.jl:110
    [3] _maybe_known_length(#unused#::Base.HasShape{0}, #unused#::Type{CartesianIndices{0, Tuple{}}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/ArrayInterface.jl:96
    [4] known_length(#unused#::Type{CartesianIndices{0, Tuple{}}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/ArrayInterface.jl:95
    [5] known_length(x::CartesianIndices{0, Tuple{}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/ArrayInterface.jl:89
    [6] maybe_static(f::typeof(ArrayInterface.known_length), g::typeof(length), x::CartesianIndices{0, Tuple{}})
      @ Static ~/.julia/packages/Static/ARZ1c/src/int.jl:121
    [7] static_length(x::CartesianIndices{0, Tuple{}})
      @ ArrayInterface ~/.julia/packages/ArrayInterface/mJodK/src/ArrayInterface.jl:38

https://github.com/JuliaSIMD/LoopVectorization.jl/runs/5186578238?check_suite_focus=true
Versus ArrayInterface 3:
julia> ArrayInterface.static_length(CartesianIndices(()))
1

This could of course be static(1).

Looks like we need a special case for zero dimensions? I'll look into these other issues some more

Looks like we need a special case for zero dimensions?

They don't really need to return static(1), but they come from code like
using LoopVectorization, Test
function smoothdim_kernel_tile_avx!(out, z, src::AbstractArray, kernel::AbstractVector, Rpre::CartesianIndices, axout_tile, Rpost::CartesianIndices)
    axkernel = axes(kernel, 1)
    zout = convert(eltype(out), z)
    for Ipost in Rpost
        @turbo for i in axout_tile
            for Ipre in Rpre
                tmp = zout
                # tmp = convert(eltype(out), z)    # failing to hoist this leads to an "UndefVarError: tmp not defined"
                for j in axkernel
                    tmp += oftype(z, src[Ipre, i+j, Ipost]) * kernel[j]
                end
                out[Ipre, i, Ipost] = tmp
            end
        end
    end
    out
end

# Mimic of ImageFiltering/ArrayFiltering's separable filters
σ = 3
ax = OffsetArray(-6:6, -6:6)
kernel = float(T)[exp(-i^2 / (2 * σ^2)) for i in ax]   # 1-d Gaussian kernel
kernel ./= sum(kernel)
srcax = 1+firstindex(ax):M+lastindex(ax)
Mpad = length(srcax)
src = OffsetArray(rand(T, Mpad, Mpad, Mpad, Mpad, Mpad), srcax, srcax, srcax, srcax, srcax)
dest1 = Array{float(T),5}(undef, M, M, M, M, M)
dest2 = similar(dest1)
for d = 1:ndims(src)
    Rpre = CartesianIndices(axes(dest1)[1:d-1])
    Rpost = CartesianIndices(axes(dest1)[d+1:end])
    smoothdim_kernel_tile!(dest1, float(zero(T)), src, kernel, Rpre, axes(dest1, d), Rpost) # version without `@turbo`
    smoothdim_kernel_tile_avx!(dest2, float(zero(T)), src, kernel, Rpre, axes(dest2, d), Rpost)
    @test dest1 ≈ dest2
    fill!(dest2, NaN)
    smoothdim_kernel_tile_avx_2!(dest2, float(zero(T)), src, kernel, Rpre, axes(dest2, d), Rpost)
    @test dest1 ≈ dest2
end

I.e., Rpre and Rpost both might be 0-dimensional here, and the code should be able to handle this.

The problem with zero dimensions has been fixed. It was a bug with Static.eachop. I'm still getting a single error for broadcast tests.

A little bit more on the problem with broadcasting. It's specifically with *ˡ.
If you drop the adjoint and just do @tturbo @. D2 = A *ˡ b then you still get NaNs, but @tturbo @. (b .+ x') works just fine.


[SMALLFIX]Improve the index page of the Chinese doc

Improve the index page of the Chinese document.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8525/
Test PASSed.

LGTM. Thanks for the improvement!


archlinux test container is broken: jq now requires GLIBC_2.39

Install packages required for installation (jq, curl, and/or tar)
  :: Synchronizing package databases...
   core downloading...
   extra downloading...
  resolving dependencies...
  looking for conflicting packages...

  Package (2)      New Version  Net Change  Download Size

  extra/oniguruma  6.9.9-1        0.87 MiB       0.21 MiB
  extra/jq         1.7.1-2        0.73 MiB       0.28 MiB

  Total Download Size:   0.50 MiB
  Total Installed Size:  1.60 MiB

  :: Proceed with installation? [Y/n]
  :: Retrieving packages...
   jq-1.7.1-2-x86_64 downloading...
   oniguruma-6.9.9-1-x86_64 downloading...
  checking keyring...
  checking package integrity...
  loading package files...
  checking for file conflicts...
  :: Processing package changes...
  installing oniguruma...
  installing jq...
  :: Running post-transaction hooks...
  (1/1) Arming ConditionNeedsUpdate...
jq: /usr/lib/libm.so.6: version `GLIBC_2.39' not found (required by jq)

there was a recent change upstream to jq package https://gitlab.archlinux.org/archlinux/packaging/packages/jq/-/commit/0620080827b37757a876144b701ca7bc48aebbc7
But that doesnt appear to be the problem.
And when I attempt to reproduce locally, it works.
> docker run -it alpine
Unable to find image 'alpine:latest' locally
latest: Pulling from library/alpine
d25f557d7f31: Pull complete
Digest: sha256:77726ef6b57ddf65bb551896826ec38bc3e53f75cdde31354fbffb4f25238ebd
Status: Downloaded newer image for alpine:latest
/ # apk --no-cache add jq
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.20/community/x86_64/APKINDEX.tar.gz
(1/2) Installing oniguruma (6.9.9-r0)
(2/2) Installing jq (1.7.1-r0)
Executing busybox-1.36.1-r28.trigger
OK: 9 MiB in 16 packages
/ # jq --help
jq - commandline JSON processor [version 1.7.1]
...

looking at the error, /usr/lib/libm.so.6: version GLIBC_2.39' not found (required by jq)`, it's triggered by libm.
So perhaps it's only triggered when libm is used? e.g. when actually doing some json filter/select?

jq . cargo-cyclonedx.json (and similar selecting) was successful.  Will look into filtering..

Ignore above local success - I was testing on alpine.
with https://github.com/jayvdb/install-action/actions/runs/9433057502/job/25983566199
I've debugged the script to identify this as the jq that is failing
++ call_jq -r .rust_crate /__w/install-action/install-action/./manifests/biome.json
++ [[ -n '' ]]
++ jq -r .rust_crate /__w/install-action/install-action/./manifests/biome.json
jq: /usr/lib/libm.so.6: version `GLIBC_2.39' not found (required by jq)
+ rust_crate=

and I  can reproduce locally
> docker run -it archlinux
Unable to find image 'archlinux:latest' locally
latest: Pulling from library/archlinux
d9884827b07b: Pull complete
8bc4fe693d3a: Pull complete
Digest: sha256:e0cdf8208d276f77eaba78e1ef0e94f7a70c15090cfc09299be5521ceb4a0705
Status: Downloaded newer image for archlinux:latest
..
[root@5dfc63cf6ee5 /]# pacman -Sy --noconfirm  jq
:: Synchronizing package databases...
 core downloading...
 extra downloading...
resolving dependencies...
looking for conflicting packages...

Package (2)      New Version  Net Change  Download Size

extra/oniguruma  6.9.9-1        0.87 MiB       0.21 MiB
extra/jq         1.7.1-2        0.73 MiB       0.28 MiB

Total Download Size:   0.50 MiB
Total Installed Size:  1.60 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
 jq-1.7.1-2-x86_64 downloading...
 oniguruma-6.9.9-1-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
installing oniguruma...
installing jq...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[root@5dfc63cf6ee5 /]# jq --version
jq: /usr/lib/libm.so.6: version `GLIBC_2.39' not found (required by jq)


⚠ Auth has degraded performance

In ea2b8d1, Auth (https://auth.k2lin.com) experienced degraded performance:

HTTP code: 200
Response time: 16267 ms

Resolved: Auth performance has improved in edc35dc.


Segmentation fault when training on my own data.

Hi,
Thank you for your wonderful work. But after I simply change the path to my own dataset (all pictures with the size of 1280x720), I meet the segmentation fault. :( Can you please help me locate the bug?

It could be related to the corner pooling compilation. Can you try this? Also, can you provide the full screenshot that includes the full configuration details? That may help.

Thank you. Updating gcc from 4.8 to 4.9.4 solved this problem.

hello @zxDeepDiver , i also meet the bug:
training start...
0%|                                                | 0/500000 [00:00<?, ?it/s]Segmentation fault
you mean that updataing the gcc to 4.94 can solve this bug?


GOG descriptions not being downloaded in English

It would be great to be able to choose in wich language I want to have the downloaded details. I'm a spaniard, but live in Switzerland.
My option would be to have the details in either spanish or english. BUT for Steam and Origin games the details are downloaded only in english, from GOG everything is in german... it's quite a mess.
It's a suggestion that sooner or later would come.
I'm totally in love with Playnite and only use it from yesterday. THANK YOU!!!

Done in the latest update.


--stats displays a negative size if more than 2GB searched

Example in Windows, but the problem will be the same in Unix when int is 32-bits:
F:\DDA\Samples\Archived>ag --stats "]]>"
0 matches
0 files contained matches
1429 files searched
-1970704972 bytes searched
6.796805 seconds

F:\DDA\Samples\Archived>dirsize
2,324,262,324

Sorry for answering this so late...
This is fine for 64-bit builds, but not of 32-bit builds.
I hit the problem while searching a 6GB file tree using a WIN32 build for Windows.
Is there any issue with the simple fix using long long that I proposed?


Please add metadata-cascade-policies:create

Is your feature request related to a problem? Please describe.
We need to create metadata cascade policy for many folders.
We want to use CLI but it looks like it doesn’t have metadata-cascade-policies:create command.
I guess metadata-cascade-policies:force-apply command doesn’t work for us as it requires metadata id that has already cascade enabled.
Describe the solution you'd like
Please simply add  box metadata-cascade-policies:create command which calls the following API.
https://developer.box.com/reference/post-metadata-cascade-policies/

Hi @kobay
I think you can use box metadata-templates:cascade to create a new cascade policy for a folder.


Develop

I rewrote the get-auth-map function to use Google REST API (instead of Java interop) and added a new type for AuthMap, which is returned by that function now. This also converts the json returned by google with keys like "access_token" to a proper clojure map with the key :access-token, which is what is expected in GoogleCtx. I'm using HTTPkit to send the requests and clojure.data.json to parse the json response. HTTPkit can easily be replaced by whatever other library you'd prefer to send HTTP requests, but it works pretty well.
Furthermore, I added a function to refresh an existing google token, which also returns an AuthMap containing the new token.
Users can also specify their own redirect-url, instead of always using copy paste, this enables you to have google send the auth-code directly to your web app. Consequently, you may also now specify your access-type as "online" or "offline". Both values are read from the google-context, defaulting to the previous functionality if none are given.
PS: Sorry for the messy commits, I worked on the master branch and then merged to develop. If you want you can also merge the master branch directly.

Hey, this is an ridiculously late response but I want to thank you for putting together this very reasonable PR. We completely dropped the ball on maintaining this library; we're sorry for that and understand how annoying it is to get radio silence after putting work into a PR. We're currently undergoing a review of our open source policies w/ legal and, for what it's worth, should be able to respond to PRs on this project soon


Fixing parameter at SqlBuilder.

Hi,
I made some corrections into you SqlBuilder.
The Alias was inverted.
Thank you.

Thank you. I'm not proficient in GitHub and need to learn few things. Please bare with me. Your commit indicates that you changed the target version of .net. I'd prefer to avoid this change. Is that possible?

Are you confident in your change? It doesn't seem to be right, just by looking at your commit. I'm not setup for SqlServer and it would take me some time to validate it.
But I'd expect that the alias name should be added to column name, not value. Did you mean to include it in the square brackets, like this?
[j0.{0}] = {1}
instead of my version being
j0.[{0}] = {1}

The .NET version doesn't need to be changed, it was changed by the Visual Studio Restore Package Feature. But there's no need to change it.
I received the ambiguous column error when I tried to perform an update statement with a subtraction operation, with this code:
db.Users(m => m.UserId == .id).Update(u => new User { Age = u.Age- 5 });
In SQL the generated code is like this:
exec sp_executesql N'UPDATE [dbo].[Users] SET
[Age] = [Age] - 5
FROM [dbo].[Users] AS j0 INNER JOIN (
SELECT
    [Extent1].[Age] AS [Age],
    [Extent1].[UserId] AS [UserId]
    FROM [dbo].[Users] AS [Extent1]
    WHERE ([Extent1].[UserId] = @p__linq__0)
) AS j1 ON (j0.[UserId] = j1.[UserId])',N'@p__linq__0 uniqueidentifier',@p__linq__0='04D5AA08-1A41-4935-8E87-8F2296481D69'

To eliminate ambiguous column, just put the alias, as in the code like this:
exec sp_executesql N'UPDATE [dbo].[Users] SET
[Age] = j0.[Age] - 5
FROM [dbo].[Users] AS j0 INNER JOIN (
SELECT
    [Extent1].[Age] AS [Age],
    [Extent1].[UserId] AS [UserId]
    FROM [dbo].[Users] AS [Extent1]
    WHERE ([Extent1].[UserId] = @p__linq__0)
) AS j1 ON (j0.[UserId] = j1.[UserId])',N'@p__linq__0 uniqueidentifier',@p__linq__0='04D5AA08-1A41-4935-8E87-8F2296481D69'


Deployment script modules

Description
closes #60
PR is draft, whilst i complete the remainder of the steps in the contribution guide
Adding a new module

[x] A proposal has been submitted and approved.
[x] I have included "Closes #{module_proposal_issue_number}" in the PR description.
[x] I have run brm validate locally to verify the module files.
[x] I have run deployment tests locally to ensure the module is deployable.
[ ] README.md is complete and ready for review

New commits to my branch don't seem to be flowing through to the PR.


Can't open locally with Safari Version 11.0.3 (13604.5.6) on MacOS

When I try to open it directly in the local file-system in Safari on MacOS I just get a white screen (works fine in safari though):
Safari Version 11.0.3 (13604.5.6)
these lines are in the the error log:
[Error] Not allowed to load local resource: file://fonts.googleapis.com/css?family=Lato
[Error] SecurityError (DOM Exception 18): The operation is insecure.
	get (artemis.min.js:29:366)
	(anonyme Funktion) (monogatari.js:157)

first line looks related to @import url(//fonts.googleapis.com/css?family=Lato); in main.css.  Is there a missing https: at the start?
the second one seems to be a bug in Artemis - something to do with localstorage sandboxing looks like.

Ah, I'm really sorry! Somehow I missed this issue!
The @import url(//fonts.googleapis.com/css?family=Lato); does not have an http: or https: at the beginning because it will adapt to whatever protocol the page is running, it's producing an error because if you run it locally, it will use file: as the protocol, as if requesting a local file and of course the file will not be fount. That error should not be a problem though.
It's probably not working on Safari because Safari blocks access to local storage if the page is not trusted (if it's being served locally and without a server, it probably isn't trusted) I think there is an option somewhere in Safari's settings to disable that protection but I would actually advice against that and prefer using another browser for development. Since local storage can't be used, some operations fail, causing the blank screen. I'll be sure to address that in a better way so it doesn't simply turn out unusable :)


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 409

Questions ?
Please refer to the Backport tool documentation


SwaggerUI (not found in project, manifest or registry)

(@v1.7) pkg> add SwaggerUI
ERROR: The following package names could not be resolved: * SwaggerUI (not found in project, manifest or registry)
I'm using Julia v1.7.3 and Genie v4.18.2

mb, it should be add SwagUI, I'll update the readme file, thanks for pointing this out


[Bug] Nodes with metadata not found for a short time after persisting in Pinecone

Is this a new bug in the Pinecone Python client?

[X] I believe this is a new bug in the Pinecone Python Client
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hello,
I'm having an issue with fetching vectors from an index with metadata filtering. Here's the flow:

I'm parsing some nodes and labelling them with metadata
I'm storing the nodes in Pinecone
Immediately after persisting the nodes I query the index for the nodes, however the search turns out empty

I know that the nodes are persisted correctly, but they're not available for retrieval for some period of time after persisting. I've fallen back to using sleep(30) after calling persist to around this problem. 10 seconds seems to be not be enough, but 30 gets the job done.
It seems plausible for the Plausible backend to take a while to build proper indexes for new nodes, but I'd need to reliably be able to tell when I can run my query. If there was some kind of API that can allow me to check whether they're indexed or not that would be great
Expected Behavior
I can reliably fetch nodes after persisting them in Pinecone
Steps To Reproduce
Happy to submit a fully reproducible example if needed, just want to confirm that it's an actual bug first
Relevant log output
No response
Environment
- OS: MacOS
- Python: 3.11.6
- pinecone: 2.2.4

Additional Context
No response

I've managed to work around this problem by getting rid of Pinecone, so as far I'm concerned, the problem is "solved"

Same issue here, if you query immediately after upsert you will get empty result.


[SPARK-42357][CORE] Log exitCode when SparkContext.stop starts

What changes were proposed in this pull request?
This PR aims to log exitCode when SparkContext.stop starts as a clear boundary to ignore the meaningless log messages from user jobs.
Why are the changes needed?
This PR adds the following log.
23/02/06 02:12:55 INFO SparkContext: SparkContext is stopping with exitCode 0.

In the simplest case, it stops like the following.
$ bin/spark-submit examples/src/main/python/pi.py
...
Pi is roughly 3.147080
23/02/06 02:12:55 INFO SparkContext: SparkContext is stopping with exitCode 0.
23/02/06 02:12:55 INFO AbstractConnector: Stopped<EMAIL_ADDRESS>(http/1.1)}{localhost:4040}
23/02/06 02:12:55 INFO SparkUI: Stopped Spark web UI at http://localhost:4040
23/02/06 02:12:55 INFO MapOutputTrackerMasterEndpoint: MapOutputTrackerMasterEndpoint stopped!
23/02/06 02:12:55 INFO MemoryStore: MemoryStore cleared
23/02/06 02:12:55 INFO BlockManager: BlockManager stopped
23/02/06 02:12:55 INFO BlockManagerMaster: BlockManagerMaster stopped
23/02/06 02:12:55 INFO OutputCommitCoordinator$OutputCommitCoordinatorEndpoint: OutputCommitCoordinator stopped!
23/02/06 02:12:55 INFO SparkContext: Successfully stopped SparkContext
23/02/06 02:12:56 INFO ShutdownHookManager: Shutdown hook called

However, in the complex case, there are many many logs after invoking SparkContet.stop(0). Sometimes, this makes users confused. New log will show a clear boundary to ignore the meaningless messages.
23/02/06 02:59:27 INFO TaskSetManager: Starting task 283.0 in stage 34.0 (TID 426) (<IP_ADDRESS>, executor 5, partition 283, PROCESS_LOCAL, 8001 bytes)
...
23/02/06 02:59:27 INFO BlockManagerInfo: Removed broadcast_35_piece0 on <IP_ADDRESS>:41741 in memory (size: 5.7 KiB, free: 50.8 GiB)
...
23/02/06 02:59:27 INFO SparkUI: Stopped Spark web UI at http://r6i-16xlarge-3402-0203-apple-3-bf3f7e8624a90a37-driver-svc.default.svc:4040
...
23/02/06 02:59:27 INFO DAGScheduler: ShuffleMapStage 34 (q24a) failed in 0.103 s due to Stage cancelled because SparkContext was shut down
...
23/02/06 02:59:27 INFO KubernetesClusterSchedulerBackend: Shutting down all executors
...
23/02/06 02:59:27 INFO KubernetesClusterSchedulerBackend$KubernetesDriverEndpoint: Asking each executor to shut down
...
23/02/06 02:59:27 ERROR TransportRequestHandler: Error while invoking RpcHandler#receive() for one-way message.
org.apache.spark.SparkException: Could not find CoarseGrainedScheduler.

Does this PR introduce any user-facing change?
No, this is a log-only change.
How was this patch tested?
Manually.

Could you review this PR, @viirya ?

Thank you! Merged to master/3.4.

late LGTM


Linting and Formatting Enforcement

Summary: Pre-commit hooks for pylint and black may not be running consistently across all environments.
Details: Some team members reported that their pre-commit hooks were not properly enforcing linting or formatting due to differences in local Git configurations.
Affected Areas: Git pre-commit hook configuration (.pre-commit-config.yaml).
Dependencies: Pre-commit tool.

Proposed Solution: Ensure all team members have pre-commit installed and configured properly. Add a verification step in the README.md for checking the pre-commit configuration during setup.

Added a section in the README.md explaining the configuration and installation of pre-commit hooks.

Continue verifying that pre-commit hooks are running consistently across all team members by adding a verification section to the README.md.

Next Steps: Continue testing across different environments and document setup instructions for pre-commit hooks.

Update documentation with instructions for setting up pre-commit on different platforms.

Pre-commit hooks were updated, and the setup instructions in CONTRIBUTING.md were expanded to include clearer guidelines for configuring .pre-commit-config.yaml. Consistent formatting is now enforced across all environments


print resource list metadata in velero backup describe --details

Download and print backup resource list metadata when running velero backup describe --details <name>.
e.g.
$ velero backup describe --details nginx-backup-2
Name:         nginx-backup-2
Namespace:    velero
Labels:       velero.io/storage-location=default
Annotations:  <none>

Phase:  PartiallyFailed (run `velero backup logs nginx-backup-2` for more information)

Errors:    2
Warnings:  0

Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  app=nginx

Storage Location:  default

Snapshot PVs:  auto

TTL:  720h0m0s

Hooks:  <none>

Backup Format Version:  1

Started:    2019-07-31 13:55:29 -0700 PDT
Completed:  2019-07-31 13:55:46 -0700 PDT

Expiration:  2019-08-30 13:55:29 -0700 PDT

Resource List:
  apps/v1/ReplicaSet:
    - nginx-example/nginx-deployment-5b658f5d7f
    - nginx-example/nginx-deployment-75675f5897
  v1/Endpoints:
    - nginx-example/my-nginx
  v1/Namespace:
    - nginx-example
  v1/PersistentVolume:
    - pvc-dd06dd30-b259-11e9-a63b-025000000001
  v1/PersistentVolumeClaim:
    - nginx-example/nginx-logs
  v1/Pod:
    - nginx-example/nginx-deployment-5b658f5d7f-28qpb
  v1/Service:
    - nginx-example/my-nginx

Persistent Volumes: <none included>

depends on #1709
fixes #396
Signed-off-by: Adnan Abdulhussein<EMAIL_ADDRESS>

I updated the TestGetDownloadURL test to test multiple keys for different scenarios (e.g. scheduled, prefix, multiple dashes in the name). It's a little bit more verbose, but might be easier to add additional kinds in the future. Let me know what you think!

The test LGTM, though looks like the cases for restore logs & results got dropped

@skriss the restore logs/results are still there, just moved under the expectedKeyByKind for each test

Ah, I see. It's slightly confusing because they're in tests that are titled "backup", "backup with prefix", etc.  It might make sense to separate out the restore-specific targets into their own test cases.

Good point, and also it doesn't really make sense in the context of the scheduled backup. I'll split those out, thanks!

Merging in prep for beta, can address any further feedback in followups.


Allow to configure GOMEMLIMIT / automatically set GOMEMLIMIT according cgroups

Is your feature request related to a problem? Please describe.
In Kubernetes I want to set resource limits:
resources:
  limits:
    memory: 10G
  requests:
    cpu: "3"
    memory: 10G

I could then set the GOMEMLIMIT like this with the downwards API:
env:
  - name: GOMEMLIMIT
    valueFrom:
      resourceFieldRef:
        resource: limits.memory
        divisor: "1Mi"

But this is not recommended, because you should set GOMEMLIMIT to 90% of the available memory. This is currently not possible with the downwards API.
Therefore it would be nice, if oCIS would automatically configure it (whenever possible).
A POC is done in #4856

@butonic This is important and contributes to your observations during the benchmark tests. Can you take care to get that POC merged?

fixed with https://github.com/owncloud/ocis/pull/5732


Add "use_mmap" to environment variable

I recently discovered the potential benefits of the --no-mmap option, particularly for specific system configurations, such as PCs or laptops equipped with only 8GB of system RAM and a GPU with VRAM of 6GB or more, capable of loading entire models onto it.
Loading models with mmap can render the use of 8B models nearly impossible, as it can cause RAM usage to spike to 99% and remain there, often leading to complete freezing of the PC and requiring a hard reset.
Disabling mmap allows users to load 8B models while still having half of the RAM available for other tasks. The only drawback is a slightly longer initial model load time (around 5-10 seconds in my case), which I believe is a worthwhile trade-off. Quick benchmarks even suggest that --no-mmap might be slightly faster for generating tokens.
Now, here's the rationale for adding an environment variable.
Many frontends/UIs utilize Ollama, but a significant portion of them lack the toggle option to set the "nommap". By introducing an environment variable, I can globally set "nommap" and ensure that any frontends will load models with the nommap flag enabled.

It seems "mmap" configuration is only available via Ollama pip package which is on the client-side. It would be very useful if web ca provide this as an arg to the server command such as:
"ollama server --use-mmap False" or something

It would be great having this option server side globally


Take throttle from the appropriate controller given the current mode.

Bench tested with VT_FW_PERM_STAB = 0 and VT_FW_PERM_STAB = 1

Flight tested,  will merge soon.

Merged.


Instantiate loads modules for every instance

Current behaviour
When using jco transpile with --instantiation, the generated code loads and compiles the necessary WASM modules for every created instance:
export async function instantiate(compileCore, imports, instantiateCore = WebAssembly.instantiate) {
  const module0 = compileCore('component.core.wasm');
  const module1 = compileCore('component.core2.wasm');
  const module2 = compileCore('component.core3.wasm');
  // ...
}

A better way
It would be better to load the modules one, and re-use the loaded modules. You could even load them the same way they are loaded without the --instantiation flag, so that the user doesn't have to provide the compileCore function.
A full example can be seen here with the usage here, but here is the code snippet:
// TODO: should be Promise.all
const module0 = await fetchCompile(
  new URL("./component.core.wasm", import.meta.url)
);
const module1 = await fetchCompile(
  new URL("./component.core2.wasm", import.meta.url)
);
const module2 = await fetchCompile(
  new URL("./component.core3.wasm", import.meta.url)
);

export async function instantiate(
  // compileCore, // not needed anymore
  imports,
  instantiateCore = WebAssembly.instantiate
) {
  // Not needed anymore either
  // const module0 = compileCore('component.core.wasm');
  // const module1 = compileCore('component.core2.wasm');
  // const module2 = compileCore('component.core3.wasm');
  // ... same code as before
}

This is not only better for performance (doesn't re-fetch and re-compile modules for every instance), but also better for the user, since they don't need to worry about the compileCore function.
Things to iron out
This was kind of "hacked together", but it shows that it can work. The modules should be loaded in parallel with Promise.all, and there might be other problems with a top level await, but I assume both of these issues can be easily resolved.

Firstly note you can just write compileCore to cache fetch (which you probably should).
I'd be open to this, but as a variation of the --instantiation flag to indicate it's a third virtualization level sitting in between full virtualization and host-level resolution.
The current instantiation in this general form doesn't assume the location of Wasm modules on the filesystem or top-level await. In theory by not relying on Promise.all we also allow bindings work to continue even when some modules are still being compiled.
Perhaps --instantiation=full is used to distinguish the current form, or something similar? Would you be interested in working on a PR?

Firstly note you can just write compileCore to cache fetch (which you probably should).

Good idea. This would load and compile the cores "lazily" on the first instantiate, which has it's advantages, but might not always be desired.
I am still "stuck" in the "Component::new"/Module::new and "component.instantiate"/Module.instantiate being 2 separate things, but I guess I could do something like this:
export function preLoadCores(compileCore) {
  return Promise.all([
    compileCore('component.core.wasm'),
    compileCore('component.core2.wasm'),
    compileCore('component.core3.wasm'),
  ]);
}

export async function instantiate(compileCore, imports, instantiateCore = WebAssembly.instantiate) {
  const module0 = compileCore('component.core.wasm');
  const module1 = compileCore('component.core2.wasm');
  const module2 = compileCore('component.core3.wasm');
  // ...
}

The current instantiation in this general form doesn't assume the location of Wasm modules on the filesystem

That's true, the module bytes could be in-memory, which they are in my use-case

... or top-level await

I am not familiar enough with how JS modules are loaded to understand the pros and cons of top-level awaits.
One thing I will not though is that the exports without instantiation mode are kind of messed up.
You get an $init object that you are supposed to await, and the exported functions, which you should call after awaiting the init object, but the exported function are not the result of awaiting the init object, you just get and can call them "wrongly".
I understand that this is workaround for situation where the top-level await will not be awaited, but it's still kind of messed up.

... to indicate it's a third virtualization level sitting in between full virtualization and host-level resolution.

I will admit I have no idea what that means.

In theory by not relying on Promise.all we also allow bindings work to continue even when some modules are still being compiled.

That's a good point. I added the // TODO: should be Promise.all mostly because in the proof of concept code the cores were being loaded sequentially instead of simultaneously, which Promise.all would solve.

Perhaps --instantiation=full is used to distinguish the current form, or something similar? Would you be interested in working on a PR?

Maybe, what I would be interested in is exporting two separate functions:

compile that compiles the cores and returns the instantiate function. This function can take compileCore as an argument, but it would be even better if it was an optional argument and the default would be to take the cores from the same directory as the .js script is it, the same way it is done without the instantiation flag.
instantiate function that works with the already-compiled cores. You cannot call instantiate without calling calling compile first, because you get the instantiate function as a result of the compile function.

If this workflow is something you would be willing to merge (enabled with the --instantiation=full flag, let's say), then I can work on it.

Your suggestions sounds fairly sensible to me. I would still prefer that compile be optional though and that just-in-time compilation can still be used by default as it is currently structured. So that instead of this being an explicit compile "step", it is an optional precompile step.
Something like:
let compileCache = {};
const defaultCompileCore = name => compileCache[name] || (compileCache[name] = fetchCompile(name));

async function fetchCompile (name) {
  // ... standard implementation ...
}

export const precompile (compileCore = defaultCompileCore) => Promise.all([
  compileCore('name1.core.wasm'),
  // ...
]);

export async function instantiate(imports, compileCore = defaultCompileCore, instantiateCore = WebAssembly.instantiate, compileCore = ) {
  // .. compileCore interleaving remains ..
  const modulen = await compileCore('componentn.core.wasm');
}

Does the above work for you? If so, in this framing we don't even need another mode for it and could make it the default, possibly with an optional --no-precompile flag or something to disable it?

The argument order in instantiate changed, but that can be fixed with something like
export async function instantiate(compileCore, imports, instantiateCore = WebAssembly.instantiate) {
  compileCore = compileCore || defaultCompileCore,
  // .. compileCore interleaving remains ..
  const modulen = await compileCore('componentn.core.wasm');
}

Now it's slightly confusing that the first argument is optional, but changing the argument order is a breaking change.
I could start working on a PR, but currently I have other things I want to finish first.

@kajacx JCO is currently under active development so it's fine to make breaking changes.

We almost got to a concrete proposal here, which I'd be very happy to land in this project, but short of that work actually happening - since this is in theory purely ergonomic and neither a feature nor a bug, closing for now.


how do i use it myself?

I said it wrong, I'm trying to connect myself, how do I release my access?

how do I connect other devices as I am on the same Wi-Fi as the. as when I do it says Error connecting

how do I connect multiple devices connected to the same Wi-Fi as me?

You would have to set it to your private IP insted of <IP_ADDRESS> or localhost, that should help. Thats at least what I did.


add fixtures from the thrift library

@nnance these are the .thrift files from the test suite of the C Thrift library.  I copied them over and added some comments about things we don't support.  I'm not sure if you want to include them verbatim.

+1

Merged into develop branch as 0184eb59a59decf74deca425179233d359ed24ab


Update Eclipse to 2023-12-R (4.30)

Release notes
https://eclipse.dev/eclipse/news/4.30/
https://projects.eclipse.org/releases/2023-12
Tested links

Eclipse Java: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2023-12/R/eclipse-java-2023-12-R-linux-gtk-x86_64.tar.gz&r=1#/eclipse-java-4.30.tar.gz
Eclipse JEE: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2023-12/R/eclipse-jee-2023-12-R-linux-gtk-x86_64.tar.gz&r=1#/eclipse-jee-4.30.tar.gz

Hello @dusansimic, requesting a review :)

Thanks for the contribution and sorry for the delay 😄


namespace for generated configMap

The provider seems to always put the generated confgiMap into the default namespace. There is a setting in the target section to control the name of the configMap, but not its location. How can I create a confgMap in a different namespace?

Looks like namespace is set when creating the resource.

Correct, the target ConfigMap is in the namespace of the AzureAppConfigurationProvider resource.


WIP: model.base: Add new attributes to class AdministrativeInformation

Version 3.0 of the spec introduces the 2 new attributes

creator
template_id to class AdministrativeInformation.
This PR adds them to the class.

Todo: Adapt the adapters. @jkhsjdhjs could you do that please?

Sure, I also just noticed that you forgot to add the _string_constraints decorator for Identifier.

I would suggest this to be merged before #106, as this PR is already done and #107 will need to be adjusted and rebased so it changes the newly introduced GlobalReference to ExternalReference as well.


BUG: Fix bug with loading from database

Problem
The difficulty is not being calculated correctly when loading a chain from the database and so the chain fails to fully load.
Steps to re-produce

start a private node locally with a database
mine against the private node for a while
stop and restart the node - and see the chain does not fully load due to invalid difficulty

This is re-lated to the current difficulty algorithm.

I did a little research into this and I think the problem may be rooted in these magic numbers in src/core/blockchain/concensus.cr
BLOCK_TARGET_LOWER  = 10_i64
BLOCK_TARGET_UPPER  = 40_i64
BLOCK_AVERAGE_LIMIT =     720
Specifically BLOCK_AVERAGE_LIMIT of 720 .. I've noticed in testing that things go south consistently at block 723 .. just a few blocks after the algorithm transitions in how it computes the current_target.
The bug can be avoided by changing BLOCK_AVERAGE_LIMIT to a value above the current known block height (I did this just as a test), or getting rid of the 'if' that is related to BLOCK_AVERAGE_LIMIT.  This isn't the correct fix obviously... that's probably rooted in making this calculation more closely match the difficulty calculation in mining... but I thought I'd leave this info here as current progress on research.

So it appears that the only other place BLOCK_AVERAGE_LIMIT is used is in mining, where it is adjusted by 10 in src/core/blockchain.cr:
if block_averages.size > Consensus::BLOCK_AVERAGE_LIMIT + 10

Therefore when loading mined blocks from the DB, the same adjustment must be made.  Not sure why the above adjustment was done this way, but all mined blocks were done with this offset in difficulty calculation.. so to fix the above would mean that the existing chain would have to be expunged .. so the fix that works with the existing chain is to do the same adjustment to the if statement in the code in src/core/blockchain/concensus.cr

The correct fix is the implementation of 'Dark Gravity Wave' so that issue (250) supersedes this one.


Update CONTRIBUTING.md for Improved Contribution Guidelines

Issue Description:
As our project continues to grow and attract contributors, it's essential to ensure that the contribution process is as clear and straightforward as possible. The CONTRIBUTING.md file serves as a vital resource for new and existing contributors. However, it can always be improved to provide better guidance and make it easier for contributors to get started.
Requirements:

Simplified Onboarding: Update the CONTRIBUTING.md file to provide clear, step-by-step instructions on how to get started with contributing to the project. Include information on setting up the development environment, running tests, and submitting pull requests.

Code Style and Guidelines: Include coding style guidelines and any specific rules or conventions that contributors should follow when submitting code changes. This ensures consistency in the project's codebase.

Issue Reporting: Clarify how contributors should report issues, including the information required in an issue report and how to use issue templates if applicable.

This update will greatly improve the experience for both new and experienced contributors, making it easier for them to understand and follow the contribution process.
If you have any questions or suggestions for specific improvements to the CONTRIBUTING.md file, please feel free to comment on this issue. Your input is valuable in enhancing the contribution process.
Thank you for your willingness to help improve our project's documentation and onboarding process!

interested can u assign me

Hey, can you assign it to me and also provide some details on code style and guidelilnes

Hey can u please assign this to me

Hey there,  I would like to contribute to this issue, Can you please assign this to me.!?

Hello @yashj09, @Vijayabaskar56, @i-am-SnehaChauhan and @kunjshukla ,
Thank you all for your interest in contributing to this task. I appreciate your willingness to help improve our contribution guidelines.
To make this process more collaborative, I'm assigning this task to all of you. Each of you has the option to either collaborate and create a single, comprehensive CONTRIBUTING.md file together, or you can each work on your own version. In the end, we will evaluate the contributions and choose the one that best aligns with our project's needs and goals.
Please coordinate among yourselves and feel free to discuss any questions or ideas you may have during the process. Once you've completed your contributions, please submit them for review.
Looking forward to seeing your work and thank you for your valuable contributions!

@yashj09 @Vijayabaskar56 @i-am-SnehaChauhan
I would suggest we all collaborate to make a file together.
But I have a doubt about this, @ajaynegi45 how will each of us benefit if we collaborate to make one single file.!?

We can divide each one , one would take simplify onboarding another one can take code styling and guidance vicea Versa

@yashj09 @Vijayabaskar56 @i-am-SnehaChauhan
I would suggest we all collaborate to make a file together.
But I have a doubt about this, @ajaynegi45 how will each of us benefit if we collaborate to make one single file.!?

We can divide each one , one would take simplify onboarding another one can take code styling and guidance vicea Versa

Hi @kunjshukla ,
That's a valid concern, and I appreciate your question. Collaborating to create a single file can actually be quite beneficial in several ways:

Efficiency: When multiple people work together on one file, you can divide the task into smaller, manageable parts. This often leads to faster completion since several individuals can work in parallel.

Quality Control: By collaborating, we can ensure that the file is reviewed and improved by multiple contributors, which can lead to a higher-quality end product.

Diverse Perspectives: Different  members can bring diverse perspectives and expertise to the table, resulting in a more well-rounded and comprehensive solution.

Here's how we can make it work:

Each of you can divide the task into specific sections or components.
Make the necessary changes and improvements in your respective sections or components.
Once your work is ready, create a pull request for review.
After reviewing the changes, we can merge them into the main file.

By following this collaborative approach, we can efficiently create a single, well-structured file while benefiting from the contributions of each member.
Thank you for considering this approach, and I look forward to our collaboration!

Thank you @ajaynegi45 for your idea for Collaborating.
@Vijayabaskar56 @kunjshukla @i-am-SnehaChauhan
So, according to me CONTRIBUTING.md file has 4 main section

Introduction and Purpose
Getting Started
How to Contribute/Contributing Guidelines
Code of Conduct
.
so my idea is that we all 4 can choose 1 section and work on that  , so if u agree with me then comment you section you want to work.

I will take how to contribute section

Okay, I'll do getting started.

i will do Introduction and Purpose section

Which section is left .?

@kunjshukla code of conduct


Change Select border styling to match Coastline input styling

Note: I did not attempt to incorporate the Coastline stylesheet in any way. This is a quick fix to update the styling closer to current Coastline styling.
.Select-control: We remove border-color since it is already applied in
the border property.
.Select.is-open > .Select-control: We remove border-color to match the
normal Input styling, which doesn't change when it is open.
Updated Select:

Existing `Input type='select':

Closing in favor of a Coastline change


Enhancement: Deprecation eslint rule. Closes #6237

Closes #6237

Hi @milanholemans, could you please re-run the workflow? Seems like a random error. Thanks

Thank you @MartinM85, we'll try to review it ASAP.

Not sure right now, but the error on macos

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Can be related to eslint-plugin-deprecation issue.

Not sure right now, but the error on macos

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Can be related to eslint-plugin-deprecation gund/eslint-plugin-deprecation#67

Hmm that's quite problematic.

If it's failing our pipelines, and we can't fix it, we should consider something else.

I have also encountered an issue with increased execution time of the linting. The CLI for M365 has a large code base, the performance of this plugin is really bad.
In the worst case, we can get rid of the plugin eslint-plugin-deprecation and keep the refactored code.

I have also encountered an issue with increased execution time of the linting. The CLI for M365 has a large code base, the performance of this plugin is really bad.
In the worst case, we can get rid of the plugin eslint-plugin-deprecation and keep the refactored code.

That's a pity. Like you mentioned, if we can't get it to work, we'll just review the refactored code.

Plugin eslint-plugin-deprecation removed

@waldekmastykarz  eslint-plugin-deprecation was causing the error when running test on macos.

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Similar to https://github.com/gund/eslint-plugin-deprecation/issues/67
https://github.com/pnp/cli-microsoft365/actions/runs/10370949281/job/28746774555
and increased execution time of the linting, because the CLI for M365 has a large code base, the performance of this plugin is really bad.
I only refactored deprecated functions.

Thanks for clarifying. Let's update the PR's title to communicate this more clearly.

Merged manually. Thanks for the fix!


race condition in bombastic_reindexing integration tests

After debugging the bombastic_reindexing, it looks like there is a race condition if there are > 1 bombastic API pod running, and I think this is why:

Test indexes the test document
API pod A pulls down the new index
API pod B has not yet pulled down the new index
Test queries for the number of hits and the load balancer goes to API pod A which returns 1
Test moves into the second part to modify the document and index it again
Test queries for the number of hits and the load balancer goes to API pod B which returns 0
API pod B pulls down the new index
Test fails

The whole issue stems from the fact that the API pods are completely independent and may pull the new index at different points in time.
I will push a fix that resolves this by allowing the second assertion to fail similarly to the first assertion, which should handle the case where the second pod hasn't synced the index yet.
Another, more complex approach, could be to coordinate the index sync between the pods but that would require some coordinator service like etcd/zookeeper or something built into the processes (raft). However, I don't think that API pods being out of sync for a few seconds is that big of an issue.
CC @jcrossley3

Nice catch!


Add files via upload

Please add Staatliche Berufsschule 1 Bayreuth.

Please fork SWOT repository, copy file.zip in the root folder of your forked SWOT repository. Then unzip file.zip there with no changes to the directory structure. Then make a new pull request. If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message. I have to close this request without merging. Thank you for your understanding.


improve output files metadata in the ro-crate

Thanks to the edit-ro-crate.py script we now have descriptions for the RO-Crate that the wf returns; see #18.
However, the description can improve to a great extent and probably add more things there; that I guess is a bit of research issue as well.
@cymon @isanti @kmexter I open this issue mostly as a poke for future versions of the wf. :tada:

OK, we can certainly have a look at that, in the context of FAIR EASE for sure.

Hi all! this is a nice thread! @hariszaf thank for opening it.
The following are examples of some simple additions in the output file metadata, file formats in particular.
The main motivation of such additions is to increase machine readability further.
Via looking up ontologies like EDAM (https://edamontology.org/page) the "fileFormat" of some of the metaGOflow output files could be described
e.g. #1
"@id": "results/ERR4765907_2.fastq.trimmed.fasta",
"@type": "File",
"encodingFormat": "text/plain",
"name": "Filtered .fastq file of the single-end reads (forward/reverse)."
could also include:
"fileFormat":  {"@id": "http://edamontology.org/format_1929"}
where:
http://edamontology.org/format_1929 corresponds to the FASTA format including NCBI-style IDs.
e.g. #2
"@id": "results/taxonomy-summary/SSU/ERR4765907.merged_SSU.fasta.mseq_json.biom",
"@type": "File",
"encodingFormat": "application/json-ld",
"name": "BIOM formatted taxon counts for SSU sequences"
could also include:
"fileFormat":  {"@id": "http://edamontology.org/format_3746"}
where:
http://edamontology.org/format_3746 corresponds to the BIOM format.
e.g. #3
ditto for TSV files (http://edamontology.org/format_3475; Tabular data represented as tab-separated values in a text file)
and so on!
This could be really powerful as subsequent analysis modules could not only cross-check if an input file is e.g. text, but it also conforms to the appropriate file format.

Sounds good. I have not looked at what is currently there, but to give you an idea of a minumum of provenance information that we are adding to the ARMS co-create.json files, see my spreadsheet https://docs.google.com/spreadsheets/d/12Xc19hyD0NUoLezvUjMtZU6KBsyGvZ0dhPde59xEkmQ/edit?usp=sharing which I am using to tell Cedric what to add to the ro-crates that are automatically created for the 4 repos mentioned in the 4 tabs. You will see things like
geo coverage
time coverage
contributors
influences
description (I believe you have this field already)
keywords
to which perhaps you could add
dependsOn
dependOn


Timezone as "hour" offset from GMT/UTC

This is a tremendous GEO lookup. Thank you. Wondering if it is easy to add a property to the location object that represents the timezone as hour offset from GMT/UTC (+/-). Doesn't have to identify daylight savings changes. The timezone string is helpful but requires significant parsing/mapping depending on the underlying system being used to determine the timezone hour offset. Note that this application is for a server-side request where the timezone offset in Date objects represents the "server's" location so we need to use the timezone from the lookup results to get an accurate idea of what timezone the user is in. Thank you so much.

Unfortunately this information is not included in the MaxMind Database, so to provide this information I would need to add it to the result after the actual lookup.This has two disadvantages:

There would be a second (timezone-offset database) that has to be maintained.
Adding information from a second database to the result would have a negative impact on performance. (which absolutely matters when doing lots of requests per second.)

This is why I will not add this additional information to the results.

Understood. Thanks.


Run notebook pages with pyodide

We currently use sphinx-book-theme launch buttons and Thebe to make pages that are generated from Jupyter notebooks 'runnable' in the browser (e.g. linking to Colab or Binder). It would be faster, though, to run the notebooks directly with WASM with pyiodide. Some relevant links:

Thebe talk at JupyterCon 2023
https://executablebooks.github.io/thebe/
https://mystmd.org/thebe/quickstart-lite

@shenvitor I was mentioning this issue. Seems that the way to go forward is to use the new jupyterlite-sphinx


Improve stack test and enable back on CI

:shipit:

Nice :shipit:

@jianchun @ianwjhalliday Thanks for the review


Is predefined role pg_signal_backend required when.using unpriv user?

Bon soir,
I want to run ldap2pg v6 using an unprivileged user. Next to role options CREATEDB & CREATEROLE do I also need to grant predefined postgres role pg_signal_backend so that ldap2pg can kill existing sessions before dropping a user?
Why is the role option CREATEDB required in v6 od ldap2pg? Does the unprivileged user have to be the owner of the managed DB or can the DB have a different owner?
Thanks,
Mat

Hi. In general, ldap2pg must have the privileges it will be able to grant.
E.g. if you manage superusers, ldap2pg must be superusers.
Note that Postgres 16 changes a lot role management. Prior to Postgres 16, CREATEROLE is considered flawed and is de facto equivalent to being superuser. This is because CREATEROLE allows to escalade privileges by granting almost any other roles.
So I'd suggest to run superuser for Postgres 15 and wait for ldap2pg 6.1 to be released to run unprivileged with Postgres 16.
Is that clear for you ?
Regards,

Thanks for your reply. I understood that superuser is recommended (for PG 15).
In my case, the owner of the DB is not a superuser so I need to run ldap2pg as superuser in order to be able to manage privileges and additional roles that inherit from the DB owner role.
BR,
Mat

In my case, the owner of the DB is not a superuser so I need to run ldap2pg as superuser in order to be able to manage privileges and additional roles that inherit from the DB owner role.

You can inherite from DB owner with ADMIN option, that should do the trick.


cluster monitoring failure on 2.4.7: The CustomResourceDefinition "podmonitors.monitoring.coreos.com" is invalid

V 2.4.7
k8s 1.18.8
operator-init-crds pod failed
The CustomResourceDefinition "podmonitors.monitoring.coreos.com" is invalid:

spec.validation.openAPIV3Schema.properties[spec].properties[podMetricsEndpoints].items.properties[targetPort].anyOf[0].type: Forbidden: must be empty to be structural

Delete and redoing yields in the same

same in v2.5.1 with k8s v1.19.3

@superxor I'm closing this issue out in favor of https://github.com/rancher/rancher/issues/29348 since it seems to be the same underlying issue. As noted in https://github.com/rancher/rancher/issues/29348#issuecomment-708963326, this seems to be an issue with the Custom Resource Definition that is deployed itself.

This did not resolve the issue

@superxor the linked issue is still open / unresolved, but it tracks the same bug.


imdecode/imencode plus some refactoring

Dear Danilo,
this time I've attached a patch against the 0.8 release which adds cv::imdecode and cv::imencode to transfer data between cv::Mat and Tcl byte arrays. The strings for e.g. filenames are now recoded to system encoding or UTF-8 normalized for putText. A few fixes and a little bit code cleanup is also in the patch.
Hope, you'll find it useful,
Christian
tcl-opencv-0.8.diff.gz

Thanks for your effort.


[PE-D][Tester E] Commands stated in the Command summary section are not updated

In he Command summary section in the user guide, the unassign task, clear task, and exit command are not added here.

Labels: type.DocumentationBug severity.Low
original: zengzihui/ped#9

Fixed in #139.


Fixing autograd images

When being build, auto-grad links are not behaving as expected. Adding full links to fix images on this page.

Restarted stuck CI job.


[FLINK-17026][kafka] Introduce a new Kafka connect or with new proper…

…ty keys
What is the purpose of the change
This patch add a new table factory for new connector properties based on FLIP-122 and new source sink based on FLIP-95.
Brief change log
(for example:)

Add new table factories for Kafka 0.10, 0.11 and the universal version
Add new table source sinks for Kafka 0.10, 0.11 and the universal version

Verifying this change
Added UTs and ITs.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? not documented

Unfortunately, the following case is failed.
[ERROR]   Kafka011TableITCase>KafkaTableTestBase.testKafkaSourceSink:145 » Execution org...

Passed in my branch: https://dev.azure.com/imjark/Flink/_build/results?buildId=89&view=results
Merging...


Exporting and importing db functions, triggers, indexes, etc

refer to
active record migration
https://github.com/rails/arel

will be handled as dumping and filling from .sql dump files - however we will still have to account for matching to schemas, migrations, and other rails knowledge that might not necessarily be contained in or can be not included within a sql dump


Docker Hub repository name
test/non-existing-extension
Terms of services

[X] I accept the term of services

/validate

/validate

/validate

:x: There was a problem during the validation job.
Someone from the @docker/extensions will have to take a look at this issue.
We will let you know in this issue when it is fixed.

See [action]({{ .workflow_url }}) for more details.


updating waitlist dec 15

📝 Changed routes:

/index.content

(view full size)

Commit 9e14588976c3a990c22f32ee9a2249a4228c5c8b (https://opo-data-3e7ah71fv-coa-solutions.vercel.app).


WASM cannot be installed

Describe the bug
When I try to install mobiflight and is asked to installed the WASM I get a message that it failed to installed.
I get at popup where it says "MobiFlight WASM was not installed successfully. Please check the Log for more information"
I have checked the log but there is no info regarding WASM.
I have installed the latest version: 10.0.2
Steps To Reproduce
Steps to reproduce the behavior:
I have removed the old installation of all flightsim related on my PC to make a new installation of my simulator environment.
I installed the MSFS
installed all airports I have bought
Installed addon aircraft (Fenix)
Installed MobiFlight Connector. That is installed with no issue, but when I try to installed the WASM the popup is shown. I have also tried to reboot, uninstall and install again, install from the menu in MobiFlight connector
Expected behavior
Successfully installation of WASM
Actual behavior
See above
Details

MobiFlight Version: [10.0.2]
FlightSim: [MSFS2020]
AddOn: [Fenix. a lot of different airpoirts]

Additional context
Add any other context about the problem here.

Try deleting the folder mobiflight-event-module in your MSFS community folder because it might've been corrupted.

That solve the issie, Thanks @LazoYoung


difference between this repo with the torchvision deformable convolution op

Hi, author, what's the difference between this repo with the torchvision DCN op.
https://pytorch.org/vision/stable/_modules/torchvision/ops/deform_conv.html

Also
https://github.com/developer0hye/Simple-PyTorch-Deformable-Convolution-v2/blob/main/experiment.ipynb

Hi, author, what's the difference between this repo with the torchvision DCN op. https://pytorch.org/vision/stable/_modules/torchvision/ops/deform_conv.html

The previous versions of DCNv2 in dcn_v2_cuda.cu use THCUDA which causes errors during setup.py. This repo uses AT Tensor functions which resolves the issue for higher pytorch and CUDA versions

@haak0 I am also curiousity about this. Honestly speaking I do not know.


Custom editor search functionality crashes visual studio code

Type: Bug
We are currently writing our own extension to support the coq language using coq-lsp. The extension will be published on the market place very soon under the name Waterproof. Our extension supports multiple panels to be open at the same time displaying different information. Now, in these panals we would like to support search functionality to search through text in these panels. When we have enabled this search functionality we can use it to search terms in this panel. However, when we enter text in the search functionality and click to another panel it crashes the entirety of visual studio code, shutting it down. This only happens when text is present in the search bar. When there is no text one can click to other tabs without crashing. I will update this issue once the extension has been published.