chore(pypi): publish git-cliff on PyPI

Description
This PR updates the CI/CD for packaging git-cliff for PyPI.
Motivation and Context
Closes #150
How Has This Been Tested?
At time of writing this has not been tested.
Screenshots / Logs (if applicable)
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (no code change)
[ ] Refactor (refactoring production code)
[x] Other: packaging

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.
[ ] I have formatted the code with rustfmt.
[ ] I checked the lints with clippy.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@orhun Took a crack at this mostly following the example of typos which you linked in the related issue, modifying the approach to conform to the existing style in the workflow. Please let me know if you've spotted an error or would like to see any changes.
I've set this as a draft since this was an initial effort - I haven't really reviewed everything.

Codecov Report
Patch coverage has no change and project coverage change: -0.44 :warning:

Comparison is base (2d72125) 44.08% compared to head (a5a2413) 43.64%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #158      +/-   ##
==========================================
- Coverage   44.08%   43.64%   -0.44%
==========================================
  Files          12       12
  Lines         565      573       +8
==========================================
+ Hits          249      250       +1
- Misses        316      323       +7

Flag
Coverage Δ

unit-tests
43.64% <ø> (-0.44%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks for feedback/corrections! I'll have some time to take a look and incorporate your suggestions this weekend most likely.

One more general question I had: in typos PyPI packaging is handled in a separate workflow yaml. For this PR I integrated it directly into cd.yaml since that seemed to me to be more appropriate given how the workflow is currently structured and I thought would lead to the least amount of duplication. Do you agree with that decision or would you prefer refactoring to a separate file?

Great, looking forward to it! For testing purposes on another repository, is there a dry-run option available? Otherwise we can simply create RC releases I think.

Yes! I think we should be able to use TestPyPI: https://packaging.python.org/en/latest/guides/using-testpypi/

One more general question I had: in typos PyPI packaging is handled in a separate workflow yaml. For this PR I integrated it directly into cd.yaml since that seemed to me to be more appropriate given how the workflow is currently structured and I thought would lead to the least amount of duplication. Do you agree with that decision or would you prefer refactoring to a separate file?

I think it is good this way. We have the NPM packaging in the same structure as well.

Great, looking forward to it! For testing purposes on another repository, is there a dry-run option available? Otherwise we can simply create RC releases I think.

Yes! I think we should be able to use TestPyPI: packaging.python.org/en/latest/guides/using-testpypi.. which I guess isn't fully "dry" in the sense I think you mean, but might be better

Oh, nice. It is definitely better than a dry run.

Replied to some comments, there are two items to review still. I think we need to test it out against TestPyPI next

Looks good for testing now, how do we proceed?

You'll want to make an account with PyPI and TestPyPI -- they are separate, and generate API tokens that you can set in the repository secrets under the keys PYPI_API_TOKEN and TESTPYPI_API_TOKEN.
To roll it out, I can think of two options:
Option 1

Configure workflow to use TestPyPI and TESTPYPI_API_TOKEN (I need to look this up, but it should be an argument or envvar that is set on the maturin upload action)
Run workflow
Verify that everything works
Re-configure workflow to use PyPI and PYPI_API_TOKEN

Option 2
We tweak the workflow to use either TestPyPI or PyPI depending on the value of another repository variable eg. USE_TEST_PYPI. This is cleaner because it doesn't require editing the workflow to switch between the test and real package index.
If it doesn't work first shot, let's do some testing locally since it'll be faster to iterate than via Actions.

Seems the maturin upload command can be pointed to either PyPI or TestPyPI by adding an --repository <REPOSITORY> argument, with valid values being pypi or testpipy. Alternatively, the same values will be taken from the MATURIN_REPOSITORY environment variable. So maybe something like this:
publish-pypi:
  name: Publish PyPI packaage
  runs-on: ubuntu-22.04
  needs: [pypi-sdist, publish-binaries]
  steps:
    - uses: actions/download-artifact@v3
      with:
        name: wheels
    - name: Publish to PyPI
      uses: PyO3/maturin-action@v1
      env:
        MATURIN_PYPI_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
        MATURIN_REPOSITORY: ${{ vars.USE_TEST_PYPI == 'true' && 'testpypi' || 'pypi' }}
      with:
        command: upload
        args: --skip-existing *

Also, just noted a spelling mistake: "packaage"
I haven't used vars in a workflow before, and according to the docs, they are still a beta feature, so we can use secrets if you prefer.

In that case, we need to use PYPI_API_TOKEN or TESTPYPI_API_TOKEN respectfully as well, right?

Yes, you're right, like so:
      env:
        MATURIN_PYPI_TOKEN: ${{ vars.USE_TESTPYPI == 'true' && secrets.TESTPYPI_API_TOKEN || secrets.PYPI_API_TOKEN }}
        MATURIN_REPOSITORY: ${{ vars.USE_TESTPYPI == 'true' && 'testpypi' || 'pypi' }}

note I also suggest renaming the USE_TEST_PYPI repository variable to USE_TESTPYPI for consistency/correctness.

I can commit something when I'm done work, but please feel free to take over if you'd prefer

Alright, I think we're ready for a test run so long as all of the repository variables/secrets are set as discussed above and defined in cd.yaml. Let me know if you'd want me to squash commits.
Also, will running this workflow manually cause any issues or side-effects? We're good on PyPI thanks to the test repo but not sure about other bits..

Just want to note that when I tested locally just now the build command yields an error.
Not sure if this will also be a problem in the context of the PyO3/maturin-action@v1 action, but I'm guessing it would be.
$ maturin build --manifest-path git-cliff/Cargo.toml --release --out dist
📦 Including license file "/home/radu/github/git-cliff/LICENSE"
💥 maturin failed
  Caused by: Found a directory with the module name (git-cliff) next to Cargo.toml, which indicates a mixed python/rust project, but the directory didn't contain an __init__.py file.

I think we're good to go for real now. Remaining questions, which:

can you run the workflow normally in it's current form without messing up other deployments?
will the version of the python project be correct? maturin should pull it from cargo.toml before deployment, but I saw that the version updates are handled through release.sh. I think it should be called but I didn't look at it in depth.
will maturin run correctly in the context of the action? It runs fine locally now and produced an installable wheel

Alright, I think we're ready for a test run so long as all of the repository variables/secrets are set as discussed above and defined in cd.yaml. Let me know if you'd want me to squash commits.

Cool! I will squash the commits on merge so there is no need :3

Also, will running this workflow manually cause any issues or side-effects? We're good on PyPI thanks to the test repo but not sure about other bits..
can you run the workflow normally in it's current form without messing up other deployments?

cd.yml affects the other releases so I was thinking of releasing a "rc" release for testing this. Wouldn't that work?

will the version of the python project be correct? maturin should pull it from cargo.toml before deployment, but I saw that the version updates are handled through release.sh. I think it should be called but I didn't look at it in depth.

If maturin uses the version from Cargo.toml, that's perfectly fine. I don't see a version set anywhere in the workflow file so we should be good.

will maturin run correctly in the context of the action? It runs fine locally now and produced an installable wheel

I guess we will see 🐻

I will take a look at the code and add a review. But before actually testing this with a new release, I would like to release 1.2.1 first for the pending changes in main. Let's have a clean slate for PyPI :3
From the semver standpoint, would you say we need to bump minor for these changes since there will be a new package?

cd.yml affects the other releases so I was thinking of releasing a "rc" release for testing this. Wouldn't that work?

That should work with the downside that you're creating release candidates for something that isn't a core feature -- but because they're rc's it should be fine and not annoying to end-users? Maybe we're splitting hairs here lol, but here are some alternatives I can think of:

split off this workflow file and attempt to avoid code duplication through use of reusable workflows.
split off workflow file into separate repository that only exists to test the workflow with TestPyPi... maybe can even do this with my fork
maybe try using act locally? Since I think we just need to see that this workflow works with TestPyPi, you can temporarily edit (or copy) cd.yaml to remove cargo and npm publishing steps

I will take a look at the code and add a review. But before actually testing this with a new release, I would like to release 1.2.1 first for the pending changes in main. Let's have a clean slate for PyPI :3

Sounds good! Now that you mention it, it should be possible to test this workflow without consequence at least once with the release of 1.2.1. If you merge this PR first, the repository variable USE_TESTPYPI is true and TESTPYPI_API_TOKEN is set, and then you release 1.2.1, we should see a git-cliff==1.2.1 on TestPyPi - which will not pollute the eventual PyPi release.

From the semver standpoint, would you say we need to bump minor for these changes since there will be a new package?

I would agree with that!

Hey I started testing this in a separate branch and found this error: "working-directory" is not available with "uses". it is only available with "run" (message as reported by actionlint).

Alright, so I hacked away parts of the CD workflow until it got to the bits that are relevant to this PR (I jettisoned things like signing, npm publishing etc. that needed more set up in my forked repo).
Now failing at:
Run actions/download-artifact@v3
  with:
    name: wheels
Starting download for wheels
Error: Unable to find any artifacts for the associated workflow

See: https://github.com/radusuciu/git-cliff/actions/runs/5106471991/jobs/9178781857
I'll continue on it but just wanted to leave an update.

So I think I've sorted out all of the issues with paths that were causing problems. I still haven't managed to get a workflow to publish to TestPyPI though. Here's the latest:
https://github.com/radusuciu/git-cliff/actions/runs/5116808835/jobs/9199428899
##[debug]followSymbolicLinks 'true'
##[debug]implicitDescendants 'true'
##[debug]matchDirectories 'true'
##[debug]omitBrokenSymbolicLinks 'true'
##[debug]Search path '/home/runner/work/git-cliff/git-cliff/pypi/wheels'
/home/runner/work/_temp/d5019b40-47ac-4166-bc22-d10defe06b01/maturin upload --skip-existing /home/runner/work/git-cliff/git-cliff/pypi/wheels/test_pypi_deploy_git_cliff-1.3.1-py3-none-manylinux_2_31_x86_64.whl /home/runner/work/git-cliff/git-cliff/pypi/wheels/test_pypi_deploy_git_cliff-1.3.1.tar.gz /home/runner/work/git-cliff/git-cliff/pypi/wheels/test_pypi_deploy_git_cliff-1.3.14-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl /home/runner/work/git-cliff/git-cliff/pypi/wheels/test_pypi_deploy_git_cliff-1.3.14.tar.gz
🚀 Uploading 4 packages
💥 maturin failed
  Caused by: 💥 Failed to upload "test_pypi_deploy_git_cliff-1.3.1-py3-none-manylinux_2_31_x86_64.whl" (3.7 MB)
  Caused by: Failed to upload the wheel with status 400:

  <title>400 This filename has already been used, use a different version. See https://test.pypi.org/help/#file-name-reuse for more information.</title>

400 This filename has already been used, use a different version. See https://test.pypi.org/help/#file-name-reuse for more information.

  The server could not comply with the request since it is either malformed or otherwise incorrect.

This filename has already been used, use a different version. See https://test.pypi.org/help/#file-name-reuse for more information.

I incremented versions a bunch while testing and it seems that for some reason we're building wheels for two different versions. I'm planning on wiping all of my testing commits to see if it'll work when starting from a clean slate. It's possible that we're already there.

Hi @orhun, after a lot of back and forth, mostly dealing with issues related to paths, I've got a successful run of a pared down action: https://github.com/radusuciu/git-cliff/actions/runs/5123788390.
Here's the package on TestPyPI: https://test.pypi.org/project/test-pypi-deploy-git-cliff/

No worries!
Please feel free to tag me in if there's any issues

Hey @radusuciu, I created the RC release today and there was a build error: https://github.com/orhun/git-cliff/actions/runs/5911302728/job/16033716352
Can you look into it? 🐻

Just disabled win32-arm64 and released another RC, it worked this time! 🥳

https://test.pypi.org/project/git-cliff/

$ pip install -i https://test.pypi.org/simple/ git-cliff

Hey @radusuciu, I created the RC release today and there was a build error: https://github.com/orhun/git-cliff/actions/runs/5911302728/job/16033716352
Can you look into it? 🐻
edit: maybe we can disable win32-arm64 releases for PyPI...

Hmm, most of the references I've come across for this point towards issues installing ring due to something musl related but that doesn't make sense here.
I was just travelling but jotting down some links for later (may or may not be relevant, I'll look into it more)

https://stackoverflow.com/questions/68149955/rust-sorry-unimplemented-64-bit-mode-not-compiled-in/70628855#70628855
https://github.com/rust-lang/rust/issues/63939#issuecomment-665952545
https://github.com/briansmith/ring/issues/1488


v1.1.0

Implement function to convert genotypes of uncertain genotypes to ref/ref (0/0), which can be applied optionally

#11

Incorporate into the script conversion of variant representation to non-parsimonious form and conversion of uncalled variants to 0/0, which are currently done manually (see Canrisk manual v3)

#10
#14

Display genotype of PRS variants which failed depth and CNV overlap checks in their respective check files

#12
#13

Fix #15
No longer output empty check files if no variants are found which fail the checks

This change is

Successful jobs
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/GqZYB684qZgzqv6G35g5v6Kx
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/GqZYj2j4qZgb7Bzjjj2JzG73
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/GqZYj304qZgYQfv4J3K53g1K (expected to fail)
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/GqZYj384qZgfF197Bbv75Xkj

App rebuilt post-changes and re-tested.
dx run app-GqBkX2Q4zXGYbVvYyy9BpjvK \
-idepth=500 \
-isample_vcf=file-Gv7p2k04qZgXp6X7q5xK3Z1v \
-isegments_vcf=file-GqX0vFj4qZgXPVF629P8Bvq5 \
--name="test_convert_low_dp_and_cnv_overlaps_and_uncalled_vars" -y

dx run app-GqBkX2Q4zXGYbVvYyy9BpjvK \
-isample_vcf=file-Gv7p2k04qZgXp6X7q5xK3Z1v \
--name="test_input_conflict_no_segments_file_provided_and_convert_cnv_requested" -y

dx run app-GqBkX2Q4zXGYbVvYyy9BpjvK \
-idepth=500 \
-isample_vcf=file-Gv7p2k04qZgXp6X7q5xK3Z1v \
-isegments_vcf=file-GqX0vFj4qZgXPVF629P8Bvq5 \
-iconvert_gt_cnv=false \
-iconvert_gt_low_dp=false \
-iconvert_gt_no_call=false \
--name="test_no_dp_cnv_or_uncalled_conversion" -y

Links to jobs:
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/Gv7vQ304qZggf7FVv5zBzkqg
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/Gv7vQ2j4qZgX8Z1XZB00jg0P
https://platform.dnanexus.com/panx/projects/GqBkBFj4qZgbBbZy86yBQ10j/monitor/job/Gv7vQ384qZgjVbq1GFZGyg5z


vue-storefront got error in lastest updates pull

Error :
ERROR in /var/www/html/vue-storefront/core/helpers/index.ts
./core/helpers/index.ts
[tsl] ERROR in /var/www/html/vue-storefront/core/helpers/index.ts(165,33)
TS2339: Property 'observable' does not exist on type 'VueConstructor'.

I have switched the tags(branch) version in to v1.8.2.. Now its working fine. I think the latest version have some issues.. it's not stable now

Hey @rebinti, could you switch to 1.8.4 and check if problem you have appears there?
It also looks like you haven't run yarn command after switching versions.
Let me know if this helped you.

Now I create a new local git repository (branch : vuestorefront) for this. Now I tried to build storefront in my local.. but got above error. but works fine in server.  Any idea?

@patzick  I have used same repository for local and server

Now in our last commit seems
below
"remove . inactive core member ;<"
commit ID : 489eefb5a1c0d781bc48c3f7e94bc6f7735e68e7
is there any additional pull required

Hi @rebinti is this issue still valid?


Reference front file was not found at resources/reference_front/ZDT1.pf

Hi.
I just installed jMetalPy using pip install in the anaconda prompt, however for some reason the resources are not being installed properly.
Anyone else having this issue?
Thanks in advance.
Edit: I mean, I can install it manually, but I do not know where I should copy the resource folder if I want to use it on Anaconda's Spyder.

[CLOSED]
I manually downloaded it to my project's root folder, and it worked just fine.


Refactored Kafka transport

Implemented Kafka protocol
Splitted Kafka Receiver in Receiver (which implements transport.Receiver) and Consumer (which implements transport.Opener)

LGTM
now I can finally use kafka :D


Can you post an example?

Would it be possible to post a working example? The old PTSampler example doesn't seem to work anymore. In particular, the Sampler object doesn't have a keyword "iterations".

I suggest you go back to the 1.00 release https://github.com/willvousden/ptemcee/releases/tag/1.0.0
I don't think Will is (sadly) very active here anymore.

It's in the devel branch in the emcee repo
https://emcee.readthedocs.io/en/develop/user/pt/


errors shows in the output but not in the editor or problems panel

trmnl

output

however the extension always display an error at the end of the analyze
PHPStan: process exited with error, see log for details

and here is the output
[12/4/2024, 8:28:52 PM] [status-bar] Hiding status bar, last operation result = Error
[12/4/2024, 8:28:52 PM] [check:1] Check completed for file, errors= {"fileSpecificErrors":{},"notFileSpecificErrors":[]}

sadly am also using a bit of an old version of phpstan v0.12.99,however am not sure if there is something am missing to get it to display the results in the editor.

It could indeed be because of the old version. Are there any other errors being shown in the log? I get a lot of "deprecated" errors, which are causing the extension to think that something has gone wrong. Is it the same for you or is this all you see?

sorry for the delay, yes same here as well

Ah alright that explains it then. You should be able to ignore those warnings by using the phpstan.ignoreErrors setting, which takes an array of regexes. Let me know if that helps

thank you for ur help but currently its unusable and the error msgs are too many, when running the cmnd
phpstan analyze -c phpstan.neon --error-format=json --no-interaction --no-progress path/to/file.php

at some point i get
⚠  You're running a really old version of PHPStan.

The last release in the 0.12.x series with new features
and bugfixes was released on September 12th 2021,
that's 1190 days ago.

Since then more than 67 new PHPStan versions were released
with hundreds of new features, bugfixes, and other
quality of life improvements.

To learn about what you're missing out on, check out
this blog with articles about the latest major releases:
https://phpstan.org/blog

Upgrade today to PHPStan 1.8 or newer by using
"phpstan/phpstan": "^1.8" in your composer.json.

then more deprecation text & the last line is
{"totals":{"errors":0,"file_errors":0},"files":[],"errors":[]}%

Hmm I guess you could always try ignoring .* and just ignore everything. If that doesn't work then maybe it's just not possible :(

unfortunately the deprecation errors are unskippable, still thank you so much for your help.


Compiled example on IDX downloaded on a CT50  but application does not run

Thank you for your work and example provided!
I have managed to compile example on idx.google.com
I have made "flutter build apk" and loaded on my CT50 device, Android 6.0.1 , hw version MVT , aplication start but says Device Supported: False.
I can click on start / stop scanner but does not make something usefull.
Any hint would be highly apreciated !
Thank you,
Daniel

Update. I have borrowed and installed build test aplication on a EDA71 device and works nice !
Please if you can provide any hint what to try on CT50 since this is my device .
Can I restrict somehow Android release  ? EDA71 it's on android 10 . CT50 it's on Android 6.0.1
Thank  you,
Daniel

Hi, Android version should not be a problem. I have not tested any Dolphin CT50 my self but if it is on the default supported devices it should work, that list is provided by Honeywell.
I recommend you two things:

Try using a different version of the Data Collection library honeywell.aar simply download a newer or older version from from Honeywell portal, check the readme.
Debug the Android project and check whatever log or exception when starting the data collection service so you can see the cause.

Thank you Luis for guidance !
I did not found exactly honeywell.aar. I have found DataColection.aar inside honeywell-android-data-collection-sdk.zip
I have tried releases : 054 - and crashes totally
085, 096, 0143 and does not scan.
What seems to be strange it's that "honeywellScanner.isSupported();" reports that's not supported but device it's CT50.
I have upgraded this device to Android 6.0.1.  I see that there are 2 releases GMS and Non GMS. What would be preffered  ?
Another question : if I push side buttons for scanning on eda71 start scanner light even without sw started.  on CT50 nothing happens.
What else to check  ?  BEsides debug ( I don't have yet a docking station for usb debug -  I will try over ethernet)
Should I reupdate device to a GMS one ?  Are those devices depending on a licence per device that has to be installed locally ?
Thank you,
Daniel

Hi, yeah DataColection.aar is the original name of the .aar package in the Honeywell sdk, to use it you just need to rename it to honeywell.aar and copy it to your project.
If the honeywellScanner.isSupported(); returns false that means that the creation of AidcManager.create(context, this); didn't complete successfully, you can check it here:
https://github.com/luis901101/honeywell_scanner/blob/baa059841a89d6fbe2cd83e0890fbf0bab1f3c3b/android/src/main/java/com/plugin/flutter/honeywell_scanner/HoneywellScannerNative.java#L48-L55
Honeywell PDA's are scanners so the physical buttons will trigger a scan event no matter if you pressed the "Start scanner" button in the example app... what the "Start scanner" does is to listen to the scanner events... however, if my memory serves me correctly you can also disable/enable physical button scanning by setting properties through the plugin or through the PDA's system settings.
Something important here... If your CT50 does nothing when you press on the physical scan buttons then check the PDA's system settings so you are sure the scanner is enabled and active... the point here is to check the PDA works fine outside the plugin example so then you can check with the plugin... a simple test would be to open the browser or messages app or whatever app having an InputField, tap on the field and scan something... whatever get's scanned should be typed automatically in the InputField... this is a simple test, then you can try with the plugin.
Compare the EDA71 system settings with your CT50... make sure there are similar, or simply Restore to Defaults confs in your CT50
Regarding the GMS and non GMS I don't think it's related to the issue, for this you should check on the manufacturer info to see if they mention something related to the scanner and the GMS, but I doubt it.
The best way to know what's happening would be to debug the plugin running on the PDA 🤷♂...
These are my EDA51-1 System Settings

Thank you so much for continous support !
and please excuse me for wasting your time : let me explain :
I was kind of clueless , I have went with device to an authorised Honeywll service center , technician reinstalled the SW / android.
Now seems to scan but android keypad does not work and I cannot progress further for moment.
It seems that I am closer. For moment lesson learned it's that sw pack from oficial gateway it's not the best one....
Thank you,
Daniel

Once again thank you for your time and apologies missleading.
I have upgraded this device CT50 from Android 4 to Android 6.0 but it seems that I have not completed all the steps . I am missingsome system services related to Honeywell sensor . I am still digging to find our what's missing and I will update case maybe some others may try this .
Application works correclty now.
Daniel

Glad to help, I hope you get the solution soon 🤓.
“Application works well” you mean you can scan codes already?

YEs , application works now !
Unfortunately I still not know for sure how to completely upgrade the device .
For any one following this path / upgrading some old devices please follow article :
https://sps-support.honeywell.com/s/article/How-to-install-an-ECP-SCP-or-DCP-package-on-an-Android-device

statement  "Starting on Android 9 the Client Pack applications (SmartTE, BasicTE, Enterprise Browser and Honeywell Launcher) are now included in the Operating System." it's explanatory.
Thank you once again thank you Luis !
Daniel


Issues deploying the Pachyderm IDE

What happened?:
Ran pachctl deploy ide on a cluster where enterprise and auth are enabled. We ran into several errors:
The Helm package in pachctl is unable to create resources in the k8s cluster, even though running the Helm CLI works:
failed to deploy Pachyderm IDE: install failed: create: failed to create: an empty namespace may not be set during creation

Once we deployed manually with Helm, the 1.1.0 images are missing from DockerHub, so we had to manually specify the images to use:
pachctl deploy ide --dry-run --hub-image pachyderm/ide-hub:1.0.0 --user-image pachyderm/ide-user:1.0.0 > values.json

The 1.0 Hub image appears to be missing the health check endpoint, so the pod would never become ready. logs:
[I 2021-02-25 14:38:50.241 JupyterHub proxy:301] Checking routes
[W 2021-02-25 14:38:54.117 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.35ms
[W 2021-02-25 14:39:04.118 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.24ms
[W 2021-02-25 14:39:14.117 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.13ms
[W 2021-02-25 14:39:24.117 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.26ms
[W 2021-02-25 14:39:34.118 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.47ms
[W 2021-02-25 14:39:44.117 JupyterHub log:158] 404 GET /hub/health (@<IP_ADDRESS>) 1.34ms

I was able to work around this by disabling the readiness check in the Helm chart:
helm upgrade --install pachyderm-ide jupyterhub/jupyterhub --version 0.9.1 -f values.json --set hub.readinessProbe.enabled=false

What you expected to happen?:
The IDE should be deployed.
How to reproduce it (as minimally and precisely as possible)?:
We don't have a clean reproduction for the first Helm issue. The rest of the errors happen on the happy path.
Anything else we need to know?:
Environment?:

Kubernetes version (use kubectl version): 1.19.3
Pachyderm CLI and pachd server version (use pachctl version): 1.12.3
Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): Azure AKS
OS (e.g. from /etc/os-release):
Others:

The customer also ran into an issue where the default persistent volume name can be longer than 64 characters, because Pachyderm usernames are very long. The solution was to use the userid in the volume name template instead of the username itself:
helm upgrade --install pachyderm-ide jupyterhub/jupyterhub --version 0.9.1 -f values.json --set hub.readinessProbe.enabled=false --set singleuser.storage.dynamic.volumeNameTemplate='jupyter-volume-{userid}-{server}' --set singleuser.storage.dynamic.pvcNameTemplate='jupyter-claim-{userid}-{server}'


Profiling: archiveStates is slow

While syncing Altona, CPU profiler shows significant time spent in archiveStates, specifically, because we call stateCache.values, which iterates thru all states/contexts and copies them. Even though this is relatively lightweight, it adds up.
Is your feature request related to a problem? Please describe.
Slow stateCache.values is a bottleneck.
Describe the solution you'd like
avoid calling stateCache.values alltogether. Ideally, we should be able to use the information from the forkChoice (with some minor refactoring) to figure out which stateRoots to remove. Currently, it seems we immediately delete the old forkChoice data, and only delete the old stateCache afterwards as a "task".
Describe alternatives you've considered
Make copying/cloning cheaper (we should try to do this too)

One solution could be to have forkChoice be an EventEmitter with a pruned event, emitting the pruned BlockSummarys. This information could be used to archive both the states and blocks more efficiently.


Use rolling app deployment feature in CF CLI

https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html

Great, thanks @asudoh!

Thanks @abdonrd - We found that IBM Cloud CLI doesn't seem to support the CF version with rolling deploy feature v7. So it's likely that we need to wait for a new IBM Cloud CLI version (though I may be wrong).

I see we can force a CF CLI update with: ibmcloud cf install -v 7.1.0


Allow Institutions (specifically Funders, i.e., USGS, etc.) to create Public Customizations

Currently only DMPTool Admins can create public customizations. It would be nice if the funders could customize public DMPs that they create.
Case:   USGS can create a "public" DMP template, but USGS admins can only create customizations that their "USGS" logged-in users see. It would be great if USGS customizations could show up for anyone who creates a USGS DMP.

I agree with Sherry re adding a funder-level admin role or the need for some other solution to cross-cut institution-level customization and maintenance


[scala] Fix link for 3.3

There is no changelog for 3.3.1 and 3.3.2.

According to https://scala-lang.org/download/ the latest release is 3.3.0, there is no 3.3.1 or 3.3.2. Perhaps there once was a tag and our automation didn't recognize that they are removed later.

Looks like I was the one that did the mistake in 9d1afec8d72cfe53d2135a599b10720362905387.

Fixed. Updated the PR title and description.


clarification arround UPN

This statement is not clear:
The UPN you use to subscribe to Azure Virtual Desktop must exist in the Active Directory domain the VM is joined to.
Is it requried that the UPN is configured for the user or is it really enough if the upn is present?

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

ID: d2eeca14-80ef-c0b4-2719-80ceb286ba3d
Version Independent ID: b7d3df23-3158-2807-eecc-73e7230c2033
Content: What is Azure Virtual Desktop? - Azure
Content Source: articles/virtual-desktop/overview.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@marcelkmfst Thank you for the feedback!  I've assigned this to the document author for clarification.

#label:"virtual-desktop/overview.md"

Thanks for the feedback. This was referring to a specific hybrid identity scenario if the UPNs or SIDs in AAD and AD didn't match for a user.  I have clarified this and the change should be visible later today.
#please-close


Retain highlighter during pdf convert

Tested block:
<mark>multicolor highlighter</mark>
==multicolor highlighter==
[[#green]]==multicolor highlighter==
Currently highlighted texts are printed as normal text without background

after this code change converted pdf will have highlighted text and it will work well with the logseq text wrap plugin

Thanks for the PR!


Table 5901 : Service Item Line - Out of Memory

Create a new Service Item Line and select a first "Repair Status", "Service Price Group", ...
--> Out of Memory
Response Time (Hours) - OnValidate()
Calls "UpdateResponseTimeHours;"
IF ("Response Time (Hours)" <> xRec."Response Time (Hours)") OR ("Response Time (Hours)" = 0) THEN BEGIN
    SkipResponseTimeHrsUpdate := TRUE;
    GetServHeader;
    CalculateResponseDateTime(ServHeader."Order Date",ServHeader."Order Time");
  END ELSE
    UpdateResponseTimeHours;

UpdateResponseTimeHours()
Calls VALIDATE("Response Time (Hours)",CalculateResponseTimeHours)
  IF NOT SkipResponseTimeHrsUpdate THEN BEGIN
    IF "Response Time (Hours)" <> xRec."Response Time (Hours)" THEN
      VALIDATE("Response Time (Hours)",CalculateResponseTimeHours)
    ELSE
      IF "Response Date" = 0D THEN
        VALIDATE("Response Time (Hours)",CalculateResponseTimeHours)
      ELSE
        "Response Time (Hours)" := CalculateResponseTimeHours;
    SkipResponseTimeHrsUpdate := FALSE
  END;

Nice catch! Let's get the issue to a team who will fix and backport it, as this repo only is for extensibility related issues in the upcoming release. We suggest that you open a support case or file a bug in Collaborate.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using. Here's a link to Collaborate: https://developer.microsoft.com/en-us/dashboard/collaborate/engagements/1173/feedback/wits/Bugs/create.
Thanks for reporting the issue.


Verify printed book is fine

We have submitted the final book cover and contents to the publisher.
Norm and I are waiting to receive the publishing proofs to ensure that the final printed book is okay.  As Mario has commented to us, verifying proofs is important :-).
If the publishing proofs are okay, we will announce on the metamath mailing list how to get a copy of the physical book and start the process of getting it on Amazon. Amazon will be the more expensive way to get it, but it will make the book visible to people who might not otherwise see it.

It looks great!!


BOT: .send message does not say FLUX

needs deploy https://github.com/webaverse/ethereum-bot/commit/7137aa7e1f7fd20c6af18ccb9db337de96d78832

needs deploy https://github.com/webaverse/ethereum-bot/commit/7137aa7e1f7fd20c6af18ccb9db337de96d78832

Deployed.

Deployed.


Draw paths to objectives

Use the pathfinding implementation in toolbox to obtain paths to quest objectives, then draw those paths over the toolbox minimap

I know that the pathfinding module is not completely functional yet, but leaving this as a reminder. I'll try to tackle it next week once I get home from holidays

Oh I see the logic already exists in the QuestModule, but currently the module is not hooked up anywhere

More logic needs to be written around how and when to recalculate the path based on the players position between points and the end point. You can turn it on with a few lines of code, and I’m sure you’ll come across the same issue I did

Idk why the custom renderer doesn't draw the lines for the waypoints, but I see the issue with the quest markers

So I think the reason the logic keeps spamming marker updates is because, first you call calculate, which sets the current waypoint to 0, so the logic updates the marker to the waypoint 0 (that is the player position).
Then, almost immediately, Update() calculates the correct waypoint, detects that the waypoint is different than waypoint 0 and Updates the UI

Taken discussion onto discord


Update the Travis config to support the newer version of SQLite for Django 2.2

Description
After upgrade to Django 2.2. The minimal supported version SQLite is increased from 3.7.15 to 3.8.3. The latest version of SQLite on the default distribution of Travis CI is 3.8.2.
Rationale
We need to upgrade the Travis CI distribution from 14.04 to 16.04 (xenial).
Use case(s) / visualization(s)

Thanks! Would you mind removing the sudo: true as well? It's deprecated now.

Sure. I just pushed the new commit. Thanks.

Awesome, thanks 🎉


UI: driver checksum does not say which algorithm is used for checksum

Version: v2.2.2-rc1
Version: v2.1.8 (pre-existing issue)
What kind of request is this (question/bug/enhancement/feature request):
Bug, usability
Steps to reproduce (least amount of steps as possible):

Add a node driver look at the checksum field

Result:

The algorithm is not listed. I presume this is just an md5 hash, but could we say which? this way if we need to troubleshoot, etc we can calculate our own hash for the image, etc.
I would like to propose simply changing %modalEditDriver.checksum.help% to:
Optional: Verify that the downloaded driver matches the expected checksum (ALGORITHM_HERE).
Other details that may be helpful:
Useful for support / testing purposes. As an end user I need to know what type of algorithm.

Is pre-existing issue; should probably remove from v2.2.2 milestone.


Filtering default exclude values based on the include passed in

What do these changes do?

Related issue number
Resolves #362

[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff
[x] passes black --check modin/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/219/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/280/
Test PASSed.


feat: eventfd syscall

Test cases: https://github.com/YXalix/starry_fastdds_testcases/pull/7/files
Test evidence:

Maybe you can condense the number and content of your commits through operations like rebase.

Maybe you can condense the number and content of your commits through operations like rebase.

@Azure-stars Good point. I normally use squash merge to do so, but seems this feature is missing in GitHub.

Oh, I made a wrong force push...


Documentation site down: 404 not found

I have been trying access the torchrl documentation site provided at the following link and I keep getting 404 page not found response like this:

Did it move to another site? I can't find any indications on that and this repo cites that link for the official documentation.

+1
Same here -- is anyone working on a fix?

Not sure what broke there... I'll have a look asap

The documentation is back online!


Comment out empty Moniker for schild-report.schild-report

Microsoft Reviewers: Open in CodeFlow

Intentional
[Policy] Reset Labels


Run the workflow hourly and switch to a new implementation

Description
Run the workflow hourly. Also ups the action version to 0.0.6β which fixes the API abuse problems.
Technical details
The new implementation adds the issue to the project first, and uses the response to determine if the issue was already in that particular project. This eliminates the need to pull in every single card from the project when adding the new cards.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors. Not locally per se, but in purelyfortesting.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@kgodey to work around GitHub abuse detection, the action first adds the issue to Active Sprint (to check if it can be added, and is thus not already present in the project), then deletes it and adds it to the Backlog. It creates two entries in the activity but works perfectly fine otherwise:


Keyword Error

facing object 'dashboard' is not J-Son serializable

Hi! Yes, the Dashboard object is not JSON serialisable by default and we did not implement specific method to dump it is as a JSON yet. But we are considering this direction though!
Are you trying to do something like:
import json
dashboard_json = json.dumps(dashboard)

?
Could you please tell us more about the end problem you are truing to solve? We might be able to suggest something.

Hey @achandras1597!
Despite the fact that we do not have a specific method to dump dashboard as a nice JSON file, we implemented a quick solution for you.
We implemented methods ‘_json()’ and ‘_save_to_json(path)’ for Dashboard class. Current implementation dumps the whole Dashboard data into the JSON, which is probably way too much! :) But these methods are already available (you will need to update the package), so you can give it a try.
This is an example of the JSON generation:
drift_report = Dashboard(reference_frame, current_frame, column_mapping = None, tabs=[DriftTab])
drift_report._json()

And  an example of the saving JSON file:
drift_report = Dashboard(reference_frame, current_frame, column_mapping = None, tabs=[DriftTab])
drift_report._save_to_json('filename.json')

Also, we added —output_type parameter for terminal mode, so now you can choose ‘json’ option there as well:
python -m evidently analyze --config config.json --reference reference.csv  --current current.csv --output_path save_report_here --output_type json

Hope, this will help!


Vespr Blog added

Checklist

[X] I have read the How to Contribute.
[X] I have run yarn build after adding my changes without getting any errors.

It's "blog" not "bug".

thanks @katomm - sorry; they do look similar if your eyes are a little shaky 😅


Decide on what "robust" and "default" solvers are for pymbar before 4.0 launch.

Decide what solver sequences to recommend for "robust" and "default", beyond what is proposed in #446.

Dealing with this as part of #469


Fixed broken links for ASP.NET Core

Proposed changes
Fixed two broken links for development with ASP.NET Core.

Deploy preview for docsdocker ready!
Built with commit 30e1a7d3415b1722bb194d0422afc22aa8ae72b0
https://deploy-preview-9633--docsdocker.netlify.com


My Unity application receives notifications with the application closed on some devices and NOT on others

Notifications are received with the app closed on a Huawai Y6 with Android 8 and are not received on a Huawai Y5 with Android 6

Just to clarify, I assume you are sending notifications through the firebase console for your project?  Are you sending to the specific device via the token, sending via a topic, or just sending to the application?
If the app is running, do you see the messages coming through then?

As an update, I've contacted some of the folks that might have a better understanding of why this might occur, as it is likely not a Unity specific issue.  Apparently there have been some problems similar to this with Huawai devices in the past that have to do with battery optimization preventing messages from going through, which might be the cause of your problems.

For context, there is a description of this here https://stackoverflow.com/questions/38016196/firebase-cloud-messaging-not-received-when-app-in-background


Revise WAMP docs (router code moved)

Now that the router code has moved to Crossbar.io, revise the docs accordingly ...

This is done now:
  doc/wamp/programming.rst:Starting with release 0.9.4, all WAMP router code in |Ab| has been split out and moved to `Crossbar.io


INFO logging seems more like DEBUG

Examples from: ilab generate --pipeline full
INFO 2024-07-27 00:46:23,461 instructlab.sdg.llmblock:50: LLM server supports batched inputs: False
INFO 2024-07-27 00:46:23,461 instructlab.sdg.pipeline:172: Running block: gen_questions
INFO 2024-07-27 00:46:23,461 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response'],
    num_rows: 5
})
INFO 2024-07-27 00:53:06,986 instructlab.sdg.pipeline:172: Running block: eval_questions
INFO 2024-07-27 00:53:06,987 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response', 'num_samples', 'question'],
    num_rows: 146
})
INFO 2024-07-27 00:58:05,372 instructlab.sdg.pipeline:172: Running block: gen_responses
INFO 2024-07-27 00:58:05,373 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response', 'question'],
    num_rows: 27
})
INFO 2024-07-27 00:58:29,652 instructlab.sdg.pipeline:172: Running block: evaluate_qa_pair
INFO 2024-07-27 00:58:29,652 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response', 'question', 'response'],
    num_rows: 18
})
INFO 2024-07-27 00:59:09,898 instructlab.sdg.pipeline:172: Running block: filter_qa_pair
INFO 2024-07-27 00:59:09,899 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response', 'question', 'response', 'evaluation', 'score'],
    num_rows: 18
})
INFO 2024-07-27 00:59:10,443 instructlab.sdg.datamixing:123: Dataset columns: ['task_description', 'seed_question', 'seed_response', 'question', 'response', 'id', 'messages']

Opinions may vary on this.  INFO logging should generally be used for messages appropriate for end users and not so chatty that it couldn't be left on all the time without being annoying.  Some of these messages are probably fine but could be a little more user friendly.  Exs:
LLM server supports batched inputs: False
Running block: gen_questions
Running block: eval_questions
Running block: gen_responses
Running block: evaluate_qa_pair
Running block: filter_qa_pair

They are probably all fine but better written as sentences that give the user the context to know what's going on.
Others feel more like debug.  Exs:
INFO 2024-07-27 00:46:23,461 instructlab.sdg.pipeline:173: Dataset({
    features: ['task_description', 'seed_question', 'seed_response'],
    num_rows: 5
})
INFO 2024-07-27 00:59:10,443 instructlab.sdg.datamixing:123: Dataset columns: ['task_description', 'seed_question', 'seed_response', 'question', 'response', 'id', 'messages']

Perhaps there is some useful INFO there like how many tasks are being processed.  A sentence stating that would probably be more appropriate for an INFO log.  Otherwise it might be better to move a bunch of these to debug.

still relevant


Issue with special characters

Unfortunately complicated passwords may contain special charcaters that need escaping.
Most of all if the password contains ":" then there regex will fail.
I suggest changing it from PATTERN = re.compile(r'^(.*):(.*):(.*):(.*):(.*)$', re.MULTILINE)
to: PATTERN = re.compile(r'^([^:\n]*):([^:\n]*):([^:\n]*):([^:\n]*):([^\n]*)$', re.MULTILINE)
However in addition to ":" and "" I also found "," that will need escaping.
So I'd suggest to add the following to the _sanitize_str method...
.replace(r',', ',').replace('\\', '\')

Thanks, will look to make these changes when I can next jump in the code. Working on the next version is bubbling up in my list.


Starknet DA

Hi,
Starknet use blobs or calldata for DA Layer.
I think it would be good to indicate it to highlight that they were the first to implement it.

I see it's implemented thank you !


Reddening correction

Correct for the different distortions caused by dust in different parts of the sky (dec, ra). Dust causes reddening, and we can download the correction vector (with a transformation) from SDSS.

The class prior probabilities also change with location in the sky. Stars are more common in a certain band (Milky way).

With the correction for dust extinction, there are three sets of correction. Apply each of them (subtract them from the magnitudes) and plot the heat map.
Here's a prediction. Before the correction, the classes diffuse in the feature space. They are smoothed out, with a lot of overlap. Now the best correction should unstretch and move the classes back in the right direction, giving us a more compact set of classes. That is, we should get the least amount of class ambiguity afterwards.
But how do we measure class ambiguity? Here's an idea. If we have relative probabilities, then we can look at how sharp these probabilities are. Perhaps a better method is to simply look at the confusion matrix on the test set. The confusion matrix and the derived accuracy rates should correlate well with the level of class ambiguity. Plot these measures on a heat map.

Another note on class ambiguity. Suppose that we have unbalanced classes in our training set. Then we can infer the proportion of the smaller classes.that need to be in the overlapping region, which we will feed into the classifier. This is where active learning might be of use, in addition to outlier detection.


Inquiry: Actual objects dimensions

Thanks for the valuable work. Can we extract the actual dimensions/size (width, height) for objects in real-world units such as centimeters?

No, this is a different computer vision problem...


docs(typo): more proofreading [ci-skip]

Corrected a few other typos.

@PLNech it's "ci skip" :dancer: no big deal


Panic: no Auth Provider found for name "gcp"

Greetings!
I'm using the configuration as follow in this Pastebin:
Panic: no Auth Provider found for name "gcp"
This is the Pastebin go.mod: go.mod
I'm running:

GKE Cloud: 1.17.9-gke.600

GO:  go1.14.6 linux/amd64

Kubectl: Major:"1", Minor:"18", GitVersion:"v1.18.3"

Ubuntu: 5.3.0-1032-gcp #34~18.04.1-Ubuntu SMP

This is the error that I got:
Log file created at: 2020/08/05 05:49:49 Running on machine: gke-admin Binary: Built with gc go1.14.6 for linux/amd64 Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg F0805 05:49:49.453823   20353 k8s-deploy.go:62] Could not read kubeconfig /home/infraops/.kube/config: no Auth Provider found for name "gcp"
Can anybody help me with this please?, thx in advance

have you enabled the auth plugin? see https://github.com/kubernetes/client-go/blob/master/examples/out-of-cluster-client-configuration/main.go#L33-L40 for examples of enabling all auth plugins or just the gcp one

Regards!
Thx for your response, when I enabled the plugin it threw me the following
error:
~] ./k8s-deploy.go:37:9: imported and not used: "
k8s.io/client-go/plugin/pkg/client/auth/gcp"
But, 'cause you ask me about it, I uncommented the line again and I solve
the problem with this alias " _ ", so the import plugin stayed like this:
_ "k8s.io/client-go/plugin/pkg/client/auth/gcp"

Now, it's working, sorry for my lack of experience.
Thank you again.
On Wed, Aug 5, 2020 at 8:54 AM Jordan Liggitt<EMAIL_ADDRESS>wrote:

have you enabled the auth plugin? see
https://github.com/kubernetes/client-go/blob/master/examples/out-of-cluster-client-configuration/main.go#L33-L40
for examples of enabling all auth plugins or just the gcp one
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/client-go/issues/839#issuecomment-669175919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH3UJT5MZISJSSQTJNUYYDR7FJAHANCNFSM4PVDZSGA
.


  This happens most commonly with Web comics but also with sites like Flickr.  This never happens on the Web.  This issue has been happening for months to perhaps even years.  It is not consistent within a single feed — sometimes an image will load, sometimes it won't.  The same thing affects the images in the article list.  I have had trouble reproducing this with a debugger attached, but figured I might as well post a few examples here from today:

You can see below that 4 recent xkcd comics loaded fine, and 2 didn't.

Do you have Offline images enabled? We rewrite image URLs when that preference is turned on, choosing to use the local copy instead of the remote copy. It's possible the local copy is not fully downloaded but we use it anyhow.

(Whoops, didn't mean to close it!) Yes, I have offline images enabled.

Closing this; please re-open if it still occurs for you (and provide steps to reproduce).


Snippet tabstop selecting content of previously entered variable only works when separated by space

VSCode Version: 1.10.2
OS Version: Windows 10 Enterprise

Steps to Reproduce:

Create and load snippet for language javascript:"import": {
  "prefix": "imp",
  "body": "import ${2:${1:module}} from '${1:module}'$0",
  "description": "Default import"
}

Open .js file, type imp
Press TAB, type styled-components (you now have import styled-components from 'styled-components')
Press TAB again, cursors don't move and you could now continue typing at the end of what you just typed. This is unexpected.

Expected:

Press TAB again, the first styled-components is selected and you can start typing to overwrite it, e.g. by pressing TAB and typing styled, creating import styled from 'styled-components'

The whole thing works as expected when the snippet body is this: import ${2: ${1:module}} from '${1:module}'$0 - except that you then have a whitespace where you didn't want one.

For better multi-cursor support we replace the snippet controller and that also fixed this issue

Still an issue when you accept the content assist's proposal instead of exiting content assist with Escape.

@chrmarti You were seeing #27898  which we fixed late

VSCode Version: Code - Insiders 1.13.0-insider (eaa887c507e1614f90c9f04a30ceda775759e814, 2017-06-06T10:23:09.381Z)
OS Version: Darwin x64 15.6.0
Extensions:

Extension
Author
Version

vscode-eslint
dbaeumer
1.2.11

cpptools
ms-vscode
0.11.4

Still an issue:

not severe for May


font and borderWidth options

Two new options in the MDCSwipeToChooseViewOptions class:
borderWidth (pass nil to default width)
font (pass nil to default font)
for Liked and Nope options.

@gali8 please discard project.pbxproj from your pull request. I will merge after that.

+1 @modocache it would be great if you could merge this request.

+1 looking forward to this request


feat: Allow setting the sitename when creating site from backup.

This PR includes the ability to name a site when you create it from a backup, and a few copy changes!
https://user-images.githubusercontent.com/142006/130287266-4d836320-4abd-4802-b811-54140ab26c47.mov
I also resolved a small bug where the site you selected during the add site flow would persist the next time you went to clone from a backup.

Just pushed up a few changes:

Make the disabled radio button scale with the width of the screen.

Before this change:

After:

When you click "log in" on the add-site screen, we will now close the add-site modal. This is because it does not auto reload when you login.

Add new copy for when a user isn't logged in, versus when the user is logged in with no active providers.


identity: add support for "associate"

Add support for "associate" turnpike types.

There's x.509 too. e.g:
{
  "identity": {
    "auth_type": "X509",
    "type": "X509",
    "x509": {
      "issuer_dn": "/O=Red Hat/OU=prod/CN=Certificate Authority",
      "subject_dn": "/C=US/ST=North Carolina/L=Raleigh/O=Red Hat/OU=Cloud Services<EMAIL_ADDRESS>    }
  }
}

Ah good point. I'll add an "x509" too. Maybe even an error check in EnforceIdentity that makes sure "type" is one of the valid types.

Codecov Report

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

@@            Coverage Diff             @@
##           master      #14      +/-   ##
==========================================
- Coverage   86.88%   86.00%   -0.89%
==========================================
  Files           2        2
  Lines          61       50      -11
==========================================
- Hits           53       43      -10
+ Misses          7        6       -1
  Partials        1        1

Impacted Files
Coverage Δ

identity/identity.go
100.00% <ø> (ø)

request_id/request_id.go
72.00% <0.00%> (-3.00%)
:arrow_down:

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 92eb73c...bce4a36. Read the comment docs.

LGTM


Lessen AppCore dependency, remove double-define

Removes some #import "APCAppCore.h" and replaces them with the individual imports needed by the class.
Also removes the kLastUsedTimeKey double-define and moves the one last-used-date capture into AppDelegate.

r=me


y211ga Cameras. Was it a bad idea to update to <IP_ADDRESS>_202202170022? Motion detection is completely silent.

I got two cams of the type y211ga. Before I installed the hack 0.2.0 I read through the discussions and as suggested there updated the cams with the official app first. Now I am at <IP_ADDRESS>_202202170022 on both and have one problem. Motion detection is dead silent. I tried the official addin and MQTT and both say nothing when I hop around in my room. Detection is active in the official app, no paid service was chosen.
I made shots of the whole config. Maybe I am just too stupid: https://photos.app.goo.gl/Eur5NTmZDA2zyu1y7
Any idea?

backup QFUSY65V64.zip
Full Backup script made dump off the new firmware. Maybe useful? This one was made BEFORE hacking.

A friend bought the same cameras and yet did not update or hack anything. This is the firmware in v9 range
backup_v9.zip

About the comparison between the 2 versions above, it's not clear.
For sure home and backup partitions are upgraded (mtdblock3 and mtdblock4 are different).
But the other partitions are also different, and I think that nobody would do the OTA update of the bootloader, kernel, etc...
I don't know...

Is there a possibility of downgrading the firmware? I also have the <IP_ADDRESS>_202202170022 and no motion detection after the hack. Of course I only have a backup with version <IP_ADDRESS>_202202170022, but here is a zip with version <IP_ADDRESS>_202105081647. How do I get it into my YI 1080p Home IFUS?
Thanks in advance

There is the way the former unbrick hard way says... Soldering and Serial on UBoot. I have no clue if it's doable to use DD command via telnet to overwrite the partitions. Likely it will die while doing that. RAW Overwriting the OS from the OS sounds like a terrible idea... I think if you don't want to solder (I would prefer not to) we have to wait until it's supported. That's why I passed over my 11.x backup and the 9.x one from my friend.

The soft unbrick is possible without soldering.
Check the wiki and this thread:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/305

Sure, but we have more than just partition4 aka Backup changed...

You can use the soft method for all partition.
But avoid to use it for u-boot.

Hmm, OK. Then I need to tinker a bit with that on weekend. I just read of the backup dump there, so I thought that's it. So it does use all dumps I give to it on recovery file creation?

You have to copy these files on your SD and reboot the cam (and wait 10 minutes).
Start with backup, then home.
Probably kernel and rootfs are not necessary.
Avoid env and uboot.

Alright, so one file only and then two 10 minute sessions for the two partitions. I will keep you updated. ^^

So, good news. I did as you said, first backup, then home AND skipped the kernel image. Result:

The app now detects movements and sometimes even sounds, without the Kami Cloud paid for.  But the sensors MQTT and official addin do not do much yet... Likely my MQTT settings are wrong? https://photos.app.goo.gl/Eur5NTmZDA2zyu1y7 Pics off the old non downgraded one and 0.2.0 Hack, but the settings I took 1:1 of these again. Do you see any stupidity here? Or is the kernel maybe still the problem here?
P.S: The 0.2.1 hack reduced the lag from RTSP down to less of a second :D

OK, I disabled all the advanced advertisement and now... IT WORKS !!!!! No clue why, but it works great :D
OK, so I have to decide between motion and human detection, right?
Btw, the 11.X firmware claims to add animal, vehicle and improved person detection. (And Activity Zone for these and timestamps for the videos) Just to let you know that maybe the new firmware might be interesting to add somewhere in far future.

OK, so I have to decide between motion and human detection, right?

Yes.

Btw, the 11.X firmware claims to add animal, vehicle and improved person detection. (And Activity Zone for these and timestamps for the videos) Just to let you know that maybe the new firmware might be interesting to add somewhere in far future.

I'm not sure but I think that new feature are "server side".

Alright. In this case. First: THANKS for help! All is fine now and this way to downgrade can be used to get back to a working state for others. I will close this one now.

Alright. In this case. First: THANKS for help! All is fine now and this way to downgrade can be used to get back to a working state for others. I will close this one now.

@dreimer1986 How did you success a Revert to 9.0.36 ? I am trying to use the unbrick procedure, but nothing append, i am still in 11.xx version

Of course you are. You need a v9 backup of the same camera type and flash the partitions off it back on yours. That's what I did

@dreimer1986 I have the backup v9 on my own camera.
I have build the files via the unblock Readme.
I have :
backup_y211ga.gz
home_y211ga.gz
rootfs_y211ga.gz

Then I have :
gunzip backup_y211ga.gz
gunzip home_y211ga.gz
gunzip rootfs_y211ga.gz

Format SDCARD to FAT32
Paste backup_y211ga, and the start camera.
Led blinks one time in yellow and then it start normally after 15sec. (Longer than normal boot)
Once done, I make the same with home & rootfs. But I am still in v11. I tried with the backup file on this thread, but same behavior. I might miss something :-/

I used the WIndows tool found there a bit hidden (https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/305#issuecomment-983783470) for making the files and I even skipped rootfs. Only backup and home on my cams was reverted. All fine here. And ALWAYS do ONE AT A TIME. Not all of them thrown on SD and boom!. DO one, remove it, do next.

So to confirm, you have NOTHING on the flash drive except the 1 file?  Example: backup_y211ga?  How does the camera know to pick up the file and process it?

I have finally be able to revert.

I have format SDCARD via FAT32 with Pi Imager. (If I format with the Yi Home App, it fails)
I need to use the file files from the backup_v9, use backup and then home file. (revert works)
I made the same with my own backup file, I have a newer 9.0.36 than the one on backup_v9
I reapplied the hack.
All is OK now.
It was a long journey

@Minims
Hmm...  I must be doing something wrong :(
I downloaded the v9 zip file you posted in https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/388#issuecomment-1062645815.
I downloaded the mkimg file from https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/305#issuecomment-987908753
I then ran the command in windows:
mkimg.EXE -A arm -O linux -T filesystem -C none -a 0x0 -e 0x0 -n "xiaoyi-backup" -d mtdblock4.bin backup_y211ga

I used Pi Imager as you did just incase to Format the SD Card FAT32.
I then copied the backup_y211ga to the root of the SD card.  This is the ONLY file on the SD camera.
I inserted it into the camera, plugged it in and waited 10 minutes!  (Yes, I set a timer)...
Then unplugged it.
I then copied the home_y211ga file and deleted the the backup_y211ga file to the SD card.  Again, only left with ONE file on SD Card called home_y211ga
I inserted it into the camera, then booted it.  Waited 10 minutes!  (Yes, I set a timer again!)...
Then unplugged it.
Removed the SD Card, plugged the camera in.
YI Home still says I'm on version 11.  I don't think it did ANYTHING!  Am I missing something?

@meluvalli does the yellow led has blink one time just after the boot ?

I have remove the camera from Yi Home App
I have clean the application cache too (try this every time you update a file backup, home or rootfs)
Then I have rest the camera via reset button and had it again.

Got it.   I think reset was the key :)
Thank you!


Add option to manually kill Android singleton instance

As you can imagine, having to manage a singleton in a declarative framework built around templating and letting instances take care of themselves is... less than fun. When the Android YouTube player is a child of a component that is popped off the stack, and a new instance of that same component is then pushed on the stack, the following happens, regularly:
05-07 22:41:08.672  4295  4295 E AndroidRuntime: java.lang.IllegalArgumentException: No view found for id 0x2f3 (unknown) for fragment VideoFragment{372cf91 #0 id=0x2f3}
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:987)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1171)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.BackStackRecord.run(BackStackRecord.java:816)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1578)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.FragmentManagerImpl$1.run(FragmentManager.java:483)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:751)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:95)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6119)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
05-07 22:41:08.672  4295  4295 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

I understand if the Android version of the YouTube class must remain a singleton, but is there any way that we could get a class method to destroy the singleton on the unmount of a parent, similar to removing a listener? As it stands, the singleton nature makes the Android player either unpredictable or a micro-management nightmare.
Edit: My suggestion here is built on my assumption that what's happening is that the next render of <YouTube ... > is looking for the old singleton in memory, for some reason, despite the fact that its parent cleanly unmounted. If I'm wrong about this, please let me know.
Edit edit: still may be a singleton issue but also possibly a duplicate of #249

Hey, I've recently faced a similar issue with Android Youtube player remembering the dimensions of the recently played video so the next video is played in the same aspect ratio despite the fact that the control was unmounted and mounted back on the other screen. Can't get the previous instance killed.
Did you figured our the way to do this?

@foggy1 @webdevbyjoss Anyone find a workaround for this?


Bring PyPy2 and 3 under one project.

I will either send a new PR to set up AppVeyor or just send a new commit to this PR.

@kirbyfan64 So are you a fan of just continuing to push to https://chocolatey.org/packages/python.pypy or should we start a new one for pypy / pypy2? Also, did you want me to add you to https://chocolatey.org/packages/pypy3?

I added an AppVeyor config and amazingly it worked on my first try: https://ci.appveyor.com/project/dhermes/chocolatey-pypy3/build/1.0.17.test-appveyor
So I've added that file here in this PR.

Also, that build has a 6.0.0 build artifact for python.pypy so I started the submission process there: https://chocolatey.org/packages/python.pypy/6.0

So are you a fan of just continuing to push to https://chocolatey.org/packages/python.pypy or should we start a new one for pypy / pypy2?

Hmm...should probably be pypy2 and pypy3, since that's what main PyPy still uses.

Outside of that, LGTM :+1:

Hmm...should probably be pypy2 and pypy3, since that's what main PyPy still uses.

Does it? AFAICT main PyPy uses pypy and pypy3. We could also ask them?

Merging now, punting discussion to #9.


Fix wrong package name in readme

it's lychee
https://archlinux.org/packages/community/x86_64/lychee/

it's lychee
archlinux.org/packages/community/x86_64/lychee

That didn't work for me but I am on Manjaro. I went after the docs in https://lychee.cli.rs/#/installation/packages?id=arch-linux.
I do see now that the rename must have happened recently and it just hasn't made it to Manjaro yet: https://packages.manjaro.org/?query=lychee
Sorry for the inconvenience :)

it has now.


Calling shuffle on IterableDataset will disable batching in case any functions were mapped

When using dataset in streaming mode, if one applies shuffle method on the dataset and map method for which batched=True than the batching operation will not happen, instead batched will be set to False
I did RCA on the dataset codebase, the problem is emerging from this line of code here as it is
self.ex_iterable.shuffle_data_sources(seed), function=self.function, batch_size=self.batch_size, as one can see it is missing batched argument, which means that the iterator fallsback to default constructor value, which in this case is False.
To remedy the problem we can change this line to
self.ex_iterable.shuffle_data_sources(seed), function=self.function, batched=self.batched, batch_size=self.batch_size

Hi :) Good catch ! Feel free to open a PR if you want to contribute, this would be very welcome ;)

Have raised the PR here

Fixed by #2717.


gitkraken: 4.2.1 -> 4.2.2 & fix missing gsettings schemas

Motivation for this change
Update gitkraken 4.2.1 to 4.2.2
Fix gitkraken missing GSettings schemas
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@worldofpeace Thank you for the feedback. I've updated the PR.

@Mic92 @worldofpeace Can someone check this again ?


Create links

It would be nice to have a command that can create a link to a zet for public consumption.
It should create a public (not relative) url such as:

Mudmap Sub-Accounts
(https://github.com/danielmichaels/zet/tree/main/20220505024039)

zet link <searchTerm>
Then drop into select list, like view.
zet link last
Return the most recent entry as a url.


Plonky3 has the ability to break our build

We depend on the main branch of an external repository. If plonky3 changes the API on main (which is changing constantly), our build breaks.
This is serious because it renders our older versions unbuildable. We can't do a git bisect across the point where Powdr uses a different Plonky3 interface from the version that is in our local Cargo.lock.

Wasn't this fixed in the PR?

Yes.


title type when create page

it fail when creating page, as follow:

it success where create page. as follow:

The issue you are describing has been resolved in newer versions of the API.


Update service-tier-hyperscale.md

A few changes with grammar, punctuation and wording.

Replaced by internal PR https://github.com/MicrosoftDocs/sql-docs-pr/pull/28663.
@KoprowskiT We use the Oxford comma, so I removed a few of your edits. As my colleague also noted, Azure SQL Database is the name of the service, so other edits were redacted.
It will take about a day for the internal PR to be approved and published, at which point you will see the updated content.
Thank you again for your contributions. We appreciate your close attention to our content.


Microsoft Edge - tab styling has scrollbars

hmm, i don't see this on the open repo, at least on this mac build of Edge:
Version <IP_ADDRESS> (Official build) Dev (64-bit)
could it be a conflict in your client's CSS layer?


Add sample class

Resolves #81

I believe we can skip this intermediate class, let's simply add "geometry" subsection whereever is needed, like we have in substrate, without the need of this semi-general step
What do you think?

@aalbino2 @hampusnasstrom I see. Based on our discussions in today's team meet:

getting a consensus on the term Sample will mean more discussions beyond this PR, which have already occurred in recent years.
CompositeSystem is meant to handle samples. A possibility could be to add geometry in the CompositeSystem. However, since geometry is optional for the composite system, it should be added while extending CompositeSystem.
In coming months, System will replace CompositeSystem, making these classes even more general. Adding geometry there is not recommended.
Suggestion: move this class to the IKZ plugin. And the name of the class will be <Synthesis process name>IKZSample.


⚠ Bofrost.com has degraded performance

In 52f27ec, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 539 ms

Resolved: Bofrost.com performance has improved in d67733e after 8 minutes.


Idea: Docker support

What about an official Docker for this awesome project?
Thank you in advance :)

Great idea @julianxhokaxhiu! Would you be up for writing a Docker compose file?

Absolutely @julianxhokaxhiu. I'll get started on that today. Can you ping me at<EMAIL_ADDRESS>so we can collaborate via email?

Sure!

I'll provide a PR tomorrow :)


Request to update privatelink for purviewstudio

While creating a Purview account Private endpoint now requires a new type "privatelink.purviewstudio.azure.com" which is not properly listed in your documentation: https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns
"resources": [
{
"type": "Microsoft.Network/privateDnsZones",
"apiVersion": "2018-09-01",
"name": "privatelink.purviewstudio.azure.com",
"location": "global",
"tags": {},
"properties": {}
},
Can you please update the document?
Thank  you.

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

@CarlosMendozaB, Thanks for reaching out. We will investigate and update this thread.

Few days back privatelink.purviewstudio.azure.com was introduced to in this other document:
https://docs.microsoft.com/en-us/azure/purview/catalog-private-link
"Ensure that a new Azure Private DNS Zone (privatelink.purviewstudio.azure.com) is created during the deployment of the portal private endpoint, and that a corresponding A record (web) exists in the the Private DNS Zone."
I believe this confirms the need of listing it within https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns

@CarlosMendozaB, Appreciate your patience. The doc has been edited accordingly and it would take some time for the changes to get reflect over the doc.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Migration docs issue

Bug report

What is the current behavior?
If a user follows the migration guide directly, they will install an old version of webpack.   yarn add webpack@next --dev installs version "webpack": "^5.0.0-rc.6", where the user most likely intended to install the latest version "webpack": "^5.11.1",
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Remove @next or have @next point to a version that works

Other relevant information:
webpack version:
Node.js version:
Operating System:
Additional tools:

@dbuck Thanks for heads-up, I've filed a pull request to fix it.

Fixed


Added a silo for #280, Added a Grim Reaper hood for #734, Added Werewolf Mask for #725, Added Scare Crow Mask for #723

The image is of dimension 96 x 96 for world-x2.

Thank you @123survesh! Nice sprites. I'll close the corresponding issues later today.

Sorry I couldn't send separate pull requests for each image :sweat_smile:


[Bug]: Help with weird scenes

Describe the bug
Background
Today i updated from pyloxone 0.6.4 to 0.6.10, after the update all my scenes in HA aren't working anymore as expected. Because all my non loxone lights are still working, i decided to update also my loxone miniserver. To eventually resolve the issue. So i updated loxone from version <IP_ADDRESS> to the newest <IP_ADDRESS>.
Nothing happens, still the same problem.
Before the update, every light was flawlessly functioning and the state was saved in the scenes.
Problem
So whats actually my issue:
My lights that are making problems:

Loxone Ceiling RGBW Lights (in loxone config: V2 light controller with smart actor)
Loxone Ceiling Spot RGBW (also smart actor on a V2 light controller)

When i look at my scenes, all the configured loxone lights have no color saved state. So when i call the scene, the light is not turning on.
when i now set a certain color state on the light und press "save". Everythings fine. But now can go back in and the light is off in the scene.
https://github.com/user-attachments/assets/9048700c-9827-4b7e-9b48-61bec0671953
I only want to acheive that the lights turn on, in a specific color state, when i call the scene. Nothing special.
Firmware of your Miniserver
<IP_ADDRESS>
HomeAssistant install method
manual
Version of HomeAssistant
OS: 12.4
Core: 2024.7.2
Version of Pyloxone
0.6.10
Update pyloxone
yes
Log
No response

I figured out, that i only can save the state in the scene, when i set an effect in the lightcontrol entity. Then the scene calls the effect in loxone and everything works.
But the pain is now, that i can't change the scene or light from homeassistant directly, like before.
Every effect MUST be set from the loxone app.
Do someone knows a workaround?

@daes10 this is now the way it should be. We had a lot of problems with the old implementation. You you should define your scenes in loxone for the loxone lights and not use the scenes with homeassisant. For other lights you you could use the homeassistant way.

@daes10 I understand now your problem better. Maybe you have added the light controller to the scene. The light controller now is not able to set the dimmer values or the color anymore. For that you can let pyloxone create the subcontrols for the light controller. Then you can add these subcontrolls, for example a dimmer, to the scene. There you can set the dimmer value for the scene and it will be saved to the scene as before. The light controller it self is like a scene. To you can use the light controller of a scene in home assisstant. But not a light controller in scene. This does not make sense.

Thank you @JoDehli for your fast reply.
Yes thats right. But things go really weird, when i only put the subcontrols in the scene.
I have 3 scenes in each room: one for low light, one for middle light and one for full light. Now i put only the subcontrols in the scene (like i configured it the last year and worked good in pyloxone version <=0.6.4)
The weird thing is now, when i save a dimmer state (for example a RGBW Loxone light), sometimes the dimmer don't save. And when i save the same dimmer in another scene, the new dimmer state will override the old one.
See my demonstration video:

First i show that all my scenes from this room are completely off.
Then i set the "wenig Licht" scene to a certain state...
Afterwards i set the scene "viel Licht" to another state...
Then i checked the scene "Aus", if everythings fine.
When i now go back to my "wenig Licht" scene, you can see, that the "Einbauspots" were off (not as before, in the saved state). So the scene was override in the background, when i saved another state to this lights.

https://github.com/user-attachments/assets/40376a58-4b91-449c-8c5a-52344c3bce95

@daes10 I tested it with some lights and it worked well for me. I can not reproduce your problem.
But I think the best way is to define the Scenes in a light controller. Create a light controller for each room and define the states in the light controller. The only set the light controller effect with a scene or a service call. This should work perfect.

Ok thanks for your try.
So then i will do it, this way and create all scenes in the loxone app.
PS: Thank you for your awesome work with this Integration! I appreciate your work every day!


Added scenario for trust policy and trust store

Signed-off-by: Toddy Mladenov<EMAIL_ADDRESS>This is related to the #438

Do you think we should place all generic specs in the notaryproject repo? There is another scenario spec in that repo: https://github.com/notaryproject/notaryproject/blob/main/scenarios.md.


Update identity docs to also include "external identity" text.

To make it easier for users to look up information and commands regarding the Cumulocity IoT "external identity", the documentation and commands should also use the official "external identity" terminology.

Resolved by #227


[HIPIFY] Segfault while hipifying any CUDA source, when hipify-clang is linked with LLVM+Clang libs starting from 7.0.0

This snippet of axpy.cu code is from Compiling CUDA with clang This code is verified that it can be successfully compiled by clang using:
clang++ axpy.cu -o axpy --cuda-gpu-arch=<GPU arch> -L<CUDA install path>/<lib64 or lib> -lcudart_static -ldl -lrt -pthread
I have tried to do:
hipify-clang square.cu --   -x cuda   --cuda-path=/opt/cuda   --cuda-gpu-arch=sm_30   -isystem /opt/cuda/samples/common/inc   -I /opt/cuda/cuDNN and get a segfault from there
Then I tried to do the conversion by using the clang command I used in clang standalone compilation but stil got an error of:

Error while processing /home/kneternal/Work/test/clang_test/axpy.cu.hipify-tmp.

My version of LLVM+Clang is 7.0.0 and they are built and installed from source. Could I get some help about this?

Please provide Linux, its version and CUDA version installed.

Verified on Ubuntu 16.04 with LLVM 7.0.0 release built from sources and CUDA 8.0:
emankov@spb-hlc-fiji1h:~/git/HIP/hipify-clang/build$ ./hipify-clang ../../tests/hipify-clang/square.cu -- -x cuda --cuda-path=/usr/local/cuda-8.0 --cuda-gpu-arch=sm_30 -isystem /usr/local/cuda-8.0/samples/common/inc
#0 0x000000000140375a llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x140375a)
#1 0x0000000001401c4c llvm::sys::RunSignalHandlers() (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x1401c4c)
#2 0x0000000001401db7 SignalHandler(int) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x1401db7)
#3 0x00007f5cad788390 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x0000000000656118 clang::ast_matchers::MatchFinder::MatchFinder(clang::ast_matchers::MatchFinder::MatchFinderOptions) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x656118)
#5 0x000000000064c355 HipifyAction::CreateASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x64c355)
#6 0x000000000067b4e6 clang::FrontendAction::CreateWrappedASTConsumer(clang::CompilerInstance&, llvm::StringRef) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x67b4e6)
#7 0x00000000006822b3 clang::FrontendAction::BeginSourceFile(clang::CompilerInstance&, clang::FrontendInputFile const&) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x6822b3)
#8 0x00000000006a85b6 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x6a85b6)
#9 0x00000000007687e4 clang::tooling::FrontendActionFactory::runInvocation(std::shared_ptr<clang::CompilerInvocation>, clang::FileManager*, std::shared_ptr<clang::PCHContainerOperations>, clang::DiagnosticConsumer*) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x7687e4)
#10 0x000000000076326f clang::tooling::ToolInvocation::runInvocation(char const*, clang::driver::Compilation*, std::shared_ptr<clang::CompilerInvocation>, std::shared_ptr<clang::PCHContainerOperations>) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x76326f)
#11 0x000000000076558b clang::tooling::ToolInvocation::run() (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x76558b)
#12 0x000000000076737e clang::tooling::ClangTool::run(clang::tooling::ToolAction*) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x76737e)
#13 0x0000000000761b4c clang::tooling::RefactoringTool::runAndSave(clang::tooling::FrontendActionFactory*) (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x761b4c)
#14 0x00000000006450d8 main (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x6450d8)
#15 0x00007f5cac2dd830 __libc_start_main /build/glibc-Cl5G7W/glibc-2.23/csu/../csu/libc-start.c:325:0
#16 0x0000000000644329 _start (/home/emankov/git/HIP/hipify-clang/build/hipify-clang+0x644329)
Segmentation fault (core dumped)

Verified on Ubuntu 16.04 with LLVM 6.0.1 release built from sources and CUDA 8.0:
No segfault. Hipification is correct.
Conclusion: Bug appeared with LLVM+Clang 7.0.0.

This is a six months old clang bug: https://bugs.llvm.org/show_bug.cgi?id=36384.
It is not related to hipify-clang internals. Please use the previous (6.0.x) releases of LLVM+Clang for hipification, they work fine.

This is a six months old clang bug: https://bugs.llvm.org/show_bug.cgi?id=36384 "MatchFinder constructor causes segfault".
It is not related to hipify-clang internals. Please use the previous (6.0.x) releases of LLVM+Clang for hipification, they work fine.

Thank you so much for help. It is working now using LLVM6.0.1

Maybe it is good to give a note in the installation guide to tell people not to use 7.0.0 for now

Readme is updated: https://github.com/ROCm-Developer-Tools/HIP/pull/729

Is still reproduced on LLVM trunk (8.0). Going to fix or workaround as the bug is a serious showstopper for hipify-clang.

The segfault is not observable on the trunk [3d28a4490ff9cefedd3597c6ac3e14e523e6e13].
The segfault is not observable on clang 8.0.0 release.
Clang bug 36384 is closed.
Readme is updated: #1011: latest stable release for Linux is clang 8.0.0, which supports CUDA up to 10.0.


A sample command that doesn't work (giving experiment permission)

A sample command in "Give experiment permission to your AKS cluster" doesn't work.

az role assignment create --role "Azure Kubernetes Cluster User Role" --assignee-object-id $EXPERIMENT_PRINCIPAL_ID --scope $RESOURCE_ID

First, "Azure Kubernetes Cluster User Role" does not exist. Instead of it, there is "Azure Kubernetes Service Cluster User Role".
And, "Azure Kubernetes Service Cluster User Role" doesn't seem to have enough permissions to run the experiment. I got the following error.
The client 'my-id' with object id 'my-id' does not have authorization to perform action 'Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action' over scope '/subscriptions/my-sub/resourceGroups/my-rg/providers/Microsoft.ContainerService/managedClusters/my-cluster' or the scope is invalid. If access was recently granted, please refresh your credentials.

"Azure Kubernetes Service Cluster User Role" can not do 'Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action'. But that's possible with "Azure Kubernetes Service Cluster Admin Role".
Could you consider correcting this doc? Thanks.

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

ID: e96734ea-cf4c-626a-8429-78df16c4b12a
Version Independent ID: 18227f13-77c6-fee9-4227-ba203720113d
Content: Create an experiment that uses an AKS Chaos Mesh fault using Azure Chaos Studio with the Azure CLI
Content Source: articles/chaos-studio/chaos-studio-tutorial-aks-cli.md
Service: chaos-studio
GitHub Login: @johnkemnetz
Microsoft Alias: johnkem

@ToruMakabe Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

I faced the same issue. I think that this is crical document bugs. I hope that this fix will be applied soon.

This documentation issue has been fixed.
#please-close


✨ Track number of crossings

Description
Add a tracker for the number of crossings in a layout that is automatically updated when a crossing is added or removed.
Checklist:

[ ] The pull request only contains commits that are related to it.
[ ] I have added appropriate tests and documentation.
[ ] I have added a changelog entry.
[ ] I have created/adjusted the Python bindings for any new or updated functionality.
[ ] I have made sure that all CI jobs on GitHub pass.
[ ] The pull request introduces no new warnings and follows the project's style guidelines.

Only now thought of the possibility to also log the crossing numbers in the stats of our various physical design algorithms. Maybe that would be nice. What do you think?

Good idea 👍

Only now thought of the possibility to also log the crossing numbers in the stats of our various physical design algorithms. Maybe that would be nice. What do you think?

Good idea 👍

Many thanks! The adjusted _stats classes also need to be reflected in the Python bindings, though.

Only now thought of the possibility to also log the crossing numbers in the stats of our various physical design algorithms. Maybe that would be nice. What do you think?

Good idea 👍

Many thanks! The adjusted _stats classes also need to be reflected in the Python bindings, though.

They are reflected in the python bindings that make use of members of the _stats object. Is this what you meant?

I see that we have some inconsistencies going on in how the _stats classes are exposed to Python. Sometimes, we use
    py::class_<fiction::exact_physical_design_stats>(m, "exact_stats", DOC(fiction_exact_physical_design_stats))
        .def(py::init<>())
        .def("__repr__",
             [](const fiction::exact_physical_design_stats& stats)
             {
                 std::stringstream stream{};
                 stats.report(stream);
                 return stream.str();
             })

        ;

(no access to the attributes, just printing via __repr__ function)
sometimes, we do
py::class_<fiction::technology_mapping_stats>(m, "technology_mapping_stats", DOC(fiction_technology_mapping_stats))
        .def(py::init<>())

        .def("report", &fiction::technology_mapping_stats::report, DOC(fiction_technology_mapping_stats_report))

        ;

(no access to the attributes, just printing via a report function)
and sometimes we do
py::class_<fiction::graph_oriented_layout_design_stats>(m, "graph_oriented_layout_design_stats",
                                                            DOC(fiction_graph_oriented_layout_design_stats))
        .def(py::init<>())
        .def("__repr__",
             [](const fiction::graph_oriented_layout_design_stats& stats)
             {
                 std::stringstream stream{};
                 stats.report(stream);
                 return stream.str();
             })
        .def_readonly("time_total", &fiction::graph_oriented_layout_design_stats::time_total,
                      DOC(fiction_graph_oriented_layout_design_stats_duration))
        .def_readonly("x_size", &fiction::graph_oriented_layout_design_stats::x_size,
                      DOC(fiction_graph_oriented_layout_design_stats_x_size))
        .def_readonly("y_size", &fiction::graph_oriented_layout_design_stats::y_size,
                      DOC(fiction_graph_oriented_layout_design_stats_y_size))
        .def_readonly("num_gates", &fiction::graph_oriented_layout_design_stats::num_gates,
                      DOC(fiction_graph_oriented_layout_design_stats_num_gates))
        .def_readonly("num_wires", &fiction::graph_oriented_layout_design_stats::num_wires,
                      DOC(fiction_graph_oriented_layout_design_stats_num_wires))

        ;

(read-only access to the attributes and printing via __repr__)
In my opinion, the last one is the best. However, we could also add the report function there, too, for completeness. And then adjust all other _stats in pyfiction to follow this best practice.


Execute L1Handler transactions using the RpcState

Based on #1094
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #1103 (05ef718) into rpc-state-reader-deploy (d1245e2) will decrease coverage by 0.01%.
The diff coverage is 4.34%.

:exclamation: Current head 05ef718 differs from pull request most recent head 6c9f643. Consider uploading reports for the commit 6c9f643 to get more accurate results

@@                     Coverage Diff                     @@
##           rpc-state-reader-deploy    #1103      +/-   ##
===========================================================
- Coverage                    89.19%   89.18%   -0.01%
===========================================================
  Files                           50       50
  Lines                        13419    13441      +22
===========================================================
+ Hits                         11969    11988      +19
- Misses                        1450     1453       +3

Files
Coverage Δ

src/transaction/l1_handler.rs
89.90% <4.34%> (-10.10%)
:arrow_down:

... and 1 file with indirect coverage changes