ci: github workflow

Summary of PR

[X] Add GitHub Workflow for CI
[ ]  Release workflow for publishing

Tests for unexpected behavior
You can test run ->  https://github.com/saihaj/ShabadOSdesktop/actions/runs/144226934

Time spent on PR
2 hours
Reviewers
@Harjot1Singh

Can;t really remove CCI, since we need it for releases

@Harjot1Singh we have 2 options to choose from when creating and publishing release in gihtub actions:

We create a release using actions/create-release@v1 and generate changelog (You can see example of this here -> https://github.com/saihaj/ShabadOSdesktop/runs/973714966). Then we have another workflow in which we create binaries for OS and then using this<EMAIL_ADDRESS>we get the draft release we created and upload assets to it and finally update the release to mark it published using something like<EMAIL_ADDRESS>

Other option is that will allows us to keep one file. We extend on what I have right now for CI once the binaries are built we upload them to GitHub actions artifacts section(similar to CCI job) using actions/upload-artifact@v2 and then have a new job that will depend on build step (once all the binaries have been built and uploaded to gh-actions artifacts section) we create a release using actions/create-release@v1, retrieve built binaries using actions/download-artifact@v2 and upload them to our release using actions/upload-release-asset@v1

Please rename the title of the PR to match our commit guidelines
I think in this case the type would be "build" instead of "ci"

That is my bad, I honestly didn't know we had a "ci" type -- My apologies!

@saihaj what's the difference to what comes out, between the two?

@saihaj are you planning on working on this? if not, close the PR. If it's something you want to work on but can't because you're waiting on something else change the status from Hold to "Blocked" so it's in the correct PM column.

Now we have the actions repo we will most likely use those. I guess it is easier to just make a new one


Fatal error while running container for CVE-2021-44228

Hey there,
when running the container for CVE-2021-44228, I get the following output.
 Continuing.
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | # A fatal error has been detected by the Java Runtime Environment:
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | #  SIGSEGV (0xb) at pc=0x00007f44839fa532, pid=1, tid=0x00007f44847ce700
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | # JRE version: OpenJDK Runtime Environment (8.0_102-b14) (build 1.8.0_102-8u102-b14.1-1~bpo8+1-b14)
cve-2021-44228-solr-1  | # Java VM: OpenJDK 64-Bit Server VM (25.102-b14 mixed mode linux-amd64 compressed oops)
cve-2021-44228-solr-1  | # Problematic frame:
cve-2021-44228-solr-1  | # C  [libc.so.6+0x36532]  abort+0x232
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | # Core dump written. Default location: /opt/solr/server/core or core.1
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | # An error report file with more information is saved as:
cve-2021-44228-solr-1  | # /opt/solr/server/hs_err_pid1.log
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  | # If you would like to submit a bug report, please visit:
cve-2021-44228-solr-1  | #   http://bugreport.java.com/bugreport/crash.jsp
cve-2021-44228-solr-1  | # The crash happened outside the Java Virtual Machine in native code.
cve-2021-44228-solr-1  | # See problematic frame for where to report the bug.
cve-2021-44228-solr-1  | #
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [error occurred during error reporting , id 0xb]
cve-2021-44228-solr-1  |
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1  | [Too many errors, abort]
cve-2021-44228-solr-1 exited with code 139

Cannot reproduce in my machine. It my logs:
λ docker compose logs
cve-2021-44228-solr-1  | neither jattach nor jstack in /usr/lib/jvm/java-8-openjdk-amd64/jre could be found, so no thread dumps are possible. Continuing.
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory (errno = 12).
cve-2021-44228-solr-1  | 2023-05-21 07:02:27.656 INFO  (main) [   ] o.e.j.u.log Logging initialized @781ms to org.eclipse.jetty.util.log.Slf4jLog
cve-2021-44228-solr-1  | 2023-05-21 07:02:27.826 INFO  (main) [   ] o.e.j.s.Server jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 1.8.0_102-8u102-b14.1-1~bpo8+1-b14
cve-2021-44228-solr-1  | 2023-05-21 07:02:27.838 INFO  (main) [   ] o.e.j.d.p.ScanningAppProvider Deployment monitor [file:///opt/solr/server/contexts/] at interval 0
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.015 INFO  (main) [   ] o.e.j.w.StandardDescriptorProcessor NO JSP Support for /solr, did not find org.apache.jasper.servlet.JspServlet
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.022 INFO  (main) [   ] o.e.j.s.session DefaultSessionIdManager workerName=node0
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.022 INFO  (main) [   ] o.e.j.s.session No SessionScavenger set, using defaults
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.024 INFO  (main) [   ] o.e.j.s.session node0 Scavenging every 660000ms
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.066 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter Using logger factory org.apache.logging.slf4j.Log4jLoggerFactory
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.069 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter  ___      _       Welcome to Apache Solr™ version 8.11.0
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.069 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter / __| ___| |_ _   Starting in standalone mode on port 8983
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.069 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter \__ \/ _ \ | '_|  Install dir: /opt/solr
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.069 INFO  (main) [   ] o.a.s.s.SolrDispatchFilter |___/\___/_|_|    Start time: 2023-05-21T07:02:28.069Z
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.075 INFO  (main) [   ] o.a.s.c.SolrPaths Using system property solr.solr.home: /opt/solr/server/solr
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.076 INFO  (main) [   ] o.a.s.c.SolrXmlConfig Loading container configuration from /opt/solr/server/solr/solr.xml
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.173 INFO  (main) [   ] o.a.s.c.SolrXmlConfig MBean server found: com.sun.jmx.mbeanserver.JmxMBeanServer@1ed1993a, but no JMX reporters were configured - adding default JMX reporter.
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.479 INFO  (main) [   ] o.a.s.h.c.HttpShardHandlerFactory Host whitelist initialized: WhitelistHostChecker [whitelistHosts=null, whitelistHostCheckingEnabled=true]
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.585 WARN  (main) [   ] o.e.j.u.s.S.config Trusting all certificates configured for Client@5049d8b2[provider=null,keyStore=null,trustStore=null]
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.585 WARN  (main) [   ] o.e.j.u.s.S.config No Client EndPointIdentificationAlgorithm configured for Client@5049d8b2[provider=null,keyStore=null,trustStore=null]cve-2021-44228-solr-1  | 2023-05-21 07:02:28.701 WARN  (main) [   ] o.e.j.u.s.S.config Trusting all certificates configured for Client@7e094740[provider=null,keyStore=null,trustStore=null]
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.702 WARN  (main) [   ] o.e.j.u.s.S.config No Client EndPointIdentificationAlgorithm configured for Client@7e094740[provider=null,keyStore=null,trustStore=null]cve-2021-44228-solr-1  | 2023-05-21 07:02:28.736 WARN  (main) [   ] o.a.s.c.CoreContainer Not all security plugins configured!  authentication=disabled authorization=disabled.  Solr is only as secure as you make it. Consider configuring authentication/authorization before exposing Solr to users internal or external.  See https://s.apache.org/solrsecurity for more info
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.826 INFO  (main) [   ] o.a.s.c.TransientSolrCoreCacheDefault Allocating transient core cache for max<PHONE_NUMBER> cores with initial capacity of 1024
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.832 INFO  (main) [   ] o.a.s.h.a.MetricsHistoryHandler No .system collection, keeping metrics history in memory.
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.880 INFO  (main) [   ] o.a.s.m.r.SolrJmxReporter JMX monitoring for 'solr.node' (registry 'solr.node') enabled at server: com.sun.jmx.mbeanserver.JmxMBeanServer@1ed1993a
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.880 INFO  (main) [   ] o.a.s.m.r.SolrJmxReporter JMX monitoring for 'solr.jvm' (registry 'solr.jvm') enabled at server: com.sun.jmx.mbeanserver.JmxMBeanServer@1ed1993a
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.881 INFO  (main) [   ] o.a.s.m.r.SolrJmxReporter JMX monitoring for 'solr.jetty' (registry 'solr.jetty') enabled at server: com.sun.jmx.mbeanserver.JmxMBeanServer@1ed1993a
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.902 INFO  (main) [   ] o.a.s.c.CorePropertiesLocator Found 0 core definitions underneath /opt/solr/server/solr
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.935 INFO  (main) [   ] o.e.j.s.h.ContextHandler Started o.e.j.w.WebAppContext@2cb4893b{/solr,file:///opt/solr/server/solr-webapp/webapp/,AVAILABLE}{/opt/solr/server/solr-webapp/webapp}
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.946 INFO  (main) [   ] o.e.j.s.AbstractConnector Started<EMAIL_ADDRESS>(http/1.1, h2c)}{<IP_ADDRESS>:8983}
cve-2021-44228-solr-1  | 2023-05-21 07:02:28.946 INFO  (main) [   ] o.e.j.s.Server Started @2073ms

It seems like there is a crash in your Java runtime. You can try it in another Linux machine such as Ubuntu, I'm not sure if it related to your CPU architecture.


removing shinylogs and all dependencies

Now that the app is deployed on shinyapps.io, we don't need internal logging systems.
Sorry in advance @CCorrado for the cache rebuild this will cause!

LGTM. Cache is just a diff, so as long as you didn't add anything new it was as fast as it could be!


Presubmits should be run on release branches.

Context: this PR has been merged without running any tests. Changes to clusterloader2 have a potential to break things and presubmit is a cheap way to prevent at least trivial issues.

/area clusterloader
/priority important-soon
Ideally configuration of those presubmits should be generated when, the new release branch is created.

/remove-lifecycle rotten
@jkaniuk @mm4tt - FTR

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten


Bug 1707941: bump github.com/containers/{storage,image,buildah}

Bump github.com/containers/storage to v1.12.7, github.com/containers/image to 9467ac9cfd92c545aa389f22f27e552de053c0f2, which switches from using github.com/boltdb/bolt to using github.com/etcd-io/bbolt, and github.com/containers/buildah to 7ae362bcedfed09eb5c644a94696fe59e16126dd.
This should also fix #71, by incorporating https://github.com/containers/buildah/pull/1579.

/lgtm
@nalind is there a BZ for #71 ?

@adambkaplan I don't see an equivalent for #71 in bugzilla.

@nalind please open a BZ then, targeting the fix for 4.2.0. My hunch is that we will want to pick this to a 4.1.z release as well.

/cherrypick release-4.1

/cherrypick release-4.1


change_password: Migrate modal to dialog_widget.

Vertical alignment of Forgotten it button is not correct.
Same feedback for the error element, would be better to get a feedback on these.

Merged, thanks @ganpa3!


Anti-aliasing on the tree

Compared to the other passive tree builder (https://github.com/EmmittJ/PoESkillTree) anti-aliasing on the passive tree is something that is really noticeable, especially when you zoom out. Are there plans to add this?
Cheers

The issue isn't lack of anti-aliasing, but rather that the textures used for the lines connecting nodes become too thin when you zoom out beyond a certain point, and no amount of AA or texture filtering will make it look good, as the skill tree just isn't designed to be zoomed out that far.
PoESkillTree doesn't have this issue because it doesn't use those textures to render the connectors, and that's really the only way to solve the problem. I much prefer using the original artwork though, but I may someday add the option to use solid lines like PoESkillTree does.

Honestly it looks worse to me with mipmapping enabled, it just seems excessively blurry now.

Yeah, mipmapping's not too good for fine detail. I think it still looks fine up to a certain point though, but as I said before, ultimately the tree's artwork just isn't designed to be viewed like that. I'll leave it as is for the time being and see what other feedback I get.

I'm not sure it's a mipmapping-specific problem, the artwork resolution is just too low.
For example, on PoB Necromantic Aegis looks like this currently: http://puu.sh/wyV1K/1b51737a95.png
While the actual keystone is much higher resolution, and nowhere near as blurry: http://puu.sh/wyV4s/bc9a76b902.png

That can't be helped; the program uses the assets made by GGG for their online passive tree, and I'm already using the highest resolution version of those assets. I would like to eventually migrate towards using the actual assets and data used by the game itself, but that's no small task.

The lines disappear on some zoom levels too. Making them a minimum width of 1 pixel would solve this.


Draft: feat(series): add article series functionality

Add series functionality to TechHub:

Data logic
Overview and detail page
SeriePlaylist for article page

Don't  merge yet


Not an issue - gzip'ed content

Sorry, this is not an issue (I think), just and idea to include.
I am observing that when a service returns a gzip'ed file (javascript in my case), rewrite body is not rewriting the response.
Any chance the plugin to do:
gzip service response -> plugin-rewritebody un-gzip -> plugin-rewritebody rewrite body -> plugin-rewritebody gzip -> and so on...
Sorry not to make a pull request by my own but unfortunately I have no Go knowledge.
Cheers.

I found https://github.com/packruler/rewrite-body which might help. 😊


Kettle needs escape pods and someone to maintain the map.

Description

Reproduction

Screenshots

Additional context

i messaged checkraze and he said he was gonna update it this weekend


[Snyk] Upgrade react-awesome-query-builder from 4.10.0 to 5.3.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade react-awesome-query-builder from 4.10.0 to 5.3.1.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

The recommended version is 8 versions ahead of your current version.
The recommended version was released a month ago, on 2022-09-01.

Release notes

Package name: react-awesome-query-builder

5.3.1 - 2022-09-01
Support @ fortawesome/react-fontawesome 0.2.x (issue #757)
Fix loadFromSpel for select_not_equals op (PR #761) (issue #704)

5.3.0 - 2022-08-29No content.

5.2.1 - 2022-08-25
5.2.1

Fix type applied to filter funcs as another func's arg value (PR #743) (issue #586)
Allow self nesting of functions with allowSelfNesting (PR #698)
ES: Fix greater op (PR #749) (issue #744)
ES: Fix NOT (PR #750) (issue #723)

5.2.0 - 2022-08-19
5.2.0

! Breaking change: children1 is now array in result of getTree() to preserve items order (PR #672) (issues #589, #670)
Utils.getTree(tree, true, false) will behave same as before this change.
Support React 18. Migrate to x-date-pickers. (PR #734) (issues #710, #732)
Add path property at index.d.ts (PR #671) (issue #669)
Fixed getTotalRulesCountInTree() == 1 (should be 0) for clear tree (PR #673) (issue #583)
Handle validation of bad multiselect value correctly (PR #733) (issue #674)
Remove bad values from list, don't unset whole value.
Added config removeInvalidMultiSelectValuesOnLoad (true by default, false for AntDesign)
Fix loadFromSpel for select_equals op (PR #740) (issue #704)
Fix loadFromSpel for is_empty and is_not_empty ops (PR #713) (issues #714, #699)

5.1.2 - 2022-03-15
Added config removeIncompleteRulesOnLoad (default false) (PR #661) (issue #642)
Fix error when using same field for comparison as argument of function (PR #662) (issue #612)
Set missing id in fixPathsInTree() (PR #665) (issue #664)
Use func arg type in field selection (PR #666) (issue #615)

5.1.1 - 2022-03-09
Fix value null instead of undefined in JSON (PR #657) (issue #653)

5.1.0 - 2022-03-08
Use spel2js 0.2.8 instead of my branch (PR #638) (issues #634, #643, #654)
Add async load to antd (PR #640) (issues #616, #425)
Fix autocomplete (PRs #655, #641)
Fix setting defaultValue on set value src (PR #639) (issue #635)
Fix validation of multiselect func arg (PR #656) (issue #587)

5.0.0 - 2022-02-04SpEL support (#613)
* .
* .
* .
* spelFormatValue
* mongo: fix for empty aggregation
* fix T()
* string: fix empty aggr
* sql: add asyncListValues
* aggr
* #
* func
* ? escape
* fixed escape
* float, array, .?[true]
* #this not needed?
* formatSpelField, isSpel*
* spel2js init
* import1
* typo width
* fix revop
* fix omitBrackets
* use my fork
* .
* fix valueType and unary minus
* group basic
* inline list
* date, datetime
* time
* lint fix
* test fix
* added simple tests
* group fix
* some/all/none
* between
* valueType from field config
* !func
* excludeOperators for type
* fix $contains
* chlog
* Like -> Contains
Moved is_empty, is_null to end of operators list
* fix test
* chlog
.
.
* readme
* add "sh " for win
* ternary1
* ternary 2
.
* .
* .
* parentReordableNodesCnt
* export ?:
* import ternary
* ternary import complete with react-select
* .
* .
* fix
* add case
* !
* lint fix
* tsc fix
* fix add first case
* unsafe warning fix
* demo /switch
* fix
* fix validation
* fix
* .
* logger
* .
* fix import
* add/del default
* getSwitchValues
* lint fix
* .
* .
* lint fix
* fix for npm 7+
* .
* lint fix
.
* Added `Utils._loadFromJsonLogic()` that returns `[tree, errors]` (issue #621)
* return Errors
* useCallback
* .
* fix tests
* .
* fix

4.10.0 - 2022-01-18Bootstrap

    from react-awesome-query-builder GitHub release notes

Commit messages

Package name: react-awesome-query-builder

4291fa8 5.3.1
e381b0e fix: ui brokens when given select_not_equals operator (#761)
e5886c0 Update FUNDING.yml
ead1b17 Update CHANGELOG.md
894a4b6 Update package.json
7fc0cb5 Update CHANGELOG.md
4263d47 Able to customize item render behavior (#729)
49d7956 ES: Fix NOT (#750)
b9351ae ES: Fix greater op (#749)
d128d04 Fix type applied to filter funcs as another func's arg value (#743)
e6ba33a Allow self nesting of functions (#698)
b8f054a Fix gh-pages (#742)
97b24f6 Update CHANGELOG.md
fa0c611 Fix is_empty and is_not_empty in spel converter (#713)
025b71e Fix loadFromSpel for select_equals op (#740)
71c6766 Bump @ types/node from 17.0.45 to 18.7.7 (#737)
38ddab2 Fix validation of bad multiselect value (#733)
fbeee09 Support React 18. Migrate to x-date-pickers. (#734)
d185b90 Update README.md (#703)
359dfd1 nit
710bb96 nit
5d24de7 readme: migration to 5.2.0
4b49aef Breaking change: children1 is now array in result of getTree() to preserve items order (#672)
dcc2c32 Fixed getTotalRulesCountInTree() == 1 (should be 0) for clear tree (#673)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

/check


Automatically install phantomjs and chromedriver

Meteor-robotframework tests have dependencies on external (non - Node, non - Meteor) web driver software:

Automatable browsers (e.g. chromedriver or PhantomJS).

It would be really nice to follow the Meteor way and automatically install these when rsbatech:robotframework is aded to a project (or triggered when the project is built).
~~One strategy might be to use the robotframework java jar , instead of native python.  It might then be possible to extend a jar on the fly containing additional libraries (like Selenium2Library) and run RF using java -jar robotframework.jar [options] data_sources ~~

Released with v0.2.0


Cannot boot Alpine with signatures enabled

Alpine 3.10.3 was released 24 hours ago, and they replaced the kernel and initramfs files in-place. Therefore, the signatures no longer match, and boot fails unless I disable image signature checks.

I refreshed the sigs this morning and they seem to load now.  It looks like i'm just using the generic rolling release files for the major release from:
http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/netboot/
as opposed to minor revs:
http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/netboot-3.10.3/
It might be better to pull it from the minor revs but it might just involve more periodic updates and sig updates.  I'll try and think about a better way to do it that involves less maintenance in the future.
Thanks for the report tho!

I confirm that it boots now.


[charts-isCapped] adding isCapped key to charts response

New Response:
[
    {
        "count": "0",
        "isCapped": false,
        "timestamp": "2022-04-06T23:21:00Z",
        "types": []
    },
    {
        "count": "100",
        "isCapped": true,
        "timestamp": "2022-04-07T00:57:00Z",
        "types": [
            {
                "count": "1",
                "type": "token_pool_confirmed"
            },
            {
                "count": "37",
                "type": "message_confirmed"
            },
            {
                "count": "12",
                "type": "token_transfer_confirmed"
            },
            {
                "count": "25",
                "type": "transaction_submitted"
            },
            {
                "count": "25",
                "type": "blockchain_event_received"
            }
        ]
    }
]

Codecov Report

Merging #669 (302a9df) into main (9b787bc) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #669   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          315       315
  Lines        19370     19371    +1
=========================================
+ Hits         19370     19371    +1

Impacted Files
Coverage Δ

internal/database/sqlcommon/chart_sql.go
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 9b787bc...302a9df. Read the comment docs.


ActionView::Template::Error in admin/communication/websites/posts#preview

Error in Osuny
ActionView::Template::Error in admin/communication/websites/posts#preview
no implicit conversion of nil into String
View on Bugsnag
Stacktrace
app/services/osuny/notes.rb:38 - +
app/services/osuny/notes.rb:38 - build_note
app/services/osuny/notes.rb:24 - block in replace_notes!
app/services/osuny/notes.rb:23 - each
app/services/osuny/notes.rb:23 - replace_notes!
app/services/osuny/notes.rb:13 - prepare
app/helpers/application_helper.rb:90 - prepare_notes
app/views/admin/communication/blocks/components/rich_text/_show.html.erb:1 - _app_views_admin_communication_blocks_components_rich_text__show_html_erb___2562104343778793967_219720
app/views/admin/communication/blocks/components/_show.html.erb:11 - _app_views_admin_communication_blocks_components__show_html_erb__4313543132438034948_219700
app/helpers/admin/blocks_helper.rb:18 - block_component_show
app/views/admin/communication/blocks/templates/chapter/_show.html.erb:14 - _app_views_admin_communication_blocks_templates_chapter__show_html_erb__402947063632385416_219660
app/views/admin/communication/blocks/content/_show.html.erb:3 - block in _app_views_admin_communication_blocks_content__show_html_erb__2420278854690063329_219640
app/views/admin/communication/blocks/content/_show.html.erb:2 - _app_views_admin_communication_blocks_content__show_html_erb__2420278854690063329_219640
app/views/admin/communication/websites/posts/preview.html.erb:6 - _app_views_admin_communication_websites_posts_preview_html_erb___2530155890025091126_225740
app/controllers/admin/communication/websites/posts_controller.rb:48 - preview
app/controllers/application_controller/with_locale.rb:19 - switch_locale

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been reopened in Bugsnag
ActionView::Template::Error in Communication::Website::IndirectObject::SyncWithGitJob@elephant

An error linked to this issue has been marked as fixed in Bugsnag
ActionView::Template::Error in Communication::Website::IndirectObject::SyncWithGitJob@elephant


(cloud-merge)  Support to validate TTL keys

Proposed changes
Issue Number: close #xxx

2813
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Please pick the version you prefer for Coq 8.16 in Coq Platform 2022.09

The Coq team released Coq 8.16+rc1 on June 01, 2022.
The corresponding Coq Platform release 2022.09 should be released before September 15, 2022.
It can be delayed in case of difficulties until October 15, 2022, but this should be an exception.
This issue is to inform you that the opam package we are currently testing in Coq Platform CI works fine with Coq 8.16+rc1.
Coq Platform CI is currently testing opam package coq-ext-lib.0.11.6
from official repository https://coq.inria.fr/opam/released/packages/coq-ext-lib/coq-ext-lib.0.11.6/opam.
In case this is the version you want to see in Coq Platform, there is nothing to do for you - please just close this issue.
In case you would prefer to see an updated or an older version in the upcoming Coq Platform 2022.09, please inform us as soon as possible and before August 31, 2022!
The working branch of Coq Platform, can be found here main.
It contains package pick ~8.16+rc1~2022.09~preview1 which already supports Coq version 8.16+rc1 and contains already working (possibly patched / commit pinned) Coq Platform packages.
In case you want to select a different version, please don't close this issue, even after creating the new tag and/or opam package.
We will close the issue after updating Coq Platform.
This is a measure of 'double book keeping' in order to avoid that we ship the wrong version.
In any case, Coq Platform won't be released before this issue is closed!
Thanks!
P.S.: this issue has been created automatically based on CI status.
CC: https://github.com/coq/platform/issues/274

https://github.com/coq-community/coq-ext-lib/tree/v0.11.7

Thanks! I udated coq-extlib to version 0.11.7 in the preparation branch and close now.


[CHALLENGE SUBMISSION] Challenge 05: Logic Apps

Please provide the following information for your submission:
What is your name? (First, Last)
Barbara Forbes
Where is your GitHub Repo ?(Link to your challenge solution)
https://github.com/Ba4bes/SeasonsOfServerless/tree/main/C05-Tteok-guk_for_The_New_Year
What Challenge is this for? (Challenge number between 1 and 7)
5
(Optional) Anything else we should know? e.g., language used, location, blog post, tell us how you solved this solution, including any challenges you faced solving it.
For this challenge I combined Logic Apps and Teams! This makes it a bit harder to share the solution, especially since it was created with the designer. I added the code to the repository and made some gifs of the process in Teams, to give you a bit of the experience :)

thank you for this submission!

thank you for this submission!


(New?) RG353V has issues with ArkOS

Describe the Issue (If applicable)
ArkOS fails to boot from the image most of the time. I've used a few different MicroSD cards, including an official nintendo themed switch card. I've flashed it using the recommended tool a few times. Another unit I bought for someone else booted right away with the same image and tool on their SD card, so I think it might be a hardware revision or something. I saw something about a new screen?
Once it finally gets to the "the partition will now be expanded" part, it starts partitioning and stops at "File system created successfully." After a few more reboots, it gets back to this point and finishing copying/removing files. After that, reboot just has the ArkOS 2.0 (10162023) text and eventually after a few minutes just goes to a black screen. Reboots after that just sit at the ArkOS logo, usually showing a black screen after but loading into emulation station every few reboots. This is before I added any ROMS.
How can the issue be reproduced? (If applicable)
It happens 9/10 times.
What device are you using?
RG353V (Translucent Purple)
What version of ArkOS are you on?

You can find this during the initial boot process right before the Emulationstation loading screen

I cannot get to this but I'm using the latest precompiled image (10/16).
Anything else you'd like to include that may help to review this issue or feature request?
I'm familiar with linux and programming etc so I'd be willing to try any patches/updates/etc to see if it fixes it. Maybe the new release could help? (I couldn't find a new image).

That new DTB improved boot reliability significantly. Most times it loads into Emustation without issue. I only get black screens about every 1/5 boots. Is there a way to turn on debug mode or something and provide any information that would be useful to detect whether it should use the higher or lower clock speed based on that?
Also, will booting into ArkOS at 1.4Ghz cause all subsequent apps launched from it to run at that speed as well?
Thank you for you help and hard work!

Unfortunately no debug without getting a serial cable and soldering the points on the board.  Once the unit gets to a bad state, there's nothing you can do anymore but reboot or power down the device.  That dtb locks the max speed of the entire OS to 1.4Ghz so higher end emulation may suffer.  I suspect there's a power related issue in which some SOC bins need more voltage to run at higher speeds than others.  The chips used on these handhelds are not going to have consistent QC so what works well for one, may not work well for another.  There's been a whole discussion about this in the ArkOS firmware channel within the RetroHandhelds Discord.  You're welcome to join there and review the chat history.  The invite for RetroHandhelds Discord is available below.  You have good proof of the situation in which you brought 2 units yet one runs ArkOS fine and the other doesn't.
https://discord.gg/retrohandhelds

I have the same issue with arkos on rg353vs . After 7-8 reboots finish first boot.Every time i turn on the device needs 3-4 reboots to load and when load arkos after a while freezes.Back to stock OS (this runs very well).

If you're able to see an image on screen on one of the boots, then the issue is not the screen. The issue is that some units can reliably boot ArkOS at the spec speed of 1.8Ghz and some can not. Here's a dtb you can try here to see if it gives you reliable booting. It lowers the max speed to 1.4Ghz. Just unzip it and place the rk3566-OC.dtb file in the BOOT partition overwriting the existing one. The BOOT partition is fat32 so you should be able to access it from a Mac, Windows, or Linux computer to replace that file. Let me know your results.
https://github.com/christianhaitian/arkos/files/13262434/rk3566-OC.zip

I replace the dtb file and arkos works without issues

That'll have to do for now until a better solution is found.  Perhaps I'll eventually get a unit that exhibits this issue so I can further investigate it.  For now, none of my units have this issue.

I just got a new RG353V that wouldn't boot with ArkOS - using this file fixed it for me, maybe it should be merged into the default build?

If you're able to see an image on screen on one of the boots, then the issue is not the screen. The issue is that some units can reliably boot ArkOS at the spec speed of 1.8Ghz and some can not. Here's a dtb you can try here to see if it gives you reliable booting. It lowers the max speed to 1.4Ghz. Just unzip it and place the rk3566-OC.dtb file in the BOOT partition overwriting the existing one. The BOOT partition is fat32 so you should be able to access it from a Mac, Windows, or Linux computer to replace that file. Let me know your results.
https://github.com/christianhaitian/arkos/files/13262434/rk3566-OC.zip

I would like to mention that after ripping my hair out for past 2 days this also fixed the boot up issues on my RG353V. Looks like I'm also one of the lucky owners of these (new) units.

I had this problem in one of my two units, luckily in the second everything worked fine. Jelos or stock I had no problem... don't they ever use 1.8ghz?
As for what it could be, maybe it's just the mediocre dissipation, I'll try a mod to see if this solves it. Could you create a 1.6ghz one?

I would make an effort to swap your device.
It may be something that gets worst over time, as the summer heat arrives.
You might argue that the console is unstable on warm days. Something like that, difficult for them to reproduce.

I had the above issue on my rg353m, changed the rk3566-OC.dtb which solved the stability issues however now my right shoulder button doesn't register a long press :D, as in the button works but in a game like drill dozer for example, where you need to hold it down, it just triggers like a quick press.
Swapped the rk3566-OC.dtb file back, right shoulder button works again, crashes happen again.
Regarding the stability issues, it may well be that it's a poorly binned chip, however I don't get any stability issues in either Jelos or the default Anbernic linux the device came with (just as a point of data).

It is software issue. I'm on the same boat. Other OSs work without an issue. Not sure if they are using different booting method or why arkos is having this problem. Maybe arkos booting method can be changed? Hope it will be resolved somehow as its quite annoying issue. Of course arkos is the best and i don't want to change to other os.

I would agree if I could replicate the issue on any of my 7 RK3566 (RG353V v1, RG353V v2, RG353M v1, 2 RG503 units, RGB30 v1 and RGB30 v2) devices but I can not as of yet . ¯_(ツ)_/¯

I know it's not a supported model, but I was having this intermittent crash/hang on my RG353PS and had swapped in the file you attached (which I believe lowers the clock rate) and haven't had the device hang on me since.

I have a device coming to me soon that has the issue.  Hopefully I will be able to resolve the issue once I can finally replicate it.

I know it's not a supported model, but I was having this intermittent crash/hang on my RG353PS and had swapped in the file you attached (which I believe lowers the clock rate) and haven't had the device hang on me since.

The same with my unit.... I also have a RG353PS and cannot run fine arkos most of the time with random crashes... with the dtb file provided it's rock stable.... I can't compare performances with previous configuration... but I think psp games needs tweaking with the new version of the file...

Have a relatively old RG353V that boots to a black screen frequently. If I tap the power button to sleep/wake a few times then the menu comes up and everything works fine. To my knowledge, the issue didn’t seem to happen on a fresh install. It started when I added a bunch games. Specifically Ports, N64, DC, PSP, and Saturn as I’m testing those first. It feels like a software issue but I’ll try the file that lowers clock speed. If performance suffers as a result then I’ll have to consider JELOS again. I don’t really like JELOS because of how it tries to integrate with RetroArch which conflicts with my preferred configuration. Stock doesn’t let you update RetroArch from what I can tell. ROCKNIX makes you delete Android, no thanks. ArkOS is the most normal option I’ve found besides this damn startup issue. Hope you find a solution that doesn’t sacrifice performance. Thanks for your time and effort.

I have a device coming to me soon that has the issue. Hopefully I will be able to resolve the issue once I can finally replicate it.

Hey, just wondering, were you able to replicate it with that unit? I've been on Jelos ever since but I would still switch over to Ark if that issue was fixed.

I bought an RG353V a couple weeks ago, and am having this boot issue as well. The modified DTB file allows me to boot, but with compromised performance. Hopefully you find a solution soon!

Same here. I bought a 353m and arkos get stuck at boot. Anbernic sent me a new motherboard, but same issue with this new one... I'm really disappointed because I've worked a lot on this build and I can't get a functional second unit...

I did receive a unit that supposedly has the issue but it boots and functions consistently with my samsung and sandisk cards just fine so i still can’t replicate the issue yet.

I did receive a unit that supposedly has the issue but it boots and functions consistently with my samsung and sandisk cards just fine so i still can’t replicate the issue yet.

Does that point to an SD Card compatibility issue?
I'm using this:
"SanDisk 32GB Ultra microSDHC UHS-I Memory Card  - 120MB/s, C10, U1, Full HD, A1, Micro SD Card "

I did receive a unit that supposedly has the issue but it boots and functions consistently with my samsung and sandisk cards just fine so i still can’t replicate the issue yet.

I managed to boot with a Sandisk Ultra Plus 32GB. Fresh install. But when I swap with the Sandisk Extreme 32GB present in my first unit, it can't boot correctly. Maybe some components aren't exactly the same on the two motherboards ? It takes 2s longer to boot with Utra Plus but it's not a big deal ;)

So which sd card is recommend? Sandisk Ultra Plus ? I can buy one and test as my unit has problem with booting

Sandisk Ultra Plus 32GB

imma try this.. where'd you purchase yours from?

So which sd card is recommend? Sandisk Ultra Plus ? I can buy one and test as my unit has problem with booting and currently i'm using Sandisk Ultra card.

sounds like it. looks like Best Buy and Target both stock it..

I'm Europe based, i will look for it in big retailers or buy online

So which sd card is recommend? Sandisk Ultra Plus ? I can buy one and test as my unit has problem with booting and currently i'm using Sandisk Ultra card.

Yes, I tried an ultra plus 32GB and an ultra 256GB. No problem. But ! The second sd card reader doesn't recognize any of my cards :-(
I've got a RGB30 too, and it does not appreciate Sandisk Extreme serie either.

went a bought a "Plus" card, and still not able to boot, but got further along in the process than other cards I've tried.
to summarize..
stock card Kioxia 16gb - hangs at ArkOS logo screen
SanDisk Ultra 32Gb - hangs at ArkOS logo screen
SanDisk Ultra PLUS 32Gb - ArkOS logo for ~10 sec, loading screen with progress bar for ~2 minutes, eventually gets to a black screen where it hangs indefinitely...
it seems like the speed and quality of the card have something to do with it, but for now the stock OS is working ok for me. I also looked into JelOS and apparently its no longer being supported.

It has nothing to do with SD memory. Yes, the modified DTB only reduces the CPU speed to 1.4ghz and this solves the problems in all cases.
Then the problem may be related to some CPUs that are not capable of working at 1.8ghz. Although the question would be. Ambelec and Rocknix do the rk3566 work at 1.8ghz?

For me original rk3566-OC.dtb doesn't work too. With 1.4 Ghz CPU frequency it works, but if you increase frequency in dtb my device stops booting. I've tried to modify dtb file and actually came with some results. If you violate cpu policy and avoid using tcsd4525 power policy to cpu (vdd_cpu),  device actually boots, and the performance didn't suffer. From dmesg logs it seems like device can't find policy for all cpus. but booted succesfully without any problem.
DMESG logs:
`[  182.222522] rockchip-dmc dmc: cpu0 policy NULL
[  182.282531] rockchip-dmc dmc: cpu0 policy NULL
[  182.335829] rockchip-dmc dmc: cpu0 policy NULL
[  182.532567] rockchip-dmc dmc: cpu1 policy NULL
[  182.635863] rockchip-dmc dmc: cpu2 policy NULL
[  182.689148] rockchip-dmc dmc: cpu2 policy NULL
[  182.752578] rockchip-dmc dmc: cpu3 policy NULL
[  183.022583] rockchip-dmc dmc: cpu0 policy NULL
[  183.075864] rockchip-dmc dmc: cpu0 policy NULL
[  183.129231] rockchip-dmc dmc: cpu0 policy NULL
[  183.182571] rockchip-dmc dmc: cpu0 policy NULL
[  183.359161] rockchip-dmc dmc: cpu0 policy NULL
`
I attached modified dts and dtb, maybe this is not a good way to fix that problem, but for me it works flawlessly.
rk3566-OC-fix.zip

This is working, thanks! However i have no sound. I copied and renamed dtb file, should i copy dts file also? How to fix the sound?

This is working, thanks! However i have no sound. I copied and renamed dtb file, should i copy dts file also? How to fix the sound?

Sound might be a problem with Arkos itself. Find option in advanced "fix sound" or something like that

Tried that without success. When i copied back orginal dtb file sound returns so it seems like problem with that new dtb unfortunately

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz

Old fix is now obsolete and not recommended to use.
rk3566-OC.FIXED-v2.zip

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. rk3566-OC.FIXED-v2.zip

Thank you very much friend.- 1.9 is the stable limit that rk3566 can work

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

What changes did you make to get this stable for your unit?

You are hero, sound problem which i described is caused probably because i'm using rg353m with stereo speakers. Hope your file will be adjusted for all devices

Finally I was able to boot with my Sandisk SD this fix.
Sound does not work in built in speakers, I tried with bluetooth speakers and it was ok.

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: [rk3566-OC.FIXED-v2.zip](https://github.com/user-attachments/files/16317347/
What changes did you make to get this stable for your unit?

I 've changed power regulator values. (vdd_cpu)
First, I remove  value. I've found the discussion of rockchip-linux kernel developers, where they make a guess, that this part can be obsolete and unstable, and now actually there is a dts file in Torvalds repo of linux kernel for RK3566, where this value isn't presented. Secondly, I've changed  line to more generic type of regulator "fcs, fan53555”. And actually that's it. In my dtb, name of regulator changed from tcs4525@40 to regulator@40, but that change actually doesn't do anything. Made it, cause seems like rk3566 can have tcs4525 ot sti817 cpu power regulator.

Finally I was able to boot with my Sandisk SD this fix. Sound does not work in built in speakers, I tried with bluetooth speakers and it was ok.

Well, my unit doesn't have that problem. I've got sound problem like yours once, but I've fix it with provided script in options -> advanced -> fix sound
You can try that. If that is not worked for you, well if you can connect to your device by ssh and provide dmesg -k logs, I'd be able to know what exactly the problem is.
And yeah, do you have 353V or 353VS unit?

If i provide you with orginal rg353m file would you be able to do adjustment there ? Hope this can solve problems with sound on stereo devices

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

with this new dtb i can boot my rg353vs finally into arkos, thank you, no sound issue too

Finally I was able to boot with my Sandisk SD this fix. Sound does not work in built in speakers, I tried with bluetooth speakers and it was ok.

Well, my unit doesn't have that problem. I've got sound problem like yours once, but I've fix it with provided script in options -> advanced -> fix sound You can try that. If that is not worked for you, well if you can connect to your device by ssh and provide dmesg -k logs, I'd be able to know what exactly the problem is. And yeah, do you have 353V or 353VS unit?

My device is a RG353M, same as @czapa86 . Did not notice that is fix is only for RG353VS. Also works with 353M version but could not be for it.
Find the attached log
log.txt

If i provide you with orginal rg353m file would you be able to do adjustment there ? Hope this can solve problems with sound on stereo devices

Sure thing! Give me your original dtb, I'll patch it

If i provide you with orginal rg353m file would you be able to do adjustment there ? Hope this can solve problems with sound on stereo devices

Sure thing! Give me your original dtb, I'll patch it

Much appreciated! Attaching original RG353M file.
rk3566-OC-RG353M.zip

@czapa86 @JMarques90 Here you go!
Tested on my RG353V, boots and works fine. And sound work too. The only difference I see in dtbs, is that RG353M have additional line out-l2spk-r2hp in audio codec section, which enables stereo support on devices with RK817 audio chip.
Now I think it should work just fine.
rk3566-OC-353M-FIXED.zip

YOU ARE LEGEND !!! Now indeed sound works. Thank you so much !!!

Hi guys
I've been following this thread with interest.
Do I understand correctly that you now have a working 353M dtb with 1.9ghz?
If you need an official beta tester, please post the 353M dtb here.
Thanks

Worked 😁😁😁😁😁
Finally I can use this mini console.
Thank you @Galaxy13
Thanks to Arkos devs

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

Hey, tried this, seems to be working consistent. If anything changes ill let you know. Thanks for this! :)

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

so ive seen something pop up just now for me, i plugged it in to charge after turnin it on when it was low, no sound now at all. i turn up the system volume too, nothing.

Forgive my ignorance but I also have a 535m
I open the Boot sector on my MicroSD and I can see
rk3566-OC.dtb
rk3566-OC.dtb.bright
I downloaded the Patched version from this threath
rk3566-OC-353M-FIXED.dtb file
Should I just drop this new dtb file in the Boot folder, or rename and replace the  original dtb files for this fix to work?
regards

Hi!
Yes, just rename your rk3566-OC.dtb to something like rk3566-OC-old.dtb, place fixed file and rename fixed file to rk3566-OC.dtb

I went the route of going through Anbernic tech support, and they replaced my RG353V unit for free.
Now I have no problem running ArkOS using the standard dtb file.

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

Thank you. Good news but I was using this and suddenly it went out. Can't you lower 1.8GHz?

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

thank you Good news, but my device started up smoothly but suddenly turned off while in use. I hereby report.

I have been testing adjusted dtb file on 353M and no issues so far. Maybe battery life is a little shorter but really not 100% sure.

Sorry but my RG353V still boots to a black screen occasionally with the v2 dtb.

One thing I can't understand: The stock Linux handles both types of screens without issues. What's their trick? Even incompatible, we should at least be able to extract and implement their timings ...

@czapa86 @JMarques90¡Aquí tienes! Probado en mi RG353V, arranca y funciona bien. Y el sonido también funciona 😄. La única diferencia que veo en dtbs es que el RG353M tiene una salida de línea adicional l2spk-r2hp en la sección de códec de audio, lo que parece habilitar la compatibilidad estéreo en dispositivos con chip de audio RK817. Ahora creo que debería funcionar bien. rk3566-OC-353M-FIXED.zip

Hello! First of all thank you for your great work!
I'm 1-2 days away from receiving a rg353ps and I would like to use ArkOS without problems, if it's not too much trouble could you do me the favour of modifying the .dtb file if I attach it to you so I can make the correct configuration and work at 1.8 (the maximum of series if I read correctly) and with the same modification for stereo sound of the rg353m? thanks again!

@czapa86 @JMarques90¡Aquí tienes! Probado en mi RG353V, arranca y funciona bien. Y el sonido también funciona 😄. La única diferencia que veo en dtbs es que el RG353M tiene una salida de línea adicional l2spk-r2hp en la sección de códec de audio, lo que parece habilitar la compatibilidad estéreo en dispositivos con chip de audio RK817. Ahora creo que debería funcionar bien. rk3566-OC-353M-FIXED.zip

Hello! First of all thank you for your great work!
I'm 1-2 days away from receiving a rg353ps and I would like to use ArkOS without problems, if it's not too much trouble could you do me the favour of modifying the .dtb file if I attach it to you so I can make the correct configuration and work at 1.8 (the maximum of series if I read correctly) and with the same modification for stereo sound of the rg353m? thanks again!

Hello! Yeah, no problem. But I think you can easily use RG353M file. It works fine on my RG353V, since their hardware is pretty much the same. Unless it is v2 screen. If that so, I'll try to build another dtb for RG353V/VS/M/PS with v2 screen or preferably universal file.

353M file will work perfectly fine on rg353ps :)

@czapa86 @JMarques90¡Aquí tienes! Probado en mi RG353V, arranca y funciona bien. Y el sonido también funciona 😄. La única diferencia que veo en dtbs es que el RG353M tiene una salida de línea adicional l2spk-r2hp en la sección de códec de audio, lo que parece habilitar la compatibilidad estéreo en dispositivos con chip de audio RK817. Ahora creo que debería funcionar bien. rk3566-OC-353M-FIXED.zip

Hello! First of all thank you for your great work!
I'm 1-2 days away from receiving a rg353ps and I would like to use ArkOS without problems, if it's not too much trouble could you do me the favour of modifying the .dtb file if I attach it to you so I can make the correct configuration and work at 1.8 (the maximum of series if I read correctly) and with the same modification for stereo sound of the rg353m? thanks again!

Hello! Yeah, no problem. But I think you can easily use RG353M file. It works fine on my RG353V, since their hardware is pretty much the same. Unless it is v2 screen. If that so, I'll try to build another dtb for RG353V/VS/M/PS with v2 screen or preferably universal file.

RG353M file will work perfectly fine on RG353PS

Thank you for your answer! indeed I tried the RG353M file and it worked without problems, thanks for the clarification!

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

Was having issues with ArkOS freezing on startup ~50% of the time on my RG353V, happy to confirm that this fixed the issue and the unit has had zero issues since.  Thanks!

After some digging, I actually find problem with CPU voltage regulator, now DMESG didn't throw any error and lscpu actually shows that now my unit can capable of 1.9 GHz in ArkOS  Old fix is now obsolete and not recommended to use. Use this version instead: rk3566-OC.FIXED-v2.zip

This is great! Finally fixed my 353vs, it's booting normally and so far no random freezes happening!
Didn't have sound right after booting, but it worked fine after the "audio fix" in configuration>advanced


refactor: add thin transaction and implement in mempool

This change is

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

Project coverage is 50.81%. Comparing base (808f1f6) to head (bd2a037).

Additional details and impacted files
@@                                            Coverage Diff                                            @@
##           mohammad/end-to-end-test/implement-simple-test-with-network-component     #103      +/-   ##
=========================================================================================================
+ Coverage                                                                  50.44%   50.81%   +0.37%
=========================================================================================================
  Files                                                                         17       17
  Lines                                                                        561      549      -12
  Branches                                                                     561      549      -12
=========================================================================================================
- Hits                                                                         283      279       -4
+ Misses                                                                       270      262       -8
  Partials                                                                       8        8

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


Add a Gitter chat badge to README.rst

striglia/pyramid_swagger now has a Chat Room on Gitter
@striglia has just created a chat room. You can visit it here: https://gitter.im/striglia/pyramid_swagger.
This pull-request adds this badge to your README.rst:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Available at https://gitter.im/striglia/pyramid_swagger (linked off the badge). We'll see how this goes...might be a nice alternative to bothering with a Freenode.


Adjustment POAP Allocation Factors

Based on community feedback we are slightly adjusting factors used for the POAP allocations.
Changes include:

reducing "Kaffee 24/9" by 50%. This is effectively done by multiplying all other categories *2.
reducing the allocation for "SC Deployment 24h Special Mainnet" to factor 2.

Overview new factors:

Factor
Event
Token ID

4
Kaffee 23/7
4437

4
Kaffee 30/7
4813

4
Kaffee 6/8
5182

2
SC Deployment 24h Special Mainnet
6102

2
SC Deployment 24h Special xDai
6103

4
Kaffee 27/8
6457

100
CowStar August
6739

4
Kaffee 3/9
6887

2
Kaffee 10/9
7330

2
Kaffee 17/9
8092

1
Kaffee 24/9
8824

100
CowStar September
9533

40
UX Participants
11743

100
Picasso Winner
12420

100
CowStar October
12654

20
Coffee Challenge Winner 5/11
13346

20
Coffee Challenge Winner 19/11
15296

20
Squid
15311

20
Coffee Challenge Winner 26/11
15739

100
CowStar November
18465

20
Coffee Challenge Winner 17/12
21839

100
CowStar December
22201

16
Alpha Mainnet
[Dune query]

4
Alpha Gchain
[Dune query]

Sorry forgot to update alpha traders. Just a moment.


Set default memory allocator

We improved memory allocator #168.
So, CuPy should use memory pool by default.

Are they intended to be set by users, or just internal implementation?
Don't we need accessor functios to set them?

Can users turn off memory pool?
I mean that memory.malloc_managed is public, but memory._malloc is private.

I add useful method.

Can users turn off memory pool?
I mean that memory.malloc_managed is public, but memory._malloc is private.

Pelase use cupy.cuda.set_allocator().

Is it bad idea to publish memory._malloc ?
I felt cupy.cuda.set_allocator(memory.malloc) is easier to understand because this PR changes the default to be memory pool allocator. cupy.cuda.set_allocator() looks like it changes the allocator to be default, which is the memory pool allocator now.

OK, I will fix.

Pros.

Users can use it.
Cons.
malloc and alloc are confusing. I think It needs a new name.
The user can directly create a Memory object. This is not difficult.

OK

issued https://github.com/cupy/cupy/issues/524


Create Intro Video about the Summit

This would be used on the website and to be shown OWASP Chapter meetings
See https://twitter.com/jonathanmarcil/status/832733228251230208

we should ask past summit participants to create a quick video (recorded on phone of computer) about their experiences and what they look for in the next Summit
try to make it as a professional as the Kickstarter intro videos (use same format)

presentation is on the 23rd (Thursday) so we don't have much time to create the first version of this video


(18)+NEW SEX@XXX@VIDEOS]* Russian Girls MMS Viral Video Russian Actress Private MMS Leaks Original Video On Social Media

37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video Russian Girls MMS video Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Russian Girls MMS video Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
[-wATCH-]—Russian Girls MMS video ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMS video ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMS video Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
Russian Girls MMS video Original Video video took the internet by storm and amazed viewers on various social media platforms.Russian Girls MMSvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoRussian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter
Russian Girls MMSvideo Original Video video oficial twitter
L𝚎aked Video Russian Girls MMS video Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
Russian Girls MMS video-video
.
.
.
.
.
.
37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video Russian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Russian Girls MMSvideo Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
[-wATCH-]—Russian Girls MMSvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMSvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMSvideo Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
Russian Girls MMSvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.Russian Girls MMSvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoRussian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter
Russian Girls MMSvideo Original Video video oficial twitter
L𝚎aked VideoRussian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.
.
.
.
.
.
.37 seconds ago.....
[🌐 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🟢==►► 𝖶𝖠𝖳𝖢𝖧 𝖭𝖮𝖶]
[🔴 𝖢𝖫𝖨𝖢𝖪 𝖧𝖤𝖱𝖤 🌐==►► 𝖣𝗈𝗐𝗇𝗅𝗈𝖺𝖽 𝖭𝗈𝗐]
L𝚎aked Video Russian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter Telegram
[-wATCH-]—Russian Girls MMSvideo Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
[-wATCH-]—Russian Girls MMSvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMSvideo ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]—Russian Girls MMSvideo Video Original Video LinkRussian Girls MMSvideo Video Viral On Social Media X Trending Now
Russian Girls MMSvideo Original Video video took the internet by storm and amazed viewers on various social media platforms.Russian Girls MMSvideo, a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked VideoRussian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter
Russian Girls MMSvideo Original Video video oficial twitter
L𝚎aked VideoRussian Girls MMSvideo Original Video Viral Video L𝚎aked on X Twitter..
.
.

cxvd


[BUG] Using "fork" plugin to duplicate an output stream will cause CC errors

Hi Thierry @lelegard
Bug description:
I need to use the fork plugin to duplicate an output stream 2, 3 or 4 times, but I noticed that as soon as the fork plugin was used, it was causing CC errors in all the created TS outputs.
So, I reduced the number of fork plugins to one only, so that I could easily compare it with the IP output plugin.
Even with only one fork plugin, the number of CC errors keeps increasing in the multicast output.
However, it is not the case with the IP output plugin, which works as expected.
How to reproduce:
The two commands I'm using to provide strong evidences are the following:
With fork: tsp --verbose -I file videos\service16_17.ts --infinite -P regulate -P continuity --fix -P fork "tsp -O ip <IP_ADDRESS>:10001 -l <IP_ADDRESS> --packet-burst 7 --enforce-burst" -O drop
With IP output: tsp --verbose -I file videos\service16_17.ts --infinite -P regulate -P continuity --fix -O ip <IP_ADDRESS>:10001 -l <IP_ADDRESS> --packet-burst 7 --enforce-burst
Expected behavior:
Using fork plugin should not create CC errors in all forked outputs.
Errors and logs:
No errors. The logs would be the standard ones when continuity errors is detected:
 continuity: packet index: 484,120, PID: 0x026C, missing 13 packets
* continuity: packet index: 484,296, PID: 0x0277, missing 1 packets
* continuity: packet index: 484,301, PID: 0x026C, missing 15 packets
* continuity: packet index: 484,406, PID: 0x0000, missing 1 packets

Environment:

OS: Tried both on Linux and Windows
OS version: Debian 11 Bullseye, Windows 10
TSDuck full version: Latest 3.31-2740
Installation type: Official binary

Additional information:

Hi @moving-digital
The plugin fork creates a pipe with the forked process and passes all TS packets. By design, no packet can be dropped or modified in the processing the fork plugin.

Hi @lelegard
Unfortunately, I've tried by creating up to 10 independent tsp processes, each of them outputting a multicast TS.
The multicast address and ports are the same than the ones used with the fork process.
Reading the same 10 multicast on the receiver, there is not a single CC error.
On top of that, I can confidently say my system does not have any load issue (10% CPU, 20% network) and there is not a single conflict.
Let me know if you would like to get access to the TS stream, but the issue can easily be reproduced with any TS, on any system.

To all, I recently noticed a frequent use / abuse of the "bug" tag. Declaring that something is a bug presupposes an in-depth technical analysis and the evidence of a buggy behavior, preferably with precise references to source code. Observing an unexpected behavior is not a valid reason to report a "bug". Remember that 99% of unexpected behavior is due to incorrect usage of a product.

Hi @lelegard
Sorry for using the bug label.
I really don't understand why using the normal ip output plugin works, while the same command with a single fork duplicating the output, followed by a "-O drop" doesn't work as expected.
I would be extremely grateful if you could have a look at it, by just trying the two very simple commands I posted in my first post.

Hi all.
Hi @moving-digital .
I can help.
You can share the command line I can apply it to my case.
I have TSDuck installed on Linux/Ubuntu.
I can use satellite sources and or TS recorded file.
I can even give Remote access to test your self.
Have a good day.

I have the same issue. Running my script with output to IP only runs smoothly. if i add a fork to set a 2nd output to a dektec device, i get a smoth picture via dektec but the ip stream gets blurry over time. (about 5 Min after starting the stream)


Consider the following color codes

BLUE: - The person is "susceptible" but doesn't have it. (Negative antigen-test AND negative antibody-test.)
GREEN: - The person has passed an antibody-based test. (Independently recovered)
ORANGE: - The person has "unknown" status or pending test results
RED: - The person is "infected" and is under quarantine.

Yep, that's what we were going to implement, but as I said we are about to pivot away from contact tracing and leave that part to ZeroTrace, SafePaths, Apple/Google, etc.
I'm actively contributing to the first two so that they can have proper background functionality on Android.


Fix typos.

Thanks Ward for catching this. I have no idea how I made the same typo twice, glad to have it fixed up.


Possible error in GenerationalIndexArray remove method.

Hello, I think there might be an error on line 185 of src/generational_index.rs (commit id 977090a).  The comparison is checking equality of the value of e.generation against itself.

That is indeed an error!  Thanks!
Just so you know, this project was adapted from another larger project, and there was an error in translation.
The purpose of this project was just to demonstrate a particular "querying" API style, not really for serious use.  However, there's no reason to leave such a bug, so thanks for that.
I think I need to add a README that warns people away for using this for anything other than educational use and API inspiration, though.

You're welcome.  After watching your RustConf 2018 talk, I came here to learn more.  I did find this project to be helpful.


Problem with Albums and Photos options

These two queries stopped work with options:

This project uses jsonplaceholder behind the scenes. That website is currently down for some reason. Everything should be up and running again as soon as that gets resolved.

Hi @nedko-slavov , it should be working again now.
Apologies for the inconvenience and thanks for your report.


[Question] So confused. How is this different from Framework7?

I dunno if this is the appropriate channel to ask this but how does this differ from Framework7?

Hello JPBuenaventura,
This framework is a kind of wrapper that automatizes most of the boilerplate job you need to do when using Framework7 + vue.
It includes webpack configuration for easy development and some options to make an easier starter point forn an app. For example easy firebase integration or automatic route creation.
The most similar and 'vanilla' would be the framework7 Vue Webpack Template.
This channel is more appropiate for bugs or requests regarding the framework. I don't know if there is any other channel to ask questions regarding usage.
I hope my answer provided some help.
Sorry for my English!

That makes perfect sense. I'm new to Framework7 and I intend to use it to develop hybrid apps.
I used this (App Framework) and the vanilla Webpack + Vue and I found that using this instead of the vanilla one increases the productivity.
Thank you for the response :)


Cannot run phpunit tests with MySQL

Description:
MySQL tables are not visible when running phpunit tests via docker-compose exec workspace .... or docker-compose run --rm workspace ....
Expected Behavior:

Context information:
Output of git rev-parse HEAD
4f274e3d86e1a209161790514f11acd4eef7bde9

Output of docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:21:11 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:29:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker-compose version
docker-compose version 1.25.5, build 8a1c60f6
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020

System info: Mac, Windows or Linux. Include which disto/version
macOS Catalina 10.15.4 (19E287)

Steps to reproduce the issue:

Run docker-compose exec workspace /var/www/app/vendor/bin/phpunit '/path/to/my/file.php'
Run docker-compose exec workspace bash then app/vendor/bin/phpunit '/path/to/my/file.php'

Actual result
After 1st step (weird result)
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

EEE                                                                 3 / 3 (100%)

Time: 6.37 seconds, Memory: 40.50 MB

There were 3 errors:

1) path/to/my/file.php::a_test_case
Illuminate\Database\QueryException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'homestead.logins' doesn't exist (SQL: select `users`.*, (select `id` from `logins` where `user_id` = `users`.`id` order by `created_at` desc limit 1) as `last_login_id` from `users` where `is_admin` = 1)

........................
........................
........................

ERRORS!
Tests: 3, Assertions: 0, Errors: 3.

After 2nd step (expected behavior)
PHPUnit 7.5.20 by Sebastian Bergmann and contributors.

F.F                                                                 3 / 3 (100%)

Time: 4.33 seconds, Memory: 46.50 MB

There were 2 failures:

1) Tests\Unit\HasWalletTest::it_should_have_seller_pending_balance
Failed asserting that '50.0' matches expected 36.5.

/var/www/app/tests/Unit/HasWalletTest.php:26

2) Tests\Unit\HasWalletTest::it_should_have_correct_pending_balance_of_seller_with_bought_wager
Failed asserting that '1050.0' matches expected 1036.5.

/var/www/app/tests/Unit/HasWalletTest.php:74

I misconfigured my docker, reinstalling does help


Add ports for libmikmod and allegro5

I've got ports for two libraries here.  Both libraries are configured to provide as many features as possible.
The libmikmod works as intended.
The allegro5 port, however, stumps me in two ways that keep this PR from being ready to merge:
Error when building in Debug mode (for dynamic builds)
When I try to build allegro5:x86-windows-dbg (i.e. as a DLL in debug mode), I get this error in the installation process after the build is complete:
CMake Error at cmake_install.cmake:40 (file):
  file INSTALL cannot find
  "C:/Users/Administrator/Code/vcpkg/buildtrees/allegro5/x86-windows-dbg/lib/Debug/allegro-debug.pdb".

There are PDB's, but they're in C:/Users/Administrator/Code/vcpkg/buildtrees/allegro5/x86-windows-dbg/lib (note the lack of a Debug directory).  Any ideas why I'm getting this?
D3D9EX support
I assume that CMake will find this if it's actually available, but it doesn't seem to be installed on my system.  Is this available with the vcbuildtools installer?
Also:
Unrelated: Disabled Features
The following allegro5 features I've disabled because their dependencies are not available in vcpkg (if that changes, possibly by my own hand, I will update the port):

ModAudio support (needs libdumb which doesn't have a port right now)
Opus support (libopus is available but libopusfile is not)
Tremor support (not available on vcpkg)

@JesseTG,
Thanks for having already signed the Contribution License Agreement. Your agreement has not been validated yet. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Anyone?

x86-windows-dbg/lib/Debug/  <- *.pdb
x86-windows-dbg/lib/ <- *.lib
ok install

@Voskrese I don't understand, can you elaborate?

@JesseTG если файлы Debug с расширение pdb лежат в папке x86-windows-dbg/lib/Debug, а так же   *.lib в папке x86-windows-dbg/lib/ тогда инсталяция проходит без ошибок
проблема в скрипте порта

If the Debug files with the extension .PDB lie in the x 86 folder-windows-dbg Debug/lib/, as well as the x 86 folder *.lib-windows-dbg/lib/then installation runs without errors
the problem in the script of the port

для проверки можете перейти в каталог где лежит файл инсталяции cmake cmake_install.cmake
посмотреть его содержимое
для проверки выполнить cmake.exe -P cmake_install.cmake

to verify directory can go to the installation file where lies the cmake cmake cmake_install '. '
view its contents
to test run ' cmake.exe-P cmake_install. cmake '

I'll try later today, thank you.

@Voskrese I double-checked the paths in my portfile.cmake.  I still don't see what could be causing the error.  I think it might be occurring within vcpkg_install_cmake.  Or do you mean that allegro5 itself is doing something wrong or unusual in its CMakeFile.txt?

You know what, I'm just going to make a patch.  Fingers crossed.

Okay, I'm good.  Fixed, merge at will!

Great, thanks for the PR!

https://github.com/liballeg/allegro5/blob/master/cmake/FindOpus.cmake
if(OPUS_INCLUDE_DIR)
opusfile.h
 find_path(OPUS_INCLUDE_DIR opusfile.h PATH_SUFFIXES opus)
 MSVC built opus may be named opus_static
opus.h
opus_x86-windows\include\opus
    opus.h
    opus_custom.h
    opus_defines.h
    opus_multistream.h
    opus_types.h

find_library(OPUS_LIBRARY
как патч opusfile.h -> opus.h
но я не проверял

D3D9EX
https://github.com/liballeg/allegro5/blob/master/cmake/FindDirectX.cmake
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Microsoft SDKs\\\\Windows\\\\v7.0;InstallationFolder]")
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Microsoft SDKs\\\\Windows\\\\v7.0A;InstallationFolder]")
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Microsoft SDKs\\\\Windows\\\\v7.1;InstallationFolder]")
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Microsoft SDKs\\\\Windows\\\\v7.1A;InstallationFolder]")
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Windows Kits\\\\Installed Roots;KitsRoot]")
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Windows Kits\\\\Installed Roots;KitsRoot81]")

WINSDK_ROOT_DIR= - SDK v7.0 - 8.1 либо DXSDK_DIR=
find_component(DINPUT dinput.h dinput8)
find_component(D3D9 d3d9.h dinput8)
find_component(D3DX9 d3dx9.h d3dx9)
find_component(DSOUND dsound.h dsound)
find_component(XINPUT xinput.h xinput)

как вариант
check_winsdk_root_dir("[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows Kits\\Installed Roots;KitsRoot10]")


Implement 'yes' in R

I would like to work on this. Do you require me to sign a Contributor License Agreement?

Just sent me a PR.


Static bpftrace binary?

Hi there @michalgr @danielocfb! Do we have public instructions around how to build bpftrace for Android statically? If not, any chance that could be documented as part of this project?
thanks a lot

Hi Jesus, I believe https://github.com/danielocfb/bpftrace_local_manifest contains all the information you'd need.

Hi @jeez!
The easiest way to get static bpftrace binaries for android is to download the CI builds, for example from here: https://github.com/facebookexperimental/ExtendedAndroidTools/actions/runs/4785564960 (bpftrace-android-*). You should be able to build static binaries on your own, just run the following command in the provided Docker environment: make bpftrace STATIC_LINKING=true LLVM_BPF_ONLY=true

+1 on @michalgr's method. The bpftrace_local_manifest is hard to maintain since the c++ runtime's ABIs are not 100% compatible on different versions' LLVM.

thanks, all, that worked! I will be in touch.


#158049365 Update readme

What does this PR do?
This PR will update the README file with useful API endpoints
Description of Task to be completed?

Update README with endpoints
Add Authors
Add Prerequisites

How should this be manually tested?

Clone repository

git clone git@github.com:DennisWanjiru/maintenance-tracker.git

cd maintenance-tracker/

git checkout ch-update-readme-157778725

Open README.md file in  visual studio code
Press ctrl+shift+v to preview the readme

Any background context you want to provide?
None
What are the relevant pivotal tracker stories?
#158049365

Pull Request Test Coverage Report for Build 65

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.278%

Totals

Change from base Build 60:
0.0%

Covered Lines:
65

Relevant Lines:
72

💛  - Coveralls


Integrate with Airflow-astronomer channel in OSS

Integrate with Airflow-astronomer channel in OSS
This is for early access private beta

We should add sources in the answer for Nov 15 release

We have created separate DAGs for prod and dev for deployment. Named schema in weaviate as Docs_prod and Docs_dev accordingly.

This is done: https://apache-airflow.slack.com/archives/C03T0AVNA6A/p1698254331358519?thread_ts=1698244221.771919&cid=C03T0AVNA6A
We have done beta release on OSS slack.


highes elevation at night

Hello
would it be possible to calculate like
if moon is up then
moon highest Elevation yy  will be at Azimut xxx at dd.mm.yyyy hh.mm.s
have a nice day
vinc

Should this be calculated for a day or for what period of time is it intended?
What I can just imagine is trying all times for a period of time (loop) and determining the highest value of the elevation.
But I would only build something like this into the node if it is really needed by many, because it costs computing time.  On the other hand, something like this can also be built directly with Node-RED on-board resources and the moon-pos node.

Partly implemented in 2.0.1

In Version 2.0.1 the highes elevation of the moon is calculated, but only if moon rise and set times available.


Update docker versions to support Senzing API 2.0.0

See https://github.com/Senzing/docker-compose-demo/issues/101

Pull Requests:

https://github.com/Senzing/docker-web-app-demo/pull/38


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_9287a6b8-2829-430d-9138-1ec67db89d01/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_9287a6b8-2829-430d-9138-1ec67db89d01.git

Docs Build status updates of commit a10f47e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-06-17-08-50-19 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-06-17-08-50-19

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Funky error when you have read access but not write access and trying to do a write action

When you do not have either read or write access to an item, you will get this nice error
item_replace_files('538c80abe4b08f500f8fcc50', files = "out_xml/00_metadata.xml")

Error: Item not found for ID=538c80abe4b08f500f8fcc50. Either the item does not exist or the item is secured and requires authentication to access.

If you only have read access but not write, you will get this:
 Error in strsplit(headers(x)[["content-type"]], "[;]") :
  non-character argument

which is kind of a head-scratcher. If we're able to throw a useful error here it would probably save people some time.

Should be handled here. https://github.com/USGS-R/sbtools/blob/f35d7daee45db7e4502d8afa03d410744a331d7b/R/REST_helpers.R#L119
Will get to this next time I open up the project.

Would be good to make sure whatever fix goes in that it still creates extensions for FGDC compliant xml files.

I'm finally getting around to looking at this and can't reproduce. I'm getting a full on failure when it's trying to item_rm_files() and can't because I don't have permission.
Is this something you can try to reproduce easily?

Nevermind -- I got there.


feat(analysis/topology/topological_space): define T0 spaces, T4 spaces, connected and irreducible sets and components

TO CONTRIBUTORS:
Make sure you have:

[ ] reviewed and applied the coding style: coding, naming
[ ] for tactics:

[ ] added or adapted documentation in tactics.md
[ ] write an example of use of the new feature in tactics.lean

[ ] make sure definitions and lemmas are put in the right files
[ ] make sure definitions and lemmas are not redundant

For reviewers: code review check list

@digama0 Should I put this shorter proof of t2 implies t1?
⟨λ x, is_open_iff_forall_mem_open.2 $ λ y hxy,
let ⟨u, v, hu, hv, hyu, hxv, huv⟩ := H y x (mt mem_singleton_of_eq hxy) in
⟨u, λ z hz1 hz2, ((ext_iff _ _).1 huv x).1 ⟨mem_singleton_iff.1 hz2 ▸ hz1, hxv⟩, hu, hyu⟩⟩

Your proofs of exists_irreducible and exists_connected use Zorn's lemma. I guess this is not necessary in the connected case, and possibly also in the irreducible case (I don't know much about irreducible sets), because the connected component is unique. It can be defined as the union of all connected sets containing the target set.

The irreducible case corresponds to minimal prime ideal, which shouldn't be unique.


Add validation logic for bdc.json & control.json

this is to make sure the format of the bdc.json and control.json are parsable and exit gracefully if the format is not as expected.

BDC support in ADS is being deprecated so closing all related issues.


RLOS tool does not add symbology correctly if user deletes features from Project.gdb and re-runs tool.

If the user runs the tool correctly the first time and gets good results symbolized by Visible/Non-Visible (Green/Red/Other) and then deletes the results from the TOC and deletes the feature classes from the Project.gdb and re-runs the tool, the outputs are that are added to the TOC are then symbolized generically.

Expected Behavior

In a current sesion if a user deletes the feature classes from the project.gdb the tool will continue to symbolize as expected
Current Behavior

The user deletes the results for the Project.gdb and re-runs the tool, the outputs are that are added to the TOC are not symbolized generically.
Possible Solution

Steps to Reproduce (for bugs)

1.Run RLOS get and get good results symbolized correctly.
2.Delete results from TOC
3.Delete feature classes from project.gdb
4.Re-Run the tool.
Context

Your Environment

Version used: ArcPro 1.4 (7190)
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your project:

@topowright @dhagens Outside of what you guys were seeing this is all I could replicate.

@migueldls this has been fixed in the latest build. I have tested this and I do not see the same results. @nfeuerstein, @migueldls is out of the office until Jan 3, may I close this out being that I have verified that it is no longer an issue?

Absolutely.

@nfeuerstein thank you


GUI tests: use setText instead of write #53

Fixes #53
Speeds up tests about 2m 50s to 2m 10s.

@yl-coder for your review and merging

.setText doesn't really go thru the GUI layer and setText is just modify the underlying value of the GUI node. If we assume that JavaFX UIControl is working, i think it is fine.

.write() is painfully slow. Let's use setText by default. We can use write in some cases, especially if some event handling happens after every keystroke (e.g. live search).

I'm just thinking of extreme case. For example, If there is parent node consuming the key event. This method will pass the test cases, but the behaviour in reality may be different.
We can speed up the write method by implementing our own.

That kind of 'show stopper' bugs are usually noticed even without automated tests. We can make most of the tests use .setText() but a few tests use .write().
Another thing we can do is to use .setText() for the first n-2 chars and use write for the last 2 chars.

Or use write for the first few letters and set text for the remainder. For now, let's merge this. We can add a refinement later.

Right.


NEW DBField validation

Issue https://github.com/silverstripe/silverstripe-framework/issues/11391
To share the email validation logic between the EmailField::validate() and DBEmail::validate() I've simply used the symfony email constraint
There are now 3x different validate() methods

FormField::validate(Validator $validator): bool
DataObject::validate(): ValidationResult
DBField::validate(): ValidationResult [new]

Validator should really be renamed to FormValidator for clarify. A (Form)Validator has a ValidationResult as a property
TODO:

When intantiationing EmailField, set a flag if there's an associated DBField (connected to DataObject, not just an arbitary "ModelField"), and if so, skip EmailField::validate()
private static $required on DataObject and validate their existance DataObject::validate(). No need to use RequireFields()/CompositeValidators for this. Should deprecate possibly RequiredFields when used in DataObject::getCMSCompositeValidator(), or just deprecate DataObject::getCMSCompositeValidator() entirely

Closed in favor of https://github.com/silverstripe/silverstripe-framework/pull/11402


image not visible in Menu file and addition of scroball to all HTML files in Repo

Bug [image not visible in Menu file] :

Feature[addition of scroball to all HTML files in Repo]:

PLease assign this under GSSOC.

@sunny0625

Can you please assign me this issue for gssoc'24

@sunny0625 please assign me this issue

@sunny0625 please assign me this issue


2742: etc doesn't compile on Solaris because it uses flock()

Suggested fix for Solaris

@akolb1 Sorry. But the project is really called etcd. Can you please update the commit message to
pkg/fileutil: add filelock support for solaris


New package: Microsoft.RemoteToolsforVisualStudio2022 version 17.0.34916.146

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm not sure if that's an oversight (not to remove from the URL provided), or if it's intentional. I'll let @edwardskrod respond.

Please add a PackageUrl - it should be easy to navigate to the InstallerUrl from the PackageUrl.

@stephengillie cc @denelon @edwardskrod
I updated it to use most of the fields that were used when this package was removed: https://github.com/microsoft/winget-pkgs/pull/95986/files
The problem now is that the InstallerUrl always grabs the latest so when that url is updated with a newer installer the sha256 probably will no longer match - I don't have a direct link to any versions except for the ones removed. It seems like maybe the VS team would need to support that, but I don't have the context as to why this tool was removed.
If there's no steam on this, I suppose I can just use these manifest files directly in our repo(s) but I imagine there is a use case for having the remote tools installed without a VS install on the remote machine.

The problem now is that the InstallerUrl always grabs the latest so when that url is updated with a newer installer the sha256 probably will no longer match[.]

This is a common problem. We call this a "vanity URL" as these are frequently used for marketing purposes. We have an automated process that checks the hash for some of these, and opens removal and addition PRs to update if changed.

/azp run

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual
'manifests\m\Microsoft\RemoteToolsforVisualStudio2022\Latest', expected
'manifests\m\Microsoft\VisualStudio\2022\RemoteTools\latest'

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual
'manifests\m\Microsoft\RemoteToolsforVisualStudio2022\Latest', expected
'manifests\r\RemoteToolsforVisualStudio2022\latest'

Sorry to keep getting caught on the path. The the \RemoteToolsforVisualStudio2022 folder will need to be moved into \m\Microsoft. (The process for doing so is immaterial - can be a file copy or a new file on a system with a filesystem and Git installed - or a modification from within the GitHub editor.)

@stephengillie The manifests are already under the \m\Microsoft path, seems like the validation is failing on the identifier - I'll try switching it from RemoteToolsforVisualStudio2022 to Microsoft.RemoteToolsforVisualStudio2022

@stephengillie just checking in on this PR, were there any action items on me or just needs another review?

I believe we're still waiting on approval from @edwardskrod.

We haven't forgotten this PR. There is some internal discussion happening. I'll update once we come to a decision.

[Policy] Blocking-Issue

This PR is using an older version of the schema. I'm going to go ahead and close this for now. Once the manifest has been updated, either create a new PR or re-open this one.