Update homebrew dependency and assorted boilerplate

Potential alternative to or addition to #1.

Coverage remained the same at 100.0% when pulling ab53f5cb70fc65aefd0c2417fc28b7cfb3c8ba65 on jdh-update into 4bf40c32783def4e74b2163fadc29f128eb58f46 on master.

Coverage remained the same at 100.0% when pulling 2516547b8954a61ed534b964e432fed49cdfb110 on jdh-update into 4bf40c32783def4e74b2163fadc29f128eb58f46 on master.

Coverage remained the same at 100.0% when pulling e06f00d7bcf6c47426a650d446b3cd687194742e on jdh-update into 4bf40c32783def4e74b2163fadc29f128eb58f46 on master.

Coverage remained the same at 100.0% when pulling 8665ddbbaaed751b0f2f05035da70723c6d104a8 on jdh-update into 4bf40c32783def4e74b2163fadc29f128eb58f46 on master.

Coverage remained the same at 100.0% when pulling e474a89ddf6a070955bd6a735f6fb8740034e111 on jdh-update into 4bf40c32783def4e74b2163fadc29f128eb58f46 on master.


If tags is string, split on commas assuming CSV formatting.

This should fix #358! I just split on any "string" tags on commas (plus any number of spaces) in order to generate an array of tags.
I've tested it on my local environment and it works great. That said, I'm not certain that I've accounted for all edge cases, so please let me know if anything I've missed. Thanks!

Thanks for taking the time to create a PR! Sorry for being so slow to respond. This looks good, I'll merge it in and include it in the release later today.


ENI: fix calculateExcessIPs excessive calculate of excess ip

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc
[x] Thanks for contributing!

If usedIPs+preAllocate not over minAllocate + maxAboveWatermark and availableIPs over minAllocate + maxAboveWatermark, only care  IPs out of minAllocate + maxAboveWatermark calculateExcessIPs.
Fixes: #27970
ENI: fix calculateExcessIPs excessive calculate of excess ip

I left a comment on the issue if this is really intended: https://github.com/cilium/cilium/issues/27970#issuecomment-1754714778

Thanks for your patience in explaining this to me. I agree that this is a bug.
Could you also update the documentation to match the new formula? Thanks!
https://github.com/cilium/cilium/blob/16e4b689daf1f47a429aeae23f4d106bdbb8020d/Documentation/network/concepts/ipam/eni.rst#L295

I think these failed tests do not relate to this PR. Does it need to be rebased to the main?

Yes, I think recent the cilium-dbg rename requires a current branch for CI to pass.

The quay.io is unstable it responds http 500 for push manifest.

/test

The quay.io is unstable it responds http 500 for push manifest.

You will have to re-trigger the build, otherwise other CI workflows will fail due to the missing image. To re-trigger the image build, either do a force-push or close and reopen the PR

I will fix this
level=info msg="Synchronized ENI information" numInstances=1 numSecurityGroups=2 numSubnets=1 numVPCs=1 subsys=eni
level=info msg="Synchronized ENI information" numInstances=1 numSecurityGroups=2 numSubnets=1 numVPCs=1 subsys=eni
level=info msg="Synchronized ENI information" numInstances=1 numSecurityGroups=2 numSubnets=1 numVPCs=1 subsys=eni
level=info msg="Releasing excess IPs from node" available=18 excess=5 excessIps="[<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]" instanceID=i-testNodeManagerReleaseAddress-1 name=node3 releasing="[<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]" selectedInterface=75e5dd75-05f7-462c-aba6-33d5d8b00487 selectedPoolID=s-1 subsys=ipam used=10
level=info msg="Synchronized ENI information for the corresponding instance" instance=i-testNodeManagerReleaseAddress-1 numSecurityGroups=2 numSubnets=1 numVPCs=1 subsys=eni
    node_manager_test.go:473:
        ... obtained int = 13
        ... expected int = 15

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃   FAIL  package: github.com/cilium/cilium/pkg/ipam   ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
--- FAIL: Test (13.48s)
--- FAIL: Test/IPAMSuite (13.48s)
--- FAIL: Test/IPAMSuite/TestNodeManagerReleaseAddress (6.04s)
level=info msg="Discovered new CiliumNode custom resource" name=node3 subsys=ipam
level=warning msg="Unable to compute pending pods, will not surge-allocate" error="pod store uninitialized" instanceID= name=node3 subsys=ipam
level=info msg="Resolving IP deficit of node" available=0 availableForAllocation=2048 emptyInterfaceSlots=0 instanceID= maxIPsToAllocate=19 name=node3 neededIPs=15 remainingInterfaces=0 selectedInterface= selectedPoolID=global subsys=ipam used=0
level=warning msg="Unable to compute pending pods, will not surge-allocate" error="pod store uninitialized" instanceID= name=node3 subsys=ipam
level=info msg="Resolving IP deficit of node" available=19 availableForAllocation=2029 emptyInterfaceSlots=0 instanceID= maxIPsToAllocate=8 name=node3 neededIPs=4 remainingInterfaces=0 selectedInterface= selectedPoolID=global subsys=ipam used=19
level=info msg="Releasing excess IPs from node" available=27 excess=8 excessIps="[18 17 16 15 14 13 20 19]" instanceID= name=node3 releasing="[18 17 16 15 14 13 20 19]" selectedInterface= selectedPoolID=global subsys=ipam used=10
    node_manager_test.go:505:
        ... obtained int = 19
        ... expected int = 18

/test


Workspaces value does not match match config value

Problem Description
I've recently upgraded to xmonad 0.13 and xmonad-contrib 0.13, ever since I'm getting a different set of workspaces then defined in my config. I'm getting the default 1-9 workspaces instead of the 1-4 I've defined within the config.
Configuration File
import XMonad
import XMonad.Config.Desktop
import XMonad.Hooks.ManageDocks

import XMonad.Hooks.Minimize
import XMonad.Layout.Minimize

main = xmonad desktopConfig
    { terminal           = "termite"
    , modMask     = mod4Mask
    , layoutHook         = minimize . desktopLayoutModifiers . avoidStruts $ layoutHook desktopConfig
    , workspaces = ["1", "2", "3", "4"]
    , manageHook = manageHook desktopConfig <+> manageDocks
    , handleEventHook = minimizeEventHook
    }

I get the following output behavior within GHCi (which seems correct):
workspaces $ desktopConfig { workspaces = ["1"] }
["1"]

If I change the workspaces to ["a", "b", "c", "d"] I get a set of workspaces of a, b, c, d, 3, 4, 7, 8, 9.

I think someone needs to drop a trace around defaultConfig's workspaces to see if it gets evaluated before the user config is installed.
@chrissound, can you try this with a config based on defaultConfig instead of desktopConfig? An additional test might be to remove desktopLayoutModifiers from the layoutHook. (This is probing for a specific reference that might be happening.)
And you should remove the avoidStruts in any case; desktopLayoutModifiers handles it (and in the future will likely handle more things as well).

Interestingly if I set the workspaces to ["1", "2", "3], quit xmonad (modMask + Q) and execute startx - then get a set of workspaces with values of 1, 2, 3, 8, 9, c, d... - so it must be picking up these old values from somewhere?
Here is a further minimal config:
import XMonad
import qualified Data.Map as M
import XMonad.Actions.CycleWS

main = xmonad $ def {
          modMask     = mod4Mask
        , workspaces = ["1", "2", "3"]
        , terminal           = "lxterminal"
        , keys = myKeys <+> keys def
        }

myKeys conf@XConfig {XMonad.modMask = modm} = M.fromList [
               ((modm, xK_e), prevWS)
             , ((modm, xK_u), nextWS)
             ]

I deleted the ~/.xmonad/xmonad.state file and then restarted and got the correct workspace values.


use do_crt1 like other cores

Problem description
There were compilation errors on BH due to unresolved variables
What's changed
Changed the initialization of slave_idle_erisc to match that of other cores, using do_crt1
Checklist

[ ] Post commit CI passes
[x] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

The failing test in post-commit tests is related to an issue with another commit. Verified latest main fixes it locally


Adds footer to non-landing pages

Works alongside marble PR #98 to make the footer from the wedeploy.com landing page available to the non-landing pages

Just started reviewing :) :octocat: Sent from GH.

Just started reviewing :) :octocat: Sent from GH.


[wlgen] CPUs specification not working on SMP platorms

Reported by @jlelli
When running on a non big.LITTLE system, pinning tasks based on CPUs type specifiers like "bigs_first" is not possible because of the missing "bl" module in devlib.
However, still we want to be able to run workloads defined using these attributes.
Thus, we need to map these configuration options to proper CPUs.

Fixed in ea9ffe39f2296c9c1acd76ebede497a3a04a81e0


Free zooming

Free zooming, switch level when scale factor would be >1 or <0.5

Do not load all layers' tiles anymore at their own locations; find a way to scale them where they belong. This also helps with loading lags, as the older, off-resolution one would be shown until there is higher resolution content.

A method where there are only textures for a window size, they are dragged in [0, size] steps and map images are placed to each texture worked, but the swap of textures resulted in significant glitches when dragging.


Fixed #24391 -- Call initial callable only once for .value()

@timgraham - this addresses https://code.djangoproject.com/ticket/24391 without changing the API.
I've tested this manually, locally.

I initially wrote this to accommodate multiple accesses to the field to support specific kinds of manual form usage in a template, etc. (TIL: every time you form['field'] you get a new instance of BoundField). I did this by caching the attribute as self.form._<field name>_initial_result Instead of caching on the BoundField. I removed that to keep the patch simple at first, in case there needed to be more conversation about this approach in general.

@timgraham I'll get all those updates in there after work tonight.
In the meantime, what did you think about my comment above, the one pertaining caching the attribute on self.form, to allow for many accesses of the same field while only ever calling initial once? Or, as an alternative, do you think it would be feasible to memoize BoundField here @ https://github.com/orokusaki/django/blob/master/django/forms/forms.py#L123 (would also be a performance optimization)?

I think it might be better to do the evaluation of initial on the form itself. Having the widget evaluate initial and then cache it back on the form seems a bit convoluted. Here is the code I've been playing around with:
diff --git a/django/forms/fields.py b/django/forms/fields.py
index 6d1c145..eda9825 100644
--- a/django/forms/fields.py
+++ b/django/forms/fields.py
@@ -33,6 +33,7 @@ from django.utils.deprecation import (
 )
 from django.utils.duration import duration_string
 from django.utils.encoding import force_str, force_text, smart_text
+from django.utils.functional import SimpleLazyObject
 from django.utils.ipv6 import clean_ipv6_address
 from django.utils.six.moves.urllib.parse import urlsplit, urlunsplit
 from django.utils.translation import ugettext_lazy as _, ungettext_lazy
@@ -92,7 +93,19 @@ class Field(six.with_metaclass(RenameFieldMethods, object)):
         # localize -- Boolean that specifies if the field should be localized.
         # label_suffix -- Suffix to be added to the label. Overrides
         #                 form's label_suffix.
-        self.required, self.label, self.initial = required, label, initial
+        self.required = required
+        self.label = label
+
+        def lazy_initial():
+            data = initial()
+            # If this is an auto-generated default date, nix the
+            # microseconds for standardized handling. See #22502.
+            if (isinstance(data, (datetime.datetime, datetime.time)) and
+                    not getattr(self.widget, 'supports_microseconds', True)):
+                data = data.replace(microsecond=0)
+            return data
+
+        self.initial = SimpleLazyObject(lazy_initial) if callable(initial) else initial
         self.show_hidden_initial = show_hidden_initial
         self.help_text = help_text
         self.label_suffix = label_suffix
diff --git a/tests/model_formsets/tests.py b/tests/model_formsets/tests.py
index 217a1a1..1fd354f 100644
--- a/tests/model_formsets/tests.py
+++ b/tests/model_formsets/tests.py
@@ -1112,7 +1112,7 @@ class ModelFormsetTest(TestCase):

         self.assertEqual(len(formset.forms), 1)  # this formset only has one form
         form = formset.forms[0]
-        now = form.fields['date_joined'].initial()
+        now = form.fields['date_joined'].initial
         result = form.as_p()
         result = re.sub(r'[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}:[0-9]{2}(?:\.[0-9]+)?', '__DATETIME__', result)
         self.assertHTMLEqual(result,
@@ -1135,7 +1135,7 @@ class ModelFormsetTest(TestCase):

         # now test for when the data changes

-        one_day_later = now + datetime.timedelta(days=1)
+        one_day_later = now._wrapped + datetime.timedelta(days=1)
         filled_data = {
             'membership_set-TOTAL_FORMS': '1',
             'membership_set-INITIAL_FORMS': '0',

There is a test failure but I'm not sure it represents an actual use case. The model is using this code for the default:
callable_default_counter = itertools.count()
callable_default = lambda: next(callable_default_counter)

Failure:
======================================================================
FAIL: test_formfield_initial (forms_tests.tests.tests.FormsModelTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/tests/forms_tests/tests/tests.py", line 197, in test_formfield_initial
    self.assertNotEqual(r1, r2)
AssertionError: '<input id="id_callable_default" name="callable_default" type="number" value="4" />' == '<input id="id_callable_default" name="callable_default" type="number" value="4" />'======================================================================
FAIL: test_formfield_initial (forms_tests.tests.tests.FormsModelTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/tests/forms_tests/tests/tests.py", line 197, in test_formfield_initial
    self.assertNotEqual(r1, r2)
AssertionError: '<input id="id_callable_default" name="callable_default" type="number" value="4" />' == '<input id="id_callable_default" name="callable_default" type="number" value="4" />'

@timgraham I like your approach much better.
I also strongly agree that having a callable that maintains global (module level), like in the failing test, is probably not a real use case. However, I'm a bit confused as to why that test is failing. It appears as though the form is memoizing the initial result across 2 instantiations of the form. Am I following correctly?
Pertaining the memoizing of BoundField, your implementation seems really simple, clean, and straight forward, especially since tests pass.

I am confused by the test failure as well.

@timgraham Ah, of course. Field is only instantiated one time (at a forms module's load time), so SimpleLazyObject is being set up with a _wrapped value that is the result of calling initial the first time it is accessed, which means that Field is not a candidate for memoizing the result of initial. This means that best viable option might still be to memoize the result on the BoundField instance, which requires memoizing the BoundField instance on BaseForm (your second snippet). If I make a patch with the initial changes you had requested, and with the bound_fields_cache code, do you think there's a chance for it to get merged, given proper review from you and some of your peers?

@timgraham Your second approach (with self.bound_fields_cache) seems good. Can we agree on _bound_field_cache, though. I don't want people to use or even rely on it.

Updated in https://github.com/django/django/pull/4206

Closing this PR in favor of #4206 opened by @timgraham . Thank you for the patch, @orokusaki :smile:

@MarkusH thanks for the heads up. I meant to go check if out right after work, but I'm just now getting to it.


Bug:

PHP Version
7.3
CodeIgniter4 Version
31
CodeIgniter4 Installation Method
Manual (zip or tar.gz)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
phpdbg
Database
MySQL
What happened?
in codeginter please paste this html code in form Waqas Maqbool'
you will see success alert i want to show it as text
Steps to Reproduce
in codeginter please paste this html code in form Waqas Maqbool'
you will see success alert i want to show it as text
Expected Output
success class
Anything else?
No response

Can you provide proper information? What type of issue you are facing?

This seems to be spam. Closing.


update to 0.3.6

Changelog:

update version, checksum
arch-specific builds

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:21: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:21: version_constraints_missing_whitespace: Packages and their version constraints must be space separated
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:25: remove_python_pinning: On arch specific packages, python deps should not be constrained.
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:25: version_constraints_missing_whitespace: Packages and their version constraints must be space separated
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:41: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, reference https://spdx.org/licenses/
WARNING: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:42: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:42: missing_description: The recipe is missing a description
WARNING: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:42: missing_doc_source_url: The recipe is missing a doc_source_url
ERROR: /tmp/abs_f4y5krhwy0/clone/recipe/meta.yaml:42: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_10s23biiqj/clone/recipe/meta.yaml:44: invalid_license_family: The recipe has an incorrect about/license_family value.
WARNING: /tmp/abs_10s23biiqj/clone/recipe/meta.yaml:44: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_10s23biiqj/clone/recipe/meta.yaml:44: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_10s23biiqj/clone/recipe/meta.yaml:44: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_cbeu7xl288/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_cbeu7xl288/clone/recipe/meta.yaml:45: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_c4mkl3vzgp/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_c4mkl3vzgp/clone/recipe/meta.yaml:45: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_80wjtmqjry/clone/recipe/meta.yaml:46: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_80wjtmqjry/clone/recipe/meta.yaml:46: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_277v6rwhr_/clone/recipe/meta.yaml:46: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_277v6rwhr_/clone/recipe/meta.yaml:46: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_86cmxax6dm/clone/recipe/meta.yaml:45: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_86cmxax6dm/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_18_loknvfg/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_18_loknvfg/clone/recipe/meta.yaml:45: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_6axh1ubetm/clone/recipe/meta.yaml:45: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_6axh1ubetm/clone/recipe/meta.yaml:45: missing_license_url: The recipe is missing a license_url
Warnings were found


Feature Columns

Feature columns added in website cms are not visible on the home page

They have to be marked as partner specific I think.
On Fri, Jun 30, 2023, 7:38 PM Siouxxanne @.***> wrote:

Feature columns added in website cms are not visible on the home page
—
Reply to this email directly, view it on GitHub
https://github.com/Comics-Games-and-Things-LLC/openCGaT/issues/9, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2LKZBA2HGHVOGQICNYJLDXN5WQDANCNFSM6AAAAAAZ2ODDRE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

That worked. Go ahead and close this issue if you don't want to change that


Jenkins: Do the VM cleanup in sequential mode

From the day that we setup the parallel in checkout [0] we started to seen
the following error:
Using context: Cilium-Ginkgo-Tests
an exception which occurred:
	in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals
	in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@195b5c5
	in field com.cloudbees.groovy.cps.impl.CallEnv.caller
	in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@2dc285bc
	in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent

The parallel shouldn't be related at all, but cleanup takes <2secs, so
add it on the sequential mode to validate that it's not a parallel
issue and be able to debug all the workflow in a simple way.
[0] Commit fbf3fa21615dcf4b5b5e9078ac5e8ec4c84e7da5#diff-fb0829c8c95bc1e5695b0cb02699d295
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

test-me-please

test-me-please


chore(net): improve ecies error for unreadable stream

Closes #511
the Framed stream will return None:
https://github.com/tokio-rs/tokio/blob/3886a3eaf4f513cc3522597a6fdd990e4f68b922/tokio-util/src/codec/framed_impl.rs#L173-L197
if the stream is no longer readable.

Codecov Report

Merging #514 (ea78b40) into main (e713b0c) will decrease coverage by 0.04%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #514      +/-   ##
==========================================
- Coverage   73.44%   73.40%   -0.05%
==========================================
  Files         241      241
  Lines       24716    24717       +1
==========================================
- Hits        18153    18143      -10
- Misses       6563     6574      +11

Impacted Files
Coverage Δ

crates/net/ecies/src/error.rs
0.00% <ø> (ø)

crates/net/ecies/src/stream.rs
69.84% <0.00%> (-1.13%)
:arrow_down:

crates/net/network/src/session/active.rs
83.47% <100.00%> (ø)

crates/net/eth-wire/src/p2pstream.rs
82.18% <0.00%> (-2.01%)
:arrow_down:

crates/net/eth-wire/src/pinger.rs
91.52% <0.00%> (-1.70%)
:arrow_down:

crates/net/discv4/src/lib.rs
55.79% <0.00%> (-0.10%)
:arrow_down:

crates/net/eth-wire/src/capability.rs
61.79% <0.00%> (+1.12%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix bug found on tests for cat command in openvariant

When running the github action for the testing, turns out that 9 out of 12 of the tests performed on the command cat fail.
https://github.com/bbglab/openvariant/runs/7150358275?check_suite_focus=true

Solved:
We realized that listdir function, which is located in find_files.py file, generates a random list of directories and files of a path. Every test that we executed it was different so it failed because the results were different.
We have sorted it before to explore the directories and files that it throw:
list_files = listdir(base_path)
list_files.sort()


Added ISFT N 197 - IT Beltran

Official website URL:  https://www.ibeltran.com.ar/index.php

URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university: https://www.ibeltran.com.ar/analista_sistemas.php

@medinalautaro354 First stage of verification passed, official domain is ibeltran.com.ar as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://alumnos.ibeltran.com.ar/


Ability to collapse/minimize DHCP addresses in IP address view

Would like to see a way to collapse, hide, or minimize the IP's which are listed as DHCP for a prefix.  While it's important to track our DHCP scope(s), it's much less important to list all of them when 99% of the time we're working on entries for those outside of DHCP.

#834 would introduce IP ranges, replacing a consecutive set of discrete IPs with a single range object. But in the interim, it would make sense to include a simple filter panel to allow hiding IPs by status/role.

This would be a very handy feature!

Is there any word on when this change will be implemented? We have just started using NetBox in our environment and adding a DHCP range for a large number of IP addresses is messy when you need to scroll through multiple pages considering not all IP addresses are always in use.

Not sure why this issue is still open. We already have status and role filters for IP addresses. You can hide DHCP IPs by selecting only the other three statuses in the list.

Hi Jeremy,
Can you please be more specific regarding the ability to hide DHCP IPs?
The only option I can see is to sort by status.
Is the option to condense DHCP ranges such as in phpIPAM still in development and do you know if there is an ETA on this yet?
Thanks again for your help with this, it is much appreciated!

Would it be possible to hide all of the dhcp addresses when you look at the prefix's without having to filter them out each time, it is very tedious and messy atm. Or make it possible to condense all dhcp addresses into one object so you dont have to scroll through multiple pages. Thanks


First PR for WholeGraph 23.06 refactor and add RAPIDS CI scripts

Refactor for WholeGraph, some updates:

More WholeMemory types.
WholeMemory Embedding.
WholeMemory Embedding Cache support.
WholeMemory Embedding Sparse Optimizer.
DLPack export for WholeMemory.
Torch C10 API removed.
Packaging for conda.
RAPIDS CI scripts.

@dongxuy04 you need to add a conda environment yml file under  "conda/environments"

@dongxuy04 you need to add a conda environment yml file under "conda/environments"

@BradReesWork added conda environment yml files generated by rapids-dependency-file-generator.

Does WholeGraph provide C-API? or C++-API? Most public headers under the cpp/include directory has either .h or .cuh extensions and should I assume this is to support C users?

Does WholeGraph provide C-API? or C++-API? All the public headers under the cpp/include directory has either .h or .cuh extensions and should I assume this is to support C users?

Yes, for host API part, .h files provide C-API instead of C++-API, the initial consideration is not to introduce ABI issues. For device headers, .cuh aims to provide developing interface on WholeMemory, so it expose C++ device API to access WholeMemory.

@dongxuy04 can you rename build_components.sh to just build.sh to match other repos?

@dongxuy04 can you rename build_components.sh to just build.sh to match other repos?

@BradReesWork I have renamed build_components.sh to build.sh, and updated scripts called this script.

@BradReesWork this PR has ~50K touched lines, is there something in particular you want me to review?

For every file and kernel under cpp/src/graph_ops, can we get a description of:

what is the goal? what model this operation would be used for?
was cugraph-ops considered? if yes, why was it not possible to use cugraph-ops/what is missing from cugraph-ops?

tagging @BradReesWork since you asked for scope of duplication of operations and @dongxuy04 for visibility for the above comment

I understand that this PR only focuses on refactor of WG into a more RAPIDS-like workflow. But I too still want to mention the cugraph-ops integration into WG and urge to put this on our immediate list of things todo for WG.
I agree with both Max's/Matthias' requests. cugraphops should already provide all (if not most) of those operations. So, it's not worth the duplication. I have filed issue #17 for this.

For every file and kernel under cpp/src/graph_ops, can we get a description of:

what is the goal? what model this operation would be used for?
was cugraph-ops considered? if yes, why was it not possible to use cugraph-ops/what is missing from cugraph-ops?

These files are legacy implementations left over from previous versions of WholeGraph code. Agreed  that we need to remove these duplication and actually this is in processing. The goal might be to get most of these files replaced by cuGraph ops.
Here are the goal of the files under cpp/src/graph_ops.

append_unique*: AppendUnique op, it is an optimizing OP for ids between sampling of two layers. The action is append sampled neighbor nodes to center nodes, and the do unique while keep center nodes unchanged. May need to keep as it is not related to cuGraphOps.
csr_add_self_loop*: add self loop to sampled csr sub graph. Not sure if there is this kind of ops. If yes, we may remove that.
edge_weight_softmax*, gspmm_csr_weighted*, spadd_gat_csr*: ops related to GAT model, currently GAT module from cuGraphOps is integrating, will be removed after confirmed.
spmm_csr_no_weight*: Ops related to GraphSAGE op and GCN op, currently GraphSAGE module from cuGraphOps is integrated, will be removed later.

@MatthiasKohl @stadlmax @teju85 @BradReesWork Agreed that it doesn't worth duplication. I have verified that similar ops in cuGraphOps works and removed the duplicated ops under cpp/src/graph_ops.

the "cmake" folder should be under the cpp directory

the top level folder for python code should be called "python" and then all the moudules under that

the "cmake" folder should be under the cpp directory


debug.log CreateFile: The system cannot find the file specified

Issue Type: Bug
When several VSCode Insiders is opened
And the projects are with React.js
Then Creates debug.log in each folder where .jsx file is opened.
content of the debug.log:
[0105/011038.242:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011059.935:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011126.411:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011151.756:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011239.872:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011302.338:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011322.337:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011401.478:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
[0105/011440.340:ERROR:registration_protocol_win.cc(102)] CreateFile: The system cannot find the file specified. (0x2)
Extension version: 2.1.14
VS Code version: Code - Insiders 1.53.0-insider (98106c48a07d4d07f0f71b4db9b3ff156f223339, 2021-01-01T05:22:15.141Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (2.01GB free)

Process Argv
--crash-reporter-id f21b2d82-b794-4f79-ba69-28b549a30887

Screen Reader
no

VM
0%

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
openlogontheside:30221882
python763:30178808
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
python504:30227505
vswsl492cf:30208930
wsl2prompt:30219162
vstry914:30230485
pythonvsdeb440:30224570
unusedprompt:30219164
folderexplorer:30219166
openfilemenucf:30219169
pythonvsded773:30223139
core-portspanel:30233467

@Tsenzuk can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

@Tsenzuk can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

I am also seeing this issue.  ESlint from cli reports multiple errors in a file, but vscode doesn't show any of them.

I am also seeing this issue.  ESlint from cli reports multiple errors in a file, but vscode doesn't show any of them.

@robross0606 any steps you can share best via a GitHub repository I can clone

@robross0606 any steps you can share best via a GitHub repository I can clone

I have this also, And i figured out it is this repo with a bisect. What I have right now is the svelte next setup
npm init svelte@next
I did an npm install, and a npm run dev -- --open
I just click in the vscode explorer on any file / folder, and at some point it appears. The debug log can appear in the root folder, or any other.
In general I suspect that this is nothing that you can reproduce with a specific repo. My guess would be that this specific to our PCs. But you can try and tell me if it happens for you.

I have this also, And i figured out it is this repo with a bisect. What I have right now is the svelte next setup
npm init svelte@next
I did an npm install, and a npm run dev -- --open
I just click in the vscode explorer on any file / folder, and at some point it appears. The debug log can appear in the root folder, or any other.
In general I suspect that this is nothing that you can reproduce with a specific repo. My guess would be that this specific to our PCs. But you can try and tell me if it happens for you.

@Aron4u thanks for the investigation.

@Aron4u thanks for the investigation.

Damn, I somehow typed something that I did not mean. I meant, that I figured out that its this extension, by doing a bisect.
Sorry for the confusion.
@dbaeumer Are you able to reproduce this with the svelte next repo?
otherwise, I could try to get some extra logging for you, if you tell me what you need and how to get it :)

Damn, I somehow typed something that I did not mean. I meant, that I figured out that its this extension, by doing a bisect.
Sorry for the confusion.
@dbaeumer Are you able to reproduce this with the svelte next repo?
otherwise, I could try to get some extra logging for you, if you tell me what you need and how to get it :)

From my experience something like this depends on a lot of things including eslint and plugin versions. That is why I usually ask for a repro to ensure that we are looking at the same setup.

From my experience something like this depends on a lot of things including eslint and plugin versions. That is why I usually ask for a repro to ensure that we are looking at the same setup.

@dbaeumer We are in the process of switching from TSLint to ESLint in a relatively big codebase, and I have the same issue, but only in one specific package. When I run the CLI, it displays correctly the different warnings and errors, but the ESLint plugin doesn't show anything, and autoFix on save isn't working either.
Usually I run the CLI from the root of the project, which has all the plugins required. The first time I tried to set up ESLint, I added an .eslintrc.js in the folder of the project, but I got the following error:

At that time, to fix the issue, I used that flag: yarn run eslint --resolve-plugins-relative-to ., that fixed my issue, but not the visual cues. I tried to remove the package react-scripts (which also removed the plugin) and then everything started working fine.
So yeah, looks like a version mismatch, my version of react-scripts is pretty old (2.1.8) and my guess is that VSCode tries to use the plugin from the current active directory, and not from the location of my eslint.js file (which I would expect)

@allardy a GitHub repository I can clone with steps to reproduce is always welcome. Please keep in mind that ESLint is very sensitive to the current working directory when resolving things. So the eslint.workingDirectories setting might be your friend here.

@dbaeumer Clone this branch: https://github.com/botpress/botpress/tree/ya-mig-eslint
Then remove the config eslint.nodePath from .vscode/settings.json, then reload the window.
If you open the file src/bp/ui-admin/src/api.tsx and change the order of the imports (or type any code that should be fixed by eslint), nothing will be highlighted and if you save, it doesn't fix it. But if you add the config eslint.nodePath again, it will work correctly.
In the same folder src/bp, you can also try it in ui-studio, this package is not affected at all by that change.
Since we have only a single .eslintrcjs, shouldn't we expect that any invocation will use the libraries in the node_modules closest to the rc file ? I think the worst thing is that the error is completely silent and doesn't give a clue of what's happening, like if there's a version mismatch somewhere

I was about to post the below then as i was getting my version of vscode insiders I noticed there was a update avaible, on the latest version i am unable to reproduce the issue.
Version: 1.54.0-insider (system setup)
Commit: 40b3204d70a9c72305c613164272175d0b344b5f
Date: 2021-02-10T17:39:27.208Z
Electron: 11.2.3
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

I have been encountering the same issue that Tsenzuk mentioned.
So far I found that opening up a vscode project that has been saved as a workspace or from the recents list causes the issue.
Quick steps to reproduce, im using nestjs to quickly demo it

nest n p1 (answer prompts)
nest n p2 (answer prompts)
In a new window of vscode open p1
In a new window of vscode open p2
observe that opening any ts files works as one would expect
close all vscode windows
from "recent folders & workspaces" open p1, opening any ts files works as expected
from "recent folders & workspaces" open p2 while p1 remains open in another window, opening a ts file creates a debug.log

I also created 2 repos to demo this.
p1
p2

@allardy works for me without any problems. See

@SamuelColacchia works for me. No debug.log in any of the folders where I opened the TS file from


bloaty: 1.1 -> unstable-2023-11-06

Description of changes
Update of bloaty to a recent commit. No updated tag since 2020 (see https://github.com/google/bloaty/issues/334). On aarch64-darwin the build failed today with the following error:
[...]
[ 27%] Building C object third_party/capstone/CMakeFiles/capstone-static.dir/arch/X86/X86Module.c.o
In file included from /tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googlemock/src/gmock-all.cc:39:
In file included from /tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googlemock/include/gmock/gmock.h:59:
/tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googlemock/include/gmock/gmock-actions.h:454:3: error: definition of implicit copy constructor for 'PolymorphicAction<testing::internal::ReturnNullAction>' is deprecated because it has a user-declared copy >
  GTEST_DISALLOW_ASSIGN_(PolymorphicAction);
  ^
/tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googletest/include/gtest/internal/gtest-port.h:679:8: note: expanded from macro 'GTEST_DISALLOW_ASSIGN_'
  void operator=(type const &) = delete
       ^
/tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googlemock/include/gmock/gmock-actions.h:1010:10: note: in implicit copy constructor for 'testing::PolymorphicAction<testing::internal::ReturnNullAction>' first required here
  return MakePolymorphicAction(internal::ReturnNullAction());
         ^
/tmp/nix-build-bloaty-1.1.drv-0/source/third_party/googletest/googlemock/include/gmock/gmock-actions.h:454:3: error: definition of implicit copy constructor for 'PolymorphicAction<testing::internal::ReturnVoidAction>' is deprecated because it has a user-declared copy >
  GTEST_DISALLOW_ASSIGN_(PolymorphicAction);
 [...]

Full build log
An update to a recent commit fixed the build issue
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1276


java: Update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

gradle (source)

minor
8.10.2 -> 8.11

org.projectlombok:lombok (source)
dependencies
patch
1.18.34 -> 1.18.36

:warning: Warning
Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

gradle/gradle (gradle)
v8.11: 8.11
Compare Source
The Gradle team is excited to announce Gradle 8.11.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
alyssoncs,
Bilel MEDIMEGH,
Björn Kautler,
Chuck Thomas,
Daniel Lacasse,
Finn Petersen,
JK,
Jérémie Bresson,
luozexuan,
Mahdi Hosseinzadeh,
Markus Gaisbauer,
Matthew Haughton,
Matthew Von-Maszewski,
ploober,
Siarhei,
Titus James,
vrp0211
Upgrade instructions
Switch your build to use Gradle 8.11 by updating your wrapper:
./gradlew wrapper --gradle-version=8.11

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.


Linking.getInitialURL() returns null on Android and restarts app

I'm working on integrating CIO with Android, and I'm not seeing any additional configurations required to get deep linking support. The docs only require to set up deep link navigation using @react-navigation/native. I've done that, but I have two issues:

The app restarts, even with config.pushClickBehaviorAndroid = PushClickBehaviorAndroid.ActivityPreventRestart;
When the app restarts and triggers the NavigationContainer linking prop, the value for Linking.getInitialURL() is null

Is it necessary to make any updates to the AndroidManifest.xml, when using the customerio-expo-plugin?

Hi @miguelespinoza. Sorry for any inconvenience caused by the behavior you mentioned. There could be multiple factors linked to this behavior, so I'm trying to narrow it down by asking a few questions to help you better.

Can you confirm version of React Native and Expo SDKs you are using so we can ensure we are debugging the same code?
Can you confirm if you are using Bare or Managed workflow?
Do you have multiple push providers added to your SDK (e.g. rnfirebase, expo-notifications)? If yes, are you handling push notifications by using one of the options mentioned in React Native docs?
Are you using Simple Push (only title and body), Rich Push (title, body, and image/link, or one of image or link), or Custom Payload?
The behavior you are currently seeing is:

Notification displayed when app is in foreground
Tapping on notification restarts app despite setting PushClickBehaviorAndroid.ActivityPreventRestart
All your components are recreated in React App and NavigationContainer receives an empty link in linking prop

Any other information or customization you made that you think might be helpful, please share with us

For your question:

Is it necessary to make any updates to the AndroidManifest.xml, when using the customerio-expo-plugin?

Only if you are using multiple push providers and want our SDK to handle all your notifications. However, this may prevent other push providers from triggering some callbacks. If you want to continue using callbacks from other SDKs, you can implement option 1 as suggested in our React Native SDK docs.
Please feel free to ask any more questions you have. Appreciate your cooperation while we debug this together. Have a great day!

Hey @mrehan27, thanks for the reply!

SDK versions:

Didn't see any major changes between 3.8.0 and 3.4.0, so didn't upgrade
fwiw, I have iOS working with deep linking

"customerio-expo-plugin": "1.0.0-beta.15",
"customerio-reactnative": "3.4.0",
"expo": "50.0.8",
"react-native": "0.73.4",

Expo managed workflow
I do have multiple push providers, "expo-notifications": "0.27.6" to be exact. But I was under the impression the CIO SDK worked in tangent. I kept expo-notifications on iOS because it had support for provisional notification permissions. That's the only reason we use expo-notifications. Would there be conflicts on Android having expo-notifications? I recall seeing a change that allowed expo-notifications along with customerio-react-native.
I'm using custom_payload, this always gets me, not sure where to put the payload metadata. This is what I have right now (using rails)

{
      transactional_message_id: message_id,
      identifiers: {
        id: recipient.id
      },
      link: message_data[:link],
      message_data:,
      custom_payload: {
        ios: {...},
        android: {
          message: {
            notification: {
              title: message_data[:title],
              body: message_data[:body],
              image: message_data[:image],
            },
            data: {
              title: message_data[:title],
              body: message_data[:body],
              link: message_data[:link],
              image: message_data[:image]
            },
          }
        }
      }
    }

The behavior you are currently seeing is: ... That's all correct. If it helps, this is what my linking prop looks like

export const createNavigationLinkingConfig = ({
  ....
}): LinkingOptions<NavigationParams> => {
  return {
    prefixes: [
      Linking.createURL("/"),
      "app://",
      "https://app.is/",
    ],
    config: {
      screens: {
        ...
      },
    },
    async getInitialURL() {
      const initialUrl = await Linking.getInitialURL();
      // 🚨 This is where I expect initialUrl to exist for Android, this works on iOS
      if (initialUrl) {
        // use initialUrl to build the link
      }

      const branchParams = await getBranchParams();
      if (branchParams && Object.keys(branchParams).length > 0) {
        // use branchParams to build the link
      }
    },
    subscribe(listener) {
      const linkingSubscription = Linking.addEventListener(
        "url",
        async ({ url }) => {
          // use url to build the link
        },
      );

      const branchUnsubscribe = branch.subscribe({
        onOpenComplete: async ({ error, params, uri }) => {
          if (params?.["+clicked_branch_link"]) {
            // use params to build the link
          }
        },
      });

      return () => {
        linkingSubscription.remove();
        branchUnsubscribe();
      };
    },
  };
};

Thanks for the great details @miguelespinoza. Much appreciated.
Thanks for sharing SDK versions. We recommend keeping SDK version up-to-date for better experience and improved performance. There isn't any fix linked to this recently so no rush on this, but updating to latest version as soon as possible is still recommended and much appreciated. I was mainly asking to make sure we rule out any potential code differences and ensure we are looking at the same version of code that your app is using.
If you are using expo-notifications, it could possibly be conflicting and preventing our SDK from handling notifications. Unfortunately, push notifications come with some restrictions and have different behavior across iOS and Android, due to which compatibility may differ. We are constantly working on minimizing those challenges, making the behavior consistent, and keeping our docs up-to-date for better developer experience and will continue working on improving this.
Since you mentioned you only needed expo-notifications for iOS mainly, can you try going with Option 2 mentioned in React Native docs? This will prevent any callbacks for Android from expo-notifications but should solve any other challenges you are facing while sending notifications from Customer.io. Since you mentioned you are on managed workflow, our expo plugin does allow implementing option 2 by just enabling android.setHighPriorityPushHandler config option as follows:
"android": {
  "setHighPriorityPushHandler": true
}

For the payload you shared, sorry I haven't caught up much recently with how exactly the Rails code accepts the payload, but overall this looks fine and should work for you. In case you are wondering what final payload sent from our editor is, you can always find it out by following these steps:

Go to Push Editor on Fly
Compose a push with desired fields using our Rich Push Editor
Click on "Preview payload" button at top of Preview Window on the right and it should reflect final JSON we expect (You can select your desired platform iOS or Android to see their respective JSONs)

This should help you get initialUrl correctly. Do let me know if you still face the issue, so I can suggest next steps to narrow this down further.
Once again, appreciate your cooperation. Please feel free to post any questions you have so we can continue to help you better!

Hey @miguelespinoza. From the details so far, this looks like expected behavior, so I'll go ahead and close this issue. If the above responses don't help or if you have more questions, please feel free to reach out and ask. Have a great day!


How can we stop it from updating the appVersion in the charts.yaml

Any idea??

So the request is for the app version to but be versioned with the chart? If so I can add a flag.

Yeah! we keep out helm charts separate from code base. Chart Version and App Version being same is good only when they are published for same branch or tag. It would be good to have toggle/flag to choose  whether app version in Chart.yaml should get updated or not

When not updating the appVersion I'm guessing you also don't need to update values.yaml's image.tag value.  Is that correct?

@Galileo1 checkout the PR and let me know if that accomplishes what you wanted.

true!! we don't want to update the image tag aswell.  sounds good to me.


[New chain]: Morph Mainnet 1.4.1

Summary
I would like to add the 1.4.1 contract addresses for the Morph Mainnet
Chain ID
2818
Chain detail URL
https://chainlist.org/chain/2818
RPC URL
https://rpc.morphl2.io
Blockscout Client URL
No response
Etherscan Client URL
No response
Etherscan Client API URL
No response
Version
1.4.1
Address (Master copy)
0x41675C099F32341bf84BFc5382aF534df5C7461a
Deployment Tx hash (Master copy)
0xc3fe1e2b066f3705a503984bb153d0238c1354c96856b2055d51e748602885ff
Block explorer URL (Master copy)
https://explorer.morphl2.io/address/0x41675C099F32341bf84BFc5382aF534df5C7461a
Address (Master copy L2)
0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Deployment Tx hash (Master copy L2)
0x5bdcf717f92a1b2e3649f8cec22b5c9f9e3880e56d9bd01fbb6c2911ecca5503
Block explorer URL (Master copy L2)
https://explorer.morphl2.io/address/0x29fcB43b46531BcA003ddC8FCB67FFE91900C762
Address (Proxy factory)
0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67
Deployment Tx hash (Proxy factory)
0x5b8a324e79dae83f1cb2f68025d9b7d15f33285197bc1d65460eb01c9e3d8767
Block explorer URL (Proxy factory)
https://explorer.morphl2.io/address/0x4e1DCf7AD4e460CfD30791CCC4F9c8a4f820ec67

/execute


creating a style property for the TextButton wrapper

Great resource.
I want to suggest you create a property that can enable us customize the TextButton style of the widget

I used a container


Storage::check should return a reference

While the original idea was that you could iterate over certain entities while still being able to borrow a storage inside, it's also useful to just get a bitset with the contained components. Thus, I'd suggest we return a reference and make cloning explicit.

Maybe we should just change it to mask or something?

Well you can also just do
for (pos, vel, _) in (&pos, &vel, (&bitset, &other_filter, &other_component)).join() {
    println!("Pos: {:?}", pos);
}

mask is a better name, yes. Let's deprecate check and add mask.


Bundle validation fails with CRD not found

Type of question

Question
What did you do?
operator-sdk bundle validate ./deploy/bundle --verbose

What did you expect to see?
Bundle is valid.

What did you see instead? Under which circumstances?
Error that says some of the owned CRDs are not found, even though it is included in the bundle.
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephCluster: owned CRD "ceph.rook.io/v1, Kind=CephCluster" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephBlockPool: owned CRD "ceph.rook.io/v1, Kind=CephBlockPool" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephObjectStore: owned CRD "ceph.rook.io/v1, Kind=CephObjectStore" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephObjectStoreUser: owned CRD "ceph.rook.io/v1, Kind=CephObjectStoreUser" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephNFS: owned CRD "ceph.rook.io/v1, Kind=CephNFS" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephClient: owned CRD "ceph.rook.io/v1, Kind=CephClient" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephFilesystem: owned CRD "ceph.rook.io/v1, Kind=CephFilesystem" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephRBDMirror: owned CRD "ceph.rook.io/v1, Kind=CephRBDMirror" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephObjectRealm: owned CRD "ceph.rook.io/v1, Kind=CephObjectRealm" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephObjectZoneGroup: owned CRD "ceph.rook.io/v1, Kind=CephObjectZoneGroup" not found in bundle "ocs-operator.v4.8.0"
ERRO[0000] Error: Value ceph.rook.io/v1, Kind=CephObjectZone: owned CRD "ceph.rook.io/v1, Kind=CephObjectZone" not found in bundle "ocs-operator.v4.8.0"

Environment
Operator type:

/language go

Kubernetes cluster type:
OpenShift

$ operator-sdk version
operator-sdk version: "v1.2.0", commit: "215fc50b2d4acc7d92b36828f42d7d1ae212015c", kubernetes version: "v1.18.8", go version: "go1.15.3", GOOS: "linux", GOARCH: "amd64"

$ go version (if language is Go)
go version go1.15.2 linux/amd64

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"ffd68360997854d442e2ad2f40b099f5198b6471", GitTreeState:"clean", BuildDate:"2020-11-13T23:53:02Z", GoVersion:"go1.15.0", Compiler:"gc", Platform:"linux/amd64"}

Additional context
https://github.com/openshift/ocs-operator/tree/master/deploy/bundle is the bundle generated by sdk that I am trying to validate.

/cc @camilamacedo86

/cc @camilamacedo86

Could you share the bundle.Dockerfile content please?

Could you share the bundle.Dockerfile content please?

Could you share the bundle.Dockerfile content please?

https://github.com/openshift/ocs-operator/blob/master/deploy/Dockerfile

Could you share the bundle.Dockerfile content please?

https://github.com/openshift/ocs-operator/blob/master/deploy/Dockerfile

HI @umangachapagain,
Following some questions

What the motivations for these changes in the default layout? Because if you move the things you need to customize the commands and makefile and etc .. to make all still working and you will face problems to upgrade the project for further versions. So, why these changes are required at all? What problems are you trying to solve it?

How are you generating the bundle?

HI @umangachapagain,
Following some questions

What the motivations for these changes in the default layout? Because if you move the things you need to customize the commands and makefile and etc .. to make all still working and you will face problems to upgrade the project for further versions. So, why these changes are required at all? What problems are you trying to solve it?

How are you generating the bundle?

@camilamacedo86 will open an issue for this in the api repo, since this issue is caused by duplicate CSV values not generating warnings.

@camilamacedo86 will open an issue for this in the api repo, since this issue is caused by duplicate CSV values not generating warnings.

Done: https://github.com/operator-framework/api/issues/93

Done: https://github.com/operator-framework/api/issues/93


rtx implode

To make it a bit easier to uninstall, we could have an “implode” command that deletes the rtx binary, installs, plug-ins, and cache

It would be cool to have the ability to clean up everything except the binary (like a clean install), especially for those that install rtx via package manager.
Also instead of implode, destroy might be a better name.


Configure the language(s) in the pre-commit hook

Is your feature request related to a problem? Please describe.
Topiary is expected to be multi language, and the number of supported languages will surely grow. In that situation, it can happen that you want to use Topiary e.g. only for one or a restricted number of languages but use other formatters for other languages. Typically, topiary is the only formatter able to handle Nickel right now, but I don't want it to try to format the bash scripts of the Nickel repo.
Describe the solution you'd like
Make the exported pre-commit-hook a function that take as an input the language to enable, or to exclude. In the long term, it could be even nicer to have a module-like approach (which I believe is the case for built-in pre-commit-hooks), but as long as it's parametrizable, it would already be awesome.
Additional context
I can take a stab at implementing this change, but I won't have the bandwith in the coming weeks, I fear.

pre-commit-hooks already allow you to customise its hooks, so I believe what you're asking for is already doable. For instance, with the official hooks, instead of
topiary.enable = true;

you can do
topiary = {
  enable = true;
  files = "(\\.sh$)|(\\.mli$)";
};

which overrides the default pre-commit's behaviour so that it only runs on .sh and .mli files. If you are using the pre-commit hook from our flake, this would be
topiary = topiary.lib.${system}.pre-commit-hook // { files = ... };

What do you think of this solution? I can see how that maybe does not fully solve your problem, so I would be interested in hearing what shortcomings you see to this!

I tried and it fits the bill for my simple use-case, thanks. For the record, if you want to use the latest topiary from Topiary's flake, you should rename the entry inside pre-commit-hooks (I used topiary-latest, but whatever works), otherwise Nix complains about one option having conflicting declarations, because topiary is already defined by pre-commit-hooks.
@Niols I let you decide if this issue should stay open or not, if you think a better solution is mandated, but as far as I'm concerned, my problem is solved.

I would like to say that Topiary currently also reads the languages.toml file present in .topiary/languages.toml in the current directory or any above it.

I think this is the right answer, actually, and this is what you should do, @yannham. That way, you can ensure that Topiary as run by contributors and Topiary as run by pre-commit hooks use the exact same configuration. If there was a way to define which languages to support positively (instead of disabling extensions of languages), then that would entirely solve your issue in a clean way, I think.

So, IIUC, I should revert my change and just use the plain hook from pre-commit-hook, and add a file .topiary/languages.toml. But I'm not sure to understand the latter format: does the example given by @ErinvanderVeen enables only bash, or disables only bash? If it's a blacklist process, it's not very maintainable, as I need to keep up to date with supported languages and disable them all but Nickel.

So, IIUC, I should revert my change and just use the plain hook from pre-commit-hook, and add a file .topiary/languages.toml.

I think that would be the best option.

But I'm not sure to understand the latter format: does the example given by @ErinvanderVeen enable only bash, or disable only bash? If it's a blacklist process, it's not very maintainable, as I need to keep up to date with supported languages and disable them all but Nickel.

It is also something that I wonder now that I am looking at how configuration works. I feel configuration files do not replace the default configuration but only add to it (potentially nullifying some values in it), and I don't like that so much either.

Hej! Definitely not, and we need to implement a better way to override the configuration file. This was only meant as a possible workaround, and definitely not meant to be sustainable.
I'm working on #564 right now, whatever comes out of that should be the right approach for you.

(draft) PR is open here: https://github.com/tweag/topiary/pull/567


feat: cube support

feat: cube support

Closes https://github.com/jayy-lmao/sql-gen/issues/9 by adding postgres cubes.
Note when using this you will need sqlx >= 0.8, but wont be a dep unless your db has cubes in it.

Wont merge until after https://github.com/jayy-lmao/sql-gen/pull/13, as https://github.com/jayy-lmao/sql-gen/issues/9 will also need enum support anyways 👍


keep doesn't work as an after hook for get

I've been using version 4 forever and tried updating to version 5.
In version 5, the keep hook seems to remove all fields when used as an "after" hook of a get service, regardless of the parameters. Downgrading to 4.14.1 seems to work fine.
Example usage:
const hooks = require('feathers-hooks-common')

// setup code deleted

app.service('/siteinfo').hooks({
    before: {
        find: hooks.disallow(),
        create: hooks.disallow(),
        update: hooks.disallow(),
        remove: hooks.disallow()
    },
    after: {
        get: hooks.keep(
            'name',
            'contact',
            'siteUrl'
        )
    }
})

Removing the keep hook returns the full record as expected.
I'm wondering if there has been an undocumented API change regarding keep, or am I just using it wrong?
Thanks!

It should be backwards compatible so something worth looking at. I'm just wondering why the tests are passing with the prerelease in https://github.com/feathersjs-ecosystem/feathers-hooks-common/pull/623 can you reproduce this in a simple app?

With a simple app, no. It works with a basic service, such as:
const feathers = require('@feathersjs/feathers')
const hooks = require('feathers-hooks-common')

const app = feathers()

app.use('/test', {
    async get(id) {
        return {
            id,
            public: 'public data',
            private: 'private data'
        }
    }
})

app.service('/test').hooks({
    before: {
        find: hooks.disallow(),
        create: hooks.disallow(),
        update: hooks.disallow(),
        remove: hooks.disallow()
    },
    after: {
        get: hooks.keep(
            'public'
        )
    }
})

app.service('/test').get(1).then((result) => {
    console.log(result)
})

I should have added that my service is created from feathers-mongoose (8.3.3), set up as:
app.use('/siteinfo', service({ Model: organization, id: 'code', lean: false }))

where organization is a mongoose model, and code is a unique index on the collection. So that's harder to set up as a "simple" application without a mongodb backend, and a more complicated use case to diagnose.

I'm not sure how this worked for you before, but if you are setting lean: false you will get Mongoose models which not be modified by common hooks unless you convert them with toJSON first (see the Important section at https://github.com/feathersjs-ecosystem/feathers-mongoose#serviceoptions).

Because I have business rules in the backend hooks, I've found it handy to get Mongoose models back from service calls in hooks of other services. I should probably be using Mongoose to make direct DB queries instead of using service calls for that.
I've actually never had any issue with any hook removing fields (like passwords etc.) to this point from the full model.  This particular service never needs to return a model, so problem solved there. Returning an empty object sure does seem like an odd result, though.


not compiling

I think it needs an update to the latest version of literal text? the old doesn't compile.
cargo run
Compiling literalext v0.1.1
error[E0554]: #![feature] may not be used on the stable release channel
--> /Users/doctorstrange/.cargo/registry/src/github.com-1ecc6299db9ec823/literalext-0.1.1/src/lib.rs:19:37
|
19 | #![cfg_attr(feature = "proc-macro", feature(proc_macro))]
|                                     ^^^^^^^^^^^^^^^^^^^^
error: aborting due to previous error
error: Could not compile literalext.
To learn more, run the command again with --verbose.

It looks like you're using the stable version of the compiler? Maud only supports the Nightly version of Rust, so you need to use that instead.
You're right that we need to upgrade literalext, but the old version should still work.


mecab-python3 errors.. popping up.

I don't know how to solve this.

You need to explicitly install unidic.
- python -m unidic download


Switched broken pypip.in badges to shields.io

Hello, this is an auto-generated Pull Request. (Feedback?)
Some time ago, pypip.in shut down. This broke the badges for a bunch of repositories, including django-extras. Thankfully, an equivalent service is run by shields.io. This pull request changes the badges to use shields.io instead.

Coverage remained the same at 75.816% when pulling 5683510db4b89069fc0809128aec4b864f51f501 on movermeyer:fix_badges into 3191b611604cac8890e8f57fbb6b2ce18034d93b on timsavage:master.

Coverage remained the same at 75.816% when pulling 5683510db4b89069fc0809128aec4b864f51f501 on movermeyer:fix_badges into 3191b611604cac8890e8f57fbb6b2ce18034d93b on timsavage:master.


Re-add dry run

Signed-off-by: Ashish Tiwari<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Is this only invoked on click of the Validate operation or in other situations, too?

This is invoked everytime a design/pattern is saved on canvas.

@Revolyssup oooh, ouch. Yes, we can't do that. Designs are saved with extremely high frequency. We can't have a dry run getting in the way of saves. It's time to breakout "dry run" from "validate". Will you propose an approach to this?

@Revolyssup Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

@Revolyssup can we invoke dry-run only before deploy,un-deploy and validate ??// @leecalcote

Yes?

Creating another PR


[Environment Variables] Functions/Tags inside nested block referring to another Environment Variable do not render variable value

Describe the bug
When using Environment Variables, functions/tags inside a nested block referring to another Environment Variable that is constructed from an environment variable do not use the calculated variable value; instead the literal string is used. This only seems to impact functions, as direct references to these variables seem to still work.
To Reproduce
Steps to reproduce the behavior:

Go to Base Environments
Use this environment config:

{
  "first_name": "Bobby",
  "last_name": "'; DROP TABLES;'",
  "full_name": "{{ _.first_name }} {{ _.last_name }}",
  "baseEncodedRoot": "{% base64 'encode', 'normal', _.full_name %}",
  "sub": {
    "baseEncodedSub": "{% base64 'encode', 'normal', _.full_name %}",
    "full_name": "{{_.full_name}}"
  }
}

Mouse over both _.baseEncodedRoot and _.sub.baseEncodedSub tags and notice that they are both listed as having the same value.
Click Done to exit the Manage Environments
Create a new request
Add two parameters:

base64EncodedRootName={{ _.baseEncodedRoot }}
base64EncodedSubName={{ _.sub.baseEncodedSub }}

Click to preview/execute request
Notice the values in the parameters are different
Notice if you decode the base64 values, the root value is the calculated value (i.e., Bobby '; DROP TABLES;'; CORRECT), whereas the sub value is the literal string of the referenced value (i.e., {{ _.first_name }} {{ _.last_name }}; INCORRECT)

Expected behavior
Usage of a tag/function that refers to another variable that is constructed from other variables should be the same whether it is on the root or nested in a block.
Screenshots

Desktop (please complete the following information):

OS: [e.g. macOS 10.15.1]
Installation Method: [homebrew, built from source]
App Version: Insomnia 2021.4.1
Release date: 7/6/2021
OS: Darwin x64 19.6.0
Electron: 9.3.5
Node: 12.14.1
V8: <IP_ADDRESS>-electron.0
Architecture: x64
node-libcurl: libcurl/7.73.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 zstd/1.4.9 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.42.0

Additional context
This was first discovered while using the Default Headers plugin to construct a header. After digging into things, I realized it wasn't an issue with the default headers plugin but has to do with the way the variables are being rendered outside the Manage Environments section.

Same thing happens if you try to do the function calculation in the root variable and refer to it in the nested object. For example:
{
  "first_name": "Bobby",
  "last_name": "'; DROP TABLES;'",
  "full_name": "{{ _.first_name }} {{ _.last_name }}",
  "baseEncodedRoot": "{% base64 'encode', 'normal', _.full_name %}",
  "sub": {
    "baseEncodedSub": "{{_.baseEncodedRoot}}"
  }
}

_.baseEncodedRoot is calculated correctly. However, _.sub.baseEncodedSub is not (it uses the literal {{ _.first_name }} {{ _.last_name }})

This also seems to only occur on the Base Environment; the variable is rendered correctly when a Sub Environment is selected.


Proposal: use ooth for user identity management

Hi there, I'm the developer of ooth, a modular user identity management system built on top of passport.js (which, famously, only handles the authentication part, but not the storage of user information part).
You have a nice starter here, but if people want to extend the login functionality with other strategies (e.g. facebook or google login) they are on their own. With ooth they could just plug in another strategy and move. What do you think?

Hey @nmaro, It would be nice actually. The only thing is I don't want to add more library because It will gonna too much for basic project. But I'm preparing plugin system for RAN so theoretically, you can create plugin when it's ready. Unfortunately, I still need time to finish it.

Sounds good, thanks


Attestation failure message emits secret

brew doctor output
Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
<EMAIL_ADDRESS>
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libMsgCom.dylib
  /usr/local/lib/libSysCtlCom.dylib
  /usr/local/lib/libwep_airdrop.dylib
  /usr/local/lib/libwep_burn.dylib
  /usr/local/lib/libwep_cbcarbon.dylib
  /usr/local/lib/libwep_cbcocoa.dylib
  /usr/local/lib/libwep_chrome.dylib
  /usr/local/lib/libwep_dutil.dylib
  /usr/local/lib/libwep_ff.dylib
  /usr/local/lib/libwep_icloud.dylib
  /usr/local/lib/libwep_mail.dylib
  /usr/local/lib/libwep_post.dylib
  /usr/local/lib/libwep_printer.dylib
  /usr/local/lib/libwep_screen.dylib

Warning: Found Ruby file outside tgt/brewhouse tap formula directory.
(/opt/homebrew/Library/Taps/tgt/homebrew-brewhouse/Formula):
  /opt/homebrew/Library/Taps/tgt/homebrew-brewhouse/ghe_download_strategy.rb

Found Ruby file outside go-vela/vela tap formula directory.
(/opt/homebrew/Library/Taps/go-vela/homebrew-vela/Formula):
  /opt/homebrew/Library/Taps/go-vela/homebrew-vela/template.rb

I've got this whittled down from a lot more stuff in here before I pushed submit<EMAIL_ADDRESS>is still used by several formulae:
$ brew uses --installed<EMAIL_ADDRESS>git-filter-repo      libcroco             liblqr               peru                 proselint            sox                  sshtrix              wemux

And the other things are particular to my enterprise environment.
Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 4.3.0-15-gf520383
ORIGIN: https://github.com/homebrew/brew.git
HEAD: f520383897b3c3e36cf6a08c82a0d27b5cef48ab
Last commit: 29 minutes ago
Core tap HEAD: 1e50fab716a8726ad47782cf1e6b6f8d4d621547
Core tap last commit: 51 minutes ago
Core tap JSON: 14 May 15:59 UTC
Core cask tap HEAD: 29b229ac878e6fa2e53028f9682d9f6dcc330d4b
Core cask tap last commit: 23 minutes ago
Core cask tap JSON: 14 May 15:59 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_BAT_THEME: DarkNeon
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: vim
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_MAKE_JOBS: 10
HOMEBREW_SORBET_RUNTIME: set
HOMEBREW_VERIFY_ATTESTATIONS: set
Homebrew Ruby: 3.1.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.1.4/bin/ruby
CPU: 10-core 64-bit arm_firestorm_icestorm
Clang: 15.0.0 build 1500
Git: 2.45.0 => /opt/homebrew/bin/git
Curl: 8.4.0 => /usr/bin/curl
macOS: 14.3.1-arm64
CLT: <IP_ADDRESS>.1.1708646388
Xcode: N/A
Rosetta 2: false

What were you trying to do (and why)?
brew upgrade while HOMEBREW_VERIFY_ATTESTATIONS=1 is set.
What happened (include all command output)?
==> Upgrading gh
  2.49.0 -> 2.49.2
==> Verifying attestation for gh
Error: The bottle for gh has an invalid build provenance attestation.

This may indicate that the bottle was not produced by the expected
tap, or was maliciously inserted into the expected tap's bottle
storage.

Additional context:

attestation verification failed: Failure while executing; `\{\"GH_TOKEN\"=\>\"LITERALLYMYGHTOKEN\"\} /opt/homebrew/bin/gh attestation verify /Users/Z003XC4/Library/Caches/Homebrew/downloads/1d47281ddb66d5bfb053e1f74cff84446c6626f87d7536b93b5c7dbc5555f073--gh--2.49.2.arm64_sonoma.bottle.tar.gz --repo trailofbits/homebrew-brew-verify --format json` exited with 127. Here's the output:

N.b., there was no further output.
What did you expect to happen?
I did not expect to see my token in the command output.
…I also expected the attestation to work but that's being handled in another forum.
Step-by-step reproduction instructions (by running brew commands)
`brew upgrade` while `HOMEBREW_VERIFY_ATTESTATIONS=1` is set.

Triaging: I think the right way to do this is to pass the token's value to ErrorDuringExecution for redaction, but this is likely to be difficult to plumb through Utils.safe_popen_read.
Instead, I think I need to fix ErrorDuringExecution's rendering of the cmd more generally -- it should render the Hash as an environment listing instead of just dumping it (if present), and should also apply an allowlist of variables that don't need to be redacted.


server helper: Change SSLError log level to warn in accept

Signed-off-by: Masahiro Nakagawa<EMAIL_ADDRESS>
Which issue(s) this PR fixes:
No issue
What this PR does / why we need it:
Follow on_readable and identify what is the cause.
With trace level, users hard to find ssl setting mistake.
Docs Changes:
No need.
Release Note:
Same as title.

Anyone found a solution?


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:36: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: Apache-2.0
ERROR: /tmp/abs_e9nxfedqa8/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:1: missing_python: For pypi packages, python should be present in the host and run sections. Missing in host
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:1: missing_python_build_tool: Python packages require a python build tool such as setuptools.
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:1: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:32: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:36: incorrect_license: The recipe's about/license key is not an SPDX compliant license or license exception, closest match: Apache-2.0
ERROR: /tmp/abs_32fmfsn2uf/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


[HIPIFY][perl][feature request] Specify output file as a cli parameter

Cheers,
Would be nice to have the possibility to specify the output file of the hipify-perlcommand.
This is useful In those cases I want to generate on-the-fly a translation without involving a shell or at least not involving pipe redirections.
An example is the execute_process()(*) CMake command.
Of course, for that case a workaround is to invoke the shell command /bin/sh -c "....".
Is it possible that I had missed the feature (perhaps CMake spefici too)? Or we cannot avoid to pass through a shell because of the environment?
Thanks in advance
(*) E.g. execute_process

Implemented by #298


0.1.0 Release

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/97273
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 6c0756609764900e0bc3aa6b0d25c0a4e7fadff0
git push origin v0.1.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/97273
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 393da84e3a5bdad5e902cd72e55b94d827840a45
git push origin v0.1.0


Consider Jellyfin support

Possible Jellyfin support was mentioned on Reddit. I'm opening this issue so support/progress can be tracked in the project's repo.

Began looking into this. Stumbled upon an (minor) issue.
As of right now, when deleting the music file from the server, it will persist in jellyfin until it is manually deleted. Same goes for Albums and Artists (issue in Jellyfin repo).
To avoid this and keep things clean, I think it would be beneficial to create a separate media library for Explo. This way, it wouldn't "pollute" the main music library with potentially messy metadata.
Development will be in the dev branch

Jellyfin support added in v0.6.0
A separate library will be created for Explo


Cancellation Reason always empty

API: /api/v1/rides/${rideId}/cancellation-reasons
Hi team, I'm working on getting the API cancellation reason with 'rideId' (API above) but it always returns empty. I have found a way to add these reasons on the control panel but I don't see it. Can you have a look at this and assist me in adding it?
This is a cURL :
curl --location 'https://client.staging.eu.autofleet.io/api/v1/rides/431bbbdc-a2c2-4ca2-80e4-e39e367be778/cancellation-reasons' \ --header 'x-loco-ds-id: {demandSourceId}' \ --header 'x-loco-op-id: {demandSourceId}' \ --header 'Authorization: Bearer token'

Hi @tonyuride, there were no cancelation reasons set up in the staging env, we added a few now. Can you please check again?


Update Code

There are some conflicts that are too complex for me to resolve, please try to make a new branch from the initial code and recommit your final code instead of having two commits, which might be the problem, try not to chance the name of the code or delete any lines, simply just add


Backport 2.1: Fix typo in asn1.h

Status
READY
This is a backport of https://github.com/ARMmbed/mbedtls/pull/1065 to mbed TLS 2.1

Reviewed, approved and merged.


influx client exits if it doesn't connect to a server when launching

Currently, if you invoke the influx cli and it can't connect to the default localhost:8086 the program exits.
It should show the warning, but not exit, as you may not have a server on that port.
$ influx
Failed to connect to http://localhost:8086
Please check your connection settings and ensure 'influxd' is running.

It's been like this for a while. Remember I fixed the bug where we were actually trying to connect?

When I fixed it, it exited, you reviewed the code. :-)

I actually think it should exit. Other CLIs do the same thing:
~ $ mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Ok, after thinking about this I'm fine with it.  You can easily pass -host and -port if you want to connect to a different server.


update(.github/FALCO_VERSIONS): unsupporting 0.37

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

Proposed rule maturity level

Uncomment one (or more) /area <> lines (only for PRs that add or modify rules):

/area maturity-stable

/area maturity-incubating

/area maturity-sandbox

/area maturity-deprecated

What this PR does / why we need it:
See https://github.com/falcosecurity/rules/pull/208
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


some maintenance and code readability

changed some res layouts for very slightly better performance
escaped apostrophes that were causing errors
java 1.8 compatibility (converted anonymous java expressions to lambdas and methods, etc)
make build.gradle files a bit more understandable
update kotlin to 1.3
update gradle to 4.10.2

Lol I need to remember to make my commit messages a little more verbose. I first group them by directory and module, and add them to different changelists named after said groupings. I then commit each changelist.

You can always revert the HTML changes if you don't like them :) (To avoid having extra commits, I think one can pull up to that commit, revert said undesired change, and then pull the remaining ones. Has to be done through git bash (or Android Studio if you prefer) though.)


Highlighting List Item Doesn't Change Label or Image Contrast

Closing this because Unity does not provide a clean way to edit the styles of the child element.