PrimeIntellect/SWE-rebench-V2 huggingface dataset:
Repository: box-project/box (php)

Issue:
Docker support with PHP 8
As latest version 3.16.0, Box is supposed to support both PHP 7.x and 8.x

But when you look inside [DockerFileGenerator](https://github.com/box-project/box/blob/3.16.0/src/DockerFileGenerator.php#L43-L49) no images are defined for PHP 8.0 and 8.1

Is it just forgotten ? `8.0-cli-alpine` and `8.1-cli-alpine` images are available on DockerHub

Pull request:
Add PHP 8.0 and 8.1 to DockerFileGenerator
Closes #630

Patch:
diff --git a/src/DockerFileGenerator.php b/src/DockerFileGenerator.php
index e4a82edb..863ad7af 100644
--- a/src/DockerFileGenerator.php
+++ b/src/DockerFileGenerator.php
@@ -41,6 +41,8 @@ final class DockerFileGenerator
         Dockerfile;
 
     private const PHP_DOCKER_IMAGES = [
+        '8.1.0' => '8.1-cli-alpine',
+        '8.0.0' => '8.0-cli-alpine',
         '7.4.0' => '7.4-cli-alpine',
         '7.3.0' => '7.3-cli-alpine',
         '7.2.0' => '7.2-cli-alpine',


Test patch:
diff --git a/tests/DockerFileGeneratorTest.php b/tests/DockerFileGeneratorTest.php
index a7211a4c..fadd6213 100644
--- a/tests/DockerFileGeneratorTest.php
+++ b/tests/DockerFileGeneratorTest.php
@@ -66,7 +66,7 @@ class DockerFileGeneratorTest extends TestCase
             ;
         } catch (UnexpectedValueException $exception) {
             $this->assertSame(
-                'Could not find a suitable Docker base image for the PHP constraint(s) "^5.3". Images available: "7.4-cli-alpine", "7.3-cli-alpine", "7.2-cli-alpine", "7.1-cli-alpine", "7-cli-alpine"',
+                'Could not find a suitable Docker base image for the PHP constraint(s) "^5.3". Images available: "8.1-cli-alpine", "8.0-cli-alpine", "7.4-cli-alpine", "7.3-cli-alpine", "7.2-cli-alpine", "7.1-cli-alpine", "7-cli-alpine"',
                 $exception->getMessage(),
             );
         }
Repository: vaskoz/dailycodingproblem-go (go)

Issue:
Day 228
Good morning! Here's your coding interview problem for today.

This problem was asked by Twitter.

Given a list of numbers, create an algorithm that arranges them in order to form the largest possible integer. For example, given `[10, 7, 76, 415]`, you should return `77641510`.

Pull request:
Day228
Resolves #470.

Patch:
diff --git a/README.md b/README.md
index 8cb2218..c1adf43 100644
--- a/README.md
+++ b/README.md
@@ -237,3 +237,4 @@ problems from
 * [Day 224](https://github.com/vaskoz/dailycodingproblem-go/issues/462)
 * [Day 225](https://github.com/vaskoz/dailycodingproblem-go/issues/465)
 * [Day 226](https://github.com/vaskoz/dailycodingproblem-go/issues/467)
+* [Day 228](https://github.com/vaskoz/dailycodingproblem-go/issues/470)
diff --git a/day228/problem.go b/day228/problem.go
new file mode 100644
index 0000000..f5954a8
--- /dev/null
+++ b/day228/problem.go
@@ -0,0 +1,23 @@
+package day228
+
+import (
+	"sort"
+	"strconv"
+	"strings"
+)
+
+// LargestPossibleInteger returns the largest possible integer
+// constructed by these given numbers.
+func LargestPossibleInteger(nums []int) int {
+	strs := make([]string, len(nums))
+	for i, num := range nums {
+		strs[i] = strconv.Itoa(num)
+	}
+	sort.Slice(strs, func(i, j int) bool {
+		first, _ := strconv.Atoi(strs[i] + strs[j])
+		second, _ := strconv.Atoi(strs[j] + strs[i])
+		return first > second
+	})
+	result, _ := strconv.Atoi(strings.Join(strs, ""))
+	return result
+}


Test patch:
diff --git a/day228/problem_test.go b/day228/problem_test.go
new file mode 100644
index 0000000..9f0bc6f
--- /dev/null
+++ b/day228/problem_test.go
@@ -0,0 +1,31 @@
+package day228
+
+import "testing"
+
+var testcases = []struct {
+	nums     []int
+	expected int
+}{
+	{[]int{10, 7, 76, 415}, 77641510},
+	{[]int{7, 76, 789}, 789776},
+	{[]int{789, 7, 76}, 789776},
+	{[]int{789, 76, 7}, 789776},
+	{[]int{791, 7}, 7917},
+}
+
+func TestLargestPossibleInteger(t *testing.T) {
+	t.Parallel()
+	for _, tc := range testcases {
+		if result := LargestPossibleInteger(tc.nums); result != tc.expected {
+			t.Errorf("Expected %d, got %d", tc.expected, result)
+		}
+	}
+}
+
+func BenchmarkLargestPossibleInteger(b *testing.B) {
+	for i := 0; i < b.N; i++ {
+		for _, tc := range testcases {
+			LargestPossibleInteger(tc.nums)
+		}
+	}
+}
Repository: vue-gl/vue-gl (js)

Issue:
VueGL + Nuxt: Cannot read property 'trim' of undefined
I created a project with Nuxt (2.14.0), VueGL (0.22.0) and Three (0.117.1) packages. Then I created 3 pages, each one with a different VueGL example. Each page have only one section with `vgl-` components inside, all of they imported and exposed to the template. This is [the repository](https://github.com/ErickPetru/tdcsp2020-vuegl) of the project.

When in development (`yarn dev`), I receive an error when trying to navigate between pages with `$router.push` or `nuxt-link`: 

    TypeError: Cannot read property 'trim' of undefined
      at ze (vue-gl.esm.js?2692:1)
      at VueComponent.beforeDestroy (vue-gl.esm.js?2692:1)
      ...

Strangely, I have no error if I reload the page from scratch (i.e. <kbd>F5</kbd>) or even if I run the project from `dist` folder, after using `yarn generate` (as you can see it working without errors in [the deployed static site](https://tdcsp2020-vuegl.netlify.app/).


Pull request:
Fix an error on beforeDestroy hook when the material prop is not defined
Resolves #977 

Patch:
diff --git a/src/mixins.js b/src/mixins.js
index 093c828..d01af95 100644
--- a/src/mixins.js
+++ b/src/mixins.js
@@ -37,7 +37,9 @@ export const VglObject3dWithMatarial = {
   },
   beforeDestroy() {
     const { vglNamespace: { materials }, material, setMaterial } = this;
-    parseNames(material).forEach((name) => materials.unlisten(name, setMaterial));
+    if (material !== undefined) {
+      parseNames(material).forEach((name) => materials.unlisten(name, setMaterial));
+    }
   },
 };
 


Test patch:
diff --git a/test/objects/vgl-mesh.spec.js b/test/objects/vgl-mesh.spec.js
index 59308b6..0160f39 100644
--- a/test/objects/vgl-mesh.spec.js
+++ b/test/objects/vgl-mesh.spec.js
@@ -1,6 +1,8 @@
 import Vue from 'vue/dist/vue';
 import { Mesh } from 'three';
-import { VglMesh, VglObject3d, VglNamespace } from '../../src';
+import {
+  VglMesh, VglObject3d, VglNamespace, VglMaterial,
+} from '../../src';
 
 describe('VglMesh', () => {
   let inject;
@@ -16,4 +18,18 @@ describe('VglMesh', () => {
     expect(Object.keys(new (Vue.extend(VglMesh))({ inject }).$props))
       .toEqual(expect.arrayContaining(Object.keys($props)));
   });
+  // #977
+  test('the parsing names should not be called when the material prop is not defined', async () => {
+    Vue.config.errorHandler = jest.fn();
+    const vm = new (Vue.extend(VglMesh))({ inject });
+    vm.$destroy();
+    await vm.$nextTick();
+    expect(Vue.config.errorHandler).not.toHaveBeenCalled();
+  });
+  test('the material prop can accept multiple material names', () => {
+    const { inst: mt1 } = new (Vue.extend(VglMaterial))({ inject, propsData: { name: 'mt1' } });
+    const { inst: mt2 } = new (Vue.extend(VglMaterial))({ inject, propsData: { name: 'mt2' } });
+    const { inst } = new (Vue.extend(VglMesh))({ inject, propsData: { material: 'mt1 mt2' } });
+    expect(inst).toHaveProperty('material', [mt1, mt2]);
+  });
 });