Getting these errors when I got to the customizer settings page

Version info:
Application version: 1.2.13
PHP version: 7.3.0
PHP SAPI: apache2handler
HTTP Client: cURL
OS version: Linux 4.19.88-Unraid
Database driver: mysql
Database version: 10.4.11-MariaDB-1:10.4.11+maria~bionic-log
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0

Getting these errors in the customizer screen:
Warning: filemtime(): stat failed for plugins/Customizer/Assets/rgbaColorPicker/rgbaColorPicker.css in /srv/http/kanboard/app/Helper/AssetHelper.php on line 37
Warning: filemtime(): stat failed for plugins/Customizer/Assets/css/customizer.css in /srv/http/kanboard/app/Helper/AssetHelper.php on line 37
Warning: filemtime(): stat failed for plugins/KanboardCSS/kanboardcss.css in /srv/http/kanboard/app/Helper/AssetHelper.php on line 37
Warning: filemtime(): stat failed for plugins/Customizer/Assets/css/theme.css in /srv/http/kanboard/app/Helper/AssetHelper.php on line 37
Warning: filemtime(): stat failed for plugins/Customizer/Assets/rgbaColorPicker/rgbaColorPicker.js in /srv/http/kanboard/app/Helper/AssetHelper.php on line 24
Warning: filemtime(): stat failed for plugins/Customizer/Assets/js/customizer.js in /srv/http/kanboard/app/Helper/AssetHelper.php on line 24

I'll run tests next chance I get, haven't tested with 1.2.13 yet. I'll let you know what I find.


Flash: move w25qxxdv driver to new SPI API

I think the title says all about the issue.

Fixed via #5921


Update examples and tutorial after automatic sharding has landed

Stack from ghstack:

-> #505
#504

After the DataLoader automatic sharding for DataPipe PR has landed in core, this PR is updating the relevant example and tutorial
This should be cherry-picked to release.
Differential Revision: D37040383

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@nivekt has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


Jj acontrib

Closes: #144

Issue #144

What is the purpose of the change

Adds a link to the Git Cheat Sheet url that was provided

(E.g.: This pull request improves documentation of area A by adding ....)

@all-contributors add @Ostyantic as code


Fund raise to fix the @ionic-native/google-maps plugin

Overview

Fundraise amount: $1,000 USD
Fix the bugs of the @ionic-native/google-maps plugin
Create a demo of the @ionic-native/google-maps plugin for all methods.

Description
As you may know, the ionic provides as @ionic-native/google-maps, but the wrapper plugin is not written by me actually.
Because of this, there are lots of bugs in the wrapper plugin.
I fixed lots of problems, but too many bugs.
In order to figure out the bugs, and fix them, I need to create the demo of all methods.
Some contributors and I tried to create that, but it takes so much time, and no profits.
The keypoint is time is money.
Working on the @ionic-native/google-maps spend my private time a lot.
Also the time of the contributors as well.
I discussed with the ionic team regarding the sponsor ship , but they refused my offer.
That's why I stop fixing the @ionic-native/google-maps plugin anymore.
However, I also understand many ionic users prefer the @ionic-native/google-maps plugin instead of the pure JS version. But nobody pay for our work.
Thus, I start the fund raising at here to fix the problems of the @ionic-native/google-maps plugin.
If the amount reach to $1,000 USD, we will restart the working to create the demo project.
https://github.com/wf9a5m75/ionic-googlemaps-demo
At the same time, I will restart to fix the @ionic-native/google-maps plugin.
Until the time, we stop our activities for a while.

How to donate to this project?
Please donate from here.

Benefits

I will let you know when I fix the new bugs of the @ionic-native/google-maps plugin
I will support your project if you have a problem with the @ionic-native/google-maps plugin (I don't support for non-donated person, sorry)
If you donate $200 USD, I support in private (by e-mail base. E-mail supporting is stressful for me, but if you donate the amount, I will support for that)

The usage of the amount
I will share it with the contributors based on their work.

Got to fix the badge icon/link

@thezakman Fix the icon and link!

Thank you for your donation, @Javi124

So currently getting this error message when trying to install:
Error: Failed to fetch plugin
https://github.com/mapsplugin/cordova-plugin-googlemaps#multiple_maps
via registry.
Probably this is either a connection problem, or plugin spec is
incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
...Is this because you are no longer providing the module? It worked fine yesterday and today it stopped....

@heyjohnny Why did you post your issue at here?
And did you find in the past issues? https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1435#issuecomment-299580754
That is npm problem, not this plugin.

Hi @wf9a5m75, apologies for not following up in a timely manner on your email. We haven't refused to support the project, it's just not something we've done before so I hope you'll understand it's a process on our end figuring out how to do that.
However, we just donated to the cause which I hope helps in the short term. We very much appreciate your support and understand there's a large demand on your time from the community.
I will follow up via email and we can continue the conversation there.

Hi @mlynch , thank you for understanding, and the donation!
Yes, let's discuss how we can effort for each others.

Since the total amount is reached to the end, I close this thread at once, and I support the closed issues.
And I will send the PR, which is I closed before, to the @ionic-native repository.
Also the contributors and I resume the demo project.


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/iobroker-community-adapters/ioBroker.places

[ ] [E150] No common.connectionType found in io-package.json
[ ] [E152] No common.dataSource found in io-package.json
[ ] [E154] common.dependencies must contain{"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
[ ] [E605] No actual year found in copyright. Please add "Copyright (c) 2018-2022 BasGo<EMAIL_ADDRESS>at the end of README.md
[ ] [E701] No actual year found in LICENSE. Please add "Copyright (c) 2018-2022 BasGo<EMAIL_ADDRESS>at the start of LICENSE

Thanks,
your automatic adapter checker.

Thanks, that all bugs have been fixed.


💄 Redesigns and theme options

Resolves https://github.com/stumpapp/stump/issues/229
Foundational work towards https://github.com/stumpapp/stump/issues/227
PR has a large diff, but the overview is as follows:

Add base logic required for supporting custom themes

For now, custom themes will be code-first contributions. Later, local CSS files are aimed to also be supported
Default themes are:

dark
light
bronze (light but with the Stump orange tones in the gray colors)

Redesigned the settings navigation
Refreshed a large amount of pages to improve:

Spacing
Font sizes and readability
Colors

Added a new top bar navigation option
Added the tracking of library visits per user to support last library visited functionality for quick links
Added a handful of UI preferences to the user_preferences table

Rough UI mocked out for future configurations down the road (e.g. compact vs default spacing, color preferences, etc)

Fixed a link in documentation

I have to eye ball the colors on a few screens, double check the en.json changes, but then this should mostly be good to go 🚀

I've done a good amount of pixel peeking and I'm satisfied enough to merge this shortly. I'm sure I'll find a couple of UI things that need correcting, but overall this is a large net improvement IMO


stroke-dasharray usage

Hi there!
I was trying to plot a simple function with a dashed line, but failed. Here is the code:
functionPlot({
  target: '#demo',
  data: [{
    fn: 'x^2',
    color: 'red',
    attr: {
      'stroke-dasharray': '0.1,0.5'
    }
  }]
});

Here is how it looks like:

Dashes are very small (which can be expected given the arguments to the stroke-dasharray) and irregular (which isn't expected). When I try to make them longer, dashes disappear completely. I don't fully understand SVG paths, but it looks like that's because of the way the path is specified.
Do you think it's possible to make a dashed plot? It's very useful for printing stuff out in grayscale.

Yep, the problem is that this library uses interval arithmetic by default to evaluate functions and its renderer works by rendering a lot of rectangles instead of connecting lines as you would expect.
This problem is not present with the other renderer which you can trigger with graphType: polyline, refer to the docs/examples for more info on the differences between them
functionPlot({
  target: '#demo',
  data: [{
    fn: 'x^2',
    color: 'red',
    graphType: 'polyline',
    attr: {
      'stroke-dasharray': '5, 5'
    }
  }]
});

Ah, I get it! Thanks a lot :)


Add useful info for pod history

This PR is part of a series (see #646 ) to enable showing human-readable history of relevant information about the lifecycle of underlying K8s resources that back Sematic runs. This PR introduces code that inspects K8s jobs/pods/containers to collect information that can then be summarized into a high-level status containing:

a status kind (ex: "Running", "Pending", "Failed", etc..)
a human readable message: ("The pod abc123 is running on node 123456.")
a timestamp that the status was produced by

A subsequent PR will store a history of these status objects in a new table so that they can be displayed on the front-end. For now, the status is just logged to the server logs.
NOTE: Unit tests will be added once we agree on behavior.
Testing
I manually tested several scenarios we have seen in user deployments that required Sematic authors to debug via kubectl in response to questions from an end-user. As I tested, I modified some of the code, so the messages shown below may not exactly match what the code on the latest commit produces.
Tested scenarios
Normal, successful completion of a run
{
  "content": [
    {
      "job_id": "josh/sematic-worker-ae95971c7624481d924338b625c854e2-e92d7b",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.742216,
          "state_name": "Deleted"
        },
        {
          "description": "Job is running with pod sematic-worker-ae95971c7624481d924338b625c854e2-e92d7b-fdplj on node ip-10-42-40-19.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.0256553,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-ae95971c7624481d924338b625c854e2-e92d7b-fdplj on node ip-10-42-40-19.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.1845317,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.9966528,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Exception raised from user's python code (no retries)
JobStatus is the same as for normal success. The error is indicated in the Run's status, and exception display.
{
  "content": [
    {
      "job_id": "josh/sematic-worker-2ecae713740945fe8ad4711baafe702a-980b3d",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.9616737,
          "state_name": "Deleted"
        },
        {
          "description": "Job is running with pod sematic-worker-2ecae713740945fe8ad4711baafe702a-980b3d-jghbx on node ip-10-42-40-19.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.1904194,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-2ecae713740945fe8ad4711baafe702a-980b3d-jghbx on node ip-10-42-40-19.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.4721277,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.3436668,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Bad node selector
Similar message is shown for bad resource requests (ex: somebody asks for 1000 CPUs). Status history taken before job was canceled (jobs with bad resource requests will hang until either resource requests get met by autoscaler or job is canceled).
{
  "content": [
    {
      "job_id": "josh/sematic-worker-1c9536209c234f0a963ee03fa9686ea2-feb793",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "Pod is not scheduled. Reason: Unschedulable: 0/22 nodes are available: 22 node(s) didn't match Pod's node affinity/selector.. Depending on your Kubernetes cluster's configuration and current usage, this may or may not resolve itself on its own. Please consult your cluster operator.",
          "last_update_epoch_time":<PHONE_NUMBER>.5712745,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.4305027,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Invalid image
History taken before manually cancelling job. Note that in a normal case, the bad image would also be used for the resolver in which case we wouldn't be able to see this for an individual job. This highlights the need for some background thing to be monitoring the state of resolvers. Once we do that though, this kind of message should show up.
{
  "content": [
    {
      "job_id": "josh/sematic-worker-ed93858fa3bb480d98cf50ca8195d26e-0a2413",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "Job is running with pod sematic-worker-ed93858fa3bb480d98cf50ca8195d26e-0a2413-mw6ls on node ip-10-42-24-29.us-west-2.compute.internal. Container is waiting: InvalidImageName; Failed to apply default image tag \"558717131297.dkr.ecr.us-west-2.amazonaws.com/sematic-dev@sha256:0c577e47021e808f6f9970c726cd5eeb3b66dfa2e49195b1994e0c5b7f61fed4badsuffix\": couldn't parse image reference \"558717131297.dkr.ecr.us-west-2.amazonaws.com/sematic-dev@sha256:0c577e47021e808f6f9970c726cd5eeb3b66dfa2e49195b1994e0c5b7f61fed4badsuffix\": invalid reference format.",
          "last_update_epoch_time":<PHONE_NUMBER>.3823001,
          "state_name": "Pending"
        },
        {
          "description": "Job is running with pod sematic-worker-ed93858fa3bb480d98cf50ca8195d26e-0a2413-mw6ls on node ip-10-42-24-29.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.1739278,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.9362588,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Pod exited with 0, no Sematic terminal status
{
  "content": [
    {
      "job_id": "josh/sematic-worker-c582a0dedb9b4404bd950ef111bb01aa-ae27fa",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.49388,
          "state_name": "Deleted"
        },
        {
          "description": "Job failed. The container exited with a 0 exit code, but Sematic did not record the terminal state from the worker. Did the code inside the Sematic func contain a forced premature exit (ex: sys.exit(0), os._exit(0))?",
          "last_update_epoch_time":<PHONE_NUMBER>.297772,
          "state_name": "Failed"
        },
        {
          "description": "Job is running with pod sematic-worker-c582a0dedb9b4404bd950ef111bb01aa-ae27fa-4q2ml on node ip-10-42-43-248.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.2985516,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-c582a0dedb9b4404bd950ef111bb01aa-ae27fa-4q2ml on node ip-10-42-43-248.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.5447397,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.4130428,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Pod exited with non-0
{
    "content": [
        {
            "job_id": "josh/sematic-worker-3263b6fefc434e33833d225848bad05d-c7ffcb",
            "job_kind": "worker",
            "status_history": [
                {
                    "description": "The job no longer exists",
                    "last_update_epoch_time":<PHONE_NUMBER>.6002445,
                    "state_name": "Deleted"
                },
                {
                    "description": "Job failed. Container is terminated: Error; Exit code is 42.",
                    "last_update_epoch_time":<PHONE_NUMBER>.3686655,
                    "state_name": "Failed"
                },
                {
                    "description": "Job is running with pod sematic-worker-3263b6fefc434e33833d225848bad05d-c7ffcb-q45qs on node ip-10-42-43-248.us-west-2.compute.internal.",
                    "last_update_epoch_time":<PHONE_NUMBER>.6653364,
                    "state_name": "Running"
                },
                {
                    "description": "Job is running with pod sematic-worker-3263b6fefc434e33833d225848bad05d-c7ffcb-q45qs on node ip-10-42-43-248.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
                    "last_update_epoch_time":<PHONE_NUMBER>.8955245,
                    "state_name": "Pending"
                },
                {
                    "description": "The job has been requested, but no pods are created yet.",
                    "last_update_epoch_time":<PHONE_NUMBER>.756671,
                    "state_name": "Requested"
                }
            ]
        }
    ]
}

Node where pod is running was drained
{
    "content": [
        {
            "job_id": "josh/sematic-worker-f9a2b4d2a1d1487bb165c8acb6a9fa5c-1dd068",
            "job_kind": "worker",
            "status_history": [
                {
                    "description": "The job no longer exists",
                    "last_update_epoch_time":<PHONE_NUMBER>.2872872,
                    "state_name": "Deleted"
                },
                {
                    "description": "Job is running with pod sematic-worker-f9a2b4d2a1d1487bb165c8acb6a9fa5c-1dd068-rngrl on node ip-10-42-40-19.us-west-2.compute.internal.",
                    "last_update_epoch_time":<PHONE_NUMBER>.4377398,
                    "state_name": "Running"
                },
                {
                    "description": "Job is running with pod sematic-worker-f9a2b4d2a1d1487bb165c8acb6a9fa5c-1dd068-rngrl on node ip-10-42-40-19.us-west-2.compute.internal. The pod was restarted by Kubernetes without Sematic's intervention, and was assigned to a new Kubernetes node. This can have many causes.",
                    "last_update_epoch_time":<PHONE_NUMBER>.5995288,
                    "state_name": "Running"
                },
                {
                    "description": "Job is running with pod sematic-worker-f9a2b4d2a1d1487bb165c8acb6a9fa5c-1dd068-t6xxr on node ip-10-42-43-248.us-west-2.compute.internal.",
                    "last_update_epoch_time":<PHONE_NUMBER>.8254652,
                    "state_name": "Running"
                },
                {
                    "description": "Job is running with pod sematic-worker-f9a2b4d2a1d1487bb165c8acb6a9fa5c-1dd068-t6xxr on node ip-10-42-43-248.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
                    "last_update_epoch_time":<PHONE_NUMBER>.0939994,
                    "state_name": "Pending"
                },
                {
                    "description": "The job has been requested, but no pods are created yet.",
                    "last_update_epoch_time":<PHONE_NUMBER>.9488337,
                    "state_name": "Requested"
                }
            ]
        }
    ]
}

OOM
{
  "content": [
    {
      "job_id": "josh/sematic-worker-d143b20bd70f4196baa7483b86af304c-18f457",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.6261988,
          "state_name": "Deleted"
        },
        {
          "description": "Job failed. Container is terminated: OOMKilled; Exit code is 137.",
          "last_update_epoch_time":<PHONE_NUMBER>.4108913,
          "state_name": "Failed"
        },
        {
          "description": "Job is running with pod sematic-worker-d143b20bd70f4196baa7483b86af304c-18f457-kwpgc on node ip-10-42-24-29.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.6080809,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-d143b20bd70f4196baa7483b86af304c-18f457-kwpgc on node ip-10-42-24-29.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.9703972,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.832541,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

Sematic Retry
Note that (a) there are two job objects and (b) the second one begins with the message: The job has been requested, but no pods are created yet.Sematic has retried the job, this is try number 2.
{
  "content": [
    {
      "job_id": "josh/sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-561b06",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.8195384,
          "state_name": "Deleted"
        },
        {
          "description": "Job is running with pod sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-561b06-f9k5k on node ip-10-42-40-19.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.7701516,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-561b06-f9k5k on node ip-10-42-40-19.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.0434384,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.",
          "last_update_epoch_time":<PHONE_NUMBER>.8794644,
          "state_name": "Requested"
        }
      ]
    },
    {
      "job_id": "josh/sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-8bf688",
      "job_kind": "worker",
      "status_history": [
        {
          "description": "The job no longer exists",
          "last_update_epoch_time":<PHONE_NUMBER>.893179,
          "state_name": "Deleted"
        },
        {
          "description": "Job is running with pod sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-8bf688-t45h8 on node ip-10-42-24-29.us-west-2.compute.internal.",
          "last_update_epoch_time":<PHONE_NUMBER>.0799432,
          "state_name": "Running"
        },
        {
          "description": "Job is running with pod sematic-worker-276cd8a09eb6461ea79b9ac0b926d218-8bf688-t45h8 on node ip-10-42-24-29.us-west-2.compute.internal. Container is waiting: ContainerCreating.",
          "last_update_epoch_time":<PHONE_NUMBER>.210826,
          "state_name": "Pending"
        },
        {
          "description": "The job has been requested, but no pods are created yet.Sematic has retried the job, this is try number 2",
          "last_update_epoch_time":<PHONE_NUMBER>.0470638,
          "state_name": "Requested"
        }
      ]
    }
  ]
}

I noticed that the chronological sequence of this and external resource event history is completely opposite, one is flowing forward in time and the other is flowing backward in time.
Can we keep this the same as the external resource event history ?

Superseded by #701 and friends


barrier: Add test for no barrier, no blocking case

I'm reviewing barrier recipes now.

How are you @cybergrind 😀
Are you OK in a COVID-19 situation?
I live in Seoul, South Korea. It's OK here.

@rhdxmr all is good, I've reviewed you PR's and they looks ok, but couldn't rebase it correctly from web interface, will merge soon

@cybergrind
I'm glad to hear that. Stay safe home.

merged in v0.24.0


FIX: Show at correct time

@teonlamont @dengemann I think this is what we actually want... the show should be delayed until the very end, no?

Yrah ...


DrawImage Transparency Problem

When I draw a image, with DrawImage the background never is transparent no matter what I do, I tried it with CreateImage from a path and from a MemoryStream, didn't try from Resources as it won't work for what I am using this

@yasha107
just saw your email so i quickly follow up...

Can you provide a code example?
Can you upload the image you are using?

The library is trying to guess the best format to use with your image. it would be great to have the actual image to debug the issue.
If you can not provide the exact image then please provide anothewr one where it isn't working aswell.

gfx.DrawImage(gfx.CreateImage("E:/Downloads/cross-shaped-target.png"), 0, 0);

Thank you!
There is indeed a problem with my image decoder.
DirectX reports several supported formats on my machine but it seems like the preferred one isn't working and thats why there is a fallback for standard RGB.
I will use your image to create a better algorithm picking the best supported image format.
And just to make sure... Youre not using this one liner in production? You will run out of memory pretty soon. Load the image only once and use it from there on.

But i will do it tomorrow 😪

Nope, not using it like this, I do load it once. This one was just for showing a fast example of the issue

Well, unfortunately both BitmapDecoder.DecoderInfo.PixelFormats and BitmapFrameDecode.PixelFormat don't work in our case.
The first one returns only RGB formats (no alpha) and the second one returns an unsupported format.
I currently rely on the returned PixelFormat[] from the Decoder.
My only idea is to change this behaviour to use a bruteforce approach by enumerating a list of all supported formats while prefering the ones with higher bits per pixel and alpha channel.
I'll probably need another day to implement the sorting algorithm, caching and loop.
Performance wise i see no problem when images get pre loaded. Support for the alpha channel and all different image formats is worth it i guess.
Here a picture of your image drawn with transparency.

Perfect, would be very nice if this gets implemented)

@yasha107
I uploaded a new NuGet package with the fixes applied.
I got good results when trying to load png, bmp and gif images.
If you got no more questions i will close the issue here.

Thanks! Works very well now))


GH-647 Store/Cache/Sync knots correctly on pin disconnects

Fixes #647

Applied to main (=2.1) and branch 2.0.


rewrite Gate impl for better observability

get rid of the name, rely on stable Arc pointer instead and spans from guards which were holding the gate open.
TODO:

regress tests hopefully will already fail with not allowed warning from Guard::drop
fix the duplicated duplicated span usage with tenant deletion

I was not expecting as many failures, interesting :)

Failures on Postgres 16

test_gc_cutoff: debug

I see no clear reason for this timeout. Logs are quite unreadable as well.

Failures on Postgres 16

test_timeline_size_quota_on_startup: release

Failures on Postgres 14

test_timeline_size_quota_on_startup: release

This looks flaky by nature... Basebackup is read after initial logical size is at least started in both cases. Since some passed, perhaps this the limits are wrong? Passing runs have more time in between them... Or then we are waiting for initial logical sizes to be calculated but not necessarily being sent to the safekeepers who do not by default provide push back if there is no logical size info from pageserver.

Regress tests do have an example which I think is looking promising:
2024-01-31T11:16:47.490148Z  WARN request{method=POST path=/v1/tenant request_id=eafa23f2-f345-4016-ab78-f4845baf87fc}:upsert_location{tenant_id=f5a28135ac918a4edc114b9416eae5c2 shard_id=0000}: closing is taking longer than expected gate=0x7f63dc026e40 elapsed_ms=1001

2024-01-31T11:16:47.623021Z  INFO request{method=POST path=/v1/tenant/f5a28135ac918a4edc114b9416eae5c2/timeline request_id=11588b8a-a4fb-4a63-b22a-3354bc021ef5}:timeline_create{tenant_id=f5a28135ac918a4edc114b9416eae5c2 shard=0000 timeline_id=d5ae457c9ee939c648c72922bc4f9411 lsn=None pg_version=None}: kept the gate from closing gate=0x7f63dc026e40

2024-01-31T11:16:47.623409Z  INFO request{method=POST path=/v1/tenant request_id=eafa23f2-f345-4016-ab78-f4845baf87fc}:upsert_location{tenant_id=f5a28135ac918a4edc114b9416eae5c2 shard_id=0000}: close completed gate=0x7f63dc026e40 elapsed_ms=1134

Overall I like the idea of carrying a span in a GateGuard to get insight into who was slow -- this is definitely useful near term, and if it turns out to have low performance impact we might just keep it forever in anticipation of future shutdown bugs.
I've commented on the removal of name -- I'm concerned that without that, we will not know which entities a stuck gate relates to, because we only see the spans printed if the GateGuard drops, which won't happen if it's a bad bug that hangs forever.

Very nice. Will the demotion to INFO make it harder to find such cases? For instance we won't notice it in regress tests, right?

The flip side is that many tests could fail with this because of busy runners. Though I guess such would still be interesting to look at as possible causes for prod issues? OTOH I have a feeling that not many are looking at the existing flakyness instead just re-running so I wouldn't really want to add to it.

Failures on Postgres 16

test_gc_cutoff: debug

This is too slow for debug + pg16 right now.


Use tegola with Openstreet Map

Hello,
I would like to use tegola with an existing Openstreetmap database. If it's possible, can you tell me how todo it ?
Thanks

@Alex237 check out: https://github.com/go-spatial/tegola-osm.

tank you @ARolek .
I saw this, but by reading the doc, it means i have to reimport my OSM database no use an existing osm database or What if i want to keep my openstreetmap database updated? should i have to import all again ?

@Alex237 you will want to look at imposm3's documentation for updating: https://imposm.org/docs/imposm3/latest/tutorial.html#updating. They have a way to run a daemon that will keep the data up to date. It also spits out tile lists which tegola can work with using tegola cache seed tile-list my-tile-list.txt

ok, i will take a look to this


feat: math hints integration tests

Not te be merged now.
Will add cairo files one after the other after testing.
For now, these cairo files are not detected when doing make integration as i created new folders to store them. Will adapte the make integration command input fetching once  Finalize Segment PR is merged

[x] : isQuadResidue
[ ] : signedDivRem (undetected by our VM because of backslash)
[x] : pow
[x] : splitFelt
[x] : is_positive: also corrected an issue with the operander name
[x] : cmp hints (tests include isNN, isNNOutOfRange, isLeFelt, assertLtFelt, assertLefelt, assertNN hints, and also pow)
[x] : assertNotZero
[x] : assertNotEqual
[x] : assert250Bits

@cicr99  i tried copy pasting the lambda go VM but it still doesnt work.
Lambda uses const instead of string:
const SIGNED_DIV_REM = "from starkware.cairo.common.math_utils import as_int, assert_integer\n\nassert_integer(ids.div)\nassert 0 < ids.div <= PRIME // range_check_builtin.bound, \\\n    f'div={hex(ids.div)} is out of the valid range.'\n\nassert_integer(ids.bound)\nassert ids.bound <= range_check_builtin.bound // 2, \\\n    f'bound={hex(ids.bound)} is out of the valid range.'\n\nint_value = as_int(ids.value, PRIME)\nq, ids.r = divmod(int_value, ids.div)\n\nassert -ids.bound <= q < ids.bound, \\\n    f'{int_value} / {ids.div} = {q} is out of the range [{-ids.bound}, {ids.bound}).'\n\nids.biased_q = q + ids.bound"

when i do
signedPowCode string = "from starkware.cairo.common.math_utils import as_int, assert_integer\n\nassert_integer(ids.div)\nassert 0 < ids.div <= PRIME // range_check_builtin.bound, \\\n    f'div={hex(ids.div)} is out of the valid range.'\n\nassert_integer(ids.bound)\nassert ids.bound <= range_check_builtin.bound // 2, \\\n    f'bound={hex(ids.bound)} is out of the valid range.'\n\nint_value = as_int(ids.value, PRIME)\nq, ids.r = divmod(int_value, ids.div)\n\nassert -ids.bound <= q < ids.bound, \\\n    f'{int_value} / {ids.div} = {q} is out of the range [{-ids.bound}, {ids.bound}).'\n\nids.biased_q = q + ids.bound"

it doesnt work

there is probably a trick to make it work with string , any idea?


Priorities

Allow user to supply a function to prioritize which assets are fixed first.

Blocked by #2


Do you have any tips for including in a typescript based package?

Hi, I am writing a plugin using the homebridge-plugin-template  which utilizes typescript. I would like to use fakegato-history but have been struggling with the correct syntax to 'import' rather than 'require' the FakeGatoHistoryService and add this to my accessory. Any help would be appreciated.

Sorry, I don't have any experience with typescript, maybe someone else.

Fakegate in a typescript project is included like this:
`
import fakegato from 'fakegato-history';
(...)
class MyClass:
historyService: fakegato.FakeGatoHistoryService;
constructor(...) {
this.log = this.platform.log;
const FakeGatoHistoryService = fakegato(this.platform.api);
this.historyService = new FakeGatoHistoryService('weather', this.accessory);
}
`

I'm getting an error on this line of code:
const FakeGatoHistoryService = fakegato(this.platform.api);
Error:
UnhandledPromiseRejectionWarning: TypeError: fakegato_history_1.fakegato is not a function
Any ideas?

There seems to be an issue with how fakegate-history has been imported in the namespace of the module?
Mine is installed under: <plugin_dir>/node_modules/fakegato-history/fakegato-history.js
I am also struggling with instantiating historyService properly, so I had to manually set some properties:
const FakeGatoHistoryService = fakegato(this.platform.api);
    this.historyService = new FakeGatoHistoryService('weather', this.accessory, {minutes:1});
    this.historyService.accessoryName = <accessoryName>;
    this.historyService.log = this.platform.log;

Right now I get a new entry every 1 minutes, but I also have 1000+ historical entries that I tried adding with
this.historyService.addEntry({time: <unix timestamp>, temperature: <value>, humidity: <value>})

But looking at the code I am not sure its possible to add historical data this was to fakegato. I am beginning to fear that I have to write them to a file first, and instantiate the fakegato service with a fs (filesystem) backend for persistent data ... and that's a bummer :(

Yeah my bad. I was not using import incorrectly with { } brackets around fakegato.
I have the accessory working with Eve now. I can see the graph and the temp is recorded every 10 mins which is fine. However,  my accessory will need to be rewritten to properly support it. Currently, I only update the characteristics on an as needed basis and so the temp doesn't update unless someone is viewing the app.
I send updates using the following code:
     this.historyService.addEntry({       time: Date.now(),       temp: currentValue     })

@fjs21 With the latest release I had included some minor tweaks around typescript support, in particular in regards to logging.  Please see this in the README
https://github.com/simont77/fakegato-history#advanced-options

Thanks. I will take a look. From my perspective this issue can be closed as I was able to incorporate fakegato into the plugin I have been working on (homebridge-kumo).

Closing


serial tests

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

test


Upgrades tiller version to 2.9.0

We've recently upgraded our tiller version to 2.9 to support some helm charts which are only compatible with >= 2.8.x, and has been working pretty well so far.

@anguslees Any chance of getting this reviewed? We would like to depend on the latest master again.

@anguslees thanks for taking a look! I updated the tiller.jsonnet with the helm init -o json from helm 2.9.1, and you were right - it has removed the automountServiceAccountToken field.


Handle OS signals in testv2

What this PR does / why we need it:
In order to properly clean-up cloud resources after prow tries to kill pod, we have to properly handle OS signals, instead of immediate exit.
Which issue(s) this PR fixes:

Fixes #2346
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

/test pull-kubeone-e2e-aws-amzn-install-containerd-v1.22.12

/test pull-kubeone-e2e-aws-amzn-install-containerd-v1.22.12

/test pull-kubeone-e2e-aws-default-install-containerd-v1.24.3

/test pull-kubeone-e2e-aws-default-install-containerd-v1.24.3

/test pull-kubeone-e2e-aws-default-upgrade-containerd-from-v1.23.9-to-v1.24.3


added JNI PoC with compiler optimization

Added JNI interface to Android app and enable -Ofast and openMP in a library. I got approx 90 tokens/sec with optimizations on Pixel 7 Pro (without optimization approx 16 tokens/sec)
Screen_recording_20230728_121057.webm
full code in an android branch:
https://github.com/celikin/llama2.c-android-wrapper/tree/android/android

increased speed byt openMP threads 4 to  achieved tok/s: 205.479452

added loading models from assets


P/mike/job history upstream

The purpose of this feature is to show the past task executions for each job (if data exists).  Data is extracted from the existing Cassandra setup.  The tasks are reverse sorted by date, with the most recent at the top.
There are two commits for this request.  The commits are separated to show the initial change to the cassandra table schema by changing the indexing scheme.  To adapt to the existing schema that upstream uses, I changed to go from a partition key to a secondary index.  After getting feedback, I'll squash the commits and merge the final version.

@brndnmtthws @elingg - since this is the same area as the last pull request, can you please review again? thanks :)

Looks great, minus some minor comments. Can you also squash & rebase into 1 commit, please.
Thanks!

Another thing: can you update the README to explain how this works? I'm worried some folks (who don't use the C* stuff) will be confused as to why they don't have this data.

@brndnmtthws - comments addressed. can you review again?

One minor nit pick.
Any comments from @elingg?

Thanks for the contribution @mngo87 and for the review @brndnmtthws, I'll take a final look at this ASAP.

Sure no problem.  I updated once more to address @brndnmtthws 's comments

Looks great now, thanks.

This is really great work, @mngo87! My main concern at this point is with clean code, specifically in the method, getParsedJobStatsByName. I want to make sure we have a clean way of updating the appropriate fields in TaskStat and loading and saving the object to DB. Right now we modify different fields at different times, which is not ideal and difficult to read.

Thanks @elingg for the review.  Let me know your thoughts on what I said.  Just to re-iterate, TaskStat is just merely a object representation of the chronos table.  It will pull all the data at once and then parse.  It will not get the subsequent updates during parsing.  That can be a feature for later.

Thanks for the quick response @mngo87! I left by reply above. That's fine that we don't persist the TaskStat or the Map, but I would like to clean up that method for simplicity and readability.

@elingg - I just updated the request.  Instead of dealing with when to clear the taskMap, I decided to go back to the disposable map model and use it for temporary storage.  i separated out the code.  Let me know what you think

@mngo87, with the cleaner logic, the disposable map makes more sense. I think it is a reasonable design. Nice work! I just made one comment to address, but it LGTM

@elingg - let me know your thoughts on my comments and I'll address if needed.  Thanks for the review.

Responded, thanks!

@elingg - updated and tested.

Sweet! :100:


Mocha/Chai or Jasmine - client-side testing

Mocha/Chai or Jasmine - client-side testing
!story G17.6
!component test

Stared working with Jasmine.js for client-side testing.  Looked into plugin's, but I am not sure this is the way to go right now.  Been talking to Scottie to find out the best way to get this working in a Grails project

Jasmine testing environment has been added to the project in the web-app static file directory.  I also added the $inject.js library so that we could test inside of our modules.  I was having a problem writing tests against our existing code because we are following the module pattern, and putting everything in IIIFE's (Immediately-Invoked Function Expressions).  $ingest.js fixes this, and allows us to drill into the modules and test individual components.

Added three new spec's last night that test the $ajax request being sent to the create, update, and delete methods.  I think we should move this task to 'Done', with the understanding that new client-side development should be utilizing this new testing environment.


gatsby starter hangs

Description
Installed the Gatsby starter linked through your docs. Ran through some simple tests (posted, edit an existing blog post). The app successful posted, but unable to edit an existing post .. the terminal no loner permits to stop the app
Steps to reproduce

installed Gatsby starter which I linked to through your docs
Gatsby develop
opened the app in browser
4 opened the sidebar and posted
clicked on existing blog post
6 opened the side bar to edit
edits are not applied in the Gatsby blog
8 terminal is now unresponsive … unable to ctl c our of app

Expected result

blog post created (success)
blog post changed (failed)

Actual result
see above
Environment
win 10 environment with latest versions of nodejs

Can you provide a link to a public repository to demo this behavior?


Fix Link interaction Kakao

Close: #25

@Unlimity previously we did't have API 29 testing =) Now we can understand that some test can fails on some specific version.


Add link to release note or changelog.

Closes #905
Example PR: https://github.com/exoego/scala-steward-test-project/pull/94

It seems that some PRs include links to non-existent pages:

https://github.com/balhoff/arachne/pull/17
https://github.com/balhoff/arachne/pull/19


[Snyk] Upgrade html-snapshots from 3.10.1 to 3.10.2

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade html-snapshots from 3.10.1 to 3.10.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.

The recommended version was released on 2 days ago.

Release notes

Package name: html-snapshots

3.10.2 -<EMAIL_ADDRESS>

3.10.1 - 2024-06-05update examples, devdeps

    from html-snapshots GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

coverage: 99.245%. remained the same
when pulling 404615b9bb48d1e87f51551fbf5d3601645d3b34 on snyk-upgrade-f653b0c69230b677ede527cc8dc439bf
into a6420ee01615212c8278babcd6644890e4244f6b on master.


Rotating not going into full screen

below is my config, for some reason when switching to landscape, the player will not go into fullscreen. (I even confirmed that !isPortait() is true)
          <YouTubePlayer             ref={ytRef}             videoId={id}             autoPlay={false}             fullscreen={!isPortrait()}             showFullScreenButton={true}             showSeekBar={true}             showPlayPauseButton={true}             startTime={5}             style={{ width: "100%", height: 200 }}           />
this is awesome btw!

Platform and much more info about React version etc ?

@farad4y
react-native: 0.61.4
and its both IOS and Android for me

i met the same issue, change props fullscreen to true/false do not work.

This is a native library so when state changed, fullscreen parameter won't be sent native side.
If you want to use dynamic fullscreen param, view must be re-rendered.
@mattruddy @ducpt2


Add TrustSource reporter plugin

This adds the reporter plugin for the TrustSource JSON format.
To use it, simply specify 'TrustSource' in the list of report formats (-f).

Thanks @sselbach, I'll have a look once I'm back from vacation later this week.

@sselbach Please have a look at the failing tests. To start with, the commit message title needs to follow Conventional Commits, and a single sign-off line is enough.


Parsing error on fresh project creation

Creation Command
npx create-expo-stack movie-star --expo-router --tamagui --import-alias
When a project is started with this command, a parsing error is returned on page 404 ([...unmatched.tsx]). The project starts with the square brackets of the options in the <Stack.Screen> not closed.

looking into this

fixed and released in version 2.3.13, should be available on npm (out now)


Number Solver: Change colour palette.

Make the colour palette of the number solver match the theme of the other solvers in the page.
Use the blue-golden colour palette.
Don't change anything functionality wise.

I want to work on this project under JWOC'24

Go for it@SuvayuN


Support allOf in paths properties

Example of OpenAPI path:
/send-otp:
    post:
      description: Send OTP-code
      operationId: otp_send
      parameters:
        - description: Pika-pika!
          in: header
          name: X-Device-Platform
          required: true
          schema:
            allOf:
              - {$ref: '#/components/schemas/Platform'}
            description: Pika-pika!
            title: X-Device-Platform

It's already supported for schemas (look at the path /allof and schema #/components/schemas/AllOfResp)

https://github.com/artsmolin/pythogen/commit/3f7d0c50e8c7d43a753b637b41321187a7ab8c9d


Broker not authenticated with local DAPS

I have deployed an omejdnDAPS, a DSC version 7.0.1 and the latest version of the metadata broker in my local environment.
The issue is that the broker is not authenticating our local DAPS.
With a previous release of the metadata broker, in order to set-up it we used the command "mvn clean package"  to create a broker-core-4.2.8-SNAPSHOT.jar with the correct files configured (broker-core/src/main/resources/isstbroker-keystore.jks and application.properties with daps.url specified).
Currently, the "mvn clean package" is not working with the latest version of the metadata broker. I used this in order to create our "registry.gitlab.cc-asp.fraunhofer.de/eis-ids/broker-open/core" image.
Now, with the docker-compose.yml file which is at (https://github.com/International-Data-Spaces-Association/metadata-broker-open-core/tree/master/docker/composefiles/broker-localhost) I can configure properly the DAPS_URL and the IDENTITY_JAVAKEYSTORE
broker-core:
    image: registry.gitlab.cc-asp.fraunhofer.de/eis-ids/broker-open/core:latest
    container_name: broker-core
    volumes:
      - /etc/idscert/localhost:/etc/cert/
    restart: always
    environment:
    - SPARQL_ENDPOINT=http://broker-fuseki:3030/connectorData
    - ELASTICSEARCH_HOSTNAME=broker-elasticsearch
    - SHACL_VALIDATION=true
    - DAPS_VALIDATE_INCOMING=true
    - IDENTITY_JAVAKEYSTORE=/etc/cert/isstbroker-keystore.jks
    - COMPONENT_URI=https://localhost/
    - COMPONENT_CATALOGURI=https://localhost/connectors/
    - JWKS_TRUSTEDHOSTS=daps.aisec.fraunhofer.de,omejdn
    - DAPS_URL=https://omejdn/token
    expose:
    - "8080"

When I try to obtain the description of the metadatabroker from the Dataspace Connector it gives the following error:
curl -X 'POST' \'https://localhost:7080/api/ids/description?recipient=https%3A%2F%2Fbroker-reverseproxy%2Finfrastructure' \-H 'accept: */*' \ -d ''

Server response
Error: response status is 417
Response body
{
  "details": {
    "reason": {
      "properties": null,
      "@id": "https://w3id.org/idsa/code/NOT_AUTHENTICATED"
    },
    "payload": "An error occurred while verifying your token",
    "type": "de.fraunhofer.iais.eis.RejectionMessageImpl"
  },
  "message": "Received unexpected response message."
}

Is it possible to introduce/configure in the docker-compose.yml our own daps.crt?
This file is located at  (https://github.com/International-Data-Spaces-Association/metadata-broker-open-core/tree/master/docker/broker-core) and I assume that this is the problem why the broker is not authenticating our local DAPS.
Waiting for your response, thanks in advance.

I am not able of following your proposed solution:

The command "mvn clean package" is currently not working for the latest version of the Metadata Broker.
I need this command in order to create the target folder with the appropriate broker-core-x.x.x-SNAPSHOT.jar
With this SNAPSHOT I can create our own image "registry.gitlab.cc-asp.fraunhofer.de/eis-ids/broker-open/core"
Then, with this image I execute the docker-compose.yml and can set-up correctly the Metadata Broker so that it can interoperate with the other components.

I can not obtain the Metadata Broker self-description due to token not authenticated.
I need to change and use our file daps.crt that is inside metadata-broker-open-core/docker/broker-core/

@jfernandezsqs Can you please elaborate if the updated daps.crt helped you to get rid of the 'NOT_AUTHENTICATED' error?

I can not verify if the daps.crt is correct becuase the "mvn clean package" command is not working.
It is detailed in this issue https://github.com/International-Data-Spaces-Association/metadata-broker-open-core/issues/86
We need mvn clean package in order to set-up our local testbed

daps.crt was not set-up correctly.
Fixed.


[terra-embedded-content-consumer] Add screenreader support to announce context of embedded iframe content

Summary

Added screenreader support to announce context of embedded iframe content
What was changed:
Added visually hidden text before and after the iframe wrapper.
Why it was changed:
To provide additional context to screen reader users on when the embedded content will begin and end.
Testing

This change was tested using:

[ ] WDIO
[x] Jest
[x] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Visual Testing
https://github.com/cerner/terra-framework/assets/37230460/0465860d-9151-4596-bcc3-1f4f973b5929
https://github.com/cerner/terra-framework/assets/37230460/86ce370b-8fcd-4f43-9081-0b484b63bd80
https://github.com/cerner/terra-framework/assets/37230460/c1c63cae-d381-49a3-8630-8f50c2aeccd9
https://github.com/cerner/terra-framework/assets/37230460/73af2ed3-ec3d-4d07-8819-880d083ef9c4
Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9528

Thank you for contributing to Terra.
@cerner/terra

Could we rebase and resolve conflicts after addressing comments?

@sdadn @sycombs - This PR is ready for you to take another look when you get a chance. Thanks!

Code changes look good to me. Could we retest via the VO and JAWS to make sure the functionality still works as expected?

I retested and updated all of the recordings, looks like the functionality is still working as expected

The build is failing due to a failing terra-data-grid Jest test that does not appear to be related to these changes.

The build is failing due to an outdated terra-menu snapshot that does not appear to be related to these changes.


ARTEMIS-3488 Added env variable ARTEMIS_MASK_PASSWORD_CODE

I've reworked this (changed the property name, added docs, etc.) and sent #3780.


feat(aws-stepfunctions-tasks): service integration invocation for lambda (including callback pattern)

This PR allows one to work with Lambda Task states that implement the callback service integration pattern.
Fixes #2658

Pull Request Checklist

[X] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[X] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[X] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

This PR is used as a reference (and code share) for PR #2686

Duplicate of existing PR: https://github.com/awslabs/aws-cdk/pull/2686

Thanks for the post. I'm going to close this since it's purely for reference, but we've got the code now.


Why Sink.view is private ?

how can i implement my own sink ? thanks.

You can't, sorry. More optimizations are possible when we know the complete set of concrete types. I didn't want to open it up to be fully abstract. Everything should be possible with the types provided, though.


Spring DEBUG logging removed - corrected grammar

Hi Ernest,
a couple of minor changes:

application.properties: removed logging.level.org.springframework=DEBUG that I used when working with the previous PR. Sorry about that.
Corrected grammar on the team description.

Regards

Hi Jose,
No worries at all!
Best Regards


S3 Parallel Upload and Deletions

Fixes #1319

Now I understand that cache hit! So it checks if a poetry is available locally and if so, use it rather than installing it! Nice!

Yes! I can (and want) go over it in detail because it's a nice caching pattern that can be used for anything where packages are involved, including node.


nsc-events-nextjs-256-archive-functionality

Created ArchiveDialog component with functions for archiving event
Added isArchived to activityDatabase

https://github.com/SeattleColleges/nsc-events-nextjs/assets/22021615/40a624e6-04e4-4bec-b8fe-53e5c7e79ad1

I'm experiencing the same thing as @taylorpapke. I am able to archive the event successfully, the event is hidden on the frontend, and the backend is updated. I didn't create new events, but I do have other events that I have had for a while and they are not displaying even when there are less than 5 events visible. I think the other events not showing up may have to do with what we talked about with BC last quarter: how the events being displayed are limited to 5 events, except the deleted and archived events are still in the database but hidden, so our other events including new ones won't show up. I could be wrong though.
@cshimm Are you also running the backend using this PR at the same time with this PR?

So, I tested this PR and it is working as far as archiving events on the frontend and making the proper changes to the data on the backend:
However, I am running into an issue with creating events now. When I create an event, it will not display on the home page. I tested main and it is working so I think it might have to do with some of the changes that were made to HomeEventGetter.tsx or UpcomingEvent.tsx components. @keiffer213

As Hanan said there's a 5 event limit thats fetched from the backend, when we call archive we're only hiding the event on the frontend and adding any more then 5 won't show on the frontend unless we delete any of the first 5 from the database.

I got it working, thanks for the info @heosman

@Ali-7s @taylorpapke Let's get this PR reviewed and merged, and then address the 5 event limit in another issue. I'll add it to the product backlog for now.


allowedvalues ignored for APIObjectField if it's an enum type

I have an enum that I have implemented a Converter for to use a getLabel() method for conversion rather than the standard name value.  My allowedvalues values are ignored on APIObjectField and no matter what I do it simply shows the enum constants.

I see. I think the best way to proceed is to use the allowedvalues property of the ApiObjectField annotation to override the enum values. I'll implement that.


Unable to make it work

Hello,
I'm relatively new to VScode, and I can't get it to work. This is I have:
Version 1.23.1
Commit d0182c3417d225529c6d5ad24b7572815d0de9ac
Date 2018-05-10T17:11:17.614Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
I've looked at all the keyboard mappings and I can't find anything that would interfere with the Control+Shift+; key assignment.

If you go to settings --> keyboard shortcuts, and search for "Insert semicolon" you should be able to see what the hot key is currently mapped to. (probably ctrl + /).  I submitted a request to fix this, I think it's cause by different keyboard layouts.


support env.valueFrom for TF_VAR_ values from Secrets?

being able to create environment variables from secrets is super handy in k8s - I wonder if we should extend the EnvVar struct to also support k8s style valueFrom too?
So you could populate your TF vars as:
apiVersion: tf.isaaguilar.com/v1alpha1
kind: Terraform
metadata:
  name: tf1
spec:
  env:
  - name: TF_VAR_foo
    value: someValue
  - name: TF_VAR_bar
     valueFrom:
       secretKeyRef:
         name: mysecret
         key: token

or is there a nicer TF way to inject secret values?

I've started on a little PR but thought I'd check you liked this approach first

This is a good idea. The closer to k8s style resource definitions will have better adoption. Users can assume how to define their deployments more accurately; especially users like me who like to work by trail and error. :)


GECCO Error

Hi Matin,
when I run GECCO on the Lactobacillus_delbrueckii example dataset with bgcflow run, I get this error:
/usr/bin/bash: line 2: 657128 Illegal instruction     (core dumped) gecco run --genome data/interim/processed-genbank/GCA_000014405.1.gbk --output-dir data/interim/gecco/0.9.10/GCA_000014405.1 --antismash-sideload --jobs 2 --force-tsv 2>> logs/gecco/run/0.9.10_GCA_000014405.1.log
[Wed Sep 25 13:46:48 2024] Error in rule gecco:     jobid: 98     input: data/interim/processed-genbank/GCA_000014405.1.gbk     output: data/interim/gecco/0.9.10/GCA_000014405.1/GCA_000014405.1.clusters.tsv     log: logs/gecco/run/0.9.10_GCA_000014405.1.log (check log file(s) for error details)     conda-env: /mnt/data/studenti/agentile/bgcflow/.snakemake/conda/fc38642a72f0d9780c1726281ad2a8f0_     shell:
 gecco run --genome data/interim/processed-genbank/GCA_000014405.1.gbk             --output-dir data/interim/gecco/0.9.10/GCA_000014405.1             --antismash-sideload             --jobs 2             --force-tsv 2>> logs/gecco/run/0.9.10_GCA_000014405.1.log
(one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
Exiting because a job execution failed. Look above for error message Complete log: .snakemake/log/2024-09-25T134640.083718.snakemake.log WorkflowError: At least one job did not complete successfully. Stopping panoptes server: PID 655760
This is the log file:
2024-09-25T134640.083718.snakemake.log
If I run GECCO with snakemake -s /home/agentile/data/bgcflow/workflow/rules/gecco.smk, I get this specific error:
WorkflowError in file /home/agentile/data/bgcflow/workflow/rules/gecco.smk, line 22: Rule antismash_db_setup is not defined in this workflow. Available rules: gecco
Seems like it's finding problems in the snakefile.

Hi @andrekind17, can you also send me this file for debugging?
logs/gecco/run/0.9.10_GCA_000014405.1.log
From the error message: /usr/bin/bash: line 2: 657128 Illegal instruction     (core dumped), it seems that the issue came from the machine? Where are you running this?

Here it is, it's always empty (I run it multiple times):
0.9.10_GCA_000014405.1.log
All the other rules work on the example dataset, and I'm now trying on my data.
I'm running BGCFlow on a Linux server. These are the specifications:
uname -a
Linux elio 5.15.0-122-generic #132-Ubuntu SMP Thu Aug 29 13:45:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 22.04.5 LTS Release:        22.04 Codename:       jammy
lshw -short -C memory
H/W path             Device    Class          Description /0/0                           memory         144GiB System memory
lscpu
Architecture:             x86_64   CPU op-mode(s):         32-bit, 64-bit   Address sizes:          46 bits physical, 48 bits virtual   Byte Order:             Little Endian CPU(s):                   24   On-line CPU(s) list:    0-23 Vendor ID:                GenuineIntel   Model name:             Intel(R) Xeon(R) CPU E5-2630L v2 @ 2.40GHz     CPU family:           6     Model:                62     Thread(s) per core:   2     Core(s) per socket:   6     Socket(s):            2     Stepping:             4     CPU max MHz:          2800.0000     CPU min MHz:          1200.0000     BogoMIPS:             4799.81     Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi                            mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon p                           ebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monito                           r ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_d                           eadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr                           _shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts m                           d_clear flush_l1d Virtualization features:     Virtualization:         VT-x Caches (sum of all):         L1d:                    384 KiB (12 instances)   L1i:                    384 KiB (12 instances)   L2:                     3 MiB (12 instances)   L3:                     30 MiB (2 instances) NUMA:                        NUMA node(s):           2   NUMA node0 CPU(s):      0,2,4,6,8,10,12,14,16,18,20,22   NUMA node1 CPU(s):      1,3,5,7,9,11,13,15,17,19,21,23 Vulnerabilities:             Gather data sampling:   Not affected   Itlb multihit:          KVM: Mitigation: VMX disabled   L1tf:                   Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable   Mds:                    Mitigation; Clear CPU buffers; SMT vulnerable   Meltdown:               Mitigation; PTI   Mmio stale data:        Unknown: No mitigations   Reg file data sampling: Not affected   Retbleed:               Not affected   Spec rstack overflow:   Not affected   Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl and seccomp   Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization   Spectre v2:             Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP conditional; RSB filling; PBRSB                           -eIBRS Not affected; BHI Not affected   Srbds:                  Not affected   Tsx async abort:        Not affected


New Design

This will transform our old prototype UI into the new design and general functionality.  Only modifying the frontend for now with mock endpoints, will probably save the backend for another PR.

I think I'm going to merge this at this point.  I've implemented everything major except for the "thank you" page.  Everything is still ugly and needs another pass to make it match the designs, but it's in a place that should make that easy as I collaborate with Malte.

@dionjwa Heads up that this is going in.  Let me know if you want a chance to code review stuff like this in the future, sorry for merging while you're offline :)


Router panic

#[component]
pub fn App(cx: Scope) -> Element {
    view! { cx,

          <Router>

               <ContentLayer />

          </Router>

    }
}

#[component]
pub fn ContentLayer(_cx: Scope) -> Element {
    view! {
        _cx,

           <Routes>
              <Route path="/doc/about" element=move |cx| view! { cx,
"about"
 } />
           </Routes>

    }
}

From what I can get from the stack trace it's happening here:

$leptos_router::components::routes::Routes::{{closure}}::h6cc2a448d4d924f1

Full stack: localhost-1669653084164.log

Okay so my impression is that this is strange behavior that has to do with the order of evaluation of element children in hydration mode, and therefore executes <ContentLayer/> before executing <Router/>, and therefore not having access to the context <Router/> is supposed to provide.
If you need a very shady temporary fix to unblock you, or if anyone else comes across this issue in the meantime, it does not panic if <Router/> has another child that precedes <ContentLayer/>, like this
view! { cx,

          <Router>

<ContentLayer />

          </Router>

    }

Obviously I'll work on actually fixing it.

Thanks for the tip!


Routing Logic Clarification

From the docs it says:

Routing rules have matching priority that is based on node types and does not depend on routes definition order:

Static nodes, for example, /users/
Named nodes, for example, :id.
Wildcard nodes, for example, *path.

The following routes are sorted by their matching priority from the highest to the lowest:

/users/list.
/users/:id.
/users/*path.

Clarification needed
Based on this example from the docs I can conclude, that the Wildcard node in this particular example will never match/hit. Or am I missing something?

Ok, so turned out I had a knot in my thinking :D
It of course matches nested paths. So time to get some fresh air and closing this one


Incompatible with opencv-python

Hello,
I tried to install photobooth-app on my raspberry (raspbian bullseye, python 3.9.2) yesterday and I got the following error:
$ pip install photobooth-app
...
Collecting photobooth-app
  Downloading https://www.piwheels.org/simple/photobooth-app/photobooth_app-0.1.0b4-py3-none-any.whl (8.4 MB)
     |████████████████████████████████| 8.4 MB 8.6 MB/s
  Downloading https://www.piwheels.org/simple/photobooth-app/photobooth_app-0.1.0b3-py3-none-any.whl (8.4 MB)
     |████████████████████████████████| 8.4 MB 8.5 MB/s
  Downloading https://www.piwheels.org/simple/photobooth-app/photobooth_app-0.1.0b2-py3-none-any.whl (8.4 MB)
     |████████████████████████████████| 8.4 MB 3.2 MB/s
  Downloading https://www.piwheels.org/simple/photobooth-app/photobooth_app-0.1.0b1-py3-none-any.whl (8.4 MB)
     |████████████████████████████████| 8.4 MB 10.2 MB/s
ERROR: Cannot install photobooth-app==0.1.0b1, photobooth-app==0.1.0b2, photobooth-app==0.1.0b3, photobooth-app==0.1.0b4, photobooth-app==0.1.0b5, photobooth-app==0.1.0rc12, photobooth-app==0.1.0rc3, photobooth-app==0.1.0rc4, photobooth-app==0.1.0rc5, photobooth-app==0.1.0rc6, photobooth-app==0.1.0rc7, photobooth-app==0.1.0rc8 and photobooth-app==0.1.0rc9 because these package versions have conflicting dependencies.

The conflict is caused by:
    photobooth-app 0.1.0rc12 depends on opencv-python<4.9 and >=4.7
    photobooth-app 0.1.0rc9 depends on opencv-python<4.9 and >=4.7
    photobooth-app 0.1.0rc8 depends on opencv-python<4.9 and >=4.7
    photobooth-app 0.1.0rc7 depends on opencv-python<4.9 and >=4.7
    photobooth-app 0.1.0rc6 depends on opencv-python~=4.7.0
    photobooth-app 0.1.0rc5 depends on opencv-python~=4.7.0
    photobooth-app 0.1.0rc4 depends on opencv-python~=4.7.0
    photobooth-app 0.1.0rc3 depends on opencv-python~=4.7.0
    photobooth-app 0.1.0b5 depends on opencv-python<<IP_ADDRESS> and >=<IP_ADDRESS>
    photobooth-app 0.1.0b4 depends on opencv-python<<IP_ADDRESS> and >=<IP_ADDRESS>
    photobooth-app 0.1.0b3 depends on opencv-python<<IP_ADDRESS> and >=<IP_ADDRESS>
    photobooth-app 0.1.0b2 depends on opencv-python<<IP_ADDRESS> and >=<IP_ADDRESS>
    photobooth-app 0.1.0b1 depends on opencv-python<<IP_ADDRESS> and >=<IP_ADDRESS>

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

Full error logs
Thank you

Hi, what system you use? Apt is up to date?
See the full log, there is a problem in pip cmake building opencv . That's why it complains.

I find this is an issue on the 32bit version of raspberry pi os.
I highly recommend to change to the 64Bit version, on that version installation works fine.
Otherwise if you get it to run on 32bit machine I would be glad if you could provide the procedure to solve.

Hmm I will try again with a fresh 64bits install this weekend, thanks

Confirmed that 64bit works and has no drawbacks so far.
I close this issue. Please reopen if needed. Have fun ✨

Hi,
Yes I just tried again and got no issue with 64 bits rapsbian. Not sure what changed since when I tested in spring but I have my solution :)


FeinCMS prevents migration in Django 1.11

I'm trying to upgrade my project to Django 1.11, and when I try to run manage.py makemigrations myapp, I get the error:
Traceback (most recent call last):
  File "manage.py", line 9, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 364, in execute_from_command_line
    utility.execute()
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute
    django.setup()
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/__init__.py", line 27, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/apps/registry.py", line 108, in populate
    app_config.import_models()
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/apps/config.py", line 202, in import_models
    self.models_module = import_module(models_module_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/feincms/models.py", line 16, in <module>
    from django.contrib.contenttypes.models import ContentType
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/contrib/contenttypes/models.py", line 139, in <module>
    class ContentType(models.Model):
  File "/usr/local/myproject/.env/local/lib/python2.7/site-packages/django/db/models/base.py", line 118, in __new__
    "INSTALLED_APPS." % (module, name)
RuntimeError: Model class django.contrib.contenttypes.models.ContentType doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS.

This error is common in Django apps that haven't been upgraded to Django 1.10+. However, from the Travis tests, it looks like you officially support Django 1.11. Why is FeinCMS triggering and exception from ContentTypes?

Hmm. Did you remove django.contrib.contenttypes from INSTALLED_APPS by chance? FeinCMS seems to depend on the contenttypes app, probably because we are using the contenttypes' ID for a cache key somewhere.

No, I haven't changed anything in my INSTALLED_APPS. It seems to be a bug in Django 1.11. I was trying to make migrations for just a single app, and apparently that's no longer fully supported. When I removed the app name, it ran without error.


Topic state machine

Migrate the state enum in Topic to a state machine in the access attribute.
See documentation.

Pull Request Test Coverage Report for Build 261

28 of 28 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 92.601%

Totals

Change from base Build 254:
0.03%

Covered Lines:
1702

Relevant Lines:
1838

💛  - Coveralls


Working foliofn endpoints

I tested these and seems to work.

Awesome, thanks for doing this.  I've released this in version 1.0.13 (the lucky version).
Cheers 🥂


Feature flag support (e.g. launchdarkly)

Other options:

flagsmith
Others?

https://github.com/open-feature/rust-sdk


useFormContext cannot be used because register is of undefined union type

The current useFormContext function has an issue where the returned value from the inject function can be undefined, causing a need to validate the stability of register. However, since defaultInjectionKey is provided, there is no actual scenario where undefined would be returned.
Solution
Updated the useFormContext function to cast the injected value to FormHandlerReturn directly, ensuring it is always a valid context.

Your contribution was included in the v1 release :)


Precompile process. Uglifier::Error: In strict mode code.

Is currently not possible to deploy or, more specifically, run rails RAILS_ENV=production assets:precompile when Binda API is installed.
Rails throws the following error:
I, [2018-05-22T12:18:37.829546 #4938]  INFO -- : Writing /home/myapp_deploy/admin/public/assets/application-e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855.css.gz
rake aborted!
Uglifier::Error: In strict mode code, functions can only be declared at top level or immediately within another function.
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/uglifier-4.1.10/lib/uglifier.rb:234:in `parse_result'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/uglifier-4.1.10/lib/uglifier.rb:216:in `run_uglifyjs'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/uglifier-4.1.10/lib/uglifier.rb:168:in `compile'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/uglifier_compressor.rb:53:in `call'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/uglifier_compressor.rb:28:in `call'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:75:in `call_processor'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:57:in `block in call_processors'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `reverse_each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/processor_utils.rb:56:in `call_processors'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/loader.rb:134:in `load_from_unloaded'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/loader.rb:60:in `block in load'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/loader.rb:317:in `fetch_asset_from_dependency_cache'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/loader.rb:44:in `load'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:20:in `block in initialize'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/cached_environment.rb:47:in `load'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/base.rb:66:in `find_asset'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/base.rb:73:in `find_all_linked_assets'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:142:in `block in find'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:114:in `block (2 levels) in logical_paths'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:228:in `block in stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:212:in `block in stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:227:in `stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:231:in `block in stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:212:in `block in stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:227:in `stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:231:in `block in stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:212:in `block in stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:209:in `stat_directory'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/path_utils.rb:227:in `stat_tree'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:105:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:105:in `block in logical_paths'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:104:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/legacy.rb:104:in `logical_paths'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:140:in `find'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:185:in `compile'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-rails-3.2.1/lib/sprockets/rails/task.rb:68:in `block (3 levels) in define'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-3.7.1/lib/rake/sprocketstask.rb:147:in `with_logger'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/sprockets-rails-3.2.1/lib/sprockets/rails/task.rb:67:in `block (2 levels) in define'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `block in execute'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:271:in `execute'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:213:in `block in invoke_with_call_chain'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:193:in `invoke_with_call_chain'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/task.rb:182:in `invoke'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:160:in `invoke_task'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `each'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:116:in `block in top_level'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:125:in `run_with_threads'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:110:in `top_level'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:83:in `block in run'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:186:in `standard_exception_handling'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/lib/rake/application.rb:80:in `run'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
/home/myapp_deploy/.rbenv/versions/2.5.1/bin/rake:23:in `load'
/home/myapp_deploy/.rbenv/versions/2.5.1/bin/rake:23:in `<top (required)>'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `load'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:75:in `kernel_load'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli/exec.rb:28:in `run'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:424:in `exec'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:27:in `dispatch'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/cli.rb:18:in `start'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/exe/bundle:30:in `block in <top (required)>'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/lib/bundler/friendly_errors.rb:122:in `with_friendly_errors'
/home/myapp_deploy/.rbenv/versions/2.5.1/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/exe/bundle:22:in `<top (required)>'
/home/myapp_deploy/.rbenv/versions/2.5.1/bin/bundle:23:in `load'
/home/myapp_deploy/.rbenv/versions/2.5.1/bin/bundle:23:in `<main>'
Tasks: TOP => assets:precompile

The current workaround is to comment out line 43 in conifg/environments/production.rb contained in the app that mounts Binda API.
# config.assets.js_compressor = :uglifier

The issue seems to be cause by this gem as Binda doesn't generate any issue when Binda API is not present.

The issue might be caused by a import statement not executed at the top of the file but after some code. When uglifier compile javascript files in strict mode this generates a error.

I passed by set in production environment
config.assets.js_compressor = Uglifier.new(harmony: true, compress: { unused: false })
but have strange error on production( worked on development), maybe related with compile JS problem ?
Uncaught Error: Cannot use e "__Schema" from another module or realm.
Uncaught ReferenceError: GraphiQL is not defined

It's definitely related to the way JS is compiled.
Binda uses a script compiled with Webpack which is then compiled by Uglifier during the precompile process. This was mandatory as, at the time, Webpacker didn't offer the possibility to run Webpack on Rails Engines.
I've seen they have done some progress so it might be worth trying to replace the Webpack configuration with Webpacker into Binda. (see https://github.com/rails/webpacker/issues/348)
Otherwise we need to tweek the current Webpack config (which needs updates anyway).

Hi @lufutu. Can you share how to reproduce your error?
I've been deploying an application with Binda (from my fork) and Binda API (from current master) on Heroku and had no issue.
Are you using Capistrano? Let me know so I can investigate further.

Just seen that the bug I was referencing on May was due to a graphiql-rails gem issue.
@lufutu I've seen you have found it as well.
I'm closing this issue and opening another one with the one you referred above


Contribution teplates

Describe the problem you're trying to solve
The goal is to elaborate a git workflow for contributing
Describe your solution
I wrote templates for Issues & PR as well as a CONTRIBUTING.md in order to guide people through the convention they need to respect in order to contribute to the project.
Describe the task list

[X] Contributing.md
[X] Issue & PR templates

[Edit]
The CONTRIBUTING.md has nothing to do in a template repository. There will be only one in the main project repository.
Tasks:

[ ] Remove CONTRIBUTING.md


PopUp on the tittle bar

Issue:
PopUp on the tittle bar.
Expected Behavior:
PopUp must not occupy the title bar.
Environment:
Platform: Windows
.NET Version: 8.0.0
Mopups Version: 1.3.1
Maui Version: 8.0.6
Steps to Reproduce:

Clone Project.
Click the button
See that the pop up are in the windows tittle bar.

Repro
https://github.com/MADSENSE/MADSENSE.MAUI.Sample.App/tree/mopup-on-tittle-bar
Image

You can probably just add a margin to ur frame to avoid it.
I don't personally see this as an issue, as there might be use cases someone would want it to cover the entirety of the page behind it including the title bar


Add GraphQL Service Generation Support with CLI Command

Purpose
Generate GraphQL service for a given GraphQL schema with CLI command.
Samples
CLI command
bal graphql [-i | –-input] <graphql-schema-file-path>
            [-o | –-output] <output-location>
            [-m | --mode] <service-operation-mode>
            [-r | –-use-records-for-objects]

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


Support Python 3.7 timezone in datetime bindings

As part of #200 (which added the Python datetime bindings), the update for the full Python 3.7 interface, which includes:

PyDateTime_TimeZone_UTC
PyTimeZone_FromOffset
PyTimeZone_FromOffsetAndName

The timezone API was added to CPython in PR 5032.
I believe this can be accompanied on the Rust side by a PyFixedTimeZone object or something. It's worth noting that no _Check methods accompany this, because you are really not intended to subclass these things.

Can I get some pointers on how to provide a wrapper for PyDateTime_TimeZone_UTC?
I see that we can do PyObject::from_borrowed_ptr(py, PyDateTimeAPI.TimeZone_UTC) but should we do it the same way as python::NotImplemented()? I wonder how should we handle the singleton in this case?
Also, how can one do <PyXXXUTC as PyTryFrom>::try_from(ob) when implementing FromPyObject for chrono::Utc? I don't get how do we PyTryFrom a thing that does not have a thin wrapper, even if we have, I am still confused if we can use pyobject_native_type! for this?

@pickfire I'm thinking about the correct design for this; please allow me a few days.

Just discussing, I will only get to use FromOffset (which correlates to chrono FixedOffset) and UTC (which correlates to chrono UTC), so minimally I require those two, but while doing that I can probably add the FixedOffsetWithName as well.
I believe I can just start with PyTimeZone_FromOffset since that is straightforward. Maybe I will keep UTC for later.

@pickfire maybe #1573 gets you started? With that PR you could do ffi::PyDateTime_TimeZone_UTC.as_ref(py) to get a &PyAny representing the singleton.


[ECS] Prefixed version and custom sniff testing has misses parent test case

@TomasVotruba I've installed dev-main, now I got Class 'Symplify\PackageBuilder\Testing\AbstractKernelTestCase' not found in .../vendor/symplify/easy-coding-standard/src/Testing/PHPUnit/AbstractCheckerTestCase.php:19. Ohhhh.
Originally posted by @ERuban in https://github.com/symplify/symplify/issues/3422#issuecomment-884064757

Hi, @TomasVotruba
any updates or ideas how to fix it?

Hi, I would create reproducible repository and try to update AbstractCheckerTestCase namespace in the /vendor, untill it works. Then apply the manual change in as a script in scoper.php file.

Ok, so I've created reproducible repository https://github.com/ERuban/ecs-testing-issue-example
Have tried to do some in the /vendor but without success.

After 2 days of work, I think I've made some progress. For future generations of scoping and downgrading explorers. There have been couple of bugs to solve this issue:

make sure the regex starts and ends with same character https://github.com/symplify/symplify/commit/7cb57dc83212eb6a5c6d21e3fdc14eb21d6ce576, otherwise there is silent error that leads to skipping whole file (I wish there was an exceptoin, but php-scoper ignores it)
include scoper-autoload.php at the start of your project - https://github.com/symplify/symplify/commit/4c9c0445c5c55ceb754414b8eaca6a38c7d82996, otherwise all un-scoped classes are ignored
make sure you downgrade to correct version - to PHP 7.1, not to PHP 7.0, the PHPUnit will fail on extra void type then - https://github.com/symplify/symplify/commit/95f5ca6bbb6e794f7f4d5d0b83929bc3a4a24ac5
make the Abstract*TestCase as simple as possible, avoid to multiple inheritance that would require complex logic hard to debug - https://github.com/symplify/symplify/commit/826cd7858266b1a5bd604c91fcb7cce1ef401aac

@ERuban Could you verify in your test repository? I tried it myself, but want to be sure it doesn't work only on my machine ;)

Thanks for confirmation :parachute: :+1:

The 9.4.25 has been just tagged :hammer: