feat: add participation to account manager nodejs

Description of change
Merge #1616 first!
Add participation methods to account manager.
Type of change
Choose a type of change, and delete any options that are not relevant.

Enhancement (a non-breaking change which adds functionality)

How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that new and existing unit tests pass locally with my changes

Can you rebase please 🙏🏻 ?


API key in Src/MapPredictions.ipynb

your code has your API key for bing maps, might cost you a lot if people keep using

Thank you @ncdejito, for bringing this to my attention, thank you very much.


Stopped Functioning as of 3-ish days ago

Don't know why but it simply doesn't show up anymore

Hopefully fixed now with 1.3.0


Load  GCP metadata from H1 NetCDF file

name: Feature request
title: 'Load  GCP metadata from H1 NetCDF file'
labels: 'enhancement'
assignees: ''

Is your feature request related to a problem? Please describe.
Some of the NetCDF files for HYPSO-1 have GCP (Ground Control Points) embedded into it as metadata. This is essential for accurate georeferencing. The library should try to embed this information when loading NetCDF file with this metadata available, and not fail when it is not available.
Describe the solution you'd like
A part of the loading of NetCDF files should check for the GCP metadata and incorporate it into the loaded variable, if available, for analysis tasks where high accuracy geo.referencing is important.
Describe alternatives you've considered
N/A

Blocked by #4


Route "/" accessible in wrangler dev but not in production

As titled. Do I miss something?

What are your wrangler settings? Can DM on Twitter if you don't want to share here.

We spoke a little bit on Twitter. I cannot reproduce this. Here's my very basic setup:
// src/index.ts
import { Router } from 'worktop';
import * as Cache from 'worktop/cache';

const API = new Router;

API.add('GET', '/about', (req, res) => {
  res.send(200, 'ABOUT');
})

API.add('GET', '/', (req, res) => {
  res.send(200);
})

Cache.listen(API.run);

// package.json
{
  "private": true,
  "name": "worktop123",
  "main": "build/index.js",
  "scripts": {
    "build": "cfw build src --single"
  },
  "devDependencies": {
    "cfw": "0.1.3",
    "typescript": "4.2.4",
    "worktop": "0.5.0"
  }
}

# wrangler.toml
name = "worktop123"
type = "javascript"
workers_dev = true

route = ""
account_id = "<REDACT>"
zone_id = ""

[build]
command = "npm run build"
upload.format = "service-worker"

Currently deployed to https://worktop123.lukeed.workers.dev.
The home page returns a blank page (200 code) because I sent no content.
The about page, for added measure, returns the ABOUT text for a 200 status code.

Closing as invalid/not reproducible, but happy to try again if you have something I can try again.
Although, my hunch is that there's something else going on with your account/routing settings (not sure what) – and isn't code-related.

No idea but it works now.

Probably networking hiccup on CF side for the new dev domain 🤷


OCM-2424 | fix: Made info message only print when on auto mode

OCM-2424 Is about an info message that wasn't supposed to pop up when using the create oidc-config command in Manual mode, but it did. Now the info message should only pop up when the mode is Auto

/lgtm

/lgtm


Unable to manage SPN Permissions since Pydanticv2 Upgrade

Using the API to manage permissions in a pipeline requires the use of a service principal. However since the upgrade to PydanticV2 (my only correlation) this is now erroring with 'Internal Server Error'
Steps to reproduce the behavior:
Portal behaviour:
Using a Admin User Account, attempt to add service principal as admin = 422 Error received
{
    "detail": [
        {
            "type": "value_error",
            "loc": [
                "body",
                3
            ],
            "msg": "Value error, email should not be set for 'principal' type",
            "input": {
                "type": "Principal",
                "name": "REDACTED",
                "id": "REDACTED",
                "email": null
            },
            "ctx": {
                "error": {}
            },
            "url": "https://errors.pydantic.dev/2.4/v/value_error"
        }
    ]
}

Viewing the Log Stream within the application the following error is visable:
2023-10-10T10:55:37.878872401Z   {'type': 'value_error', 'loc': ('response', 1), 'msg': "Value error, email should not be set for 'principal' type", 'input': {'type': 'Principal', 'name': 'REDACTED', 'email': None, 'id': 'REDACTED'}, 'ctx': {'error': ValueError("email should not be set for 'principal' type")}, 'url': 'https://errors.pydantic.dev/2.4/v/value_error'}

API Behaviour (using postman as SwaggerUI is missing auth headers)

As Admin - add SPN user POST /admin/admins - postman returns no response body
Run Get /admin/admins with user account and internal Server Error is shown:

Remove Admin using Delete /admin/admins/{objectId}
Run Get /admin/admins again and response succeeds:

[
    {
        "type": "User",
        "name": "Chris",
        "email": "REDACTED",
        "id": "REDACTED"
    },
    {
        "type": "User",
        "name": "Chris(UK Dev)",
        "email": "REDACTED",
        "id": "REDACTED"
    },
    {
        "type": "User",
        "name": "Barry",
        "email": "REDACTED",
        "id": "REDACTED"
    }
]

Great work @DCMattyG

Thanks for all of the helpful details above @ChrisSidebotham and the chat on Teams. Definitely helped to get this fixed ASAP!


Don't show monaco for package files

With this change, the monaco toolbox only shows up for main.ts.

@abchatra says it's fine.


Added Angular 4 example

Description

GitHub Issues

Coverage decreased (-15.7%) to 57.869% when pulling a2d7e360df6250130ae9285c04d0bbf06c05481e on miguel3010:master into 29bddcb29fda5c71f0aa29bea6f5694d8b15761c on Miserlou:master.

Coverage decreased (-15.7%) to 57.869% when pulling a2d7e360df6250130ae9285c04d0bbf06c05481e on miguel3010:master into 29bddcb29fda5c71f0aa29bea6f5694d8b15761c on Miserlou:master.

Coverage decreased (-15.7%) to 57.869% when pulling a2d7e360df6250130ae9285c04d0bbf06c05481e on miguel3010:master into 29bddcb29fda5c71f0aa29bea6f5694d8b15761c on Miserlou:master.


HTML and JavaScript indent plugin conflicts

Steps to reproduce

Create HTML file like this

Example

<script>
	123
	function a(){
			return 1
		}
</script>

vim --clean main.html
=G to format all
The wrong indentation does not change.

Expected behaviour
JavaScript is indented correctly

More info:

When let g:html_indent_script1 = "zero" is set in vimrc, it works correctly
However, it's documented in html-indent that "zero" is the default, yet the JavaScript plugin sets it to inc if the user doesn't set it manually, which is a bug.

Otherwise, even if the user explicitly specify the option to be "inc", the formatting is still incorrect
because the HTML plugin manually adds; however sometimes the JavaScript plugin already indent correctly, for example:

<script>
    function a(){
        return 1 // (1)
    }

function b(){ // (2)
        return 1
}

In this case,
* GetJavascriptIndent() returns the correct indent at line 1 (= 8)  by looking at the previous function, so that when the HTML plugin adds the indent it becomes wrong
* However, outside a function/block (line (2)) it returns the wrong indent, so when the HTML plugin adds the indent value it becomes correct.
Operating system
Arch Linux
Version of Vim
(isn't this text box too small?) VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May 28 2021 06:58:52) Included patches: 1-2891
Logs and stack traces
No response
cc @bounceme as the maintainer?

It seems that GetJavascriptIndent() returns 0 on top-level code lines, and adapts to the indentation level of the code block otherwise.
My workaround:
Make a copy of indent/html.vim, find s:Alien3() in it and change
if b:hi_indent.scripttype == "javascript"
  " indent for further lines
  return eval(b:hi_js1indent) + GetJavascriptIndent()
else
  return -1
endif

to
if b:hi_indent.scripttype == "javascript"
  " indent for further lines
  if GetJavascriptIndent() == 0
    return eval(b:hi_js1indent)
  endif
  return GetJavascriptIndent()
else
  return -1
endif

I didn't look into this in depth so not sure if this would break certain things, but it works fine for me at least for now.


incompatibility with Ubuntu 14.04

From email 2016-03-16:
I am trying to install spinalcord toolbox in my system with OS "UBUNTU 14.04 LTS" and facing an error, "Failed to check the ANTs compatibility with OS ". Kindly see the attached screen shot & log file. I need your help in this regard.

Log file:
date
(0, 'Wed Mar 16 18:57:15 PKT 2016')
whoami
(0, 'sidra')
pwd
(0, '/home/sidra')
Check which OS is running...
.. linux (Linux-4.2.0-27-generic-x86_64-with-debian-jessie-sid)
Check number of CPU cores...
.. Available: 8
.. Used by SCT: 8
Check RAM...
MemTotal:       16339136 kB
total       used       free     shared    buffers     cached
Mem:         15956       5148      10807        242        133       3709
-/+ buffers/cache:       1306      14649
Swap:        16283          0      16283
Check which Python is running...
.. /home/sidra/miniconda2/bin/python
Check SCT path...
echo $SCT_DIR
.. /usr/local/sct2.2
Check SCT version...
.. 2.2
Check if scikit-image (0.11.3) is installed.........[OK]
Check if matplotlib (1.4.3) is installed............[OK]
Check if scipy (0.16.0) is installed................[OK]
Check if sympy (0.7.6) is installed.................[OK]
Check if numpy (1.9.2) is installed.................[OK]
Check if pandas (0.16.2) is installed...............[OK]
Check if nibabel (2.0.1) is installed...............[OK]
Check if ornlm is installed.........................[OK]
Check if dipy is installed..........................[OK]
Check ANTs compatibility with OS ...................[FAIL]
>> isct_antsRegistration
(512, '/usr/local/sct2.2/bin/isct_antsRegistration: 4: /usr/local/sct2.2/bin/isct_antsRegistration: Syntax error: ")" unexpected')

Check PropSeg compatibility with OS ................[OK]
(0, '\nsct_propseg\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nPart of the Spinal Cord Toolbox <https://sourceforge.net/projects/spinalcordtoolbox>\nVersion: 2.2\n\n\nDESCRIPTION\nThis program segments automatically the spinal cord on T1- and T2-weighted images, for any field of \nview. You must provide the type of contrast, the image as well as the output folder path.\n  Initialization is provided by a spinal cord detection module based on the elliptical Hough \n    transform on multiple axial slices. The result of the detection is available as a PNG image us\n    ing option -detection-display.\n  Parameters of the spinal cord detection are :\n   - the position (in inferior-superior direction) of the initialization\n   - the number of axial slices\n   - the gap (in pixel) between two axial slices\n   - the approximate radius of the spinal cord\n  \n  Primary output is the binary mask of the spinal cord segmentation. This method must provide VTK \n    triangular mesh of the segmentation (option -mesh). Spinal cord centerline is available as a bin\n    ary image (-centerline-binary) or a text file with coordinates in world refe\n    rential (-centerline-coord).\n  Cross-sectional areas along the spinal cord can be available (-cross).\n  Several tips on segmentation correction can be found on the "Correction Tips" page of the \n    documentation while advices on parameters adjustments can be found on the "Parameters" page.\n  If the segmentation fails at some location (e.g. due to poor contrast between spinal cord and \n    CSF), edit your anatomical image (e.g. with fslview) and manually enhance the contrast by add\n    ing bright values around the spinal cord for T2-weighted images (dark values for T1-weighted)\n    . Then, launch the segmentation again.\n\nUSAGE\nsct_propseg -i <image_nifti> -c {t1,t2}\n\n\nMANDATORY ARGUMENTS\n  -i <image_nifti>            input image.                  \n  -c {t1,t2}                  type of image contrast, t2: cord dark / CSF bright ; t1: cord bright \n                              / CSF dark\n\n\nOPTIONAL ARGUMENTS\nGeneral options\n  -ofolder <folder_creation>  output folder.                \n  -down <int>                 down limit of the propagation, default is 0\n  -up <int>                   up limit of the propagation, default is the highest slice of the \n                              image\n  -v {0,1}                    1: display on, 0: display off (default) Default value = 1\n  -h                          display this help             \n\nOutput options\n  -mesh                       output: mesh of the spinal cord segmentation\n  -centerline-binary          output: centerline as a binary image \n  -CSF                        output: CSF segmentation      \n  -centerline-coord           output: centerline in world coordinates\n  -cross                      output: cross-sectional areas \n  -init-tube                  output: initial tubular meshes \n  -low-resolution-mesh        output: low-resolution mesh   \n  -detect-nii                 output: spinal cord detection as a nifti image\n  -detect-png                 output: spinal cord detection as a PNG image\n\nOptions helping the segmentation\n  -init-centerline <image_nifti>filename of centerline to use for the propagation, format .txt or \n                              .nii, see file structure in documentation\n  -init <float>               axial slice where the propagation starts, default is middle axial \n                              slice\n  -init-mask <image_nifti>    mask containing three center of the spinal cord, used to initiate the \n                              propagation\n  -radius <float>             approximate radius of the spinal cord, default is 4 mm\n  -detect-n <int>             number of axial slices computed in the detection process, default is \n                              4\n  -detect-gap <int>           gap in Z direction for the detection process, default is 4\n  -init-validation            enable validation on spinal cord detection based on discriminant \n                              analysis\n  -nbiter <int>               stop condition: number of iteration for the propagation for both \n                              direction, default is 200\n  -max-area <float>           [mm^2], stop condition: maximum cross-sectional area, default is 120 \n                              mm^2\n  -max-deformation <float>    [mm], stop condition: maximum deformation per iteration, default is \n                              2.5 mm\n  -min-contrast <float>       [intensity value], stop condition: minimum local SC/CSF contrast, \n                              default is 50\n  -d <float>                  trade-off between distance of most promising point and feature \n                              strength, default depend on the contrast. Range of values from 0 to \n                              50. 15-25 values show good results.\n\n\nEXAMPLE\nsct_propseg -i t2.nii.gz -t t1 -c t1 -ofolder My_Output_Folder/ -v 0\n')

Tested commit: 8c6e636b7f131ff5ae9e5e8d63ffaba35966f36b
on VM Ubuntu 14.04.4.
All tests passed:
Run sct_check_dependencies...
SpinalCord Toolbox version 2.2_dev
SCT installed in /home/osboxes/sct
PYTHON /home/osboxes/sct/python/bin/python /home/osboxes/sct/python /home/osboxes/sct
running /home/osboxes/sct/scripts/sct_check_dependencies.py

Check which OS is running...
.. linux (Linux-4.2.0-27-generic-x86_64-with-debian-jessie-sid)
Check number of CPU cores...
.. Available: 1
.. Used by SCT: 1
Check RAM...
MemTotal:        4047400 kB
total       used       free     shared    buffers     cached
Mem:          3952       3202        750         17         67       2333
-/+ buffers/cache:        801       3150
Swap:         3452          0       3452
Check which Python is running...
.. /home/osboxes/sct/python/bin/python
Check SCT path...
.. /home/osboxes/sct
Check SCT version...
.. 2.2_dev
Check if scikit-image (0.11.3) is installed.........[OK]
Check if matplotlib (1.5.1) is installed............[OK]
Check if scipy (0.17.0) is installed................[OK]
Check if sympy (0.7.6) is installed.................[OK]
Check if numpy (1.10.4) is installed................[OK]
Check if pandas (0.16.2) is installed...............[OK]
Check if nibabel (2.0.2) is installed...............[OK]
Check if ornlm is installed.........................[OK]
Check if dipy is installed..........................[OK]
Check ANTs compatibility with OS ...................[OK]
Check PropSeg compatibility with OS ................[OK]

INSTALLATION DONE!

 This may take a moment.
  warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.')
[OK]
Checking test_sct_smooth_spinalcord.................[OK]
Checking test_sct_straighten_spinalcord.............[OK]
Checking test_sct_warp_template.....................[OK]
Checking test_sct_documentation.....................[OK]
Checking test_sct_dmri_create_noisemask.............[OK]
status: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Finished! Elapsed time: 222s

Remove temporary files...
rm -rf tmp.160320125419/
0

Installing SCT_beta from scratch:
sudo apt-get install curl
sudo apt-get install git
git clone --depth=1 --branch=master https://github.com/neuropoly/spinalcordtoolbox.git sct
cd sct/
yes | ./install_sct
source ~/.bashrc
cd
sct_testing

related to issue #711


numpy.diff fails on datetime64[ns] array

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

The following code can't compile:
import numba
import numpy as np

@numba.jit(nopython=True, nogil=True)
def bug(times: np.ndarray):
  return np.diff(times)

bug(np.array([np.datetime64('2023-08-01T12:00:00'), np.datetime64('2023-08-01T12:00:01')]))

The error message is:
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<function diff at 0x1041ff420>) found for signature:

 >>> diff(array(datetime64[ns], 1d, C))

There are 2 candidate implementations:
   - Of which 2 did not match due to:
   Overload in function 'np_diff_impl': File: numba/np/arraymath.py: Line 3508.
     With argument(s): '(array(datetime64[ns], 1d, C))':
    Rejected as the implementation raised a specific error:
      TypingError: Failed in nopython mode pipeline (step: nopython frontend)
    No implementation of function Function(<built-in function setitem>) found for signature:

     >>> setitem(array(datetime64[ns], 1d, C), int64, timedelta64[ns])

    There are 16 candidate implementations:
          - Of which 16 did not match due to:
          Overload of function 'setitem': File: <numerous>: Line N/A.
            With argument(s): '(array(datetime64[ns], 1d, C), int64, timedelta64[ns])':
           No match.

    During: typing of setitem at /Users/samuelhapak/Library/Caches/pypoetry/virtualenvs/wutils-MifiL3zq-py3.11/lib/python3.11/site-packages/numba/np/arraymath.py (3534)

    File "../../../Library/Caches/pypoetry/virtualenvs/wutils-MifiL3zq-py3.11/lib/python3.11/site-packages/numba/np/arraymath.py", line 3534:
        def diff_impl(a, n=1):
            <source elided>
                for i in range(size - 1):
                    work[i] = a2[major, i + 1] - a2[major, i]
                    ^

  raised from /Users/samuelhapak/Library/Caches/pypoetry/virtualenvs/wutils-MifiL3zq-py3.11/lib/python3.11/site-packages/numba/core/typeinfer.py:1086

Looking at the implementation here
the issue seems to be creating the empty array of type datetime64[ns] whereas the correct type should be timedelta64[ns].
This is wrong in this particular case because unlike most of the types, difference of two datetime64[ns] is of type timedelta64[ns].

Executing the code doesn't reproduce the issue because it doesn't lead to compilation. I don't know much about datetimes, so can you please suggest a line of code that calls bug() to reproduce the exact error?

@gmarkall sure, I added it to description. It's essentially this line:
bug(np.array([np.datetime64('2023-08-01T12:00:00'), np.datetime64('2023-08-01T12:00:01')]))

@gmarkall I don't really think that this is an appropriate comparison.
I completely understand why you would hesitate supporting overriding data in array of type A with data of type B. But, this is not the case. The numpy.diff function is supposed to create new array.
I also think that the fix should be relatively straightforward. All that's needed is to have a special case where a.dtype is datetime handled by creating output array of type timedelta.
I am not versed in writing numba, but this seems to me like something that shouldn't be that hard to achieve?

(to provide a little more context, the exception message is telling us that this is the problem:
   Overload in function 'np_diff_impl': File: numba/np/arraymath.py: Line 3508.
     With argument(s): '(array(datetime64[ns], 1d, C))':
    Rejected as the implementation raised a specific error:
      TypingError: Failed in nopython mode pipeline (step: nopython frontend)
    No implementation of function Function(<built-in function setitem>) found for signature:

     >>> setitem(array(datetime64[ns], 1d, C), int64, timedelta64[ns])

)


Multiple Syntax Errors and Unknown Option Errors for seemingly valid syntax/options

I am getting multiple syntax errors and unknown option errors for the Earthfiles in this repo:
https://github.com/input-output-hk/catalyst-voices
catalyst_voices/Earthfile
Syntax Errors on Lines 20,21:
    LET gen_code_path  = lib/generated/catalyst_gateway
    LET local_gen_code_path = packages/catalyst_voices_services/lib/generated/catalyst_gateway/

catalyst_voices/test_driver/Earthfile Lines 10,12, 16:
    LET driver_port = 4444

    IF [ $browser = "chrome" ]
        LET driver = "chromedriver"
    END

    IF [ $browser = "firefox" ]
        LET driver = "geckodriver"
    END

catalyst-gateway-crates/c509-certificate/Earthfile Line 35:
#     SAVE ARTIFACT c509-certificate-binding AS LOCAL ./pkg

catalyst-gateway/event-db/Earthfile Line 41, Unknown Option:
        SAVE IMAGE --push --insecure $local_registry/event-db:latest

docs/Earthfile Line 51, Unknown Option:
        SAVE IMAGE --push --insecure $local_registry/cat-voices-docs:latest

These last two, the option it complains about is --insecure which is a valid option. See: https://docs.earthly.dev/docs/guides/configuring-registries/self-signed#insecure-registries

Is this language server still maintained?

Is this language server still maintained?

yes, I had to take a break but will be back to it next week. Contributions are more than welcome :-)


QA: Test Node Uptime Calculation Fix

We need to address the inaccurate calculation of node uptimes in our current system. This ticket covers the testing of the fix proposed by @Bob Stevens in PR #414 (follow up of https://github.com/masa-finance/masa-oracle/issues/413)
Objective:
Verify that the Implementation of an accurate node uptime calculation system is working across the network.
Tasks

[ ] Plan for resetting the entire network's nodeData

Determine the optimal time for the reset
Create a backup of the current nodeData for reference
Develop a script or process for the reset

[ ]  Coordinate with the team (@Ettore Di Giacinto, @John Durkin, @JDutchak, @Bob Stevens) for live testing in the test environment

Schedule a team meeting to discuss the testing process
Assign roles and responsibilities for the test
Prepare a test plan with specific scenarios to verify

[x] https://github.com/masa-finance/roadmap/issues/67
[ ] Conduct thorough testing of the new uptime calculation

Test various scenarios (node joining, leaving, rejoining)
Verify accuracy of uptime calculations over different time periods
Check for any regression in related functionalities

[ ]  Monitor the network post-implementation for any anomalies
[ ]  Document the changes and update any relevant documentation

Key Changes from PR #414:

[ ] Revised UpdateAccumulatedUptime function for more accurate calculations
[ ] Improved handling of node status changes (ActivityLeft, ActivityJoined)
[ ] Prevention of uptime inflation and overestimation

Acceptance Criteria:

[ ] PR #414 is reviewed, approved, and merged
[ ] The entire network's nodeData has been successfully reset
[ ] Live testing in the test environment is completed without major issues
[ ] Uptime calculations are verified to be accurate across various scenarios
[ ] No regression in related system functionalities is observed
[ ] Team consensus that the fix is working as intended

not relevant anymore, we will get back at this one if we are still seeing issues with it. Too many changes went in the code and now things works very much different since this card was opened up


comby doesn't work correctly with a single quote in haskell

Describe the bug
A single quote in Haskell can be used not only as a delimeter for Char (e.g. "asdf" == ['a','s','d','f']) but also as a part of an identifier (e.g. s = 1; s' = s + 1). It seems that the current haskell matcher can't tell the second case from the first.
Reproducing

Works as intended with a simple example: here.
Doesn't match if there is a single quote in an identifier somewhere prior: here.
Matches again if a closing quote is added (thus restoring "quote balance"): here.

Expected behavior
To match hello in the second example.

Hey, thanks for the note. You're right, the matcher is too strict here, expecting ' to be balanced. I've made it less strict.

This is fixed, but not released yet. I'll release an updated version today.

@rvantonder I've seen you just released the new version, is there a change log somewhere?

Hey @s0kil I was just writing it up and editing the release notes--I should probably have done that before publishing :-) Check out https://github.com/comby-tools/comby/releases/tag/1.1.0


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
a575d34 -> 55c4c41

terraform-ibm-modules/common-pipeline-assets
action
minor
v1.17.9 -> v1.18.1

Release Notes

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.18.1
Compare Source
Bug Fixes

install dependencies before running pre-commit stage (#566) (97afd7d)

v1.18.0
Compare Source
Features

added the ability pass tfswitchDir (#565) (d492025)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 3.9.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Error while creating big sized Modin DataFrame

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
AWS instance: c5.18xlarge
Modin version (modin.__version__): 0.8.2
Python version: 3.7
Code we can use to reproduce:

import argparse
parser = argparse.ArgumentParser()
parser.add_argument('-r', metavar='n', help='ray init', type=int, default=0)
args = parser.parse_args()`

if args.r==1:
    import ray
    ray.init(num_cpus=36)
    print(ray.nodes())

import modin.pandas as pd
import daal4py as d4p
from daal4py.sklearn import patch_sklearn
patch_sklearn()

import numpy as np
from sklearn.decomposition import PCA
from sklearn.datasets import make_classification

X = pd.DataFrame(make_classification(n_samples=10000000, n_features=280)) # error

algo = d4p.normalization_zscore(doScale=True)
X = algo.compute(X).normalizedData

pca = PCA(n_components=2, svd_solver='daal')
Xt = pca.fit_transform(X)

if args.r==1:
    ray.shutdown()

To reproduce use conda envs, install modin from pip and run python file.py

Describe the problem

At this instance we have error while creating DataFrame. It was noticed first with using read_csv() for reading dataset with similar shape. This error wasn't reproduced on other machines. If we manage ray processes manually(python file.py -r 1) this error wasn't reproduced too.
Source code / logs

Intel(R) Data Analytics Acceleration Library (Intel(R) DAAL) solvers for sklearn enabled: https://in                                                                                telpython.github.io/daal4py/sklearn.html

UserWarning: Distributing <class 'tuple'> object. This may take some time.
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1605601119" if you are using GNU date ***
PC: @                0x0 (unknown)
*** SIGBUS (@0x7f94fbf76fe0) received by PID 4659 (TID 0x7f91f5e69700) from PID<PHONE_NUMBER>3641881568                                                                                ; stack trace: ***
    @     0x7fa70a2b33c0 (unknown)
    @     0x7fa70a23a877 (unknown)
    @     0x7fa6eed3f421 execute_native_thread_routine_compat
    @     0x7fa70a2a7609 start_thread
    @     0x7fa70a1ce103 clone
Bus error (core dumped)

Hi @KalyanovD, thanks for posting! I think DataFrame, which you want to create, is not able to fit in memory of your machine. If it is, you should consider out of core feature in Modin (please, look at here). If it is not, please let us know. Also, when creating DataFrame with the way you use, I get the following the message (VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray). Thus, you need to consider a recommendation from that message.

Hi @KalyanovD , piggy backing off what @YarShev , could you give some details on what machines this wasn't reproduced on? Did those machines have more memory? I'm going to go ahead and close this issue since the thread has gone stale, but please re-open if the issue still persists.


[#74] Add (beta) CI Pipeline interface: live view-only

Updates every 5 seconds and displays how long jobs are running. With colors!

Last thing here is identify a certain pesky unhandled panic that seems to happen when a pipeline exists but isn't "ready" usually retrying the command works, but by that time we've already borked your terminal


Add in depth search feature.

Currently we can only search on same level which is tiring.

Will be done after merging #18


Is there a roadmap?

It's mentioned in the README:

It is still very much a work in progress. I have a large list of features I still want to add and some features are only partially implemented. Use at your own risk.

Is there a roadmap that we can contribute to? Perhaps some of the ideas can be listed on the repo's project board?

Hi Patrick, sorry for the delay responding.  I haven't really worked on this in quite a while now as I no longer use it as much as I was when I made it.  Basically I switched jobs and I can't run Hammerspoon on my new work laptop due to company restrictions and automating work tasks was the primary reason I created it.  I may go back to working on it at some point but can't make any promises.


[TEP 0075, 0076] More ways of referencing params and results

Feature request
There are certain ways of referencing params and results, either as a whole or accessing keys, are implemented and tracked in #4723, but there are other ways that should be considered for accessing params and results.
Thanks for @chuangw6 and @Yongxuanzhang 's summary, a few other ways are listed below that are not supported but should be considerred:

String Types

$(tasks.myTask.results.myStringResult)
$(tasks.myTask.results.myStringResult)
$(tasks.myTask.results[‘my.String.Result’])

Array Types

$(tasks.myTask.results.myArrayResult[*])
$(tasks.myTask.results[‘myArrayResult’][*])
$(tasks.myTask.results[“myArrayResult”][*])
$(tasks.myTask.results.myArrayResult[i])
$(tasks.myTask.results[‘myArrayResult’][i])
$(tasks.myTask.results[“myArrayResult”][i])

Object Types

$(tasks.myTask.results.myObjectResult[*])
$(tasks.myTask.results.myObjectResult.key1)
$(tasks.myTask.results[“my.Object.Result”][*])
$(tasks.myTask.results[“my.Object.Result”].key1)
$(tasks.myTask.results[“my.Object.Result”][“my.key1”])

Use case
Stated above.

$(tasks.myTask.results[“my.Object.Result”].key1)
$(tasks.myTask.results[“my.Object.Result”][“my.key1”])

Object param/result name and its keys shouldn't contain dots. see more details here


ttt-utils:0.1.2

I am submitting

[x] an update for a package

Description: Fixed some minor errors and refactored some functions

Thanks!


Update dependency matrix-project to v785

This PR contains the following updates:

Package
Update
Change

matrix-project
major
772.v494f19991984 -> 785.v06b_7f47b_c631

Release Notes

jenkinsci/matrix-project-plugin
v785.v06b_7f47b_c631
Compare Source

👷 Changes for plugin developers

Remove disable checkbox (#104) @janfaracik

👻 Maintenance

chore: use jenkins infra maven cd reusable workflow (#108) @jetersen
Remove java 8 from CI (#118) @timja

Configuration
📅 Schedule: "after 5:00 am before 11:00 am" in timezone utc.
🚦 Automerge: Disabled due to failing status checks.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

Branch has one or more failed status checks


Added ALIKED+LightGlue

Added support for aliked and lightglue
(removed duplicate dust3r entry in readme)

Thanks for your PR. Please format and correct the code using the command at the top directory.
bash format.sh


This dependency was not found:  mux.js/lib/mp4/caption-parser

This dependency was not found:

mux.js/lib/mp4/caption-parser in ./node_modules/videojs-flash/node_modules/video.js/dist/video.es.js

To install it, you can run: npm install --save mux.js/lib/mp4/caption-parser
In my develop enviroment, if I use "yarn  intsall" command, this error always happen.  but if i use "npm install", this file will exist.  Recently, in my production enviroment(use jenkins), it is "npm install", this error happens too.

@Anne3720 did you find any solution about your issue ?


Add specification for set connector sync job error

This PR adds a specification to align with https://www.elastic.co/guide/en/elasticsearch/reference/master/set-connector-sync-job-error-api.html

💚 All backports created successfully

Status
Branch
Result

✅
8.17

Questions ?
Please refer to the Backport tool documentation


feat: add dashmap support

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
Refer to the moka and memory implementations.
Tests failure is encountered when the environment variable OPENDAL_DASHMAP_TEST=on
---- services_dashmap_list::test_list_dir stdout ----
Error: Unsupported (persistent) at scan, context: { called: kv::Adapter::scan, service: dashmap, path: / } => kv adapter doesn't support this operation

failures:
    services_dashmap_list::test_check
    services_dashmap_list::test_list_dir
    services_dashmap_list::test_list_dir_metadata_cache
    services_dashmap_list::test_list_empty_dir
    services_dashmap_list::test_list_nested_dir
    services_dashmap_list::test_list_non_exist_dir
    services_dashmap_list::test_list_rich_dir
    services_dashmap_list::test_list_sub_dir
    services_dashmap_list::test_remove_all
    services_dashmap_list::test_scan

Please also update the readme~

My bad, no support for scan at the moment, remove AccessorCapability::Scan

Great PR!


fix: remove legacy template

Description
Removes legacy Jekyll templating

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


CamelCase elements always nil

If an element is CamelCased, its content always evaluates to nil:
pry(main)> foo = HappyMapper.parse("<foo><MessageId>f3a16e4c-b812-4934-a009-742ac51668b5</MessageId></foo>")
=> #<#<Class:0x00000002945e60>:0x000000029448d0 @message_id=nil>
pry(main)> foo.message_id
=> nil

Renaming the elements to lowercase yields correct content but since my input will always be camelcased, that's not an option.

If you need a work around until this is fixed: explicitly set the tag name:
class Foo
  include HappyMapper

  tag 'foo'
  has_one :message_id, String, tag: 'MessageId'
end

Foo.parse "<foo><MessageId>f3a16e4c-b812-4934-a009-742ac51668b5</MessageId></foo>"
#=> <Foo:0x007fc774211798 @message_id="f3a16e4c-b812-4934-a009-742ac51668b5">

Thanks you for the hint. I had hoped to not need classes for every case, but I'll give it a try!


docs: Add raw query param to resource image from README

Signed-off-by: mendesbarreto<EMAIL_ADDRESS>This PR closes #135
Changes:

[x] Add query param to github resrouce imsage message.png
[x] Fomart README.md file following the markdown good practices (additional white spaces, indentation e etc.)

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

Thank you for your contribution. Please join our slack community if you haven't already. This solved issue gives you + 1 point in the event :)


Update total upload size limit for records for harms

As a ministry coordinator
I want the system to stop  the upload of records for a request that in total are 2GB or more
so that do not upload records only to find that I cannot download the Harms later

Assumptions & Scope
Gathering Records feature does not handle large files (2GB or greater). The processing of records follow these steps:

Removal of duplicates
Conversion to PDF
Stitch PDF into consolidated PDF for each division tagged
Zip PDF(s) and incompatible files into a ZIP file for download onto the user's desktop

Currently, the Gathering Records file cannot support the create of ZIP files that are greater than 2 GB.
As a result, we need to stop the user from uploading records packages that are greater than 2GB, and instead redirect them to use the current process (i.e. LAN, Intella).
What is IN scope?

Capturing the size of a records package in the DB for the request.
Blocking the upload of a batch of records that exceeds the 2GB limit
Blocking the upload of a batch when the batch about to be uploaded, and a previous batch(es) uploaded, exceed the 2GB limit.

DOD

[x] Limit the total upload size for records to 2 GB.
[x] Create a new env variable for configuring the total size limit.
[x] Avoid duplicate files while calculating the total file size already uploaded.
[x] Add an error message on the modal once limit exceeds - Need wording.

Deployment Steps

set REACT_APP_TOTAL_RECORDS_UPLOAD_LIMIT env config for web

What is NOT in scope?
Acceptance Criteria
Scenario 1: Batch limit of 2GB exceeded

GIVEN the user is on the upload records modal
AND the user select 1 (1 tag maximum) tag for the new uploads: Division A, Division B, etc.
AND the user has uploaded file(s)
WHEN the total file size of the batch is  greater than 2GB
THEN a warning will show "A maximum 2GB or records can be uploaded per request. Please load the records for this request onto the LAN and notify IAO by updating the request state to Deduplication and posting a comment in the request."
AND the 'Continue' button will be disabled.

Scenario 2: Request record limit of 2GB exceeded

GIVEN the user is on the upload records modal
AND the user select 1 (1 tag maximum) tag for the new uploads: Division A, Division B, etc.
AND other batches for the request have already been uploaded
AND the user has uploaded file(s)
WHEN the total file size of the batch and previous batches is greater than 2GB
THEN a warning will show "A maximum 2GB or records can be uploaded per request. Please load the records for this request onto the LAN and notify IAO by updating the request state to Deduplication and posting a comment in the request."
AND the 'Continue' button will be disabled.

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/831805474
Click on 2nd Request ID from the top to see expected view on hover
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

@m-prodan @lmullane Can you update the error message to be shown on Frontend?

Total Limit & Already uploaded record size design :

Working as expected

@aparna-aot There was an issue if we try to upload a small file and a large file. Then system removes the large files(since it exceeds the 2 Gb limit), but user is unable to proceed with small file

small issue with showing the uploading limit as @Gb and allowing more files in the attachment modal   will test after @aparna-aot fixing that

Needs to mention that some times after file conversion total size goes beyond 2 GB(like .0001GB ), but it wont allow user to add more files later. So closing the ticket. @m-prodan @lmullane


KOGITO-7211: KN CLI workflow plugin

JIRA
https://issues.redhat.com/browse/KOGITO-7211
On this PR
Adds the new kn-plugin-workflow package.
About
This package is a plugin for the Knative CLI. It adds the workflow subcommand, resposible to create, build and deploy workflow projects built in Quarkus.
Read more about Knative plugins here.
Commands
All commands have the --help and --verbose option.

create
kn workflow create
Create a Quarkus workflow project with the following extensions:

kogito-quarkus-serverless-workflow
kogito-addons-quarkus-knative-eventing
resteasy-reactive-jackson
quarkus-kubernetes

Also creates a "hello world" workflow file in the .//src/main/resources folder.

build
kn workflow build
Builds a Quarkus workflow project and generates a container image

deploy
kn workflow deploy
Deploys a previous built Quarkus workflow project using the .//target/kubenertes deployment files.

Demo
https://drive.google.com/file/d/1ya9QebSSAq3GbdcVSa0B6dliRxswwrTS/view?usp=sharing

Hi @spolti, I've added you as a reviewer. I guess you could give some insightful feedback.

@ricardozanini @spolti  Thanks a lot for your effort in reviewing this PR. I believe I've made all the requested changes and answered your questions. If I missed something, let me know.
Also, I've added Podman support with the following command:
kn workflow build --jib-podman
@spolti I've created a JIRA to work as an enhancement in the near future regarding the logging library.
@ricardozanini I believe this README is the first version of the documentation and is something to improve before adding it to the kogito-docs, so I've created a JIRA for it, but if you prefer I can send a PR with the installation steps the way it is.

@ricardozanini I believe this README is the first version of the documentation and is something to improve before adding it to the kogito-docs, so I've created a JIRA for it, but if you prefer I can send a PR with the installation steps the way it is.

@ljmotta the kn CLI is a hard requirement for DP1. Therefore, it would be nice to have the guide as soon as possible. I think the README info we have here is enough for now. Open the PR, I'll add a few people there that will have the final say.

@ljmotta @ederign just to reinforce, my comment is not a blocker. We can open a PR later linking the guide in the README. My only concern is to not keep the same information in two places.


Enable customizing the linkage of a platform's C runtime

Enable the compiler to select whether a target dynamically or statically links
to a platform's standard C runtime through the introduction of three orthogonal
and otherwise general purpose features, one of which will likely never become
stable and can be considered an implementation detail of std. These features do
not require the compiler or language to have intrinsic knowledge of the
existence of C runtimes.
The end result is that rustc will be able to reuse its existing standard library binaries for the MSVC and musl targets to build code that links either statically or dynamically to libc.
The design herein additionally paves the way for improved support for dllimport/dllexport, and cpu-specific features, particularly when combined with a std-aware cargo.
Rendered

cc @vadimcn @retep998
cc @Ericson2314 this has some small implications for std-aware cargo

@aturon this is strongly related to your irlo post about arch/plattform-specific configuration.

cc @japaric @KennethAdamMiller @zhangyt26 a way forward on musl dynamic linking

Another alternative would be to separate libstd into two crates: one of which is just a stub which calls out to the actual CRT. Instead of recompiling the whole of libstd, you just link with a different stub.

How would this interact with RFC #1717?
If we have these annotations,
#[link(name = "msvcrt", kind="dylib", cfg(not(target_feature = "crt-static")))]
#[link(name = "libcmt", kind="static-nobundle", cfg(target_feature = "crt-static"))]

how do we decide whether to emit dllimport's on symbols?   Using the default state of that target feature?

@vadimcn ah this was intended to clarify that:

When dllimport or dllexport needs to be applied, it will evaluate the final compilation unit's #[cfg] directives and see if upstream #[link] directives apply or not.

Which is to say that when dllexport/dllimport need to be appplied, the #[link] annotations are resolved with their cfg.
Note, though, that this is not intended to be a general purpose mechanism. It's the unstable feature of this RFC which is never intended to become stable. It does't affect liblibc at all as well because the extern block the #[link] annotations decorate has 0 bindings.

Well this satisfies my requirements of getting libc to not depend on msvcrt.lib when I want libcmt.lib instead, as well as informing build scripts and downstream crates of how the CRT is being linked so they can change what they do accordingly. So this seems like it'll work.
However, it is worth paying attention to how this feature could be extended for other options in the future.
For example choosing which winapi family you are targeting, with mutually exclusive options such as WINAPI_FAMILY_DESKTOP_APP and WINAPI_FAMILY_PC_APP that affect which functions are available to you. In particular std would have to change which functions it relies on, which means it would have to be recompiled. This would also affect which system libraries are linked to.
Another option might be the minimum version of Windows that needs to be supported, which affects which functions can be directly linked to and adding fallback code paths for certain functionality. Libstd could handle this by always supporting the lowest version possible, but if it could be recompiled it could take advantage of higher minimum version requirements to strip out code branches for older versions.

I'll have much more to say, but can't cfg_attr be used with link? :)

When dllimport or dllexport needs to be applied, it will evaluate the final compilation unit's #[cfg] directives and see if upstream #[link] directives apply or not.

Okay, so all upstream crates should also be compiled with the same target-feature flag?

I think #1711 ought to be a blocker for this. Once we start passing this stuff to build scripts we will have to be much more careful about stability..

I'll have much more to say, but can't cfg_attr be used with link? :)

I believe the idea is that this new link cfg syntax is specifically for lazy cfg evaluation. It will be evaluated at the point of linking, so the upstream crate doesn't need to know what the target-feature flag is when it was compiled, rustc will store both of those attributes with their respective cfgs and evaluate it later when linking. cfg_attr would be evaluated immediately and so would be unusable for libstd as at the time of building libstd it doesn't know how you want the crt to be linked yet.

Okay, so all upstream crates should also be compiled with the same target-feature flag?

There's no way dllimport/dllexport can be applied lazily unless you forbid translation of any function that calls extern symbols from such a lazy cfg'd link block until the final compilation unit where linking will occur.
Actually, @alexcrichton , how does this interact with dylibs? You need to know which CRT you are linking every time you are linking, and when making a Rust dylib, you are still linking stuff so you need to know which CRT to use. If statically linking the CRT in a given dylib, that means it has its own copy of the CRT which is fundamentally unique from all other dylibs. What happens if code works with a CRT object in a Rust dylib which statically linked the CRT, but that function is then inlined or monomorphized into a different dylib?

CC @eternaleye, you're probably interested.

There's no way dllimport/dllexport can be applied lazily unless you forbid translation of any function that calls extern symbols from such a lazy cfg'd link block until the final compilation unit where linking will occur.

Exactly.  But I think @alexcrichton meant that for exact dllimport targetting all upstream crates would be compiled with the same target-feature flag.
Of course, this doesn't help with crates that Rust ships in a binary form, so we'll still have to rely on linker to fix things up.

What happens if code works with a CRT object in a Rust dylib which statically linked the CRT, but that function is then inlined or monomorphized into a different dylib?

I believe the CRT symbols will be resolved to the other crate's CRT.  Which isn't necessarily a problem if they are all stateless functions.

I believe the CRT symbols will be resolved to the other crate's CRT. Which isn't necessarily a problem if they are all stateless functions.

Fortunately in the case of libstd it is all stateless functions. However anyone who uses CRT state in their own Rust crates has to be keenly aware that if someone uses the static CRT with their crate, it will completely screw up their code.

@vadimcn

Okay, so all upstream crates should also be compiled with the same target-feature flag?

Indeed! This is already the case with Cargo, and the only exception is the standard library. This "happens to work" today, however. The same standard library can be linked both dynamically and statically to the CRT. Eventually, though, Cargo custom-compiling std will enable us to easily recompile std with the right options as well, so today is just a temporary stopgap.

Of course, this doesn't help with crates that Rust ships in a binary form, so we'll still have to rely on linker to fix things up.

To be clear, libstd, the binary we're shipping, barely uses the CRT. The amount of "fixing up" here should be vanishingly small and not matter in practice. What little perf we're losing we can regain once we can recompile std on demand.
The real meat of the problem here is downstream code which is likely linking in lots of C code using the CRT. That's what's fixed by this RFC, however.
@Ericson2314

I think #1711 ought to be a blocker for this.

I disagree. Custom target specifications will continue to be as unstable/stable as they've always been, and this isn't adding any extra layers to that. They'll have the ability to say whether they recognize a target feature of the name "crt-static", but otherwise I don't see any need to block one decision on another.
@retep998

Actually, @alexcrichton , how does this interact with dylibs?

My plan is to punt on this entirely. Virtually no one uses rust dylibs linking to other rust dylibs, so designing in a large solution here seems onerous. The support in the RFC will still stand, and it's basically the case where if you dive too far into misconfiguration you'll get weird errors rather than the compiler giving you a nicer message about what happened.
As a result this question is mostly just theoretical. In the compiler we'll do something and make sure we're consistent with the binaries we distribute, and that's basically the only time this problem will arise.

@alexcrichton:

Virtually no one uses rust dylibs linking to other rust dylibs

Just to pipe up here: As a distro packager, I really really want to. The utter lack of tooling support for it may very well be a far larger contributor than lack of interest.

@eternaleye You are aware that Rust dylibs don't allow you to replace them with a new version right? Rust can and will inline/monomorphize many functions which means they won't be loaded from the dylib but will in fact be statically linked in. The only thing that is never inlined is statics themselves which stay in the same dylib they were defined in to provide a single source of truth for them, and that is more useful for plugins, not for distros.

@retep998: The goal here is not replacement, it's a combination of sharing and dependence.
In particular, if a CVE is found in a specific version of a Rust crate, uninstalling that crate with the system PM "breaking" everything that has depends on it (at least, depends on it in a way the PM is unaware of - if it is aware, it can rebuild against a newer, parallel-installed version of the affected crate) is, in fact, better than them silently continuing to work (static linkage).

@eternaleye So dylibs are useful for cases where the package manager is incapable of realizing one of the packages was built against a dependency which has been pulled somehow?

As long as packages are written by humans, and can't be 100% generated perfectly, there will be underspecified dependencies. Planning to handle those cases is just good engineering.
And due to "#[link]", Cargo.toml can underspecify dependencies.

@eternaleye

Just to pipe up here: As a distro packager, I really really want to.

Yeah I can understand your feeling here about how it's becoming a self-fulfilling prophecy. But frankly spending hours of time figuring out precisely how this feature works with dylibs will have no practical effect on this situation. To have this state of affairs change it would require a champion to take charge and push dylibs all the way to the finish line. Spot-checking tiny instances to make sure small pieces work won't ever get us to the point where they're generally usable.
As a result I'd still prefer to continue punting on this specific RFC, and the details of dylibs can be fleshed out later if need be. The details here are intended to be vague enough that we can tweak the implementation as needed for future changes.

@alexcrichton

I disagree. Custom target specifications will continue to be as unstable/stable as they've always been, and this isn't adding any extra layers to that. They'll have the ability to say whether they recognize a target feature of the name "crt-static", but otherwise I don't see any need to block one decision on another.

Well, glad to be wrong here! Looking back I see the RFC mentioned not sending the tokens to build scripts until stable?

target-feature=-crt-static is very misleading, the - before crt-static is too implicit to recognize (VS explicit literal 'crt-static'). I don't prefer things that 'I+love-you' means 'I love you', but 'I-love-you' means 'I hate you'.

@alexcrichton:

But frankly spending hours of time figuring out precisely how this feature works with dylibs will have no practical effect on this situation.

Well, crt-static isn't going to be default except on musl, is it? So it should be OK to say dylibs are not supported with crt-static except a handful of known-to-work cases like COM components. For any other cases, if one knows enough details of the linking, they might be able to make it work, anybody else should simply use dynamic runtime when they want to use dylibs.

@jan-hudec that sounds plausible to me!

For the distro case, I imagine if they want to dynamically link Rust dependencies, surely they would also want to dynamically link the C runtime as well, so I don't see crt-static having an affect on that situation. Simply don't use crt-static and it should work identically to how it does today.

@retep998, I was just saying COM is (probably most) common example of such C ABI (that carefully avoids sharing any CRT objects).

@rfcbot fcp merge
Discussion here seems to have reached a close but it seems to me that this may have agreement from stakeholders. I propose we merge!

I just had someone trying to get some Rust code to link against the debug CRT, so would this be easily extendable to that as well?

Yeah my guess is we could either infer that from -g or add a new -C target-feature for that

I'd rather not infer it from -g because using debug info with the normal non-debug CRT is a really common and standard thing to do.

@rfcbot reviewed

@rfcbot reviewed

Can we use something more explicit than cfg (e.g. lazy_cfg) for lazy linking that indicates that something special is going on here? Since the feature is going to stay unstable forever, it doesn't have to be as ergonomic as something more exposed to the end user.

@michaelwoerister sure yeah, I don't mind basically picking anything for that in the time being.

🔔 This RFC is now entering its week-long final comment period for merging :bell:

This isn't a concern, but to my knowledge nothing is blocking stdlib deps, and @japaric has done excellent work making std actually buildable by cargo in practice, so perhaps "Lazy link attributes" won't even need to be implemented?

Looks like no new concerns arose during FCP, so merging! Thanks again for the discussion everyone!


devpi-server: 5.1.0 -> 5.2.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/devpi-server/versions.
meta.description for devpi-server is: '"Github-style pypi index server and packaging meta tool"'.
meta.homepage for devpi-server is: '"http://doc.devpi.net"

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.2.0 with grep in /nix/store/ahbjx80mb38lpsn9i4s3rfz5lf5whmmw-devpi-server-5.2.0

directory tree listing: https://gist.github.com/66c114a31b112ba55d4bb42dec4c1b8f

du listing: https://gist.github.com/4f8de6323548100c0dc1e58eadbadaca

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
devpi-client
devpi-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ahbjx80mb38lpsn9i4s3rfz5lf5whmmw-devpi-server-5.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A devpi-server https://github.com/r-ryantm/nixpkgs/archive/dffa1afed3d1c3bc28f8a8f4bbbe6b83504744bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ahbjx80mb38lpsn9i4s3rfz5lf5whmmw-devpi-server-5.2.0
ls -la /nix/store/ahbjx80mb38lpsn9i4s3rfz5lf5whmmw-devpi-server-5.2.0/bin

cc @makefu for testing.

does that mean that devpi-client does not build anymore after this PR?
@GrahamcOfBorg build devpi-client devpi-server

devpi-client was broken to begin with

@jonringer I fixed devpi-client by rewriting the package and updating it to 5.0.0 with #70721 (25 days ago)

devpi-client should have been fixed by #72607.
And it builds for me on master

it was broken by a dependency bump, that package itself was fine

okay sounds good to me, let me test it real quick.


Cleanup old web3

Description
Now that the web3 refactor is complete, we should fix up all the naming and any remaining dangling references. This PR removes the web3 vuex module and the old composable files. Also cleaned up any dangling references to the old code.
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Other

How should this be tested?
Just give a general sense check to the app. Only names have changed here, and files.
Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code where relevant, particularly in hard-to-understand areas
[X] My changes generate no new console warnings
[X] The base of this PR is master if hotfix, develop if not

Thanks for this! Couple of things still need to be done I think:

Do a code search for .web3 and you'll see that there are still some references to the web3 vuex module.

Can we get rid of components/modals/AccountModal.vue?
Can we get rid of constants/connectors.json?


Assets are not loaded

Hi, after installing the plugin and restarted redmine, the assets files cannot be accessed.
The plugin appear in the activated plugins list in the configuration page

Did you follow the installation instructions to the point?
Did you run rake redmine:plugins:migrate RAILS_ENV=production from redmine root dir?
Can you make sure that after running this and restarting redmine, the assets are physically located in ${redmine_root}/public/plugin_assets/redmine_lightbox2/ and have the correct permissions to be accessible by your webserver?

Yes, i did it and restarted redmine
www-data@web01:~/redmine/plugins/redmine_lightbox/assets$ cd ~/redmine/
www-data@web01:~/redmine$ rake redmine:plugins:migrate RAILS_ENV=production
Migrating redmine_lightbox2 (Redmine Lightbox 2)...
www-data@web01:~/redmine$ ll plugins/redmine_lightbox/assets/*
plugins/redmine_lightbox/assets/images:
total 44
-rw-r--r-- 1 www-data www-data    43 août   6 17:10 blank.gif
-rw-r--r-- 1 www-data www-data 13984 août   6 17:10<EMAIL_ADDRESS>-rw-r--r-- 1 www-data www-data  6567 août   6 17:10 fancybox_loading.gif
-rw-r--r-- 1 www-data www-data  1003 août   6 17:10 fancybox_overlay.png
-rw-r--r-- 1 www-data www-data  6553 août   6 17:10<EMAIL_ADDRESS>-rw-r--r-- 1 www-data www-data  1362 août   6 17:10 fancybox_sprite.png

plugins/redmine_lightbox/assets/javascripts:
total 28
-rw-r--r-- 1 www-data www-data 23135 août   6 17:10 jquery.fancybox-2.1.5.pack.js
-rw-r--r-- 1 www-data www-data  2532 août   6 17:10 lightbox.js

plugins/redmine_lightbox/assets/stylesheets:
total 12
-rw-r--r-- 1 www-data www-data 4955 août   6 17:10 jquery.fancybox-2.1.5.css
-rw-r--r-- 1 www-data www-data  717 août   6 17:10 lightbox.css
www-data@web01:~/redmine$ sudo service apache2 restart
[ ok ] Restarting web server: apache2 ... waiting .

This is the wrong folder!
I said you have to make sure that the assets are loaded in THIS folder: ${redmine_root}/public/plugin_assets/redmine_lightbox2/
This is NOT the plugins folder, it's the public folder! This is where the plugin migration copies the assets to make them available to the public webfrontend.
Also I noted that your plugin is located in the wrong folder:

www-data@web01:~/redmine/plugins/redmine_lightbox/assets$ cd ~/redmine/

Please read the README once again to the point. There is written:

Clone or download this repo into your redmine_root/plugins/ folder

$ git clone https://github.com/paginagmbh/redmine_lightbox2.git

If you downloaded a tarball / zip from master branch, make sure you rename the extracted folder to redmine_lightbox2

But you downloaded, copied or cloned the plugin to a folder named redmine_lightbox - so this can never work!

If you rename this folder ~/redmine/plugins/redmine_lightbox to ~/redmine/plugins/redmine_lightbox2 and run the migration again, everything should be working fine!

Oh yes i made a mistake while renaming the plugin folder!
I could not clone the repos because my redmine version is too old for the latest plugin version.
So i manually downloaded the corresponding version but renamed redmine_lightbox instead of redmine_lightbox2.

No problem.
You could also have cloned the repo and then checked out the branch for Redmine 3.3 like so:
cd ~/redmine/plugins/
git clone https://github.com/paginagmbh/redmine_lightbox2.git
cd redmine_lightbox2
git checkout redmine-3.3
cd ../../
rake redmine:plugins:migrate RAILS_ENV=production

It's a better idea, I'll do that. Thank for the trick!


jq/gojq discrepancy in handling of "compile error"

For jq, {(0):1}is a compile-time error:
jq -n 'empty|{(0):1}'
jq: error: Cannot use number (0) as object key at <top-level>, line 1:
empty|{(0):1}
jq: 1 compile error

But for gojq:
$ gojqMaster -n 'empty|{(0):1}'
$

Are such discrepancies "bugs"?

After fixing this specific query, you'll report empty|{(0+0):1}. Constant folding is quite complex and unlikely implemented in gojq. Also I think the behavior of jq is halfway, it does not fold constant variables; 1 as $x|empty|{($x):1}. After all this kind of feature creates wired specs, I'd rather prefer letting the check on runtime.

@itchyny - Thanks for the clarification.  As I've already indicated, I never thought of this kind of discrepancy as a "bug" or even as particularly important (though it does frustrate automated testing), but I would like to point out that since there's an obvious difference between expressions such as {(J):1} on the one hand (where J is a literal JSON expression), and {(E):1} (where E is a non-JSON expression) on the other, it seems to me that jq's creators have found a very reasonable and principled way to balance the goals of avoiding complexity and providing some compile-time analysis.


[move] Adjust verifier to accommodate recent core Move modifications

Recent change to core Move (https://github.com/move-language/move/pull/561) requires modifications to Sui's bytecode verifier to accommodate new API. This PR brings Sui's verifier and core Move implementation in sync.

Bit of duplicate work maybe? I already have this goin in #5242

I don't see id_leak_verifier.rs being modified there. Wrong PR number?

Already done in https://github.com/MystenLabs/sui/pull/5240


September 2019 Recovery Endgame

[x] Create a milestone <Month> Recovery <year> owner
[x] Bump the version number owner
[x] Include an issue 'update translations' owner
[x] Assign candidate issues to the recovery milestone team
[x] Review the candidate issues, and if they pass the review assign them to the recovery milestone team
[x] All candidate fixes are peer reviewed and pushed to master and then cherry-picked into the release branch team
[x] Initiate insiders build from master
[x] Issues are tested in the insiders team
[x] Build stable for all platforms from release branch owner
[x] Make rpm signing request @Tyriar
[x] Issues are verified on stable build and the verified label is added owner
[x] Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch owner
[x] Update the release notes and include a link to a query for the fixed issues @gregvanl
Smoketest stable bits  (⚠ MUST run with --stable-build argument ⚠ )

[x] Windows - owner
[x] OS X - owner
[x] Linux - owner

[x] Sanity check of installable bits

[x] Windows 32 bit owner

[x] signed installer 32-bit @sbatten
[x] signed user installer 32-bit @sbatten
[x] zip 32-bit @mjbvz

[x] Windows 64 bit @roblourens

[x] signed installer 64-bit
[x] signed user installer 64-bit
[x] zip 64-bit

[X] OS X - @mjbvz
[x] Linux

[X] deb package 64-bit  @mjbvz
[x] rpm package 64-bit @roblourens
[X] archives  @mjbvz

[x] Publish website @gregvanl
[x] Publish stable build owner
[ ] Publish rpm to repository manually @Tyriar
[x] Add a git tag to HEAD of release/<x.y> in format x.y.z

Closing as we've shipped the recovery


ie9

There are errors with ie9 on the latest version. On your online demo it says 'WeakMap' is undefined. And my local project gives "TypeError: Unable to get property 'add' of undefined or null reference".
Is it worth me trying to find a workaround like a polyfill or do you have an earlier version that might work?

I don't directly use WeakMap, so it's probably just Angular dying in IE9. I don't try to support old versions of IE.


Connection & Session Pool made by OCI

Hi,
You are considered handle Connection & Session Pool made by OCI ?
Regards,
JM

Yes, several times. But I don't really understand the several possibilities Oracle provides.
The Go version is waay simpler, no magic: use as many connections (Srv) as you wish, and pool the sessions (Ses) per Srv.


Add Paragon VMDK Mounter

Add Paragon VMDK Mounter for Mac

@vitorgalvao What do you mean *so no can do?

I mean that solution cannot be used.

Thanks @vitorgalvao, I read the Uninstall Stanza Details and updated the cask.
I'm curious why pkgutil cannot do the work of launchctl and kext automatically

Thank you, @cybertk. I ask you, however, to format it as such:
uninstall :launchctl => 'com.paragon-software.vdmounter',
          :kext => 'com.paragon-software.kext.VDMounter',
          :pkgutil => 'com.paragon-software.VDMounter.pkg'

to be in line with other casks, and that you squash your commits.
As for your question, :pkgutil only lists files to download, and this way gives us more versatility. Some apps install extra launch daemons and kernel extensions after being installed, and some installers aren’t pkgs. This way we cover all grounds.

Thanks a lot @vitorgalvao, I saw you already cherry-picked my code.

Thank you for the contribution.


the cli doesn't work

II tried several different files and types based on the examples given in the documentation, but none of them generated anything except empty files.

Please elaborate. Version? OS? How did you install it?

Closing as stale, please re-open if more information on what version, what command with what settings or parameters was used.


Fix gitlab tests

fix: pipelines as code build -- build via git hook in tekton

PTAL @lkingland @gauron99

this should fix https://github.com/knative/func/issues/2185 right?

PTAL @jrangelramos

/unhold


Blocks using credential blocks update on every plan

I am finding that my S3 Bucket block that references my AWS Credentials block is updating on every plan.  My code looks like this:
resource "prefect_block" "prefect_aws" {
  name      = "prefect--aws"
  type_slug = "aws-credentials"

  data = jsonencode({
    aws_access_key_id     = aws_iam_access_key.prefect_aws.id
    aws_secret_access_key = aws_iam_access_key.prefect_aws.secret
    region_name           = data.aws_region.current.name
  })
}

resource "prefect_block" "my_prefect_results" {
  name      = "my-prefect-results"
  type_slug = "s3-bucket"

  data = jsonencode({
    bucket_name = "my-prefect-results"
    credentials = { "$ref" : { "block_document_id" : prefect_block.prefect_aws.id } }
  })
}

which always seems to yield this update on every plan:
OpenTofu will perform the following actions:

  # prefect_block.my_prefect_results will be updated in-place
! resource "prefect_block" "my_prefect_results" {
!       data      = (sensitive value)
        id        = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
        name      = "my-prefect-results"
!       updated   = "2024-12-10T11:37:39Z" -> (known after apply)
        # (2 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

This is just because of the data field right?  Or am I missing something.  It's only the s3 bucket block that this is happening for.

hey @jbnitorum - is the prefect_aws block changing at all during these cases?

No, we are not seeing any changes in that block within the plan.  Only showing a change on the s3 bucket block.  Doesn't look like any changes are actually happening to me, but it and only it comes up on every single plan.

understood - I'm able to reproduce the issue. Investigating it now


pull request for e2e test at 01/27/2017 03:26:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Identified as a trojan by Windows security

Downloaded Cairo from Softpedia. Windows security identified it as Trojan:Win32/Emali.A!cl. False positive?????

for what it's worth, VIrusTotal says that 0 vendors flagged the URL itself; however, I see that uploading the executable directly from the GitHub release link results in 4/67 detections.


elencare nel README esempi / librerie / plugin / bundles che usano questa libreria

al momento:

https://github.com/simevo/spid-php-lib-example
https://github.com/italia/spid-symfony-bundle
https://github.com/simevo/spid-symfony3-example
https://github.com/simevo/spid-wordpress

a breve:

https://github.com/simevo/spid-laravel
...

fixed with pull request #52


GradleProperties has not been loaded yet. Groovy Gradleplugin  test cases failing

Sorry that you're having trouble with Gradle!
Your issue lacks information about how to reproduce the problem you're having. A reproducer project can really help us track down and fix your problem quicker.  We may also be able to suggest workarounds or ways to avoid the problem if we can reproduce it.
This issue will be closed after 7 days, unless you can provide more information.

Closing due to inactivity.


Add a job to install dependencies

Signed-off-by: shaoyue.chen<EMAIL_ADDRESS>/cc @zwd1208

/lgtm


Use go1.19 memory management changes to GC

Description
Follow up to moving to go1.19 (to be shipped after 74 in order to ensure no adverse effects)
https://tip.golang.org/doc/gc-guide
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Will start running on scale tests

/test

/test gke-scale-tests

/retest

I'm not sure the go max procs change is actually helping us

/test gke-scale-tests


[UX]Revision deploy option is not available for API definition updates

Steps to reproduce:

Create a REST API
Navigate to API definition tab
Import an API definition

Only an import option is provided. There is no option for revision deployment.

This is fixed in latest pack.


[Mutator] Capture CanAm

The author of this mutator, according to the readme, are Cynical Modder and Tomcat
The readme says "This mod was coded by Cynical Modder and textured by Tomcat"

URL: https://unrealarchive.org/mutators/unreal-tournament/C/capture-canam_54ee35ab.html
Hash: 54ee35ab6249ec733c5393b7f5b27e70c9cd8951
Current name: Capture CanAm

Updated


Stick to a ruby style guide

As rack-attack gem developers
We want to stick to a ruby code style guide
So that codebase is consistent and there's less decisions to be made about code style when coding
Idea brought up by @lmansur in https://github.com/kickstarter/rack-attack/pull/284

I think it would be great code style checks to be part of the regular workflow. So that e.g. anyone cloning the repo could easily check code style. I.e.

Contributor clones rack-attack repo
$ bundle install
$ rake runs tests + rubocop, and is all green
Contributor codes something in a topic branch
$ rake to check tests and rubocop again

A possible way to start small on this could be adding rubocop and running $ rubocop --auto-gen-config, which leaves you with no offenses and a TODO list of offenses to work-on/fix. Then we can tackle each offense one by one, instead of trying to fix them all at once.

Are we going to stick to the default configuration?

Hi @lmansur, good question. Not sure.
Can we start with something like this for now?
AllCops:
  DisabledByDefault: true

Layout:
  Enabled: true

We fix all layout offenses.
We grow from there.

PR welcomed if you want to work on that first step :-)
Let me know.

I think the config you posted is good.
We should be careful when incorporating Rubocop into the contribution workflow. I think we ought to point Rubocop as an important tool to reaching a consistent codebase but leaving very explicit that the Cops are a guiding point and not set in stone.
There are some Cops that I personally disagree with (and so does a good share of the community), so we should have an open space for the discussion of what we think is valid or not.
With that in mind, I'm happy to work on a PR. What do you need for the first step? Generate the mentioned configuration file, fix the layout offenses and update the contribution workflow?

With that in mind, I'm happy to work on a PR.

Thank you!

What do you need for the first step? Generate the mentioned configuration file, fix the layout offenses and update the contribution workflow?

Yes, please.

@lmansur Anything i can do to help with this let me know

I didn't have the time yet to start the PR. I'll try and get it over with this week

Sure, no worries. Just checking in case i could help in any way.
Thanks again!


Collaboration?

Hello there!
I started on https://github.com/tecosaur/Voting.jl a ~year and a half ago, would you be interested in collaborating?

Hello!
Thanks for stumbling across my repo. I think I have a similar story. I started this project about a year and a half ago.  Just a quick disclaimer: rank choice voting systems are not my expertise. Its just a topic that piqued my interest.
Yeah. I would be interested in collaborating at some point. Let me finish a few projects and take some time to compare the repos. Maybe one design is better than the other, or maybe there is a third hybrid that is superior to the two components. Maybe they are just different tradeoffs. I'll see if I can get a lay of the land.

Thanks for getting back to me so quickly! Sounds like we indeed came from the same place, I think I just started reading about voting systems at some point and was disappointed there seemed to be no easy way to try them out and compare in practice.
I've only taken a glance at your work, but I see a few nice overlaps. Currently, I like the look of:

You having any docs at all :sweat_smile: :see_no_evil:
My Ballot and Result types + API
Your satisfies methods that can be applied to particular elections
Your methods that I haven't implemented
The methods I've implemented, that you have not

If you're interested in realtime chat I'm around on the Julia Discourse and Zulip as Timothy (same avatar as here).


List of Atom windows is missing on mac

The Window menu item doesn't display the open Atom windows on OS X. I think this feature was present in previous versions.
I'm using Atom 1.2.0 on OS X 10.11.1.

This has already been fixed in the 1.3.0 betas.


Debian package is not present in Jessie

What the title says.

And it will never be. Onces a stable version is released no new packages
get into that release, just security updates or bug fixing updates.
It could get into Jessie anyhow using backports, but i doubt backports team
care enought for that script.
2016-03-15 17:10 GMT+01:00 Pedro<EMAIL_ADDRESS>
What the title says.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/fcambus/ansiweather/issues/91

--
Por limitaciones presupuestarias nos hemos visto obligados a apagar la luz
al final del túnel. Disculpen las molestias.

Thanks for the clarification, Brigo.


No documentation for using AzCopy on a Mac

Please add documentation for using AzCopy on a Mac or say to use help on the command line.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 15911160-5ba2-fb0a-0b24-16b3857e20ce
Version Independent ID: d925bc9f-f825-2f82-168c-6c30d716b9ce
Content: Copy or move data to Azure Storage with AzCopy v10 (Preview)
Content Source: articles/storage/common/storage-use-azcopy-v10.md
Service: storage
GitHub Login: @artemuwka
Microsoft Alias: artemuwka

@yangsiyu007 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

What's the correct way to resume a failed download? I'm trying to download a 200gb VHD, it always fails at some point. I try to resume using 'azcopy jobs resume [jobId] --source-sas="[sasToken]"', and I get the following (very unhelpful) message in the job's log:
[P#0-T#0] has worker 177 which is processing TRANSFER
ERR: [P#0-T#0] DOWNLOADFAILED: url: 000 : Blob already exists
Dst: c:///localpath/vhdfilename.vhd
JobID=[jobId], Part#=0, TransfersDone=1 of 1
all parts of Job [jobId] successfully completed, cancelled or paused

This article is supposed to be platform agnostic and should help with all three platforms: Mac, Unix and Windows. Have you found any of the steps here to be invalid for Mac ?

Sorry, was confused looking at the doc for v8 and didn't realize v10 is cross platform.


Fix(kclvm-windows): rm '\?' in windows path.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

issue #379

2. What is the scope of this PR (e.g. component or file name):

kclvm-windows.
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

rm '\?' in windows path for 'cl.exe'.
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[x] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.562%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1612

Relevant Lines:
1780

💛  - Coveralls

LGTM

Need more unit tests on \\?


Changing default evaluation interval value from 0 to 1

Description
Fixing default value of evaluation interval for medianstoppingpolicy form 0 to 1
Related bug : https://dev.azure.com/msdata/Vienna/_workitems/edit/1884030
Tested experiment: https://ml.azure.com/experiments/id/4b59aa5a-f03c-4e40-9de4-09339d60de8d/runs/test_494226976163?wsid=/subscriptions/b17253fa-f327-42d6-9686-f3e553e24763/resourceGroups/nilesh-new-rg/providers/Microsoft.MachineLearningServices/workspaces/sdk_vnext_cli&tid=72f988bf-86f1-41af-91ab-2d7cd011db47#hyperdriveOverview
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


Fair squares W3F grant application

Project Abstract
Fair Squares aims to co-create a more transparent and fair housing market for tenants, co-owners and social investors. In order to make rental housing more affordable and accessible to a larger group of people.
For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] I have read and understood the FAQs, application guidelines and announcement guidelines.
[x] A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledge the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.
[ ] I prefer the discussion of this application to be in a private Element/Matrix channel. My username is: @_______

How Did You Hear About our grants program?

[x] Social Media
[ ] Hackathon
[ ] Personal Recommendation
[x] Substrate Builders Program
[ ] Investor/VC
[ ] Online Search
[x] Other: We are aware since the inception of the grants programme.

We have closed #969 and re-submitted it with this PR.


Local audio recording

Hi everyone I have made a web app using livekit similar to https://zencastr.com/   but right now I am figuring out is it possible to record the individual voices of people in the room locally as https://zencastr.com/ do.
Thanks in advance :)
Cc : @davidzhao

individual track recording isn't possible today.. but it will be soon.

@adarsh-technocrat individual track recording is now available!
Blog post:
https://blog.livekit.io/livekit-universal-egress-launch/
Docs:
https://docs.livekit.io/guides/egress/
Repo:
https://github.com/livekit/egress


NuGet client version report ignore 'NuGet VS VSIX' user agents

This report has skewed results because 4.6.0+ VSIX downloads are not included.

https://www.nuget.org/stats
Today, user agents starting with NuGet VS VSIX/ are categorized in the stats DB with an empty string category.

ClientName
Major
Minor
Patch
ClientVersion
ClientCategory

NuGet VS VSIX
5
0
0
5.0.0

NuGet VS VSIX
4
9
0
4.9.0

NuGet VS VSIX
4
8
1
4.8.1

NuGet VS VSIX
4
8
0
4.8.0

NuGet VS VSIX
4
7
1
4.7.1

NuGet VS VSIX
4
7
0
4.7.0

NuGet VS VSIX
4
6
2
4.6.2

NuGet VS VSIX
4
6
1
4.6.1

NuGet VS VSIX
4
6
0
4.6.0

Note that for Newtonsoft.Json, this client name is the 3rd most popular:
https://www.nuget.org/stats/packages/Newtonsoft.Json?groupby=ClientName
We are excluding this from the client version report:
https://github.com/NuGet/NuGet.Jobs/blob/7cf33fcf128330b407bd5b2f2242d260fa0c2963/src/Stats.Warehouse/Programmability/Stored Procedures/dbo.DownloadReportNuGetClientVersion.sql#L25
I think the fix here is to put the proper client category of "NuGet". Since PR https://github.com/NuGet/NuGet.Client/pull/1967 (fixing issue https://github.com/NuGet/Home/issues/5853), the VSIX has used this new user agent.
We should fix this so the client version report is not skewed.

Verified in PROD:
ClientName	Major	Minor	Patch	ClientVersion	ClientCategory
NuGet VS VSIX	5	0	0	5.0.0		NuGet
NuGet VS VSIX	4	9	3	4.9.3		NuGet
NuGet VS VSIX	4	9	2	4.9.2		NuGet
NuGet VS VSIX	4	9	1	4.9.1		NuGet
NuGet VS VSIX	4	9	0	4.9.0		NuGet
NuGet VS VSIX	4	8	1	4.8.1		NuGet
NuGet VS VSIX	4	8	0	4.8.0		NuGet
NuGet VS VSIX	4	7	1	4.7.1		NuGet
NuGet VS VSIX	4	7	0	4.7.0		NuGet
NuGet VS VSIX	4	6	2	4.6.2		NuGet
NuGet VS VSIX	4	6	1	4.6.1		NuGet
NuGet VS VSIX	4	6	0	4.6.0		NuGet


How can I insert a jingle / video intro (not strictly speaking an ad) before the main video plays ?

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
Latest
Please ask your question
I have searched the documentation, the open issues and the FAQ, but I could not find an answer to this question (I even asked ChatGPT who made up some configuration options that do not exist :) :
How can I insert a jingle / video intro before the main video plays? I have the URL of the jingle video, (it is not strictly speaking an ad)

Is it possible to "hijack" the ad management system?
With a metadata track somehow ?

Any advice is welcome!
Thanks

We don't have a built-in way to do this. And I kind of doubt that the IMA SDK provides an API to load random video file URLs as though they were client-side ads, either.
It's not pretty, but if the jingle is something that the browser can play natively in a media element you can kind of hijack parts of the ad API to kind of fake a client-side ad.
Something like...
const playJingle = async (uri, shakaPlayer, shakaVideo, shakaControls) => {
  // Make a video for playing the jingle.
  const jingleVideoContainer = shakaControls.getClientSideAdContainer();
  const jingleVideo = document.createElement('video');
  jingleVideoContainer.appendChild(jingleVideo);
  jingleVideo.style.width = '100%';
  jingleVideo.style.height = '100%';

  // Pause the real video, and start loading the jingle.
  shakaVideo.pause();
  jingleVideo.src = uri;
  jingleVideo.play();
  await new Promise((resolve) => jingleVideo.onplaying = () => {
    resolve();
    jingleVideo.onplaying = null;
  });

  // Create a synthetic ad event that wraps the jingle video.
  const adManager = shakaPlayer.getAdManager();
  adManager.dispatchEvent(new shaka.util.FakeEvent('ad-started', {'ad': {
    isLinear: () => true,
    isPaused: () => jingleVideo.paused,
    pause: () => {
      jingleVideo.pause();
      adManager.dispatchEvent(new shaka.util.FakeEvent('ad-paused'));
    },
    play: () => {
      jingleVideo.play();
      adManager.dispatchEvent(new shaka.util.FakeEvent('ad-resumed'));
    },
    getSequenceLength: () => 1,
    getDuration: () => jingleVideo.duration,
    getRemainingTime: () => jingleVideo.duration - jingleVideo.currentTime,
  }}));

  // Wait for the jingle to end, then resume the video and tear down the jingle.
  await new Promise((resolve) => jingleVideo.onended = resolve);
  adManager.dispatchEvent(new shaka.util.FakeEvent('ad-stopped'));
  shakaVideo.play();
  jingleVideoContainer.removeChild(jingleVideo);
});

I guess you'll also want to hide the shaka-ad-counter-span element so that it doesn't say that your jingle is an ad.

Thanks for this detailed response... But I feel like it's a bit complicated just for a jingle...  I think I'll go with a simple src= on the video element, and once the playback is finished , load the shaka player with the same video element.


Call to undefined function _\\get()

I'm struggling to get this library to work.
I've required it via composer. I'm trying to include it with a class (none of the examples in the docs show how to work within classes).
composer.json
{
    "name": "cakephp/app",
    "description": "CakePHP skeleton app",
    "homepage": "https://cakephp.org",
    "type": "project",
    "license": "MIT",
    "require": {
        "php": ">=5.6",
        "lodash-php/lodash-php": "^0.0.6",

php code
<?php
namespace App\Controller\Api;
use function _\get;
class Controller{
    public function __construct()
    {
        get('one.two.three');
    }

error:
 {
            "status": "500",
            "title": "Internal Server Error",
            "detail": "Call to undefined function _\\get()"
 }

I tried this without using classes and I get the same error:
<?php
namespace App\Controller\Api;
use function _\get;
get('obj.one.two.three');
die();

error: Call to undefined function _\\get()
Update: it seems other functions are working, it's only get that doesn't (Murphy's law because that's the only function I'm interested in!).
Looking through the vendor src folder I can see that the get function is not included. The README seems to indicate that it would be expected in the Objects folder but it is not present there.
I also tried composer remove and then require again. Same deal, src/Objects/get.php is missing. I'm on Mac OS X Catalina and Composer version 1.8.6
I also notice that the tests for get are missing from the tests folder.

I tried this without using classes and I get the same error:
<?php
namespace App\Controller\Api;
use function _\get;
$obj = [
    'one' => [
        'two' => [
            'three' => 3,
        ],
    ],
];
get('obj.one.two.three');
die();

Update: it seems other functions are working, it's only get that doesn't (Murphy's law because that's the only function I'm interested in!).
Looking through the vendor src folder I can see that the get function is not included. The README seems to indicate that it would be expected in the Objects folder but it is not present there.

I also tried composer remove and then require again. Same deal, src/Objects/get.php is missing. I'm on Mac OS X Catalina and Composer version 1.8.6

Unfortunately,  the version 0.0.6 doesn't have the function get, but if you get from master branch it will be there.

I solve it to this way.
$company = [
'departments' => [
['teste' => "teste result"],
['teste2' => "teste result 2"]
]
];
function get($data, $string, $default = null){
$arrStr = explode('.', $string);
$result = $data;
foreach($arrStr as $lvl){
if( isset($result[$lvl]) ) $result = $result[$lvl];
else $result = $default;
}
return $result;
}
echo get($company, 'departments.0.teste', 'default');

To get _::get() and get() do this:

setup your composer.json like this:

{
    ...
    "require": {
       ...
        "lodash-php/lodash-php": "dev-master",
       ...
    },
    "repositories": [
      {
        "type": "vcs",
        "url": "https://github.com/lodash-php/lodash-php.git"
      }
    ]
    ...
}

run composer update

Thanks @gedsonmarcelino for the hint!

Version 0.0.7 has now been tagged, which includes the get function.

Thanks for adding the 0.0.7 tag @pierredup.

Thanks for adding the 0.0.7 tag @pierredup.


Tyle8552/names

[x] sample main class name to have "Sample" suffix.
[x] fxml files to have sample name prefix. Ex: mission_replay.fxml
[x] build.gradle update mainClassName
[x] settings.gradle files update include
[x] update readmes to change "Features" to "Tags"
[x] fix image names

@vGandhi Can you review this when you get a chance?

@tyle8552 Looks good.


Fine-tuning.ipynb with gpu

Can some explanation be added to make this notebook run with gpu
Changes like
gpus=1
and hotdog_w = mx.nd.split(pretrained_weight_param.data().as_in_context(mx.gpu())
hotdog_b = mx.nd.split(pretrained_bias_param.data().as_in_context(mx.cpu())
and deep_dog_net.load_params('deep-dog-4.params', mx**.gpu()**)
isn't enough
I tried making
new_classifier_w = mx.nd.concat(mx.nd.random_normal(shape=hotdog_w.shape, scale=0.02).as_in_context(mx.gpu(), hotdog_w,
dim=0)
which also isn't enough.
I wonder is "not_hotdog_validation-c0201740.rec" the culprit?
I get an error at
classify_hotdog(deep_dog_net, '../img/real_hotdog.jpg')
where the second parameter is on cpu. How do I move to gpu?

To run this notebook on gpu...make following changes:
Cell [2]:
change line "gpus = 0" to "gpus = 1"
Cell [7]:
change line "net = models.squeezenet1_1(pretrained=True, prefix='deep_dog_')" to
"net = models.squeezenet1_1(pretrained=True, prefix='deep_dog_', ctx = mx.gpu(0))"
Cell [8]
change line "deep_dog_net = models.squeezenet1_1(prefix='deep_dog_', classes=2)" to
"deep_dog_net = models.squeezenet1_1(prefix='deep_dog_', classes=2, ctx = mx.gpu(0))"
change line "deep_dog_net.collect_params().initialize()" to
"deep_dog_net.collect_params().initialize(ctx = mx.gpu(0))"
Cell[9]:
change line "image = mx.nd.expand_dims(image, axis=0)" to
"image = mx.nd.expand_dims(image, axis=0).as_in_context(mx.gpu(0))"
Cell[12]:
change line: "new_classifier_w = mx.nd.concat(mx.nd.random_normal(shape=hotdog_w.shape, scale=0.02),"
to                 "new_classifier_w = mx.nd.concat(mx.nd.random_normal(shape=hotdog_w.shape, scale=0.02).as_in_context(mx.gpu(0)),"
change line "new_classifier_b = mx.nd.concat(mx.nd.random_normal(shape=hotdog_b.shape, scale=0.02)," to
"new_classifier_b = mx.nd.concat(mx.nd.random_normal(shape=hotdog_b.shape, scale=0.02).as_in_context(mx.gpu(0)),"
Cell[16]:
change line "deep_dog_net.load_params('deep-dog-4.params', mx.cpu())" to
"deep_dog_net.load_params('deep-dog-4.params', mx.gpu())"
change line "deep_dog_net.load_params('deep-dog-5a342a6f.params', mx.cpu())" to
"deep_dog_net.load_params('deep-dog-5a342a6f.params', mx.gpu())"