Add service button issue (torrents module)

Environment
Docker
Version
0.10.0
Describe the problem
When torrents module is enabled, clicking on some parts of the "Add Service" button will open torrent module's settings instead of opening "add service" popup. The affected area is mostly center.
Additional info
Video:
https://user-images.githubusercontent.com/56438628/188941400-9fb4d867-c30d-4e0b-b30a-8b47dd70e0d7.mp4
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

I can verify that I have this issue in 0.10 too. This was not introduced with the latest update from 0.9 and has probably been around in Homarr for quite some while.

don't really know how it happens. What browser / os are you using ?

don't really know how it happens. What browser / os are you using ?

Chrome on win10. I don't have this problem on Android (also chrome)

So I've been trying to pin down the issue with this. I have a suspicion what the problem could be, but wasn't able to verify it yet.
My investigation

Usually, Menu or Popovers require some sort of anchor element, to determine their position.
The issue only seems to occur on the torrent module. There is not much special about this module.
The issue occurs only occasionally on specific screen sizes. I verified that I got the issue on both Chrome, Firefox and Edge. I have the most issues with it on my touch laptop?

My suspicion
I think, that the problem lies within this line:
https://github.com/ajnart/homarr/blob/master/src/modules/moduleWrapper.tsx#L207
Why? I think this line causes the issue, because it acts as the anchor for the dropdown position.
Lowercase components in React are quite unusual. But perhaps this library is also doing some funky useMemo / state stuff, which breaks the <Menu.Target/>? We could try to wrap the <motion.div> in a <div /> to verify this theory.

@pacjo sorry for the late reply. Do you still have this issue happening on latest ? I have still not been able to replicate it

So I've been trying to pin down the issue with this. I have a suspicion what the problem could be, but wasn't able to verify it yet.
My investigation
* Usually, Menu or Popovers require some sort of anchor element, to determine their position.

* The issue only seems to occur on the torrent module. There is not much special about this module.

* The issue occurs only occasionally on specific screen sizes. I verified that I got the issue on both Chrome, Firefox and Edge. I have the most issues with it on my touch laptop?

My suspicion I think, that the problem lies within this line: https://github.com/ajnart/homarr/blob/master/src/modules/moduleWrapper.tsx#L207
Why? I think this line causes the issue, because it acts as the anchor for the dropdown position. Lowercase components in React are quite unusual. But perhaps this library is also doing some funky useMemo / state stuff, which breaks the <Menu.Target/>? We could try to wrap the <motion.div> in a <div /> to verify this theory.
Weirdly, it almost never happens on my high end desktop pc, so I wonder if it has to do something with the CPU / IO load.

Might be the Menu target. I'll investigate it. It might be due to the absolute positioning breaking on slow JS loads. No clue

Latest didn't fix it.

Okay, thanks for confirming

Ok, so I figured it out. Solution was actually pretty simple. I'll push a branch very soon. @pacjo would you be able to test out on a test docker image, to confirm that it was fixed?

Sure, just let me know, when you're ready.

Can you test, if this fixes it? I forgot that GitHub Actions workflows do not work with forks, so you'll have to clone the project and run it manually. Is this okay for you?

I've cloned the project and it seems to run, but I can't access it from another device (my pc, as I run in on headless server).
is it the intended behavior? I've never used yarn before.
logs:
kamil@kronos:~/homarr$ HOST=<IP_ADDRESS> yarn start
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
warn  - You have enabled experimental feature(s).
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use them at your own risk.

kamil@kronos:~/homarr$

Yes, those warnings are expected behavior and can be ignored. Would you be able to run it on the server where you normally run Homarr, if I build a docker image?

Would you be able to run it on the server where you normally run Homarr, if I build a docker image?

Sure

Done. Make sure that you pull this image:
https://github.com/ajnart/homarr/pkgs/container/homarr/45925518?tag=test-absolute-position-torrents-menu

That fixed it.


Not loaded issue

Xiaomi Miot Auto
Not loaded
can't see data anymore

Any error/warning logs ?

https://github.com/al-one/hass-xiaomi-miot#installing

Error
Config flow could not be loaded: undefined
when trying to install from integration

It's working great work!

how can i add Mi 360 Webcam Camera Control video support?

how can i add Mi 360 Webcam Camera Control video support?

Unsupported.

@MiAutomations Upgrade to latest release version.

a

@al-one I'm currently using the last one available over the hacs v1.4.1
What is the last one mentioned by you?
Thank you

@MiAutomations


Fixed resource type for VMSS recommendation.

Overview/Summary
Fixed wrong resourceType reference for VMSS recommendation.
Related Issues/Work Items
Fixed wrong resourceType reference for VMSS recommendation.
This PR fixes/adds/changes/removes

Fix resourceType for VMSS recommendation.

As part of this pull request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[x] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Ensured PR tests are passing
[x] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
[x] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Thanks, @michielvanschaik

@michielvanschaik I'm a bit confused by this PR.
It looks as though the recommendation with aprlGuid df0ff862-814d-45a3-95e4-4fad5a244ba6 exists in both Microsoft.Compute/virtualMachines and Microsoft.Compute/virtualMachineScaleSets. I'm not sure when this recommendation was duplicated, but we should fix that problem. The ARG query runs against Microsoft.Compute/virtualMachines so that seems to be the appropriate place for the recommendation.
I think we need to remove the duplicate recommendation from Microsoft.Compute/virtualMachineScalesets and leave the kql file in its current location.
It is also unclear why the 1074f391-22bf-42f5-9c95-68af5ad89bf6.kql file is being deleted. Was the recommendation previously removed?

@ejhenry , I guess the issue is #171 and proposed fix is #172

Closing this PR as the VMSS recommendation with aprlGuid df0ff862-814d-45a3-95e4-4fad5a244ba6 was a duplicate of a VM recommendation with the same aprlGuid. The duplicate VMSS recommendation has been removed in #172.


Change base64 encoded callback URL to plain text on the clients QR code

At the moment, the readme has uses Base64 encoding on the claims URL.  Make it more readable and thus more secure by making it plain text.
https://github.com/dltxio/idem-mobile/blob/main/README.md
Current: did://callback=ZGVtby5pZGVtLmNvbS5hdS92ZXJpZnk=?nonce=8b5c66c0-bceb-40b4-b099-d31b127bf7b3&claims=EmailCredential,NameCredential
Expected: did://callback=https://demo.idem.com.au/verify=?nonce=8b5c66c0-bceb-40b4-b099-d31b127bf7b3&claims=EmailCredential,NameCredentia

Issue is unclear whether this is this just updating the readme or changing the functionality in the app?

App too.  Need to test with a QR code where the query string call back is plain text.

Can't test: https://dltxworkspace.slack.com/archives/C01H0NYBBQW/p1654071541354199?thread_ts=1654071297.235279&cid=C01H0NYBBQW


Create Hari

simple interst calculate

@itzme-hari18 you don't have to commit the solution here. I will close this PR.


Qa

Coverage increased (+0.03%) to 85.439% when pulling 38c834425030013151edacf14ba9c411747374b6 on qa into 6fdfb44a8bf6b517a18b17754aa0dfd457b25b75 on master.


Update to Django 3.2.11

Fixes #2523

Django Form Fields are no more Orderdict in Django3.0 because of python versions.  As it is explained here https://groups.google.com/g/django-developers/c/zL_eMRHanE4. So, we can't use move_to_end method here and many other places.
We got two options, either we change back the fields from dict to Orderdict(in forms init method) or we need to define the field_order so that we can move a field to end of dict.
Which option seem better to you all?
In my opinion, we may use Orderdict because python dict already introduced reversed method and I think it may have move_to_end soon?

Update: Form fields dict has converted back to OrderedDict at a few places. It seems working fine. Some tests were giving errors due to the query crashes with Django3.0 that has been fixed in 3.0.2 and further. So, I upgrade it to 3.0.14.
Now only one test is failing, its executed query number is lesser than expected.

Codecov Report

Merging #2678 (2d3f1fb) into main (591f2c3) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2678   +/-   ##
=======================================
  Coverage   80.63%   80.63%
=======================================
  Files         651      651
  Lines       23189    23194    +5
=======================================
+ Hits        18698    18703    +5
  Misses       4491     4491

Impacted Files
Coverage Δ

hypha/apply/determinations/forms.py
76.00% <100.00%> (+0.26%)
:arrow_up:

hypha/apply/funds/forms.py
87.54% <100.00%> (+0.09%)
:arrow_up:

hypha/apply/funds/tests/test_forms.py
98.18% <100.00%> (ø)

hypha/apply/funds/widgets.py
69.56% <100.00%> (ø)

hypha/apply/stream_forms/fields.py
95.65% <100.00%> (ø)

hypha/public/people/wagtail_hooks.py
83.33% <100.00%> (ø)

hypha/public/utils/wagtail_hooks.py
88.88% <100.00%> (ø)

Continue to review full report at Codecov.

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

Do not merge this PR for now
I am working on its testing part and I found something interesting, I'll share it soon. Until then don't merge this PR.

Happy that this is on the way! This will allow us to update to latest Wagtail as well..

This PR is now ready to review and merge.
There was an issue in initializing a Form with an updated Django version.
Problem:  Model Form's fields were not getting initialized for fields as empty list[]. Because of uninitialised form, we were short of 4 queries in ReviewerFormQueries Test.
Reason: They particularly changed this behavior of forms's model_to_dict method with this commit.
Solution:

We change the number of queries in our test. - I discussed this with @sks444 and we decided not to change our tests.
We use a custom duplicate model_to_dict method to initialize the form with the same data and same number of queries.

For now, I have implemented the second method.  Please feel free to share your suggestions.

We will not deploy this to main branch until we are all the way to 3.2 since other versions between 2.2 and 3.2 are not supported.

@frjo We already have draft PRs for 3.1 and 3.2 which worked well for me. Let me push the other changes here in a single place(PR).

I have pushed the changes for 3.2.  But there is still a warning to set the default auto field for some models. Let me fix that first.

@frjo This PR is ready to review now. I have updated it to 3.2.11 and also resolved all warnings.

@sandeepsajan0 I needed to revert your merge. We have updated to node 16 that use a new format for the package-lock.json file.


Event specific background colors

Apologies in advance, I already know that this is a repeat/duplicate issue, however I'm not sure if the previous advice/codepen still applies following the changes for v2.0 onwards?
I've followed the previous discussion in #115  Similar to that issue, I'm looking to pass through a background colour alongside the event. I've tried to follow the example code-pen that was mentioned there, but being fairly new to vue, I'm struggling to get something that's actually working - and I'm using the typical template syntax rather than the provided pug format.
Following between a few different examples here and there I got to the below, which renders and looks like it did before I tried to override the template, but I'm pretty sure I've put the styling in the wrong place (and probably did some other things I shouldn't)
In the code-pen I saw a div with the event-content class being used, but introducing that div applied the styling too late i.e. inside the div I actually want to style.
This is what I've currently got
<template>

        <vue-cal
            :hide-title-bar="true"
            :hide-view-selector="true"
            :click-to-navigate="false"
            :dblclick-to-navigate="false"
            :time-from="8 * 60"
            :time-to="19 * 60"
            :time-step="60"
            :events="events"
            @ready="fetchEvents"
            @view-change="fetchEvents"
            style="height: 500px">
            <template v-slot:event-renderer="{ event, view }" :style="{ backgroundColor: event.color }">
                <v-icon>{{ event.icon }}</v-icon>

                    {{ event.start.substr(11,5) }}
                     - {{ event.end.substr(11,5) }}

            </template>
        </vue-cal>

</template>

Ideally I'd also like to be able to make use of the formatTime function that I've seen being used  (rather than using substr), but so far I've not been able to use in in the above context - again probably something really simple that I've probably over-complicated.
I hope that in the future this could eventually be supported natively by the component, as it doesn't feel like event specific colouring is that unusual of a use-case, although I respect the decision that has made.

Hi @Rjs37,
The Codepen example given in #115 is still accurate I updated it after the v2 release with the new slots syntax.
https://codepen.io/antoniandre/pen/XwNdQz?editors=1010
From this Pug markup, in template(slot="event-renderer" slot-scope="{ event, view }"), the template tag does not create an html tag, so putting a style on it won't work and it will be lost.
That's why you should add a div with a class inside, like div.event-content so that you can apply extra not-inline CSS style.
The content-renderer does not allow you to modify the root event container .vuecal__event, as you say it is one level deeper, so all the style the you wanted to be on the .vuecal__event element should be placed on .event-content if it has to be dynamic style, and if you need an extra wrapper you can put it inside it.
Regarding the formatDate and formatTime methods, I have updated the Codepen to show how to do it. For information, it will use the format you have set in vue-cal by default (twelve-hour or not) but you can still override it if you want.
formatTime(minutes) // Uses the default format.
formatTime(minutes, 'hh:mm') // You can pass the format you want.

And for the last thing:

I hope that in the future this could eventually be supported natively by the component, as it doesn't feel like event specific colouring is that unusual of a use-case, although I respect the decision that has made.

It will not change in a near future, I don't think vue-cal should carry styles in the internal logic as the end user has a way to apply it as they want through renderers. If we were to add background color then why not bold, uppercase, border, box shadow, or anything that should be treated case by case outside of vue-cal.
I hope it makes sense for you and helps understanding.

Cheers for the very quick response!
That worked a treat, in both cases. Slowly but surely understanding more about how to use Vue in the right way :+1:


makeDraggable not present in mxUtils

Trying to make some drag feature but makeDraggable which I need don't seem to be present in the typing ?
Documentation link

The mxgraph typings are borrowed from https://github.com/lgleim/mxgraph-typings and it will be great if any missing pieces are applied there first.
The particular mxDraggable method belongs to mxUtils which is of type any. You should be able to use it but it won't give you any type safety.

I see, this part is really time consuming.
Thanks for the info, for me this issue is closed. Or maybe let it open for hypothetical future updates


[docs]: Create Deprecation page per deprecation group

This is a rough POC to see if it works for our purpose to improve the deprecation messages.
Text might need some improvement/additional information
@benlesh @cartant

Fixed some typos that were pointed out above and rebased onto master.
There are some deprecation messages that still include the {@ ... } markup that's discussed here. IMO, it would be best to remove these ATM, as they clutter the output in VS code and on the command line. Apart from that, this LGTM and, IMO, improvements regarding the deprecations need to be incorporated into the current v6 docs ASAP.

FWIW, we really should try to get the deprecation messages sorted before this lands:
https://mobile.twitter.com/WenluWang/status/1275458404132073473
We should really fix them in v6 too, as people are going to be using that for a while in Angular, etc.


Add files via upload

A python code for declaring and traversing a linked list.

Try adding an appropriate title next time


JAMES-3225 configures CI for builds.apache.org

As an individual contributor I prefer having slow CI builds than no CI
builds at all. This commit introduces a minimal JenkinsFile to be
further refined.
I was shamelessly adapted from the activemq project's
JenkinsFile
and the JenkinsFile
proposed in the gradle branch.

I intend to make a followup PR adding -T1C to the maven commands to try and speedup the build but I prefer to start with a simpler build :)

I checked and my intuition was correct, the builds don't trigger because I am (rightly ;) ) considered an untrusted source
Getting remote pull request #264...

    Checking pull request #264
    Checking pull request #264
    (not from a trusted source)
      ‘Jenkinsfile’ not found
    Does not meet criteria

  1 pull requests were processed

(source : https://builds.apache.org/job/james/job/ApacheJames/indexing/events)
I'm pretty sure the Jenkinsfile is there so I assume it gets filtered away because I'm not to be trusted. This means the Jenkinsfile has not even been linted for now. A maintainer will have to recreate/push the branch in its own repo or possibly in this repo and reopen a PR for it to be picked up

I have cleaned up and rebased the Jenkinsfile which seems to work in #265
there was an issue with the git describe which was disabled in 8880117 , I think that using the git describe --always is better than disabling the plugin entirely :
       --always
           Show uniquely abbreviated commit object as fallback.

it preserves the current behavior while providing a working fallback for PRs which seem to be tested in detached head mode. combined with the already present --dirty it should never fail. The only downside is that jars generated for these builds will not have useful version information but they are not published either.
Another solution could be to use profiles to only enable the plugin on master / selected branches ...

The CI builds are now reasonnably successful see https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/activity
The PR history is clean and it seems an admin enabled build for all PRs

test this please

\o/

According to https://issues.apache.org/jira/browse/INFRA-20673 and https://plugins.jenkins.io/pipeline-github/#issuecommenttrigger : test this please should work now
sorry to the participants for the extra notification

The latest crash is ... interesting : I have no idea what to do about it ...
[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 8. See FAQ web page and the dump file /home/jenkins/workspace/james_ApacheJames_PR-264/server/protocols/webadmin/webadmin-mailbox/target/surefire-reports/2021-01-07T12-25-01_355-jvmRun8.dumpstream

The latest crash is ... interesting : I have no idea what to do about it ...
[WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 8. See FAQ web page and the dump file /home/jenkins/workspace/james_ApacheJames_PR-264/server/protocols/webadmin/webadmin-mailbox/target/surefire-reports/2021-01-07T12-25-01_355-jvmRun8.dumpstream

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.007 s <<< FAILURE! - in org.apache.james.webadmin.routes.CassandraMappingsRoutesTest
[ERROR] org.apache.james.webadmin.routes.CassandraMappingsRoutesTest  Time elapsed: 6.007 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:2b4247eb252e9826687d0b7adb6d411963caad11295bc433e8fe3e8f5e714049"

Problem using docker
test this please

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.007 s <<< FAILURE! - in org.apache.james.webadmin.routes.CassandraMappingsRoutesTest
[ERROR] org.apache.james.webadmin.routes.CassandraMappingsRoutesTest  Time elapsed: 6.007 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:2b4247eb252e9826687d0b7adb6d411963caad11295bc433e8fe3e8f5e714049"

Problem using docker
test this please

I can't figure out what breaks.
test this please

I can't figure out what breaks.
test this please

12:26:17,264 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project james-server-data-cassandra: There was a timeout or other error in the fork -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project james-server-data-cassandra: There was a timeout or other error in the fork

12:26:17,264 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project james-server-data-cassandra: There was a timeout or other error in the fork -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project james-server-data-cassandra: There was a timeout or other error in the fork

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.468 s <<< FAILURE! - in org.apache.james.mailbox.cassandra.mail.CassandraMailboxCounterDAOTest
org.apache.james.mailbox.cassandra.mail.CassandraMailboxCounterDAOTest  Time elapsed: 6.468 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:8c0edf3bbb37eda4019a560c1a68292c991a9e493f74b47266f64d2caf19cd85"

Image caching is probably the root of our problem

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.468 s <<< FAILURE! - in org.apache.james.mailbox.cassandra.mail.CassandraMailboxCounterDAOTest
org.apache.james.mailbox.cassandra.mail.CassandraMailboxCounterDAOTest  Time elapsed: 6.468 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:8c0edf3bbb37eda4019a560c1a68292c991a9e493f74b47266f64d2caf19cd85"

Image caching is probably the root of our problem

org.apache.james.rrt.cassandra.CassandraRecipientRewriteTableV6Test  Time elapsed: 6.512 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:8825a65748992b57919e0610c7b43bb2431cf8467295962d32696af687417745"

org.apache.james.rrt.cassandra.CassandraRecipientRewriteTableV6Test  Time elapsed: 6.512 s  <<< ERROR!
java.lang.ExceptionInInitializerError
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=<resolving>, imagePullPolicy=DefaultPullPolicy())
Caused by: com.github.dockerjava.api.exception.DockerClientException: Could not build image: unable to find image "sha256:8825a65748992b57919e0610c7b43bb2431cf8467295962d32696af687417745"

After :

using a unique name for the cassandra singleton image to avoid clashes between parallel maven runs overwriting each other's docker cache
dropping fork reuse entirely to get rid of memory leaks inducing OutOfMemoryError: Direct buffer memory

last failure is :
23:31:06.935 [ERROR] ?.3.2] - Could not start container
java.lang.IllegalStateException: Container exited with code 1
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:469)
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:325)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:323)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311)
	at org.apache.james.linshare.Linshare.start(Linshare.java:71)
	at org.apache.james.linshare.LinshareSingleton.<clinit>(LinshareSingleton.java:27)
	at org.apache.james.linshare.LinshareExtension.<clinit>(LinshareExtension.java:62)
	at org.apache.james.modules.LinshareGuiceExtension.<init>(LinshareGuiceExtension.java:39)
	at org.apache.james.LinshareBlobExportMechanismProvidingTest.<clinit>(LinshareBlobExportMechanismProvidingTest.java:29)

23:31:06.973 [ERROR] ?.3.2] - Log output from the failed container:
wait-for-it.sh: waiting 15 seconds for ${LS_SERVER_HOST}:${LS_SERVER_PORT}
wait-for-it.sh: timeout occurred after waiting 15 seconds for ${LS_SERVER_HOST}:${LS_SERVER_PORT}
INFO:init.sh: Checking all required env variables...
LS_SERVER_HOST : backend
LS_SERVER_PORT : 8080
LS_LDAP_URL : ldap://ldap:389
LS_USER_URL : https://user.linshare.local
LS_EXTERNAL_URL : https://user.linshare.local
LS_PASSWORD : admi...
LS_NO_REPLY_ADDRESS<EMAIL_ADDRESS>INFO:init.sh: All env variables checked
INFO:init.sh: Checking all optional env variables...
LS_LDAP_DN : cn=linshare,dc=linshare,dc=org
LS_LDAP_PW : lins...
LS_LDAP_BASE_DN : ou=People,dc=linshare,dc=org
LS_LDAP_NAME : ldap-local
LS_FORCE_INIT : 0
LS_DOMAIN_PATTERN_NAME : openldap-local
LS_DOMAIN_PATTERN_MODEL : 868400c0-c12e-456a-8c3c-19e985290586
LS_EXTRA_INIT_SCRIPT :
LS_JWT_PUB_KEY : /linagora/data/public.pem
LS_JWT_PUB_KEY_NAME :
INFO:init.sh: All env variables checked
23:21:22 WARNING : Current password is not valid.
23:21:22 INFO    : Trying to authenticate with the new provided password
23:21:22 ERROR   : Can't update the current password.

Since Linshare is yet another singleton which generates a docker image, I'll try assigning it a unique image name just in case.
see you tonight for the results (build takes >6h)

11:02:45.062 [ERROR] o.a.j.u.c.ConcurrentTestRunner - Error caught during concurrent testing (iteration 0, threadNumber 9)
com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency SERIAL (1 responses were required but only 0 replica responded)
	at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:91)
	at com.datastax.driver.core.Responses$Error$1.decode(Responses.java:66)
	at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:297)
	at com.datastax.driver.core.Message$ProtocolDecoder.decode(Message.java:268)
	at com.datastax.shaded.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
	... 27 common frames omitted

full log at https://builds.apache.org/blue/rest/organizations/jenkins/pipelines/james/pipelines/ApacheJames/branches/PR-264/runs/43/nodes/86/log/?start=0&download=true

We finally got a green run : https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/51/pipeline
to get there we had to drop all attempts at parallelisation: no surefire-forks, no running jobs in parallel and be lucky not to be hit by the copy on write issue (see the detailed logs for  org.apache.james.smtp.SmtpRandomStoringTest and you will find the signature null pointer exception ```
15:53:44.340 [ERROR] o.a.j.t.m.d.MailDispatcher - Error While storing mail.
java.lang.NullPointerException: null
at org.apache.james.server.core.MimeMessageInputStream.(MimeMessageInputStream.java:63)
or by timeouts as in https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/50/tests

build 52 where I attempted to run test suites in parallel again failed with a linshare container initialization failure which had been [encountered before](https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/41/tests):

java.lang.ExceptionInInitializerError
at org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed
at org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
at org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
I started archiving the test-run.log on failure and logging as much test container related stuff as possible to have more details on such failures: it looks like the container fails to coordinate internally or maybe is killed during initialization by a timeout that is a bit too optimistic for the CI plateform ...  (the database receives a fast-shutdown command while it is apply migrations and the backend which is starting fails to connect)

03:59:52.056 [DEBUG] org.apache.james.linshare.Linshare -  COMMIT
03:59:52.105 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.155 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.222 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.271 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.345 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.397 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.455 [DEBUG] org.apache.james.linshare.Linshare -  CREATE VIEW
03:59:52.456 [DEBUG] org.apache.james.linshare.Linshare -
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -  LOG:  received fast shutdown request
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -  waiting for server to shut down...LOG:  aborting any active transactions
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -  .LOG:  autovacuum launcher shutting down
03:59:52.466 [DEBUG] org.apache.james.linshare.Linshare -  LOG:  shutting down
03:59:52.706 [DEBUG] org.apache.james.linshare.Linshare -  [WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006: Missing cache[default-update-timestamps-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
03:59:52.706 [DEBUG] o.t.c.output.WaitingConsumer - STDOUT: [WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006: Missing cache[default-update-timestamps-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.efault-query-results-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
03:59:52.737 [DEBUG] o.t.c.output.WaitingConsumer - STDOUT: [WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006: Missing cache[default-query-results-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'..ehcache.missing_cache_strategy' to 'create'.
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare -  06-Feb-2021 03:59:56.291 WARNING [localhost-startStop-1] org.postgresql.core.v3.ConnectionFactoryImpl.log ConnectException occurred while connecting to linshare_database:5432
03:59:56.296 [DEBUG] o.t.c.output.WaitingConsumer - STDERR:     java.net.ConnectException: Connection refused (Connection refused)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare -     java.net.ConnectException: Connection refused (Connection refused)
03:59:56.296 [DEBUG] o.t.c.output.WaitingConsumer - STDERR:             at org.hibernate.tool.schema.internal.exec.ImprovedExtractionContextImpl.getJdbcConnection(ImprovedExtractionContextImpl.java:60)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare -             at java.net.PlainSocketImpl.socketConnect(Native Method)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare -             at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)

I rebased on master it's building now

What are the build time statistic after these changes?

all parallelization optimizations have been disabled the last  the last successful build took 7 hours and 2 minutes

I guess we will then have discussions on how to make this build faster.
I see that JMAP draft integration tests takes quit a bunch of time. Do we really need them to run on top of both cassandra-guice and distributed james? (We could reclaim 1h of build time very easily there).
Maybe some features (LinShare for instance?) have little meaning in this Apache project and could be removed + maintained by third parties. Should we plan to audit such features?

I see that JMAP draft integration tests takes quit a bunch of time. Do we really need them to run on top of both cassandra-guice and distributed james? (We could reclaim 1h of build time very easily there).

I think I read in a discussion that JMAP draft was going to be dropped "soon" anyways which is why I didn't spend any time splitting this off.

I think I read in a discussion that JMAP draft was going to be dropped "soon" anyways which is why I didn't spend any time splitting this off.

Yes, we kinda finished implementing JMAP RFC-8621 - missing MDN support, but once done we should be ready for a deprecation/removal.

new successful build : https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/58/pipeline/ 7h10
build 57 failed because docker cassandra failed to start within 1 min, analysing the logs it actually took 1m10s to start
on my laptop (in an isolated case) the container started in 22 seconds.
curious I tried adding test steps to measure node performance,  sysbench  was an attempt with low probability but cpuinfo and free worked.
The compute node for 59 advertises 24 6-core Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz CPUs (cat /proc/cpu) and 94GB of RAM

Ok so the PR is green (sometimes) and the history is clean, would people agree I merge it on master ?

I do agree - hopefully we will quickly shorten the build time to make it less problematic.

MERGED :tada:

Congrats!
Now let's work together to get the build below 3h :-)


feat: added check in the validator for info section.

Validator will return an error if the info section is missing or filled out incorrectly.

:tada: This PR is included in version 0.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


measurementManager.registerSource Invalid scheme for app destination: https; dropping the source

Hi,
A register source endpoint had been defined at https://the_host_uri/endpoint_path?parameters
calling the registerSource attribution API as follows,
measurementManager.registerSource(attributionSourceUri, null, mCallback );
generated the exception:
2023-12-17 13:45:57.413 17656-17690 adservices com.google.android.adservices.api E Invalid scheme for app destination: https; dropping the source.
at times, this error is written as well:
AndroidRuntime com.google.android.adservices.api FATAL exception:
java.lang.ClassCastException: com.android.okhttp.internal.huc.HttpURLConnectionImpl cannot be cast to javax.net.ssl.HttpsURLConnection at com.android.adservices.service.measurement.MeasurementHttpClient.setup(MeasurementHttpClient.java:63) at com.android.adservices.service.measurement.registration.AsyncSourceFetcher.openUrl(AsyncSourceFetcher.java:705)
Please note:
the sdk project and taboola trc server are using javax.net.ssl.HttpsURLConnection
the request to the end point service is successful if sent from postman.
in case the endpoint service is a postman mock server, there is no error and registerSource is sent to the mock server.
I'd like to ask what is blocking the request from being sent to the actual endoint (not the mock server) and how it can be resolved.
Thanks !

As far as I understand, app destinations can only be specified with the android-app scheme which specifies a package name. Would that be possible for your use-case?
I don't have any insight into the bad cast problem though.
cc @arpanah @vikassahu29

Please use the web_destination field for specifying any websites you want use as destination. The destination field is used only for app destinations.
Documentation Reference

Thanks @vikassahu29, using the web_destination field did work for the app-to-web.


deprecated tags api get_discussions_by_xxx and follows api

I believe everybody using busy.org already noticed these problems. I initially thought these might be temporary, but maybe not. It is related to APIs no longer supported, described here: Upcoming Changes to api.steemit.com by @steemitdev on 12/01/2018. While they didn't specify the deadline, it seems the time has come :( So unless Steemit doesn't support them again, these problems will be permanent, so busy should change the code.
API changes are described the post in the above, and here is the main summary for busy:

get_discussions_by_xxx is no longer supported as tags API but as condenser API:  change tags_api => condenser_api
get_discussions_by_active is no longer supported at all
follows queries should also be used through hivemind condenser API.

May need to change at least these two files:

https://github.com/busyorg/busy/blob/develop/src/client/helpers/apiHelpers.js
https://github.com/busyorg/busy/blob/develop/src/client/steemAPI.js

Expected behavior

Blog, feed should be shown properly depending the option chosen.
Recommended posts should be shown.
Replies should be shown.
Follower/Following "should" be shown alphabetically (It was before. and steemit.com still does)

Actual behavior

Showing the same old posts again and again. sometimes random flash scrolling
Showing nothing (e.g., recommended posts/reblogged authors/replies)
Blog/Feed/Feed with tag (trending/created/active/hot)
Follower/Following users are shown in random order.

same posts, no reblogged authors, no recommended posts

There are 8 comments, but show nothing.

Followers/Following are shown in a random order (not alphabetically)

How to reproduce
They occur every time on all platforms(Win/MacOS/Android/iOS, every browser I tested)

Thanks for analysing the problem.
get_discussions_by_xxx methods are still supported, but they are served by different system. There were undocumented changes to the responses of those methods.
We didn't port our code to use api.steemitdev.com as per Steemit recommendation yet, but I regard Steemit approach to implementing those changes as unprofessional. They didn't specify what exactly would change, instead just requested us to try the new API and see ourselves what doesn't work because at some point in the future (that wasn't specified as well) your entire application might stop working.
We are trying to figure out what has changed now and fix those bugs.

Hi @Sekhmet, I'm the guy who left a comment about vote value before. Nice to see you again and thank you for your comment.
and sure, get_discussions_by_xxx is now supported by condenser api as I wroted. But get_discussions_by_active isn't ported. I've tested this.
I agree that they're unprofessional. They just suddenly pulled the plug yesterday (maybe unintentionally). I strongly agree that even the announcement is very unclear what's the real change. But we have no power but to follow their changes :( I already changed the code for my bot.
Since busy is quite intensively used, you may need to think a little bit more which option is the best. But I doubt that they supported them again in the previous way. You may need to prepare the changes. Thank you.
ps. Two suggestions after this turmoil. (not new ones but many people want)

edit for posts longer than 7 days
confirm for downvote to prevent mistake. (currently it's 100% downvoting without any confirmation)

Thank you!

I also added "follows api" is also not supported as hivemind. Currently busy is showing followings/follower in a random order (steemit.com show alphabetically as before). Of course this isn't urgent. Please fix feed/blog first. Thank you.

Sure, and I'm letting you know that, as you may have noticed, they're offering previous APIs again. Not sure if this is temporary or not. Better to be prepared eventually. Many thanks! I love busy! and busy voting :)


Logo not changed in the login/signup page

What's wrong with the existing documentation
The logo of swap reads is not changed in the login/signup page.
Add ScreenShots

I want to work on this issue under gssoc'24.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!
Make sure to attach before & after screenshots in your PR. Also, star the repo before working on it. While creating your PR, ensure you pull all existing changes beforehand to avoid conflicts.
Happy open-source contributing!


first draft of CR September 2024 workshop page

Compared to the previous workshop, I added the "Q&A helper" role. Its name and description may be need to be changed.
I added your names in some places, @bast and @rkdarst. Pls. let me know if you disagree.

I am happy to contribute to organization but organizers are you and Enrico? Or has this changed?

I am happy to contribute to organization but organizers are you and Enrico? Or has this changed?

It has not changed, but I though you may want credit for all the question answering.

@bast, should I remove your name from the organizers list? I will add Enrico's of course.

Updated PR with Radovan's name removed and added Enrico's.


ISSUE #5 solved

#5
ISSUE 5 SOLVED
requirements.txt created and shell scripting updated to run automatically run "pip3 install -r requirements "

!bounty 6


Not working with developer key!

The batch example: https://github.com/google/google-api-php-client/blob/master/examples/batch.php#L43 not working if the developer key is set but if commenting out then its working!
How is it like so?
If try to print the result then the error message in the array like so:
There is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your API key configuration if request from this IP or referer should be allowed.

But I should not have exceeded the quota.

This message is not about the quota, it's about the IP address you are making the request from.
Try whitelisting your requesting IP by editing your API Key where it says *Accept requests from these server IP addresses *:

The reason you can comment out the key is the Book API is public. However, you have a limited quota when accessing it this way, and will eventually receive a quota error without a key.

I see. I was using browser key instead of server key.

Yes, Google "what is my IP" and use that one.
On Wed, Feb 17, 2016 at 1:11 AM Sazzad Hossain Khan <
<EMAIL_ADDRESS>wrote:

I see. I was using browser key instead of server key.
—
Reply to this email directly or view it on GitHub
https://github.com/google/google-api-php-client/issues/856#issuecomment-185107592
.

... Assuming your application is running on your local machine.


Standalone app & docker image

Hi again Oleg,
I found your tool very useful indeed; it even changed how I see GraphiQL in my workflow. Initially, any new GraphQL server I created had /graphql and /graphiql endpoints, but now I see this an anti-pattern. The main reason is that not every GraphQL server in my team may be written in JS, plus there is also a problem of updating all these copies and carrying lots of identical dependencies around. Using just one GraphiQL tool at a fixed url and saving/loading its state looks much more universal! This reminds me of redux-devtools, which once were commonly placed into every new React app but then moved to a Chrome extension.
I made a standalone copy of graphiql-workspace, which is basically an instance of create-react-app with only one component. The app can be shipped as a pretty lightweight docker container (< 20MB!), which makes it extremely easy to launch at https://graphiql.yourcompany.com (this may be viewed as a slightly safer option than running a public copy, plus cors in graphql endpoints may be easier to setup).
I uploaded the result to GtiLab, here's the URL: https://gitlab.com/kachkaev/graphiql-workspace-app
Feel free to share the link if you want and thanks again for your great work on bringing GraphiQL to a new level!

This sounds awesome!! I would be great if you can create a PR to update README and include this info (in this repo). I think it would be interesting for many people!
Maybe a "Community" section at the bottom. Then I can also add my graphql-toolbox there as well.


added iron-iconset-svg dependency to bower.json

fixes #23
app-datepicker.html
imports app-datepicker-icons.html
which imports iron-iconset-svg.html
however iron-iconset-svg.html was missing from bower.json

@HaykoKoryun LGTM.


Add newline before command categories

The simple formatting change adds a nice blank line before each command
category.  Documentation in README.md is also updated to be more
accurate.

:+1: thanks!


Save settings for multiple servers

One thing that I wish the official client had is an easy way to switch between servers. After server settings are saved, it should appear in a drop down in the log in screen.

This issue appears to be closed, the login screen contains a server list dropdown atleast.


just incase (spawns a cube instead of pistol model should we be unable to load the model)

Im doing a refactor /combat to get it ready for the presentation. We can add this later. closing to stop merge conflict.


Delete pod_cache and rely on updating pod status by kublet.

@davidopp @bgrant0607 @lavalamp
This fixes #2947. It is also related to #2726

LGTM
Am I correct in understanding that this is the last in the following sequence of PRs: #5205, #5555, #5624?

Please check/fix test issue. (Shippable failed, Travis is just very slow right now.)

@davidopp Yes, this is the last PR in the sequence (except that I think you've meant #5714 not #5624)
I checked shippable and it failed on some initial step not related with kubernetes itself (docker pull). I have restarted it - hopefully it'll be green this time.

One of the shippable runs failed, the other succeeded. Looks like a flake, but I'll take a look tomorrow.

FYI @bprashanth

Rebased. e2e test passes.

It seems there is a bug in integration tests #5872. I'm sending a separate PR to fix it.


Possible wrong Coud-Init network-config generated file

What steps did you take and what happened:
Sorry I submit this as a bug, but maybe it isn't.
When deploying a cluster with Talos as provider for bootstrap and controlplane, Talos' init process finds a cloud-init drive, but then complains about network-config file. Talos' error says: "network-config metadata version=0 is not supported", maybe because it starts with "network:". Is it supported? Reading the manual, it shouldn't.
cloud-init manual
What did you expect to happen:
Maybe cluster deployment should generate a network-config file starting without a top level "network:".
Environment:

Cluster-api-provider-proxmox version: 0.1.0
Kubernetes version: (use kubectl version): 1.28.3
OS (e.g. from /etc/os-release): Talos 1.5.5

@ricottatosta
As I can see, you're trying to use Talos as a control and bootstrap provider.
It's recommended that you submit this issue in talos-control-plane-provider

Thanks for changing my submission with type 'support'.
The issue involves cidata.iso created by capmox to pass configuration via cloud-init, and talos vm boot image that uses it at boot time.
Or am I supposed to believe that Talos bootstrap and controlplane are involved in creating cidata.iso?
Maybe the issue should be submitted in "talos os".

Hmmm,
CAPMOX Now only creates data supported by Debian and Ubuntu distributions.
If it's related to supporting Talos Cloud-init, you're right.
I don't know how Talos load the cloud-init iso,
If you know something, I can help you add support for Talos.

As far as I know, Talos expects cloud-init datasource to be in "nocloud" format. In this format, network-config file can't start with "network:".
Because of the presence of "network:", Talos doesn't find the top level key "version: 2" and assumes it to be "version: 0".
I can do nothing, that's the way you build cidata.iso and depends on how cloud-init expects data to be arranged in distributions like Debian and Ubuntu. You should find a way, either arranging data in a way that is good for all situations or let the user choose what kind of datasource format to produce in cidata.iso.
I know this means more effort. But I think Talos and CAPMOX are great together.

A couple of usefull links:
Talos NoCloud
Cloud-Init NoCloud datasource

Will check this out

This is the console output of Talos NoCloud booting image regarding the issue:
[talos] found config disk (cidata) at /dev/sr0
ISO 9660 Extensions: IEEE_P1282
[talos] fetching meta config from: cidata/meta-data
[talos] fetching network config from: cidata/network-config
[talos] fetching machine config from: cidata/user-data
[talos] restarting platform network config {"component": "controller-runtime", "controller": "network.PlatformConfigController", ..., "error": "network-config metadata version=0 is not supported"}

I will check this if it works with other netplans distros, and then I will implement it

I'm really looking forward to hearing good news from you.

I will test it on ubuntu but can you tested on Talos,

What am I supposed to test? Release 0.1.1?
Does it contains any changes in the code involved in the issue?

Currently, we support only Netplan-based distros,
We will try to add more support for other network-configs.
If someone wants to take effort and add this, it will be great.

OK. It was expected.
Unfortunately I'm not good at programming in Go. And  the solution I found out is not suitable for being integrated in your code.
As my solution is quite simple (just delete a bunch of characters from a template string), I'll patch your code every time you release a new version.
Thank you for your support.

We will try to support this soon.

I would like to share my experience about using CAPMOX with TALOS.
This is the template I use in pkg/cloudinit/network.go:
const ( 	/* network-config template. */ 	networkConfigTPl = version: 2
ethernets:
{{- range $index, $element := .NetworkConfigData }}
eth{{ $index }}:
match:
macaddress: {{ $element.MacAddress }}
dhcp4: false
addresses:
{{- if $element.IPAddress }}
- {{ $element.IPAddress }}
{{- end }}
{{- if $element.IPV6Address }}
- {{ $element.IPV6Address }}
{{- end }}
{{- if eq $index 0 }}
{{- if $element.Gateway }}
gateway4: {{ $element.Gateway }}
{{- end }}
{{- if $element.Gateway6 }}
gateway6: {{ $element.Gateway6 }}
{{- end }}
{{- if $element.DNSServers }}
nameservers:
addresses:
{{- range $element.DNSServers }}
- {{ . }}
{{- end -}}
{{- end -}}
{{- end -}}
{{- end -}}
TALOS dislikes defining static routes in place of gateways and perhaps even defining nameservers for each device.
For the rest, it works like a charm.

Thanks for sharing,
I guess the best solution for this is to support another version of network-config thats actually different from the netplan config.

We have released a new version.

I'm trying to make nocloud template string work like the netplan one as much as possible. But there is an issue.
If I omit to define a gateway, the injector refuse to build the cloudinit image complaining it wants it.
There is a way to define only address and netmask for a network device?

I will create new issue, so we can take this as a feature to support multiple cloud-init network-config.
However, DHCP will be included in the next release, i don't know if that helps you.

Issue is added
https://github.com/ionos-cloud/cluster-api-provider-proxmox/issues/94

I have been trying to get the talos bootstrap provider and proxmox infrastructure provider together the whole morning. Running into the network-config metadata version=0 is not supported issue... So glad to finally find this github issue about it, meaning that I probably did nothing wrong in my configuration :)
Has there been any progress on the topic since January? Could possibly some sort of variable be added that makes it generate the cidata in the nocloud format such that it is compatible with talos?

Unfortunately not. We don't use Talos and as such we can't commit to adding support for it. Patches welcome, of course, and we are more than happy to accept additional maintainers :-)

CAPMOX works well with TALOS. But it needs some patches to the CAPMOX's code.
Furthermore, it is possible to make your cluster "elastic", even self-managed (without an external cluster that creates and manages it).
All it needs to do is modifying network.go file located at pkg/cloudinit/ in the source code and rebuild docker image.
If something ready to use is needed, there is a docker image at https://hub.docker.com/r/ricottatosta/cluster-api-provider-proxmox already patched for TALOS. After deploying CAPMOX, patch CAPMOX deployment manifest and let its container image point at the new URL.
As mentioned earlier, it works like a charm.

CAPMOX works well with TALOS. But it needs some patches to the CAPMOX's code. Furthermore, it is possible to make your cluster "elastic", even self-managed (without an external cluster that creates and manages it). All it needs to do is modifying network.go file located at pkg/cloudinit/ in the source code and rebuild docker image. If something ready to use is needed, there is a docker image at https://hub.docker.com/r/ricottatosta/cluster-api-provider-proxmox already patched for TALOS. After deploying CAPMOX, patch CAPMOX deployment manifest and let its container image point at ricottatosta/cluster-api-provider-proxmox:[tag]. Last version (0.3.0) has the following patch applied:
...
const (
	/* network-config template. */
	networkConfigTPl = `version: 2
renderer: networkd
ethernets:
{{- range $index, $element := .NetworkConfigData }}
  eth{{ $index }}:
    match:
      macaddress: {{ $element.MacAddress }}
    dhcp4: {{ if $element.DHCP4 }}true{{ else }}false{{ end }}
    dhcp6: {{ if $element.DHCP6 }}true{{ else }}false{{ end }}
  {{- if or (and (not $element.DHCP4) $element.IPAddress) (and (not $element.DHCP6) $element.IPV6Address) }}
    addresses:
    {{- if $element.IPAddress }}
      - {{ $element.IPAddress }}
    {{- end }}
    {{- if $element.IPV6Address }}
      - '{{ $element.IPV6Address }}'
    {{- end }}
  {{- if eq $index 0 }}
    {{- if and $element.Gateway (not $element.DHCP4) }}
    gateway4: {{ $element.Gateway }}
    {{- end }}
    {{- if and $element.Gateway6 (not $element.DHCP6) }}
    gateway6: '{{ $element.Gateway6 }}'
    {{- end }}
    {{- if $element.DNSServers }}
    nameservers:
      addresses:
      {{- range $element.DNSServers }}
        - {{ . }}
      {{- end -}}
    {{- end -}}
  {{- end -}}
  {{- end -}}
{{- end -}}
{{- $vrf := 0 -}}
{{- range $index, $element := .NetworkConfigData }}
{{- if eq $element.Type "vrf" }}
{{- if eq $vrf 0 }}
vrfs:
{{- $vrf := 1 }}
{{- end }}
  {{$element.Name}}:
    table: {{ $element.Table }}
    {{- if $element.Routes }}{{ template "routes" $element }}{{- end -}}
    {{- if $element.FIBRules }}{{ template "rules" $element }}{{- end -}}
    {{- if $element.Interfaces }}
    interfaces:
    {{- range $element.Interfaces }}
      - {{ . }}
    {{- end -}}
    {{- end -}}
{{- end -}}
{{- end -}}
{{- define "rules" }}
    routing-policy:
    {{- range $index, $rule := .FIBRules }}
      - {
      {{- if $rule.To }} "to": "{{$rule.To}}", {{ end -}}
      {{- if $rule.From }} "from": "{{$rule.From}}", {{ end -}}
      {{- if $rule.Priority }} "priority": {{$rule.Priority}}, {{ end -}}
      {{- if $rule.Table }} "table": {{$rule.Table}}, {{ end -}} }
    {{- end }}
{{- end -}}
{{- define "routes" }}
    routes:
    {{- range $index, $route := .Routes }}
      - {
      {{- if $route.To }} "to": "{{$route.To}}", {{ end -}}
      {{- if $route.Via }} "via": "{{$route.Via}}", {{ end -}}
      {{- if $route.Metric }} "metric": {{$route.Metric}}, {{ end -}}
      {{- if $route.Table }} "table": {{$route.Table}}, {{ end -}} }
    {{- end }}
{{- end -}}
`
)
...

It's not tested against vrf. My use case is two ethernets, public and private. As mentioned earlier, it works like a charm.

Thanks! This patch appears to be working. I am now getting past the point where it was complaining that: "network-config metadata version=0 is not supported" :)
On a related point, how are you setting up the initial network for the control plane using Talos and Proxmox? I am attempting to use the VIP solution built into Talos but it seems to not be working... If you don't mind it would be very nice to see an example of your TalosControlPlane and ProxmoxCluster objects

For networking I use Cilium without kube-proxy.
For VIP I use kube-vip in BGP mode as daemonset.
Following is what you asked for:
`
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
kind: ProxmoxCluster
metadata:
name: k8s-test
namespace: k8s-test
spec:
allowedNodes:
- pve1
- pve2
- pve3
controlPlaneEndpoint:
host: <IP_ADDRESS> (my VIP)
port: 6443
dnsServers:
- <IP_ADDRESS>
ipv4Config:
addresses:
- <IP_ADDRESS>-<IP_ADDRESS>
gateway: <IP_ADDRESS>
prefix: 16
apiVersion: controlplane.cluster.x-k8s.io/v1alpha3
kind: TalosControlPlane
metadata:
name: k8s-test-control-plane
namespace: k8s-test
spec:
controlPlaneConfig:
controlplane:
generateType: controlplane
talosVersion: v1.6.1
configPatches:
- op: add
path: /machine/network/extraHostEntries
value:
- ip: <IP_ADDRESS>
aliases:
- kubernetes
......
infrastructureTemplate:
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
kind: ProxmoxMachineTemplate
name: k8s-test-control-plane
replicas: 1
version: 1.28.3
`

@ricottatosta Thank you for this - can you submit it as a PR, please?

After commenting PR #290, here is a recap of the issue.
Talos expects network-config to be in cloud-init nocloud format. It needs a parameter in proxmoxmachine spec such that it can be possible to build the requested format during cidata.iso creation.
I have prepared cluster-template-talos.yaml as a baseline for further templating.

After reading the relative issue on Talos I guess there is no need for further discussion. Talos is going to support cloud-init format, isn't it? thanks to @ekarlso.

Better. Talos 1.8.1 already supports it! Thank you all!

Better. Talos 1.8.1 already supports it! Thank you all!

I removed your patch from my setup and reinitialized the cluster with talos 1.8.3 and it all just appears to work. Nice find! :+1:

@isZumpo try to add the skipCloudInitStatus and skipQemuGuestAgent

Appears to be working :partying_face:
For those who run into the same issue, these are the fields which @mcbenjemaa mentions:
apiVersion: infrastructure.cluster.x-k8s.io/v1alpha1
kind: ProxmoxMachineTemplate
metadata:
  name: talos-cluster-worker
spec:
  template:
    spec:
      ...
      checks:
        skipQemuGuestAgent: true
        skipCloudInitStatus: true

However, there is one issue with the above solution, it is not bundled with any recent release of this provider yet. Perhaps time for a new release?
Until then, getting it installed is quite tricky. I am using the cluster-api-operator to declaratively install everything cluster-api related. Had to make a release in my fork of this repo, tweak the release files a bit, and point my InfrastructureProvider towards it like this:
apiVersion: operator.cluster.x-k8s.io/v1alpha2
kind: InfrastructureProvider
metadata:
 name: proxmox
 namespace: proxmox-infrastructure-system
spec:
 version: v0.5.2
 fetchConfig:
   url: https://github.com/isZumpo/cluster-api-provider-proxmox/releases/latest/infrastructure-components.yaml

Will make a PR soon which makes the fork release process a bit smoother for those who also use cluster-api-operator.


Infection develop fails

See https://github.com/codeigniter4projects/website/actions/workflows/infection.yml?query=branch%3Adevelop
Run git fetch --depth=1 origin $GITHUB_BASE_REF
  git fetch --depth=1 origin $GITHUB_BASE_REF
  infection --threads=2 --skip-initial-tests --coverage=build/phpunit --git-diff-base=origin/$GITHUB_BASE_REF --git-diff-filter=AM --logger-github --ignore-msi-with-no-mutations
  shell: /usr/bin/bash -e {0}
  env:
    COMPOSER_PROCESS_TIMEOUT: 0
    COMPOSER_NO_INTERACTION: 1
    COMPOSER_AUTH: {"github-oauth": {"github.com": "***"}}
From https://github.com/codeigniter4projects/website
 * [new branch]      dependabot/composer/codeigniter4/devkit-1.1.0 -> origin/dependabot/composer/codeigniter4/devkit-1.1.0
 * [new branch]      dependabot/composer/codeigniter4/framework-4.2.6 -> origin/dependabot/composer/codeigniter4/framework-4.2.6
 * [new branch]      master     -> origin/master

In Process.php line 112:

  The command "'git' 'diff' 'origin/' '--diff-filter' 'AM' '--name-only' '--'
   'app/'" failed.

  Exit Code: 128(Invalid exit argument)

  Working directory: /home/runner/work/website/website

  Output:
  ================

  Error Output:
  ================
  fatal: bad revision 'origin/'

run [--test-framework TEST-FRAMEWORK] [--test-framework-options TEST-FRAMEWORK-OPTIONS] [-j|--threads THREADS] [--only-covered] [-s|--show-mutations] [--no-progress] [--force-progress] [-c|--configuration CONFIGURATION] [--coverage COVERAGE] [--mutators MUTATORS] [--filter FILTER] [--formatter FORMATTER] [--git-diff-filter GIT-DIFF-FILTER] [--git-diff-lines] [--git-diff-base GIT-DIFF-BASE] [--logger-github [LOGGER-GITHUB]] [--logger-html LOGGER-HTML] [--noop] [--only-covering-test-cases] [--min-msi MIN-MSI] [--min-covered-msi MIN-COVERED-MSI] [--log-verbosity LOG-VERBOSITY] [--initial-tests-php-options INITIAL-TESTS-PHP-OPTIONS] [--skip-initial-tests] [--ignore-msi-with-no-mutations] [--debug] [--dry-run]

Error: Process completed with exit code 1.

I've been seeing this on my own repos. I haven't looked into it yet, but it isn't something specific to this project.

I don't know why, but failed again in develop.
Run git fetch --depth=1 origin $GITHUB_BASE_REF
From https://github.com/codeigniter4projects/website
 * [new branch]      MGatner-patch-1 -> origin/MGatner-patch-1
 * [new branch]      master          -> origin/master

In Process.php line 112:

  The command "'git' 'diff' 'origin/' '--diff-filter' 'AM' '--name-only' '--'
   'app/'" failed.

  Exit Code: 128(Invalid exit argument)

  Working directory: /home/runner/work/website/website

  Output:
  ================

  Error Output:
  ================
  fatal: bad revision 'origin/'

run [--test-framework TEST-FRAMEWORK] [--test-framework-options TEST-FRAMEWORK-OPTIONS] [-j|--threads THREADS] [--only-covered] [-s|--show-mutations] [--no-progress] [--force-progress] [-c|--configuration CONFIGURATION] [--coverage COVERAGE] [--mutators MUTATORS] [--filter FILTER] [--formatter FORMATTER] [--git-diff-filter GIT-DIFF-FILTER] [--git-diff-lines] [--git-diff-base GIT-DIFF-BASE] [--logger-github [LOGGER-GITHUB]] [--logger-html LOGGER-HTML] [--noop] [--only-covering-test-cases] [--min-msi MIN-MSI] [--min-covered-msi MIN-COVERED-MSI] [--log-verbosity LOG-VERBOSITY] [--initial-tests-php-options INITIAL-TESTS-PHP-OPTIONS] [--skip-initial-tests] [--ignore-msi-with-no-mutations] [--debug] [--dry-run]

Error: Process completed with exit code 1.

I found the cause. $GITHUB_BASE_REF does work only on PR.
See https://github.com/codeigniter4/tasks/pull/107


cmake: Port PR30519 from the master branch

This PR ports https://github.com/bitcoin/bitcoin/pull/30519.

cc @fanquake @maflcko


Add support for specifying custom logger

fixes #7

@simoneb Sure, give me a sec.

@simoneb Sure, give me a sec.

Codecov Report

Merging #11 (8c3c5de) into master (e8febb4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           26        28    +2
=========================================
+ Hits            26        28    +2

Impacted Files
Coverage Δ

plugin.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #11 (8c3c5de) into master (e8febb4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           26        28    +2
=========================================
+ Hits            26        28    +2

Impacted Files
Coverage Δ

plugin.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add TLS verify callback for Python and JS

Release 1.6.0 of grpc-java added support for using a custom TLS hostname verifier with clients. This feature parity doesn't exist for gRPC clients in other languages, which this PR tries to address (although an "override hostname" can be specified, support for an arbitrary callback is missing). In particular this adds support for a verification callback in JavaScript and Python. As an example, callbacks in JS look like:
grpc.credentials.createSsl(
    fs.readFileSync("truststore.pem"),
    fs.readFileSync("client.pem.key"),
    fs.readFileSync("clent.pem.crt"),
    {
      "insecureSkipHostnameVerify": true,
      "checkServerIdentity": function(host, cert) {
        authContext = newAuthContextFromPem(cert);
        if (authContext.name != expectedName || (authContext.environment != myEnvironment) {
          throw "Invalid server certificate presented";
        }
      }
    });

The "checkServerIdentity" idiom was chosen to match the same option available to TLS clients with the built-in node library. (InsecurySkipHostnameVerify was inspired by golang's InsecureSkipVerify option.)
In Python it looks like this:
def checkServerIdentity(host, cert):
     authContext = newAuthContextFromPem(cert)
     if authContext.name != expectedName or authContext.environment != myEnvironment:
        return False
     return True

grpc.ssl_channel_credentials(
    clientTrust.encode('utf-8'),
    open(clientKeystore[1]).read().encode('utf-8'),
    open(clientKeystore[0]).read().encode('utf-8'),
    {
      "insecureSkipHostnameVerify": True,
      "checkServerIdentity": checkServerIdentity
    })

For better context, the motivation for having callbacks like this stems from our internal PKI infrastructure where multidimensional identity information is added to various proprietary X.509 extensions. The policy on exactly which dimensions are relevant and should be checked varies from client to client so it's important that each client be able to supply verification logic.
In a less proprietary context, custom verifiers are often used as a supplemental check to do things like certificate or CA pinning.
We've been using an internal fork based on this PR for a few months now, so at least for JS and Python I have some practical confidence that this works as intended.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

This looks like a breaking change in the Node API, so we probably wouldn't accept it without a proposal for an API change to be included in the next major version bump. Also, development on the node library has been moved to https://github.com/grpc/grpc-node.

Ah, good to know, I'll check out that repo. That said, I don't think it's a breaking change; it adds an optional 4th parameter (JS object), so if left undefined existing behavior would be unchanged.

You're right, it's not a breaking change. I mixed it up with the optional parameter at the end of the server credentials SSL factory function.

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @JackOfMostTrades isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
The Linux Foundation CLA GitHub bot

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @JackOfMostTrades isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
The Linux Foundation CLA GitHub bot

Ok, I finally got around to pulling out the skip_hostname_verify option, so what's left is just the checkServerIdentity callback which is strictly supplemental to hostname verification.

Is there any information on what it will take to get this merged?  This code sitting unmerged/unaddressed is substantially impacting our ability to enable our non-java systems to interact with our Java-gRPC servers (which was a core promise that brought gRPC into our ecosystem).

Could you please split this PR into two, one on grpc core change and the other on wrapped languages? I can start reviewing the grpc core change.

Is this still an active concern? If so, can the conflicts in this pull request be resolved?
Also it might be wise to do Python as one pull request and Ruby as a separate pull request? I think the code reviews might be more manageable.

Yes, we definitely still want to get this PR in, but this piece is on hold until just the changes to core get merged in PR 15274. I think we're pretty close on that one. If it will help, I can split out this PR to the python and ruby pieces once that's in and we're ready to get this part going again.

The core PR has been merged now (#15274), so I've rebased this PR on top of it. This is just a thin bit of code for exposing the new verify peer callbacks from core up to python and ruby.

@nathanielmanistaatgoogle Thanks for the review! I think I've fixed everything from your comments on the python pieces.

Python/Cython changes LGTM. Pinging @apolcyn for Ruby review & @jiangtaoli2016 for security review.

@JackOfMostTrades Please take a look at Sanity test failures. (pylint is whining in particular). You can run them locally too, with tools/run_tests/run_tests.py -lsanity --use_docker -j 10

Thanks for the pointer. Looks like pylint didn't like my use of nonlocal in the test, so I just refactored that a tiny bit. Apparently I also needed to run generate_projects, yapf, and clang_format. So hopefully it should be all fixed up properly now!

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,976,654      Total (=)      1,976,654

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,775,735      Total (<)     10,775,739

 No significant differences in binary sizes

Hey there, thank you for creating this PR. I have an issue where I get a SSLV3_ALERT_BAD_CERTIFICATE.
I've tried this branch in my project, but it never run into the verify_callback method.
Is this branch working right now?
Thank you

Thanks for this change. It looks like it's in flux with a dependency on another PR. Feel free to create a new request or reopen if this needs more attention.


Added emscripten support

Hi, thank you for fenster. It is really nice to just drop the file into a directory and have a demo ready to go.
I spent some time adding support for emscripten in my fork because I wanted my demo to be runnable in a web browser as well.
I've modified the makefile in the drawing-c example to demonstrate how to build it once your emscripten environment is set up. It will create an output directory web/ that contains all the HTML, JavaScript and wasm files. There is also a serve target in the Makefile that will use Python3's http module to serve the application on http://localhost:9000/ for testing purposes .

SDL seems inappropriate for Fenster.


Refactor to allow configurable backends (configmap, eks configmap, crd)

This enables the authenticator server to support multiple backends (sources of IAM->user+group mappings) at the same time with a well-defined order of precedence according to the backend-mode argument.
Fixes https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/247
also fixes https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/261
TODO: more tests -- will do in a follow-up
TODO: update README -- done
TODO: fix server_test.go -- done
TODO: sts regional endpoint -- needs some discussion, will do in a follow-up

@wongma7 awesome, yeah I think the regional endpoint is a separate concern.

I think tests can be a follow-up. But I need to update the documentation (and fix the travis build). Will ping when that is ready.

RE: tests there are a couple tests that inadvertently use multiple mappers but no explicit tests yet. https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/269/files#diff-8151a8a5ca3b510f06b426f0cfb48708R646 I would like to refactor server_test.go in a followup as it will be quite verbose to have a configmap+file+crd version of every testcase. Then add some explicit tests.

/lgtm


Editorial fix. Add periods, use bold, fix typos

Add periods, use bold for parameters and fix minor typos.

 All CLA requirements met.

Hi @barbkess - The backslashes in line 33 were added in https://github.com/MicrosoftDocs/azure-docs/pull/24508. It looks correct to me (so the backslash renders in the live article) so I merged it, but it's reversed in this PR. Could you review the current updates, and other updates in the PR? Thanks.

@javierruizjimenez : Thanks for your contribution! The author, @barbkess, has been notified to review your proposed change.

Thanks @ktoliver for noticing the reversed PR. I have added the changes from #24508 to the PR.

@javierruizjimenez Thanks for the fixes! I'll merge this now.


[Bug] Icon_Picker does not have line-awesome library?

Bug report
What I did
Im using icon_picker field on my crudcontroller but it does not have line-awesome library in it.. In the upgrade guide we've been advised about line-awesome
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.2 (cli) (built: Jan 22 2020 06:30:58) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.2, Copyright (c), by Zend Technologies
LARAVEL VERSION:
v7.29.3@93f6d565a07045baa0e4b941ae1f733cd5984d65
BACKPACK VERSION:
4.1.27@bd1bab5dde08df20eebd730ca3a2992e1bf334f7

Hi @mpixelz! Just confirmed it's not supported, it should be easy to add it though.
I'll do some tests and feedback in a minute.

yeah i checked the blade file and it should be easy to implement but my point was.. maybe it was missed as 4.1 upgrade guide focuses on using line-awesome fonts for better compatibility but was not implemented in the icon_picker.

Sure @mpixelz, probably icon picker was forgotten. I managed a way to solve it, and pushed a PR to solve it #3342.
Thank you for your feedback, if you have the time please test the code on your side and let us know if it works.
I'll close this issue for now, lets move the conversation to #3342.


Kernel version error

I'm using Ubuntu 20.04 ROS noetic.
The error occurred when running ./scripts/patch-realsense-ubuntu-lts.sh
error : Unsupported kernel version 5.15.0-71-generic. The Focal patches are maintained for Ubuntu LTS with kernel 5.4, 5.8, 5.11 only

Hi @TapleFlib  This kernel patch script does not support kernel 5.15.  You should instead use ./scripts/patch-realsense-ubuntu-lts-hwe.sh for kernel 5.15.

Ah yes I remember, thanks so much!


Init Docusaurus for Documentation Web

Motivation
We have to give better docs website for CRA Universal
The solution is to use Docusaurus to generate the boilerplate
Note:

I create the boilerplate first, so we can discuss about the UI for content and versioning that we want to display
We can follor prettier.io docs

Codecov Report

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

@@          Coverage Diff          @@
##           master    #73   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines          58     58
  Branches       10     10
=====================================
  Hits           58     58

Continue to review full report at Codecov.

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


Fix the panic message of MemQuota.Record

What problem does this PR solve?
The panic message should be "MemQuota.record".
Issue Number: close #10478
What is changed and how it works?
Check List
Tests

No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/check-issue-triage-complete

/test cdc-integration-storage-test

/approve

/retest


Separate opt in out urls scan

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

Codecov Report
Patch coverage: 100.00% and project coverage change: -3.19 :warning:

Comparison is base (373c58e) 92.32% compared to head (3d29bb8) 89.14%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1256      +/-   ##
==========================================
- Coverage   92.32%   89.14%   -3.19%
==========================================
  Files          67      112      +45
  Lines        4116     6373    +2257
==========================================
+ Hits         3800     5681    +1881
- Misses        316      692     +376

Flag
Coverage Δ

jobs_cache_maintenance
99.08% <ø> (?)

jobs_mongodb_migration
83.49% <ø> (?)

libs_libcommon
91.82% <100.00%> (?)

services_admin
85.85% <ø> (?)

services_api
88.14% <ø> (?)

services_worker
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

libs/libcommon/src/libcommon/config.py
76.41% <ø> (ø)

libs/libcommon/tests/test_processing_graph.py
100.00% <ø> (ø)

libs/libcommon/src/libcommon/constants.py
100.00% <100.00%> (ø)

libs/libcommon/src/libcommon/utils.py
93.10% <100.00%> (ø)

libs/libcommon/tests/test_utils.py
100.00% <100.00%> (ø)

... and 174 files with indirect coverage changes

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


EXC_BAD_ACCESS (code=1, address=0x54)

Environment info:

iOS 12.0 (16A5339e)
XCode 10 beta 5
Particle SDK 0.7.0

Issue description:
The Particle SDK is crashing always in EventSource.m when this function is called:
- (void)connection:(NSURLConnection *)connection didFailWithError:(NSError *)error. The crash is happening on line 176 when this part of code is executed:
dispatch_after(popTime, self.queue, ^(void) {
        if (self.retries < 5) {
//            NSLog(@"connection retries %d",self.retries);
            self.retries++;
            [self open];
        }

    });

It crashes with Thread 10: EXC_BAD_ACCESS (code=1, address=0x54) error when iOS is trying to connect to a device

Ok, I've found there was newer version 0.8.1, but the update didn't help... I'd recommend better documentation in readme.md for actual version.
The issue is when dispatch_after(popTime, self.queue, ^(void) {} is executed the self.queue is nil, that causes the BAD_ACCESS error. I'm not sure why this is happening.

Thanks, will investigate. The latest SDK version is displayed right below the header.

Can you please verify this is happening with non-beta xcode & non-beta iOS versions?

@RaimundasSakalauskas sorry I can't as I don't have any other device with iOS 11 and my non-beta xcode 9.4.1 won't let me install and run any application on iOS 12.
Do you have any suggestion what is causing the error?

@skyfoxa thank you for you answer. Apparently queue for some reason gets deallocated, but it's hard for me to tell why without further investigation. Can you please let me what is the reliable way to trigger the error you are having? I will try it on iOS 11. I'd assume that eventsource is deallocated without canceling some long running code. By the time scheduled call is triggered, queue is deallocated and causes a crash. Most likely the solution will be 1 of 2:

Making sure all long running code is canceled before deallocating eventsteam
Wrapping the crashing code with nil check

Knowing the steps you do to trigger the crash will help me a lot with fixing this.

@RaimundasSakalauskas here is all thread stack info:
* thread #12, queue = 'com.apple.root.background-qos', stop reason = EXC_BAD_ACCESS (code=1, address=0x54)
  * frame #0: 0x00000001086b3bac libdispatch.dylib`dispatch_after + 292
    frame #1: 0x000000010676d318 Particle_SDK`-[EventSource connection:didFailWithError:](self=0x0000000281525020, _cmd="connection:didFailWithError:", connection=0x00000002833141d0, error=domain: @"NSURLErrorDomain" - code:<PHONE_NUMBER>3709550611) at EventSource.m:168
    frame #2: 0x00000001a2731a6c CFNetwork`__65-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:]_block_invoke + 60
    frame #3: 0x00000001a24a2cd8 CFNetwork`-[NSURLConnectionInternal _withConnectionAndDelegate:onlyActive:] + 200
    frame #4: 0x00000001a24a77e4 CFNetwork`-[NSURLConnectionInternal _withConnectionAndDelegate:] + 56
    frame #5: 0x00000001a26ee398 CFNetwork`_NSURLConnectionDidFail(_CFURLConnection*, __CFError*, void const*) + 84
    frame #6: 0x00000001a2631690 CFNetwork`___ZN27URLConnectionClient_Classic17_delegate_didFailEP9__CFErrorU13block_pointerFvvE_block_invoke + 116
    frame #7: 0x00000001a262f228 CFNetwork`___ZN27URLConnectionClient_Classic18_withDelegateAsyncEPKcU13block_pointerFvP16_CFURLConnectionPK33CFURLConnectionClientCurrent_VMaxE_block_invoke_2 + 108
    frame #8: 0x000000010869cde4 libdispatch.dylib`_dispatch_client_callout + 16
    frame #9: 0x00000001086a0a2c libdispatch.dylib`_dispatch_block_invoke_direct + 232
    frame #10: 0x00000001a270e15c CFNetwork`RunloopBlockContext::_invoke_block(void const*, void*) + 36
    frame #11: 0x00000001a1e29b2c CoreFoundation`CFArrayApplyFunction + 80
    frame #12: 0x00000001a270e010 CFNetwork`RunloopBlockContext::perform() + 128
    frame #13: 0x00000001a270f1e4 CFNetwork`MultiplexerSource::perform() + 312
    frame #14: 0x00000001a270ef44 CFNetwork`MultiplexerSource::_perform(void*) + 60
    frame #15: 0x00000001a1e8a5b8 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
    frame #16: 0x00000001a1e8a538 CoreFoundation`__CFRunLoopDoSource0 + 88
    frame #17: 0x00000001a1e89e1c CoreFoundation`__CFRunLoopDoSources0 + 176
    frame #18: 0x00000001a1e84ce8 CoreFoundation`__CFRunLoopRun + 1040
    frame #19: 0x00000001a1e845b8 CoreFoundation`CFRunLoopRunSpecific + 436
    frame #20: 0x00000001a1e85354 CoreFoundation`CFRunLoopRun + 80
    frame #21: 0x000000010676c8b8 Particle_SDK`-[EventSource open](self=0x0000000281525020, _cmd="open") at EventSource.m:116
    frame #22: 0x000000010676c12c Particle_SDK`__49-[EventSource initWithURL:timeoutInterval:queue:]_block_invoke(.block_descriptor=0x0000000283fb0c90) at EventSource.m:66
    frame #23: 0x000000010869cde4 libdispatch.dylib`_dispatch_client_callout + 16
    frame #24: 0x00000001086a01e0 libdispatch.dylib`_dispatch_continuation_pop + 528
    frame #25: 0x00000001086b2cac libdispatch.dylib`_dispatch_source_invoke + 1864
    frame #26: 0x00000001086ae1f8 libdispatch.dylib`_dispatch_root_queue_drain + 376
    frame #27: 0x00000001086aebe4 libdispatch.dylib`_dispatch_worker_thread2 + 156
    frame #28: 0x00000001a1b16190 libsystem_pthread.dylib`_pthread_wqthread + 472
    frame #29: 0x00000001a1b18d00 libsystem_pthread.dylib`start_wqthread + 4

Maybe I discovered the cause. The whole process starts by calling ParticleCloud.sharedInstance().injectSessionAccessToken(accessToken, withExpiryDate: expiry), when the EventSource with initWithURL is called at the beginning. But injectSessionAccessToken calls [self logout]; that leads to [EventSource close] function. There is  self.queue = nil; that deallocates the queue. I commented this row and the BAD_ACCESS stopped.

so it helped only in 1 test case and in all other tries it crashed again because of nil queue. Is there another place where this queue could be set to nil except [EventSource close] function?

Thanks for clarifying. Investigating now. Will keep this thread updated.

Can you please reach me at<EMAIL_ADDRESS>I'm unable to reproduce this neither on iOS 12 simulator, nor on iOS 11 even when I explicitly set queue to nil throughout the project. Maybe we could arrange screenshare or cooperate otherwise trying to solve this.

@RaimundasSakalauskas thanks for investigating on this.
Meantime I tried these steps:

I updated to iOS 12 Beta 11 and xCode 10 beta 6
I tried the hack to comment out the  self.queue = nil; in [EventSource close] again.
Clean build folder
Build

It didn't crash in any try and everything works as expected. I can't find any other place from where this close function or dealloc for EventSource could be called right now as I didn't write that code, so I'm still discovering what is going on. So I think I'll test the app with this hack for a while.
Do you think you could remove this self.queue = nil; line in next version? I think it isn't necessary as the queue is marked as Strong property so it won't cause a retain cycle.

@skyfoxa I assume that you can't share the project source, but maybe you could share the part of the code that interacts with Particle SDK? I would really like to understand what is happening there, because so far I was unable to reproduce the crash no matter what I try.
This is pure guessing at his point, but given that this part of code hasn't been changed for quite a while now (2 years?) and this is the first time it is reported, I would like to make sure there is nothing wrong with the way you use SDK.

@RaimundasSakalauskas yeah, I don't have permission to share the project nor the source code. But I understand your situation and I'll discuss it with my superior colleague.
I think it is definitely caused by new iOS 12 or new xCode 10, as you've said this wasn't changed for quite a while - we have been using deprecated SparkSDK for a year until now. Firstly I thought the issue was caused by my refactoring of some controllers (I didn't refactor the communication layer), but when the issue happened I tested previous branch with SparkSDK and iOS 12/xCode 10 and the issue happened too (the queue was set to nil). This is why I think something got change in new iOS 12/xCode 10 causing the issue.

After seeing this crash in crashlytics I tried to dig deeper. Was able to reproduce if I ran inectAccessToken + test device was offline (no mobile data or wifi connection). I noticed that one EventStream object would first be closed then callback on that eventource would trigger which would cause a crash (wonder what changed in ios12 for this to start happening). I was able to prevent the crash by adding extra checks for that. Please see commit: https://github.com/particle-iot/particle-sdk-ios/commit/e1473b746b89873fbee269e9b090b181071ae357

Hey @RaimundasSakalauskas, thanks for update.
Your use case is similar to our functionality, the crash occurs when user has to change wifi network in the device, so for a while it is offline.
However it looks like your update isn't enough. In didFailWithError we are having issue with
dispatch_after(popTime, self.queue, ^(void) {
        if (wasClosed) {
            return;
        }

        if (self.retries < 5) {
            self.retries++;
            [self open];
        }

    });

self.queue looks to be still nil.

There are multiple event sources running simultaneously and this code executes on different threads. Can you please confirm that you are still seeing this error even with the latest commit on the mesh branch (https://github.com/particle-iot/particle-sdk-ios/tree/feature/mesh)? I think I added few more changes after I replied the last time therefore the linked commit might be outdated.
We have 0 issues regarding this with our Tinker app after these changes were introduced and your reply leaves me slightly puzzled.
I'm sure you know how to use development pod (not the public release), but just in case someone who reads this thread does not here's the instruction:

Clone this repo
Check out mesh branch
Define path to local git repo in your project file like this: pod 'Particle-SDK', :path => '../particle-sdk-ios'
Run git install (if it's a new project) or pod update Particle-SDK if the dependencies have previously been installed and you are only swapping public pod for a development pod.

@RaimundasSakalauskas we updated on v0.9.2 and everything works fine now. Thanks for the update.


DO NOT MERGE 302 andrey contributors and releases

Deploy preview for landscape ready!
Built with commit 61fa7ca16ce3f55f6d7d946aa67f7e1821060db8
https://deploy-preview-369--landscape.netlify.com

@dankohn please review!


Document how to review and revoke access granted to DemoGenerator

This is a cool application :-)
This app is used to set up lab environments during MS trainings.  If there is a problem with using a promo code somone may be pressed to solve it by granting access to some other subscription that belongs to that person just to be able to do the lab exercise and may wish to revoke the granted access after the training is over.
You are missing documentation explaining where to review the permissions granted to the app and how to revoke them.

@dpurge you can find all applications that you have authorized here. https://dev.azure.com/{ORGANIZATION}/_usersSettings/authorizations
You can revoke by clicking on delete icon there.

@dpurge  if you need any more info you can reopen this issue.


README example of apt_repository should be updated

The example for apt_repository that adds 'nginx-php' should be updated. The URI specified (http://ppa.launchpad.net/nginx/php5/ubuntu) is not available and gives a 404.
It would be easier to figure out how to use apt_repository by starting from a working example.

:+1: @thommay


Question about Twitter-2015

Hello,
I ran your code on the Twitter-2015 dataset and achieved an F1-score of 75.30, which closely aligns with the results reported in your paper. However, I later discovered that some labels in your dataset had been modified, and you mentioned that the paper's results are based on the original version. In an attempt to replicate the reported results, I replaced the 'train.txt,' 'valid.txt,' and 'test.txt' files with the original text files. This time, I only managed to achieve an F1-score of 73.27, which is clearly not an ideal outcome.
I've made several attempts to tune the parameters, but I'm still unable to match the results presented in the paper. Could you kindly provide me with some guidance or hints to help me reproduce your reported results?
Thank you very much.

Thanks for your attention. We have identified noise in the 2015 dataset during our previous experiments, which led to incorrect labels (this has also been confirmed in our discussions with reviewers). Consequently, we have rectified the annotations of certain data points. It is common in our experiments to observe variations in a single point due to disparities in GPU and precision on the 2015 dataset. We have conducted multiple runs of the experiments ourselves, and the results were not very consistent, primarily due to the presence of noise in the data. To address this issue, you can additionally adjust parameters such as learning rate and batch size. We recommend considering the use of only the 2017 dataset instead of the 2015 dataset, as the noise present in the 2015 dataset poses difficulties in accurately evaluating the results.

Thank you for your response. I will try to tune the parameters to achieve a better performance.


setup.cfg: remove 3.11 compatibility

universal_pathlib is currently broken for 3.11, see https://github.com/fsspec/universal_pathlib/issues/67

Replaced with https://github.com/iterative/pytest-servers/pull/21