Content security policy

Slick slider is not CSP compliant https://en.wikipedia.org/wiki/Content_Security_Policy
====================================================================

No fiddle because it requires server headers
====================================================================
Steps to reproduce the problem

Enable CSP on your server
Add slick

====================================================================
What is the expected behaviour?
Beautiful and safe website
====================================================================
What is observed behaviour?
CSP stopped execution because of this:
        _.$slides.each(function(index, element) {
            $(element)
                .attr('data-slick-index', index)
                .data('originalStyling', $(element).attr('style') || '');
        });

        if(_.options.rows > 1) {
            originalSlides = _.$slides.children().children();
            originalSlides.removeAttr('style');
            _.$slider.empty().append(originalSlides);
        }

        if (_.$slides) {

            _.$slides
                .removeClass('slick-slide slick-active slick-center slick-visible slick-current')
                .removeAttr('aria-hidden')
                .removeAttr('data-slick-index')
                .each(function(){
                    $(this).attr('style', $(this).data('originalStyling'));
                });

setting inline style!

====================================================================
More Details

Which browsers/versions does it happen on?
All browsers supporting CSP
Which jQuery/Slick version are you using?
Present in slick/slick.js in master branch
Did this work before?
Nope?

Whats the fix here? Sanitizing the originalStyling data ?

I'm suprised that noone in web knows about https://en.wikipedia.org/wiki/Content_Security_Policy
It's here for few years already, and it completly solves XSS problems.
Fix is to stop using inline styles .attr('style', something).

Yeah that's not gonna happen

Ok so it looks like using the CSS object model to store and reapply those styles is the actual fix. If anyone cares to PR that, I'll gladly take it.

For what purpose you need inline styles?

For literally everything having to do with dynamically positioning elements?

After reading the spec, it's not about having inline styles it's about how they are applied. CSS object model is compliant"

Well depends on definition of inline :) I was using terminology from spec.
If you could provide some introduction for my frontend dude I think that he could contribute in near future (of course only if you want to be compilant ;)).

If those are the only offending lines, it shouldn't be too hard to refactor into compliance. What's the best way to get a CSP error thrown, so I can reproduce this?

You need to add csp header on your server, for example:
content-security-policy: default-src 'self'
and then load document returned by that server. You will see error in console saying
Refused to apply inline style because it violates the following Content Security Policy directive (...).
I am not sure if that are only offending lines. I just checked for
"attr('style', ...)" in source (afaik it directly modifies the DOM, and forces browser to reload styles from attribute thus rejecting style as inline).
Csp also forbids inline javascript (in <script> tags or in attributes, for instance onclick="sayHi(event);"). I don't see any eval, so that's good.

Did some ctrl + f for 'attr' in the source and looks like the only lines where the style attribute is targeted are 516 [816],(https://github.com/kenwheeler/slick/blob/master/slick/slick.js#L816), and 884
And if it's only the application of styles using the attr (and not retrieving/removing the value), then 884 is the only culprit.
After googling the subject a bit, I didn't find any way to directly take the properties in a style attribute value and apply them using the CSS Object Model, so I wrote wrote a function to parse it, here.
@kenwheeler didn't want to PR it in case you'd already made headway on the issue/had set up a testing environment, but let me know if the above thinking makes sense to you and would like me to tackle it.
Thanks!

I think that you are fighting problem that does not exist ;)  If csp is on there won't be style attribute, so script should do nothing (not even attempt to set/clear style attribute). I think that just reading style attribute does not trigger csp violation.

Oh hmm, maybe I'm confused--I thought: a) the implementation of slick with the CSP enforced was throwing an exception; and b) that exception could be circumvented through the use of CSS Object Model, as opposed to the use of the style attribute.

Yes, that''s right. But most styles are applied using CSSOM already (css() jquery method). Slick uses style attribute only for managing original styles - originally present on that attribute (am I right?). The only problem arises when slick tries to clear style attribute (which is not there, because CSP in on).

Okay, ye, thanks for clarifying.
So here's my understanding:
There are three lines in the js (detailed here), where the jQuery attr method is use in connection with styles. The reason they exist at all is so that if a slick needs to be unslicked, any inline styles that existed on the elements prior to a slick init, can be reapplied when the slick is destroyed so it looks as nature intended.
The three lines correspond to: 1) retrieving the styles, and storing them in the slick object; 2) removing the existing styles, in preparation for the application of slick's inline styles (applied, as you say, using the CSSOM); and 3) reapplying the original styles back if the slick destroy method is called.
My guess at this point is that the offending lines were just the removal and reapplication of the styles, and not simply the retrieval/storage of them. Assuming that is the case, I'm thinking we'll need one function for the removal of the styles, where I guess we parse the styles in the attribute and set the value to initial, and then another function to reapply, which I believe is at least partially satisfied by what I wrote in the codepen.
If the retrieval and storage of initial styles using the attr method violated the CSP policy, then I'm not sure what, if it exists, is the compliant way to do that.
Sounds like you're going to get deep on this in the near term, which is awesome. Let me know if all that makes sense to you and your front-end colleague.
Thanks!

@ShadowDancer how'd this go for y'all?

Closing: dormant


Resolve issues found when testing with a qif file generated by Moneywell

Hi,
I was trying to use a .qif file generated by Monewell (see https://moneywell.app ), and ran into a couple issues.  It looks like it will sometimes put strings into the check number field, and it looks like there was a bug in your code to add new classes from a transaction - it was returning a list but then trying to add them to a dict with the update() method.  I suspect this latter is because you changed it be a dict in the outer code but missed updating the inner code to return a dict.
Anyway, with these changes I can now import my wife's file successfully, and they seemed generally applicable so I thought you might be interested in pulling them in.
-Matt

Thank you for bringing this up! Accepted and merged.


please implement programtically accept input from mouse and keyboard from pynput

please implement programtically accept input from mouse and keyboard from pynput

please implement programtically accept input from mouse and keyboard from pynput

please implement programtically accept input from mouse and keyboard from pynput

please implement programtically accept input from mouse and keyboard from pynput


Drop dependency on deriving-aeson; update to Aeson 2

Dropping the deriving-aeson dependency keeps compilation times low enough, while still allowing the upgrade to Aeson 2.
Some changes were made to ensure compatibility with Aeson 1.x and 2.x.
Compilation times:

Master: ~3 min
Aeson 2.0: ~6 min
Aeson 2.0 without deriving-aeson: ~3 min

Weird that CI doesn't run. We should definitely make that work since this PR requires compilation of a number of dependencies (with CI we'll have those in the cachix cache).

A workaround to fix CI is to follow this guide to allow running a workflow manually for a branch.


chore(package): update expression-expander to version 5.3.0

https://greenkeeper.io/

Current coverage is 44.53% (diff: 100%)

Merging #27 into master will not change coverage

@@             master        #27   diff @@
==========================================
  Files             7          7
  Lines           119        119
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             53         53
  Misses           66         66
  Partials          0          0

Powered by Codecov. Last update 102c692...3abdbe6


Fix edpm_compute target

Commit fde88988e8e50db9b81f4e51f732d473781cc7fd
introduced the following error:
+ touch ''\''/tmp/edpm-firstboot-extra'\'''
touch: cannot touch "'/tmp/edpm-firstboot-extra'": No such file or directory

due to an extra quotes around the default value of the new env var.
It is removed now.

/lgtm

recheck
2024-08-26 08:05:24.510755 | controller |     + ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /home/zuul/.ssh/id_rsa<EMAIL_ADDRESS>'bash /tmp/repo-setup.sh'
2024-08-26 08:05:24.510769 | controller |     Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
2024-08-26 08:05:24.510783 | controller |     Repository 'openstack-17.1-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 08:05:24.510796 | controller |     Repository 'rhceph-6-tools-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 08:05:24.510810 | controller |     Repository 'fast-datapath-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 08:05:24.510824 | controller |     The server rate limit has been exceeded, please try again later.
2024-08-26 08:05:24.510839 | controller |     + rv=70
2024-08-26 08:05:24.510855 | controller |     + rm -rf -- /tmp/tmp.1z16v3RQCu
2024-08-26 08:05:24.510873 | controller |     + exit 70
2024-08-26 08:05:24.510909 | controller |     make: *** [Makefile:474: standalone_deploy] Error 70

recheck
same thing different job:
2024-08-26 11:57:56.613618 | controller |     + ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /home/zuul/.ssh/id_rsa<EMAIL_ADDRESS>'bash /tmp/repo-setup.sh'
2024-08-26 11:57:56.613629 | controller |     Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
2024-08-26 11:57:56.613639 | controller |     Repository 'openstack-17.1-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 11:57:56.615160 | controller |     Repository 'rhceph-6-tools-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 11:57:56.615176 | controller |     Repository 'fast-datapath-for-rhel-9-x86_64-rpms' is enabled for this system.
2024-08-26 11:57:56.615182 | controller |     The server rate limit has been exceeded, please try again later.
2024-08-26 11:57:56.615188 | controller |     + rv=70
2024-08-26 11:57:56.615197 | controller |     + rm -rf -- /tmp/tmp.llYXYFYziv
2024-08-26 11:57:56.615203 | controller |     + exit 70
2024-08-26 11:57:56.615209 | controller |     make: *** [Makefile:474: standalone_deploy] Error 70


EAST-2418

NOTE: we could leave the connection_properties value 'undef' and pass it via Hiera config for each evn as well.
Update dbconfig.xml
Adding the following to the  section in the dbconfig.xml file:
defaultRowPrefetch=200
What this does is change the default value (10) to 200. It helps with sprint operations performance when there is a large number of sprints.
Please check for more details: https://jira.atlassian.com/browse/JSWSERVER-20618.
Add thread name to access logs:
Adding the "%I" (uppercase i) parameter to the Access Log valve in /atlassian-jira/conf/server.xml.
Example:
<Valve className="org.apache.catalina.valves.AccessLogValve"                   pattern="%a %{jira.request.id}r %{jira.request.username}r %t %I "%m %U%q %H" %s %b %D "%{Referer}i" "%{User-Agent}i" "%{jira.request.assession.id}r""/>

I think we should do this like this instead:
https://github.com/bt-lemery/puppet-jira/commit/cb8727aa0fb9da19113c1da74bad7532aeb6cb9a
Should make it easier to get back in to upstream.
Leave connection_properties null by default and have it accept a hash of options which we loop through in the template.  If you want to set defaultRowPrefetch to be 10 by default in our environments you still can via hiera.  Other people may or may not have set that value (or additional ones) via the GUI and probably wouldn't appreciate our suddenly changing it on them.
To set your connection_properties just update the 'jira' class declaration like
  class { ::jira:     ...     connection_properties => {       'defaultRowPrefetch' => '10',       'foo'                            => 'bar',     }   ...   }
Will render a template like:
`

default
default
oracle10g

jdbc:oracle:thin:@hostname.com:1234/jiradb
oracle.jdbc.OracleDriver
username
password
30
200
30000
60
defaultRowPrefetch=10
foo=bar
true
300
select 1 from dual
60000
300000
true
false

`


JBREM000200 error when trying to deploy to remote domain with RBAC enabled

Hi,
we are starting to use Wildfly 8.1.0 setup as a domain with RBAC, and we're unable to get the maven plugin to successfully connect to it from our CI server.
I tried with two different users that have assigned different roles:

Deployer
SuperAdmin (just to see if it's a permission issue, didn't help though)

The pom.xml looks something like this:
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>1.0.2.Final</version>
<executions>
   <execution>
      <id>deploy</id>
      <phase>install</phase>
      <goals>
         <goal>deploy</goal>
      </goals>
   <configuration>
      <domain>
         <server-groups>
            <server-group>${DEPLOY-ENV}</server-group>
         </server-groups>
      </domain>
      <filename>
            ${project.build.directory}/deploy/${BUILD.ARTIFACT.NAME}
      </filename>
      <force>true</force>
      <name>${deploymentName}</name>
      <hostname><IP_ADDRESS></hostname>
      <port>9990</port>
      <username>phdeploy</username>
      <password>supersecret</password>
   </configuration>
   </execution>
</executions>
</plugin>

The error output is:
[INFO] --- wildfly-maven-plugin:1.0.2.Final:deploy (deploy) @ ph-deployment ---
Aug 07, 2014 9:14:22 AM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.2.Final
Aug 07, 2014 9:14:23 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.2.Final
Aug 07, 2014 9:14:23 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.3.Final
Authenticating against security realm: ManagementRealm
Aug 07, 2014 9:14:24 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 26.372s
[INFO] Finished at: Thu Aug 07 09:14:24 CEST 2014
[INFO] Final Memory: 17M/318M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.2.Final:deploy (deploy) on project ph-deployment: Could not execute goal deploy on /home/tubuild/.hudson/jobs/GenericDeployment/workspace/target/home/tubuild/.hudson/jobs/GenericDeployment/workspace/target/deploy/suchkundenportal.war. Reason: I/O Error could not execute operation '{
[ERROR] "operation" => "read-attribute",
[ERROR] "address" => [],
[ERROR] "name" => "launch-type"
[ERROR] }': java.net.ConnectException: JBAS012174: Could not connect to http-remoting://<IP_ADDRESS>:9990. The connection failed: Authentication failed: the server presented no authentication mechanisms
[ERROR] -> [Help 1]

Accessing the management interface with curl works, though:
$ curl --digest -L -D - http://<IP_ADDRESS>:9990/management --header "Content-Type: application/json" -d '{"operation":"read-attribute","address":[{"host":"slave-dev08"},{"server":"dev08-s01"}],"name":"server-state","json.pretty":1}' -u phdeploy
Enter host password for user 'phdeploy':
HTTP/1.1 401 Unauthorized
Connection: keep-alive
WWW-Authenticate: Digest realm="ManagementRealm",domain="/management",nonce="n7ZmV3fpyBoNMTQwNzM5NzY5NjcwNcwqjtowKi3FU1XErGUk0Cw=",opaque="00000000000000000000000000000000",algorithm=MD5
Content-Length: 77
Content-Type: text/html
Date: Thu, 07 Aug 2014 07:48:16 GMT

HTTP/1.1 200 OK
Connection: keep-alive
Authentication-Info: nextnonce="9CGwwkViihENMTQwNzM5NzY5NjcwNiWN5MY8pEKD/XkBROQunpo="
Content-Type: application/json; charset=utf-8
Content-Length: 55
Date: Thu, 07 Aug 2014 07:48:16 GMT

{
    "outcome" : "success",
    "result" : "running"
}

Given that using curl seems to work fine, I suspect an issue with the maven plugin.
Any ideas?

Sorry for the extremely long delay. Is this still an issue?

I'm going to close this. If this is still an issue could you please refile it on here https://issues.jboss.org/browse/WFMP?


Column actions should support facet by compound primary keys

On https://latest.datasette.io/fixtures/compound_three_primary_keys the column action menu doesn't display for the pk1, pk2 and pk3 columns (because they are primary keys) even though faceting by them is actually useful.
Refs #98

The code that skips the "facet by this" menu option for primary key columns could take into account if there are multiple primary keys.
https://github.com/simonw/datasette/blob/141544613f9e76ddb74eee38d6f8ee1e0e70f833/datasette/static/table.js#L91-L98


Proposal: Datepicker

Hello,
Native date picker are not the same on every browser, I personally use Litepicker and it will be good to have one, maybe with this package.

Same as https://github.com/symfony/ux/issues/15

Same as https://github.com/symfony/ux/issues/15

Ho sorry, I didn't see it. But litepick is deprecated for litepicker.

Ho sorry, I didn't see it. But litepick is deprecated for litepicker.

I personally use this one which seems to offer many possibilities : https://flatpickr.js.org/
But generally I agree with the idea. It remains to be seen which library to rely on

@bastien70 this one looks nice 👍🏻

@bastien70 I used to use Flatpicker but quicky moved to litepicker  which offers the same behaviors and more.
It has some plugins  (maybe more later).

I feel like we could have support for multiple frontend libraries (ux-datepicker-flatpicker, ux-datepicker-litepicker, ...) but with the same form type and core options, in the same way to Notifier component works. If someone wants to chat about that and contribute, I'd be happy to give a hand :) !

Found an other interesting library : https://air-datepicker.com/

Actually a date range picker would be awsome as it's a nightmare to find one not abandonned and qualitatif.

@johndodev As I previously said, AirDatePicker is quite neat and actively maintained (until now 😄)


nightfox-gtk-theme: unstable-2023-05-28 -> 0-unstable-2024-06-27

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I would like to use -l on install.sh but it works on HOME folder, so it is not possible to work on libadwaita linking.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4206


heap-check cause program hangs

On my RetHat, I link my program with tcmalloc and set environment HEAPCHECK=normal to run it. As a result, the program hangs. I use pstack to find reasons. I found it locks on dl_iterate_phdr, as described in 64-BIT ISSUES in the doc.
How can I do or is there any way to walkaround? thx.
my system info:
uname -r
2.6.32.-358.el6.x86_64
lsb_release -a
LSB Version:          :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID:       RedHatEnterpriseServer
Description:           Red Hat Enterprise Linux Server release 6.4 (Santiago)
Release:                 6.4
Codename:            Santiago

Make sure you have latest gperftools and then try running with TCMALLOC_STACKTRACE_METHOD=libgcc environment variable. This should make heap checker work.

Sorry for feeding back so late. But adding TCMALLOC_STACKTRACE_METHOD=libgcc does not improve my situation. The program still hangs on start-up.

In addtion, the traceback is:
#0  0x0000003bf220e054 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x0000003bf22093a3 in _L_lock_892 () from /lib64/libpthread.so.0
#2  0x0000003bf2209287 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x0000003bf1f25c8b in dl_iterate_phdr () from /lib64/libc.so.6
#4  0x00007fe21b480d63 in _Unwind_Find_FDE () from /usr/local/gcc/lib64/libgcc_s.so.1
#5  0x00007fe21b47d956 in uw_frame_state_for () from /usr/local/gcc/lib64/libgcc_s.so.1
#6  0x00007fe21b47ea30 in uw_init_context_1 () from /usr/local/gcc/lib64/libgcc_s.so.1
#7  0x00007fe21b47f2a8 in _Unwind_Backtrace () from /usr/local/gcc/lib64/libgcc_s.so.1
#8  0x00007fe21c0ede7a in ?? () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#9  0x00007fe21c0ee232 in ?? () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#10 0x00007fe21c0eb519 in ?? () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#11 0x00007fe21c0ec0ab in ProfileHandler::SignalHandler(int, siginfo*, void*) () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#12
#13 0x0000003bf2209281 in pthread_mutex_lock () from /lib64/libpthread.so.0
#14 0x0000003bf1f25c8b in dl_iterate_phdr () from /lib64/libc.so.6
#15 0x00007fe21b480d63 in _Unwind_Find_FDE () from /usr/local/gcc/lib64/libgcc_s.so.1
#16 0x00007fe21b47d956 in uw_frame_state_for () from /usr/local/gcc/lib64/libgcc_s.so.1
#17 0x00007fe21b47f2d8 in _Unwind_Backtrace () from /usr/local/gcc/lib64/libgcc_s.so.1
#18 0x00007fe21c0edeca in ?? () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#19 0x00007fe21c0ee2c6 in ?? () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libprofiler.so.0
#20 0x00007fe21be9f078 in MallocHook_GetCallerStackTrace () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libtcmalloc.so.4
#21 0x00007fe21be92180 in NewHook(void const*, unsigned long) () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libtcmalloc.so.4
#22 0x00007fe21be9ebe6 in MallocHook::InvokeNewHookSlow(void const*, unsigned long) () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libtcmalloc.so.4
#23 0x00007fe21beac244 in tc_newarray () from /home/lidajun/ldjdev/main/dev/server/thirdpart/lib/libtcmalloc.so.4
#24 0x0000000001472ea9 in std::basic_string<char, std::char_traits, std::allocator >::_Rep::_S_create(unsigned long, unsigned long, std::allocator const&) ()
#25 0x0000000001473b5b in std::basic_string<char, std::char_traits, std::allocator >::_Rep::_M_clone(std::allocator const&, unsigned long) ()
#26 0x0000000001473c00 in std::basic_string<char, std::char_traits, std::allocator >::reserve(unsigned long) ()
#27 0x0000000001473ff6 in std::basic_string<char, std::char_traits, std::allocator >::append(unsigned long, char) ()
#28 0x000000000115bb33 in google::protobuf::internal::WireFormatLite::ReadString(google::protobuf::io::CodedInputStream*, std::basic_string<char, std::char_traits, std::allocator >) ()
#29 0x000000000118d5e3 in google::protobuf::FieldDescriptorProto::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream) ()
#30 0x000000000118e6b5 in google::protobuf::DescriptorProto::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream*) ()
#31 0x0000000001193a77 in google::protobuf::FileDescriptorProto::MergePartialFromCodedStream(google::protobuf::io::CodedInputStream*) ()
#32 0x000000000115aac6 in google::protobuf::MessageLite::ParseFromArray(void const*, int) ()
#33 0x000000000119719a in google::protobuf::EncodedDescriptorDatabase::Add(void const*, int) ()
#34 0x0000000001161469 in google::protobuf::DescriptorPool::InternalAddGeneratedFile(void const*, int) ()
#35 0x00000000012af86e in GtReq::protobuf_AddDesc_GtReq_2eproto() ()
#36 0x00000000014906e6 in __do_global_ctors_aux ()
#37 0x000000000044dca8 in _init ()
#38 0x0000000007f4a1c8 in ?? ()
#39 0x0000000001490665 in __libc_csu_init ()
#40 0x0000003bf1e1ec70 in __libc_start_main () from /lib64/libc.so.6
#41 0x000000000044fed1 in _start ()
it seems that it is the intializationg of protobuf cause the problem.

TCMALLOC_STACKTRACE_METHOD=libgcc does not work with cpu profiler. Your program is running with both cpu profiler enabed and heap profiler enabled.
If you need to run with both, then the only really safe option is using frame pointers. If you need to run just cpu profiler, then frame pointers or libunwind should work. With libunwind having chance of deadlocking. If you need just heap profiler, then all stack tracing options should work. But IMHO libgcc should be more reliable than libunwind.

Em, yeah, now it works. Thanks for detailed explanation.


update docker version to 18.06

Issue #, if available:
Updating the docker version installed by default to 18.06
https://alas.aws.amazon.com/ALAS-2019-1156.html
Description of changes:
Updated the default docker version to fix https://alas.aws.amazon.com/ALAS-2019-1156.html
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks @OpenSourceZombie  !


Wrangler preview can fail if browser has HSTS set for "localhost"

🐛 Bug Report
I am observing a bunch of errors after running wrangler preview --watch. Preview is not auto-updating on code change.
Environment

operating system: macOS High Sierra 10.13.6
browser: Google Chrome Version 76.0.3809.100 (Official Build) (64-bit)
output of rustc -V: command not found
output of node -v: v8.11.4
output of wrangler -V: wrangler 1.2.0

Steps to reproduce
Run wrangler preview --watch
What did you expect to see?
🌀  Detected changes...
🌀  Detected change during cooldown...
🌀  Cooldown over, propogating changes...
✨  Built successfully, built project size is 2 KiB.
👷  Updated preview with changes

What did you see instead?
🌀  Detected changes...
🌀  Detected change during cooldown...
🌀  Cooldown over, propogating changes...
✨  Built successfully, built project size is 2 KiB.
👷  Updated preview with changes
[2019-08-19T19:36:53Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:04Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:15Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:26Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:37Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:48Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:37:58Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:38:09Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:38:20Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:38:31Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:38:42Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:38:53Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:04Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:15Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:26Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:37Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:48Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:39:59Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:40:10Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:40:21Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:40:32Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.
[2019-08-19T19:40:43Z ERROR ws::handler] WS Error <Http(Token)>: Invalid byte where token is required.

It seems like something is trying to connect to the wrangler websocket server and passing in bytes that don't make sense. the local websocket is using http, so if an extension was forcing https that could cause an error of this type.

Figured this one out. The Invalid byte errors come from ws-rs trying to interpret an SSL handshake as a plain HTTP handshake.
If you run into this issue, you can go into chrome://net-internals/#hsts and put localhost in under "Delete domain security policies" and click delete. This will stop your browser from forcing https on the websocket connection and fix the errors.
Unfortunately, we can't get a certificate for localhost as we don't own the hostname, so there's no way to support https for the websocket.
I think we can prevent this from happening again by switching the UI to connect to <IP_ADDRESS> instead of localhost, since HSTS isn't a thing on IP addresses.

Fixed in latest UI release, previewer now connects using <IP_ADDRESS> instead of localhost.


CMakeList - MIOpen Dependencies

MIOpen Dependencies should be removed from RPP.
-- AMDGCN assembler: MIOPEN_AMDGCN_ASSEMBLER-NOTFOUND

@LokeshBonta can you look at this issue

@kiritigowda  Created a PR

#30 merged.


Screenshot not updated

the screenshot at point 1 in the list is not updated.
this is the new look of the UI.

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

ID: 183a8242-3c94-8a80-6d36-85c608790a25
Version Independent ID: 2d8728c3-3662-27a3-6cd4-2c88b08f7847
Content: Merge or append on-premises and cloud data sources - Power BI
Content Source: powerbi-docs/connect-data/service-gateway-mashup-on-premises-cloud.md
Service: powerbi
Sub-service: powerbi-gateways
GitHub Login: @arthiriyer
Microsoft Alias: arthii

Thanks for your comment, @R1k91. This issue has been assigned to the doc author for review.

Thanks for your help and suggestion. We've updated that screenshot.


Update Isuru-Tharanga.md

participation details added

Hi, you needed to add this to a new page,
I've done that for you, see http://owaspsummit.org/Participants/remote/Isuru-Tharanga.html

Hi, Thank you very much for the support.


Custom validation of object properties not showing error next to field

Schema:
{
    'type': 'object',
    'properties': {
        'my_prop': {
            'type': 'string',
            'helpText': 'Some help text.',
            'required': True
        }
    }
}

Custom validation inside model:
def clean(self):
  error_map = ErrorMap()
  key = 'my_prop'
  url = self.config[key]
  try:
      URLValidator()(url)
  except ValidationError:
      error_message = _('URL is invalid')
      error_map.set(coords=[key], msg=error_message)
      raise JSONSchemaValidationError(
          error_message,
          error_map=error_map
      )

Tests:

submitting the form with no values - PASS

submitting the form with data that would fail the validation - FAIL

Expected result:

the custom error message is shown next to the field in the same way as the required validation

Versions:

django-jsonform: 2.21.5
django-semantic-admin: 0.4.0 (tried without as well and same effect)
django: 5.0
python: 3.12.1

The only thing I can think of is that coords=[key] isn't correct but the docs don't cover this simple case (they focus on an array with an object inside) and all the other ways I've tried didn't work.

Doing this inside a model's clean method isn't possible because then the validation will be handled by the model (not the json field). So the model doesn't pass the error_map object over to the json field.
What we want to do is to make this validation at the field level. So that field can catch the exception early and use the error_map.
So, you are required to create a custom form for this and set a custom validator on the json field. See docs: https://django-jsonform.readthedocs.io/en/latest/guide/validation.html#creating-a-form

Awesome, thanks for clarifying!


Vendor folder is missing angular-mocks and angular-ui-router to run unit tests

I was looking at add a feature to your awesome pagination directive. My first step for this was to get the existing unit tests up and running on grunt. When I ran the tests they failed with two warnings saying:
Running "karma:unit" (karma) task
WARN [watcher]: Pattern "C:/Work/angularUtils/vendor/angular-mock/angular-mock.js" does not match any file.
WARN [watcher]: Pattern "C:/Work/angularUtils/vendor/angular-ui-router/release/angular-ui-router.js" does not match any file.

I managed to dig up these files and get the unit tests passing but it might be handy if these were included in your vendor folder on GitHub.
Keep up the awesome work!

Hi,
Thanks for that - actually the vendor folder should probably be omitted altogether from the repo, and we should instead rely on bower install to populate it. Looks like the bowerfile is incomplete anyway - it doesn't include jQuery, which is used in the unit tests.
I'll mark this as one to fix next time I get a bit of time.


Improve Preview Feed Experience

Per https://github.com/wojtpl2/ExtendedXmlSerializer/issues/182#issuecomment-388785324 it would be useful to append packages with a suffix or some identifier that differentiates it from existing versions so that new downloads and subsequent installs are successful.

I am thinking we should get into the habit of updating the version after we deploy, and that should fix this problem.
So for now, we should update the dir.props file to 2.1.14 but do not tag until we are ready to deploy to nuget.  That way we have 2.1.13 on our public feed, and 2.1.14 on our private feed.  The different versions should keep this caching issue from occuring.
What do you think, @wojtpl2?

I don't mind.
But I wonder how do this problem is solved by other libraries like BenchmarkDotNet.

Good question. :)
Here's BDN's preview feed:
https://ci.appveyor.com/nuget/benchmarkdotnet
Currently, the version there is <IP_ADDRESS>5 and was released yesterday.
The public version is 0.11.1.  So, I am thinking any version that is higher than the public feed version will do the trick.
Are you able to modify build numbers with appveyor?  Otherwise I think a simple increment will do.  We'd have to update the process from:

Update version
Tag and push

To:

Tag and push
Update version (for preview feed)


OSError: Multiple exceptions: [Errno 61] Connect call failed ('::1', 5432, 0, 0), [Errno 61] Connect call failed ('<IP_ADDRESS>', 5432)

Describe the bug
Clean install on MacOS running Docker Desktop 4.15. For reasons I'm unable to figure out, streamlit, portfolio create, etc. are unable to connect to PostGres.
I've verified Docker image started, PostGres is running, and no errors are present in logs, but Liu will not successfully connect.

Desktop (please complete the following information):

MacOS Monterey
12.2.1

@wmelton is that log from you docker?!

@amor71 no, that's from your package attempting to connect to the postgres instance launched via docker compose at run time.

@wmelton after you run liu quickstart there are details at the end. among it is to run environment variables, which set the port to 5400, your example is looking for port 5431 which makes me think we didn't follow all steps, and hence you can't connect to the Postgres running on the docker.

@amor71 where?
+--------------------+
| setting up samples |
+--------------------+
Downloading https://raw.github.com/amor71/LiuAlgoTrader/master/examples/quickstart/tradeplan.toml to /Users/user/Documents/Dev/alpaca/liu_samples/...
Downloading https://raw.github.com/amor71/LiuAlgoTrader/master/examples/quickstart/vwap_short.py to /Users/user/Documents/Dev/alpaca/liu_samples/...
Downloading https://raw.github.com/amor71/LiuAlgoTrader/master/examples/quickstart/momentum_long_simplified.py to /Users/user/Documents/Dev/alpaca/liu_samples/...

creating environment variables script
setup completed successfully.

+---------------+
| what's next?  |
+---------------+

Congratulations, Liu Algo Trader is ready to go!
From here, you can either run the back-testing UI, or read the docs.
The full documentation is available here: `https://liualgotrader.rtfd.io/`.

The restored database includes data for the first week and half of Oct 2020.
You may now run a back-testing sessions for these days, as well as
analyze an existing trading session.

To experience Liu Algo Trading for the first time:
1. change your working directory to the sample directory /Users/wesmelton/Documents/Dev/alpaca/liu_samples ('cd /Users/wesmelton/Documents/Dev/alpaca/liu_samples'),
2. run the env-vars script ('source env_vars.sh'),
3.`streamlit run https://raw.github.com/amor71/LiuAlgoTrader/master/analysis/backtester_ui.py`
4. On the app selection select the 'analyzer` app
5. copy and paste the batch-id '2398380c-5146-4b58-843a-a50c458c8071' and press <enter>

Thank you for choosing Liu Algo Trading Framework.

@amor71 so it looks like the env_vars.sh script does set it up, however, I'm pretty sure the liu_samples folder only gets created if you tell the quickstart prompt to include samples. Might be a worthy update to create the env_var.sh file in the root of the project.
After running env_vars.sh the issue is resolved. Thanks!


Attention❗ Typo Mistake

Hey @Ayush7614,
Please fix the typo mistake highlighted in the image

Let me resolve this issue.

Let me resolve this issue.

Why not ??


survey plugin docs

Thanks!! It looks like there are still some minor tweaks that need to be made. I wonder if there is a better way to convey the nested parameters. I worry that having questions and prompt on the same level is confusing because it seems like this should work:
var trial = {
  type: 'survey-text',
  questions: { ... }, // not totally clear what goes inside this
  prompt: // this should be nested in questions...
}

Maybe the description for the questions parameter needs to be a lot longer, and include all the information about the nested parameters?

Ok I'll work on making it more descriptive. I just thought that the
examples toward the bottom of the docs would clarify what questions is
supposed to have.
On Thu, Jul 27, 2017 at 3:13 PM, Josh de Leeuw<EMAIL_ADDRESS>wrote:

Thanks!! It looks like there are still some minor tweaks that need to be
made. I wonder if there is a better way to convey the nested parameters. I
worry that having questions and prompt on the same level is confusing
because it seems like this should work:
var trial = {
type: 'survey-text',
questions: { ... }, // not totally clear what goes inside this
prompt: // this should be nested in questions...
}
Maybe the description for the questions parameter needs to be a lot
longer, and include all the information about the nested parameters?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jspsych/jsPsych/pull/455#issuecomment-318459278, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANcI-40Wet-MD7D43TxNdsC2OkW-XKoeks5sSOFogaJpZM4OltI3
.

Yep, those definitely help a lot. I think we can clarify further.


[OPPRO-112] CI: Enable TPC-H functionality testing

Note: Q7, Q13, Q16 are currently executed due to Parquet source issue


chores: cleanup for PR

Alright, would be in the next implementation

Can you get it done between today and tomorrow?

yes ofcourse


Build interactive playground version!

This one is non-critical and for long down the road... but this is very cool:
http://playground.tensorflow.org/
And I wonder if we can build anything remotely like this sort of sandboxed playground interface :)?

Good idea!

Yeah this is pretty awesome.

Closing this for now


Flutter Android Alarm Manager is not firing events as expected when screen is off

Steps to Reproduce
Run the Flutter official example app "Android Alarm Manager": https://github.com/flutter/plugins/tree/master/packages/android_alarm_manager/example
with the modification that AndroidAlarmManager.oneShot is called directly after its finished, so we have a continuous one after another flow of oneShot calls:
  static Future<void> callback() async {
    print('Alarm fired!');

    // Get the previous cached count and increment it.
    final prefs = await SharedPreferences.getInstance();
    int currentCount = prefs.getInt(countKey);
    await prefs.setInt(countKey, currentCount + 1);

    // This will be null if we're running in the background.
    uiSendPort ??= IsolateNameServer.lookupPortByName(isolateName);
    uiSendPort?.send(null);

    // ------> Here is the only modification: triggering alarm again
    await AndroidAlarmManager.oneShot(
      const Duration(seconds: 10),
      // Ensure we have a unique alarm ID.
      Random().nextInt(pow(2, 31)),
      callback,
      exact: true,
      wakeup: true,
    );
    // End of modification
  }

Expected results:
AndroidAlarmManager.oneShot is being fired every 10 seconds after first start.
Actual results:
In emulator and when real device is debugged using USB - everything works well. However on a real device with the screen turned off (and no USB debugging) - AndroidAlarmManager.oneShot calls are not fired properly (strangely delayed or not fired at all after first one).
This issue is probably related to this one: https://github.com/flutter/flutter/issues/39115
I don't think it matters on which physical device I'm running, but its Android version is 10.
Versions:
Everything latest: Flutter and Android Alarm Manager.

hI @alemoi
Using official example using modification in release mode with screen off without cable and usb debugging off
  static Future<void> callback() async {
    print('Alarm fired!');

    // Get the previous cached count and increment it.
    final prefs = await SharedPreferences.getInstance();
    int currentCount = prefs.getInt(countKey);
    await prefs.setInt(countKey, currentCount + 1);

    // This will be null if we're running in the background.
    uiSendPort ??= IsolateNameServer.lookupPortByName(isolateName);
    uiSendPort?.send(null);

    await AndroidAlarmManager.oneShot(
      const Duration(seconds: 10),
      // Ensure we have a unique alarm ID.
      Random().nextInt(pow(2, 31)),
      callback,
      exact: true,
      wakeup: true,
    );
  }

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-1.0.pre, on Mac OS X 10.15.5 19F96, locale en-GB)
    • Flutter version 1.19.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 456d80b9dd (3 weeks ago), 2020-05-11 11:45:03 -0400
    • Engine revision d96f962ca2
    • Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (3 available)
    • macOS      • macOS      • darwin-x64     • Mac OS X 10.15.5 19F96
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.61

• No issues found!

Can you please provide your flutter doctor -v? This could be device specific, which device you tested on?
Thank you"

Dear @TahaTesser, thanks for the reply!
I still can reproduce it on several devices (all Android 10), don't think doctor information will tell you anything. Reproduction scenario:

Have the reoccurring oneShot alarm as described before. But set the Duration to 60 seconds for easier counting (in both oneShot calls).
Start the "Android Alarm Manager" and some default Android Stopwatch timer, so you can verify the results. And start them both one after each other.
Just put the phone aside with screen off.
For me on any device, for example, after 15 minutes on Stopwatch, I see around 7 alarms fired in "Android Alarm Manager", and it should be 15 instead.

That's basically it. Again, setting oneShot to 60 seconds just simplifies counting.

@alemoi
Thanks for detailed steps, i can definitely reproduce this now

flutter doctor -v
[✓] Flutter (Channel dev, 1.19.0-4.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.19.0-4.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 2f7a59a8da (3 days ago), 2020-06-05 03:44:02 -0700
    • Engine revision d17c84e7af
    • Dart version 2.9.0 (build 2.9.0-13.0.dev 02915ec5ce)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.45.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (4 available)
    • SM M305F   • 32003c30dc19668f • android-arm64  • Android 10 (API 29)
    • macOS      • macOS            • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server • web-server       • web-javascript • Flutter Tools
    • Chrome     • chrome           • web-javascript • Google Chrome
      83.0.4103.97

• No issues found!

@TahaTesser my pleasure :) Hope it helps moving this hot topic of background jobs further :)

I'm also facing the issue, when the app screen is off too long, alarm manager is delay 5 mins to 30 mins to execute, the problem is not alerting at exact time.

It may be related to Android doze mode. Doc here states this :

The following restrictions apply to your apps while in Doze:

Network access is suspended.
The system ignores wake locks.
Standard AlarmManager alarms (including setExact() and setWindow()) are deferred to the next maintenance window.

If you need to set alarms that fire while in Doze, use setAndAllowWhileIdle() or setExactAndAllowWhileIdle().
Alarms set with setAlarmClock() continue to fire normally — the system exits Doze shortly before those alarms fire.

You could try with :
allowWhileIdle: true,
exact: true

or just :
alarmClock: true

Im facing an issue with alarms that androidAlarmManager never handle over  doze mode even i used setAlarmClock().
Android Document says:"Alarms set with setAlarmClock() continue to fire normally — the system exits Doze shortly before those alarms fire."
Also i checked the plugin codes  in android_alarm_manager-0.4.5 17 version,
with parameters ( wakeup: true, rescheduleOnReboot: true, alarmClock: true), AndroidAlarmManager.oneShot() func is returning setAlarmClock() with RTC_WAKEUP clock from native side.
Below you can find how im calling oneShot();
AndroidAlarmManager.oneShot(Duration(milliseconds: nextAlarmTimeInMilliseconds), item.id, _notificationCallBack,
    rescheduleOnReboot: true,
    alarmClock: true ,
);

Everythings seems working when phone awake however when phone enter doze mode, alarms not firing on exact time. Whenever the phone exit doze mode by moved or touched by someone,  alarms are firing with delay.

You could try the fix suggested in https://github.com/flutter/flutter/issues/30555

@klitzouille not working with that fix neither any of the suggestions listed above, so basically this plugins is useless if your phone enters the doze mode?

I did a little digging in the plugin code, and I found out that it uses Android's JobIntentService, scheduled through JobScheduler to execute the dart code provided in the callback.
Doc here says that any task scheduled with JobScheduler can be delayed by the system as it sees fit (doze mode, strong memory pressure, ...). I don't think there is a way to ensure your task will be triggered when in doze mode with this plugin.
Google's alarm app uses a ForegroundService instead of a JobIntentService to achieve that, so it may work for you as well, but you will have to code in Java/Kotlin for this part.

Hi @alemoi
Thanks, @klitzouille, I agree it depends on the system's resources, I doubt the package can't do anything here. Alternatively, you can try any third-party packages that support ForegroundService.
Closing, as this isn't an issue with `android_alarm_manager. itself. If you disagree, please write in the comments and I will reopen it.
Thank you

Hi @alemoi
Thanks, @klitzouille, I agree it depends on the system's resources, I doubt the package can't do anything here. Alternatively, you can try any third-party packages that support ForegroundService.
Closing, as this isn't an issue with `android_alarm_manager. itself. If you disagree, please write in the comments and I will reopen it.
Thank you

AndroidAlarmManager.oneShot(Duration(seconds: 10), 0, _playSound,
exact: true,wakeup: true);
wakeup: true  solve it for me.

For screen off wakeup: true solve it like:
AndroidAlarmManager.oneShot(Duration(seconds: 10), 0, _playSound,
exact: true,wakeup: true);
But if you kill the app I needed to use notification with alarm manager to make it work like in:
await flutterLocalNotificationsPlugin.initialize(initializationSettings,
onSelectNotification: (String payload) async {
if (payload != null) {
debugPrint('notification payload: $payload');
//do some work
}


Can we add IS logo to the help pages

Moved from: https://wso2.org/jira/browse/IDENTITY-7105
Currently, all the help pages have a WSO2 Carbon logo, which doesn't make much sense to an external user. Is it possible to add IS logo here?

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


EL-1217: New UAT - WIP

Jira ticket
What changed and why

Guidance to review

Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing
Branch is generally up to date with main Github - definitely no conflicts
No unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
PR description says what changed and why, with a link to the JIRA story.
Diff has been checked for unexpected changes being included.
Commit messages say why the change was made.

I ran the redis script we wrote in https://github.com/ministryofjustice/laa-estimate-financial-eligibility-for-legal-aid/pull/1012 as a way of testing the import of data across UATs.
There were some small issues importing old namespace UAT redis into new namespace UAT redis, I tried this three times and each time, the migration failed due to 1 or 2 'missing' keys. But we think this is because new keys were being generated as the migration was running.
The verify this, we amended the script slightly so that we could import new namespace UAT redis into new namespace UAT staging (we knew no one was using these at the time). The script imported successfully with no failures. This implies the first few fails were due to new keys being created at time of migration.
As we will put the site in maintenance mode when we run this in production, we think that should eliminate this type of failure, and it should run successfully.


feat(widgets): create widget tabs

Description
Please describe the reason related to the changes:
Type
Please select the type related to the changes:

[ ] bugfix
[ ] build
[ ] continuous delivery (CD)
[ ] continuous integration (CI)
[ ] documentation
[ ] feature
[ ] formatting
[ ] refactoring
[ ] styling
[ ] other (please describe below):

Breaking Change
Does your changes introduce a breaking change?

[ ] no
[ ] yes

Behavior
Please describe the current behavior:
Changes
Please describe the new behavior:
Information (issue, links, logs, etc.)
Please list any other useful information:
Checklist
Please make sure this pull request follow the requirements:

[ ] commit guidelines @commitlint/config-conventional
[ ] 100% code coverage
[ ] tests passing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

56 of 69 (81.16%)  changed or added relevant lines in 11 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-10.6%) to 88.281%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/widgets/src/tabs/actions.ts
7
20
35.0%

Totals

Change from base Build<PHONE_NUMBER>:
-10.6%

Covered Lines:
199

Relevant Lines:
213

💛  - Coveralls


Error "value must be enumerable"

Hi,
I am using Dynamoid version 1.0 and I am getting the following error while executing the line :
Line :

Node.where(:region => region).where(:is_completed => 'f').count

Error:

value must be enumerable

Logs:

/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/set.rb:85:in do_with_enum' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/set.rb:310:in merge'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/set.rb:75:in initialize' dynamoid (1.0.0) lib/dynamoid/persistence.rb:99:in new'
dynamoid (1.0.0) lib/dynamoid/persistence.rb:99:in undump_field' dynamoid (1.0.0) lib/dynamoid/persistence.rb:61:in block (2 levels) in undump'
dynamoid (1.0.0) lib/dynamoid/persistence.rb:60:in each' dynamoid (1.0.0) lib/dynamoid/persistence.rb:60:in block in undump'
dynamoid (1.0.0) lib/dynamoid/persistence.rb:59:in tap' dynamoid (1.0.0) lib/dynamoid/persistence.rb:59:in undump'
dynamoid (1.0.0) lib/dynamoid/document.rb:133:in load' dynamoid (1.0.0) lib/dynamoid/document.rb:128:in block in initialize'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:113:in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:113:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:552:in block (2 levels) in compile' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:502:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:502:in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:86:in run_callbacks'
dynamoid (1.0.0) lib/dynamoid/document.rb:123:in initialize' dynamoid (1.0.0) lib/dynamoid/persistence.rb:51:in new'
dynamoid (1.0.0) lib/dynamoid/persistence.rb:51:in from_database' dynamoid (1.0.0) lib/dynamoid/identity_map.rb:15:in from_database'
dynamoid (1.0.0) lib/dynamoid/dirty.rb:8:in from_database' dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:143:in block (2 levels) in records_via_scan'
dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:362:in <<' dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:362:in block (3 levels) in scan'
dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:362:in each' dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:362:in block (2 levels) in scan'
dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:359:in loop' dynamoid (1.0.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:359:in block in scan'
dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:142:in each' dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:142:in each'
dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:142:in block in records_via_scan' dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:115:in each'
dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:115:in each' dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:115:in to_a'
dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:115:in Array' dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:115:in records'
dynamoid (1.0.0) lib/dynamoid/criteria/chain.rb:95:in each' app/models/node.rb:925:in count'
app/models/node.rb:925:in all_in_region_and_incomplete' app/controllers/nodes_controller.rb:201:in all_in_region_and_incomplete'
app/controllers/nodes_controller.rb:13:in index' actionpack (<IP_ADDRESS>) lib/action_controller/metal/implicit_render.rb:4:in send_action'
actionpack (<IP_ADDRESS>) lib/abstract_controller/base.rb:189:in process_action' actionpack (<IP_ADDRESS>) lib/action_controller/metal/rendering.rb:10:in process_action'
actionpack (<IP_ADDRESS>) lib/abstract_controller/callbacks.rb:20:in block in process_action' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:113:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:113:in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:552:in block (2 levels) in compile'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:502:in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:502:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:86:in run_callbacks' actionpack (<IP_ADDRESS>) lib/abstract_controller/callbacks.rb:19:in process_action'
actionpack (<IP_ADDRESS>) lib/action_controller/metal/rescue.rb:29:in process_action' actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:32:in block in process_action'
activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:159:in block in instrument' activesupport (<IP_ADDRESS>) lib/active_support/notifications/instrumenter.rb:20:in instrument'
activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:159:in instrument' actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:30:in process_action'
actionpack (<IP_ADDRESS>) lib/action_controller/metal/params_wrapper.rb:250:in process_action' actionpack (<IP_ADDRESS>) lib/abstract_controller/base.rb:136:in process'
actionview (<IP_ADDRESS>) lib/action_view/rendering.rb:30:in process' actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:196:in dispatch'
actionpack (<IP_ADDRESS>) lib/action_controller/metal/rack_delegation.rb:13:in dispatch' actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:232:in block in action'
actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:80:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:80:in dispatch'
actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:48:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:73:in block in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:59:in each' actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:59:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:690:in call' rack (1.5.2) lib/rack/etag.rb:23:in call'
rack (1.5.2) lib/rack/conditionalget.rb:25:in call' rack (1.5.2) lib/rack/head.rb:11:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/params_parser.rb:27:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/flash.rb:254:in call'
rack (1.5.2) lib/rack/session/abstract/id.rb:225:in context' rack (1.5.2) lib/rack/session/abstract/id.rb:220:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/cookies.rb:562:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:29:in block in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:82:in run_callbacks' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:27:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/reloader.rb:73:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/remote_ip.rb:76:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:17:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/show_exceptions.rb:30:in call'
railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:38:in call_app' railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:20:in block in call'
activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:68:in block in tagged' activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:26:in tagged'
activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:68:in tagged' railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:20:in call'
/opt/brazil-pkg-cache/packages/AmazonRailsLogger/AmazonRailsLogger-<IP_ADDRESS>/RHEL5_64/DEV.STD.PTHREAD/build/ruby1.9/site_ruby/1.9.1/amazon/set_request_id.rb:9:in call' /opt/brazil-pkg-cache/packages/AmazonRailsLogger/AmazonRailsLogger-<IP_ADDRESS>/RHEL5_64/DEV.STD.PTHREAD/build/ruby1.9/site_ruby/1.9.1/amazon/set_request_id.rb:9:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:21:in call' rack (1.5.2) lib/rack/methodoverride.rb:21:in call'
rack (1.5.2) lib/rack/runtime.rb:17:in call' activesupport (<IP_ADDRESS>) lib/active_support/cache/strategy/local_cache_middleware.rb:26:in call'
rack (1.5.2) lib/rack/lock.rb:17:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/static.rb:84:in call'
rack (1.5.2) lib/rack/sendfile.rb:112:in call' railties (<IP_ADDRESS>) lib/rails/engine.rb:514:in call'
railties (<IP_ADDRESS>) lib/rails/application.rb:144:in call' railties (<IP_ADDRESS>) lib/rails/railtie.rb:194:in public_send'
railties (<IP_ADDRESS>) lib/rails/railtie.rb:194:in method_missing' rack (1.5.2) lib/rack/lint.rb:49:in _call'
rack (1.5.2) lib/rack/lint.rb:37:in call' rack (1.5.2) lib/rack/showexceptions.rb:24:in call'
rack (1.5.2) lib/rack/commonlogger.rb:33:in call' rack (1.5.2) lib/rack/chunked.rb:43:in call'
rack (1.5.2) lib/rack/content_length.rb:14:in call' rack (1.5.2) lib/rack/handler/webrick.rb:60:in service'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/httpserver.rb:138:in service' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/httpserver.rb:94:in run'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/server.rb:191:in `block in start_thread'
Can any one please help me in this issue?

What version of Ruby are you using?

Hi,
I am making the dynamodb connection through
Aws.config.update({     region: region,     credentials: Aws::Credentials.new(a.public.text, a.private.text),   })
I am getting the error while executing the line :

Node.where(:is_submitted => 't').where(:is_signed_off => 'f').count

Error :

Seahorse::Client::NetworkingError

SSL_connect returned=1 errno=0 state=error: certificate verify failed

Logs :

/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/net/http.rb:800:in connect' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/net/http.rb:800:in block in connect'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/timeout.rb:69:in timeout' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/timeout.rb:100:in timeout'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/net/http.rb:800:in connect' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/net/http.rb:756:in do_start'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/net/http.rb:751:in start' aws-sdk-core (2.3.19) lib/seahorse/client/net_http/connection_pool.rb:281:in start_session'
aws-sdk-core (2.3.19) lib/seahorse/client/net_http/connection_pool.rb:93:in session_for' aws-sdk-core (2.3.19) lib/seahorse/client/net_http/handler.rb:116:in session'
aws-sdk-core (2.3.19) lib/seahorse/client/net_http/handler.rb:68:in transmit' aws-sdk-core (2.3.19) lib/seahorse/client/net_http/handler.rb:42:in call'
aws-sdk-core (2.3.19) lib/seahorse/client/plugins/content_length.rb:12:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/dynamodb_crc32_validation.rb:27:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/json/error_handler.rb:8:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/request_signer.rb:84:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:87:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:118:in retry_request' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:101:in retry_if_possible'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/retry_errors.rb:89:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/json/handler.rb:11:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/user_agent.rb:12:in call' aws-sdk-core (2.3.19) lib/seahorse/client/plugins/endpoint.rb:41:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/param_validator.rb:21:in call' aws-sdk-core (2.3.19) lib/seahorse/client/plugins/raise_response_errors.rb:14:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/dynamodb_simple_attributes.rb:112:in call' aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/param_converter.rb:20:in call'
aws-sdk-core (2.3.19) lib/aws-sdk-core/plugins/response_paging.rb:26:in call' aws-sdk-core (2.3.19) lib/seahorse/client/plugins/response_target.rb:21:in call'
aws-sdk-core (2.3.19) lib/seahorse/client/request.rb:70:in send_request' aws-sdk-core (2.3.19) lib/seahorse/client/base.rb:207:in block (2 levels) in define_operation_methods'
dynamoid (1.1.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:368:in block (2 levels) in scan' dynamoid (1.1.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:367:in loop'
dynamoid (1.1.0) lib/dynamoid/adapter_plugin/aws_sdk_v2.rb:367:in block in scan' dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:142:in each'
dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:142:in each' dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:142:in block in records_via_scan'
dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:115:in each' dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:115:in each'
dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:115:in to_a' dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:115:in Array'
dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:115:in records' dynamoid (1.1.0) lib/dynamoid/criteria/chain.rb:95:in each'
app/controllers/application_controller.rb:108:in count' app/controllers/application_controller.rb:108:in set_global_counts'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:429:in block in make_lambda' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:143:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:143:in block in halting_and_conditional' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:501:in call'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:501:in block in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:501:in each'
activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:501:in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:86:in run_callbacks'
actionpack (<IP_ADDRESS>) lib/abstract_controller/callbacks.rb:19:in process_action' actionpack (<IP_ADDRESS>) lib/action_controller/metal/rescue.rb:29:in process_action'
actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:32:in block in process_action' activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:159:in block in instrument'
activesupport (<IP_ADDRESS>) lib/active_support/notifications/instrumenter.rb:20:in instrument' activesupport (<IP_ADDRESS>) lib/active_support/notifications.rb:159:in instrument'
actionpack (<IP_ADDRESS>) lib/action_controller/metal/instrumentation.rb:30:in process_action' actionpack (<IP_ADDRESS>) lib/action_controller/metal/params_wrapper.rb:250:in process_action'
actionpack (<IP_ADDRESS>) lib/abstract_controller/base.rb:136:in process' actionview (<IP_ADDRESS>) lib/action_view/rendering.rb:30:in process'
actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:196:in dispatch' actionpack (<IP_ADDRESS>) lib/action_controller/metal/rack_delegation.rb:13:in dispatch'
actionpack (<IP_ADDRESS>) lib/action_controller/metal.rb:232:in block in action' actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:80:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:80:in dispatch' actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:48:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:73:in block in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:59:in each'
actionpack (<IP_ADDRESS>) lib/action_dispatch/journey/router.rb:59:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/routing/route_set.rb:690:in call'
rack (1.5.2) lib/rack/etag.rb:23:in call' rack (1.5.2) lib/rack/conditionalget.rb:25:in call'
rack (1.5.2) lib/rack/head.rb:11:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/params_parser.rb:27:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/flash.rb:254:in call' rack (1.5.2) lib/rack/session/abstract/id.rb:225:in context'
rack (1.5.2) lib/rack/session/abstract/id.rb:220:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/cookies.rb:562:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:29:in block in call' activesupport (<IP_ADDRESS>) lib/active_support/callbacks.rb:82:in run_callbacks'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/callbacks.rb:27:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/reloader.rb:73:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/remote_ip.rb:76:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/debug_exceptions.rb:17:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/show_exceptions.rb:30:in call' railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:38:in call_app'
railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:20:in block in call' activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:68:in block in tagged'
activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:26:in tagged' activesupport (<IP_ADDRESS>) lib/active_support/tagged_logging.rb:68:in tagged'
railties (<IP_ADDRESS>) lib/rails/rack/logger.rb:20:in call' /opt/brazil-pkg-cache/packages/AmazonRailsLogger/AmazonRailsLogger-<IP_ADDRESS>/RHEL5_64/DEV.STD.PTHREAD/build/ruby1.9/site_ruby/1.9.1/amazon/set_request_id.rb:9:in call'
/opt/brazil-pkg-cache/packages/AmazonRailsLogger/AmazonRailsLogger-<IP_ADDRESS>/RHEL5_64/DEV.STD.PTHREAD/build/ruby1.9/site_ruby/1.9.1/amazon/set_request_id.rb:9:in call' actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/request_id.rb:21:in call'
rack (1.5.2) lib/rack/methodoverride.rb:21:in call' rack (1.5.2) lib/rack/runtime.rb:17:in call'
activesupport (<IP_ADDRESS>) lib/active_support/cache/strategy/local_cache_middleware.rb:26:in call' rack (1.5.2) lib/rack/lock.rb:17:in call'
actionpack (<IP_ADDRESS>) lib/action_dispatch/middleware/static.rb:84:in call' rack (1.5.2) lib/rack/sendfile.rb:112:in call'
railties (<IP_ADDRESS>) lib/rails/engine.rb:514:in call' railties (<IP_ADDRESS>) lib/rails/application.rb:144:in call'
railties (<IP_ADDRESS>) lib/rails/railtie.rb:194:in public_send' railties (<IP_ADDRESS>) lib/rails/railtie.rb:194:in method_missing'
rack (1.5.2) lib/rack/lint.rb:49:in _call' rack (1.5.2) lib/rack/lint.rb:37:in call'
rack (1.5.2) lib/rack/showexceptions.rb:24:in call' rack (1.5.2) lib/rack/commonlogger.rb:33:in call'
rack (1.5.2) lib/rack/chunked.rb:43:in call' rack (1.5.2) lib/rack/content_length.rb:14:in call'
rack (1.5.2) lib/rack/handler/webrick.rb:60:in service' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/httpserver.rb:138:in service'
/home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/httpserver.rb:94:in run' /home/lakhwani/FCLaunchRequirement/env/FCLaunchRequirementWebsite-1.0/runtime/ruby1.9/1.9.1/webrick/server.rb:191:in block in start_thread'

Can any one help me in this?

Hi,
I am using Ruby 1.9.3.
BTW Now I am struggling with Seahorse::Client::NetworkingError error.
I have no idea about this error.
 But I have no idea about how to get this
issue resolved.
Can you help me in this?
On Tue, Aug 2, 2016 at 6:04 PM, Peter Boling<EMAIL_ADDRESS>wrote:

What version of Ruby are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Dynamoid/Dynamoid/issues/93#issuecomment-236890309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIP0YV73EkiXq_0EEx8Sjvt68fRGSpd5ks5qbzlLgaJpZM4JZZ5u
.

--
Thanks and Regards,
Ronak Lakhwani
Computer Science and Engineering, IIT Roorkee
Contact :<PHONE_NUMBER>

Seahorse is a tool that is part of the aws-sdk ruby library.  You might try a forum related to that.  But you're not going to get much help I think unless you are willing to upgrade Ruby.  Ruby 1.9.3 is no longer supported by anything or anyone.


[#2314] fix(postgresql): postgresql public schema should not be filtered in listDatabases

What changes were proposed in this pull request?
Remove the public schema from the SYS_PG_DATABASE_NAMES attribute
Why are the changes needed?
public schema is the default schema if not specifying schema names. we shouldn't filter it
Fix: #2314
Does this PR introduce any user-facing change?
N/A.
How was this patch tested?
Existing tests can cover it.

@lw-yang could you fix the failed IT?

TestMultipleJdbcLoad > testCreateMultipleJdbc() FAILED
    org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
        at app//org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
        at app//org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
        at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
        at app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
        at app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:527)
        at app//com.datastrato.gravitino.integration.test.catalog.jdbc.TestMultipleJdbcLoad.testCreateMultipleJdbc(TestMultipleJdbcLoad.java:125)

I think there lacks a UT to cover the changes.

@FANNG1 I'll fix it soon

Could you add a listSchemaTest in CatalogPostgreSqlIT, add a check whether public schema is listed out.

@FANNG1 i will add a listSchemaTest in CatalogPostgreSqlIT


simplifying creation of ECR repo within jupyter notebook

*Issue #, if available:*https://github.com/aws-samples/eks-kubeflow-workshop/issues/12
Description of changes: added single command line and remove screenshot to simplify ECR repo creation from notebook
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Jeffwan I've added two more commits to improve 02_06_fairing_e2e.ipynb. Can you take a look?

/lgtm


Exclude Folder Option Lacks Empty Selection in Settings

I am experiencing an issue with the Exclude Folder option in the settings of the obsidian-open-weather plugin. Once I select a folder to exclude, there is no option to deselect or choose an empty selection in the dropdown menu. This means that I am forced to always specify one folder, which is not ideal for my workflow.
It would be more user-friendly if there were an option to clear the selection or to have an empty choice available in the dropdown. This would allow users to easily adjust their settings without being locked into a single folder exclusion.

After further investigation, I realized that I needed to set my template folder as an Exclude Folder. This is crucial because, without this setting, the weather information in my templates is converted to static text, and new files created from those templates do not update in real-time.
Given this new understanding, I would like to close the previous issue. Thank you for your support, and I appreciate the functionality of the plugin!


Document default usernames for SSH on all providers

As @saswatp pointed out in #701, it can be confusing what users are available on which platforms. Here is the complete list:

Vagrant: vagrant
DigitalOcean: root
GCE: centos
AWS: centos
vSphere: no default
Openstack: cloud-user

SoftLayer: root

Openstack is dependent on who builds the images. We should probably just include ssh_user in the openstack example terraform files and default to centos.

Could we add the ssh user for each provider to its documentation, in addition to having it in the tf files?


Docker (Running as root without --no-sandbox is not supported)

Minimal, reproducible example
const browser = await puppeteer.launch([{
    executablePath: '/usr/bin/google-chrome-stable',
    args: [ '--disable-gpu', '--disable-setuid-sandbox', '--no-sandbox', '--no-zygote'],
  }]);

Error string
[71:71:0310/171518.544718:ERROR:zygote_host_impl_linux.cc(100)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Bug behavior

[ ] Flaky
[ ] PDF

Background
My Dockerfile is:
FROM node:16

# Create app directory
WORKDIR /home/administrator/app
RUN mkdir /wso
RUN mkdir /scrubs
RUN mkdir /download
RUN mkdir /fonts

# We don't need the standalone Chromium
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true

RUN apt-get update && apt-get install gnupg wget -y && \
  wget --quiet --output-document=- https://dl-ssl.google.com/linux/linux_signing_key.pub | gpg --dearmor > /etc/apt/trusted.gpg.d/google-archive.gpg && \
  sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
  apt-get update && \
  apt-get install google-chrome-stable -y --no-install-recommends && \
  rm -rf /var/lib/apt/lists/*

# Install app dependencies
# A wildcard is used to ensure both package.json AND package-lock.json are copied
# where available (npm@5+)
COPY package*.json ./

RUN npm install

# Bundle app source
COPY /src/ .
VOLUME "/home/administrator/app" "/home/administrator/app"

EXPOSE 5252
CMD npx nodemon -L server.js
#CMD [ "npm", "install" "npx","nodemon","-L","server.js" ]

Expectation
I'd expect passing --no-sandbox to work
Reality
[71:71:0310/171518.544718:ERROR:zygote_host_impl_linux.cc(100)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Puppeteer configuration file (if used)
No response
Puppeteer version
22.4.1
Node version
16.20.2
Package manager
npm
Package manager version
10
Operating system
Linux

@RayburnTrading Do you see the same issue if you use the official Puppeteer Docker image?
I can see that we do set a separate user for it - Dockerfile.


Work on branch  cell_values_and_cell_maps_refactoring

Misc. comments on the developments done at  branch  cell_values_and_cell_maps_refactoring

[ ] I have decided to delete IterCellData and flatten(::CellArray) from CellValues, since they are only used as low level helpers in Vtkio. They (or equivalent functionality) have to be moved to the latter module

For the moment, I will not introduce the inconsistency between inner and varinner
Custom broadcasting in Map missing


Add Google's Python course to resources

Seems worth a mention to me. :)

This course enforced Google's Python style guide, rather than the much preferred PEP8. That could be problematic.

I am not sure I see this as a problem. The google style guide agrees with PEP8 on nearly everything. it's really meant more as a complimentary guide than a substitute

As a side note, this course is for Python 2.6+ (from https://developers.google.com/edu/python/set-up#python-on-linux-mac-os-x-and-other-os):
For Google's Python Class, it's best to use Python 2.7. Although Python 3.x is becoming more popular, this course is designed for Python 2.6 or later.

that, I am far more troubled by. I think that disqualifies it.

As the one who originally brought this up, I agree, and I think this should be closed, but I'll let you decide. ^^


Added missing<EMAIL_ADDRESS>from chosen.js

Fixes https://github.com/HubSpot/tether/issues/156. Image copied from https://github.com/harvesthq/chosen/blob/master/public/chosen-sprite%402x.png

Ah, thanks!


chore(android): migrate to AGP8, increment target SDK

Made it work with current gradle and Android setup :)

publish on 0.1.3


Medium severity vulnerability affecting this repo

Hi there,
We noticed that your repo has a medium severity vulnerability:

Cross-site Scripting (XSS)
Affected package: jquery <3.0.0-beta1 >2.2.0 || <2.2.0 >1.12.3 || <1.12.0 >=1.4.0

Here is the test report for this repo.
If you’d like to fix this vulnerability, Snyk lets you generate a pull request that recommends the best upgrade path - there’s a link to fix this vulnerability on the test report.
Stay secure :-)
Snyk Community

False positive, the vulnerability affects jQuery.  This isnt jQuery.


Published full README and package.json

The newest version (1.1.0) released the entire README and package.json on NPM.
Isn't that because clean-publish was not used when publishing?

Fixed in v1.1.1. Thanks for letting me know!


Classes order causing issue

I'm using a utility framework with Classcat and it wasn't rendering the classes for one of the checks even thought it was evaluating to true. Switching the order of the classes, or renaming the first class made it work.
cc([
    'mr-auto px-1 py-0.5 font-bold tracking-lg rounded',
    {
        'text-black bg-white': isNew(order),
-       'text-white bg-grey': isPending(order), // don't work
+       'bg-grey text-white': isPending(order), // works
// or
+       'text-green bg-grey': isPending(order), // works
        'text-white bg-grey': isAccepted(order),
        'text-red bg-white': isExpired(order),
    }
])

I'm reporting because it looks like a bug.

@pedroborges Thanks. What classcat version were you using and can you post the original code you used? I don't understand what the diff is supposed to show.
I am trying to repro this issue here to no avail. 🤔

@pedroborges Could this be a bug with your CSS and not in classcat?

Thanks for the input guys! I have reverted the order of the classes for that particular item and it's working fine today. Yesterday I must have messed it somehow 😕


Naming conventions for UI - user interface

Should we use Ui or UI as the abbreviation of the user interface? E.g. ExecuteOnUiThread or ExecuteOnUIThread` ?

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

ID: 0eba6b11-5703-355f-0e85-08ee7451120d
Version Independent ID: 4691fbb3-7b6d-8c02-e372-315ca302e48e
Content: Capitalization Conventions
Content Source: docs/standard/design-guidelines/capitalization-conventions.md
Product: dotnet
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

This is covered by the following section of the docs:

A special case is made for two-letter acronyms in which both letters are capitalized, as shown in the following identifier:
IOStream

Such as this namespace we have in .NET: System.Web.UI

Thanks for the explanation.
Just note: examples from the .NET are not valid always. The .NET naming has changed over the years. E.g. Id vs ID:
System.Threading.Thread.GetDomainID
vs.
System.Threading.Thread.CurrentThread.ManagedThreadId
etc.

@terrajobst and @KrzysztofCwalina to confirm the right convention. I know that we haven't always been consistent.

"UI" just like "IO", i.e. the guideline is: two letter initialisms have both letters upper cased.


Safe UI is out of sync with blockchain

Description
After executing a transaction, and long after it is mined, it is still shown as "pending" in the UI.
refreshing (And hard-refresh) doesn't change it.
Environment

Browser: chrome, firefox
Wallet: MetaMask, Trezor
Safe:
Environment:

production

Steps to reproduce

have a queue of multiple transaction pending executing
execute the first noe
try to execute the next (you can't, until the UI gets sync with the blockchain the first TX was mined)

Expected result
after a transactiongets mined, the UI should be updated directly from the blockchain, so that I can continue and execute the rest of the transctions, instead of waiting to gnosis-specific backend to synchronize itself with the blockchain.

As I understand, the problem with this approach is that querying the blockchain directly will only tell you if an outer Ethereum transaction was executed. The delegated Safe transaction inside the Safe is another story.
Your MM will show you if the Ethereum transaction has succeeded, but it's not trivial to check if the inner Safe transaction has finished. It relies on Safe contract-emitted events for that, and there's a lot of logic around it. Which is currently abstracted away by our backend, and we have no plans duplicating it on the frontend.
cc @rmeissner – please correct me if I'm wrong

That said, frontend might have a workaround for this in future. E.g. accumulating multiple transactions in a batch and executing just one tx.

The problem is that your frontend is centralized to an unacceptable level: a transaction was executed, and all "vital signs" (e.g. events) show it was completed, but the UI refuses to accept it and let me sign the next tx in the queue.
Worse: by showing the transaction as "pending" it let me sign and submit the same transaction  again - which will get reverted later on chain.

The problem is that your frontend is centralized to an unacceptable level

Everyone is welcome to fork it and tweak it to the way they find acceptable

Worse: by showing the transaction as "pending" it let me sign and submit the same transaction again - which will get reverted later on chain.

This will be addressed in the upcoming release.
@drortirosh I understand the problem and we'll continue iterating on this. I'll close this particular issue for now.


BarChart secondaryData is completely ignored

Trying to do a bar chart with two y axis with different scale. But secondaryData property is ignored. All data is set with data like this:
barData.push({
  value: count * 1000,
  frontColor: '#125BFF',
  spacing: 0,
});
barData.push({
  value: miles,
  frontColor: '#FF9500',
});

What I'm trying to do is add blue bars to data, but orange bars to secondaryData, because they are different scaled values.
maxValue and stepValue are set different for main yAxis and secondaryYAxis
(Largest orange bar value is 8192 on the image below. It is showing up like its scaled for main y axis, but not for the secondary one)

Same here, any updates?
I'm trying to have bars for individual values (primary data) and a line for accumulative values (secondary data).
The line is not following secondary Y-axis scale :(
const data = [200,125,175,50],
  accData = [200,325,500,550];

...

<BarChart
  frontColor={greenColor}
  data={data}
  maxValue={600}
  showLine
  lineConfig={{ /* for hiding the line for primary data */
      startIndex: 0,
      endIndex: 0,
      hideDataPoints: true,
      isSecondary: false
  }}
  lineConfig2={{
      color: blueColor,
      thickness: 3,
      hideDataPoints: true,
      isSecondary: true
  }}
  lineData2={accData}
  secondaryYAxis={{
      maxValue: accData[accData.length-1].value + 10
  }}
/>

Hi @ilyabreev 👋
Secondary Bars can now be achieved by setting isSecondary: true inside the data array objects. See https://github.com/Abhinandan-Kushwaha/react-native-gifted-charts/discussions/828
I have removed the secondaryData prop from Bar charts, as it was useless.
This is available from versions 1.4.35 onwards. Please use the latest version of the library.
@gloriamannok 👋
Can you try again in the latest version of the library? I have made fixes and refactors related to secondary data and the secondary Y-axis.
Also, you don't have to use the hack using 2 lines and 2 lineConfigs. Just have one lineConfig, and inside this set isSecondary: true. It will show the line from the lineData prop. If the lineData prop is not provided, then it renders the line from the data prop.


Translate tutorials/stateful-application/basic-stateful-set/ into Japanese

This is a Feature Request
What would you like to be added
Translate tutorials/stateful-application/basic-stateful-set/ into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/close


People 139 users list on skill show view

Ticket
https://netguru.atlassian.net/browse/PEOPLE-139
Description

Talent manager should be able to see all of the users with their rates on show view for selected skill.
Implemented query object for fetching data from database
Modified template for displaying users

Before merge checklist

[ ] CircleCI is passing
[ ] Proper labels are set

is it available for every user or just admins/talent?

@lubieniebieski only for admins. I have added one more feature to let leaders display only their team. It requires updating specs for query service. (it is last commit, can be reverted in a case).


CUPS should be able to use different paper(tray) for job-sheets (support IPP attribute 'job-sheets-col')

CUPS is playing a core role in many educational institutions and other large organisations where thousands of users print their documents on a few dozen "public" printers. In these environments it is very common to enforce -o job-sheets=some-custom-postscript for each job to be printed on colorized paper so that they serve as separator sheets, with the actual job-sheet containing PostScript code to do the magic of tray switching (setpagedevice) as well as code to fill its page contents with time-at-processing, job-originating-user-name and what-not variable values.
To be honest, this method has always been a mild "hack", only necessitated because CUPS did never have a "canonical" support to pick a different tray for job-sheets.
By default, "legacy" CUPS always printed job-sheets on the same paper as the main job documents. The lack of direct support for banner pages from a different tray has always been one of the biggest deficiencies of CUPS -- and it was easily overcome by many organizations in need of it through their usage of custom PostScript "hacks".
But this situation has worsened now: When using the "new" job-sheet format (application/vnd.cups-banner), where the job-sheet is supposed to be dynamically created as a PDF for each job by a x-bannertopdf filter there is no means any more to get banners printed on different media as compared to the main job.
It is time to fill the gap. Else PostScript job-sheets will still be the holdout and prevent a full-scale PDF workflow.
It looks like IPP (but only the IPP extension for "production printing" purposes) already provides an appropriate job attribute for what's needed: job-sheets-col.
However, CUPS does not support this yet. It should, soon!

Yes, this is would be an important and valuable feature for CUPS!
Colored separator sheets that are deposited in a special paper tray are especially important when using CUPS for a large number of daily print jobs from different users like in educational institutions.
It considerably simplifies and  accelerates the process of sorting the print jobs.
Thumbs up for this feature.

Considering for a future release.

Now tracking this over in OpenPrinting CUPS as issue #138.


The driving-traffic API does not work

curl --location --request GET 'https://api.maptiler.com/maps/directions/v5/mapbox/driving-traffic/5.550339,52.039176;5.559641,52.041519?access_token=pk.eyJ1IjoiaXZhbm51a29sIiwiYSI6ImNsZGszYmV3eTF1NWEzbnBpNjd5aWRyZngifQ.CgRUbleOH0QkODA54mYutA&alternatives=true&geometries=polyline6&overview=full&steps=true&bearings=%3B&continue_straight=true&annotations=congestion%2Cdistance&language=en&roundabout_exits=true&voice_instructions=true&banner_instructions=true&voice_units=metric&key=45p5VMQdkfaQTsiyN7xW'
--header 'Authorization: Token ed2f63d7e237415b99cab718fcd15f1d_ff9fc7afd409aa9115b0a52611291eaf72fdc41f06ef6646e2afe848f5f6c763'

I am not sure if Maptiler is offering a directions API.
Right now the default should work with OSRM or Mapbox. You should be able to implement custom routing engines, for example GraphHopper. See also #44.


Change some headers for admin cli ls

Attached To -> Attached To VM
Created By -> Created By VM
Tested with make all and CI
Fixes #434

LGTM

LGTM.

LGTM. This one was easy :-)

As discussed with Mark the other day, this is just a log message during a negative test, which is why CI still passes. Will work to somehow disable or annotate it.


Update versions

Pins GitHub actions to a commit SHA (https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)
Updates GitHub actions to get rid of deprecation warnings due to an outdated Node version

All of this is optional, feel free to close this PR.
Currently Github actions complains that outdated Node versions are used which will be deprecated/removed at some point. This means we need to update the Github actions versions and at the same time I took the liberty of pinning the dependencies. If you don't like that I can also move to the old v4 style again.
And when trying to run npm install with the current set of dependencies I get this error:
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/svelte
npm error   dev<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error node_modules/svelte-motion
npm error   dev<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/lars/.npm/_logs/2024-06-18T08_56_58_646Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/lars/.npm/_logs/2024-06-18T08_56_58_646Z-debug-0.log

With the old mode-watcher dependency I get this ominous error:
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "link:": link:@testing-library/jest-dom/matchers

I can't see details on why Vercel failed.
I did run npm run build and  npm run test locally and it worked but there's a good possibility this broke something.

Thank you for the PR! I've already upgraded the deps separately in #86 as I didn't notice this PR was already open 😅 sorry about that, but much appreciated!