Creating files for MiRo-B robot platform capability

I have created new files for miro-b robot, which should not have impact on the original code.
To be aware, the image_processing_miro_b.py does not use the exact same code as the image_processing.py due to some array issues, this will be investigated further.
The creation of new teleop_joy is due the reason that MiRo-B does not use TwistStamp, it simply uses Twist message type.

The launch files look good
The new teleop_joy node makes sense - I guess remove the commented out code from the Miro-E
I don't quite follow the differences with the new image_stitcher and image_processing. Were you getting an error with the existing code? At least for the image processing I think it makes more sense just to add a new function instead of a whole new file replicating most of the same functionality.

From memory, the image_processing says something along different shape between the two arrays. So I went back to the one you committed few months ago that allows other robots to do the stitching and processing (commit f6b5eb51596581f6db9b008eddb4ba8c61fd7f78).

That version of image_processing should basically be the same as the current version I added the other day - I just added a check to make sure the patch_size is odd in the latest version, which shouldn't affect the stitching/blending.

I think you should also add calibration files for the Miro-B's cameras, then update the launch files to use them.
Then can you revert the image_stitcher so it passes the calibration files to the image stitching? You'll probably need to pass different parameters to this function. It's explained a bit in #36
Then do you still get an error in the image stitching? If so there's a problem I need to fix - can you post the error message?

My bad I have realized that I have commented out the 'rectify_stitch_stereo_image' function call within the 'image_stitcher_miro_b'. But the following error is the one I get if running the recent code.

line 478, in rectify_stitch_stereo_image
stitched[:,:warped_left.shape[1]] = warped_left * blend_map_linear
ValueError: operands could not be broadcast together with shapes (240,520) (600,)

Another question, how did you generate your calibration files, is it simply scaling? (camera resolution of Miro-B is 320x240).
Or did you run the camera_calibration.launch to generate the data as well as the image you have in https://github.com/QVPR/teach-repeat/issues/36.
Thank you

Ahh, I think I see the problem that I never added a way for the parameters to be passed through - I'll fix that.
But yeah, can you use camera_calibration.launch to get the calibration files for each camera. There are some good ROS tutorials for this here and here if you've never done it before. Actually we just want a calibration file for each camera individually, we don't need the stereo calibration.

Ok, I made some changes that should help. Can you pull from here https://github.com/QVPR/teach-repeat/tree/pr38 into this branch? Alternatively, on the right hand side on github there should be an option to allow me permissions to push to your fork - I think this isn't enabled at the moment because I'm getting an authentication error?

The permission is already enabled, so not sure why it is not working, I have created a new branch in my repository from the branch you have mentioned.
I will definitely take a look into the materials you have provided and I will give it another go once I have the chance to do so.
Thank you for you help Dominic.

Hmm, that's weird. Maybe it's me doing something wrong then haha. When you get the chance it should work to merge the pr38 branch into your master and the PR will update.
No worries though!

Hi @Dominic-DallOsto @n10200568 - what's the status of this PR?

I have merged the pr38 branch (mentioned by @Dominic-DallOsto) into my master branch, and everything works without conflicts. From memory I have removed the image_processing_miro_b.py file on my local files, but have not yet pushed through to the repository. I will double check later today and make the necessary changes, thank you.

I have pushed the required files on to my repository. Everything should be fine to merge without affecting the original codes. The modification to files data_collect.py, image_matcher.py and image_sticher.py was from the merge of pr38 branch into master branch on my repository.

I think this looks OK code-wise.
I think the configuration for the image stitching should be verified before merging though

Can you make a calibration file for each of the Miro-B's cameras (I think they have a different field of view to the Miro-E cameras), and put those calibration files in the repo / reference them in the Miro-B launch files?
Then can you check the output of the image_stitcher - are the image blended nicely enough? Can you adjust the parameters in the launch file to improve it

Then I think we should be all good

Hi @n10200568 - I suggest to keep this PR limited to what is written in the title (i.e. compatibility with MiRo-B instead of MiRo-E), and open a separate PR that contains the multi-robot stuff. Otherwise it's too hard to review. Especially considering that we were "nearly there" with just the changes needed for MiRo-B.

Camera calibrations had been updated, where previous commits of the multi-robot system have been reverted, so only relevant files are present for the miro-b compatibility.

Ta - @Dominic-DallOsto any chance you could have another look?

Cool, that looks good! Can you just change the names of the calibration files to be eg. left_240_miro_b, and change the comments inside to say these calibration files are for the Miro-B and how you got them (I guess doing a calibration at 240*320)?
Then can you send an image of the output of the image stitcher, just to check how it looks?
Thanks!

Here are two images with different parameters.

The above one is with empty_pixel=0 and blank_pixel=0.1.

This one is with empty_pixel=0 and blank_pixel=0.5.
@Dominic-DallOsto I am unsure how you did the unwrap image like in #36  and I have tried to tune the variables. But however I change the variables it seems like the images are overlaying on top of each other, rather than only overlap on the edges so it looks like a panorama view. Will it be like FOV parameters or other parameters that can cause this issue?

It look like there's a rotation between the left and right images which
is weird.
Hmmm...
Could you save an image each from the left and right cameras, then run
the image_processing.py script locally to do the following:

show the left and right raw images from the camera
run rectify_stitch_stereo_image but comment out the right image so
it just stitches the left, and vice versa - this should give you
something like in #36 and let you measure blank_pixel
if this doesn't look right, it could be that I didn't get
camera_half_fov and camera_offset correctly - can you check them
against the geometry of the Miro-B?

If you could post those images, that should help us debug to see where
the issue is at the moment.
Thanks!
On 5/09/2022 8:17 am, Kai-Cherng Lee wrote:

Here are two images with different parameters.
000000
https://user-images.githubusercontent.com/62236175/188371715-91d90fde-4d6d-4d33-b2de-8877939ab9f1.png
The above one is with |empty_pixel=0| and |blank_pixel=0.1|.
000000
https://user-images.githubusercontent.com/62236175/188371621-2afb6f1f-9341-4a29-a0b6-c47fffa7aa39.png
This one is with |empty_pixel=0| and |blank_pixel=0.5|.
@Dominic-DallOsto https://github.com/Dominic-DallOsto I am unsure
how you did the unwrap image like in #36
https://github.com/QVPR/teach-repeat/issues/36 and I have tried to
tune the variables. But however I change the variables it seems like
the images are overlaying on top of each other, rather than only
overlap on the edges so it looks like a panorama view. Will it be like
FOV parameters or other parameters that can cause this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/QVPR/teach-repeat/pull/38#issuecomment-1236578694,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGM5S3CMD5DNVGQUMJQDCC3V4WF5ZANCNFSM52IT3RZA.
You are receiving this because you were mentioned.Message ID:
@.***>

Below are the two raw images:

Left

Right
When using rectify_stitch_stereo_image() function locally with, extra_pixels=0, and blank_pixels=0. The below is the stitched image:

And when extracting the warped_left and warped_right images, from rectify_stitch_stereo_image(), these are what I have got:

Warped Left

Warped Right

The change of the rotation divergence worked. Although I am not too sure how you got the rectification matrix, was it using the stereo camera calibration method? Because @Dominic-DallOsto  you previously mention we only need to calibrate it individually so I am unsure was that the issue.
But the results are shown here.

Both Image Combined (extra_pixels_ratio=0, blank_pixels_ratio=0)

Left Warped Image

Right Warped Image
Modifying (extra_pixels_ratio=0.5, blank_pixels_ratio=0.36)

Although there is still a slight mismatch at the center, but I presume that's due to the rectification_matrix in the calibration file. So if the rectification_matrix is acquired by using the stereo camera calibration method, I am happy to do so to get a better result.

Ahh nice - that looks a lot better!
I got the recitifcation matrix just using the geometry of the camera placement from the docs - each camera is rotated 27 degrees horizontally from the centre line - so the rectification matrix is just a rotation matrix for 27 degrees to rotate both images to be as if taken from facing straight ahead.
Like you say, that's not perfect and actually calibrating the stereo offset would be better. I never managed to do this successfully though because there isn't a lot of stereo overlap between the cameras so I found that the automatic stereo camera calibrator ROS package didn't work.
If you have enough time to try it out / really need the image stitching to be nice, maybe it's worth trying. But overall I think it should be good enough after downscaling the image a bit anyway. You could also just try changing the rectification matrix to be a rotation of a degree or two more or less and see if that improves it.
Happy to merge this now when you're ready. Thanks a lot for your work!

Awesome! I'd say let's merge this now, and then do the remaining changes in the next PR with the multi robot stuff.


Add support for extension_dn

Description
Add support for extension domain name check, similar to how it's done for admin certificate or for nodes from different clusters More about that in the task: https://github.com/opensearch-project/security/issues/2730
Issues Resolved
https://github.com/opensearch-project/security/issues/2730
Currently the implementation looks like this:
During extension initialization via REST call, DNs are passed in the request body:
curl -XPOST -k -u user:password "https://localhost:9200/_extensions/initialize" -H "Content-Type:application/json" --data '{ "name":"hello-world", "uniqueId":"hello-world2", "hostAddress":"<IP_ADDRESS>", "port":"4500", "version":"1.0", "opensearchVersion":"3.0.0", "minimumCompatibleVersion":"3.0.0", "dependencies":[{"uniqueId":"test1","version":"2.0.0"},{"uniqueId":"test2","version":"3.0.0"}], "distinguishedNames": ["CN=extension-0.example.com,OU=node,O=node,L=test,DC=de"] }'
In next iterations I'd like to store configuration in index and make it dynamic.
PR on openserch-core side:
Here's old PR that I created at the beginning of working on the task, additional input from @cwperks is there.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @cwperks, I believe this PR is ready for merge or another review round. There are some problems with coverage. Most of the highlighted changes are ones that got to my branch from main. Since PR points to feature/extensions those changes are not yet included in this branch feature.
Another issue is usage of the word "extension" in various classes. For example https://github.com/MaciejMierzwa/security/blob/d27fe9f3c92f1f73bb2bbec4fb1757744ec23da9/src/main/java/org/opensearch/security/transport/SecurityRequestHandler.java#L396-L397. I can change the Extension extension object declaration to Extension ext but I doubt it will help since tool seems to pick class name anyway. Other than that, there are some failed test runs -> I think it's flakiness.
Let me know what you think

Thank you @MaciejMierzwa . I will take a look ASAP.
FYI you can suppress the check following this example: https://github.com/opensearch-project/security/blob/8063e1b64f880afb7dc54311f3110b162b913038/src/main/java/org/opensearch/security/support/ConfigConstants.java#L103-L106

@MaciejMierzwa Seems like your last commit: da1eeca brought in changes from main but this PR is against feature/extensions. Once you address this, the issue should be fixed.

I think I included changes from main at a point in time when security wouldn't build. I figured since somebody will surely merge main anyway and additional commits pulled into the branch by me wouldn't pop up.


ICF-Provider Tool bat script is not working as expected

Description:
icf-provider.bat script (Windows OS) is not working as expected
Suggested Labels:
Bug
Affected Product Version:
5.2.1 onwards
Steps to reproduce:

Download activemq-client-5.9.0.jar from https://mvnrepository.com/artifact/org.apache.activemq/activemq-client/5.9.0
icf-provider.bat org.apache.activemq.jndi.ActiveMQInitialContextFactory /temp/activemq-client-5.9.0.jar /temp should create the BundleActivator to jar activemq-client-5.9.0.jar which will register the user mentioned ICF implementation according to the OSGi JNDI spec (However it doesn't in Windows environment)

Related Issues:

https://github.com/wso2/carbon-kernel/issues/1577 - Need to provide support to register InitialContextFactory classes according to OSGi JNDI spec

Can someone resolve this issue?

Ok I realized, what was the problem.
Firstly, in icf-provider.bat is badly formated carbon.home property in java -cp command.
You should use -Dcarbon.home=%CARBON_HOME% instead of -Dcarbon.home="%CARBON_HOME"
Full command should be
java -cp ".\*;..\bin\tools\*" -Dcarbon.home=%CARBON_HOME% -Dwso2.carbon.tool="icf-provider" org.wso2.carbon.tools.CarbonToolExecutor %1 %2 %3 %4
The second problem is in ICFProviderTool.java, especially in addBundleActivatorHeader method.
URI uri = URI.create("jar:file:" + (finalJarPath.toString());
This cannot work correctly in windows, because windows contains backslashes in path and on the other hand, URI can't work with backslashes. So you have to put Path converted to uri to method URI.create().
So following code works correctly ->
 URI uri = URI.create("jar:file:" + Paths.get(finalJarPath.toString()).toUri());
Did someone test this tool on windows before release?

Just downloaded SP 4.3.0 which still contains this bug.
Above solution solves the issue.
./icf-provider.bat notation is also not available on Windows


Matrix options must only contain primitive values

https://github.com/passwa11/Certificate-Transparency-Monitor---Rust
name: Rust

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

env:
  CARGO_TERM_COLOR: always
  CRATE_NAME: passwa11
  GITHUB_TOKEN: ${{ github.token }}
  RUST_BACKTRACE: 1

jobs:
  test:
    name: ${{ matrix.platform.os_name }} with rust ${{ matrix.toolchain }}
    runs-on: ${{ matrix.platform.os }}
    strategy:
      fail-fast: false
      matrix:
        platform:
          - os_name: FreeBSD-x86_64
            os: ubuntu-20.04
            target: x86_64-unknown-freebsd
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-FreeBSD-x86_64.tar.gz
            skip_tests: true
          - os_name: Linux-x86_64
            os: ubuntu-20.04
            target: x86_64-unknown-linux-musl
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-x86_64-musl.tar.gz
          - os_name: Linux-aarch64
            os: ubuntu-20.04
            target: aarch64-unknown-linux-musl
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-aarch64-musl.tar.gz
          - os_name: Linux-arm
            os: ubuntu-20.04
            target: arm-unknown-linux-musleabi
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-arm-musl.tar.gz
          - os_name: Linux-i686
            os: ubuntu-20.04
            target: i686-unknown-linux-musl
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-i686-musl.tar.gz
            skip_tests: true
          - os_name: Linux-powerpc
            os: ubuntu-20.04
            target: powerpc-unknown-linux-gnu
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-powerpc-gnu.tar.gz
            skip_tests: true
          - os_name: Linux-powerpc64
            os: ubuntu-20.04
            target: powerpc64-unknown-linux-gnu
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-powerpc64-gnu.tar.gz
            skip_tests: true
          - os_name: Linux-powerpc64le
            os: ubuntu-20.04
            target: powerpc64le-unknown-linux-gnu
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-powerpc64le.tar.gz
            skip_tests: true
          - os_name: Linux-riscv64
            os: ubuntu-20.04
            target: riscv64gc-unknown-linux-gnu
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-riscv64gc-gnu.tar.gz
          - os_name: Linux-s390x
            os: ubuntu-20.04
            target: s390x-unknown-linux-gnu
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Linux-s390x-gnu.tar.gz
            skip_tests: true
          - os_name: NetBSD-x86_64
            os: ubuntu-20.04
            target: x86_64-unknown-netbsd
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-NetBSD-x86_64.tar.gz
            skip_tests: true
          - os_name: Windows-aarch64
            os: windows-latest
            target: aarch64-pc-windows-msvc
            bin: Certificate-Transparency-Monitor.exe
            name: Certificate-Transparency-Monitor-Windows-aarch64.zip
            skip_tests: true
          - os_name: Windows-i686
            os: windows-latest
            target: i686-pc-windows-msvc
            bin: Certificate-Transparency-Monitor.exe
            name: Certificate-Transparency-Monitor-Windows-i686.zip
            skip_tests: true
          - os_name: Windows-x86_64
            os: windows-latest
            target: x86_64-pc-windows-msvc
            bin: Certificate-Transparency-Monitor.exe
            name: Certificate-Transparency-Monitor-Windows-x86_64.zip
          - os_name: macOS-x86_64
            os: macOS-latest
            target: x86_64-apple-darwin
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Darwin-x86_64.tar.gz
          - os_name: macOS-aarch64
            os: macOS-latest
            target: aarch64-apple-darwin
            bin: Certificate-Transparency-Monitor
            name: Certificate-Transparency-Monitor-Darwin-aarch64.tar.gz
            skip_tests: true
        toolchain:
          - stable
          - beta
          - nightly
    steps:
      - uses: actions/checkout@v4
      - name: Cache cargo & target directories
        uses: Swatinem/rust-cache@v2
      - name: Configure Git
        run: |
          git config --global user.email<EMAIL_ADDRESS>          git config --global user.name "J. Doe"
      - name: Install musl-tools on Linux
        run: sudo apt-get update --yes && sudo apt-get install --yes musl-tools
        if: contains(matrix.platform.name, 'musl')
      - name: Build binary
        uses: houseabsolute/actions-rust-cross@v0
        with:
          command: "build"
          target: ${{ matrix.platform.target }}
          toolchain: ${{ matrix.toolchain }}
          args: "--locked --release"
          strip: true
      - name: Run tests
        uses: houseabsolute/actions-rust-cross@v0
        with:
          command: "test"
          target: ${{ matrix.platform.target }}
          toolchain: ${{ matrix.toolchain }}
          args: "--locked --release"
        if: ${{ !matrix.platform.skip_tests }}
      - name: Package as archive
        shell: bash
        run: |
          cd target/${{ matrix.platform.target }}/release
          if [[ "${{ matrix.platform.os }}" == "windows-latest" ]]; then
            7z a ../../../${{ matrix.platform.name }} ${{ matrix.platform.bin }}
          else
            tar czvf ../../../${{ matrix.platform.name }} ${{ matrix.platform.bin }}
          fi
          cd -
        if: |
          matrix.toolchain == 'stable' &&
          ( startsWith( github.ref, 'refs/tags/v' ) ||
            github.ref == 'refs/tags/test-release' )
      - name: Publish release artifacts
        uses: actions/upload-artifact@v4
        with:
          name: Certificate-Transparency-Monitor-${{ matrix.platform.os_name }}
          path: "Certificate-Transparency-Monitor-*"
        if: matrix.toolchain == 'stable' && github.ref == 'refs/tags/test-release'
      - name: Generate SHA-256
        run: shasum -a 256 ${{ matrix.platform.name }}
        if: |
          matrix.toolchain == 'stable' &&
          matrix.platform.os == 'macOS-latest' &&
          ( startsWith( github.ref, 'refs/tags/v' ) ||
            github.ref == 'refs/tags/test-release' )
      - name: Publish GitHub release
        uses: softprops/action-gh-release@v2
        with:
          draft: true
          files: "Certificate-Transparency-Monitor-*"
          # body_path: Changes.md
        if: matrix.toolchain == 'stable' && startsWith( github.ref, 'refs/tags/v' )

error:
Matrix options must only contain primitive values

I'm not sure exactly what's going on, but it doesn't really have anything to do with this action. I've not seen this error from GH Actions before, and from some Googling it's not clear exactly what in your config isn't a primitive value.


Can demultiplex pipeline take multiple annotation sheets?

The demultiplex pipeline currently takes a single annotation sheet, which is fine for almost all cases. Flow lanes can have multiple annotation sheets, where there is a mix of, say, CLIP and RNA-Seq samples in a single multiplexed reads file. What would the options be for allowing multiple annotation sheets as inputs?
Having an arbitrary number might be hard, but we could hardcode say, 5 (--annotation, --annotation2 etc) of which only the first is required. The CLIP_SAMPLESHEET_TO_BARCODE module could then take multiple input CSVs and create a single barcode file (as the three columns that Ultraplex cares about would be in all annotation sheets).
Not super urgent, but will probably be required eventually.

This seems very possible, I think also an arbitrary number wouldn't be difficult, --annotation can take a list as input and then only the necessary columns are taken forward from each csv and just concatenated. Will see where this fits in with mine and Chris' other tasks.

Sometimes a lane of sequencing data can contain multiple data types - such as in ule lab they might combine quantseq and clipseq or riboseq on the same lane, so this would be useful. Ultraplex is flexible for really any kind of data demultiplexing so I really don't see this as CLIP-specific at all.

Having a single param take a column-separated list of files would mean modifying Flow (currently it's one param, one file) - but maybe it could look for all params that being annotation_n and do something with that, if you do want to let it take an arbitrary number? Hardcoding a specific number such as 5 would require the fewest changes to the way Flow works.


Introduce PAR support / add an option to ship a PEX with Python included.

With the advent of scies, Pex's can now be shipped as standalone native executables with the Python interpreter included without much effort. If Pex were to incorporate this feature, it might be spelled like:
--par {eager,lazy}

This would cause Pex to generate one or more binaries using scie-jump that either directly include the appropriate PBS Python archive or else lazily fetch it using ptex. The fiddly bit here will be selecting an appropriately matched PBS per Pex target Python / abbreviated --platform / --complete-platform.

This has been a dream since ~day 1 of Pex, it was just too much work to consider. More recent surfacing of this desire has been in #636 and #1007.

Noting that the last PBS release to support 3.7 is https://github.com/indygreg/python-build-standalone/releases/tag/20200822 and that support 3.7.9. Modern PBS releases support 3.8 through 3.11. So Pex could support --par for 3.8 through 3.11 trivially, but possibly also for 3.7 as well.

Alright, since --par is a Googlism and the real backend is scie; I'm just rolling with --scie {lazy,eager} and a few --scie-* options for exact control of the PBS Python selected when needed. The initial support is just as a Pex CLI build option. If someone wants a pex3 tool to turn an existing PEX file into a scie, that is easy enough to add later. This change contains all the infrastructure to do that.


Add PPO Part 2

This is the Unit about PPO Part 2
Content: Sample Factory and Doom
🗓 Publication date: 22/02/2023

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


still get ArgumentException: Options.ClientId must be provided Parameter name: ClientId with latest Template

Template ASPNET Core MVC Authentication Individual with latest version of VS2017 enterprise Version 15.3.0 Preview 2.
The same error happens each time I simple press F5 or Ctrl+F5:

ArgumentException: Options.ClientId must be provided Parameter name: ClientId

The appsettings.json contains the clientId, so I don't get it
"Authentication": { "IdentityService": { "ClientId": "D67625E3-714E-4A2E-9E1E-365AB5744B05", "TokenRedirectUrn": "urn:self:aspnet:identity:integrated" }
<ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0-preview2-25149" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="2.0.0-preview2-25149" PrivateAssets="All" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.0-preview2-25149" PrivateAssets="All" />
  </ItemGroup>

  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0-preview2-25149" />
    <DotNetCliToolReference Include="Microsoft.Extensions.SecretManager.Tools" Version="2.0.0-preview2-25149" />
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.0-preview2-25149" />
  </ItemGroup>

Product Information:
 Version:            2.0.0-preview2-006215
 Commit SHA-1 hash:  e67962b0de

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16199
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Users\vrith\.dotnet\x64\sdk\2.0.0-preview2-006215\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview2-25319-02
  Build    : 7983b575ebcbdc3a825eea4b141ff7fb69d25f9d

ps:
Guys, I know this is a preview, but it could be cool to get a working template when we try to learn stuff.  ;-)
Thanks

Im seeing this in ASP.NET Core 2.0 RTM. Was there any solution to this? Or do we have to set all entries by using opt => opt.XXX = Configuration["Section:XXX"]?


[JENKINS-18884] People View plugin

Repository URL
https://github.com/daniel-beck/people-view-plugin/
New Repository Name
people-view-plugin
Description
Extracting the current core feature into a plugin (without split/detached implied dependency).
Upstream is https://github.com/jenkinsci/jenkins/pull/9060
JENKINS-18884
GitHub users to have commit permission
@daniel-beck
Jenkins project users to have release permission
danielbeck
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a Jenkins Security Scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the Jenkins Security Scan were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audit were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.28.0)

:x: Jenkins Security Scan failed.
The Security team was notified about this.

FTR error came from

[ERROR] Non-resolvable import POM: The following artifacts could not be resolved: org.jenkins-ci.main:jenkins-bom:pom:2.451-SNAPSHOT (absent)

As there is an upstream PR, it's expected :)

/request-security-scan

@daniel-beck BTW you can specify an incremental (rc) version for jenkins.version. You will not be able to cut a release until it is switched to a regular version (something present in releases).

The Jenkins Security Scan did not find anything dangerous with your plugin, congratulations! :tada:

:bulb: The Security team recommends that you are setting up the scan in your repository by following our guide.

@jglick Thanks for the reminder.

/hosting host

/hosting host


Update zh-TW.json

Thanks. Can you please made the changes via our Crodwin, as per readme?

Done. sorry didn't notice that.

I will close this one if favor of https://github.com/excalidraw/excalidraw/pull/1748/files


[Suggestion] An tutorial on raising the maximum year to prevent Y2030

As the title says. Y2030 definetly in an problem, but this repo focuses on an decompilation without mods. If this is possible, then an tutorial will be great.

Refer to https://github.com/Prakxo/ac-decomp/issues/210#issuecomment-1879947404 , will not be done here


Add Impacta

The university site is different from the student's email domain. The university site is: http://www.impacta.edu.br
Here's an IT-related long-term course offered by the university (B.S. in Information Systems): http://www.impacta.edu.br/#!/cursos/sistemas-de-informacao/77

@williamfn Could you please give us a link to a page or an official document saying that alunoimpacta.com.br domains belongs to students at FIT? It is also important to ensure that only students studying in classrooms have emails in this domain, and the college does not give the email to people studying with distance learning only and short-term courses.

The university don't have distance learning courses, ony presential courses. You can check it on the courses pages:

http://www.impacta.edu.br/#!/cursos/graduacao - (B.S. level)
http://www.impacta.edu.br/#!/cursos/pos - (graduate level)
http://www.impacta.edu.br/#!/cursos/tecnicos (certificate programs level)

All they are long-term courses (minimum duration 18 months).
About the domain belonging to the university, whois's screenshots showing the same owner for both domains prove it? You can check it at the brazilian register provider: https://registro.br/cgi-bin/whois/

@williamfn Thank you for the details! Pull request merged.

Thank you!
Just one question: when the register with the university e-mail will be available for us?

@williamfn Usually updates are available in about a half an hour. If it still does not work, please let us know.

@philipto It still says my email dont belong to a known university domain. Can you check it or I need to reach the support for formal support? :)

We'll investigate this in few hours. I am sorry for the inconvenience.

12 мая 2016 г., в 0:57, William Fernandes<EMAIL_ADDRESS>написал(а):
@philipto It still says my email dont belong to a known university domain. Can you check it or I need to reach the support for formal support? :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Could you please send an email to<EMAIL_ADDRESS>and write there which email address you use to request a license? Thank you!

12 мая 2016 г., в 0:57, William Fernandes<EMAIL_ADDRESS>написал(а):
@philipto It still says my email dont belong to a known university domain. Can you check it or I need to reach the support for formal support? :)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Sure I will send now. Thanks for the help.


Update index.astro

adding font class to titles

👷 Deploy Preview for famous-marshmallow-cfbd61 processing.

Name
Link

🔨 Latest commit
d4e73aabcedf90dcda1337fc19d9e65b86a5061f

🔍 Latest deploy log
https://app.netlify.com/sites/famous-marshmallow-cfbd61/deploys/64dae6ddaaf16b00084b9ad8


API Overview link is broken

http://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/apis/dialog-apis.html should be http://www.ibm.com/smarterplanet/us/en/ibmwatson/developercloud/dialog/api/v1/

@germanattanasio you forgot to push the app to bluemix after you updated the link :P


Azure Disk Encryption

We have a requirement to enable Azure Disk Encryption for both OS and Data disks. Currently when attempting to enable this we are getting an error.
This is the first error that is seen - this is attempt #5 of 10.
OsVolumeEncrypted          : EncryptionInProgress
DataVolumesEncrypted       : EncryptionInProgress
OsVolumeEncryptionSettings : Microsoft.Azure.Management.Compute.Models.DiskEncryptionSettings
ProgressMessage            : Attempt #5 to unmount /oldroot failed with error: Command umount /oldroot failed with return code 32
                             stdout:

                             stderr:
                             umount: /oldroot: target is busy
                                     (In some cases useful info about processes that
                                      use the device is found by lsof(8) or fuser(1).)
                             , stack trace: Traceback (most recent call last):
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/Ubuntu1604EncryptionStateMachine.py", line 170, in start_encryption
                                 self.retry_unmount_oldroot()
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/transitions/transitions/core.py", line 222, in trigger
                                 return self.machine.process(f)
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/transitions/transitions/core.py", line 526, in process
                                 return trigger()
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/transitions/transitions/core.py", line 247, in _trigger
                                 if t.execute(event):
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/transitions/transitions/core.py", line 145, in execute
                                 machine.callback(func, event_data)
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/transitions/transitions/core.py", line 518, in callback
                                 func(*event_data.args, **event_data.kwargs)
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/Ubuntu1604EncryptionStateMachine.py", line 114, in on_enter_state
                                 super(Ubuntu1604EncryptionStateMachine, self).on_enter_state()
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/OSEncryptionStateMachine.py", line 65, in on_enter_state
                                 self.state_objs[self.state].enter()
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/encryptstates/UnmountOldrootState.py", line 130, in enter
                                 self.command_executor.Execute('umount /oldroot', True)
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/CommandExecutor.py", line 73, in Execute
                                 raise Exception(msg)
                             Exception: Command umount /oldroot failed with return code 32
                             stdout:

                             stderr:
                             umount: /oldroot: target is busy
                                     (In some cases useful info about processes that
                                      use the device is found by lsof(8) or fuser(1).)

Final error is:
OsVolumeEncrypted          : EncryptionInProgress
DataVolumesEncrypted       : EncryptionInProgress
OsVolumeEncryptionSettings : Microsoft.Azure.Management.Compute.Models.DiskEncryptionSettings
ProgressMessage            : Failed to encrypt OS volume with error: Attempt #11 to unmount /oldroot failed with error: Could not unmount /oldroot in 10 attempts, stack trace: Traceback (most recent call last):
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/Ubuntu1604EncryptionStateMachine.py", line 168, in start_encryption
                                 raise Exception("Could not unmount /oldroot in 10 attempts")
                             Exception: Could not unmount /oldroot in 10 attempts
                             , stack trace: Traceback (most recent call last):
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/handle.py", line 1613, in daemon_encrypt
                                 os_encryption.start_encryption()
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/Ubuntu1604EncryptionStateMachine.py", line 185, in start_encryption
                                 raise Exception(message)
                             Exception: Attempt #11 to unmount /oldroot failed with error: Could not unmount /oldroot in 10 attempts, stack trace: Traceback (most recent call last):
                               File "/var/lib/waagent/Microsoft.Azure.Security.AzureDiskEncryptionForLinux-<IP_ADDRESS>9326/main/oscrypto/ubuntu_1604/Ubuntu1604EncryptionStateMachine.py", line 168, in start_encryption
                                 raise Exception("Could not unmount /oldroot in 10 attempts")
                             Exception: Could not unmount /oldroot in 10 attempts

                             , machine state: unmount_oldroot

Is the use of ADE achievable for an elastic cluster deployed using Azure CLI 2.0?

I had the exact same problem.  For me, the fix was to stop the ES JVM process before running the encryption command.  The encryption process needs plenty of RAM to complete.

@darrell-tethr found that just stopping the ES service wasn't enough, it still gave the above errors about unmount_oldroot.
In the end I stopped the service, disabled it, rebooted the vm prior to encyption and then ran the same command for encryption this gave a successful encrypt.
Obviously this was all tested on a test instance (single master/data).
Now to do this for an entire 9 box cluster...

@robertmarks I've been meaning to test restoring an ES cluster but I haven't gotten tried yet. Thanks for the warning.  If you find a fix, please let me know. Thanks!

@darrell-tethr Found that post restore, the OS disk will come back just fine. For the datadisk which is mounted at /datadisks/disk1 you need to run the Set-AzureRmVmDiskEncryptionExtension -VolumeType Data or az vm encryption enable --volume-type data command (obviously needs the full command).
More detail here - Step 4


I recieve error from node

generic_pass.js gives error when running with node. The error:
node:internal/modules/cjs/loader:1078
throw err;
^
Error: Cannot find module 'google-auth-library'
Require stack:

C:\Users\user\Desktop\wallet-android-codelab\backend\generic_pass.js
←[90m    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)←[39m
←[90m    at Module._load (node:internal/modules/cjs/loader:920:27)←[39m
←[90m    at Module.require (node:internal/modules/cjs/loader:1141:19)←[39m
←[90m    at require (node:internal/modules/cjs/helpers:110:18)←[39m
at Object. ←[90m(C:\Users\user\Desktop\wallet-android-codelab\backend\←[39mgeneric_pass.js:1:24←[90m)←[39m
←[90m    at Module._compile (node:internal/modules/cjs/loader:1254:14)←[39m
←[90m    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)←[39m
←[90m    at Module.load (node:internal/modules/cjs/loader:1117:32)←[39m
←[90m    at Module._load (node:internal/modules/cjs/loader:958:12)←[39m
←[90m    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)←[39m {
code: ←[32m'MODULE_NOT_FOUND'←[39m,
requireStack: [
←[32m'C:\Users\user\Desktop\wallet-android-codelab\backend\generic_pass.js'←[39m
]
}

Node.js v18.15.0

I fixed it with downloading this npm i google-auth-library.
After the other problem occured.


Reverse compatibility layer

Is there any layer to consume preact-specific components in React? I mean, some module which would polyfill the h to createElement, render and so on?

react-compat.js:
import { createElement, cloneElement, render, findDOMNode, Component as ReactComponent } from 'react';

function h() {
  const vnode = createElement.apply(this, arguments);
  vnode.attributes = vnode.props;
  vnode.nodeName = vnode.tag;
  return vnode;
}

class Component extends ReactComponent {
  get base() {
    return findDOMNode(this);
  }
}

export default { render, h, createElement: h, cloneElement, Component };
export { render, h, h as createElement, cloneElement, Component };

@developit where would this go in the build process?

 I am having trouble to make it work.
My React project is setup react-scripts, I have added your script and added:
"module": {
    "exports": {
      "settings": {
        "import/resolver": {
          "alias": {
            "preact:": "./src/react-compat.js"
          }
        }
      }
    }
  }

to the .eslintrc file and also added the module eslint-import-resolver-alias.
I am not sure that setup is correct and I have an error trying to render the preact component:
Uncaught (in promise) Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

(note that the project uses React 16.5)


Fixes and optimizations to compiler

This PR makes the compiler work even if you import constants. This had been broken.
It also commits a major optimization for Font.metrics, at least in Chrome and likely in other browsers.

I have to add: optimizing a web browser implementation that runs in a web browser is quite a fun trick!


 The error looks like the aspnetcore example app is failing to wire up the Tracer correctly so it fails to inject into WeatherForecast controller.
Locally, it hangs and doesn't return. I think it's stuck waiting for trace data to arrive.
Additional context
Recent CI build

Hmmm, locally this works. I noticed that that dockerfile curls against http whereas when I run this locally, I curl https. Could that be it?

Blegh, looks like that wasn't it. Definitely something different about the dockerized environment compared to a local one on my machine.

Hm. I may have missed something somewhere, but this failure seems intermittent or this has been fixed.

I'm finding that this seems to only fail on main? I might start looking into this a little more.

I'm finding that this seems to only fail on main? I might start looking into this a little more.

Looks like it's passed in the last 3 merges to main 🎉  I think it's okay to hold off on researching further until the next merge to main and see how it goes. If it passes, let's close and re-open if flakiness returns.


Cannot read property 'title' of null

If I provide a route with allowed query params in the server routes, and then try to open that route link without any query parameters, it results in an error:
Cannot read property 'title' of null

with server returning a 500 error.
I can fix it by using: if (!Object.keys(query).length) return {};
		urlQueryParameters: (params, query) => {
			if (!Object.keys(query).length) return {};
			const allowedKeys = ['abc'];
			const allowedQueryParams = pick(query, allowedKeys);
			if (Object.keys(allowedQueryParams).length !== allowedKeys.length) return null;
			return allowedQueryParams;
		},

I think checking the empty query should be the default behavior in this package. Or at least, a proper error must be thrown.

Indeed, it's up to the package user to take care of ensuring that their URL can be accessed with or without URL query parameters. Piling up checks into this package would end up in performance loss.

@PEM-- in that case, at least there should be a better error, right? That error is not at all helpful, and emerges from probably some parameter being null in this particular case.

Cannot read property 'title' of null comes from your app not from the package. Unless I didn't get your use case, we can't prevent mistakes in user's apps.
What could be done is, instead of simply returning an array, this package could provide an object that package user would fill with their error management. Something with a contract likes:
// When there's no error
{
  res: allowedQueryParams, // An array of allowed URL query parameters
}
// When there's an error
{
  httpCode: 404, // The error code the package user would like
  httpReason: 'title is a mandatory URL query parameter', // A reason for it
}

Sounds good.
I do not think that the error is because of my code. There is no .title in the code which would cause this. I can not find any in this package too. The only option remains is that the error is emanating from react or any other package. Will dig deeper sometime soon.

PR are welcomed and encouraged 😉
I'm closing this as it's more a question than an issue.


Put binaries into github releases?

I only just learned about s3cli from recent release notes of bosh-cli. The readme infers its primarily a CLI. Perhaps its handy for each github release to include the prebuilt versions from CI - which are a little easier for 3rd party CI systems to discover and download?

@drnic I'm curious about what use case you would have for consuming the s3cli. We don't really document that it exists because users shouldn't need to know that it exists :) It's more of an implementation detail of the Director / Agent.
That said, if you need to download and upload to s3-compatible blobstores with minimal configuration, this CLI might be useful.

I've been using awscli for S3 but then needed other clis to support gcs & Azure. If s3cli is going to be the communal code that bosh-cli is going to use to accsss diff blobstores then I thought I'd give it a try in lieu of awscli.
This assumption is all based on the bosh-cli release notes when it was mentioned that this repo existed with regards to GCS support.
I'm happy to help with docs/debugging/feedback directly for s3cli as I use it. The world needs more golang & cli multi-cloud tools.
On Fri, Oct 21, 2016 at 7:48 AM +1000, "Lyle Franklin"<EMAIL_ADDRESS>wrote:
@drnic I'm curious about what use case you would have for consuming the s3cli. We don't really document that it exists because users shouldn't need to know that it exists :) It's more of an implementation detail of the Director / Agent.
That said, if you need to download and upload to s3-compatible blobstores with minimal configuration, this CLI might be useful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm happy to help with docs/debugging/feedback directly for s3cli as I use it.

Great, feel free to open issues and PRs. The docs are pretty lacking as the only consumers so far are the BOSH team, so your-milage-may-vary...
I added a link to the S3 bucket containing binaries to the README: 6d3927fa3fdb2e52a5014cf5a92d5dbdf84f5565. You should be able to grab the latest via a regex with the Concourse S3 resource or similar. Optimistically closing this out, but feel free to re-open if the S3 bucket doesn't meet your use case.

Thx
On Wed, Nov 2, 2016 at 7:26 AM +1000, "Lyle Franklin"<EMAIL_ADDRESS>wrote:
Closed #15.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Use erlef/setup-beam and bump gha versions

Remove extra redirection. See https://github.com/erlef/setup-beam/issues/20

Thanks.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


chore: add tests for explorer api abuse to watchdog canister

This PR fixes the case when API provider responds with a text string instead of a valid JSON.

I don't understand how the title and description of this PR relate to the actual change. The changes that I see are making adjustments to logs and adding tests. How does that fix how we handle API abuse?

I don't understand how the title and description of this PR relate to the actual change. The changes that I see are making adjustments to logs and adding tests. How does that fix how we handle API abuse?

good catch, thank you! I must have been tired yesterday when debugging watchdog canister. switched error print messages to panics for debugging purposes and saw a reject message about abusing explorer api (also used 5s ping rate instead of a default 60s for debugging) and incorrectly concluded that getting a string instead of a proper JSON was causing the failure.
still I think it brings value to add such a test case for checking a correct handling of an unexpected text instead of a proper JSON. updated the PR title.


Monorepo (WIP)

Split into test-utils, server-test-utils, create-instance repos

TODO

Fix broken tests
Improve build/ test pipeline
Move scripts to package root

New structure:

packages

server-test-utils (published as @vue/server-test-utils)
test-utils (published as @vue/test-utils)
create-instance (private)
shared (private)

@eddyerburgh
test/specs/mounting-options/slots.spec.js  is not tested.


mount: umount dir when program ends with SIGINT (Ctrl+C) or SIGTERM

Tested the following scenarios:

external fusermount -u: rclone exits properly
Ctrl+C: rclone exits and umount dir
killall rclone: exits and umount dir
killall rclone with busy mountpoint: dir not umounted and the following message is printed

2017/03/17 11:23:03 Fatal error: failed to umount FUSE fs: exit status 1: fusermount: failed to unmount /tmp/rclone-mount: Device or resource busy

Related issue: #1244

Nice one, thank you!
Can you update the docs (in cmd/mount/mount.go) to describe what happens on the signals please?

Updated help docs in .go file and manpage also.

Thanks!  You don't need to update the man page - it is automatically made - I'll drop that chunk from the commit.
I've merged this in 788b6ce821fceff747238e1de5501f4d284abefb - thank you very much for your contribution :-)


Unstable order when reading spec from .json file

https://github.com/kean/CreateAPI/blob/87ba65d28a657ef7b94a758697cbf68d6075dbb9/Sources/CreateAPI/Generate.swift#L159-L160
In addition to not being thread-safe, JSONDecoder also does not appear to guarantee any explicit order of object keys.

Spec
{
  "openapi": "3.0.0",
  "info": {
    "version": "1.0.0",
    "title": "Order"
  },
  "paths": {
    "/container": {
      "get": {
        "responses": {
          "200": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/Container"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "Container": {
        "type": "object",
        "required": null,
        "properties": {
          "propertyOne": {
            "type": "string"
          },
          "propertyTwo": {
            "type": "string"
          },
          "propertyThree": {
            "type": "string"
          },
          "propertyFour": {
            "type": "string"
          }
        }
      }
    }
  }
}

Output
// Generated by Create API
// https://github.com/kean/CreateAPI
//
// swiftlint:disable all

import Foundation

public struct Container: Codable {
    public var propertyFour: String?
    public var propertyThree: String?
    public var propertyOne: String?
    public var propertyTwo: String?

    public init(propertyFour: String? = nil, propertyThree: String? = nil, propertyOne: String? = nil, propertyTwo: String? = nil) {
        self.propertyFour = propertyFour
        self.propertyThree = propertyThree
        self.propertyOne = propertyOne
        self.propertyTwo = propertyTwo
    }
}

struct StringCodingKey: CodingKey, ExpressibleByStringLiteral {
    private let string: String
    private var int: Int?

    var stringValue: String { return string }

    init(string: String) {
        self.string = string
    }

    init?(stringValue: String) {
        self.string = stringValue
    }

    var intValue: Int? { return int }

    init?(intValue: Int) {
        self.string = String(describing: intValue)
        self.int = intValue
    }

    init(stringLiteral value: String) {
        self.string = value
    }
}

The easiest workaround is to convert the .json spec to a .yaml spec beforehand.

Unfortunately, that seems to be the case. It's recommended to use YAML. OpenAPIKit uses ordered dictionaries to preserve the order of the keys when it can (YAML).
There is also an option to sort properties alphabetically which is disabled by default:
entities:
  isSortingPropertiesAlphabetically: true

The primary objective of this revision is to bring YAML into compliance with JSON as an official subset.
— YAML 1.2 Specification (2009)

It should be perfectly valid to use YAMLDecoder for .json documents.
This of course hinges on how closely Yams follows the spec.
I didn't run into any issues with the OpenAPI specs I tried (two small internal ones), but that feels like too small of a sample size to conclusively rule out any nasty edge cases.

If retaining order is important for your use-case, I recommend the Yams and FineJSON libraries for YAML and JSON respectively. Also keep in mind that JSON is entirely valid YAML and therefore you will likely get good results from Yams decoding of JSON as well (it just won't encode as valid JSON).
— OpenAPIKit Documentation

Not sure if "you will likely get good results" is good enough, but I'd argue that entity generation with JSON as input should currently be considered broken, as its behavior is unexpected for anyone unfamiliar with the JSON specification.
Would you be interested in a PR that switches the JSON parser over to Yams and adds tests?
It wouldn't be necessary to check in any JSON specs, as decoding a YAML spec with Yams and consequently encoding it with JSONEncoder does retain order.

I had a go at doing this, but I found a bug in Yams that is a slight blocker (it caused one of the specs that decodes a json configuration to fail):

https://github.com/jpsim/Yams/pull/351

Other than the empty string/optional issue though, Yams has been pretty good at handling our 31,500 line OpenAPI schema in JSON format, we've just been renaming it to .yml but not converting it from JSON.

https://github.com/kean/CreateAPI/blob/87ba65d28a657ef7b94a758697cbf68d6075dbb9/Sources/CreateAPI/Generate.swift#L159-L160
In addition to not being thread-safe, JSONDecoder also does not appear to guarantee any explicit order of object keys.
Spec
Output
The easiest workaround is to convert the .json spec to a .yaml spec beforehand.

Nigger

Fixed in 0.0.4! Thanks 🚀


Backup Policy unable to take Sanpshot of Reserved Instances

Hi @cmachler ,
I have created Backup and Retention policy for my EC2 instances.  The policy is executing successfully, however it is unable to find any instance in any regions. I have 80 instances running in "US East (N. Virginia)" regions and all instances are reserved.
PFA screenshot for reference and kindly suggest

if any changes are required for reserved instances.

You may want to check you have correct role assigned in the function. For troubleshooting you may want to create a test script to just print out the instances, and start troubleshooting. From what info you have provided I would have to guess its permissions related. I am closing the issue since I believe its permissions issue on your side, and you will need to troubleshoot that.


Update configure-server-endpoints-windows-defender-advanced-threat-pr…

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3381
Fixed the screenshot.

@mjcaparas - Can you please assist to check, approve and merge the content for this PR based on issue #3381?
Thank you.


wFreeRDP multiple issues

Hi,
I have a few issues with wFreeRDP and I have tried with multiple versions found here:
https://ci.freerdp.com/job/freerdp-nightly-windows/arch=win64,label=vs2013/
And from here:
https://cloudbase.it/freerdp-for-windows-nightly-builds/
*First of all i'm not getting any console output from wfreerdp not even wfreerdp /help or /version.

I cannot connect any rdp sessions from Windows server 2012 or 2016.
wfreerdp /v:Myip  - asks for user and password and then dies.
wfreerdp /v:Myip /u:Myuser /:uMypassword - dies right away

*Connection from a Windows 7/10 machine works better but only when using IP, Computer name or FQDN does not work. However if the remote computer is NOT domain joined FQDN works!
*Also when connecting to windows server 2008/2008 R2, Start Menu and other menus and buttons are black.
All this works with an old freerdp client I found on my hard drive of unknown version from 2016.
Thank you!

I still cannot connect any rdp sessions from Windows server 2012 or 2016! This wotks with version
...
[20:36:54:772] [4692:00000264] [DEBUG][com.freerdp.core.gcc] - Server rdp encryption method: NONE
[20:36:55:100] [4692:00000264] [DEBUG][com.freerdp.core.rdp] - recv Synchronize Data PDU (0x1F), length: 22
[20:36:55:100] [4692:00000264] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[20:36:55:100] [4692:00000264] [DEBUG][com.freerdp.core.rdp] - recv Control Data PDU (0x14), length: 26
[20:36:55:100] [4692:00000264] [DEBUG][com.freerdp.core.rdp] - recv Font Map Data PDU (0x28), length: 26
[20:36:55:100] [4692:00000264] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRX32
[20:36:55:100] [4692:00000264] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16
[20:36:55:115] [4692:00000264] [DEBUG][com.freerdp.client.windows] - Main thread exited with 131075
[20:36:55:115] [4692:00001274] [DEBUG][com.freerdp.client.windows] - Keyboard thread exited.
And... then... nothing... :(

You're missing the stderr output, add a 2>&1 at the end.

The output is the same using  "... 2>&1 > file" and "... >file"... ?

wfeerdp commandline (wfreerdp.exe /v:machine01 /u:rdpuser /d:domainname /p:secret /cert-ignore /gdi:sw /log-level:TRACE > log.log) is not working from window 2012r2. Please find below the log for the reference.
I am using the latest stable build # 620 from https://ci.freerdp.com/job/freerdp-nightly-windows/arch=win64,label=vs2013/
[07:01:19:551] [11860:0000345c] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[07:01:19:551] [11860:0000345c] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[07:01:19:551] [11860:0000345c] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[07:01:19:551] [11860:0000345c] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[07:01:19:566] [11860:0000345c] [DEBUG][com.freerdp.client.windows] - Main thread exited with 0
[07:01:19:566] [11860:000044e4] [DEBUG][com.freerdp.client.windows] - Keyboard thread exited.

@gramali you're not redirecting error messages, and from my local test this command line is working to my test machines.
Might be a simple issue with DNS not resolvable or user not allowed

@akallabeth thank you for your reply. same command working fine for me as well from my laptop windows 10 64 bit.  But not working from any server with windows 2012 R2. I am able to connect the machine from windows 2012 R2 server using MSTSC with same hostname and username. So no issue with DNS and user account. I believe /log-level:TRACE > log.log will log all the message (Trace, Debug, Error, Warn). Please help to resolve this.

@gramali no, the redirektion skips the errors (or do you see one in your log?)

@akallabeth, I don't see any errors in the log. same command working fine in windows 10 and window server 2016. will older build of wreerdp.exe work. where can I download older versions of wreerdp.exe

That is what I am trying to tell you, you only redirect stdout to the file, NOT stderr which is where errors are written to....

@akallabeth Please find below stderr thrown in my windows 2012 R2
[17:14:56:022] [9184:000010e8] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_PASSWORD_CERTAINLY_EXPIRED [0x0002000F]
[17:14:56:022] [9184:000010e8] [ERROR][com.freerdp.core.transport] - BIO_read returned an error: error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error

Looks like a kerberos/domain related error.
Kerberos support is currently not very reliable :/

I am using wfreerdp latest build and not working in windows 2012 R2. pls find the command and logs (STDOUT, STDERR). pls help to resolve this.

wfreerdp.exe /v:machinename /u:user01 /d:domainname /p:secret /cert-ignore /gdi:sw /log-level:TRACE > STDOUT.log

wfreerdp.exe /v:machinename /u:user01 /d:domainname /p:secret /cert-ignore /gdi:sw /log-level:TRACE 2> STDERR.log

STDOUT.log
STDERR.log

@gramali please test with our builds (recent ones ;)) the debug messages suggest you either have a custom build or a very old one. Attach wfreerdp.exe /buildconfig so we know what exactly you're using.

@akallabeth sorry the logs posted in the previous when using the wfreerdp 1.1 version. pls find attached logs (STDOUT, STDERR) while tested with latest wfreerdp.
stderr.log
stdout.log

@akallabeth can you help on how to recompile with OpenH264 support for windows and how to create commandline interface single wfreerdp.exe.

I am trying to recompile with OPENH264 support. I am getting error message "Could NOT find OpenH264 (missing: OPENH264_LIBRARY OPENH264_INCLUDE_DIR)". Please find attached cmk
Cmake Command
c:\GitProjects>cmake -DWITH_OPENH264=ON -DBUILD_SHARED_LIBS=OFF -S . -B C:\GitProjects\FreeRDPBuild\
Cmake Logs
CMakeError.log
CMakeOutput.log

Now I am able to compile using below command. But when I MSBUILD  throws error C:\GitProjects\FreeRDP\libfreerdp\codec\h264_openh264.c(29): fatal error C1083: Cannot open include file: 'wels/codec_def.h': No such file or directory [c:\GitProjects\FreeRDPBuild\libfreerdp\free
rdp.vcxproj]. Can you someone help on this.
C:\GitProjects\FreeRDPBuild>cmake -DWITH_OPENH264=ON -DOPENH264_LIBRARY=C:\GitProjects\OpenH264\opwi
n32\openh264-1.8.0-win32.dll -DOPENH264_INCLUDE_DIR=C:\GitProjects\OpenH264\opwin32\ -DBUILD_SHARED_
LIBS=OFF -S . -B C:\GitProjects\FreeRDPBuild\

I solved by installing media foundation feature in the server (Add Features/Roles). But I could not recompile with OPENH264 support.


$this->get() is empty on POST/PUT/DELETE

Since you can also do POST test.php?a=b&c=d  the rest server needs to populate the _get_args array in every case, not only when the request method is GET

Could you not use CI's input->get() method for that case ?

Oh, I haven't thought of that.

Either way, the fix is simple. Just move the _get_args assignment out of the switch/case

But is that rest-like though?
I honestly don't know.. you're not GETting, you're POSTing...
maybe the right approach would be to take the query string element out of your urls and make them a proper uri (e.g. /test/a/b/c/d/ ... i'm not sure what the logic behind your url query string structure is..)

Yes you are probably right.


Count of Conformer parameters mismatch with that in the paper

In the Conformer original paper, the number of parameters are

However, with the implementation in this repo, the number of parameters are slightly different
Conformer  small: 10.16 M
Conformer medium: 31.86 M
Conformer  large: 120.11 M

I get the size with this script
from conformer import Conformer

def count_parameters(model) -> int:
    return sum(p.numel() for p in model.parameters() if p.requires_grad)

models = {
    'small': Conformer(
        num_classes=1000,
        input_dim=80,
        encoder_dim=144,
        decoder_dim=320,
        num_encoder_layers=16,
        num_decoder_layers=1,
        num_attention_heads=4,
        conv_kernel_size=31
    ),
    'medium': Conformer(
        num_classes=1000,
        input_dim=80,
        encoder_dim=256,
        decoder_dim=640,
        num_encoder_layers=16,
        num_decoder_layers=1,
        num_attention_heads=4,
        conv_kernel_size=31
    ),
    'large': Conformer(
        num_classes=1000,
        input_dim=80,
        encoder_dim=512,
        decoder_dim=640,
        num_encoder_layers=17,
        num_decoder_layers=1,
        num_attention_heads=8,
        conv_kernel_size=31
    )
}

for size, m in models.items():
    print("Conformer {:>6}: {:.2f} M".format(size, count_parameters(m)/1e6))

Since the convolution layer kernel size couldn't be set to 32, I just set it to 31. But this won't make such difference in number of params.

Also, num_classes affects.

I'm curious, too. I am only speculating that there may be details not mentioned in the paper.


Change how spaces in component names and attributes are handled

Add back spaces into the French Translation. Yail generation should
now always use the english names of component properties, methods and
events. So spaces or other characters that are not legal Java
identifiers can now appear in translations of these.
Component types also can now have spaces. When a component is dragged
onto the designer, spaces and single quotes are now converted to
underscores.
Change-Id: I03e49588528c06b6f853a5ef5bfe5ae11266a51e

@afmckinney @halatmit This code is on ai2-test and Adel Kassah (who did the French translation and original stumbled on this issue) says it works with his test cases.

@halatmit Actually, I'm not using that routine anymore. I flushed it.

LGTM

rebased


IceCube: SceneDuration

Feature to calculate the time from the start of a scene to the end.
Once we have the scene name included with all events, this should be made a "per-count" feature.

Note, I've put in a request for Ross to give us scene_begin and scene_end events, instead of scene_change. This will be important for SceneDuration, since we can just request those events instead of needing to look at every event of a scene.


rush update --full

Reason for rush update --full:
rhea seems to have downgraded to 1.0.21 in the lock file (along with some other dependencies)

https://github.com/Azure/azure-sdk-for-js/blame/b18a95268f1cc120b33c88bf2a62f76ebd6272e1/common/config/rush/pnpm-lock.yaml#L5808


Task - Edit TaxonName - missing relationships

validating and potentially validating relationships are missing from the ListAll

Nomenclatural code?  Class?
On Tue, Apr 30, 2019 at 2:30 PM Dmitry Dmitriev<EMAIL_ADDRESS>wrote:

validating and potentially validating relationships are missing from the
ListAll
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/issues/962, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAFQSEVCIJ2LWKZ25GAL53PTCM4HANCNFSM4HJPQQQQ
.

ICZN. TaxonNameRelationships. I was on a species page. But I assume this is true for all codes.

All ICZN (and other code) TaxonNameRelationships should be listed. At the moment, I can still access them using the search interface.

@proceps You must set the assignable property for them to be included in the all list.

I pushed changes. It is partially resolve the issue. The problem now is that the relationships are now listed, but their parent (for the hierarchy reason is not). Parent should always be visible and greyed out if self.assignable is false.

@proceps which parents are not visible? and what is the const value of those?

@jlpereira We have a hierarchy of classes (relationships and classification). Each class and subclass have property self.assignable. That is how you filter classes to display. When the subclass .assignable is true, it is displayed on the tree (for example conserved). But the parent of this class (Validating) has .assignable is false. It is out of the tree, so, conserved subclass does not have a parent on the tree. Could you please add all classes and subclasses to the tree, and permanently grey out all those which have self.assignable = false.

@Dmitriev, Dmitry A<EMAIL_ADDRESS>We need to have you configure
the JSON response (taxon_name_relationships/relationship_types.json IIRC)
so that @jlpereira can work with response.  If it doesn't look right the
constants are in config/initializers/constants/...
On Tue, Jun 4, 2019 at 7:41 PM Dmitry Dmitriev<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/5597748/58922362-24e13700-8700-11e9-9307-1c4c445b75d8.png
@jlpereira https://github.com/jlpereira We have a hierarchy of classes
(relationships and classification). Each class and subclass have property
self.assignable. That is how you filter classes to display. When the
subclass .assignable is true, it is displayed on the tree (for example
conserved). But the parent of this class (Validating) has .assignable is
false. It is out of the tree, so, conserved subclass does not have a parent
on the tree. Could you please add all classes and subclasses to the tree,
and permanently grey out all those which have self.assignable = false.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SpeciesFileGroup/taxonworks/issues/962?email_source=notifications&email_token=AAAFQSC3MAKAJQ7GHSFJLDTPY4DVJA5CNFSM4HJPQQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6IOHI#issuecomment-498894621,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAFQSBV4ZOKHC6BN75UBLTPY4DVJANCNFSM4HJPQQQQ
.

The reason why some classes are not displaying in the tree view is because it didn't have subject_status_tag or object_status_tag, this is needed to display the name in the tree. Otherwise it won't be included.

Here is an example with TaxonNameRelationship::Iczn::Validating

OK, I create the label based in the last part of the class type. For example, in the case of 'TaxonNameRelationship::Iczn::Validating' the label will be 'Validating'. This will be done everytime the class is not founded in 'all' list.

Let me know @proceps if now you're getting the correct list

Thanks @jlpereira, will be able to check in few days. Out of town now.

I think this is already solved. Closing.


Alex  mobile enter name app crash

Comments above are great. Also, per our discussion during paired programming, I've tested it in Android and the behaviour looks good. I might be nitpicking here but would it be possible to clear the error message once both of the text fields are populated? It will prevent any confusion if there's a slowdown on the device.  My android simulator is pretty slow but you can check out the video to see there might be some confusion when someone fills out the first/last name and hits submit but still sees the error message.
https://user-images.githubusercontent.com/79417944/210428081-b29b66a5-fdd9-4688-9ee2-1973a71a0566.mp4

I think getting rid of the error message once both inputs are populated by the user should not be a difficult fix and I will definitely look into it.

I am closing this PR as it has been superseded by: https://github.com/rightoneducation/righton-app/pull/512


Question: Does loadStripe function accepts restricted key?

Calling loadStripe with restricted key that has Write Tokens permission returns an error. Is this an expected behavior and not supported?

loadStripe is simply a loader for the Stripe.js Web Client SDK, which takes a publishable key. Restricted access API keys are still secret keys that should not be published in clients.
If you're trying to use API methods on your server, you can use stripe-node.


Change Default Readme

As we know, our readme file still in default gatsby template format. Please make it cleaner and suitable for rantaudev information

Since I'm new here and wanna to contribute to an open source project.
I wanna ask, what information should be include in this README? and in what language? Bahasa or English ?

should be good if we start it with our local language. Bahasa. You can provide information like our foundation value in https://github.com/rantaudev/meeting/blob/master/meeting-01.md

okay, i'll do it

im new on opensource , so other than that (readme) can i add new page like for showing cards exmaple about blogs post,
i havent use gatsby before but recently i use react,

that is good @rahulsya. you can start contribute in our repo. but first, we have to build wireframe UI/UX before developing the website.

oh ok ,i have a several card components that i create before.


Too many thread pools

google-cloud-pubsub is starting a thread pool to process incoming messages:
            @stream_pool.map do |stream|
              Thread.new { stream.start }
            end

activejob-google_cloud_pubsub is doing the same:
pool = Concurrent::ThreadPoolExecutor.new(min_threads: @min_threads, max_threads: @max_threads, max_queue: -1)

... effectively duplicating the efforts of google-cloud-pubsub, if I'm not mistaken?

Exactly. Earlier versions of google-cloud-pubsub did not use thread pools, but now it's an extra feature. I am going to fix this. Thank you very much for your attention!

could #6 be the solution for this issue ?


ability to flush user repo cache

This pull request gives us the ability to flush the user repository cache. This will finally resolve the annoying issue that arises when you create a new repository in GitHub, but then it takes 30 minutes for it to appear in Drone.


Shift-Enter stops advancing to next cell after some time

Intermittently, but frequently, when I run a cell in a notebook the vertical bar that denotes the active cell doesn't advance from the current to the next cell when I run via Shift-Enter. This seems to occur after working with the same notebook for some time. Closing and reopening "fixes" the issue for a time then eventually it re-occurs. I'm using python notebooks
This started a few releases ago, I'm fairly sure when the "new" notebook system was released.
Environment data

VS Code version: 1.61.2
Jupyter Extension version (available under the Extensions sidebar): v2021.9.1101343141
Python Extension version (available under the Extensions sidebar): v2021.10.1365161279
OS (Windows | Mac | Linux distro) and version: Ubuntu 20.04
Python and/or Anaconda version: 3.8.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pyenv
Jupyter server running: Local

Expected behaviour
Running a cell via Shift-Enter should move the cursor to the next cell
Actual behaviour
After working with any notebook for some time, eventually Shift-Enter keeps running the same cell.
Steps to reproduce:
Intermittent so not able to reproduce reliably.
Logs
I've not seen anything in the logs when this occurs.

Do you see the blue line move to the next cell? Is it running a cell different from the selected one (with the blue line on the left)?

No the blue line stays on the same cell rather than moving to the next. So Shift-Enter keeps running the same cell over and over

Not sure what the issue would be here, a gif/screen recording might help.

Next time it happens I'll try and remember to record. As I said it's intermittent, and I don't use notebooks every day so there may be a delay before I get to it.

So just an update on this, it's happened several times since I reported. The problem is I cannot make a screen recording.
The issue is "fixed" by switching focus away from the vscode window and then back again. So there's no way to start recording as each time it happens I have to switch focus from vscode and when I switch back the problem has gone.

Looks to be the same as #133038. I don't know if there if there is a fix for this yet, but there is a larger discussion there.

@harripj yes I think you're right. I'll close this.


Unable to generate workflows file using cookiecutter

Overview
When using cookiecutter https://github.com/ZenithClown/flask-docker-template not able to reproduce files when using generate_cicd_files == yes.
Steps to Reproduce

Create a new template directory using cookiecutter https://github.com/ZenithClown/flask-docker-template
Choose generate_cicd_files == yes (option 1).

Expected Behavior
Should create all workflows and CICD operation files.
Actual Behavior
(Py37MLOPs) D:\TEMPLATES>cookiecutter https://github.com/ZenithClown/flask-docker-template
You've downloaded C:\Users\debma\.cookiecutters\flask-docker-template before. Is it okay to delete and re-download it? [yes]:
project_name [My Project]: flask-api
repository_name [flask-api]:
author_name [Your name (or your organization/company/team)]: Debmalya Pramanik
description [A short description of flask-api.]: A template of flask-api built using cookiecutter.
Select open_source_license:
1 - MIT
2 - BSD-3-Clause
3 - No license file
Choose from 1, 2, 3 [1]: 1
Select generate_cicd_files:
1 - yes
2 - no
Choose from 1, 2 [1]: 1
Unable to create file '.github\workflows\CodeQL-Analysis.yml'
Error message: 'matrix' is undefined
Context: {
    "cookiecutter": {
        "_template": "https://github.com/ZenithClown/flask-docker-template",
        "author_name": "Debmalya Pramanik",
        "description": "A template of flask-api built using cookiecutter.",
        "generate_cicd_files": "yes",
        "open_source_license": "MIT",
        "project_name": "flask-api",
        "repository_name": "flask-api"
    }
}

Context
Python Version : 3.7
Operating System : Windows-10
Desktop Environment : NA

Looks like file {{cookiecutter.project_slug}}/.github/workflows/build.yml contains some ${{ matrix.os }} which confuse cookiecutter. If this file does not need to be rendered, perhaps this might help fix the issue

Originally posted by @c-martinez in https://github.com/NLeSC/python-template/issues/64#issuecomment-631735874


fix: ignore unreachable hosts

Hosts like workstations won't always be reachable so they should be ignored as part of deployment

:tada: This issue has been resolved in version 1.4.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How to prevent exposure of real IP

When disconnecting in use, how to disconnect the network to prevent exposure of the real IP

Is this happening to you?
I thought when there was an unexpected disconnect, Outline would completely block the network, until you open the Outline app.
Are you experiencing a fall back to the normal network?

Is this happening to you?
I thought when there was an unexpected disconnect, Outline would completely block the network, until you open the Outline app.
Are you experiencing a fall back to the normal network?

We don't intentionally block anything as far as I know.  @kls1361 do you mean that you're afraid that you will ezpose your IP address somewhere when you disconnect from your Outline server?

We don't intentionally block anything as far as I know.  @kls1361 do you mean that you're afraid that you will ezpose your IP address somewhere when you disconnect from your Outline server?


cutorch failure in CUDA 8

The below test code for image resize results in an error:
Specs:
Ubuntu 14.04
CUDA-8
OpenCV 3.2 / OpenCV 3.1 / OpenCV 3.1 (with CUDA 8 support)
Latest Torch-7and related packages
GPU: Titan X Pascal
Code:
require 'cutorch'
local cv = require 'cv'
require 'cv.cudawarping'
require 'cv.highgui'
require 'cv.imgcodecs'
require 'image'

cutorch.setDevice(3)
local img = cv.imread {arg[1] or 'lena.jpg', cv.IMREAD_COLOR}
print("Read image - done")
local imgCUDA = img:float():cuda() / 255
print("Cuda conversion - done")
for i=0,100,1
do
  print(i)
  local resized = cv.cuda.resize{imgCUDA, {1024, 768}}
  print("Resize - done")
  print(resized:size())
  print(resized:type())
  image.save('lenaresized.png',resized:transpose(1,3):transpose(2,3))
end

The output of the above test code is below:
Read image - done
Cuda conversion - done
0
Resize - done
  768
 1024
    3
[torch.LongStorage of size 3]

torch.CudaTensor

.
.
.

15
Resize - done
  768
 1024
    3
[torch.LongStorage of size 3]

torch.CudaTensor
THCudaCheck FAIL file=/tmp/luarocks_cutorch-scm-1-1283/cutorch/lib/THC/generic/THCStorage.c line=182 error=17 : invalid device pointer
/home/user/torch/install/bin/luajit: cuda runtime error (17) : invalid device pointer at /tmp/luarocks_cutorch-scm-1-1283/cutorch/lib/THC/generic/THCStorage.c:182

There is some memory conversion(?) issue after 15 times of looping. The corresponding line in THCStorage.c is
THCudaCheck(
        (*self->allocator->free)(self->allocatorContext, self->data));

This code runs in CUDA 6.5/OpenCV 3.1/ Torch 7. Does torch-opencv support CUDA-8?
Could someone look into this issue?

Hi,
unfortunately, I still don't have a machine with GPU to test on :(
Can you try this code? What's the output?
require 'cutorch'
local cv = require 'cv'
require 'cv.cudawarping'
require 'cv.highgui'
require 'cv.imgcodecs'
require 'image'

cutorch.setDevice(3)
local img = cv.imread {arg[1] or 'lena.jpg', cv.IMREAD_COLOR}
print("Read image - done")
local imgCUDA = img:float():cuda() / 255
print("Cuda conversion - done")
local img2 = imgCUDA:clone(); img2 = nil; collectgarbage()
print("Deallocate image - done")
local resized = cv.cuda.resize{imgCUDA, {1024, 768}}
print("Resize - done")
print(resized:size())
print(resized:type())
resized = nil; collectgarbage()
print("Deallocate resized image - done")

The error is the same. It does not execute the last statement print("Deallocate resized image - done").
Read image - done
Cuda conversion - done
0
Deallocate image - done
Resize - done
  768
 1024
    3
[torch.LongStorage of size 3]

torch.CudaTensor
THCudaCheck FAIL file=/tmp/luarocks_cutorch-scm-1-1283/cutorch/lib/THC/generic/THCStorage.c line=182 error=17 : invalid device pointer
/home/ipcv/torch/install/bin/luajit: cuda runtime error (17) : invalid device pointer at /tmp/luarocks_cutorch-scm-1-1283/cutorch/lib/THC/generic/THCStorage.c:182

The code works with CUDA 6.5/OpenCV 3.1/ Torch 7 on GTX-980 (5.2 arch).
It shows the above error with CUDA 8.0 on Titan-X (6.1 arch).


added TowerOfHanoi example

added a new file towerOfHanoi_example.py within recursion folder.

Tower of Hanoi Accepted fixed #11


Release Candidate

New terms added:

ID
Label

OBI:0003335
diffusion weighted magnetic resonance image data set

OBI:0003336
functional magnetic resonance image data set

OBI:0003337
resting state functional magnetic resonance image data set

OBI:0003338
task-based functional magnetic resonance image data set

OBI:0003339
perfusion weighted magnetic resonance image data set

OBI:0003340
proton density magnetic resonance image data set

OBI:0003341
T1 weighted magnetic resonance image data set

OBI:0003342
post-Gd T1 weighted magnetic resonance image data set

OBI:0003343
T1 weighted GRE magnetic resonance image data set

OBI:0003344
high resolution T1 weighted magnetic resonance image data set

OBI:0003345
baseline high resolution T1 weighted magnetic resonance image data set

OBI:0003346
follow-up high resolution T1 weighted magnetic resonance image data set

OBI:0003347
T1 weighted SE magnetic resonance image data set

OBI:0003348
T2 weighted magnetic resonance image data set

OBI:0003349
T2 weighted FLAIR magnetic resonance image data set

OBI:0003350
T2 weighted FSE magnetic resonance image data set

OBI:0003351
T2 weighted SE magnetic resonance image data set

OBI:0003352
T2 weighted STIR magnetic resonance image data set

OBI:0003353
T2* weighted GRE magnetic resonance image data set

OBI:0003357
brain region atlas image data set

OBI:0003358
probabilistic brain region atlas image dataset

OBI:0003359
deterministic brain region atlas image data set

OBI:0003360
image segmentation map

OBI:0003361
lesion mask

OBI:0003362
T1 lesion mask

OBI:0003363
T2 FLAIR lesion mask

OBI:0003553
intragastric administration

OBI:0003554
intracolonic administration

OBI:0003555
vaginal administration

OBI:0003556
topical administration

OBI:0003557
cervical administration

OBI:0003558
conjunctival administration

OBI:0003559
intratracheal administration

OBI:0003560
intra-amniotic administration

OBI:0003561
intra-arterial administration

OBI:0003562
intracerebral administration

OBI:0003563
intracranial administration

OBI:0003564
intraepidermal administration

OBI:0003565
intralymphatic administration

OBI:0003566
lymph node administration

OBI:0003567
urethral administration

OBI:0003568
skin scarification administration

OBI:0003569
intrauteral administration

OBI:0003570
intracarotid administration

OBI:0003571
intraocular administration

OBI:0003572
intraplacental administration

OBI:0003573
intrarectal administration

OBI:0003574
intrasplenic administration

OBI:0003575
scratching

OBI:0003603
intratumoral administration

OBI:0003607
disease causation objective

OBI:0003608
disease severity reduction objective

OBI:0003609
disease prevention objective

OBI:0003610
reactant role

OBI:0003611
precursor role

OBI:0003612
electron microscopy assay determining the 3D structure of a T cell epitope:MHC:TCR complex

OBI:0003613
electron microscopy assay determining the 3D structure of a MHC:ligand complex

OBI:0003614
disease prevalence reduction objective

OBI:0003615
antibody purification of MHC protein complex

OBI:0003616
antibody purification of MHC class I protein complex

OBI:0003617
antibody purification of human MHC class I protein complex

OBI:0003618
antibody purification of HLA protein complex with A2 serotype

OBI:0003619
antibody purification of HLA protein complex with A24 serotype

OBI:0003620
antibody purification of HLA protein complex with A2 serotype and/or HLA protein complex with A28 serotype

OBI:0003621
antibody purification of HLA protein complex with A29 serotype

OBI:0003622
antibody purification of HLA protein complex with B27 serotype

OBI:0003623
antibody purification of HLA-C protein complex

OBI:0003624
antibody purification of pig MHC class I protein complex

OBI:0003625
antibody purification of cattle MHC class I protein complex

OBI:0003626
antibody purification of rat MHC class I protein complex

OBI:0003627
antibody purification of mouse MHC class I protein complex

OBI:0003628
antibody purification of H2-Dd protein complex

OBI:0003629
antibody purification of H2-Db protein complex

OBI:0003630
antibody purification of H2-Kd protein complex

OBI:0003631
antibody purification of H2-Ld protein complex, H2-Db protein complex, and/or H2-Dq protein complex

OBI:0003632
antibody purification of H2-Dd protein complex and/or H2-Kd protein complex

OBI:0003633
antibody purification of mouse MHC class I protein complex with H2-b haplotype and/or mouse MHC protein complex with H2-p haplotype

OBI:0003634
antibody purification of H2-Kb protein complex, H2-Ks protein complex, and/or H2-Kq protein complex

OBI:0003635
antibody purification of pig MHC class I protein complex, cattle MHC class I protein complex, and/or human MHC class I protein complex

OBI:0003636
antibody purification of MHC class II protein complex

OBI:0003637
antibody purification of cattle MHC class II protein complex

OBI:0003638
antibody purification of human MHC class II protein complex

OBI:0003639
antibody purification of HLA-DP protein complex

OBI:0003640
antibody purification of HLA-DR protein complex

OBI:0003641
antibody purification of HLA protein complex with DQ3 serotype

OBI:0003642
antibody purification of mouse MHC class II protein complex

OBI:0003643
antibody purification of H2-IA protein complex

OBI:0003644
antibody purification of H2-IAg7 protein complex

OBI:0003645
antibody purification of H2-IAd protein complex

OBI:0003646
antibody purification of mouse MHC class II protein complex and/or rat MHC class II protein complex with RT1-A haplotype

OBI:0003647
tandem mass spectrometry analysis

OBI:0003648
liquid chromatrography mass spectrometry analysis

OBI:0003649
liquid chromatography-tandem mass spectrometry analysis

OBI:0003650
Illumina Infinium MethylationEPIC v2.0 BeadChip

OBI:0003651
multidimensional fatigue inventory score

This release candidate is missing a date, because of an error in the script. I'll close this without merging and we'll try again.


[FEATURE REQUEST] Add posibility to provide custom hostnames

Is your feature request related to a problem? Please describe.
Currently, there is no option to provide a custom VM hostname via epicli.
The hostname is set up referencing inventory hostname.
Describe the solution you'd like
Current: [prefix][clustername]-kubernetes[master/node]vm[x]
Needed: [prefix][clustername]-kubernetes[master/node]vm[x].[domain.name]
but it should allow to set up anything you can imagine :space_invader:
Additional context
Internal team request, if possible prepare a workaround they could apply to their LTS deployment.
Please check kind: infrastructure/virtual-machine. Maybe specification.name should be the right place for that? Right now it's overwritten after manifests merge.

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Schema updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

So this is only for Azure? Or we want this also on AWS?

The fr/fix was requested for Azure but afaik the team also uses AWS.

After some more research I found several issues with the task described above:

For both AWS and Azure the infrastructure/virtual-machine document type represents a template for a group of VM`s of a certain component . This template is then being used to generate the Terraform VM definitions on Azure and auto-scaling groups on AWS.  Any VM specific config is generated by the providers:

Adding a mechanism to specify something like a hostname per VM would require some massive changes which might not be backwards compatible.
While the hostname Azure is generated and explicitly set on AWS the hostnames are provided automatically by the auto-scaling groups. This makes it impossible without reworking a large part of the Terraform to set the hostnames easily. Probably it requires the removal of the auto-scaling groups in favor of a similar approach we have with Azure now. I think there already is an issue to do this as the auto-scaling groups are responsible for more issues regarding scaling components anyway.
A work around to change hostnames on older clusters will be expensive to provide as we need to check every component that might have configuration that uses said hostname. It will be similar as some of the outdated scripts we have now for changing IPs for certain components: https://github.com/epiphany-platform/epiphany/tree/develop/tools/ip_change

Because of these above issues I propose an easier approach to provide the team the ability to add the domain at the end of the hostname and only for Azure in the form as an additional cloud parameter in the root cluster-config document:
kind: epiphany-cluster
name: default
provider: azure
title: Epiphany cluster Config
specification:
 ...
  cloud:
    hostname_domain_extension: **domain**
 ....

This hostname_domain_extension field, if defined will be added to each machine hostname separated by a .. The same as machine VM image definitions it will be retained across Epicli versions and re-applies as changing this will cause the re-creation of the VM as changing VM images would do before.

Tested by @rafzei https://github.com/epiphany-platform/epiphany/pull/2790#issuecomment-1002068421.
Thanks man :heart:

@seriva what about adding extra validation for the hostname?
ERROR cli.engine.terraform.TerraformCommand - Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidParameter" Message="Linux host name cannot exceed 64 characters in length or contain the following characters: ` ~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \\ | ; : ' \" , < > / ?." Target="computerName"


I Tryed to do /vehicle menu but its not working the comand

when i try the command /vehicle menu the command its not running i did the mtv vehicle plugin on my aternos server but its not working

Use 2.5.3 (supports 1.20.4)


add info toast back

Thank you for contributing to the Cohere Toolkit!

[ ] PR title: "area: description"

Where "area" is whichever of interface, frontend, model, tools, backend, etc. is being modified. Use "docs: ..."  for CI changes.
Example: "deployment: add Azure model option"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change

[ ] Add tests and docs: Please include testing and documentation for your changes

[ ] Lint and test: Run make lint and make run-tests

AI Description

This pull request updates the useNotify hook and its usage in the UpdateAgent component.
Summary
The useNotify hook now includes an info function, which displays an informational toast message with a duration of 5000. This change is reflected in the UpdateAgent component, where the use of the success function has been replaced with info to display a message when an agent is updated.
Changes

The useNotify hook in toast.ts now includes an info function that takes a message string as an argument and displays it as an informational toast.
The UpdateAgent component now uses the info function from useNotify instead of success to display a message when an agent is updated successfully.

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

Project coverage is 74.99%. Comparing base (7a29e85) to head (dcb02c9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #711   +/-   ##
=======================================
  Coverage   74.99%   74.99%
=======================================
  Files         261      261
  Lines       11489    11489
=======================================
  Hits         8616     8616
  Misses       2873     2873

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


Suppress nvcc warning

Close #6943.

/test mini

Confirmed fixed in the CI build logs too (try searching __device__ or __host__). The CI failures seem irrelevant and known.

@leofang LGTM. Thanks!

@kmaehashi @asi1024 Perhaps this code-fix PR can be backported?


simplify optimized build documentation

Rationale for this change
Some of the instructions in the optimized build section are not needed
What changes are included in this PR?
Remove unused build config.
Are there any user-facing changes?
no

Since 0.2.28, we have already deprecated cache-friendly for snmalloc v1 series.

Thanks @houqp


Polish existing feature to select boundaries based on existing layers

Overview
Links to jira tickets

https://quartech.atlassian.net/browse/BHBC-1094

This PR contains the following changes

Polish existing feature to select boundaries based on existing layers

This PR contains the following types of changes

[x] New feature (change which adds functionality)
[x] Enhancement (improvements to existing functionality)

How Has This Been Tested?

Locally

Screenshots

This UI improvement should help
When layer is not selected:

disable or remove the Hide layer button

When layer is selected:

Show the Hide layer button
Display the name of the layer selected.


App entry point

My application root is by convention app. It starts like this:
 aurelia.start().then(() => aurelia.setRoot());
I noticed that app is not loaded through any of the module.hot.accept paths in aurelia-loader-webpack and hence does not support HMR. Changing code in app.ts triggers a full reload.
app.html on the other hand goes through module.hot.accept and triggers a hot reload, but the view is only updated the very first time. After that, it still triggers a hot reload but the view is not updated anymore.
I don't have that problem with other views, they refresh fine.

Interesting. Any thoughts on how to correct this?

Unfortunately no.
I have not debugged where app gets loaded and why it doesn't go through the normal code path.
Then for the app.html weird behavior, I must admit I don't fully understand yet what the aurelia HMR module does, so no idea what happens here.

This is where app is inferred when no root is specified: https://github.com/aurelia/framework/blob/d650b01993aa2db81f8c9587793b73b2d1f0476d/src/aurelia.js#L133

@jods4  maybe can be closed?

@Alexander-Taran was there a fix for that?

@jods4, sir.  Can't know sir.
I'm asking you (-:
Maybe it was resolved and you are already happy?

Nothing that I know of.


Add support to update graph

We can add vertexes and edges via the API. Update the modify to handle this an other options.

Done.


Add missing translation for "Syntax error"

It's used in the import warning dialog.
The code has never been triggered yet because there's both a crash and a early return before it, but if that get's fixed then this has to be added too.

Superseded by #540


Long Press actions

@Niteshkr123 you can now work on this

@Niteshkr123 you can now work on this

Yeah sure. Thank you for assigning :)

Yeah sure. Thank you for assigning :)