Graphs for Roy Lecture

We need a variety of graphs to illustrate the workings of the original Roy Model. I started to draft the lecture here: https://github.com/policyMetrics/sandbox/blob/master/lectures/generalized_roy/prototype.ipynb. Please include the code for the graphs here as well.

We totally forgot about these issues. @tobiasraabe is already working on them.


Allow calc function interpolation when declaring CSS custom properties.

In the example case --test: calc(#{$c} + 1); , #{$c}  is mistakenly identified as an error. Interpolation is used in SassScript to inject dynamic values into a CSS custom property. This allows interpolation when declaring CSS variables.

Thanks! I wonder if we should ignore the custom properties by default, or put this behind an option?

@kristerkari it should always ignore custom properties since these passed through to CSS as-is, for any SassScript interpolation is required.

got it, thanks :)


Document.NextVersion improvement to prevent malicious reader

Problem
Document.NextVersion defines the anchorID of the next document version. A malicious reader could add a random hash with the anchorID of the nextVersion and block the anchoring mechanism for the next document versions.
Solution
One way without trusting the reader could be the following way:
The coredocument gets a new field called NextVersionSecret which is a random number. The NextVersion would be calculated in the following way:
Document.NextVersion = sha3(Document.NextVersionSecret).
the Commit method in the anchorRepository would be changed in the following way:
...
commits[sha3(_anchorId)] = _documentRoot;
...
}

On the node we would change the anchorId to NextVersionSecret instead of NextVersion for a AnchorCommit. Only a node with the NextVersionSecret could commit the next anchor.
A reader would receive with ACL every field except the NextVersionSecret.  He  would receive the NextVersion  field to verify if he has the latest version but he can’t commit a fake next anchor.

redundant with #778


Need ability to provide imagePullSecrets for jobs generated by Plans for private registries

Is your feature request related to a problem? Please describe.
I am currently trying to deploy this system-upgrade-controller and all related pods in an airgap. We utilize a private registry to pull containers from and I do not have the ability to insert imagePullSecrets into the apply-server-plan-on-* pods - this affects both the rancher/rke2-upgrade and the rancher/kubectl containers
Describe the solution you'd like
I want to be able to add imagePullSecrets on the plan and have that flow through into the jobs that get created
Describe alternatives you've considered
The only alternative right now is to enter credentials in the registries.yaml file when booting rke2. This is problematic as my deployment process usually has the rke2 cluster running before my private registry is available and the registry credentials are randomly generated

We found that configuring the serviceaccount to use imagepullsecrets also works as an alternative: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account but going to keep this open as the issue itself is still valid as an enhancement.

We found that configuring the serviceaccount to use imagepullsecrets also works as an alternative: kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account but going to keep this open as the issue itself is still valid as an enhancement.

incase anyone needs an example of this using fluxcd's kustomize controller:
apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
kind: Kustomization
metadata:
  name: rke2-system-upgrade-controller
  namespace: bigbang
spec:
  interval: 1m
  sourceRef:
    kind: GitRepository
    name: rke2-system-upgrade-controller-repo
  path: .
  prune: true
  images:
  - name: rancher/system-upgrade-controller
    newName: private.registry/rancher/system-upgrade-controller
    newTag: v0.9.1
  patches:
    - patch: |-
        apiVersion: v1
        kind: ConfigMap
        metadata:
          name: default-controller-env
        data:
          SYSTEM_UPGRADE_JOB_KUBECTL_IMAGE: private.registry/rancher/kubectl:v1.22.6
      target:
        kind: ConfigMap
    - patch: |-
        apiVersion: apps/v1
        kind: Deployment
        metadata:
          name: system-upgrade-controller
          namespace: system-upgrade
        spec:
          template:
            spec:
              imagePullSecrets:
                - name: private-registry
      target:
        kind: Deployment
    - patch: |-
        apiVersion: v1
        kind: ServiceAccount
        metadata:
          name: system-upgrade
          namespace: system-upgrade
        imagePullSecrets:
        - name: private-registry
      target:
        kind: ServiceAccount


[Launcher] User facing files and file paths should be removed

We should validate all file path locations are scrubbed.

@crutkas / @jyuwono .  Currently the plugins save information in a directory named after the assembly that they are contained in.
I can think of a couple options:

Rename the plugin assemblies?  Eg Wox.Plugin.Program.   If we do this, it seems to indicate a hard break with the wox infrastructure, or at least that we don't intent to maintain compatibility with wox for that particular plugin.  The current plugins probably can't be dropped in as is already, but future fixes may be cherry picked back into wox.

Provide an interface that keeps the assemblies and namespaces the same, but provides a SaveDirectoryName field that can be optionally specified before falling back to the assembly name.

I'm leaning towards the latter, but if we want to update the namespaces / assemblies anyway then the first option makes more sense.  Thoughts?


Bump package version and update readme.

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   94.82%   94.82%
=======================================
  Files           5        5
  Lines         251      251
=======================================
  Hits          238      238
  Misses         13       13

Continue to review full report at Codecov.

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


Submit and go to next challenge button Hover effect not working

Describe the Issue
This is a super minor issue but I noticed that the CSS for when you hover over a button seems to not be consistent between the buttons. most buttons when you hover over them they turn the dark blue color but once you click the check your code button in a challenge the button to submit and go to next challenge does not follow the same hover effect.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-html-by-building-a-cat-photo-app/step-1
Steps to Reproduce

complete challenge
Click on Check your code button
Hover over submit and go to next challenge
See error

Expected behavior
When hovering over the submit button it should highlight dark blue
Screenshots
No response
System

Device: Macbook Laptop
OS: MacOS
Browser: Chrome
Version: 125.0.6422.41

Additional context
No response

I've noticed couple more peculiarities regarding this, both are at the 2nd step, after checking the code, when hover is not working:

After focusing different window, hover will start working. It stops again once window with the challenge is focused (without clicking on the page).
Hover will start working as expected, after clicking somewhere on the page.

@huyenltnguyen

Thanks @gikf, your video is exactly what i was seeing. It didn't seem to matter what challenge I was on during the cat for tutorial. I also witnessed it happening in some of the other tutorials as well. If possible I'd like to spend the weekend looking into this to see if I can figure it out.

It is caused by the focus event submitButtonRef.current?.focus();
https://github.com/freeCodeCamp/freeCodeCamp/blob/c2bbd98926da2dbfcfc45f5d2dd6acbaca670179/client/src/templates/Challenges/classic/lower-jaw.tsx#L266
We have CSS that doesn't allow this button's hover styles when focused.
https://github.com/freeCodeCamp/freeCodeCamp/blob/c2bbd98926da2dbfcfc45f5d2dd6acbaca670179/client/src/components/layouts/global.css
.btn:focus,
.btn-primary:focus,
.btn-primary.focus {
  background-color: var(--quaternary-background);
  color: var(--secondary-color);
  border-color: var(--secondary-color);
}

Overwrites:
button:hover,
input[type='submit']:hover,
.btn:hover,
.btn-default.active:hover,
.btn-default.active,
.btn-primary:hover {
  border-color: var(--secondary-color);
  background-color: var(--secondary-color);
  color: var(--secondary-background);
  cursor: pointer;
}

The PR changing the button element to the Button component is likely the correct approach. But I made a PR for the styles anyway.


[API] Training API with generator

There is no API to get training, validation, test data from generator
function.
In this PR, introduces new training API with generator function.
. New Tizen API.
. Add Unit Test API with generator function.
. Add Test generator for future test.
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #113. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/nntrainer/ci/repo-workers/pr-checker/113-202005251338590.38364911079407-5c1653ec9a1722661714a2ae7a62d281217de566/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/nntrainer/ci/repo-workers/pr-checker/113-202005261400240.54003500938416-bf3e9e89f70c13bc2f8199b7307c96a4838ea252/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/nntrainer/ci/repo-workers/pr-checker/113-202005261527150.12909603118896-bdf62b1476f7477bbf186031ac7dd0b3d46860fb/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/nntrainer/ci/repo-workers/pr-checker/113-202005272004570.40896511077881-970580bc6edc9a0177ec2b5aa5239864c3c9c2bb/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ec2-54-180-96-14.ap-northeast-2.compute.amazonaws.com/nntrainer/ci/repo-workers/pr-checker/113-202005281538100.95506310462952-d0a5f9a445f57a3d7777e4ff57355fc93c7e3581/.

:octocat: cibot: Oooops. The administrator of CI server must install a debian package to support 'ndk-build' command.

:octocat: cibot: Oooops. The administrator of CI server must install a debian package to support 'ndk-build' command.

:octocat: cibot: Oooops. The administrator of CI server must install a debian package to support 'ndk-build' command.

:octocat: cibot: Oooops. The administrator of CI server must install a debian package to support 'ndk-build' command.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/113-202005291838000.11026406288147-79acde84f3d99131cad9147c83c2a8d1c5471d07/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/113-202005291908170.34462094306946-79acde84f3d99131cad9147c83c2a8d1c5471d07/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/113-202005291933130.71266889572144-79acde84f3d99131cad9147c83c2a8d1c5471d07/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/113-202005291953330.040311098098755-82271d26c1c2e097c82296ab2a48c7d4d3e7d10d/.


feat: added emojipicker in chat

#927  Emojis in chat
close #927
I'm added emoji picker in chat page.

@narayan954 I'm done my task please review it.


⚠ Samsung has degraded performance

In 205d373, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2646 ms

Resolved: Samsung performance has improved in 89c8e18.


Arch-specific builds contain constants for all architectures

On my minor conquest to reduce the size of capstone-x86.min.js, I noticed that the cs object exported by capstone-x86.min.js also contains constants for other architectures (ARM_*, MIPS_*, etc.).
I believe these could be safely removed to achieve a decent (about 12k) size reduction.

True, constants were loaded from capstone-constants.js regardless of what was actually being built.
I think the build scripts need to be updated to take care of this issue, and the previous one you reported (to easily enabling diet mode, which by the way would also reduce the amount of constants, as far as I know).
I would gladly do this immediately, but I will be quite busy for the next weeks, so any pull requests would be really welcome. :-)


Extract config logic into dmutils

Depends on https://github.com/alphagov/digitalmarketplace-utils/pull/4

I've restarted the Travis build now that the Utils PR is merged.

Looks like it's still failing to import config from the utils package.

I can't see what magic you worked but looks :+1: now.

https://github.com/alphagov/digitalmarketplace-api/pull/88/files#diff-1f9f743421417fb2794c88447083a031L32 This was the change, it should have been referencing the application config all along really.


Deliver fails with "Invalid provisioning profile"

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
I have created a generic/template XCode project so the same project can be used for different bundle/app IDs for different purposes. The idea is that a newly configure app is config-driven from the get-go.
I'm getting this message when fastlane uploads to iTC:
Transporter Warning Output]: WARNING ITMS-90159: "Invalid provisioning profile. This app contains an embedded provisioning profile that is not associated with your account. Please use a provisioning profile associated with Team ID XXXXXXXXXX."
Using custom variables for team_id, app_identifier, app_name, etc my flow goes like this:
update_project_team(...)
update_info_plist(...)
match(..., type: "appstore", ...)
gym(...)
deliver(...)
The original project settings from the template are very vanilla; I haven't set the team, code signing, provisioning profile or any other specific settings apart from the Release provisioning profile which is set to $(sigh_BUNDLEID>adhoc). (I had to set this manually to see if this would make the solve the issue, but it made no difference.)
Is there something else I need to do?
Complete output when running fastlane, including the stack trace and command used
[16:13:50]: Going to upload updated app to iTunes Connect
[16:13:50]: This might take a few minutes, please don't interrupt the script
[16:14:20]: [Transporter Warning Output]: WARNING ITMS-90159: "Invalid provisioning profile. This app contains an embedded provisioning profile that is not associated with your account. Please use a provisioning profile associated with Team ID XXXXXXXXXX."
[16:14:20]: iTunes Transporter successfully finished its job
[16:14:20]: WARNING ITMS-90159: "Invalid provisioning profile. This app contains an embedded provisioning profile that is not associated with your account. Please use a provisioning profile associated with Team ID XXXXXXXXXX."
[16:14:20]: ------------------------------------------------------------------------------------------------------
[16:14:20]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[16:14:20]: ------------------------------------------------------------------------------------------------------
[16:14:20]: Finished the upload to iTunes Connect```

### Configuration Files

Please copy the complete content of your `Fastfile` and any other configuration files you use below:

Embedded in issue

### Environment

fastlane version (run `fastlane -v`): 1.95.0

Do you use bundler to execute fastlane (i.e. `bundle exec fastlane`)? No

Do you use a Ruby environment manager (e.g. `chruby`, `rbenv`, `rvm`)? No

Did you use $(sigh_BUNDLEID>adhoc)or $(sigh_BUNDLEID_adhoc) ?
The second one is the correct one.
Furthermother your Fastfile builds matchusing appstore for the type param so there is a mismatch here. Make sure you align all the planets and use $(sigh_BUNDLEID_appstore) for the Xcode configuration you are trying to build

Sorry, @nicolasbraun that was a typo.
It turns out my build order wasn't quite right. I wasn't actually matching before the gym. Correcting this saw the true error appear and it's because I need to make my $(sigh_BUNDLEID_adhoc) actyally use the bindle ID for the specific app I'm building.
This last bit I need to do dynamically.

👍  you can close this issue if this is all OK now

Just in case it helps anyone, I use this code for my scenario:
        target_filter = "ClientApp"
        config_filter = "Release"

        project = Xcodeproj::Project.open("ClientApp.xcodeproj")
        project.targets.each do |target|

            if target.name != target_filter
                break
            end

            puts target.name

            target.build_configurations.each do |config|
                if !config.name.match(config_filter)
                    next
                end

                config.build_settings["PROVISIONING_PROFILE"] = "$(sigh_#{app_identifier}_appstore)"
                #puts config.build_settings["PROVISIONING_PROFILE"]
            end

        end

        project.save()

Please excuse the quality of ruby.


Recommend SDATE use single Gregorian dates

Discussed in https://github.com/FamilySearch/GEDCOM/discussions/140
Those who have engaged in a discussion about SDATE generally agree that sorting is easiest if all sort-by dates are single dates (not ranges or periods) in the same calendar. We cannot change this in a patch or minor release as it is not backwards compatible and we know of applications that allow users to enter any kind of date in a sort-by field, but we can make a recommendation like

It is recommended that the SDATE's payload be in the Gregorian calendar and be a simple date with the calendar omitted. Including a month and day is encouraged to help different applications sort dates the same way, as the relative ordering of dates with different levels of precision is not well defined.

Steering committee discussion 14 JUN 2022:
@dthaler to create a pull request with the following wording.

Note: it is recommended to use a payload that matches [[day D] month D] year [D epoch]. Other DateValue forms may have unreliable effects on sorting.  Including a month and day is encouraged to help different applications sort dates the same way, as the relative ordering of dates with different levels of precision is not well defined.


need to store gpu options with the image configs

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@020cc27). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master     #720   +/-   ##
=========================================
  Coverage          ?   87.75%
=========================================
  Files             ?       48
  Lines             ?     3766
  Branches          ?        0
=========================================
  Hits              ?     3305
  Misses            ?      461
  Partials          ?        0

Impacted Files
Coverage Δ

vent/core/rq_worker/watch.py
42.75% <0%> (ø)

Continue to review full report at Codecov.

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


File Not Found Error  nlp/english-words.txt

Hello Everyone!!,
I am trying to setup unstructured on google colab
I am facing a "FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.10/dist-packages/unstructured/nlp/english-words.txt'"
**Code is as below
! pip install -U langchain openai qdrant-client langchain_openai  langchain-experimental
! pip install "unstructured[all-docs]" pillow pydantic lxml pillow matplotlib  tiktoken numpy
!pip install popper utils tesseract-ocr
!pip install "detectron2<EMAIL_ADDRESS>from langchain_text_splitters import CharacterTextSplitter
from unstructured.partition.auto import partition

Will  appreciate help

This was an issue with unstructured==0.13.1 but should be fixed as of 0.13.2 , initially tracked here: https://github.com/Unstructured-IO/unstructured/issues/2855 .


Add sage verification script for the group laws

This adds a SAGE script for verifying the implemented group laws.
The output should be:
Formula secp256k1_gej_add_var:
  add_infinite_ab:
    branch 0: OK
  double:
    branch 2: OK
  add:
    branch 4: OK
  add_infinite_b:
    branch 1: OK
  add_infinite_a:
    branch 0: OK
  add_opposite:
    branch 3: OK

Formula secp256k1_gej_add_ge_var:
  add_infinite_ab:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1])
  double:
    branch 2: OK (assuming Bz - 1 = 0 [b.z=1])
  add:
    branch 4: OK (assuming Bz - 1 = 0 [b.z=1])
  add_infinite_b:
    branch 1: OK (assuming Bz - 1 = 0 [b.z=1])
  add_infinite_a:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1])
  add_opposite:
    branch 3: OK (assuming Bz - 1 = 0 [b.z=1])

Formula secp256k1_gej_add_zinv_var:
  add_infinite_ab:
    branch 0: OK
  double:
    branch 2: OK
  add:
    branch 4: OK
  add_infinite_b:
    branch 0: OK
  add_infinite_a:
    branch 1: OK
  add_opposite:
    branch 3: OK

Formula secp256k1_gej_add_ge:
  add_infinite_ab:
  double:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 2: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 3: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add_infinite_b:
  add_infinite_a:
    branch 4: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 6: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 7: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 13: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add_opposite:
    branch 9: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])

Formula secp256k1_gej_add_ge_old [should fail]:
  add_infinite_ab:
  double:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add:
    branch 0: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
    branch 2: FAIL, ['on_curve', 'finite_point', 'colinear_2', 'colinear_1', 'colinear_3'] fails (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add_infinite_b:
  add_infinite_a:
    branch 1: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])
  add_opposite:
    branch 2: OK (assuming Bz - 1 = 0 [b.z=1], Bi = 0 [b_finite])

Updated with more comments.

Added exhaustive verification in Z43.

Significantly rewrote the code, it now prints assumptions more explicitly, and can deal with cases involving infinity. On the downside, the exhaustive check is too slow now, so it's disabled.

Update: make prove_zero call prove_nonzero on the denominators, to prevent 0/0. This shouldn't ever occur in reality, as the formulas should never result in 0/0, and the implementations don't return fractions... but better be safe.

Refactored the code into multiple files, in their own directory, and updated the comments.

Pushed new version to address @apoelstra's nits.

Except for the finite/infinite typos in description strings (I think I noted them all), ACK.
Thanks for clarifying the comments!

Fixed the incorrect finite/infinite descriptions.

ACK


Support of Angular 5

Any plans to support Angular 5? Thanks!
-=-=
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed.

Yeah, it's in our plans! Thanks :+1:

+1


Create an app that tells you where it's 5 o'clock

Based on an idea in the discord, I whipped up this app last night.

realized I can't start an app name with "5" closing and will re-open with new app.


fix(html report): Add consistency in numbering of mutants

The recently added "mutant table" in the html had inconsistent numbering in a lot of cases when compared to the id's in the report. I.e. mutant 25 in the report would not allign with mutant 25 in the mutant table.
fixes #422

How do we do the sorting in the component that shows the actual code? (at the left of the page) If we change the order of the numberedmutants, will that component change as well?

Yew it will. That part is also in this file: ...ter/src/templates/sourceFile.tsx


Support required TF API configuration attributes for OAMG

Configuration attributes can be seen in:

https://github.com/oamg/leapp/blob/835a3d27b52fe44cbca6ed5307e6801981df24d8/.github/workflows/tmt-tests.yml#L154-L180
https://github.com/oamg/leapp/blob/835a3d27b52fe44cbca6ed5307e6801981df24d8/.github/workflows/tmt-tests.yml#L182-L209

Implementing the attributes requires:

[ ] support for attributes in the configs ( https://github.com/packit/packit )
example PR: packit/packit#1504
(changes are mainly required in the schema and config; also the changes in config might be in different class, since metadata are deprecated as of now, so it doesn't make sense to extend them)
[ ] support for passing them from configs to TF in the service ( here )
example PR: packit/packit-service#1486

More info: https://github.com/packit/packit/issues/1600

Thanks for the inputs, @mfocko! Your point makes sense.
So, just to clarify better on the structure that the tests jobs should have:
  - job: tests
    trigger: pull_request
    identifier: tests-7to8
    metadata:
      targets:
        - fedora-36-x86_64
      fmf_url: "https://gitlab.cee.redhat.com/rolivier/leapp-packit-poc-tests"
      fmf_ref: "main"
      use_internal_tf: True
    tmt_plan_regex: "some-regex"
    environment_settings:
      provisioning: '{"post_install_script": "#!/bin/sh\nsudo sed -i s/.*ssh-rsa/ssh-rsa/ /root/.ssh/authorized_keys"}}'

In the future, without the metadata, it would look something like this?
  - job: tests
    trigger: pull_request
    identifier: tests-7to8
    targets:
      - fedora-36-x86_64
    fmf_url: "https://gitlab.cee.redhat.com/rolivier/leapp-packit-poc-tests"
    fmf_ref: "main"
    use_internal_tf: True
    tmt_plan_regex: "some-regex"
    environment_settings:
      provisioning: '{"post_install_script": "#!/bin/sh\nsudo sed -i s/.*ssh-rsa/ssh-rsa/ /root/.ssh/authorized_keys"}}'

Is that an acceptable structure for introducing the new parameters?

You can do that already :) I do not recall which options were supported »only« in metadata, but as of now metadata are parsed just for backward-compatibility.
Regarding the new parameters, regex is fine for sure. With provisioning I'm not sure whether it makes sense to do something like tf_provisioning with nested key post_install_script, or just send the whole JSON-object to the TF. On one hand it is a pretty simple solution, on the other it doesn't seem that straightforward to use and is inconsistent with rest of the config.

Nice :)
I will play a bit with both formats and see if there is any other type of settings we need to send to TF.

Hi, @mfocko. I'm applying my changes to the JobConfig class, and I got a question.
Should I replicate the two parameters I want to include to the CommonPackageConfig as well? Or making them attributes of JobConfig is enough? I was trying to follow the same example you provided in the description, and at the same time, following what is done for tmt_url, for example.
Diff of the two parameters being passed to the CommonPackageConfig
diff --git a/packit/config/job_config.py b/packit/config/job_config.py
index 06f0d6f..3f1f278 100644
--- a/packit/config/job_config.py
+++ b/packit/config/job_config.py
@@ -98,6 +98,8 @@ class JobConfig(CommonPackageConfig):
         enable_net: bool = True,
         allowed_pr_authors: Optional[List[str]] = None,
         allowed_committers: Optional[List[str]] = None,
+        tmt_plan_regex: Optional[str] = None,
+        tf_provisioning: Optional[Dict[str, Any]] = None,
     ):
         super().__init__(
             config_file_path=config_file_path,
@@ -150,6 +152,8 @@ class JobConfig(CommonPackageConfig):
             enable_net=enable_net,
             allowed_pr_authors=allowed_pr_authors,
             allowed_committers=allowed_committers,
+            tmt_plan_regex=tmt_plan_regex,
+            tf_provisioning=tf_provisioning,
         )
         self.type: JobType = type
         self.trigger: JobConfigTriggerType = trigger
@@ -203,7 +207,9 @@ class JobConfig(CommonPackageConfig):
             f"env={self.env},"
             f"enable_net={self.enable_net},"
             f"allowed_pr_authors={self.allowed_pr_authors},"
-            f"allowed_commiters={self.allowed_committers})"
+            f"allowed_commiters={self.allowed_commiters},",
+            f"tmt_plan_regex={self.tmt_plan_regex},",
+            f"tf_provisioning={self.tf_provisioning})"
         )

     @classmethod
@@ -263,6 +269,8 @@ class JobConfig(CommonPackageConfig):
             and self.skip_build == other.skip_build
             and self.env == other.env
             and self.enable_net == other.enable_net
+            and self.tmt_plan_regex == other.tmt_plan_regex
+            and self.tf_provisioning == other.tf_provisioning
         )

Diff of the two parameters being setted as an attribute of JobConfig class
diff --git a/packit/config/job_config.py b/packit/config/job_config.py
index 06f0d6f..24ee8b3 100644
--- a/packit/config/job_config.py
+++ b/packit/config/job_config.py
@@ -98,6 +98,8 @@ class JobConfig(CommonPackageConfig):
         enable_net: bool = True,
         allowed_pr_authors: Optional[List[str]] = None,
         allowed_committers: Optional[List[str]] = None,
+        tmt_plan_regex: Optional[str] = None,
+        tf_provisioning: Optional[Dict[str, Any]] = None,
     ):
         super().__init__(
             config_file_path=config_file_path,
@@ -153,6 +155,8 @@ class JobConfig(CommonPackageConfig):
         )
         self.type: JobType = type
         self.trigger: JobConfigTriggerType = trigger
+        self.tmt_plan_regex = tmt_plan_regex
+        self.tf_provisioning = tf_provisioning

     def __repr__(self):
         return (
@@ -203,7 +207,9 @@ class JobConfig(CommonPackageConfig):
             f"env={self.env},"
             f"enable_net={self.enable_net},"
             f"allowed_pr_authors={self.allowed_pr_authors},"
-            f"allowed_commiters={self.allowed_committers})"
+            f"allowed_commiters={self.allowed_commiters},",
+            f"tmt_plan_regex={self.tmt_plan_regex},",
+            f"tf_provisioning={self.tf_provisioning})"
         )

     @classmethod
@@ -263,6 +269,8 @@ class JobConfig(CommonPackageConfig):
             and self.skip_build == other.skip_build
             and self.env == other.env
             and self.enable_net == other.enable_net
+            and self.tmt_plan_regex == other.tmt_plan_regex
+            and self.tf_provisioning == other.tf_provisioning
         )

I am not going to block you on that :) From the perspective of usage, I guess the regex doesn't make a lot of sense in CommonPackageConfig…
Smaller context: JobConfig specifies schema/attributes for each of the entries in jobs, CommonPackageConfig allows you to define attributes on the global level, e.g.
tf_provisioning: «your provisioning»

jobs:
- job: tests
  identifier: my_special_tests
  tf_provisioning: «my special provision just for this job»
- job: tests
  identifier: regular_daily_grind
  # this inherits the «your provisioning»

I guess you can see why the regex doesn't make much sense :)

Ah! Now it makes super more sense to me! Thanks for the info. I was having a hard time trying to wrap my head around the usage of JobConfig/CommonPackageConfig, but now I see the difference.
Totally agree! The regex should be something related only to the JobConfig and not something globally that can be changed on the job level.

Hi guys, I am from oamg team, thank you so much for working on it!
I have a question - is it already possible with packit to pass certain artifacts (to be more specific, the fedora-copr build id)? We also require this for our tmt-tests workflow, as in here https://github.com/oamg/leapp/blob/master/.github/workflows/tmt-tests.yml#L26 .

@fernflower Packit already sets a bunch of env vars that you can use, it was implemented by our one and only @mfocko here: https://github.com/packit/packit-service/pull/1486
As Mato describes it:

Packit now passes PACKIT_COPR_PROJECT and PACKIT_COPR_RPMS variables to the Testing Farm. PACKIT_COPR_PROJECT holds Copr project in format owner/project and PACKIT_COPR_RPMS space-separated RPMs that were built in Copr.

@TomasTomecek cool, thank you, I guess we will be able to use that to implement the functionality we require.

Hi, @TomasTomecek and @mfocko! I have a follow-up question on @fernflower question.
Can we pass the values for those variables through a /packit <something> comment in the PR? Since both Leapp/Leapp-Repository will need different values each time they execute the integration tests (Correct me if I'm wrong on this, @fernflower)
For example, let's take leapp:

When a PR is open on leapp and the integration tests start executing in that PR, we need to pass the copr build of leapp-repository as well (or default to the master branch in case nothing is provided).

And for leapp-repository, the same is true here as the above example.
From what I understood from your comment, we can define those variables somewhere in the packit config file and it will be sent to the TF API too, right?
But in a case where, let's say, we want to use the copr build with number 4242 from leapp-repository, can we re-trigger that from the PR comments passing this copr build?

But in a case where, let's say, we want to use the copr build with number 4242 from leapp-repository, can we re-trigger that from the PR comments passing this copr build?

This would be a new feature request. I really like how simple it sounds: run a command that will retrigger tests using a new configuration. At the same time, we'd need to figure out reporting - if you have multiple test jobs, how does Packit associate that new test request with the existing test runs. Or even for a single test job: should that be replaced by the new test request?
Could you please open a new issue where we can start tracking this ask. And please, be as detailed as possible in how you'd expect this to work :)

@fernflower, could you help us and open a new issue with the detailed information on how that works in the current leapp tf github actions? I think you would give much more details than me on this request.
Also, if I understood correctly, @fernflower, would be too bad to leapp/leapp-repository having the branch set as a default one (let's say, master)? Until we can discuss more on this new feature request and how that would work?

Also, if I understood correctly, @fernflower, would be too bad to leapp/leapp-repository having the branch set as a default one (let's say, master)? Until we can discuss more on this new feature request and how that would work?

Imho for proof of concept we can keep leapp-repositorymaster for leapp PRs ad leappmaster for leapp-repository PRs, just not to block you.
But currently our github action tmt-tests workflow allows testing with specific versions of leapp-repository/leapp, and this feature is critical for certain big features which depend on changes in both leapp and leapp-repository, so if we don't have this support eventually, we won't be able to switch to using packit.

@fernflower, could you help us and open a new issue with the detailed information on how that works in the current leapp tf github actions? I think you would give much more details than me on this request.

I have created https://github.com/packit/packit-service/issues/1544


GDScript 2.0: match does not work in a project exported in release mode

Godot version
Godot Engine v4.0.beta2.official.f8745f2f7
System information
Windows 10 Home OS version 19043.2006 x64, AMD Ryzen 5 1600 Six-Core Processos x64-based, 8GB RAM, Radeon RX 560 Series
Issue description
ps: Sorry my horrible english
The match function is not beeing correctly interpreted by the compiler as a function like a "if (a) {return} else {return}". Its beeing interpreted as a "if (a) {return} else if (!a) {return}" that implies to the compiler that some more thing could be executed after it. But can not.
Steps to reproduce
Use the following code in a Label node:
func _ready():
	text = buggyFunction('bug')

func buggyFunction(anyValue:String) -> String:
	match anyValue:
		'bug': return 'I will never execute in production releases!'
		_: return 'I will never execute in production releases!'

func correctlyCompiledFunction(anyValue:String) -> String:
	match anyValue:
		'bug': return 'I will execute if anyValue="bug"!'
		_: return 'I will execute if anyValue!="bug"!'
	return 'This return will never execute but is necessary to the function be correctly compiled'

Now compiles a version for windows whitout debug mode.
Project -> Export -> Windows Desktop (Runnable) -> Export Project -> unmark the "Export with debug" option -> Save.
Once compiled, open the .exe file and you will see that the buggyFunction will not execute.
Godot does not correctly compiles the function "buggyFunction" but the "correctlyCompiledFunction" is OK. Note that the only difference between them is just the "return" added at the end of the function.
I understand that a simple way to solve this problem is never forgeting to add the returnment to the function but I would love to see this bug beeing solved.
Minimal reproduction project
I'm attaching a little exemple project cointaining this bug.
Every time you exports this project with debug, the function buggyFunction is correctly compiled but when you export it without debug the function buggyFunction crashes and the Label in this project is changed.
Link to download the project:
TestForMatchBug.zip

Looks to be the same as #55045


Testing

Add basic Cypress tests
Fixes #18

@thewtex This is passing now with the changes that I've mentioned inline.


Add effect to element from mouse over page

Hi,
Tihs library is amazing, simply amazing! However I have a question: I would like an image inside the page to be tilted when the mouse moves over the page (not the image itself). While the user moves the mouse over the page from left to right I would like the image to tilt accordingly.
is it possible? Many parallax libraries allow this to happen, would it be possible with this library?

Looking for the same stuff, can't find how to 😢

Looking for this as well, is there a way we can pass the element to a specified element?
Like hovering over the page will affect an image inside the page, as opposed to the page itself.

I'd like that as well

I'll just add my +1 to this. Would also love to have the option to react to the cursor, even if the cursor isn't hovering over the element.

I'll just add my +1 to this. Would also love to have the option to react to the cursor, even if the cursor isn't hovering over the element.


Regenerator Runtime?

Having issues running my compiled server (compiled via webpack) and am receiving the following error:
@risingstack/graffiti-mongoose/lib/query/query.js:15
var ref = _asyncToGenerator(regeneratorRuntime.mark(function _callee(graffitiModel, args, context, info) {

I've tried adding it as the first entry in my webpack config, and have tried requiring (separately, two different attempts) both rengerator-runtime/runtime and babel-polyfill in server.js (my primary entry) - I've also tried creating a bootstrap that requires babel-polyfill prior to requiring server.js but haven't had any luck resolving the error. It's the same every time.
Any ideas?
Webpack and primary entry below.
Current webpack config
var path = require('path');
var webpack = require('webpack');
var nodeExternals = require('webpack-node-externals');

var publicPath = 'http://localhost:9090';

module.exports = {
  target: 'node',
  devtool: '#inline-source-map',
  entry: [
    './src/server.js'
  ],
  output: {
    filename: '[name].js',
    path: path.join(__dirname, 'build'),
    publicPath: publicPath + '/scripts/'
  },
  module: {
    loaders: [
      { test: /\.js?$/, exclude: /node_modules/, loaders: ['babel', 'eslint-loader'] },
      { test: /\.json?$/, loaders: ['json-loader'] }
    ]
  },
  externals: [nodeExternals()],
  eslint: {
    emitError: false,
    emitWarning: false,
    failOnWarning: false,
    failOnError: false
  },
  resolve: {
    alias: {
      graffiti: '@risingstack/graffiti',
      "graffiti-mongoose": '@risingstack/graffiti-mongoose',
      server: './server'
    },
    extensions: ['', '.js'],
    modulesDirectories: ['node_modules']
  },
  plugins: [
    new webpack.NoErrorsPlugin(),
    new webpack.optimize.DedupePlugin(),
    new webpack.DefinePlugin({
      "process.env": {
        NODE_ENV: JSON.stringify('development')
      }
    })
  ]
};

server.js
import express from 'express';
import graffiti from '@risingstack/graffiti';
import * as mongooseSchema from './schema';
import config from 'config';
import { json } from 'body-parser';
import 'regenerator-runtime/runtime';

const app = express();
const port = config.get('PORT') || process.env.PORT || 3001;

app.use(json());

app.use(graffiti.express({
  mongooseSchema
}));

app.use((request, response) => {
  response.redirect('/graphql');
});

app.listen(port, (error) => {
  if (error) {
    throw error;
  }

  console.log(`GraphQL API running on port ${port}`);
});

Update
I've made progress with the regenerator issue by requiring babel-polyfill and regenerator-runtime/runtime - now, I'm getting the following:
.../node_modules/@risingstack/graffiti/lib/util/util.js:24
throw new Error('Required option is missing');

Ended up being an issue with the way I was exporting my schema in schema/index.js... I ended up changing the export to:
export const schema = getSchema([User]);

and the corresponding import to:
import { schema } from './schema';


small fix to loading of combined bedcounts with public data

no comment on the deletion of

Probably fixing flake8 errors.


RSDK-6974 - Add FFmpeg Static Build to Makefile

Description
This PR adds a Makefile script to clone and build FFmpeg v6.1 static libraries and CGO flags for linking to the go binary.
Here are the remaining dynamic links:
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libz.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libresolv.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]

Have verified that these libraries are available across Ubuntu and Debian versions.
Building module in the antique container allows for libc support >=2.27.
The size change is pretty small due to disabling all but necessary FFmpeg features.

Size could be reduced further by stripping symbols if we want

47 MB -> 51 MB

Try Out
To build for linux/arm64 follow these steps:

Startup canon:
canon -arch arm64
Build FFmpeg and go binary:
make bin/viamrtsp

Tests

FFmpeg static build/link working inside arm64/amd64 canon.
FFmpeg build and go build still working on MacOS.
Go build linking against FFmpeg static libs successfully through the package config flag.
Tested binary works on:

Pi4 Debian Bullseye :white_check_mark:
Pi5 Debian Bookworm :white_check_mark:
Jetson Nano Ubuntu 18.04 :white_check_mark:
Jetson Orin Nano Ubuntu 20.04 :white_check_mark:

Questions

Are we ok with using canon for Linux builds?

This PR assumes libjpeg static lib is available for fully functional (standalone) binary.
If libjpeg archive file is not available, dynamic link will be created.

Are we ok with not having a fully static build for MacOS?

Builds work for testing but will not be able to statically link to libjpeg.

Are we happy with using FFmpeg v6.1?

There are no API changes between 4.x and 6.x but looks to be lots of optimizations made. https://www.ffmpeg.org/index.html#pr6.1

@erh this is ready for you to review or merge.

Running make bin/viamrtsp on osx fails with this error:
make bin/viamrtsp
/Library/Developer/CommandLineTools/usr/bin/make /Users/nicksanford/code/viamrtsp/ffmpeg/Darwin-arm64
cd FFmpeg && ./configure --prefix=/Users/nicksanford/code/viamrtsp/ffmpeg/Darwin-arm64 --enable-static --disable-shared --disable-programs --disable-doc --disable-everything --enable-decoder=h264 --enable-decoder=hevc --enable-swscale && /Library/Developer/CommandLineTools/usr/bin/make -j8 && /Library/Developer/CommandLineTools/usr/bin/make install
/bin/sh: ./configure: No such file or directory
make[1]: *** [/Users/nicksanford/code/viamrtsp/ffmpeg/Darwin-arm64] Error 127
make: *** [build-ffmpeg] Error 2

@nicksanford There was an issue with the FFmpeg path check when clone will initialize empty folder for submodule.
I ended up refactoring back to use make target instead of submodule as it was much cleaner.

I think this accomplishes anchoring to a commit as we are using a release tag branch.
Instead of writing shell scripts to check if files exist, it seems easier to use Makefile builtin target check. Especially since I am chaining the Install path (FFMPEG_PREFIX) and FFmpeg clone path to avoid re-running these tasks.

Ok @nicksanford , passing CI now. See run here. Had to add in rtsp-demuxer to handle open for codec detection. We can remove this once that call is removed.

@seanavery initial build on osx succeeded. I'll test it more tomorrow morning & approve if I don't find any more issues. Thanks!

@seanavery
A few issues:
1.
on OSX, when I run the module I get the following spam over & over again
\_ [h264 @ 0x125610c40] Error splitting the input into NAL units.
2024-04-04T10:09:14.777-0400    ERROR   robot_server.process.viamrtsp_/Users/nicksanford/code/viamrtsp/bin/viamrtsp.StdErr      pexec/managed_process.go:252
\_ [h264 @ 0x125610c40] No start code is found.
2024-04-04T10:09:14.777-0400    ERROR

I do not get that spam output on main

Running make on osx followed by canon result in the canon build failing, probably b/c it is reusing the build directory from the different platform. The solution was to manually delete the FFmpeg directory and re-run make. Could you please add a make clean command that leaves the build in a clean state?

@nicksanford

Thanks for the comment about clean script, added!
I see extra logs on decoder from macos static build.

I think decoder logs should be handled separately with a helper to change ffmpeg loglevel.
Tested on my mac and the pipeline is still working well.

Confirmed that going from darwin/arm64 -> canon linux/arm64 causes build issues

This does not happen when going to x86 container since it will rebuild binaries.
Hopefully, the clean script is sufficient for now.

Retested:

macos arm64 ✅
pi4 ✅
pi5 ✅
x86 ✅


Revert "fix: long/short offers were flipped"

Reverts itchysats/itchysats#2764
As discussed in https://github.com/itchysats/itchysats/pull/2784

bors r+


[v1 | dds-image]: CDN asset does not load dds-image-item sub-component

ADCMS-4632
Description
When loading dds-image from CDN endpoint the <dds-image-item> sub component is not loaded.
Additionally (but perhaps unrelated?), the <dds-image> component does not display images without the default-src attribute present.
Component(s) impacted
dds-image, dds-image-item
Browser
Firefox
Carbon for IBM.com version
v1-latest
Severity
Severity 1 = The design is broken in a critical way that blocks users from completing tasks or damages the brand. Affects major functionality, no workaround.
Application/website
AEM
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
https://codepen.io/andy-blum/pen/LYaaovP?editors=1010
Steps to reproduce the issue (if applicable)
HTML
<script type="module" src="https://1.www.s81c.com/common/carbon-for-ibm-dotcom/tag/v1/latest/image.min.js"></script>

<dds-image alt="Image alt text" default-src="https://fpoimg.com/672x336?text=2:1&bg_color=53ee96&text_color=161616">
  <dds-image-item media="(min-wiidth:672px)" srcset="https://fpoimg.com/672x336?text=2:1&bg_color=ee5396&text_color=161616">
  </dds-image-item>
  <dds-image-item media="(min-wiidth:400px)" srcset="https://fpoimg.com/672x336?text=2:1&bg_color=ee5396&text_color=161616">
  </dds-image-item>
  <dds-image-item media="(min-wiidth:320px)" srcset="https://fpoimg.com/672x336?text=2:1&bg_color=ee5396&text_color=161616">
  </dds-image-item>
</dds-image>

JS
customElements.get('dds-image');
// class n { ... }

customElements.get('dds-image-item');
// undefined

Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

This was fixed in https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/11564


Add removing of register from ROB functionality

When oldest is complete, remove from buffer. Do up to 8 oldest in a clock cycle.

#Close 2


Event Passive Mode

With the chrome audit tool, in the best practices. I have an optimization to do for scroll preformances:

instantsearch.js: v2.2.4 in function setAccessor():
The listener is not in passive mode.
if (!old) node.addEventListener(name, eventProxy, useCapture);
When i use "tooltips" option in rangeSlider widgets.
If you can show this.
(same problem with instantsearch demo only with "tourism" version)
https://community.algolia.com/instantsearch.js/v1/examples/tourism/
Thanks

Hello @fabroux thanks for opening this issue. This is something that we have overlooked. Would you be interested in providing a PR/fix for that?
PS: for reference, here is a complete guide about passive event listeners.

Be careful with support here, the passive events variadic call isn’t supported anywhere. A light version https://github.com/rafrex/detect-passive-events might be needed

As far as I can tell, we no longer have event listeners on scroll at all now, and I can't reproduce this warning. Good news :D

I was wrong, we do have event handlers which are not passive on touch, not scroll:
https://github.com/algolia/instantsearch.js/blob/06eaac69204890f3c82d41ab9c5f9111ce42c21e/src/components/Slider/Rheostat.js#L375-L376


Collection view gestures breaking

I'm noticing strange behavior after the Extensions method "setGestureEnabled" gets called. It seems to break all tap gesture recognition.
https://github.com/SwipeCellKit/SwipeCellKit/issues/56
There was a similar issue of UITableView.
I think that UICollectionView should be modified in the same way as UITableView.
What do you think?
and thanks for making good open source!

What issue are you facing exactly?


Shifting to Protobuf Serialization - Cleaned

This should be clean and ready to be merged. I have checked out tmp.sqlite from both repo and history (.sqlite files are now ignored by git) and refactored DbHandler class into the righteous DBHandler.
Let me know if anything else has to be addressed.

So, can this be merged? I'll work on these files, and use this interface, in the next few PRs, so I need it to proceed!


Issue #3814 - Inactive users receive email notifications

Just a small patch for #3814.
Not sure if it's enough to cover all unwanted mailing situations.

Thanks!


File Upload Issue

I am able to send messages to the IoT Hub using message.py, but when I run the the file upload code, I can't get the file to upload. The error that I get is "HTTP operation returned: 400 ArgumentError (Error: Bad Request)". I haven't made any modifications to the code except the connection string and path to file. When I set the logging to debug, I am able to get more of the error:
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTP Response: {"Message":"ErrorCode:ArgumentInvalid;Requested Host is not supported","ExceptionMessage":"Tracking ID:"}
The IoT Hub is connected to a blob storage account/container already. I've installed azure.storage.blob & azure-iot-device
This the entire thing from MacBook Terminal: I've deleted some of the words/numbers.
`-MacBook-Air:Python $ python3 FileUpload.py
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Creating pipeline executor
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:Gateway Hostname not present. Setting Hostname to: .azure-devices.net
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTPTransportStage(InitializePipelineOperation): got connection args
DEBUG:azure.iot.device.common.http_transport:creating a SSL context
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:InitializePipelineOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting <azure.iot.device.common.evented_callback.EventedCallback object at   > in callback thread
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Creating callback executor
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:SasTokenStage: Scheduling automatic SAS Token renewal at epoch time:
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:Gateway Hostname not present. Setting Hostname to: .azure-devices.net
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage(InitializePipelineOperation): got connection args
DEBUG:azure.iot.device.common.mqtt_transport:creating mqtt client
INFO:azure.iot.device.common.mqtt_transport:Creating client for connecting using MQTT over TCP
DEBUG:azure.iot.device.common.mqtt_transport:creating a SSL context
DEBUG:azure.iot.device.common.mqtt_transport:configuring SSL context with default certs
DEBUG:azure.iot.device.common.mqtt_transport:Created MQTT protocol client, assigned callbacks
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:InitializePipelineOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting <azure.iot.device.common.evented_callback.EventedCallback object at   > in callback thread
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
IoT Hub file upload sample, press Ctrl-C to exit
INFO:azure.iot.device.iothub.sync_clients:Connecting to Hub...
DEBUG:azure.iot.device.iothub.pipeline.mqtt_pipeline:Starting ConnectOperation on the pipeline
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage(ConnectOperation): State changes DISCONNECTED -> CONNECTING. Sending op down
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(ConnectOperation): blocking
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage(ConnectOperation): connecting
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage(ConnectOperation): Starting watchdog
DEBUG:azure.iot.device.common.mqtt_transport:connecting to mqtt broker
INFO:azure.iot.device.common.mqtt_transport:Connect using port 8883 (TCP)
DEBUG:paho:Sending CONNECT (u1, p1, wr0, wq0, wf0, c0, k60) client_id=b''
DEBUG:azure.iot.device.common.mqtt_transport:_mqtt_client.connect returned rc=0
DEBUG:paho:Received CONNACK (0, 0)
INFO:azure.iot.device.common.mqtt_transport:connected with result code: 0
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting _on_mqtt_connected in pipeline thread
INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:_on_mqtt_connected called
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage(ConnectedEvent): State changes CONNECTING -> CONNECTED. Connection established
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:PipelineRootStage: ConnectedEvent received. Calling on_connected_handler
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting _on_connected in callback thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: completing connect op
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage(ConnectOperation): cancelling watchdog
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:ConnectOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(ConnectOperation): op succeeded.  Unblocking queue
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(ConnectOperation): unblocking and releasing queued ops.
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(ConnectOperation): processing 0 items in queue for error=None
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_complete in callback thread
INFO:azure.iot.device.iothub.abstract_clients:Connection State - Connected
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
INFO:azure.iot.device.iothub.sync_clients:Successfully connected to Hub
DEBUG:azure.iot.device.iothub.pipeline.http_pipeline:HTTPPipeline get_storage_info_for_blob called
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.iothub.pipeline.pipeline_stages_iothub_http:IoTHubHTTPTranslationStage(GetStorageInfoOperation): Translating Get Storage Info Operation to HTTP.
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTPTransportStage(HTTPRequestAndResponseOperation): Generating HTTP request and setting callback before completing.
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting request in azure_iot_http thread
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Creating azure_iot_http executor
INFO:azure.iot.device.common.http_transport:sending https POST request to devices/  /files .
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): .azure-devices.net:443
DEBUG:urllib3.connectionpool:https://.azure-devices.net:443 "POST /devices/  /files?api-version=2019-10-01 HTTP/1.1"
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_request_completed in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTPTransportStage(HTTPRequestAndResponseOperation): Request completed. Completing op.
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTP Response Status: 400
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_http:HTTP Response: {"Message":"ErrorCode:ArgumentInvalid;Requested Host is not supported","ExceptionMessage":"Tracking ID:-G2:-TimeStamp:2022+00:00"}
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:HTTPRequestAndResponseOperation: completing without error
DEBUG:azure.iot.device.iothub.pipeline.pipeline_stages_iothub_http:IoTHubHTTPTranslationStage(HTTPRequestAndResponseOperation): Got response for GetStorageInfoOperation
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:GetStorageInfoOperation: completing with error HTTP operation returned: 400 ArgumentError(Error: Bad Request)
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_complete in callback thread
INFO:azure.iot.device.common.evented_callback:Callback completed with error HTTP operation returned: 400 ArgumentError(Error: Bad Request)
INFO:azure.iot.device.common.evented_callback:NoneType: None
INFO:azure.iot.device.iothub.sync_clients:Initiating client shutdown
INFO:azure.iot.device.iothub.sync_clients:Disconnecting from Hub...
DEBUG:azure.iot.device.iothub.sync_clients:Executing initial disconnect
DEBUG:azure.iot.device.iothub.pipeline.mqtt_pipeline:Starting DisconnectOperation on the pipeline
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage(DisconnectOperation): State changes CONNECTED -> DISCONNECTING. Sending op down.
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(DisconnectOperation): blocking
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage(DisconnectOperation): disconnecting
INFO:azure.iot.device.common.mqtt_transport:disconnecting MQTT client
DEBUG:paho:Sending DISCONNECT
INFO:azure.iot.device.common.mqtt_transport:disconnected with result code: 0
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting _on_mqtt_disconnected in pipeline thread
DEBUG:azure.iot.device.common.mqtt_transport:_mqtt_client.disconnect returned rc=0
DEBUG:azure.iot.device.common.mqtt_transport:Cancelling all pending operations
INFO:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: _on_mqtt_disconnect called
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage(DisconnectedEvent): State changes DISCONNECTING -> DISCONNECTED. Not attempting to reconnect (User-initiated disconnect)
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:PipelineRootStage: DisconnectedEvent received. Calling on_disconnected_handler
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting _on_disconnected in callback thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_mqtt:MQTTTransportStage: Expected disconnect - completing pending disconnect op
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:DisconnectOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(DisconnectOperation): op succeeded.  Unblocking queue
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(DisconnectOperation): unblocking and releasing queued ops.
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(DisconnectOperation): processing 0 items in queue for error=None
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_complete in callback thread
INFO:azure.iot.device.iothub.abstract_clients:Connection State - Disconnected
INFO:azure.iot.device.iothub.abstract_clients:Cleared all pending method requests due to disconnect
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
DEBUG:azure.iot.device.iothub.sync_clients:Successfully executed initial disconnect
DEBUG:azure.iot.device.iothub.sync_clients:Stopping handlers...
DEBUG:azure.iot.device.iothub.sync_clients:Successfully stopped handlers
DEBUG:azure.iot.device.iothub.sync_clients:Executing secondary disconnect...
DEBUG:azure.iot.device.iothub.pipeline.mqtt_pipeline:Starting DisconnectOperation on the pipeline
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:ReconnectStage(DisconnectOperation): State is already DISCONNECTED. Sending op down
INFO:azure.iot.device.common.pipeline.pipeline_stages_base:ConnectionLockStage(DisconnectOperation): Transport is already disconnected.  Completing.
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:DisconnectOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_complete in callback thread
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
DEBUG:azure.iot.device.iothub.sync_clients:Successfully executed secondary disconnect
INFO:azure.iot.device.iothub.sync_clients:Successfully disconnected from Hub
DEBUG:azure.iot.device.iothub.sync_clients:Beginning pipeline shutdown operation
DEBUG:azure.iot.device.iothub.pipeline.mqtt_pipeline:Commencing shutdown of pipeline
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting run_op in pipeline thread
DEBUG:azure.iot.device.common.pipeline.pipeline_stages_base:Cancelling SAS Token update alarm
INFO:azure.iot.device.common.mqtt_transport:Forcing paho disconnect to prevent it from automatically reconnecting
DEBUG:azure.iot.device.common.mqtt_transport:Done forcing paho disconnect
DEBUG:azure.iot.device.common.mqtt_transport:Cancelling all pending operations
DEBUG:azure.iot.device.common.pipeline.pipeline_ops_base:ShutdownPipelineOperation: completing without error
DEBUG:azure.iot.device.common.pipeline.pipeline_thread:Starting on_complete in callback thread
DEBUG:azure.iot.device.common.evented_callback:Callback completed with result None
DEBUG:azure.iot.device.iothub.sync_clients:Completed pipeline shutdown operation
INFO:azure.iot.device.iothub.sync_clients:Client shutdown complete
Traceback (most recent call last):
File "/Users/   /Downloads/azure-iot-sdk-python-2022-03-24/azure-iot-device/azure/iot/device/iothub/sync_clients.py", line 33, in handle_result
return callback.wait_for_completion()
File "/Users/   /Downloads/azure-iot-sdk-python-2022-03-24/azure-iot-device/azure/iot/device/common/evented_callback.py", line 69, in wait_for_completion
raise self.exception
azure.iot.device.exceptions.ServiceError: HTTP operation returned: 400 ArgumentError(Error: Bad Request)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "FileUpload.py", line 83, in
main()
File "FileUpload.py", line 74, in main
run_sample(device_client)
File "FileUpload.py", line 45, in run_sample
storage_info = device_client.get_storage_info_for_blob(blob_name)
File "/Users/    /Downloads/azure-iot-sdk-python-2022-03-24/azure-iot-device/azure/iot/device/iothub/sync_clients.py", line 582, in get_storage_info_for_blob
storage_info = handle_result(callback)
File "/Users/    /Downloads/azure-iot-sdk-python-2022-03-24/azure-iot-device/azure/iot/device/iothub/sync_clients.py", line 57, in handle_result
raise exceptions.ClientError("Unexpected failure") from e
azure.iot.device.exceptions.ClientError: Unexpected failure`

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

ID: 67ba5d41-7a78-bbfd-fb5f-bac5fcbccad1
Version Independent ID: 011d111e-c1cf-bb04-c749-b53f7c065833
Content: Upload files from devices to Azure IoT Hub with Python
Content Source: articles/iot-hub/iot-hub-python-python-file-upload.md
Service: iot-hub
GitHub Login: @kgremban
Microsoft Alias: kgremban

@ikumar222 Thanks for the feedback! We are currently investigating and will update you shortly.

@ikumar222 400 Error means there's something wrong with the value of one of your properties. I.e, please check the connection string and container name and path specified. Specify the complete path and see if that solves your issue,
Also, suggest you to report this issue on the Azure IoT SDK python repo: https://github.com/Azure/azure-iot-sdk-python/issues

Since you have raised an issue on the SDK repo, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


?module transform breaks with peerDependencies ranges

react-window is an in-the-wild example. It specifies "react": "^15.0.0 || ^16.0.0", and that causes transformed imports to become<EMAIL_ADDRESS>|| ^16.0.0?module.
https://github.com/bvaughn/react-window/blob/master/package.json#L67
Here's the result:
https://unpkg.com/react-window@1.5.0/dist/index.esm.js?module

Duplicate of #123.


Cmake error

Directory: /pgosm-flex-0.2.1/build#
Command: cmake ..
error : CMake Error: The source directory "pgosm-flex-0.2.1" does not appear to contain CMakeLists.txt.

My fault


FIX Recommendation Spinner

The current spinner does not fit the overall theme of the application

 UI Update #2: Improved Spinner


syntax error, unexpected end-of-input, expecting end

~ ❯ brew install tamada/tap/urleap                                                                                3s 00:21:04
Error: tamada/tap/urleap: /opt/homebrew/Library/Taps/tamada/homebrew-tap/Formula/urleap.rb:43: syntax error, unexpected end-of-input, expecting end

Sorry, long time no see.
I just fixed the error at 9046d09775b1acae9539670abd3fec507a572174, and bdb0e43346cd18462d62e2deee11fb41e200f8ac.
@jinusean
please check it out.


Return W3002 instead of E3002 for additional resources supported by package command

cfn-lint version: cfn-lint 0.35.1
Some resources supported by aws cloudformation package return E3002 Expecting an object...; they should instead return W3002 This code may only work with package cli command... when the resource value is a string.
Example:
$ cfn-lint --version
cfn-lint 0.35.1

$ cat myTemplate.yml
Resources:

  myStateMachine:
    Type: AWS::StepFunctions::StateMachine
    Properties:
      RoleArn: myRoleArn
      DefinitionS3Location: myLocalDefinitionFile.json

$ cfn-lint myTemplate.yml
E3002 Expecting an object at Resources/myStateMachine/Properties/DefinitionS3Location
myTemplate.yml:7:7

My team is specifically interested in support for AWS::StepFunctions:StateMachine DefinitionS3Location.  We would prefer to use package for our step function definitions so we can perform static analysis on the definition separate from the cloudformation template.  That would currently require an --ignore-checks E3002 flag when validating the template, but we consider that check too critical to ignore.
Resources currently supported by package are documented at:
https://docs.aws.amazon.com/cli/latest/reference/cloudformation/package.html
Exceptions for some of these resources are implemented in cfn-lint at:
https://github.com/aws-cloudformation/cfn-python-lint/blob/fe0af928a4ab26a6cedfd76564a26c9a4120b14f/src/cfnlint/rules/resources/properties/Properties.py#L179-L184
https://github.com/aws-cloudformation/cfn-python-lint/blob/fe0af928a4ab26a6cedfd76564a26c9a4120b14f/src/cfnlint/rules/resources/properties/PropertiesTemplated.py#L42-L47

Adding an exception for DefinitionS3Location ito resolve the issue with my example is simple enough: https://github.com/aws-cloudformation/cfn-python-lint/compare/master...asjohnston-asf:master
However, I haven't found any test coverage for these exceptions, I don't appreciate any nuance of the property type being S3Location vs DefinitionS3Location, and it appears to work with/without the added item in self.resource_property_types.extend, so I'm inclined to leave the PR to the professionals.

Thanks for the report. Should be fixed for the next upcoming release
Can workaround with resource-level ignores until then:
  Resource:
    Type: AWS::StepFunctions::StateMachine
    Metadata:
      cfn-lint:
        config:
          ignore_checks:
          - E3002

Thanks for the quick turnaround!

Could we reopen this ticket?
Seems still get the error, with release 0.44.7 and 0.46.0, still get below error.
W3002 This code may only work with `package` cli command as the property

I agree on this one as status code 4 is treated as an error in our GitAction failing our CI/CD

@stevehaneytrailblazer  - Seeing this today as well.
W3002     This code may only work with package cli command as the property (Resources/IAM/Properties/TemplateURL) is a string
CFN snippet:
  IAM:
    Type: AWS::CloudFormation::Stack
    Properties:
      TemplateURL: './iam.yml'
      Parameters:
        Environment: !Ref Environment
        OidcProvider:
          !Select [1, !Split ['//', !GetAtt EKS.Outputs.OpenIdConnectIssuerUrl]]

@isuftin  fwiw I found there are options to ignore warnings altogether or specific codes so you could employ one of these:
cfn-lint -t cf-templates/global-resources/cd.yaml -i W   which would ignore all warnings
cfn-lint -t cf-templates/global-resources/cd.yaml -i W3002  ignores just that specific code

@stevehaneytrailblazer
Of course , you can ignore. But this is not the right way.
The problem here is, the definiation for this error , it is not error(Exxxx), it should be belong to warning (Wxxxx)
Hope you get the point.
E3002 to W3002


Feature Request: do not transfer leader to stores that are applying snapshot

It is not easy to let PD know which TiKV is applying snapshot now, because most of the time, the snapshot applying is fast < 10s and latter SST file snapshot can reduce the problem too.
Now we have a is_busy field to do the similar thing, but later we still need to consider other dimensions to control the scheduler.

After #811, a store that has too many pending peers will be ignored by balancers.  You may reopen if you have any further information. /cc @andelf


Issue Running make_lastz_chains-2.0.6 on Test Data

Hello,
I encountered an issue when running the test data with the following command:
make_chains.py target query test_data/test_reference.fa test_data/test_query.fa --pd test_out -f --chaining_memory 16
The error I received is as follows:
### Nextflow process chain_run finished successfully
An error occurred while executing chain_run: Error! No non-empty files found at /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chain. The failed operation label is: chain_run

Traceback (most recent call last):
  File "/home/zhaohang/soft/make_lastz_chains-2.0.6/modules/step_manager.py", line 70, in execute_steps
    step_result = step_to_function[step](params, project_paths, step_executables)
  File "/home/zhaohang/soft/make_lastz_chains-2.0.6/modules/pipeline_steps.py", line 64, in chain_run_step
    do_chain_run(params, project_paths, executables)
  File "/home/zhaohang/soft/make_lastz_chains-2.0.6/steps_implementations/chain_run_step.py", line 113, in do_chain_run
    has_non_empty_file(project_paths.chain_output_dir, "chain_run")
  File "/home/zhaohang/soft/make_lastz_chains-2.0.6/modules/common.py", line 51, in has_non_empty_file
    raise PipelineFileNotFoundError(err_msg)
modules.error_classes.PipelineFileNotFoundError: Error! No non-empty files found at /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chain. The failed operation label is: chain_run

Any assistance on this would be greatly appreciated.
Thank you!

Hi @ZhaoHang-bio
Thanks for the bug report.
pls provide the following files:
test_out/run.log
and
test_out/temp_chain_run/chains_jobslist

The content of run.log is as follows:
# Make Lastz Chains #
Version 2.0.6
Commit: unknown
Branch: unknown

* found run_lastz.py at /home/zhaohang/soft/make_lastz_chains-2.0.6/standalone_scripts/run_lastz.py
* found run_lastz_intermediate_layer.py at /home/zhaohang/soft/make_lastz_chains-2.0.6/standalone_scripts/run_lastz_intermediate_layer.py
* found chain_gap_filler.py at /home/zhaohang/soft/make_lastz_chains-2.0.6/standalone_scripts/chain_gap_filler.py
* found faToTwoBit at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/faToTwoBit
* found twoBitToFa at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/twoBitToFa
* found pslSortAcc at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/pslSortAcc
* found axtChain at /home/zhaohang/anaconda3/envs/TOGA/bin/axtChain
* found axtToPsl at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/axtToPsl
* found chainAntiRepeat at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainAntiRepeat
* found chainMergeSort at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainMergeSort
* found chainCleaner at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainCleaner
* found chainSort at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainSort
* found chainScore at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainScore
* found lastz at /home/zhaohang/soft/bin/lastz
* found chainFilter at /home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/chainFilter
found chainNet in /home/zhaohang/soft/make_lastz_chains-2.0.6/chain_clean_micro_env
All necessary executables found.
Making chains for test_data/test_reference.fa and test_data/test_query.fa files, saving results to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out
Pipeline started at 2023-09-27 20:34:45.194169
* Setting up genome sequences for target
genomeID: target
input sequence file: test_data/test_reference.fa
is 2bit: False
planned genome dir location: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target.2bit
Initial fasta file test_data/test_reference.fa saved to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target.2bit
For target (target) sequence file: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target.2bit; chrom sizes saved to: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target.chrom.sizes
* Setting up genome sequences for query
genomeID: query
input sequence file: test_data/test_query.fa
is 2bit: False
planned genome dir location: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/query.2bit
Initial fasta file test_data/test_query.fa saved to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/query.2bit
For query (query) sequence file: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/query.2bit; chrom sizes saved to: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/query.chrom.sizes

### Partition Step ###

# Partitioning for target
Saving partitions and creating 1 buckets for lastz output
In particular, 0 partitions for bigger chromosomes
And 1 buckets for smaller scaffolds
Saving target partitions to: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target_partitions.txt
# Partitioning for query
Saving partitions and creating 1 buckets for lastz output
In particular, 0 partitions for bigger chromosomes
And 1 buckets for smaller scaffolds
Saving query partitions to: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/query_partitions.txt
Num. target partitions: 0
Num. query partitions: 0
Num. lastz jobs: 0

### Lastz Alignment Step ###

LASTZ: making jobs
LASTZ: saved 1 jobs to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_lastz_run/lastz_joblist.txt
Parallel manager: pushing job nextflow /home/zhaohang/soft/make_lastz_chains-2.0.6/parallelization/execute_joblist.nf --joblist /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_lastz_run/lastz_joblist.txt -c /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_lastz_run/lastz_config.nf

### Nextflow process lastz finished successfully
Found 1 output files from the LASTZ step
Please note that lastz_step.py does not produce output in case LASTZ could not find any alignment

### Concatenating Lastz Results (Cat) Step ###

Concatenating LASTZ output from 1 buckets
* concatenated bucket bucket_ref_bulk_1 to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_concat_lastz_output/concat_0.psl.gz
Concatenated 1 files in total into 1 files

### Build Chains Step ###

Sorting PSL files, saving the results to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/sorted_psl
/home/zhaohang/soft/make_lastz_chains-2.0.6/HL_kent_binaries/pslSortAcc nohead /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/sorted_psl /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_kent /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_concat_lastz_output/concat_0.psl.gz
Bundling psl files with the following arguments:
* input_dir: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/sorted_psl
* chrom_sizes: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/target.chrom.sizes
* output_dir: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/split_psl
* max_bases: 1000000
* warning_only: False
* verbose: False
Saving results to: /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/split_psl
Bundling 2 psl files in total
Written to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/split_psl/bundle.0.psl
DONE. Produced 1 files
PSL bundle sub-step done
Building axtChain joblist for 1 bundled psl files
Saving 1 axtChain jobs to /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chains_joblist
Parallel manager: pushing job nextflow /home/zhaohang/soft/make_lastz_chains-2.0.6/parallelization/execute_joblist.nf --joblist /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chains_joblist -c /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chain_run_config.nf

### Nextflow process chain_run finished successfully
An error occurred while executing chain_run: Error! No non-empty files found at /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chain. The failed operation label is: chain_run

I have a few more questions:

does the /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_concat_lastz_output/concat_0.psl.gz contain anything?
please open /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chains_joblist and execute the command in this file

Thank you for your assistance.
When I executed the command in /home/zhaohang/soft/make_lastz_chains-2.0.6/test_out/temp_chain_run/chains_joblist, I found that the axtChain command failed.
However, after making the necessary corrections, it is now running successfully.
Once again, I appreciate your help.

@ZhaoHang-bio
Sorry, but I didn't understand - is your problem solved? (if yes - I'd close the issue)
Please let me know what corrections did you do in order to make it work. Thanks!

Yes, I've resolved the issue and it's now running successfully.
The prior failure stemmed from not checking if the UCSC Kent software was functioning properly.
Upon running the commands in the chains_joblist file, as per your feedback, I identified the error message as axtChain failed to run, with the error: libssl.so.1.0.0: cannot open shared object file: No such file or directory.
By redirecting libssl.so to libssl.so.1.0.0 in the lib path, the program now executes without issues.
Thank you again.

Nice to hear that it worked for you!
Thank you for reporting the issue, I will add the respective note in the project's TODO.


Embed author (font-weight)
how it is: {font-weight: 700}

how it should be: {font-weight: 600}

Message author (font-size, letter-spacing)
how it is: {font-size:1.1em; letter-spacing: 0.5px}

how it should be: {font-size: 1rem;} (discord uses default spacing)

Embed footer
how it is:

how it should be:

Message reply author
how it is:

how it should be:

Im using rule overrides with !important in my project to fix these for now

I have some recommendations to help make your case a little better;

firstly; out of context snippets do not help much. I'd recommend taking full screenshots of embeds to compare.
secondly; it's difficult to compare when the content isn't exactly the same.
and finally; some screenshots comparing both before and after versus a screenshot from an actual discord embed would be a huge help.

@Tylertron1998  Thanks for the suggestion! I will add full screenshots of embeds for all the things I pointed out above.

from discord.com
using discord-components

As you can see, the font-weight for the embed-title, embed-author and embed-footer are off
Another thing I've noticed  is that the fonts being used are not complete. Discord uses separate .woff files for font-weights
Here's using discord-components with my overrides + added fonts

from discord.com
using my overrides + added fonts

using my overrides + added fonts

If you already have changes then feel free to make a PR

I can fix the CDN assets, assuming that zip is the one to replace it with.
I thought it was still correct but the fonts on the CDN are pre-rebranding.

Ahh that explains it, and yup, the zip is the one that replaces old assets.
I'll create a PR as soon as I fix the inconsistencies.


Installed apps current locale available status

Can this be detected? If so, it would be nice to signal if available or not, say below the checkmark: "XX" if available or "Add XX" if not ( where XX is current locale)
/LE: Detection using resources available locally that is.

Can this be detected?

Don't think so. The idea was good though, but I'm not going to dig into root access and do some fancy stuff over the .apk files only to see the locales it's available.
If anyone is up to look at how this could be done, well, help is appreciated.

Root is an exceptional thing, yeah don't bother then.

You don't need root to access the apk, don't you (only if paid on Play Store)?

You don't need root to access the apk

You are right on that now that I think about it, APKShare doesn't need root. But still, I would need to extract the package somewhere and then scan it looking for the strings. It would be nice there was a way to simply tell the locales, but copying the .apk somewhere, extracting it and scanning it, is not quite fast.

That could be displayed in the "discover repository" thing, don't you think?

Yeah @mquinson the idea was to show a text on the same "application" item on the discover repositories thing, but the problem is I don't know how to check which locales are available in the first place :/

Wouldn't it possible to make it a configuration item? As a user, that would definitely do the job.

Sorry? Configuration item?

Ok, sorry for my misunderstanding. I see 2 possible meaning of what you've said earlier:
(1) It is hard to find out which local the current user is prefering so you don't know what to display. In this case, just add a configuration item so that the user can tell you which local to use.
(2) It is hard to find out the current level of translation in each application of the list. In this case, the easiest is probably to do a partial checkout of the git tree, to find it out. I suspect that this is easier than messing with the apk file, but still not trivial.

First use system default, then allow him to change it.
No, the idea is, since it's installed, I should have access to its resources, and so I should be able to tell which language is translated and which isn't, and simply show "this installed application you have doesn't have the locale you're using" or similar.


Feature/k8s

Codecov Report

Merging #59 (71c4650) into master (b26daab) will increase coverage by 0.01%.
The diff coverage is 75.86%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
+ Coverage   52.57%   52.59%   +0.01%
==========================================
  Files          32       34       +2
  Lines        4487     4552      +65
==========================================
+ Hits         2359     2394      +35
- Misses       2128     2158      +30

Impacted Files
Coverage Δ

tests/test_conf.py
100.00% <ø> (ø)

turbo_tunnel/k8s.py
63.07% <63.07%> (ø)

tests/util.py
93.33% <94.44%> (+0.31%)
:arrow_up:

tests/test_k8s.py
100.00% <100.00%> (ø)

tests/test_tunnel.py
100.00% <100.00%> (ø)

tests/test_utils.py
98.71% <100.00%> (+0.05%)
:arrow_up:

turbo_tunnel/__init__.py
88.23% <100.00%> (+0.73%)
:arrow_up:

turbo_tunnel/utils.py
73.95% <100.00%> (-1.13%)
:arrow_down:

turbo_tunnel/websocket.py
86.32% <100.00%> (+1.96%)
:arrow_up:

tests/__init__.py
80.00% <0.00%> (-20.00%)
:arrow_down:

... and 14 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Simple BuildInfo plugin

Simple plugin to mimic sbt-buildinfo (https://github.com/sbt/sbt-buildinfo). Not remotely as fancy but so far worked without issues for us.
I will provide some tests in a later update.

build error on windows related to Foo.java and Bar.java which are not touched in this PR.
any advice welcome.

updated to be in a separate contrib folder and published as separate module.

added initial readme for plugins. it also mentions other available plugins. needs some polishing.

tests are also missing. I will add them later when I find a bit more time.
once we have sorted out how the contrib stuff will work properly I will also move the other plugins

@benjaminfrank I've given you commit access. This looks good overall, so feel free to merge once you've got tests, the build is green and you're comfortable with the code

cool, thanks. it will take some time to polish as work load is ramping up as fast as family duties. but I am still committed to see those PRs merged one way or another 👍

Finally found some time to add simple tests.
As so much time went by I need to validate the readme once more before this is good to go.

updated to master & moved documentation.
@lihaoyi @rockjam mind to have a quick look?

lgtm, feel free to merge

I do not understand why travis does have all those strange errors...

ok i found the issue: i changed some module definition


Creation of URLs from configuration variables and relations is done in multiple ways (code duplication)

There are differences in URL creation for the same component like Minio, MLFlow tracking URL
This is a source of errors and inconsistencies in the component.
Example:
https://github.com/canonical/mlflow-operator/blob/6d7b891bb3af07c460489b59803c07cd853af82f/charms/mlflow-server/src/charm.py#L91
https://github.com/canonical/mlflow-operator/blob/6d7b891bb3af07c460489b59803c07cd853af82f/charms/mlflow-server/src/charm.py#L345
https://github.com/canonical/mlflow-operator/blob/6d7b891bb3af07c460489b59803c07cd853af82f/charms/mlflow-server/src/charm.py#L360
https://github.com/canonical/mlflow-operator/blob/6d7b891bb3af07c460489b59803c07cd853af82f/charms/mlflow-server/src/services/s3.py#L71

Added to be fixed.

Low priority.

Fixed is merged.

The S3 URL is generated in more than 1 place currently, including the service class and charm. The value is the same for both (or should be).
Please add the unit test for the new methods.

The S3 URL is generated in more than 1 place currently, including the service class and charm. The value is the same for both (or should be).
Please add the unit test for the new methods.
S3 service should have namespace in it when it is created. As a result generation of S3 endpoint is different in S3 service.
However, it is not specified anywhere in S3 code.
Plan to fix:

Add comments on S3 service code usage: add note that service must have namespace in it when S3 service is created.
Add S3 service unit tests to validate the proper generation of S3 endpoint in S3 service code.

S3 service is used correctly in the code, i.e. with namespace:
https://github.com/canonical/mlflow-operator/blob/main/charms/mlflow-server/src/charm.py#L295

@Barteus
Here is proposed patch to finilize the fix. No unit test really necessary for this.
charms/mlflow-server/src/services/s3.py
@@ -14,6 +14,14 @@ class S3BucketWrapper:
     def __init__(
         self, access_key: str, secret_access_key: str, s3_service: str, s3_port: Union[str, int]
     ):
+        """Initialize S3 Bucket Wrapper.
+
+        access_key - S3 access key ID
+        secret_access_key - S3 secret access key
+        s3_service - S3 service URL that can include namespace
+        s3_port - S3 service port
+        """
+
         self.access_key: str = access_key
         self.secret_access_key: str = secret_access_key
         self.s3_service: str = s3_service

Added unit tests and comments as specified above:
https://github.com/canonical/mlflow-operator/pull/94

Fix is merged.


Edge Favorites and Sticky Notes

I've noticed that the current iteration of USTM does not appear to migrate favorites for the Edge browser, or existing Sticky Notes.  Is this something that is planned to be added in a future version?

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

ID: d92c930a-371f-16be-6427-06432a692259
Version Independent ID: 5bc2820d-989b-0fc1-f812-1a91f159fa25
Content: User State Migration Toolkit (USMT) Reference (Windows 10)
Content Source: windows/deployment/usmt/usmt-reference.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@officedocsbot assign @mypil

@officedocsbot assign @mypil

@BillerDude The current version of USMT can transfer Edge favorites. For sticky notes, you can migrate StickyNotes.snt placed under %appdata%\Microsoft\Sticky Notes. For this purpose, you can use custom XML.
@mypil Please guide the user how he can request for this feature.
Thanks.

@BillerDude - Thank you for engaging with the community here for the docs.
I know the product teams are always looking for user feedback on how to make Windows 10 better.
They keep a close tab on user feedback and it would be awesome if you could add your voice in
User Voice https://support.microsoft.com/en-za/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub
You might find others have made a similar request that you can add to, or you can open a new one. Let us know here if you do so we can up-vote your request.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


docs: Change postags to parts_of_speech

It seems that the docs use spacy.postags but the actual module that
can be found in spacy/ is parts_of_speech.

Signed-off-by: mr.Shu<EMAIL_ADDRESS>
@honnibal I am sorry if you would like to move parts_of_speech to postags but the sample code in index.rst was not working for me. These changes make it functional.

Yeah, I didn't update that snippet. Damn, thanks!

@honnibal there has been a merge conflict which should be resolved now and this pull request can be merged again.

It was easier just to apply this patch manually. Thanks.