Fix create/edit colony metadata handler using wrong ids for motions

This PR is a fix for this issue: https://github.com/JoinColony/colonyCDapp/issues/1560
The pending colony metadata wasn't being stored when you created a motion because the auth proxy used the id of the pending colony metadata, which is not exactly the colonyAddress but ${colonyAddress}_motion-${motionTxHash} so I've added a regex to extract and use only the first address that it founds on the id.
I've tested this by skipping the auth container on dev env startup, running the auth locally, and then making some edit colony details actions and motions.
CDapp counterpart: https://github.com/JoinColony/colonyCDapp/pull/1774

@rdig @jakubcolony
The address is sent inside the editColonyMotion saga, in this block:
    /*
     * Save the pending colony metadata in the database
     */
    if (colony.metadata) {
      yield apolloClient.mutate<
        CreateColonyMetadataMutation,
        CreateColonyMetadataMutationVariables
      >({
        mutation: CreateColonyMetadataDocument,
        variables: {
          input: {
            id: getPendingMetadataDatabaseId(colonyAddress, txHash),
            displayName: colonyDisplayName ?? colony.metadata.displayName,
            avatar: colonyAvatarImage,
            thumbnail: colonyThumbnail,
            description: colonyDescription,
            externalLinks: colonyExternalLinks,
            isWhitelistActivated: colony.metadata.isWhitelistActivated,
            whitelistedAddresses: colony.metadata.whitelistedAddresses,
            objective: colonyObjective,
            // We only need a single entry here, as we'll be appending it to the colony's metadata
            // changelog if the motion succeeds.
            changelog: [
              {
                transactionHash: txHash,
                newDisplayName:
                  colonyDisplayName ?? colony.metadata.displayName,
                oldDisplayName: colony.metadata.displayName,
                hasAvatarChanged:
                  colonyAvatarImage === undefined
                    ? false
                    : colonyAvatarImage !== colony.metadata.avatar,
                hasWhitelistChanged: false,
                haveTokensChanged,
                hasDescriptionChanged:
                  metadata?.description !== colonyDescription,
                haveExternalLinksChanged: !isEqual(
                  metadata?.externalLinks,
                  colonyExternalLinks,
                ),
                hasObjectiveChanged:
                  colonyObjective === undefined
                    ? false
                    : !isEqual(metadata?.objective, colonyObjective),
                newSafes: colony.metadata.safes,
                oldSafes: colony.metadata.safes,
              },
            ],
            modifiedTokenAddresses,
          },
        },
      });
    }

id is the variable that the auth proxy is using to check whether to allow the request or not. If we move this pending metadata creation to a lambda function, would that bypass the auth proxy and therefore the need to check?


Rename organizaton public id on the Hubspot companies

For:

https://github.com/hypothesis/report/issues/51

After some back and forth, I think this is a bad idea. The name isn't really any better for the following reasons:

In Hubspot "organization" is ambiguous and could mean H organizations
It's a mapping which means the properties in Hubspot now map less cleanly to column names


Switch from minisearch to algolia

fixes #926
This PR:

switches from minisearch to algolia
indexes all the way down to <h4>s
introduces a GH action that publishes the latest search index to algolia
adds a bash script to copy the public keys into content dir and turn them into a TS default export file

Conclusions:

algolia library is about 5k minzipped
minisearch downloaded a 350k (~50k minzipped) index on the client
I increased our index's granuarity to include h3s and h4s and that increased index by 1-200k (30k minzipped)
algolia queries scale per search and minisearch scales per content
15% byte xfer decrease
12% byte xfer decrease when entered 3 search terms

Regressions:
Introducing @lit-labs/task into the search component has made rollup split up task into its own package (likely because used in both this and in tutorials). That means that we now have 2 network requests for just hydrating the UI of the searchbox which eats into the algolia implementation's perf.
Future work:

create a modal / fullscreen UI that groups results per title

Would super appreciate feedback on the GH action

Re-review ping!


[Generic] Creating an image format with an unknown type is an error

From @pap5508 on February 24, 2017 9:51
Select Photo from the Gallery iOS Simulator.
Error :
[Generic] Creating an image format with an unknown type is an error *** ASL MESSAGE SIZE (25813666 bytes) EXCEEDED MAXIMIMUM SIZE (8192000 bytes) ***
Package.json
"nativescript-imagepicker": "^2.5.1",
Copied from original issue: NativeScript/nativescript-angular#681

Hi @pap5508,
Could you provide some more info about your case? It would help if you could give us some code snippets or sample project, which will allow us to recreate the prblem.
In the meantime, you could also review the sample project here  and to verify, whether you will have the same problem.

@tsonevn : this situation is occurred while photo size is too large and converting it into base64
Will share with you screenshot and Program to regenerate the Error.

Hi @pap5508,
I tested again sample-ImageUpload app while using a large image, however, I am still unable to reproduce this behavior.
Regarding that converting the imageSource to base64 string will not work at the moment. For further info, you could keep track on the issue here.
NativeScript you could use ImageSource saveToFile method, which allows you to save the image source in a temporary file with the needed quality. For more info review the API Reference here.

the quality option doesn't work... in a file of 1mb when savetofile(path,"jpg",10) it produces an 3MB file


added Node 14.17.1 base and chrome91 browser images

any updates on this?

Going to close this image as it's over a year old. If you still need this image you can generate a new one using one of these scripts: https://github.com/cypress-io/cypress-docker-images/blob/master/package.json#L12-L14


Couple edge case fixes

Thanks, I'll fix the weird indentation myself later.

Ah... yeah, I'll try to remember to put my IDE into tab mode next time. Sorry!


Non-functional DeviceInfo::usage and usage_page with linux-static-libusb

linux-static-libusb lacks functionality that other platforms have, such as DeviceInfo::usage() and DeviceInfo::usage_page(). It appears libusb doesn't support this at all, and hidapi works around it with a rather invasive detach/reattach process, and the documentation is difficult to find.
There are no warnings in hidapi-rs' documentation that this isn't supported with the default linux-static-libusb, which led to a frustrating troubleshooting process trying to "fix" something that worked fine on macOS and Windows. 🙃
Expected behaviour

DeviceInfo::usage and DeviceInfo::usage_page should be entirely removed when using libusb backends on Linux
linux-static-hidraw should be seriously considered as the default backend on Linux (where this functionality actually works)

I have already considered moving to hidraw by default for many times, each time however, there was some problem with old linux kernel.
However since the thing with usage  & usage_page is pretty annoying (and even if in docs I doubt everyone will read them), I think its finally time to move to the hidraw backend by default. That will also make it fine to configure out the usage and usage_page properties.
If some projects want to support old kernels, they can switch to the libusb backend, and remove usage & usage_page parts in code.

Should be fixed now, I published a 2.0.0 version of the crate because of the breaking change.
Also took the time to remove all the deprecated items from the code.

Thanks for the prompt response!
PS: While hidraw is now the default, the module documentation still says libusb is the default on the master branch at the time of writing:
https://github.com/ruabmbua/hidapi-rs/blob/fcaf6df669346f067f5c847998499305e4cc3ba1/src/lib.rs#L40-L41

Thanks for noticing, fixed it and published new crate version so it gets updated on docs.rs


Erro ionicons.woff ENOSPC

help!
ionic 2.1.18
ionic serve

ionic-hello-world@ ionic:serve /home/eduardo/public_ionic/gpm
ionic-app-scripts serve "--v2" "--address" "<IP_ADDRESS>" "--port" "8100" "--livereload-port" "35729"

keywords if/then/else require v5 option
[09:53:37]  ionic-app-scripts 0.0.47
[09:53:37]  watch started ...
[09:53:37]  build dev started ...
[09:53:37]  clean started ...
[09:53:37]  clean finished in 5 ms
[09:53:37]  copy started ...
[09:53:37]  transpile started ...
[09:53:39]  transpile finished in 2.54 s
[09:53:39]  webpack started ...
[09:53:39]  copy finished in 2.65 s
[09:53:46]  webpack finished in 6.94 s
[09:53:46]  sass started ...
[09:53:47]  sass finished in 1.11 s
[09:53:47]  build dev finished in 10.62 s
[09:53:47]  watch failed: watcher error:
/home/eduardo/public_ionic/gpm/home/eduardo/public_ionic/gpm/src/assets//*,/home/eduardo/public_ionic/gpm/src/index.html,/home/eduardo/public_ionic/gpm/src/manifest.json,/home/eduardo/public_ionic/gpm/src/service-worker.js,/home/eduardo/public_ionic/gpm/node_modules/ionicons/dist/fonts//,/home/eduardo/public_ionic/gpm/node_modules/ionic-angular/fonts/**/,/home/eduardo/public_ionic/gpm/node_modules/ionic-angular/polyfills/polyfills.js:
Error: watch /home/eduardo/public_ionic/gpm/node_modules/ionic-angular/fonts/ionicons.woff ENOSPC
[09:53:47]  dev server running: http://localhost:8100/

I have the same issue.
Your system information:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.8
Node Version: v7.5.0
Xcode version: Not installed

I too got that error today. Here is my ionic info:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.4
Node Version: v6.9.5
Xcode version: Not installed

You should bump down to app-scripts 1.0.0
And then if you will get this new error -
[19:17:12]  watch failed: watcher error: /home/dmitry/work/wanted/home/dmitry/work/wanted/src/**/*.(ts|html|s(c|a)ss): Error: watch /home/dmitry/work/wanted/src ENOSPC
you should do it -
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p


Appstudio update test-component-pac-yhcw

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-yhcw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
29 seconds
clone-repository

✅ Succeeded
40 seconds
sast-snyk-check

✅ Succeeded
2 minutes
build-container

✅ Succeeded
8 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
26 seconds
sbom-json-check

✅ Succeeded
9 seconds
inspect-image

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
10 seconds
show-summary

Pipelines as Code CI/test-component-pac-yhcw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
29 seconds
clone-repository

✅ Succeeded
40 seconds
sast-snyk-check

✅ Succeeded
2 minutes
build-container

✅ Succeeded
9 seconds
inspect-image

✅ Succeeded
8 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
26 seconds
sbom-json-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
10 seconds
show-summary

✅ Succeeded
8 seconds
show-sbom

Pipelines as Code CI/test-component-pac-yhcw-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
8 seconds
sast-snyk-check

✅ Succeeded
24 seconds
build-container

✅ Succeeded
8 seconds
deprecated-base-image-check

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
49 seconds
clamav-scan

✅ Succeeded
9 seconds
inspect-image

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
6 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom


zxing.HasTorch returns false on Android even phone has a torch

I tried your sample and code below doesn't display the flash button although my phone has has torch, HasTorch returns always false. If set it true, torch is just working fine on my code. it seems like a bug on android. I tried 3 beta as well. same problem
	overlay = new ZXingDefaultOverlay()
			{
				TopText = "Hold your phone up to the barcode",
				BottomText = "Scanning will happen automatically",
				ShowFlashButton = zxing.HasTorch,
                AutomationId = "zxingDefaultOverlay",
			};

Torch does have issues on Android.    FlashCommand property of DefaultOverlay does not work.  IsTorchOn property of ScannerView does not work.  First time Torch is turned on, it doesn't turn on...    (Note: I also could not get property IsScanning to work properly: see workaround below)
Below is what I had to do to get the Torch button to work.  (Version 2.4.1 of the library - I haven't tried 3.0 in Beta)
I recommend just setting ShowFlashButton to true.   (Am curious: Is there any device who's camera is capable enough to run this library, yet does not have a torch?  Are there known issues with always setting it to true?)
I do MVVM, but couldn't for the Torch because of those properties not working.  (I do use MVVM for the scan Result)
XAML:
?xml version="1.0" encoding="utf-8"?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             xmlns:prism="http://prismlibrary.com"
             prism:ViewModelLocator.AutowireViewModel="True"
             x:Class="YourNameSpace.ScanPage"
             xmlns:zxing="clr-namespace:ZXing.Net.Mobile.Forms;assembly=ZXing.Net.Mobile.Forms"
             >
    <StackLayout>
        <Button Text="Cancel"
                Command="{Binding ExclusiveCommand}"
                CommandParameter="Cancel"
                TextColor="Black"
                BackgroundColor="LightGray"
                FontSize="10"
                HorizontalOptions="FillAndExpand"
                />
        <Grid VerticalOptions="FillAndExpand" HorizontalOptions="FillAndExpand">
            <zxing:ZXingScannerView x:Name="ScannerView"
                                    IsAnalyzing="{Binding IsAnalyzing}"
                                Result="{Binding Result, Mode=OneWayToSource}"
                                ScanResultCommand="{Binding ScanResultCommand}"
                                WidthRequest="200"
                                HeightRequest="200" />
            <!-- DOES NOT WORK in View -->
            <!--IsTorchOn="{Binding IsTorchOn, Mode=TwoWay}"-->

            <zxing:ZXingDefaultOverlay
            x:Name="ScannerOverlay"
            TopText="Place the red line over the barcode."
            BottomText="Hold the device steady for a second."
            ShowFlashButton="True"
            Opacity="0.8"
            FlashButtonClicked="ScannerOverlay_FlashButtonClicked" />
            <!-- DOES NOT WORK in View -->
            <!--FlashCommand="{Binding FlashCommand}"-->

        </Grid>
    </StackLayout>
</ContentPage>

Code Behind for Torch:  (and a few other things I couldn't get working with MVVM / bound properties)
using System;
using System.Collections.Generic;
using Xamarin.Forms;
using ZXing.Mobile;

namespace YourNameSpace
{
public partial class ScanPage : ContentPage
{
	public ScanPage()
	{
		InitializeComponent();

		// https://blog.verslu.is/xamarin/xamarin-forms-xamarin/zxing-android-skipping-frames/
		ScannerView.Options.DelayBetweenAnalyzingFrames = 5; // 5 milliseconds, and lower than the default - weird that it's better
		ScannerView.Options.DelayBetweenContinuousScans = 2000; //2000
		ScannerView.Options.InitialDelayBeforeAnalyzingFrames = 300;
		ScannerView.Options.TryHarder = false;
		ScannerView.Options.TryInverted = false;
		ScannerView.Options.AutoRotate = false;
		ScannerView.Options.UseFrontCameraIfAvailable = false;
		ScannerView.Options.PossibleFormats.Clear();
		ScannerView.Options.PossibleFormats.Add(ZXing.BarcodeFormat.CODE_128);

		// WORKS BUT DOESN'T DO ANY BETTER THAN DEFAULT
		//ScannerView.Options.CameraResolutionSelector = SelectLowestResolutionMatchingDisplayAspectRatio;
	}

	private bool _isFirstTorchOnRequest = true;

	private CameraResolution SelectLowestResolutionMatchingDisplayAspectRatio(List<CameraResolution> availableResolutions)
	{
		#pragma warning disable 162
		return new CameraResolution() { Width = 352, Height = 288 };

		if (availableResolutions == null || availableResolutions.Count < 1)
		{
			return new CameraResolution() { Width = 1088, Height = 1920 };
		}

		// Resolution is returned from lowest to highest on Android (possibly the reverse on iPhone!)
		return availableResolutions[index: 0];
		#pragma warning restore 162
	}

	private void ScannerOverlay_FlashButtonClicked(Button sender, EventArgs e)
	{
		if (_isFirstTorchOnRequest) // else won't turn on with 1st click
		{
			ScannerView.IsTorchOn = true;
			_isFirstTorchOnRequest = false;
		}
		else
		{
			ScannerView.IsTorchOn = !ScannerView.IsTorchOn;
		}
	}

	protected override void OnAppearing()
	{
		base.OnAppearing();

		ScannerView.IsScanning = true;
	}

	protected override void OnDisappearing()
	{
		base.OnDisappearing();

		ScannerView.IsScanning = false;
	}
}
}

Relevant parts of ViewModel:
	private bool _doScan = true;
	private bool _isAnalyzing = true; // start with analysis on

	public bool IsAnalyzing
	{
		get => _isAnalyzing;
		set => SetProperty(ref _isAnalyzing, value);
	}

	private Result _result;
	public Result Result
	{
		get => _result;
		set => SetProperty(ref _result, value);
	}

	private DelegateCommand _scanResultCommand;
	public DelegateCommand ScanResultCommand => _scanResultCommand ??= new DelegateCommand(ExecuteScanResultCommand);//, CanExecuteScanResultCommand);

	/// <summary>
	/// Unlike your typical button command, this methods is called from the hardware, on a non-UI thread
	/// </summary>
	private void ExecuteScanResultCommand()
	{
		if (!_doScan) // use this non-UI property to block re-entry, as this call comes in on a non-UI thread
		{
			return;
		}

		_doScan = false; // doing this immediately, in this thread, to really avoid re-entry

		_player.PlayScannerBeep(); // play early because human response is slow

		_deviceService.BeginInvokeOnMainThread(async () =>
		{
			IsAnalyzing = false; // while could set _doScane false earlier, must call the rest from UI thread
			var barcode = Result.Text;  // not exactly what I do, but same principle.
		});

		// NOTE:  DO NOT set _doScan = true here, because this code runs in separate thread from Main UI thread, BEFORE GoBackWithBarcodeAsync completes.
	}

...I haven't tried 3.0 in Beta)

Hey @thhowl can you try 3.0 beta please?

@knocte , I will try 3.0 beta next week.

I already wrote in the issue that i tried and problem persists.

I had the same issue and it appeared that I didn't have the Android FLASHLIGHT permission in the AndroidManifest.xml (silly me).


Args.InsertParam resets index to param size if it’s out of bound

Args.InsertParam panics about index out of bound if the index is larger than param size. These changes reset the index to param size for such case. This is equivalent to appending new items to the end.
This fixes #812.

:shipit: ?

Yep :ship: if it solves the problem; thanks for working on this


feat(build): use patched versions of four upstream receivers

Use patched versions of:

hostmetricsreceiver
apachereceiver
mysqlreceiver
elasticsearchreceiver

The intent is to move back to using upstream as the necessary changes are merged.

This should wait for #769


Fix border props sequence

Fixes following issue:
let's say we have a component:
const Component = () => styled.div`
  ${borders}
`

then we render it with the following props:
<Component borderBottom="1px solid" borderColor="red" />

than CSS will be:
border-color: red;
border-bottom: 1px solid;

the red color will be replaced with inherit which is #000 in Chrome 72

Good catch, thanks! Should borderStyle and borderWidth be rearranged as well?

@jxnblk absolutely!
Thanks for the awesome lib!

Thanks for this! Going to merge and :shipit:


Consider specifying a given architecture for APIs when targetting AnyCPU

Is your feature request related to a problem? Please describe.
Windows Forms needs to build for AnyCPU so customers can continue to build for AnyCPU. Some Win32 APIs are not really portable (notably the Pack = 1 versions), but for WinForms internal purposes the x86/x64 definitions are equivalent.
Describe the solution you'd like
The ability to specify in the settings json that we want specific listed APIs to come from a given architecture. This would also allow us to address things like Get/SetWindowLong/Ptr.
Describe alternatives you've considered
The only real alternative is to manually define things- which is very much not desirable. :)
Additional context
I spoke with @tannergooding a bit about this and he helped me understand this is not something we can really deal with at the Win32Metadata level as it has to allow for all consumers (can't presume .NET) and uses of the data structures (composition within other types, etc.).

In TerraFX, I ended up dealing with many of these "manually".
For example, I explicitly define custom versions of GetWindowLongPtrA/W which handles the difference between the 32-bit and 64-bit versions.
Another example is SP_DEVINFO_DATA where I've defined a helper type that unions the 32-bit vs 64-bit differences.
Such a type is "portable" for the purposes of a P/Invoke that takes this type directly. It is not however usable "everywhere". It cannot for example be used to define SP_PROPSHEETPAGE_REQUEST.
Instead we have to define 32/64-bit variants of this struct as well and expose a higher level wrapper there as well. A user would likely have to abstract it themselves for any of their own structures they define it in. This isn't "common" so it isn't normally an issue. -- There also come with a few quirks, such as not being able to use sizeof(T), etc.

Windows Forms needs to build for AnyCPU so customers can continue to build for AnyCPU.

Many assemblies in .NET are built architecture specific. In fact all of them since R2R makes them so. The requirement is that the reference assembly target AnyCPU so that customers can target AnyCPU with their apps. WinForms could do the same (and as much as you're hitting arch-specific APIs, maybe it should). I understand that the work to enable this in the multi-repo build system would be complex, so maybe that's not the right call. But let's be clear about the requirement so we consider all options.
I'm willing to think through the ramifications of the proposal, but it may not be trivial. And it may be far more complex for the user than they realize. For example, if they state they want a single struct to be declared from its x64 metadata, but that struct references other structs that are also x64, you may end up with many x64 structs, and not realize when you're using one that it isn't actually safe in x86 or arm64 processes.
This might not 'just work' for GetWindowLongPtr either. In past conversations on that topic, I thought we concluded very special code would have to be emitted. @tannergooding's example code seems to confirm that.

To be clear, this is an expediency. It is an "unsafe" feature that allows consuming the metadata. We have no choice but to keep WinForms AnyCPU and that forces manual definition of a number of things. We can iterate to move common abstractions (such as Set/GetWindowLong in CsWin32.
Perhaps we can take a page from the .NET libraries and have these in the settings as "UnsafeAsX64" and "UnsafeAsX86". Could potentially also fail out on given APIs when they're given a suitable wrap in CsWin32?


1.22.7, 1.23.0, and 1.23.1 Go releases

Opening this issue to track tagging releases for 1.22.7, 1.23.0, and 1.23.1 Go releases.
Last time this was done, https://github.com/golang-fips/go/issues/212.

I did a wip for go1.23 https://github.com/golang-fips/go/issues/224 if it can help

👋 A nudge to maintainers, this series of updates includes important updates. How can we assist in driving these forward?
cc @ash2k @dustinmm80 @ashmckenzie: We do have 1.22.7 now 👍 (https://github.com/golang-fips/go/tree/go1.22.7-1-openssl-fips)

Sorry for the delay in responding to this issue. The main branch is currently at 1.22.7, and the PR for 1.23.1 is here: https://github.com/golang-fips/go/pull/238.

Hi @derekparker,
I tried to build your PR in ubuntu 20.04 fips and scripts/crypto-test.sh failed at
=== RUN   TestBoringServerCurves/curve=25497
=== RUN   TestBoringServerCurves/curve=25497/fipstls
panic: runtime error: index out of range [0] with length 0
goroutine 131 [running]:
crypto/tls.(*Conn).makeClientHello(0xc000398a88)
/build/golang-fips/go/src/crypto/tls/handshake_client.go:152 +0x18f9
crypto/tls.(*Conn).clientHandshake(0xc000398a88, {0x89fe98, 0xc000132d70})
/build/golang-fips/go/src/crypto/tls/handshake_client.go:264 +0x7d
crypto/tls.(*Conn).handshakeContext(0xc000398a88, {0x89fca0, 0xb10400})
/build/golang-fips/go/src/crypto/tls/conn.go:1568 +0x3a6
crypto/tls.(*Conn).HandshakeContext(...)
/build/golang-fips/go/src/crypto/tls/conn.go:1508
crypto/tls.(*Conn).Handshake(...)
/build/golang-fips/go/src/crypto/tls/conn.go:1492
crypto/tls.testHandshake.func1()
/build/golang-fips/go/src/crypto/tls/handshake_test.go:479 +0x145
created by crypto/tls.testHandshake in goroutine 130
/build/golang-fips/go/src/crypto/tls/handshake_test.go:477 +0x167
Same environment 1.22.x can pass the test.  Do you see similar issue?
Thanks

Hi, @derekparker
Latest commit working now, thanks.

All set here, closing issue. Thank you!


Update typedoc-plugin-markdown

Description of change
Updated typedoc to fix the sidebar issue.
Links to any relevant issues
Fixes #751
Type of change

Documentation Fix

How the change has been tested
Tested locally
Change checklist

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation

What's up with this?

Blocked. I need to update the wiki to docusaurus v3 before this works properly it seems


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.25",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e043fb5a0336ee74614e26f0d9f36f1f5bb6d606"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "e043fb5a0336ee74614e26f0d9f36f1f5bb6d606",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "nvme: fix a possible use-after-free in controller reset during load\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.25 by commit e043fb5a0336ee74614e26f0d9f36f1f5bb6d606. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000454


HNC: exceptions feature

This issue is to track the implementation of exceptions, the design doc can be found at https://docs.google.com/document/d/17J8icBEDvLLoPT4kQ4ArZcCerRweDY-TpJ48DJKpHJ0

This isn't required for HNC v0.6 to moving to v0.7. However much we can get done in v0.6 is what we'll release.

I think we're done here - nice work!
/close


Lower default globalmax

Type of change

Bugfix

Description
Modifies examples to use a lower default global max as well as make the init script set the global max to 1/8 of container memory if it was unset (-1).
Fixes #4574
Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[x] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[x] Reference relevant issue(s) and close them after merging
[x] Update CHANGELOG.md

@enmasse-ci run tests profile=shared

:x: Test Summary :x:
TEST_PROFILE: shared
TEST_CASE:
TOTAL: 231
PASS: 213
FAIL: 5
SKIP: 13
BUILD_NUMBER: 850
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testPublishQoS0 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testPublishQoS1 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testPublishQoS2 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testRetainedMessages in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testVerylongAddressName in io.enmasse.systemtest.shared.standard.web.FirefoxConsoleTest

@enmasse-ci run tests profile=shared

:x: Test Summary :x:
TEST_PROFILE: shared
TEST_CASE:
TOTAL: 231
PASS: 213
FAIL: 5
SKIP: 13
BUILD_NUMBER: 855
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testPublishQoS0 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testPublishQoS1 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testPublishQoS2 in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testRetainedMessages in io.enmasse.systemtest.shared.brokered.mqtt.PublishTest
testFilterConnectionsByContainerId in io.enmasse.systemtest.shared.standard.web.FirefoxConsoleTest


Impossible to turn off all logging.

We need to stick a null handler on the logger if no logging is enabled, otherwise we'll crash with a "no handlers configured" error.

No longer in master


GDAL_ERROR 6: Unable to load PROJ.4 library (libproj.so)

When using admin.OSMGeoAdmin as my ModelAdmin I get the following error when viewing a PointField in admin:
GDAL_ERROR 6: Unable to load PROJ.4 library (libproj.so), creation of
OGRCoordinateTransformation failed.
Error transforming geometry from srid '4326' to srid '3857' (OGR failure.)

Looking around the heroku file system this file seems to be in this location fine /app/.geodjango/proj4/lin/libproj.so
I'm not sure how to debug any further.

That fix worked for me also. I was getting an OGRException error, but only with Heroku. Running locally with "foreman start" or "manage.py runserver" didn't cause the error. Should probably look at making this a permanent fix.

Indeed @acer9997 I've included the fix in the buildpack, no need to do manual fixing.


Increase size of parent cache

Problem:
Requests are taking a long time, particularly pod requests. If there are a large amount of resources (over 1k) records are shifted out of the cache before they are ever accessed. This causes a large amount of misses, forcing the parent information to be retrieved. This retrieval can take >50ms per item.
Solution:
Increased size of parent cache to 100k from 1k. Size of cache has increased 10x and misses have been largely reduced.
Note: object being cached has small memory footprint, and should not lead to large increase of memory
Issues:
https://github.com/rancher/rancher/issues/18870
https://github.com/rancher/rancher/issues/18522
https://github.com/rancher/rancher/issues/18295

LGTM

LGTM


Launch All Mocha Tests does not attach the debugger

I cloned the project.
Once I run with VS Code with F5 and Launch All Mocha Tests selected, it passed all tests but breakpoint does not get hit.
Any idea on this?

Debugger is getting attached to .js file instead of .ts file. Need to fix sourceMap.