tc-health-client: Display errors on stderr

When I tried the tm-health-client for the first time, it would just exiting out. No errors.
# tm-health-client
#

Traffic Control Cache Config (T3C, formerly ORT)

Current behavior:
No errors when configuration are missing. Looks like there is an exit code (166).
If you know the location of the default log file, it display information in there.
I don't think there is a way to configure it to log on stdout either (systemd).
New behavior:
Display errors on stderr by default (probably logs at the same time)
Be able to configure logging with stderr and stdout

Reading the man page, there is a systemd file provided. That's awesome. Here's the output.
[root@cdn1cdedge0002 ~]# systemctl start tm-health-client
[root@cdn1cdedge0002 ~]# systemctl status tm-health-client
● tm-health-client.service - Traffic monitor health service for Trafficserver
   Loaded: loaded (/usr/lib/systemd/system/tm-health-client.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit) since Thu 2021-09-02 14:39:45 UTC; 4s ago
  Process: 5993 ExecStart=/usr/bin/tm-health-client -vv (code=exited, status=166)
 Main PID: 5993 (code=exited, status=166)

Sep 02 14:39:44 cdn1cdedge0002.coxlab.net systemd[1]: Unit tm-health-client.service entered failed state.
Sep 02 14:39:44 cdn1cdedge0002.coxlab.net systemd[1]: tm-health-client.service failed.
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: tm-health-client.service holdoff time over, scheduling restart.
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: Stopped Traffic monitor health service for Trafficserver.
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: start request repeated too quickly for tm-health-client.service
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: Failed to start Traffic monitor health service for Trafficserver.
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: Unit tm-health-client.service entered failed state.
Sep 02 14:39:45 cdn1cdedge0002.coxlab.net systemd[1]: tm-health-client.service failed.

This still happens for me


Youtube videos submitted using bookmarklet are not showing up on pop-ups and there is not scroll-down function.

  One is Prof. Watanabe's submission, which does not have any problems.  The other one is my youtube submission using bookmarklet.  The youtube via bookmarklet pop-ups are not showing in the fancy box and the scoroll down function is not there, either.

I believe that the problem is possibly because the videos submitted through the Bookmarklet are getting categorized as "Layer Type: outside-Youtube".
However, currently no youtube videos are showing up in the fancybox for me... so I'm having a hard time testing this. Are you able to see Youtube videos in the fancybox currently, Koko?

I still cannot see a video in the fancy.
The below is the example.
The attached image item is not out-sideYoutube.
http://jdarchive.org/admin/zeega/data/item/1935005/edit
The item page does not show the video, either.
http://jdarchive.org/ja/item/1935005

Weirdly, I can see the Watanave youtube videos in fancybox, but they have no thumbnail. But other youtube videos that do have a thumbnail do not show up in fancybox.
See this link: http://jdarchive.org/en/search#media_type=Video&sort=media-date-desc&

FYI
Youtubes on Sakura on Project and Sendai Mediatheque have thumnails but the videos show up in facybox.
http://jdarchive.org/ja/user/427#media_type=Video&sort=relevant&
http://jdarchive.org/en/user/4
Those videos are imported by collaborators.
They are not submitted by bookmarklet.

@rchen152 - Hey Rebecca I know you had some success with our videos the last time, is there any chance you could take a look at this?

Hmm, so it looks like there are two separate things going on:

When the layer type or uri is wrong, the fancybox and item page videos don't show up.
When the the thumbnail uri is missing, the thumbnail doesn't show up.  (Conversely, if there is thumbnail uri, the thumbnail shows up regardless of whether the actual video is working.)
I'll see what I can do.

YouTube items are complicated!
Items with the category "Website" and layer type "Website" are sent to Internet Archive for archiving and were submitted through the contribute page, so Youtube urls which have the category "Website" are not part of #887, the problem I first mentioned.  Those seeds do not have thumnail urls and they should have waybackportion in their Uri*.   The bookmarklet submissions and API related Youtube items are in the category "video" and layertype YouTube.
Anyway, YouTube items with wayback portion uri* look great on pop-ups in the fancy box and item pages.  Thank you!
However, there is one flaw in the pop-ups in the view source link in the wayback uri* youtube items.  I will submit another issue later.

FYI
Initially, the bookmarklet-submitted YouTubes items had the Youtube url in their uri.  Jessica fixed the bookmarklet Youtube uri  on Oct, 2014 to be consistant with YouTube uri with Sakura on Project, Recorder 311. Now, the uris are showing only Youtube Ids, such as cMc1uBYImhg.
Bookmarklet Youtube submission between ID 1536049 and1935021 have Youtube url uris.
However, any of the bookmarklet submissions do not play videos in their fancybox nor item pages regardless of Uri having Youtube urls or Youtube id.
Hmm, I hope I explained this clearly to you about this problem.

I think this update fixes the issue: https://github.com/Japan-Digital-Archives/Japan-Digital-Archive/pull/906
In Chrome and IE on my laptop, the following now all display properly:
http://jdarchive.org/en/item/1942410 (video on item page)
http://jdarchive.org/ja/item/1935005 (video on item page)
http://jdarchive.org/en/search#media_type=Video&sort=media-date-desc& (thumbnails and fancybox videos)

Thank you so much @rchen152! Awesome work! =)
@jdaKoko could you confirm if the issue is resolved and close the issue if so? Thank you! =)

Great! Thank you very much.


TypeError: no implicit conversion of String into Integer

Trying to build\run this app directly, rather than just installed gem.

Fork repository.
cd pluto/pluto-merge' (or pluto/pluto`)
gem install hoe
rake init --trace

rake aborted!
TypeError: no implicit conversion of String into Integer
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:528:in `[]'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:528:in `block in define_spec'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/2.7.0/rubygems/specification.rb:2008:in `initialize'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:512:in `new'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:512:in `define_spec'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:815:in `post_initialize'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/hoe-3.22.1/lib/hoe.rb:394:in `spec'
/Users/infominer/jamstack/plutoplanet/pluto/pluto-merge/Rakefile:4:in `<top (required)>'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/rake_module.rb:29:in `load'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/rake_module.rb:29:in `load_rakefile'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:703:in `raw_load_rakefile'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:104:in `block in load_rakefile'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:103:in `load_rakefile'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:82:in `block in run'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
/Users/infominer/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/Users/infominer/.rbenv/versions/2.7.0/bin/rake:23:in `load'
/Users/infominer/.rbenv/versions/2.7.0/bin/rake:23:in `<main>'

I spent a lot of time digging around the code and trying different things, but didn't get very far.
Ultimately, I'm trying to require an additional dependency (nokogiri) to use in my template.. hopefully I'm at least pointed in the right general direction :)

That looks like a hoe rake task erros.   See  https://yukimotopress.github.io/gem-tasks for hoe.    What is:
$ rake init

trying to do?  Do you have a Rakefile?  If you want to use nokogiri in your template, add at the top:
<% require 'nokogiri' %>

Not sure why you need hoe - Hoe itself is for BUILDING / PUBLISHING new gems and not really for USING gems.

oh haha :sweat_smile: I really didn't think it could be that simple!
There are rakefiles in folders of the various components of pluto.. and I used rake init on the plutolive.starter ...
I'm getting familiar with the different aspects, and reading a bunch online while I poke around... but not quite grasping how all the parts fit together, quite yet.
I assumed if I wanted to add a dependency to the merge function I'd have to build it custom.

ERB (Embedded RuBy) in the templates is just regular plain vanilla ruby.  You can also include your own script with require or require_relative e.g. use:
<% require './myscript' %>
And in myscript.rb you can require nokogiri and add your own scripts for use in the templates.


Dataverse triger - When a row is added, modified or deleted (preview)

Describe the Bug with repro steps
Logic app Standard
In Workflow -> designer

Click add triger
Search for "dataverse"
Select "When a row is added, modified or deleted (preview)"
Select Authentication = Service principal
Fill configuration
Click create new

Then I recieve error which is for OAuth Authentication:
Failed to create connection: {"error":{"code":"AuthorizationFailed","message":"The client<EMAIL_ADDRESS>with object id '319d6aba-7c60-4c8a-8244-51aa4cf9c532' does not have authorization to perform action 'Microsoft.Web/connections/write' over scope '/subscriptions/0d59652e-c693-46af-b90f-058f89c91719/resourceGroups/rg-pv-sap-dev-we-02/providers/Microsoft.Web/connections/commondataservice' or the scope is invalid. If access was recently granted, please refresh your credentials."}}
What type of Logic App Is this happening in?
Standard (Portal)
Are you using Preview Designer or GA Designer
Preview
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Edge
Additional context
No response
AB#24375016

We should check here if we are registering for the resource providers. If we are then this is just user permissions issue

You was right ...sorry!


Swagger/OpenAPI 3.0 support?

Now that OpenAPI 3.0 (stable) specification has been released, do we have any plans for working on the 3.0 support?
Thanks!

We don't have plans for it in the immediate future.

@webron Any idea what needs to be done to upgrade to the 3.0 spec? Could you use some help?
Or will OpenAPI 3.0 never be supported by this project? I'd just like to know if that decision has been made.

swagger-play's usage is one of the lowest we have in the various projects we maintain. As such, doing the work to support Play, especially given that Play's version are backward incompatible and cause issues with every release - is very time consuming and we don't really have the capacity to actively work on it.
That said, I'm considering the options to make this happen. If anyone in the community has input on this, I'd be happy to hear.

We happen to be using this library at Iterable and are maintaining a fork, including some of the other unmerged changes from this repo: https://github.com/Iterable/swagger-play. If anyone wants to help with OpenAPI 3 support, I'm happy to help with the Play aspects, though I'm not that experienced with the Swagger APIs.
I think one reason this library is underutilized is that there are a few competing Swagger implementations for Play, including https://github.com/iheartradio/play-swagger, which seems more actively maintained and now supports OpenAPI v3, but uses comments in the routes file as opposed to annotations.

Any new updates?

Any updates please?


Error: Building package libpq:x86-windows-static failed with: BUILD_FAILED

Package: libpq:x86-windows-static
Vcpkg version: 2020.06.15-nohash
build-libpq-x86-windows-static-RELEASE-out.log
.\Release\libpq\encnames.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64' [D:\vcpkg\buildtrees\libpq\x86-windows-static-rel\libpq.vcxproj]

Could you pull latest vcpkg, delete all packages and try again?

It's still the same
.\vcpkg\vcpkg.exe --triplet x86-windows-static  install qt5-base

Closing in favor of https://github.com/microsoft/vcpkg/issues/13726


torch JIT fails to load with various PKL file not found errors

The tensor loading code tries safetensors, then torch.jit, then regular torch.load. The code path for safetensors does not fall back to torch.load if torch.jit.load fails, and it often does:
Message: 'failed to load as safetensors file, falling back to torch'
Arguments: (Exception('Error while deserializing header: HeaderTooLarge'),)
[2023-02-17 13:32:06,313] ERROR: onnx_web.convert.diffusion_original: exception setting up output: ['Traceback (most recent call last):\n', '  File "/home/ssube/onnx-web/api/onnx_web/convert/utils.py", line 212, in load_tensor\n    checkpoint = safetensors.torch.load_file(name, device="cpu")\n', '  File "/home/ssube/onnx-web/api/onnx_env/lib/python3.10/site-packages/safetensors/torch.py", line 98, in load_file\n    with safe_open(filename, framework="pt", device=device) as f:\n', 'Exception: Error while deserializing header: HeaderTooLarge\n', '\nDuring handling of the above exception, another exception occurred:\n\n', 'Traceback (most recent call last):\n', '  File "/home/ssube/onnx-web/api/onnx_web/convert/diffusion_original.py", line 1198, in extract_checkpoint\n    checkpoint = load_tensor(checkpoint_file, map_location=map_location)\n', '  File "/home/ssube/onnx-web/api/onnx_web/convert/utils.py", line 217, in load_tensor\n    checkpoint = torch.jit.load(name)\n', '  File "/home/ssube/onnx-web/api/onnx_env/lib/python3.10/site-packages/torch/jit/_serialization.py", line 162, in load\n    cpp_module = torch._C.import_ir_module(cu, str(f), map_location, _extra_files)\n', 'RuntimeError: PytorchStreamReader failed locating file constants.pkl: file not found\n']
[2023-02-17 13:32:06,313] ERROR: onnx_web.convert.diffusion_original: pipeline or config is not set, unable to continue.
[2023-02-17 13:32:06,313] INFO: onnx_web.convert.diffusion_original: converted original Diffusers checkpoint to Torch model
[2023-02-17 13:32:06,314] INFO: onnx_web.convert.diffusion_stable: converting Stable Diffusion model diffusion-snow-globe-v1: ../models/.cache/diffusion-snow-globe-v1-torch/working -> ../models/diffusion-snow-globe-v1/

This looks like it might be related to https://github.com/pytorch/pytorch/issues/47917. The filename in the model, constants.pkl, varies by source and model but appears to always be another pickle file.

Loading that particular model using torch.load does work, but it is missing some necessary keys in the UNet area:
[2023-02-17 13:44:47,705] INFO: onnx_web.convert.diffusion_original: Pred and size are epsilon and 512, using config: /home/ssube/onnx-web/models/configs/v1-training-default.yaml
[2023-02-17 13:44:47,705] INFO: onnx_web.convert.diffusion_original: v1 model loaded.
[2023-02-17 13:44:47,729] INFO: onnx_web.convert.diffusion_original: converting UNet
[2023-02-17 13:44:51,999] ERROR: onnx_web.convert.diffusion_original: exception setting up output: ['Traceback (most recent call last):\n', '  File "/home/ssube/onnx-web/api/onnx_web/convert/diffusion_original.py", line 1289, in extract_checkpoint\n    converted_unet_checkpoint, has_ema = convert_ldm_unet_checkpoint(\n', '  File "/home/ssube/onnx-web/api/onnx_web/convert/diffusion_original.py", line 496, in convert_ldm_unet_checkpoint\n    new_checkpoint = {"time_embedding.linear_1.weight": unet_state_dict["time_embed.0.weight"],\n', "KeyError: 'time_embed.0.weight'\n"]
[2023-02-17 13:44:51,999] ERROR: onnx_web.convert.diffusion_original: pipeline or config is not set, unable to continue.
[2023-02-17 13:44:52,314] INFO: onnx_web.convert.diffusion_original: converted original Diffusers checkpoint to Torch model

I've successfully converted this model using the latest main, which has a fallback path when the Torch JIT load fails: https://github.com/ssube/onnx-web/blob/main/api/onnx_web/convert/utils.py#L225
The missing keys were caused by that fallback not unwrapping the state_dict, which now occurs as well, and the model works great:


update(r3-corda-ent): ansible playbooks and roles to use the new standalone helm charts

Description
As a developer I want to cleanup, update and test ansible playbooks and roles so that the R3 Corda Enterprise network can be deployed using the new standalone helm charts
Acceptance Criteria

Network deployed using ansible playbook (No Proxy No Vault and with Proxy and Vault)
Network cleanup using ansible playbook

I will try this one


Added support for Wink Smoke and CO detectors

Description:
This adds support for Wink smoke and Co detectors, these will show up as binary sensors, one for smoke and one for co.
@rbflurry Can you test this?
Checklist:
If code communicates with devices, web services, or a:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Looks good.
binary_sensor.hallway_smoke_detector_co_detected	off
   battery_level: 90
   sensor_class: gas
   friendly_name: Hallway Smoke Detector co_detected

binary_sensor.hallway_smoke_detector_smoke_detected	off
   battery_level: 90
   sensor_class: smoke
   friendly_name: Hallway Smoke Detector smoke_detected

@rbflurry cool, thanks. What happens when you try to manually test the smoke detectors? Do these sensors turn on?

🐬

@rbflurry, How did you test this? Did your detectors get picked up via discovery? I have validated the pywink code is able to see mine, yet Home Assistant refuses to discover it. Thoughts?

Yes. It gets picked up after a restart and show up as a binary switch.

I just opened a PR (#3957). The needed "lambda:  pywink.get_sensors or pywink.get_smoke_and_co_detectors"  in wink.py was missing. Works now for me after this fix.


VirusTotal Sandbox - MALWARE TROJAN EVADER

Hello, do You know why VirusTotal triggers such alert with Your new GMS Core - "MALWARE TROJAN EVADER".
Here is link: [https://www.virustotal.com/gui/file/68ea7a4fc95fcb81cb1c1278c11c8da8caba5608ecefb6142461c668282a0545/behavior]
Old version microG was clean of that alert: [https://www.virustotal.com/gui/file/e5ce4f9759d3e70ac479bf2d0707efe5a42fca8513cf387de583b8659dbfbbbf/behavior]
I guess it's false positive but it's a little confusing.

Where did you download that GmsCore apk from?
Because using that virus scan site with the current release from here on GitHub shows no issues:
https://www.virustotal.com/gui/file/68ea7a4fc95fcb81cb1c1278c11c8da8caba5608ecefb6142461c668282a0545/detection

From this github website :) click on "Behaviour" - Sandbox.

Oh I see. Yes it must be a false positive.
Scanning the upstream MicroG release shows the same warnings:
https://www.virustotal.com/gui/file/1a6f6205d82c5075f1789cfc92924e5ea9b648b7397e9f667959ac4d956cb3f5/behavior

I don't know what is upstream MicroG but version which I used for very long time was free of that issue nad was working perfectly I posted it as second VT link.

Both the release pipeline and the source code are transparent on GitHub. This is an issue with Virus total and co.


Ability to Mark Requests as Flagged/ Resolved

Subject of the issue
Need a screen that will interact with a new table where issues can be tagged as flagged/ resolved
Original table will not be updated
Volunteers can enter the data on a screen which is only available for logged in volunteers.

Status (Flagged/ Resolved/ Duplicate etc.)
Reason (Text)
Updated by
Auto capture original ticket number, logged in user and timestamp in the table

For each original ticket, there can be multiple entries in the second table. Multiple people may/can update an original ticket.
Your environment

version of your python
which browser and its version
OS Type (iOS/Android/Linux/Windows)

Steps to reproduce
Tell us how to reproduce this issue. Please provide a working demo as a GIF, if possible.
Expected behaviour
Tell us what and how exactly is it supposed to  happen
Actual behaviour
Tell us what happens instead or what went wrong

Maybe we dont care about logged in user..bt text field abt who is updating..hopefully wont be abused. that way we open this up the the world..easier for all the teams who hve the data to update

add a reference/link to a related/subsequent request made?

@cibingeorge - Ticket number for subsequent ticket? Original ticket should be referenced. Would someone know the future ticket when updating this status?

Maybe i was too crazy..ignore that related thing suggestion

So would we be designing a new table for this referencing the original requests table?

Yes, that;'s the plan.

Would this reflect in the data from the /data endpoint?

That or ushahidi, that is the qn now

The ushahidi one seems to be taking a lot of time. I believe we could work on a quick fix on a different table as suggested so that the work can move on. The solution suggested by @vvazhayil could be done in a short time. What do you guys suggest?

@theryecatcher or anyone else available with Django dev capability, pls ping me on slack. same handle as here.

Can someone with the real on the ground experience state what resolutions should each ticket get?

Resolved
Pending
Duplicate
Flagged
? I don't know who can tell us that clearly.


Configure Azure PipelinesSet up CI with Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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


Add countries of interest as a field in the file download

Description of change
Checklist

[ ] Has a new newsfragment been created? Check changelog/README.rst for instructions
[ ] Do any added or updated endpoints appear in the API documentation? See docs/Maintaining the API documentation.md for more details
[ ] Have any relevant search models been updated?
[ ] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[ ] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[ ] Has the admin site been updated (for new models, fields etc.)?
[ ] Has the README been updated (if needed)?

waiting for @benpbenp changes to the countries of interest

Because of a the long tail of commits not related to this feature, the PR has been replicated here: https://github.com/uktrade/data-hub-leeloo/pull/2144 thus closing this PR. All change requests have been addressed


Removed unused code and suppressed warnings/errors

Added #[allow(dead_code)].
Removed TryGetIndex trait code since its not being used.

Nice! thanks. as we've discussed on discord, usually deadcode should be investigated, however since this is "legacy" code to be deleted in the future, this is fine


Finish publishing to Chocolatey

Objective
We had some outstanding changes needed to be made to get published on Chocolatey.
Acceptance Criteria

New Relic CLI is available via Chocolatey

https://chocolatey.org/packages/newrelic-cli/


SonarQube 8.9 LTS

SonarQube 8.9LTS and AEM rules 1.3 are triggering an error when performing a sonarQube maven scan.
[ERROR] Failed to execute goal sonar (default-cli) on project amazonclimatepledge.parent: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>6:sonar failed: An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>6:sonar: java.lang.NoSuchMethodError: com.cognifide.aemrules.java.checks.AdministrativeAccessUsageCheck.hasSemantic()Z

Hi @jlentink,
thanks for reporting this. Is this the full stack trace? It looks like an issue with runtime dependencies but it's not something I've seen before.
I've got a few questions to help isolate the issue:

Does this happen regardless of what project you scan or is just one affected?
Can you share the code you're scanning? If not, can you provide an anonimized example which allows this to be reproduced upon scan?

Regards,
Tomek

Hi @toniedzwiedz,
Unfortunately, I cannot share the code. But here is the full error
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal sonar:sonar (default-cli) on project projectname.parent: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>6:sonar failed: An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>6:sonar: java.lang.NoSuchMethodError: com.cognifide.aemrules.java.checks.AdministrativeAccessUsageCheck.hasSemantic()Z
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>6
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/Users/utopia/.m2/repository/org/sonarsource/scanner/maven/sonar-maven-plugin/<IP_ADDRESS>6/sonar-maven-plugin-<IP_ADDRESS>6.jar
[ERROR] urls[1] = file:/Users/utopia/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.4/plexus-sec-dispatcher-1.4.jar
[ERROR] urls[2] = file:/Users/utopia/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[3] = file:/Users/utopia/.m2/repository/org/codehaus/plexus/plexus-utils/3.2.1/plexus-utils-3.2.1.jar
[ERROR] urls[4] = file:/Users/utopia/.m2/repository/org/sonarsource/scanner/api/sonar-scanner-api/<IP_ADDRESS>2/sonar-scanner-api-<IP_ADDRESS>2.jar
[ERROR] urls[5] = file:/Users/utopia/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :projectname.parent

I have the same issue. @jlentink thanks for the workaround!

same problem here, after upgrading from SonarQube 7.x to 8.9.0. I am using the sonar-scanner-cli, so no Maven involved. it happens with every java project.
what I did:
download SQ 8.9 + unpack it
download aem-plugin and put it into extensions/plugins
start SQ
extend default java quality profile with all AEM rules, make the new quality profile the default
do a scan with sonar-scanner-cli of any project with at least 1 java file inside.
here is my stack-trace (similar to the one above):
ERROR: Error during SonarScanner execution java.lang.NoSuchMethodError: com.cognifide.aemrules.java.checks.AdministrativeAccessUsageCheck.hasSemantic()Z         at com.cognifide.aemrules.java.checks.AdministrativeAccessUsageCheck.visitNode(AdministrativeAccessUsageCheck.java:85)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.lambda$visit$6(VisitorsBridge.java:287)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.lambda$forEach$9(VisitorsBridge.java:303)         at org.sonar.java.model.VisitorsBridge.runScanner(VisitorsBridge.java:159)         at org.sonar.java.model.VisitorsBridge.access$100(VisitorsBridge.java:62)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.forEach(VisitorsBridge.java:303)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:289)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visitChildren(VisitorsBridge.java:273)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.visit(VisitorsBridge.java:293)         at org.sonar.java.model.VisitorsBridge$IssuableSubsciptionVisitorsRunner.run(VisitorsBridge.java:264)         at org.sonar.java.model.VisitorsBridge.visitFile(VisitorsBridge.java:139)         at org.sonar.java.ast.JavaAstScanner.simpleScan(JavaAstScanner.java:127)         at org.sonar.java.ast.JavaAstScanner.scan(JavaAstScanner.java:79)         at org.sonar.java.JavaSquid.scanSources(JavaSquid.java:130)         at org.sonar.java.JavaSquid.scan(JavaSquid.java:116)         at org.sonar.plugins.java.JavaSquidSensor.execute(JavaSquidSensor.java:105)         at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(AbstractSensorWrapper.java:48)         at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:85)         at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1(ModuleSensorsExecutor.java:59)         at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy(ModuleSensorsExecutor.java:77)         at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(ModuleSensorsExecutor.java:59)         at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:82)         at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)         at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)         at org.sonar.scanner.scan.ProjectScanContainer.scan(ProjectScanContainer.java:392)         at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:388)         at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:357)         at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)         at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)         at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:150)         at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:137)         at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:123)         at org.sonar.batch.bootstrapper.Batch.doExecute(Batch.java:72)         at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:66)         at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:46)         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)         at java.lang.reflect.Method.invoke(Method.java:498)         at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(IsolatedLauncherProxy.java:60)         at com.sun.proxy.$Proxy0.execute(Unknown Source)         at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(EmbeddedScanner.java:189)         at org.sonarsource.scanner.api.EmbeddedScanner.execute(EmbeddedScanner.java:138)         at org.sonarsource.scanner.cli.Main.execute(Main.java:112)         at org.sonarsource.scanner.cli.Main.execute(Main.java:75)         at org.sonarsource.scanner.cli.Main.main(Main.java:61)
I had a custom plugin developed by myself with exactly the same problem. I upgraded sonar-plugin-api to <IP_ADDRESS>852 and sonar-java-plugin to <IP_ADDRESS>025, did a rebuild of my plugin and it worked. since I only need my plugin to work in 8.9.0 I did not look into compatibility stuff, so I did not check in which version of sonar-java-plugin the API change was done and which sonar-plugin-api version is compatible with that. I simply went with the versions that are used in 8.9.0 LTS.

Hello,
We had the same issue after upgrading from sonarqube 8.6.0 to the latest lts version (8.9.1).
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>5:sonar (default-cli) on project daimler-embxp: Execution default-cli of goal org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>5:sonar failed: An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>5:sonar: java.lang.NoSuchMethodError: com.cognifide.aemrules.java.checks.AdministrativeAccessUsageCheck.hasSemantic()Z

Hello, we had the same issue

Same issue here too.

Same issue here as well. Any plans of releasing a new version of AEM rules plugin to fix this?

We've just upgraded to SonarQube 8.9.4 (the most recent LTS version) and came across the same problem.

Hope this pull request will solve the issue https://github.com/wttech/AEM-Rules-for-SonarQube/pull/216

Any updates about this issue?

Found an issue in Sonar Jira https://jira.sonarsource.com/browse/SONARJAVA-3793
I've just checked a PR with Sonar v8.9.7, it works fine. Could you please provide an update when we could expect a new release of AEM Rules plugin, because we are planing an upgrade of Sonar and we don't want to disable these checks.
Thanks

Is this project still active?

@ashokmca07 the tests pass locally for me, but I'll need to check this against a couple versions of the JDK and SonarQube. This was originally automated via TravicCI but there have been changes in how Travis operates so I'll need to get each PR to trigger a CI build first. I think I can quickly migrate to GitHub actions but that's something I'll have to pick up next week. Apologies for the further delay.

@ashokmca07 the tests pass locally for me, but I'll need to check this against a couple versions of the JDK and SonarQube. This was originally automated via TravicCI but there have been changes in how Travis operates so I'll need to get each PR to trigger a CI build first. I think I can quickly migrate to GitHub actions but that's something I'll have to pick up next week. Apologies for the further delay.

@toniedzwiedz thanks for your support

a while ago I fell into the same trap in one of my custom plugins. back then I discovered that a sonarQubeMinVersion of 8.9 enforces sonar-java 7.6
the latest sonarQubeMinVersion that does not enforce sonar-java 7.6 is 8.4, so using <sonarQubeMinVersion>8.4</sonarQubeMinVersion> should fix that.

@youngroman it's odd, because I'm using the Docker image for SonarQube Community 8.9 (sonarqube:8.9-community) and, according to the startup log, it has the plugin 'java' installed in version <IP_ADDRESS>025 (see the output in one of my last posts). If I'm not mistaken, this means that either the image is wrong, or there is compatibility.
It could be possible to support 8.4 and higher. For now, I'll try a combination of java:6.15 and SonarQube 8.9 LTS and see how the improved tests pass.

Exactly local/CI tests are always green. let me also take a look at the combination of java:6.15 and SonarQube 8.9 LTS
Local tests with docker (8.9 sonar community version):
[info] localaemrulessonarqube: waiting for web server to start ...
[info] localaemrulessonarqube: waiting for web server to start ...
[info] localaemrulessonarqube: waiting for web server to start ...
HTTP/1.1 200
[info] localaemrulessonarqube: waiting for sonarqube to be ready ...
[info] localaemrulessonarqube: waiting for sonarqube to be ready ...
[info] localaemrulessonarqube: waiting for sonarqube to be ready ...
[info] localaemrulessonarqube: waiting for sonarqube to be ready ...
{"id":"BF41A1F2-AX__o9IIvCvgEsth17C_","version":"<IP_ADDRESS>436","status":"UP"}
[info] localaemrulessonarqube: OK !
[info] localaemrulessonarqube: stopping container: f043fd9becd3ae76af35e68dee7d0cc8e39f3331a2082ee4e84828c0f7725f6e
f043fd9becd3ae76af35e68dee7d0cc8e39f3331a2082ee4e84828c0f7725f6e
localaemrulessonarqube => success```

@ashokmca07 they no longer are after the recent improvement https://github.com/wttech/AEM-Rules-for-SonarQube/runs/5855142958?check_suite_focus=true
Mind you, that test only gives us assurance that there aren't serious dependency conflicts that would prevent the server from starting up (which is something we've seen with SonarQube 7.9 in the past). To test the original issue this thread is actually about, we need to perform an analysis at runtime, with a quality profile that has AEM-11 enabled. I've reproduced the error in a version without your fix so I've got a good reference point.
For now, none of the automated tests covers this scenario (unit tests just use the java plugin version declared in the pom.xml while the startup tests just check if rules can be loaded) so this means I'll have to do a manual test.
Automation of actual analysis at runtime should be possible but it's not a scenario I can quickly cover.

https://github.com/wttech/AEM-Rules-for-SonarQube/pull/224 has a version that passes the improved tests, i.e. we know that AEM Rules have been installed. I'll test this version manually, if AEM-11 can be used without throwing errors, I think we have a release candidate :)

AEM-11 appears to work with the version from #224, I'll perform a release today and raise a PR to get it into the SonarQube marketplace

Release 1.6, compatible with SonarQube 8.9 LTS has been made available in the SonarQube marketplace. For sources and binary downloads, check https://github.com/wttech/AEM-Rules-for-SonarQube/releases/tag/v1.6
Many thanks to @ashokmca07 for the contribution and apologies for the long wait.

@toniedzwiedz Thanks a lot for your help and quick releases to SonarQube marketplace

Thanks @ashokmca07 and @toniedzwiedz for resolving this long pending issue and releasing a newer version, much appreciated!


Thank you for this fork

thank you've done this fork is a shame that the original developer abandoned beyond this application :/
Also I recommend Native Fier
You do a web app versions
You can use nativefier you to create a Facebook Messenger app and take some parts of the code to improve aluxian
https://github.com/jiahaog/nativefier

Thanks ;)
Currently I don`t have a lot of time, but as said in other issues, a new version based on electron is in development by the original dev. Its called Whatsie (its a repo on the original dev) for whatsapp, but it would be easy to convert it for facebook messenger. Eventually I might do it, but with school I currently dont have enough time.
Cheers


Update clonevirtualenv.py

The prompt prefix was incorrect in the new cloned environment.....
This seems to fix it.......

@geeregman I just got involved in maintaining this package.  Can you give more of a reproducer for the bug and/or add a test for your fix?  Thanks!


linux_lqx: 5.9.16 -> 5.10.4

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

8 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs

23 packages failed to build:

linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.ati_drivers_x11
linuxPackages_lqx.chipsec
linuxPackages_lqx.cryptodev
linuxPackages_lqx.dpdk
linuxPackages_lqx.ena
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.nvidia_x11_legacy340
linuxPackages_lqx.nvidia_x11_legacy390
linuxPackages_lqx.oci-seccomp-bpf-hook
linuxPackages_lqx.rtl8192eu
linuxPackages_lqx.rtl8812au
linuxPackages_lqx.rtl8814au
linuxPackages_lqx.rtl8821au
linuxPackages_lqx.rtl8821ce
linuxPackages_lqx.rtl88x2bu
linuxPackages_lqx.rtl88xxau-aircrack
linuxPackages_lqx.rtlwifi_new
linuxPackages_lqx.virtualbox
linuxPackages_lqx.virtualboxGuestAdditions

51 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linuxPackages_lqx.kernel
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8125
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsUnstable)

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108647 run on x86_64-linux 1

8 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs

73 packages failed to build and are new build failures:

linuxPackages_lqx.acpi_call: log was empty
linuxPackages_lqx.akvcam: log was empty
linuxPackages_lqx.amdgpu-pro: log was empty
linuxPackages_lqx.anbox: log was empty
linuxPackages_lqx.asus-wmi-sensors: log was empty
linuxPackages_lqx.batman_adv: log was empty
linuxPackages_lqx.bbswitch: log was empty
linuxPackages_lqx.bcc: log was empty
linuxPackages_lqx.bpftrace: log was empty
linuxPackages_lqx.broadcom_sta: log was empty
linuxPackages_lqx.can-isotp: log was empty
linuxPackages_lqx.chipsec: log was empty
linuxPackages_lqx.cryptodev: log was empty
linuxPackages_lqx.ddcci-driver: log was empty
linuxPackages_lqx.digimend: log was empty
linuxPackages_lqx.dpdk: log was empty
linuxPackages_lqx.ena: log was empty
linuxPackages_lqx.evdi: log was empty
linuxPackages_lqx.facetimehd: log was empty
linuxPackages_lqx.fwts-efi-runtime: log was empty
linuxPackages_lqx.gcadapter-oc-kmod: log was empty
linuxPackages_lqx.it87: log was empty
linuxPackages_lqx.jool: log was empty
linux_lqx: log was empty
(linuxPackages_lqx.kernel): log was empty
linuxPackages_lqx.mba6x_bl: log was empty
linuxPackages_lqx.mwprocapture: log was empty
linuxPackages_lqx.mxu11x0: log was empty
linuxPackages_lqx.netatop: log was empty
linuxPackages_lqx.nvidia_x11: log was empty
linuxPackages_lqx.nvidia_x11_beta: log was empty
linuxPackages_lqx.nvidia_x11_legacy340: log was empty
linuxPackages_lqx.nvidia_x11_legacy390: log was empty
linuxPackages_lqx.nvidia_x11_vulkan_beta: log was empty
linuxPackages_lqx.nvidiabl: log was empty
linuxPackages_lqx.oci-seccomp-bpf-hook: log was empty
linuxPackages_lqx.openafs: log was empty
(linuxPackages_lqx.openafs_1_8): log was empty
linuxPackages_lqx.openafs_1_9: log was empty
linuxPackages_lqx.openrazer: log was empty
linuxPackages_lqx.perf: log https://hastebin.com/raw/esaduwuhud
linuxPackages_lqx.r8125: log was empty
linuxPackages_lqx.r8168: log was empty
linuxPackages_lqx.rtl8192eu: log was empty
linuxPackages_lqx.rtl8812au: log was empty
linuxPackages_lqx.rtl8814au: log was empty
linuxPackages_lqx.rtl8821au: log was empty
linuxPackages_lqx.rtl8821ce: log was empty
linuxPackages_lqx.rtl8821cu: log was empty
linuxPackages_lqx.rtl88x2bu: log was empty
linuxPackages_lqx.rtl88xxau-aircrack: log was empty
linuxPackages_lqx.rtlwifi_new: log was empty
linuxPackages_lqx.sysdig: log was empty
linuxPackages_lqx.system76: log was empty
linuxPackages_lqx.system76-acpi: log was empty
linuxPackages_lqx.system76-io: log was empty
linuxPackages_lqx.systemtap: log was empty
linuxPackages_lqx.tmon: log was empty
linuxPackages_lqx.tp_smapi: log was empty
linuxPackages_lqx.turbostat: log was empty
linuxPackages_lqx.tuxedo-keyboard: log was empty
linuxPackages_lqx.usbip: log was empty
linuxPackages_lqx.v4l2loopback: log was empty
linuxPackages_lqx.v86d: log was empty
linuxPackages_lqx.vhba: log was empty
linuxPackages_lqx.virtualbox: log was empty
linuxPackages_lqx.virtualboxGuestAdditions: log was empty
linuxPackages_lqx.x86_energy_perf_policy: log was empty
linuxPackages_lqx.xpadneo: log was empty
linuxPackages_lqx.zenpower: log was empty
linuxPackages_lqx.zfs: log was empty
(linuxPackages_lqx.zfsStable: log was empty
,linuxPackages_lqx.zfsUnstable): log was empty

4 packages built:

linuxPackages_lqx.cpupower
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.ply

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108647 run on x86_64-linux 1

8 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs

73 packages failed to build and are new build failures:

linuxPackages_lqx.acpi_call: log was empty
linuxPackages_lqx.akvcam: log was empty
linuxPackages_lqx.amdgpu-pro: log was empty
linuxPackages_lqx.anbox: log was empty
linuxPackages_lqx.asus-wmi-sensors: log was empty
linuxPackages_lqx.batman_adv: log was empty
linuxPackages_lqx.bbswitch: log was empty
linuxPackages_lqx.bcc: log was empty
linuxPackages_lqx.bpftrace: log was empty
linuxPackages_lqx.broadcom_sta: log was empty
linuxPackages_lqx.can-isotp: log was empty
linuxPackages_lqx.chipsec: log was empty
linuxPackages_lqx.cryptodev: log was empty
linuxPackages_lqx.ddcci-driver: log was empty
linuxPackages_lqx.digimend: log was empty
linuxPackages_lqx.dpdk: log was empty
linuxPackages_lqx.ena: log was empty
linuxPackages_lqx.evdi: log was empty
linuxPackages_lqx.facetimehd: log was empty
linuxPackages_lqx.fwts-efi-runtime: log was empty
linuxPackages_lqx.gcadapter-oc-kmod: log was empty
linuxPackages_lqx.it87: log was empty
linuxPackages_lqx.jool: log was empty
linux_lqx: log was empty
(linuxPackages_lqx.kernel): log was empty
linuxPackages_lqx.mba6x_bl: log was empty
linuxPackages_lqx.mwprocapture: log was empty
linuxPackages_lqx.mxu11x0: log was empty
linuxPackages_lqx.netatop: log was empty
linuxPackages_lqx.nvidia_x11: log was empty
linuxPackages_lqx.nvidia_x11_beta: log was empty
linuxPackages_lqx.nvidia_x11_legacy340: log was empty
linuxPackages_lqx.nvidia_x11_legacy390: log was empty
linuxPackages_lqx.nvidia_x11_vulkan_beta: log was empty
linuxPackages_lqx.nvidiabl: log was empty
linuxPackages_lqx.oci-seccomp-bpf-hook: log was empty
linuxPackages_lqx.openafs: log was empty
(linuxPackages_lqx.openafs_1_8): log was empty
linuxPackages_lqx.openafs_1_9: log was empty
linuxPackages_lqx.openrazer: log was empty
linuxPackages_lqx.perf: log https://hastebin.com/raw/esaduwuhud
linuxPackages_lqx.r8125: log was empty
linuxPackages_lqx.r8168: log was empty
linuxPackages_lqx.rtl8192eu: log was empty
linuxPackages_lqx.rtl8812au: log was empty
linuxPackages_lqx.rtl8814au: log was empty
linuxPackages_lqx.rtl8821au: log was empty
linuxPackages_lqx.rtl8821ce: log was empty
linuxPackages_lqx.rtl8821cu: log was empty
linuxPackages_lqx.rtl88x2bu: log was empty
linuxPackages_lqx.rtl88xxau-aircrack: log was empty
linuxPackages_lqx.rtlwifi_new: log was empty
linuxPackages_lqx.sysdig: log was empty
linuxPackages_lqx.system76: log was empty
linuxPackages_lqx.system76-acpi: log was empty
linuxPackages_lqx.system76-io: log was empty
linuxPackages_lqx.systemtap: log was empty
linuxPackages_lqx.tmon: log was empty
linuxPackages_lqx.tp_smapi: log was empty
linuxPackages_lqx.turbostat: log was empty
linuxPackages_lqx.tuxedo-keyboard: log was empty
linuxPackages_lqx.usbip: log was empty
linuxPackages_lqx.v4l2loopback: log was empty
linuxPackages_lqx.v86d: log was empty
linuxPackages_lqx.vhba: log was empty
linuxPackages_lqx.virtualbox: log was empty
linuxPackages_lqx.virtualboxGuestAdditions: log was empty
linuxPackages_lqx.x86_energy_perf_policy: log was empty
linuxPackages_lqx.xpadneo: log was empty
linuxPackages_lqx.zenpower: log was empty
linuxPackages_lqx.zfs: log was empty
(linuxPackages_lqx.zfsStable: log was empty
,linuxPackages_lqx.zfsUnstable): log was empty

4 packages built:

linuxPackages_lqx.cpupower
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.ply

I think your bot is broken @SuperSandro2000

I think your bot is broken @SuperSandro2000

I think your bot is broken @SuperSandro2000

This is not a bot but some fancy bash functions around me and I found why I did not build anything. My machine does not have big-parallel.

I think your bot is broken @SuperSandro2000

This is not a bot but some fancy bash functions around me and I found why I did not build anything. My machine does not have big-parallel.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108647 run on x86_64-linux 1

8 packages marked as broken and skipped:

linuxPackages_lqx.ixgbevf
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.nvidia_x11_legacy304
linuxPackages_lqx.phc-intel
linuxPackages_lqx.rtl8723bs
linuxPackages_lqx.sch_cake
linuxPackages_lqx.tbs

22 packages failed to build and are new build failures:

linuxPackages_lqx.akvcam: log https://hastebin.com/raw/wujakucaki
linuxPackages_lqx.amdgpu-pro: log https://hastebin.com/raw/ilenebazoc
linuxPackages_lqx.anbox: log https://hastebin.com/raw/leledigoqa
linuxPackages_lqx.chipsec: log https://hastebin.com/raw/opinihojax
linuxPackages_lqx.cryptodev: log https://hastebin.com/raw/ujikenaxos
linuxPackages_lqx.dpdk: log https://hastebin.com/raw/Document exceeds maximum length.
linuxPackages_lqx.ena: log https://hastebin.com/raw/eminemufij
linuxPackages_lqx.mwprocapture: log https://hastebin.com/raw/megodoqajo
linuxPackages_lqx.mxu11x0: log https://hastebin.com/raw/ocosetofip
linuxPackages_lqx.nvidia_x11_legacy340: log https://hastebin.com/raw/eqecagaqaf
linuxPackages_lqx.nvidia_x11_legacy390: log https://hastebin.com/raw/ozekevufol
linuxPackages_lqx.oci-seccomp-bpf-hook: log https://hastebin.com/raw/exalosasib
linuxPackages_lqx.rtl8192eu: log https://hastebin.com/raw/vawodesuca
linuxPackages_lqx.rtl8812au: log https://hastebin.com/raw/yirizepeko
linuxPackages_lqx.rtl8814au: log https://hastebin.com/raw/yaxekafegu
linuxPackages_lqx.rtl8821au: log https://hastebin.com/raw/azobepixah
linuxPackages_lqx.rtl8821ce: log https://hastebin.com/raw/onimayelaj
linuxPackages_lqx.rtl88x2bu: log https://hastebin.com/raw/kuloyofolo
linuxPackages_lqx.rtl88xxau-aircrack: log https://hastebin.com/raw/kodoheyuzu
linuxPackages_lqx.rtlwifi_new: log https://hastebin.com/raw/bemohedesi
linuxPackages_lqx.virtualbox: log https://hastebin.com/raw/duzimusafu
linuxPackages_lqx.virtualboxGuestAdditions: log https://hastebin.com/raw/asoyapifix

51 packages built:

linuxPackages_lqx.acpi_call
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.cpupower
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.it87
linuxPackages_lqx.jool
linux_lqx (linuxPackages_lqx.kernel)
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta
linuxPackages_lqx.nvidia_x11_vulkan_beta
linuxPackages_lqx.nvidiabl
linuxPackages_lqx.openafs (linuxPackages_lqx.openafs_1_8)
linuxPackages_lqx.openafs_1_9
linuxPackages_lqx.openrazer
linuxPackages_lqx.perf
linuxPackages_lqx.ply
linuxPackages_lqx.r8125
linuxPackages_lqx.r8168
linuxPackages_lqx.rtl8821cu
linuxPackages_lqx.sysdig
linuxPackages_lqx.system76
linuxPackages_lqx.system76-acpi
linuxPackages_lqx.system76-io
linuxPackages_lqx.systemtap
linuxPackages_lqx.tmon
linuxPackages_lqx.tp_smapi
linuxPackages_lqx.turbostat
linuxPackages_lqx.tuxedo-keyboard
linuxPackages_lqx.usbip
linuxPackages_lqx.v4l2loopback
linuxPackages_lqx.v86d
linuxPackages_lqx.vhba
linuxPackages_lqx.x86_energy_perf_policy
linuxPackages_lqx.xpadneo
linuxPackages_lqx.zenpower
linuxPackages_lqx.zfs (linuxPackages_lqx.zfsStable ,linuxPackages_lqx.zfsUnstable)

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.


Add again gitective property to update version automatically

[merge]

Code not merged because @oscerd (Andrea Cosentino) is not in the Admin list.

GRRRR!
ping @davsclaus @jstrachan :-)

add to whitelist

[merge]


Support for hw transcoding using gid 106 (render)

Took me some days to finally figure this out. Might help someone:
In addition - or apart from – the given groups, I had to add gid 106 (render) to enable hw decoding on Debian 11 for Plex.
render:x:106:

https://github.com/onedr0p/home-ops/blob/6b0c4db69ebcb73d53d2eac1f52d8cdb2af31414/kubernetes/apps/default/plex/app/helmrelease.yaml#L66

via https://github.com/MichaIng/DietPi/issues/2916#issuecomment-503679311

109 is render on Ubuntu but good to know on Debian it is 106


Add universal audio player for ELSE

Download, compile and statically link ffmpeg for easier compilation
Simplified code structure a little bit
Put libsamplerate in shared folder, so circuit~ and ffplay~ can both use it

This is just a WIP version we can work on, here are some things we still need to do:

For me, it currently crashes if I hit play with no audio file loaded
The helpfile needs to be improved
We might want to change the object name
We might want to add the ability to load audio files to arrays directly (so you don't have to "record" into an array)
I think the object's interface it nice, but you might have some ideas here ;)

Maybe there could be an "array arrname" message to write the currently opened audio file to an array?

Btw, this might not read all audio file types yet. I think I need to link some extra libraries like LAME and Vorbis too.

I think we also need a new [soundfiler] object that can also import these files to arrays, and maybe save them too


[Domains] Add version of public suffix list shipped with release packages

(implements #433)

log for processed public suffix list

MD5 and SHA-512
number of bytes, lines and rules
commit date and git hash, cf. https://github.com/publicsuffix/list/issues/1808

Thanks to publicsuffix/list#1808, the solution works for any public suffix list, no matter if it is shipped in a crawler-commons release package or read from somewhere else. Note: in order to get a recent list which includes the commit date and hash, the Maven download cache needs to be cleared, e.g. rm $HOME/.m2/repository/.cache/download-maven-plugin/*
Example log output:
[main] INFO crawlercommons.domains.EffectiveTldFinder - Loading public suffix list from class path: jar:file:.../crawler-commons/target/crawler-commons-1.5-SNAPSHOT.jar!/effective_tld_names.dat
[main] INFO crawlercommons.domains.EffectiveTldFinder - Public suffix list VERSION: 2024-11-07_17-56-52_UTC
[main] INFO crawlercommons.domains.EffectiveTldFinder - Public suffix list COMMIT: e65bca4146a494d60dd4d3beb4a244376fb3825b
[main] INFO crawlercommons.domains.EffectiveTldFinder - Successfully read public suffix list: 315919 bytes, 15735 lines, 9777 rules
[main] INFO crawlercommons.domains.EffectiveTldFinder - Digest of public suffix list: MD5 = 907C046E01635ACDDB65852144C90C2F
[main] INFO crawlercommons.domains.EffectiveTldFinder - Digest of public suffix list: SHA-512 = 883B206580029F58A94DA89AB20A02FACBF93FE04113A5147AC25DD2E190A9E57207FE491C23E634897058B7697BD351D4A7E51A8FCD26CDB9B846A9B29822CA

Thanks for the review, @rzo1!
Resolved conflict and rebased to master.


StreamValue no longer sliceable

Issue Summary
Following an upgrade from Wagtail 2.10 to 2.12.3, it appears that StreamValue items are no longer sliceable.
e.g.
{% for footer in footernav|slice:":2" %}
  {% include_block footer %}
{% endfor %}

would previously render the first 2 blocks in footernav, but now renders None twice instead.
(This can be worked around by first casting the StreamValue with list().)
Steps to Reproduce

Pass a StreamValue variable into a request's context
Use the |slice filter on the variable
Check the resulting values

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: No

Technical details

Python version: 3.8.2
Django version: 3.0.13
Wagtail version: 2.12.3
Browser version: Any

Thanks @alxbridge!
I don't think this has ever worked - I suspect that the pre-2.12 behaviour of the above code was to output the complete unsliced list, so we've basically traded one bit of undefined behaviour for another. That's what I'm seeing when I test against bakerydemo, changing the {{ page.body }} in blog_page.html to
            {% for block in page.body|slice:":2" %}
                {% include_block block %}
            {% endfor %}

This is because the |slice filter returns the original value in the case of a TypeError, and the old implementation of StreamValue.__getitem__ tries looking up the index in the _bound_blocks dict, which will always fail with TypeError: unhashable type when passed a slice object.
Hopefully this should be a pretty quick thing to fix though...

PR: https://github.com/wagtail/wagtail/pull/7013

Thanks @gasman : that makes sense about the pre-2.12 behaviour - I can see that's the case now.
I've tested your PR and it works well for the example I gave above.


suggestion: rename = to var

I think (var a 1) and (var a) read closer to their intent than (= a 1) and (= a)
Also, ES6 has let, so including a let macro into eslisp later would be more orthogonal if the hoisted declaration identifier is var
And that would free up the = identifier so you could use that for assignment instead of :=, to keep things closer to js syntax

I agree—those should be the defaults.
The current names are remnants from when it hadn't quite clicked yet that I wanted eslisp to just clearly map to JS.

In v0.5.0. :sparkles:


Update walkthrough to support kubectl create

kubectl create (as opposed to kubecfg) requires kind in the pod to work, so I add it here.

LGTM

Makes me wonder why they didn't get caught by examples_test.go validation though.

https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/examples_test.go#L119 and https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/examples_test.go#L140 are where it's tested... if you only ask to decode into a specific type, does it still require a kind field in the JSON?

It's probably a decision that different code needs to make differently. The rest api should probably reject untyped incoming objects, but a cli or generation / import function may not.

On Feb 12, 2015, at 5:46 PM, Sam Ghods<EMAIL_ADDRESS>wrote:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/examples_test.go#L119 and https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/examples_test.go#L140 are where it's tested... if you only ask to decode into a specific type, does it still require a kind field in the JSON?
—
Reply to this email directly or view it on GitHub.


Extend ManagedResource controller to optionally finalize resource deletion after grace period

How to categorize this PR?

/area dev-productivity
/kind enhancement
What this PR does / why we need it:
With this PR, it is possible to annotate managed resource part of ManagedResource with resources.gardener.cloud/finalize-deletion-after=<duration>, e.g., resources.gardener.cloud/finalize-deletion-after=1h.
After this time, it will forcefully delete the resource by removing their finalizers.
Without this annotation, it would block forever until another entity removes the finalizers from the managed resource (today's behaviour).
This feature can be helpful for extension developers that want gardener-resource-manager from forcefully deleting their managed resources after some grace period (e.g., cert-/dns extension which deploy CRDs into the shoot cluster).
Special notes for your reviewer:
/cc @ScheererJ
Release note:

It is now possible to annotate managed resource part of `ManagedResource`s with `resources.gardener.cloud/finalize-deletion-after=<duration>`, e.g., `resources.gardener.cloud/finalize-deletion-after=1h`. After this time, it will forcefully delete the resource by removing their finalizers.

/approve


fixing the type of get response

fix the type of get response from Response to {data:Response}

Solves https://github.com/mondaycom/monday-sdk-js/issues/135


Ockam Enroll "email: '+' character not allowed"

Observed behavior
When enrolling in Ockam, after entering the code on the website for authentication, the console errors out. Verbose output:

ockam enroll -v

        .8888888.           dP
       d8'     `8b          88
       88       88 .d8888b. 88  .dP  .d8888b. 88d8b.d8b.
       88       88 88'  `"" 88888"   88'  `88 88'`88'`88
       Y8.     .8P 88.  ... 88  `8b. 88.  .88 88  88  88
        `888888P'  `88888P' dP   `YP `88888P8 dP  dP  dP

2023-09-26T17:33:22.001408Z  INFO ockam_node::node: Initializing ockam node
2023-09-26T17:33:22.024586Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/vault"
2023-09-26T17:33:22.024607Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/vaults/7bdd25eb.json"
2023-09-26T17:33:22.024679Z  INFO ockam_api::cli_state::traits: Set default item name=7bdd25eb
2023-09-26T17:33:22.051078Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/identity"
2023-09-26T17:33:22.051100Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/identities/default.json"
2023-09-26T17:33:22.051173Z  INFO ockam_api::cli_state::traits: Set default item name=default
2023-09-26T17:33:22.051178Z  INFO ockam_api::cli_state::traits: Created new config resource name=default
     ✔ Identity I503c97350dbf052195ac3e5da2fb4d965bd7f118
       created successfully as default
       Enrolling your default Ockam identity with Ockam Orchestrator...

       There is no identity, on this machine, marked as your default.
       Creating a new Ockam identity for you...
     ✔ Created: I503c97350dbf052195ac3e5da2fb4d965bd7f118
       Marked this new identity as your default, on this machine.
                                                                                [0/1946]
2023-09-26T17:33:22.051592Z  INFO ockam_node::router::shutdown: Initiate graceful node shutdown
2023-09-26T17:33:22.051712Z  INFO ockam_node::router: No more workers left.  Goodbye!
2023-09-26T17:33:22.054181Z  INFO ockam_node::node: Initializing ockam node
2023-09-26T17:33:22.630892Z  INFO ockam_api::enroll::oidc_service: code received: DeviceCode {
    device_code: "7ehH6Ti7-zALgvNQxogk-SuE",
    user_code: "JBZM-XGKF",
    verification_uri: "https://account.ockam.io/activate",
    verification_uri_complete: "https://account.ockam.io/activate?user_code=JBZM-XGKF",
    expires_in: 900,
    interval: 5,
} res=DeviceCode { device_code: "7ehH6Ti7-zALgvNQxogk-SuE", user_code: "JBZM-XGKF", verification_uri: "https://account.ockam.io/activate", verification_uri_complete: "https://account.ockam.io/activate?user_code=JBZM-XGKF", expires_in: 900, interval: 5 }
       To enroll we need to associate your Ockam identity with an Orchestrator account:

     │ First copy this one-time code:  JBZM-XGKF
     │ Then press  ENTER ↵  to open https://account.ockam.io/activate in your browser.

     │ Opening https://account.ockam.io/activate, in your browser, to begin authentication...
     │ Authenticated

     │ Email<EMAIL_ADDRESS>verified

2023-09-26T17:33:33.776058Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/user_info"
2023-09-26T17:33:33.776100Z  INFO ockam_api::cli_state::traits: symlink to<EMAIL_ADDRESS>2023-09-26T17:33:33.776184Z  INFO ockam_api::cli_state::traits: Set default item<EMAIL_ADDRESS>2023-09-26T17:33:33.809789Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/node"
2023-09-26T17:33:33.809814Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/nodes/911754d6"
2023-09-26T17:33:33.809867Z  INFO ockam_api::cli_state::traits: Set default item name=911754d6
2023-09-26T17:33:33.809882Z  INFO ockam_api::cli_state::nodes: node state initialized name=911754d6
2023-09-26T17:33:33.810425Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#bad9f22170574820367156ce832b4e71' with access control in:DenyAll out:DenyAll
2023-09-26T17:33:33.818531Z  INFO ockam_api::nodes::service: created a node manager for the node: 911754d6
2023-09-26T17:33:34.040250Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#94c4d84103f27f139cd80f69d295e42a' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 9e19791b1abd5733b02262ece7a0a7c6, spawner_flow_control_id: None }
2023-09-26T17:33:34.130056Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#b23eb313639702eb008be459888bf401, remote: 0#35060df75559bc8e85a831d11ea28aa1
2023-09-26T17:33:34.610619Z ERROR ockam_command::util: Failed to run command e=Failed to enroll your local identity with Ockam Orchestrator
OCK500

  × Failed to enroll your local identity with Ockam Orchestrator
  ╰─▶ An error occurred while processing the request. Status code: 400 BadRequest. Message: email: '+' character not allowed
  help: Please report this issue, with a copy of your logs, to https://github.com/build-trust/ockam/issues

  Version 0.94.0, hash: 0b170e6a414d90494b44e4e978c07ae793b56ec6

Steps to reproduce

Fresh install of Ockam: brew install build-trust/ockam/ockam
ockam enroll
Copy code from zsh into browser field
Confirm
Return to zsh and see error

Expected behavior
Expect to be able to enroll with email that created my account, however a + is not allowed. This should have been denoted when the user creates their account. If chaining is not permitted, it should be stopped before the account creation occurs.
Expected to receive an email (which I did via chaining, however the enroll function does not seem to permit it).
It is also not clear how to logout (trial and error I found that it's account.ockam.io/logout), which perpetuated many repeated attempts (login is automatically detected).
Expected output when no + is used:
ockam enroll -v

        .8888888.           dP
       d8'     `8b          88
       88       88 .d8888b. 88  .dP  .d8888b. 88d8b.d8b.
       88       88 88'  `"" 88888"   88'  `88 88'`88'`88
       Y8.     .8P 88.  ... 88  `8b. 88.  .88 88  88  88
        `888888P'  `88888P' dP   `YP `88888P8 dP  dP  dP

2023-09-26T17:43:05.743399Z  INFO ockam_node::node: Initializing ockam node
       Enrolling your default Ockam identity with Ockam Orchestrator...

2023-09-26T17:43:06.392469Z  INFO ockam_api::enroll::oidc_service: code received: DeviceCode {
    device_code: "Urs1V2vxyHJDUaqytjXOoazP",
    user_code: "GWFV-MXCS",
    verification_uri: "https://account.ockam.io/activate",
    verification_uri_complete: "https://account.ockam.io/activate?user_code=GWFV-MXCS",
    expires_in: 900,
    interval: 5,
} res=DeviceCode { device_code: "Urs1V2vxyHJDUaqytjXOoazP", user_code: "GWFV-MXCS", verification_uri: "https://account.ockam.io/activate", verification_uri_complete: "https://account.ockam.io/activate?user_code=GWFV-MXCS", expires_in: 900, interval: 5 }
       To enroll we need to associate your Ockam identity with an Orchestrator account:

     │ First copy this one-time code:  GWFV-MXCS
     │ Then press  ENTER ↵  to open https://account.ockam.io/activate in your browser.

     │ Opening https://account.ockam.io/activate, in your browser, to begin authentication...
     │ Authenticated

     │ Email<EMAIL_ADDRESS>verified

2023-09-26T17:44:40.596841Z  INFO ockam_api::cli_state::nodes: node state initialized name=523b53ec
2023-09-26T17:44:40.598408Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#1b80e1ffc820a6d0eac48a34e8d7505a' with access control in:DenyAll out:DenyAll
2023-09-26T17:44:40.600828Z  INFO ockam_api::nodes::service: created a node manager for the node: 523b53ec
2023-09-26T17:44:40.735357Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#ffed607c31d593cbaa56107746ffbb9f' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: ee217603956fb892f88410dfc5a02b90, spawner_flow_control_id: None }
2023-09-26T17:44:40.821038Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#c77ad70a3ab3361099c321fe7229b91f, remote: 0#76eca18061146cc967e61b5ad9d84612
2023-09-26T17:44:41.181657Z  INFO ockam_command::enroll::command: Enrolled successfully
       Getting available spaces in your account...
     ⠙ Checking for any existing spaces...
2023-09-26T17:44:41.249077Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#6e79374c87dc4471072dea88e75f1368' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: b58e04d1ad270e8c2132abfdbd889600, spawner_flow_control_id: None }
     ⠹ Checking for any existing spaces...
2023-09-26T17:44:41.313654Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#cc0b2260f664d3eb0a21e4f83bf57e6d, remote: 0#802b855223f973d40b165f168e7b4c5f
     │ No spaces are defined in your account.
     │ Creating a trial space for you (everything in it will be deleted in 15 days) ...
     │ To learn more about production ready spaces in Ockam Orchestrator, contact us at<EMAIL_ADDRESS>     ⠙ Creating space 012772b9...
2023-09-26T17:44:41.751739Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#c6ef2adb4d509fcaf114a82f2559aea1' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: c0015e5ca0218abe34de300222671f13, spawner_flow_control_id: None }
     ⠹ Creating space 012772b9...
2023-09-26T17:44:41.815027Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#f02b86cd82ef3334e509d947042b9c4b, remote: 0#3b2442596aefdaf72fb8ae93dc199054
2023-09-26T17:44:42.188021Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/space"
2023-09-26T17:44:42.188077Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/spaces/012772b9.json"
2023-09-26T17:44:42.188169Z  INFO ockam_api::cli_state::traits: Set default item name=012772b9
     ✔ Marked this space as your default space, on this machine.

       Getting available projects in space 012772b9...
     ⠙ Checking for any existing projects...
2023-09-26T17:44:42.188219Z  INFO ockam_command::enroll::command: Retrieved the user default space Space { id: "a4c4fa0c-8fc3-4acf-b1bd-47cf893e9e5b", name: "012772b9", users<EMAIL_ADDRESS>}
2023-09-26T17:44:42.256283Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#415a65f72d0bf0b0e502f63bb06fbc56' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: adc1fdc165f69f534a50ed42d4a8194d, spawner_flow_control_id: None }
     ⠹ Checking for any existing projects...
2023-09-26T17:44:42.319104Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#ba11dc1ab387db203dc2dd6c44b5fdfa, remote: 0#02ad29eba5b82b5500cd577b6631581c
     │ No projects are defined in the space 012772b9.
     │ Creating a project for you...
     ⠙ Creating project default...
2023-09-26T17:44:42.755555Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#f8977ea43063201a7b21cf6771f08c20' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: e584f207da1ca79c77c935a18bfb35d7, spawner_flow_control_id: None }
     ⠹ Creating project default...
2023-09-26T17:44:42.822273Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#3be499204b2a318f8b81b6748942be50, remote: 0#d91b382b6359cff4c90ac35f8447c239
     ✔ Created project default.
     ⠙ Configuring project...
2023-09-26T17:44:43.257402Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#29dc4012843c230290966c97181bd16c' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: d4d9f6d85713b5209de13b657663a8be, spawner_flow_control_id: None }
     ⠹ Configuring project...
2023-09-26T17:44:43.319187Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#9f165e40cde61eb99a653d1d5053263c, remote: 0#e7a2a2f123c4987158ab815ff99a63a5
     ⠹ Configuring project...
2023-09-26T17:44:48.561667Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#34d7eeded057f2ecf8ac8c069fc17340' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: e57ab9ab6eea79c6d22d33f456753905, spawner_flow_control_id: None }
     ⠸ Configuring project...
2023-09-26T17:44:48.623941Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#b1b4f8c1e9b272487d3a64efa6fe0992, remote: 0#aadd5552caa052fce5ac3a0c7615c04d
     ⠸ Configuring project...
2023-09-26T17:44:53.872672Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#f24a66aa007423a9f8cfcc2714698b6a' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 0b4c1925424c290584652b27754972e7, spawner_flow_control_id: None }
     ⠼ Configuring project...
2023-09-26T17:44:53.937566Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#67cc91ec20db30f4ec17ad0243f76085, remote: 0#1fdd641749b6e10beb544ce236faf066
     ⠼ Configuring project...
2023-09-26T17:44:59.191513Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#1f5909fdc972784e7b1c979826b176ce' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 74bb58329c21b9d228080ead8c3257ba, spawner_flow_control_id: None }
2023-09-26T17:44:59.265335Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#bc93dca28165ac6a71397f0fa7d5aaa6, remote: 0#c8d9b77f476afe264728fe888b8cb0c3
     ⠴ Configuring project...
2023-09-26T17:45:04.520476Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#ee827daeaaa5d8070188c566feb5243f' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 6533e562584f24fde125103cfdb78311, spawner_flow_control_id: None }
2023-09-26T17:45:04.582956Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#bc9f8f4c20aec152e21e421ae6c0b89f, remote: 0#a02ee9d29fc73270b646af7ee0832731
     ⠴ Configuring project...
2023-09-26T17:45:09.842860Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#46fa680d49e5d455550f94df1337c357' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 690ac34fffca786737a74e9faebe6309, spawner_flow_control_id: None }
     ⠦ Configuring project...
2023-09-26T17:45:09.907004Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#22e3f810341a5bfe07112bcf684f09d9, remote: 0#c3e5c56c9f90c1aae8ab0fe164ed3fe4
     ⠋ Configuring project...
2023-09-26T17:45:16.154175Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#d24ecdc123af4dc8c6bd9dc49341b60d' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 13bb0eea43386c842aa72de778c014ad, spawner_flow_control_id: None }
     ⠙ Configuring project...
2023-09-26T17:45:16.224927Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#2aaf97676d91a73bbd91ba18f00d2f50, remote: 0#68a9fda76249d095bcda0b56eead9aa3
     ⠙ Configuring project...
2023-09-26T17:45:21.470312Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#c8de0b995c5b0081a9bae7abc7bc564e' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 5ac195db4d40ada151148c0261555be9, spawner_flow_control_id: None }
2023-09-26T17:45:21.533971Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#6e88eb7cc928f687701e531aa1f198d8, remote: 0#439f69b383b828ef1677db5840a99dfc
     ⠹ Configuring project...
2023-09-26T17:45:26.782323Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#c91a4f1e45449e91a43dcca55eb83c94' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 0fd6daee2998aa7bed65b44588f7d237, spawner_flow_control_id: None }
     ⠸ Configuring project...
2023-09-26T17:45:26.845115Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#ab6775761b49016f50383d2369233202, remote: 0#24707069fe3073eb6e705bb68492977a
     ⠸ Configuring project...
2023-09-26T17:45:32.095717Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#b49b33a76f35511f4e759e788dc5e865' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 3659070f66e1d8acf250809d095f32b5, spawner_flow_control_id: None }
     ⠼ Configuring project...
2023-09-26T17:45:32.162254Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#b6781fb210eea41cfe3e908581af1b72, remote: 0#2b516c221c5e199fc5bc386463dcf5cb
     ⠸ Configuring project...
2023-09-26T17:45:37.406704Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#1f10b7425436d48c077644dbfb2618e5' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 7526147ee7968e35fc22102b6db8a5ab, spawner_flow_control_id: None }
     ⠼ Configuring project...
2023-09-26T17:45:37.468260Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#65e73c6343d3d6d7728adb252a785fea, remote: 0#ddf61a2586b10cf0d41f96f7b869527f
     ⠼ Configuring project...
2023-09-26T17:45:42.716997Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#e41f200afea6068d4aad4d28b49a45c0' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: b233925fb55ea24bdacfa54192013962, spawner_flow_control_id: None }
     ⠴ Configuring project...
2023-09-26T17:45:42.779014Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#c1dd5b62bd889947175ab9419c1f36bb, remote: 0#49741fde6d9ded682341e91f54b9a1a3
     ⠴ Configuring project...
2023-09-26T17:45:48.020692Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#c56ef2e09cfdf285dc3140259713da8c' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: a755021ef29db86ee1b5b472b7657129, spawner_flow_control_id: None }
2023-09-26T17:45:48.083535Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#9a04e7ee08a4f1d77b36f3c0fa69fa6e, remote: 0#48a05eb34758a578f21d0c3d915cb3d1
     ⠴ Configuring project...
2023-09-26T17:45:53.328331Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#7ad63e603dc2a38543a3172ade62bc94' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 13dda72c7f801e05254d3b5a296e6024, spawner_flow_control_id: None }
     ⠦ Configuring project...
2023-09-26T17:45:53.390843Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#e8ba90efc9cfb43b2eb3528126a98dba, remote: 0#692059411e27dde16c3254accfee45bc
     ⠇ Configuring project...
2023-09-26T17:45:58.809258Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#b984f2030b805e27fba9282f00b91d81' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 68a0a805bd38c150ba331ec9d5cc6184, spawner_flow_control_id: None }
     ⠋ Configuring project...
2023-09-26T17:45:58.873058Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#051eb7e3da0ffef00efcb2f58096d932, remote: 0#d55fd0f740937755fb0db17ed166de34
     ⠦ Configuring project...
2023-09-26T17:46:09.124611Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#20075f8ee6fb3e255aa725dadec893f5' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: c1c98c0c0d45a9085a36f5320da66894, spawner_flow_control_id: None }
     ⠧ Configuring project...
2023-09-26T17:46:09.190767Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#8526e258fb262077220bdb8242ad7da9, remote: 0#a09944f567744ca82a4ae36a472594e3
     ⠧ Configuring project...
2023-09-26T17:46:14.437343Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#e01d1849c66dfa39e2580b3cdb4d4662' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: bd0a48e6fa1a423afbd669c683292008, spawner_flow_control_id: None }
     ⠇ Configuring project...
2023-09-26T17:46:14.499739Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#ff9e27d88d8893bb3123d7bba781d9f0, remote: 0#fdcf089da97eb1ff99506b355f63a9df
2023-09-26T17:46:14.685080Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/project"
2023-09-26T17:46:14.685108Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/projects/default.json"
     ⠙ Waiting for project to be ready...
2023-09-26T17:46:14.685268Z  INFO ockam_api::cli_state::traits: Set default item name=default
2023-09-26T17:46:14.753899Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#9503db28ec9b6fa4a14d251e4c2691f7' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: 8c2fd001a9e6be81b47f6440141b6332, spawner_flow_control_id: None }
     ⠹ Waiting for project to be ready...
2023-09-26T17:46:14.816951Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#e46cd0077425bb4ff2b08a6347c089f5, remote: 0#b692f9071b9c3be4154732bfc53e7d9e
     ⠦ Establishing secure channel to project...
2023-09-26T17:46:15.165839Z  INFO ockam_api::nodes::service::secure_channel: Handling request to create a new secure channel: /dnsaddr/k8s-hub-nginxing-2df5f8bd32-50456abbf63cd63c.elb.us-west-1.amazonaws.com/tcp/4005/service/api
     ⠧ Establishing secure channel to project...
2023-09-26T17:46:15.243748Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#20180121e97742ed9e3c11c6a6cb087b' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: c3ce1b42fe559875422859009896d09e, spawner_flow_control_id: None }
     ⠇ Establishing secure channel to project...
2023-09-26T17:46:15.312327Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#03d4ead31f90bfd2d0604ee49f2983a0, remote: 0#6cd0b06e3d3c813196465f2073c06818
2023-09-26T17:46:15.312785Z  INFO ockam_api::nodes::service::secure_channel: Handling request to delete secure channel addr=0#03d4ead31f90bfd2d0604ee49f2983a0
     ⠇ Establishing secure channel to project authority...
2023-09-26T17:46:15.313120Z  INFO ockam_api::nodes::service::secure_channel: Handling request to create a new secure channel: /dnsaddr/k8s-hub-nginxing-2df5f8bd32-50456abbf63cd63c.elb.us-west-1.amazonaws.com/tcp/4006/service/api
     ⠋ Establishing secure channel to project authority...
2023-09-26T17:46:15.378630Z  INFO ockam_node::processor_builder: Initializing ockam processor '0#c77750f44d7b51477f279db3cfa48d65' with access control in:DenyAll out:FlowControlOutgoingAccessControl { flow_control_id: c524be8fb12c1d9d340ac1cfe23ac0b1, spawner_flow_control_id: None }
     ⠙ Establishing secure channel to project authority...
2023-09-26T17:46:15.442856Z  INFO ockam_identity::secure_channel::handshake::handshake_worker: Initialized SecureChannel initiator at local: 0#12e749fca29619a47386ee003046ed33, remote: 0#e653a4aa1f61fcb0b4ae6e047c905dd8
2023-09-26T17:46:15.443819Z  INFO ockam_api::nodes::service::secure_channel: Handling request to delete secure channel addr=0#12e749fca29619a47386ee003046ed33
     ✔ Marked this project as your default project, on this machine.

2023-09-26T17:46:15.447440Z  INFO ockam_api::cli_state::traits: removing link "/Users/me/.ockam/defaults/trust_context"
2023-09-26T17:46:15.447453Z  INFO ockam_api::cli_state::traits: symlink to "/Users/me/.ockam/trust_contexts/default.json"
2023-09-26T17:46:15.447495Z  INFO ockam_api::cli_state::traits: Set default item name=default
2023-09-26T17:46:15.447930Z  INFO ockam_command::enroll::command: Retrieved the user default project Project { id: "532594d0-8c58-4102-94bf-c622d46db59b", name: "default", space_name: "012772b9", access_route: "/dnsaddr/k8s-hub-nginxing-2df5f8bd32-50456abbf63cd63c.elb.us-west-1.amazonaws.com/tcp/4005/service/api", users: [], space_id: "a4c4fa0c-8fc3-4acf-b1bd-47cf893e9e5b", identity: Some(Identifier([49, 73, 101, 144, 39, 37, 156, 50, 179, 77, 12, 186, 250, 76, 115, 4, 250, 121, 118, 11])), authority_access_route: Some("/dnsaddr/k8s-hub-nginxing-2df5f8bd32-50456abbf63cd63c.elb.us-west-1.amazonaws.com/tcp/4006/service/api"), authority_identity: Some("81a201583ba20101025835a4028201815820e5cc957f047112891b172f2887d8d34bfe759f548092060c5cef7858483f38dc03f4041a6513188f051a77df1b8f028201815840f737edb3caf941ca8aec583f60acac3d225402a6df6c1631bd333525c54542c5cee1c566751f409b9a54990638a2cf5ce015552a18b0fbe2402313710017db0b"), okta_config: None, confluent_config: None, version: Some("0.4.0"), running: Some(true), operation_id: None, user_roles: [ProjectUserRole { email<EMAIL_ADDRESS>id: 503, role: Admin, scope: Space }] }
2023-09-26T17:46:15.449398Z  INFO ockam_command::enroll::command: Enrolled a user with the Identifier I503c97350dbf052195ac3e5da2fb4d965bd7f118
2023-09-26T17:46:15.449498Z  INFO ockam_api::cli_state::nodes: node process killed name=523b53ec
     ✔ Enrolled I503c97350dbf052195ac3e5da2fb4d965bd7f118 as one of the Ockam identities of your Orchestrator account<EMAIL_ADDRESS>2023-09-26T17:46:15.450153Z  INFO ockam_api::cli_state::nodes: node deleted name=523b53ec
2023-09-26T17:46:15.450498Z  INFO ockam_node::router::shutdown: Initiate graceful node shutdown
2023-09-26T17:46:15.453971Z  INFO ockam_node::router: No more workers left.  Goodbye!

Ockam Version
0.94.0

@lordB8r Thank you for reporting this. Very helpful in refining the experience.

I was going to take a stab at fixing this today.

@nazmulidris @mrinalwadhwa
Hello there!
Could you assign this issue to me?

@gushul That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.ockam.io


[Docs] Adding a missing "This" and attempt to add clarity with less pronouns.

I agree, I like it, thanks


Right to left writing “say” “Arabic support”

Request on forum for right-to-left language support.

I took a look into this. It's doable, up to the point where you want RTL text to wrap correctly across multiple lines - then it gets tricky. To do it right I think you would need to modify Unity's Text class to support this properly. https://bitbucket.org/Unity-Technologies/ui

The asset mentioned before is now open sourced :
https://github.com/Konash/arabic-support-unity


Support for FreeBSD platform and minor fixes

It would be nice to make the module more versatile to expand the number of distributions.
Tested with: FreeBSD 12.2-RELEASE, FreeBSD 13-ALPHA1

Thanks! Looks good.
We switched to Github Actions recently and apparently the tests didn't run. I'd like to get that fixed before merging it so we know nothing else broke.

Thanks! Looks good.
We switched to Github Actions recently and apparently the tests didn't run. I'd like to get that fixed before merging it so we know nothing else broke.

I can't find how on earth I have to fix it so the tests work. I will merge this, the tests will run then.
If anything breaks, please help 😄

I can't find how on earth I have to fix it so the tests work. I will merge this, the tests will run then.
If anything breaks, please help 😄

Ok, so this PR wasn't ready. It pretty much destroyed our tests. There was a variable missing and the code didn't follow the standard Puppet style guide. I'm close to fixing everything but should you have other changes in the future, please, please, please test them. Make sure you're not only fixing your use case but also aren't destroying other use cases.
Either way, thanks for the PR! It's still cool to have some support for FreeBSD. I'm not marking it as fully supported yet though because there are no tests for it.

Ok, so this PR wasn't ready. It pretty much destroyed our tests. There was a variable missing and the code didn't follow the standard Puppet style guide. I'm close to fixing everything but should you have other changes in the future, please, please, please test them. Make sure you're not only fixing your use case but also aren't destroying other use cases.
Either way, thanks for the PR! It's still cool to have some support for FreeBSD. I'm not marking it as fully supported yet though because there are no tests for it.

There was a variable missing and the code didn't follow the standard Puppet style guide.

Sorry i didn't notice regression through lint. Do you see errors through the PDK ?
I plan to use the module extensively, I am interested in contributing it. Thank you.

There was a variable missing and the code didn't follow the standard Puppet style guide.

Sorry i didn't notice regression through lint. Do you see errors through the PDK ?
I plan to use the module extensively, I am interested in contributing it. Thank you.

We're testing with bundle exec rake test. I think you can find most of it in the lower end of our README.
It initially errored out on the indentation of some resources you changed, you can see the test results here:
https://github.com/sensson/puppet-powerdns/runs/1753322003?check_suite_focus=true
Once this was fixed, it failed entirely because you didn't include a default for mysql_backend_package_name . You did switch some resources over to use this variable, but not a single OS was configured with it. It took me a while to find it, because it failed on completely different resources.
After fixing that too, it failed on the change you made in sqlite3. You use env to find the binary, but there is a test that checks what command is used, so that test failed too.

We're testing with bundle exec rake test. I think you can find most of it in the lower end of our README.
It initially errored out on the indentation of some resources you changed, you can see the test results here:
https://github.com/sensson/puppet-powerdns/runs/1753322003?check_suite_focus=true
Once this was fixed, it failed entirely because you didn't include a default for mysql_backend_package_name . You did switch some resources over to use this variable, but not a single OS was configured with it. It took me a while to find it, because it failed on completely different resources.
After fixing that too, it failed on the change you made in sqlite3. You use env to find the binary, but there is a test that checks what command is used, so that test failed too.

Got it. thank you. This was not done on purpose, unfortunately, I did not know.

Got it. thank you. This was not done on purpose, unfortunately, I did not know.

No worries. Still cool to have support for FreeBSD. If you can add some specific tests for FreeBSD that would be great. Note that this PR is merged now, so adding support for it should be done in a new PR.

No worries. Still cool to have support for FreeBSD. If you can add some specific tests for FreeBSD that would be great. Note that this PR is merged now, so adding support for it should be done in a new PR.


Add dailymail.co.uk to fake news list

The website has been demonstrating itself as a questionable source of information. As such, it needs to be added to the list.
Source: https://mediabiasfactcheck.com/daily-mail/

Thank you for this Anna @a2937.
Ping Mark @marktron for consideration and possible inclusion.


Integration in Home assistant?

Will the new API allow an new integration in Home Assistant without the need of using homebridge?

Hi @cboch - thanks for the feedback!  The current version of the API doesn't enable a new integration in Home Assistant without the use of Homebridge, but we will look into it and hope to add that feature in the future.

Hi @cboch - thanks for the feedback!  The current version of the API doesn't enable a new integration in Home Assistant without the use of Homebridge, but we will look into it and hope to add that feature in the future.

Sad to see the old api being deprecated, I had a perfectly working setup in home assistant.
I really hope this will be worked upon soon

Time is soon running out... Please provide an integration in Home assistant or a HomeKit compatible device otherwise I will soon switch to a concurrent device.

Hi, meanwhile, a workaround is to use HomeAssistant's new Homekit integration, as well as Homebridge and this plugin. However, you must change the mDNS Advertiser setting to Ciao, upper right corner, three dots -> Homebridge Settings.

Crap locks just go with something proper instead.
I recommend yale Linus and yale doorman

I would say that I almost agree since they only suggest developing new features (HomeKit or integration in Home assistant) but after 3-4 years it never came out. I will never buy again this lock neither. I got it for free and that is why I keep it.

I wonder what is going on with their support. Submitted query to reset my 10 Api keys, still no response, despite repeated attempts