Problem adding Surface element to existing app

I'm having some problems adding a Surface component to my existing app, I have no problem running the example files but no matter what I try in my app I get the following error:
Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.
This usually means that you're trying to add a ref to a component that doesn't have an owner (that is, was not created inside of another component's `render` method).
Try rendering this component inside of a new top-level component which will hold the ref.

Even this simple example throws the error:
var React = require('react');
var ReactCanvas = require('react-canvas');
var Surface = ReactCanvas.Surface;
var Text = ReactCanvas.Text;

window.onload = function() {
	React.render(<Surface top={0} left={0} width={100} height={100}>
		<Text>Professor PuddinPop</Text>
	</Surface>, document.body);
}

Am I doing something wrong?

Nevermind, after moving from browserify to webpack I uninstalled and installed the module again and it started working


Making mock in setup() breaks serialization of Collection

Laravel Version: 5.8.27
PHP Version: 7.3
Database Driver & Version: 5.7

Description:
When I define a mock in the setup() method of a test case, using shouldReceive() and returnUsing(), a test serializing a collection breaks, throwing an exception:
Serialization of 'Closure' is not allowed

Steps To Reproduce:
Run the test below:
<?php

namespace Tests\Unit;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Support\Collection;
use Mockery;
use PHPUnit\Framework\TestCase;

class TestClass {
    public function test(): string
    {
        return 'test';
    }
}

class Test extends TestCase
{
    /**
     * @var Mockery\MockInterface|TestClass
     */
    protected $testClass;

    public function setUp(): void
    {
        parent::setUp();

        Mockery::mock(TestClass::class)
            ->shouldReceive('test')
            ->andReturnUsing(function () {
                return 'test';
            })
            ->getMock();
    }

    /**
     * @test
     */
    public function it_serializes_a_collection_with_a_mock_inside()
    {
        $collection = new Collection([Mockery::mock(Model::class)]);
        $serialized = serialize($collection);
        $unserialized = unserialize($serialized);
        $this->assertEquals($unserialized, $collection);
    }
}

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


fix appcompat vector drawables

...and fix color of new tweet icon

...added some minor unrelated fixes

(y)

+1


Running C++ code on CPU with a Cuda-enabled installation of tensorflow

Hi,
I have built your project with GPU support and it works perfectly (Thank you!), but I wish to test my code on CPU too, Is there a way to do this with the current installation? If yes, How can I do it? What lines do I need to add to my code?
If no, How can I build tensorflow_cc in CPU-only mode? I wasn't able to find any such options in CmakeLists.txt. And Is it possible to have two installations of tensorflow_cc on one system?
I really appreciate any help as I'm new to TF and wasn't able to find anything useful by Googling (just a bunch of python stuff!). Thank you!

Hi, I am glad that tensorflow_cc works for you.
I am not sure if this is what you need, but if you have already built tensorflow_cc with GPU support, there is no need to rebuild it on order to run your program on CPU. Just launching your program with empty CUDA_VISIBLE_DEVICES environmental variable should do the job:
CUDA_VISIBLE_DEVICES="" ./my-program

This solution should actually work for any program utilizing CUDA, see Accelwareblog for more tips.
Is this what you wanted?

Thank you very much! That's exactly what I need!
On Sat, Mar 31, 2018 at 2:15 AM, Filip Matzner<EMAIL_ADDRESS>wrote:

Hi, I am glad that tensorflow_cc works for you.
I am not sure if this is what you need, but if you have already built
tensorflow_cc with GPU support, there is no need to rebuild it on order
to run your program on CPU. Just launching your program with empty
CUDA_VISIBLE_DEVICES environmental variable should do the job:
CUDA_VISIBLE_DEVICES="" ./my-program
This solution should actually work for any program utilizing CUDA, see
Accelwareblog http://acceleware.com/blog/cudavisibledevices-masking-gpus
for more tips.
Is this what you wanted?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FloopCZ/tensorflow_cc/issues/74#issuecomment-377630471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APaJX2t1EYWMERPpDvE1zXKOpIUVhSbXks5tjqd5gaJpZM4TBZnu
.


Chore: Refactored to use clap

Refactored to use a more standard way of handling command line arguments by using clap

Looks great, merged!


Adding support for SURF Features

Map matching pipeline supports SURF map with SURF DBoW2 vocabulary. Also made some bug fixes/warnings in the pipeline.
Note that the vocabulary-building pipeline is sensitive to the total number of features in the map--it won't construct a vocabulary if there are too many features. Choose a reasonable Hessian threshold for keypoint detection when constructing the map from images.
Added new tools in localization_analysis/scripts:
plot_detector_comparison compares matched poses using SURF, and BRISK, and optionally groundtruth
analyze_gaps plots a histogram of gaps in localization from a directory of bags.

Nice work! Some comments mostly about files from other places, shared functions, etc, but looks good!


[Feature]: The VS Code Extension should have access to the taq scaffold command

As a Taqueria VS Code Extension user I want the taq scaffold to be available in the command palette and show the available scaffolds so that I don't have to manually type the scaffold name in the command palette.
Acceptance Criteria

[x] Opening command palette shows taq scaffold as Taqueria: Scaffold
[x] Once 'Taqueria: Scaffold` is selected, a list of available scaffolds is shown (create QuickPick - https://code.visualstudio.com/api/references/vscode-api#window)
[x] User is able to select the scaffold from the list
[x] Once selected, the project is scaffolded out from the selected option
[ ] Honour 1st Party, Verified 3rd Party, Unverified 3rd party, Banned 3rd Party
[ ] Minimum version number for

[ ] Taqueria core
[ ] Taqueria VS Code Extension

Solution Options

Awesome Lists
Homebrew model

Issues

[x] #801
[x] #802
[x] #803

[x] #804

[x] #805
[x] #806
[x] #807

Initial Repository.json fields

Name
Description
Path to repo
1st Party, Verified 3rd Party, Unverified 3rd party, Banned 3rd Party
Link to repo
Icon URL
Homepage URL
Simple name (Alias)

Deferred

UI for scaffolds inside VS Code

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Is there an epic for bringing the extension to parity with the CLI or should we turn this into one?

Remaining steps moved to #1101.
Closing this one


HBASE-28328 Add an option to count different types of Delete Markers in RowCounter

A flag is introduced, which, when enabled, allows RowCounter to count the various types of Delete Markers - DELETE_COLUMN, DELETE_FAMILY, DELETE_FAMILY_VERSION. It will also calculate the number of rows having a delete marker.
To enable this the scan object was modified -> if flag is set, raw scan is performed without FirstKeyOnlyFilter.
Note: Commits are cherry-picked from https://github.com/apache/hbase/pull/6435

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 11s

branch-2 passed

+1 :green_heart:
compile
0m 37s

branch-2 passed

+1 :green_heart:
checkstyle
0m 14s

branch-2 passed

+1 :green_heart:
spotbugs
0m 34s

branch-2 passed

+1 :green_heart:
spotless
0m 48s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 11s

the patch passed

+1 :green_heart:
xmllint
0m  1s

No new issues.

+1 :green_heart:
spotbugs
0m 39s

the patch passed

+1 :green_heart:
hadoopcheck
16m  3s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 45s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s

The patch does not generate ASF License warnings.

29m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6496

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile spotbugs checkstyle hbaseanti

uname
Linux 9e4bfaa37199 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1568fc8a751d96ac836a15a5b3e736f03b3966ae

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-mapreduce U: hbase-mapreduce

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3 xmllint=20913

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 45s

branch-2 passed

+1 :green_heart:
compile
0m 19s

branch-2 passed

+1 :green_heart:
javadoc
0m 16s

branch-2 passed

+1 :green_heart:
shadedjars
5m 23s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 33s

the patch passed

+1 :green_heart:
compile
0m 19s

the patch passed

+1 :green_heart:
javac
0m 19s

the patch passed

+1 :green_heart:
javadoc
0m 14s

the patch passed

+1 :green_heart:
shadedjars
5m 20s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
16m  2s

hbase-mapreduce in the patch passed.

35m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6496

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4aa1cf8356c1 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1568fc8a751d96ac836a15a5b3e736f03b3966ae

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/testReport/

Max. process+thread count
2770 (vs. ulimit of 30000)

modules
C: hbase-mapreduce U: hbase-mapreduce

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 10s

branch-2 passed

+1 :green_heart:
compile
0m 25s

branch-2 passed

+1 :green_heart:
javadoc
0m 18s

branch-2 passed

+1 :green_heart:
shadedjars
5m 41s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed

+1 :green_heart:
shadedjars
5m 42s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m 47s

hbase-mapreduce in the patch passed.

40m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6496

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 20da97949aa2 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1568fc8a751d96ac836a15a5b3e736f03b3966ae

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/testReport/

Max. process+thread count
3213 (vs. ulimit of 30000)

modules
C: hbase-mapreduce U: hbase-mapreduce

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  5s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  2s

branch-2 passed

+1 :green_heart:
compile
0m 22s

branch-2 passed

+1 :green_heart:
javadoc
0m 18s

branch-2 passed

+1 :green_heart:
shadedjars
5m 54s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  0s

the patch passed

+1 :green_heart:
compile
0m 21s

the patch passed

+1 :green_heart:
javac
0m 21s

the patch passed

+1 :green_heart:
javadoc
0m 17s

the patch passed

+1 :green_heart:
shadedjars
5m 37s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
21m 17s

hbase-mapreduce in the patch passed.

42m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6496

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d784ef42e540 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 1568fc8a751d96ac836a15a5b3e736f03b3966ae

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/testReport/

Max. process+thread count
3140 (vs. ulimit of 30000)

modules
C: hbase-mapreduce U: hbase-mapreduce

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6496/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Troubleshoot Microsoft Teams for Azure Virtual Desktop

Docs below mentioned customer should not use HTTP proxies on the client endpoint device. But PG already worked for eliminating this restriction and then it should be deleted from our document.
Docs : Troubleshoot Microsoft Teams for Azure Virtual Desktop
https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-teams#known-issues-and-limitations
// Snip
Use of explicit HTTP proxies defined on the client endpoint device isn't supported.
// Snip

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

ID: c8d454bb-f393-2d2c-65ba-6b3bdca747e0
Version Independent ID: 175202ec-09b2-a3b3-fbcd-4fe56b060d57
Content: Troubleshoot Microsoft Teams on Azure Virtual Desktop - Azure
Content Source: articles/virtual-desktop/troubleshoot-teams.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@Naotaka-Kawakami-MSFT
Thanks for your feedback! We will investigate and update as appropriate.

@Heidilohr
please can you review this.

Hi @Naotaka-Kawakami-MSFT - thanks for the feedback. I've checked with PG and while it works, it hasn't been fully tested. This line needs to stay for now, but I've updated it to reflect the current status.  The change should be visible later today.
#please-close


Add regexTitle Filter

fix: better error handling in the transformerfactory
fix: better error handling in the filterfactory
fix: add new filter 'regexTitle'
test: add test for 'regexTitle' filter
test: add test for 'allDayEvents' filter
test: add test for 'declinedEvents' filter

@alxndr13 You've removed the last few commits which I had pushed :confused: . I guess that wasn't intended?

@MichaelEischer damn, yup. that wasn't intended. sorry. Do you still have the commits locally? 😞

Yep, I've force pushed them :-)

Now we should be good to go then :)


Show Open Source Licenses in About Page

I would like to work on it.

@deepakkumardk Oh hello! You can create a new activity that shows all the libraries used in this project as a list for starters. A simple scrollview with text would be awesome!

I am planning to use material-about-library to show all the license.

yeah sure! that would be great!

okay, great I am working on it.


Unexpected token u: SyntaxError: Unexpected token u

Tried using the extension, nothing happens on save/manually running "Execute rubocop", discovered this in the Console:
shell.ts:416Unexpected token u: SyntaxError: Unexpected token u
    at Object.parse (native)
    at onDidExec (/Users/orospakr/.vscode/extensions/misogi.ruby-rubocop-0.2.0/out/src/rubocop.js:40:32)
    at ChildProcess.exithandler (child_process.js:221:5)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

This extension expect JSON output by rubocop.
In this case, command outputs non-JSON output by some reason (I don't know reason).
I released version 0.2.1.
New version catches this case and output exclusive message and (few length of) raw output.


Fix color scheme for Dark Mode toggle button's enabled state

Description
The enabled state of the Dark Mode toggle looks like this currently:

This PR makes it match the look of the Notifications toggle when enabled (blue and white).
Type of Change

Bug fix ('fix', 'repair', 'bug')

Going to do a follow-up PR rewriting this as a function component


Fixing sensor state classes

Why this change ? Are you sure ?

Why this change ? Are you sure ?

I don't really think that's causing any issue, besides not being "up to" HA standards and issuing log messages about the state classes non being correct for their type. Still I haven't really tested this change aside from booting up my instance and checking logs, being night I didn't check any calculations from the integration for possible issues, still, should be an insignificant change

issuing log messages about the state classes non being correct for their type

I don't have any message like that on my side. Strange.
But I think now that all Sensor should be MEASUREMENT and not TOTAL even this gives no impact this is more on the HA philosophie. TOTAL should always increase and that is not the case here. It is a MEASURE of the current cycle.
If you want, you can change for MEASUREMENT (just replace TOTAL by MEASUREMENT) and I will merge it.


Initial implementation for supporting uploading and downloading changes

Initial stab at surfacing SyncSession.downloadAllServerChanges() and SyncSession.uploadAllLocalChanges()
I converted the Java implementation to use coroutines instead, which massively simplified it 🥳 . However there are also some missing questions that need to be solved:
TODO

[x] Testing depends on us finding a way to expose SyncSession. Should probably be in another PR: https://github.com/realm/realm-kotlin/issues/246
[x] In Java, the SyncSession is largely decoupled from the Realm due to the thread-confinement, this e.g. means you have to manually call Realm.refresh() after this is to access the latest state. If Kotlin, since we only have one Realm, it would make sense if we did this on the users behalf, but it is unclear exactly how to implement this.
[x] Constructing the SyncErrorCode object is fairly annoying, but not sure there is a better way?

Ready for review


Improve the log of the download of the images on Docker Registry

During the download process of the images to initialize systems, information of the download process of the layers that make up the image are displayed. But in some cases this information seem extremely confusing, reaching display progress bars superimposed.
Besides this problem, there is no global visibility of the donwload process. Can not identify the number of layers that are downloaded and which the total status of the download process.

I do not know if it's related to this issue, but ...
To me it appeared as 100% since the beginning

@diegoleme, this progress bar has some strange behaviours sometimes. :(


allow set relative base other than './'

Clear and concise description of the problem
it should be allowed to set base to ../../  , but now can only allowed set to './'
eg. here is my project structure
/src/index.ts
/examples/demo1/index.html
/examples/demo2/index.html

my vite.config.js  is like
{
base: './'
build:{
      rollupOptions: {
                        input: {
                            demo1: resolve(__dirname, 'examples/demo1/index.html'),
                            demo2: resolve(__dirname, 'examples/demo2/index.html'),
                        },
              },
   }
}

when I build, I got
/dist/assets/demo1.xxxx.js
/dist/assets/demo2.xxxx.js
/dist/examples/demo1/index.html

but in /dist/examples/demo1/index.html  I got
   <script type="module" crossorigin src="./assets/sdf.adeacfc4.js"></script>
  <link rel="modulepreload" href="./assets/sdf.c557bfd2.js">

it doesn't exist,  it should be ../../assets/xxxx.js
Suggested solution
allowed to set base to ../../
Alternative
or there should be a plugin hook allow us to modify base
Additional context

I need a relative base other than ./ as well, in my case I need something like ./foo/, which cannot be absolute due to constraints of the embedded deployment.
I was able to set base: '/foo/' in my build config and rewrite the HTML with the transformIndexHtml() hook, which works for regular imports in this React application.
However, it fails when lazy-loading with React.lazy() (since that's using the base value in index.js). I tried rewriting the base in the JS using @rollup/plugin-replace, but that did not have access to the Vite code that resolves assets in there.
The application works when changing the base to ./foo/  manually, so I'm not sure why the only relative base for embedded deployment that Vite allows is ./ - this restriction should be removed or explained.

With Vite 2.9.14, /dist/dir/index.html will be:
    <script type="module" crossorigin src="./assets/main.a36da92b.js"></script>
    <link rel="stylesheet" href="./assets/main.201f1386.css">

But with Vite 3.0.4, /dist/dir/index.html will be:
    <script type="module" crossorigin src="../assets/main.3688e8ac.js"></script>
    <link rel="stylesheet" href="../assets/main.d0964974.css">

https://stackblitz.com/edit/vitejs-vite-yferxk?terminal=dev
Closing as it is fixed.


Make area for each search result clickable on mobile

From your iPhone, would be so cooooool to tap the area around each search result to take you to the respective shelter or food cupboard.

Priority 2


(انمي بالكوم)cover photos for anime stopped showing up

Source information
انمي بالكوم 13.12
Source language
arabic
Steps to reproduce
the cover photos for anime stopped showing up
Expected behavior
cover photos for anime should appear
Actual behavior
cover photos for anime stopped showing up
Aniyomi version
preview r6151
Android version
emui 12
Other details
after the update, cover photos for anime stopped showing up
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Duplicate of #2084


Support getindex syntax

This is making me question whether we even need to export dispatch 😄 cc @ali-ramadhan.
Closes #11

I'll leave dispatch for now

bors r+


Control-C during terraform plan seems to do nothing

I've tested it using both Terraform 0.10.4 and 0.10.7.
It seems when I run terraform plan over a bunch of wavefront_alert resources, while they are planning, when I hit ctrl-c, it seems the provider (or Terraform) does not properly process my SIGINT, and just ignores it?
# ~/.tfenv/versions/0.10.7/terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

wavefront_alert.1479532300516: Refreshing state... (ID:<PHONE_NUMBER>516)
wavefront_alert.1458021008243: Refreshing state... (ID:<PHONE_NUMBER>243)
wavefront_alert.1494981712804: Refreshing state... (ID:<PHONE_NUMBER>804)
wavefront_alert.1490742370268: Refreshing state... (ID:<PHONE_NUMBER>268)
wavefront_alert.1487142060104: Refreshing state... (ID:<PHONE_NUMBER>104)
wavefront_alert.1487802465744: Refreshing state... (ID:<PHONE_NUMBER>744)
wavefront_alert.1460519330366: Refreshing state... (ID:<PHONE_NUMBER>366)
wavefront_alert.1496692474344: Refreshing state... (ID:<PHONE_NUMBER>344)
wavefront_alert.1506670630752: Refreshing state... (ID:<PHONE_NUMBER>752)
wavefront_alert.1478203763652: Refreshing state... (ID:<PHONE_NUMBER>652)
^Cwavefront_alert.1506054359125: Refreshing state... (ID:<PHONE_NUMBER>125)
wavefront_alert.1492125056685: Refreshing state... (ID:<PHONE_NUMBER>685)
wavefront_alert.1488961531031: Refreshing state... (ID:<PHONE_NUMBER>031)
.
.
.

OTOH, I tested the same, using same Terraform, over some AWS resources, and Terraform does interrupt appropriately:
› /usr/local/Cellar/tfenv/0.5.2/versions/0.10.7/terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

aws_vpc.vpc: Refreshing state... (ID: vpc-8f7712e9)
aws_security_group.allow_all_outbound: Refreshing state... (ID: sg-7fa24d02)
aws_internet_gateway.igw: Refreshing state... (ID: igw-478bf120)
aws_subnet.public: Refreshing state... (ID: subnet-15bcc54e)
aws_route_table.rt: Refreshing state... (ID: rtb-dfd91fa6)
aws_route_table_association.rta: Refreshing state... (ID: rtbassoc-8d028df5)
aws_main_route_table_association.mrta: Refreshing state... (ID: rtbassoc-eb028d93)
^C
------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

This may not be a bug, but is there anything a provider needs to do to process a ctrl-c?
TIA

I'm gonna close this one. It seems that CTRL-C in Terraform is not consistently cancelling the operation, regardless of provider(s) used.


SCT-597 Add testModeGetUserDisplayName to core code

TODO:
add to API
tests
docs, version bump, release
@sychan has granted me merge authority

So travis is hammered and tests pass locally and I check coverage so I'm merging.


Add unit tests

Add tests to the project to ensure that the code actually is working as expected without needing to test in prod.

closed by #45


pub build packages directory for a Polymer app is too big

Reproduction steps:
$ cd runtime/bin/vmservice/client
$ pub build --mode=release
Look in build/web/packages
Specifically,
824K	./packages/polymer/src/js/polymer
That directory has *two* copies of polymer.js (polymer.js and polymer.concat.js). It also has two map files.
1.6M	./packages/web_components
Same problem here, directory has *two* copies of platform.js (platform.js and platform.concat.js). It also has two map files (each are half a meg in size!).
I'm not sure why .map files are being included in release mode build output.

This issue has been moved to dart-lang/polymer-dart#405.


control_of_documents_v2

Now working on v4, directly forked from the most recent version of the veldnorm. Will take in account comments from here in the new pull request I will make


Pthread error on exit

Newsboat version (copy the output of newsboat -v or the first line of git show):
newsboat 2.22.1
System: OpenBSD 6.9 (amd64)
Compiler: g++ OpenBSD Clang 10.0.1
ncurses: ncurses 5.7.20081102 (compiled with 5.7)
libcurl: libcurl/7.77.0 LibreSSL/3.3.2 zlib/1.2.3 nghttp2/1.43.0 (compiled with 7.76.0)
SQLite: 3.34.1 (compiled with 3.34.1)
libxml2: compiled with 2.9.10
Config file (copy from ~/.newsboat/config or ~/.config/newsboat/config):
auto-reload yes
reload-threads 20
browser firefox

Steps to reproduce the issue:

Open newsboat, wait for it to finish fetching articles

Press q to quit

Observe this error twice in the output: pthread_mutex_destroy on mutex with waiters!

Thanks! This might be a duplicate of #674, although I'm not sure. It might also be a result of this innocuous hack. I don't know the first thing about OpenBSD — is there a way to make it tell us which mutex it is that's being destroyed while locked?

(I marked this as "cannot reproduce", but to be clear: I didn't even try, because I don't have an OpenBSD VM handy.)

Alexander Batischev wrote:

I don't know the first thing about OpenBSD

I'm kind of assuming the bug happens on other OSes as well, but OpenBSD
is just more vocal about it.
If you want an environment to test, Vultr is pretty easy:
https://www.vultr.com/servers/openbsd

is there a way to make it tell us which mutex it is that's being
destroyed while locked?

That would take more debugging. Maybe there's an OS configuration
setting to provide more info. OpenBSD hasn't ported the Clang thread
sanitizer so I'd have to investigate other options.
In the case of this particular issue, it's probably no big deal since
the program is about to be destroyed anyway. Just thought I'd point it
out in case it leads you to find other sketchy things about
synchronization in the code.

Another instance of the same core problem is https://github.com/newsboat/newsboat/issues/2101#issuecomment-1158046690: if the user quits while reloading, stfl_pool is destroyed and subsequent calls to our stfl code crash.


automatic1111 webui  a9eab236d7e8afa4d6205127904a385b2c43bb24 Can it be used？

automatic1111 webui   a9eab236d7e8afa4d6205127904a385b2c43bb24  Can it be used? I don’t want to upgrade to the latest version. When it draws a picture, it doesn’t show up sometimes. For me

https://github.com/ashen-sensored/sd_webui_SAG/pull/4


ko v0.11.1 can deadlock/hang

System Details
OS: macOS Monterey Version 12.3 (21E230)
Arch: amd64 (Intel i9)
Go Version: go1.17.8 darwin/amd64 & go version go1.18 darwin/amd64
Bash: GNU bash, version 5.1.16(1)-release (x86_64-apple-darwin20.6.0)
KO_DOCKER_REPO set to a gcr repo - but I've reproduced this using kind.local as well (see kind setup)
Terminal: iTerm2 Build 3.4.15
Repro Steps
$ go install<EMAIL_ADDRESS>$ git clone https://github.com/knative/serving
$ cd serving
 # default is zsh run bash 5.1
$ bash

# Run the following a few times until it frozen
$ ko resolve -R -f config/core/ > /dev/null

In another terminal run ps -l to see the fork succeed by the exec fail
 UID   PID  PPID        F CPU PRI NI       SZ    RSS WCHAN     S             ADDR TTY           TIME CMD
  502  4408   917     4006   0  31  0 35734780 117648 -      S+                  0 ttys004    0:00.86 ko resolve -R -f config/core/
  502  4651  4408        6   0  31  0 34924148    372 -      R+                  0 ttys004    0:08.97 ko resolve -R -f config/core/

Workaround
Using Apple's Terminal.app I couldn't reproduce the issue (~10 runs). Comparing the difference between the shells I noticed iTerm had some extra env vars.
Setting __CF_USER_TEXT_ENCODING of those did cause ko in Apple's Terminal.app to fail sporadically
export __CF_USER_TEXT_ENCODING=0x1F6:0x0:0x52

After unset'ing that env var in iTerm I didn't encounter a hang
Example run with backtraces
https://gist.github.com/dprotaso/c2725de85ce0e3226709071a29f97bc3

Seems related to the removal of watch mode in #585 -- there was a lot of fiddly concurrency involved in there before, and removing it may not have cleaned everything up correctly.

  Goroutine 58 - User: /usr/local/Cellar/go/1.17.6/libexec/src/runtime/sys_darwin.go:77 syscall.rawSyscall (0x1062327)
	 0  0x0000000001063580 in runtime.systemstack_switch
	     at /usr/local/Cellar/go/1.17.6/libexec/src/runtime/asm_amd64.s:350
	 1  0x0000000001053a86 in runtime.libcCall
	     at /usr/local/Cellar/go/1.17.6/libexec/src/runtime/sys_libc.go:49
	 2  0x0000000001062327 in syscall.rawSyscall
	     at /usr/local/Cellar/go/1.17.6/libexec/src/runtime/sys_darwin.go:77
	 3  0x0000000001068046 in syscall.rawSyscall
	     at :0
	 4  0x0000000001071f2d in syscall.forkAndExecInChild
	     at /usr/local/Cellar/go/1.17.6/libexec/src/syscall/exec_libc2.go:80
	 5  0x0000000001072cc5 in syscall.forkExec
	     at /usr/local/Cellar/go/1.17.6/libexec/src/syscall/exec_unix.go:210
	 6  0x00000000010d1ff2 in syscall.StartProcess
	     at /usr/local/Cellar/go/1.17.6/libexec/src/syscall/exec_unix.go:256
	 7  0x00000000010d1ff2 in os.startProcess
	     at /usr/local/Cellar/go/1.17.6/libexec/src/os/exec_posix.go:55
	 8  0x00000000010d19fa in os.StartProcess
	     at /usr/local/Cellar/go/1.17.6/libexec/src/os/exec.go:109
	 9  0x00000000010fe44a in os/exec.(*Cmd).Start
	     at /usr/local/Cellar/go/1.17.6/libexec/src/os/exec/exec.go:422
	10  0x00000000010fddfe in os/exec.(*Cmd).Run
	     at /usr/local/Cellar/go/1.17.6/libexec/src/os/exec/exec.go:338

I think there's something broken on my system that's preventing the credential helper from starting properly and it just hangs here

Made an go issue here: https://github.com/golang/go/issues/52086

/lifecycle frozen

This is fixed upstream - we just need to wait for a release
https://github.com/golang/go/issues/52086#issuecomment-1320328614

This is done


[BUG] Upgrade 3 nodes Harvester stuck in Pre-drained of the first node (create volume with snapshot)

Describe the bug

When upgrade from v1.1.1 to v1.1.2-rc3, the upgrade stuck in the Pre-drained state of the first node

Prior to upgrade, we have vm backup created while vm is running, create vm snapshot and create volume with volume snapshot.

Some pod keep in pending state rancher-7d68567b9d-ldvwz, harvester-8546cc6cf4-jln8c and harvester-webhook-79df879d8b-gv4z8

To Reproduce
Steps to reproduce the behavior:

Provision a three nodes v1.1.1 Harvester cluster
Create three images
Create three virtual machines separate on each node
Create three VM backups
Add some file to running VM
create two VM snapshots
Create two new volume opensuse-volume, ubuntu-volume
Create two volume snapshots
Perform offline upgrade to v1.1.2-rc3

Expected behavior

Should be able to upgrade successfully with no stuck in the Pre-drained node state when we have vm backup, vm and volume snapshot
Support bundle

supportbundle_cf1194db-d39e-42a4-81f3-153e3d2c7a92_2023-03-20T10-05-48Z.zip
Environment

Harvester ISO version: v1.1.1 -> v1.1.2-rc3
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 3 nodes bare machines

This is a similar issue with https://github.com/harvester/harvester/issues/3648 and will be addressed together in https://github.com/harvester/harvester/pull/3670.

Verified fixed on v1.1.2-rc4 (3/24). Close this issue.
Result
We can upgrade successfully with no stuck in the Pre-drained node state when Harvester have vm backup, vm snapshot and volume snapshot created before upgrade

Test Information

Test Environment: 3 nodes harvester on bare machines
Harvester version: v1.1.2-rc4 (3/24)

Verify Steps
Steps to reproduce the behavior:

Provision a three nodes v1.1.1 Harvester cluster
Create three images
Create three virtual machines separate on each node
Create three VM backups
Add some file to running VM
create two VM snapshots
Create two new volume opensuse-volume, ubuntu-volume
Create two volume snapshots
Perform offline upgrade to v1.1.2-rc3


[GPU] GPU Incorrect Scaling Errors in trivial uniform domain [0.0, 1.0]

Branch:
v1.1.1 tag head
Summary:
OpenColorIO appears to exhibit GPU quantisation errors that are pronounced when using simple 1D LUT encodings such as the sRGB inverse EOTF. It appears that domain values  near [0.0, 1.0] suffer from large 3D shader edge issues.
Additional Information and Diagnostics:
The example configuration located here has a trivial proof of principle. The reference space is a log2 shader allocation of -10 EV to +15 anchored at 0.18 as a middle grey value. Three display colourimetry sets are provided as follows:

Canonized sRGB inverse EOTF via a 1D LUT domain [0.0, 1.0] FileTransform
Commodity sRGB EOTF of pure 2.2 power function via ExponentTransform
Canonized sRGB inverse EOTF via a 1D LUT domain [-0.125, 4.875]

The edge quantisation errors for the value 1.0 in the domain [0.0, 1.0] case results in code value 1.0 transformed into 0.941 on round trip output. The stretched range seems to align the errors such that they are less noticeable. The screenshots below can be sampled for the peak 100% SMPTE test pattern. Also note that between the two identical 0.0-1.0 domains for the 1D LUTs, similar scaling errors are present between the entire range.
Sample imagery from domain [0.0, 1.0]:

Sample imagery from domain [-0.125, 4.875]

Sample imagery from ExponentTransform:

Here's a sample screenshot with the reference space being a smaller-than-sRGB coverage of values of +3 EV to -5 EV. Code value 253/255 results due to the incorrect edge sampling (?) behavior? Likely an EDGE_SIZE - 1 double up somewhere?
The reference space doesn't even cover the generic range that sRGB can cover and the edge error is apparent.


No component found for view with name "RNSVGPath"

Hi,
Sorry for polluting the issue tracker but i can't manage to get it working..
I have this very simple component:
import React, { Component } from 'react';
import Svg, { Polygon } from 'react-native-svg';

class GoodIndicator extends Component {

  constructor(props) {
    super(props);
  }

  render() {
    return (
        <Svg width="14" height="12">
            <Polygon
              fill="#FFFFFF"
              points="347,113636 22,3787205 346 23,5553156 350,454545 28,261696 360 18,1765951 358,886364 17 350,454545 25,9085058"
            />
        </Svg>
    );
  }

}

export default GoodIndicator;

Yet i have the following error:
No Component found for view with name "RNSVGPath"
rnpm says it is correcty linked:
rnpm-install info Android module react-native-svg is already linked
rnpm-install info iOS module react-native-svg is already linked

and i also check manually in the XCode project.
Any idea?
"react": "15.3.2",
"react-native": "0.35.0"

You have the problem with a linking component, rnpm is merged into react-native so you should link native component using react-native link react-native-svg

Hi, thanks for your help!
I actually linked it with the command you mention, i exactly followed what is in the README.
How can i check if the lib is properly linked?
I checked in the Xcode project, i have:

RNSVG.xcodeproj in "Libraries"
libRNSVG.a in "Link Binary With Libraries"
$(SRCROOT)/../node_modules/react-native-svg/ios in "Header Search Paths"

Did you run the project again after linking?

I don't know what happened with the linking... thanks!


Don't see a PIPE in the 'Mapped to' list inside Keyboard Manager shorcuts

Microsoft PowerToys version
0.61.1
Running as admin

[X] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
PowerToys > Keyboard Manager >Remap a Key or Remap a shortcut > in the Mapped To list there`s no PIPE  " | "

✔ Expected Behavior
Expected a pipe in the list.
❌ Actual Behavior
Pipe not available in the list
Other Software
asadasdasd

What keys do you normally press to get that character?

That's the problem... I don't!
I have a keyboard with an EN-US layout, but I use PT-BR as my main Input Windows language.

I'm sorry. Currently we only support remapping keys that are on the keyboard.
/dup #6976


Camera Zoom Speed

Type
Incorrect behavior
Operating System
Windows
OS Version
windows 10
Bug description
After the last few updates my camera zoom speed resets to default speed. You can check the settings and they are buffed up as I left them, but the physical zoom speed doesn't increase or decrease until the client resets
Screenshots or videos
No response
RuneLite version
RL: 1.10.40
Launcher: 2.7.1
Logs
No response

For sure. I guess I just assumed the "not need to restart client" came from
runelites end. But okily dokily, I know we all like the ease of access so I
wasn't sure. Thanks for the fast response, keep rocking 🤘
On Wed, Oct 9, 2024, 7:59 AM JZomDev @.***> wrote:

The fix is to restart the client which you are already doing.
Jagex's updates in that don't cause a requirement to restart the client
should have you restart the client anyways, they break the camera plugin
often. It is good practice to restart it every update or even everyday to
ensure it's always up to date.
—
Reply to this email directly, view it on GitHub
https://github.com/runelite/runelite/issues/18409#issuecomment-2402257918,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BL6YS52D6YYAD64TIPB6NF3Z2USEJAVCNFSM6AAAAABPUNYULWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBSGI2TOOJRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Red flags see on this message

What is this red flag information about?

Somebody help me


Add ability to download a configuration

It's useful to me to be able to download a config, this creates a zip file with both ini's

That's a nice feature! It may collide with #24, I'll look into it tomorrow.

I created a review in #24.

Will be done in #24


OKX: perpetual swap contracts with USDT as margin

Currently, the symbols fetched for swap contracts on OKX are the ones that use BTC as margin only:
OKX:BTCUSD.P,BTCUSD,USD
It would be useful to fetch symbols that use USDT as margin as well:
OKX:BTCUSDT.P,BTCUSDT,USDT
:pray:

Closing the issue, as both types of contracts are actually included in the same fetched file.


I/O Error when trying to run a benchmark on a FMX Forms project on Windows

If I create a Console application, I can run benchmarks on Windows 32/64 platforms.
However, if I try to create a "Multi-Device Application - Delphi", when I run a benchmark on Windows 32/64 platforms I get this error message:

Project FMXBenchmarkForm.exe raised exception class EInOutError with message 'I/O error 105'.

It seems to fail to initialize the console (displayReporter) as output for the report here:
  if displayReporter.ReportContext(context) and
    ((fileReporter = nil) or fileReporter.ReportContext(context)) then

An I/O Error happens when doing a Writeln without being a console application or having console output allocated.
That is because you did not create a console application - you can however fix it by calling AllocConsole on Windows - for other platforms I don't know the exact function for that.


Remove primer-tables package

This PR removes all code for the unneeded primer-tables package. This was carried over from old Basecoat (rip) code, and is now obsolete.
/cc @primer/ds-core & @pmarsceill because i think he is the original author.

Have added this to our release tracking board, will go out in the next major release.


Set grep tool

Hey there,
first of all. I really enjoy the plugin, thanks for all the effort you have put in. It is truly beautiful!
This is a follow up of #86 .
Users are now able to set their grep_tool and set the complete parameters for their grep_tool.
I was thinking if I should always pass the --vimgrep flag to the tool regardless of the tool. If someone has set g:clap_provider_grep_opts like #86 he would have to change it to pass the --vimgrep flag. What are your thoughts?
Best regards

I don't think we should always pass the --vimgrep flag.

Thanks!


use autosummary instead of autodoc for API reference

@daniel-thom I spent all day figuring out how to properly use sphinx autosummary to produce clean API reference docs. I've implemented it here if you want to give it a go

@daniel-thom I spent all day figuring out how to properly use sphinx autosummary to produce clean API reference docs. I've implemented it here if you want to give it a go

Thanks for the PR. I'm interested to see what this produces. Does it change the API docs or is this really for referencing the APIs within the documentation pages?

Autosummary IMO creates more user friendly docs for the API and the changes to index put them in the side bar under API reference. See the rex example here:
https://nrel.github.io/rex/_autosummary/rex.html


Updating Roslyn packages to 2.0.0

resolves #999
Adds support for C# 7

Because of the package updates, we need to validate that we won't have issues with NGEN.

Ran end-to-end NGEN tests. Clean NGEN runs. Merging.


Express Middleware

Allow easy and automatic basic-auth usage over a range of endpoints with some simple Express middleware.

Thank you, but the jshttp organization only contains low-level modules without any thing like Connect or Express ties, meant to be used to build a middleware like you did.
Express manages a basic auth middleware already in their organization: https://github.com/expressjs/basic-auth-connect
Please feel free to contribute to that repo!


Add Docker task with Artifactory

@barbelity,
In addition to my inline comments, we'll probably need to add an Artifactory Repository flag to the docker  tests. This is because the repository name used by the test will have to match the configured docker registry domain.


Fix Google Drive URL to avoid Virus scan warning

This PR fixes, in the datasets library instead of in every specific dataset, the issue of downloading the Virus scan warning page instead of the actual data file for Google Drive URLs.
Fix #3786.

Thanks for this @albertvillanova!

Once this PR merged into master and until our next datasets library release, you can get this fix by installing our library from the GitHub master branch:
pip install git+https://github.com/huggingface/datasets#egg=datasets

Then, if you had previously tried to load the data and got the checksum error, you should force the redownload of the data (before the fix, you just downloaded and cached the virus scan warning page, instead of the data file):
load_dataset("...", download_mode="force_redownload")

Thanks, that solved a bunch of problems we had downstream!
cf. https://github.com/ElementAI/picard/issues/61


Added a draft for service registry quarkus quickstart

This is the first draft outlining the main steps.
I didn't compile or run any of these locally - it might break checks.
@smccarthy-ie  can you take from here and do any changes needed

@bibryam, thanks for your contribution, it's a great start :)
I can take over and refine the draft some more, and fix up any build issues, etc.
Can you close your PR, and I'll open a fresh one? It will be a lot cleaner than me trying to work in your branch, etc.

Can you close your PR, and I'll open a fresh one?

Closed :D


Allow compressors to be registered with CompressorFactory

Migrated from https://github.com/glencoesoftware/jzarr/pull/4, as suggested by @joshmoore.
This makes some minimal changes to allow compressors other than zlib and blosc to be registered, and adds a corresponding test case. No new compression types are supported here, this is just one way to make the compression types more extensible.
I wouldn't necessarily expect this to be merged as-is, and would be happy to hear other thoughts on how to implement this feature.

@melissalinkert: leaving this out of 0.4.0 based on your final comment, but cc'ing @pedson in case he has ideas. Happy to roll a quick 0.5.0 if it's deemed worth it.


The ape shell command should go to console

Overview
When I feel like aping, I want to just type ape in my bash shell, not ape console.
Specification
Running the ape command by itself goes to console, optionally printing a notice beforehand saying "Run ape -h to see the list of available commands".
The ape console command can still stay for consistency and backwards compatibility.

you could just create an alias yourself, no?

you could just create an alias yourself, no?

what would be the alias though? doing so break the rest of the commands:
alias ape="ape console"

@unparalleled-js also consider that running python and ipython commands by themselves also drop you into a shell, so it's natural for ape to do the same

ah you are right, would need to be something different from ape.
i agree with your take on the bare python command also opening a console.

Let me bring this to request to the Council of Apes.

I think others may add their thoughts, but we are leaning on no. My reason: why not have ape test be the default command? It makes sense too. The Ape framework is many things, the console is only one of them. Using a custom alias (perhaps cape ?) is your best bet.

what would the alias be though?

You can't use a straight alias and have it still accept non-console subcommands, but there is the possibility of redefining ape as a custom function:
ape() {
    if [ $# -eq 0 ]; then
        ape console
    else
        ape "$@"
    fi
}

Of course this is just to facilitate running ape console by default, if you need ape --someflag to still run console then the setup gets a bit more complicated unless you made an alias cape="ape console" as mentioned earlier
Basically like @unparalleled-js said, ape itself is more of a process that launches specific sub-tools than a tool itself
For this reason we have it set so running just ape defaults to printing out configuration and command documentation

Makes sense, I may just call my alias iape then. Feel free to close the issue if you think it's resolved


Rename typo item_planned_payment.xml

Fixes #136

[x] Run the unit tests with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

@abhijitramesh This PR is good to go.


fix esc on tagInput component

Overview
Resolves #1472
The proposed behavior for pressing esc:

On the TagInput Autocomplete, pressing esc will close the dropdown
On the any other TagInput components, pressing esc will do nothing (the same as TextInput and TextArea component)

Screenshots (if applicable)
Documentation

[ ] Updated Typescript types and/or component PropTypes
[ ] Added / modified component docs
[x] Added / modified Storybook stories

Hey @pandurijal! Thanks for the contribution. I was in the middle of typing up a response about some issues I encountered and it looks like your most recent commit resolved them! (and fixed the failing tests - glad it was caught!) Gonna do some additional smoke testing in storybook before I merge it in, but this is looking good now.

Hi @brandongregoryscott!
Well yeah, I thought the issue was from the Downshift component, turns out your approach could fix the issue without having any additional effect on another component(s). So I think I would go with your solution after testing some more things I will push the changes.


Improve ./start local preview to try to use full web app

Currently, ./start uses the Preview app qiskit/documentation, rather than the full web app icr.io/quantum-computing/iqp-channel-docs-dev:latest. That's to simplify authentication because ./start is available to everyone. But the full web app is nicer and better reflects the real thing.
It'd be neat if ./start could auto-detect when it's safe to use the full web app. This might look like seeing if IBM Cloud Registry is set up. Maybe even trying to pull the image. We need to be careful though if it results in the preview getting too slow.

No longer in scope.


STORM-243,Record version and revision information in builds

Patch atteThe effect shown below,
For git project
$ storm version
➜  storm-current  storm version
Running: ... ...
Storm 0.10.0-SNAPSHOT
Subversion https://github.com/caofangkun/apache-storm.git  -r ffba148cc47a92185fa1a5db11f72982de10f106
Branch storm-243
Compiled by caokun on Thu Jan  8 10:47:48 CST 2015
From source with checksum 97e7c942939e3e82dcb854b497991a51
For UI:

@caofangkun It looks like you have fixed most of the issues here.  Do you think it is ready for me to review?

Hi @revans2
Thank you for your patience and advices.
I have fixed the bugs as you mentioned above & unit tests passed.
Please have a review once more.

@caofangkun Overall it looks really good, thanks for doing this.  I have a few comments, mostly to clean things up a bit, or some follow up work.

I've added a couple of comments on storm-core/src/saveVersion.sh.

@caofangkun
The changes look good to me now.  I am still a bit nervous that this will not build on windows, but that can be fixed later.   I would also like the comments by @mnogu addressed.  After that I am +1 on this.
Thanks for the work.

@mnogu
Thanks for your comments.
I have modified  saveVersion.sh use 'git rev-parse HEAD' command to get revision id & remove unused variable 'hostname'.

@revans2
if use bash shell saveVersion.sh, will be differect to run on  all platforms.
So when I come across this:
http://maven.apache.org/guides/plugin/guide-java-plugin-development.html
I'm thinking  use Java Plugin Mojo  may be a good choice for platform-independent.
So please do have a review  once again. Tanks for your patience.
eg:
java -cp  ./storm-core/target/storm-core-0.10.0-SNAPSHOT.jar backtype.storm.utils.VersionInfo
Storm 0.10.0-SNAPSHOT
URL https://github.com/caofangkun/apache-storm.git -r 802272ab1455763d649fdba647f167a3c8c87abd
Branch storm-243
Compiled by caokun on 2015-01-13T04:26Z
From source with checksum 2184521b30e34cbbc5530ff6e9ae02c

Looks great to me. +1.  I'll give it a few days to be sure no one else has any comments.

@caofangkun one small thing, now that I think of it.  It would be nice to change the properties file from core-version-info.properties to storm-core-version-info.properties  This is really minor though, I am still +1 without it.


update webrings

Added myself to webrings..! :)

Looks good, I'll be merging the PR now. Thanks @sampoder for reviewing!


How do I detect code that are not completely same but structrally same?

Is it already supported or planned?
I've read all the readme but didn't find any option about detecting structurally same code.Any help would be grateful.

Hello
Currently it is not supported from the box. jscpd use Rabin-Karp algorithm for duplicates detection and don't use source tree as input for detection. You can try to find other tools for you task, for example jsinspect.


torpedo tests fails in production setup

 [FAILED] Unexpected error:
      <*errors.errorString | 0xc000917b50>:
      failed to get [autopilot] namespace, Err: the server could not find the requested resource (get storageclusters.core.libopenstorage.org)
      {
          s: "failed to get [autopilot] namespace, Err: the server could not find the requested resource (get storageclusters.core.libopenstorage.org)",
      }
  occurred
  In [It] at: /go/src/github.com/portworx/torpedo/pkg/log/log.go:334 @ 02/12/24 09:43:15.357

  Full Stack Trace
    github.com/portworx/torpedo/pkg/log.FailOnError({0x8a77720, 0xc000917b50}, {0x80a0dcc?, 0xc001ce4000?}, {0x0?, 0x6dd7c20?, 0xc000633940?})
    	/go/src/github.com/portworx/torpedo/pkg/log/log.go:334 +0x290
    github.com/portworx/torpedo/tests.processError({0x8a77720?, 0xc000917b50?}, {0x0?, 0x0?, 0x0?})
    	/go/src/github.com/portworx/torpedo/tests/common.go:626 +0x45
    github.com/portworx/torpedo/tests.ValidateContext.func2.1.ValidateVolumes.func1.1()
    	/go/src/github.com/portworx/torpedo/tests/common.go:1075 +0x34e
    github.com/portworx/torpedo/tests.ValidateContext.func2.1.ValidateVolumes.func1()
    	/go/src/github.com/portworx/torpedo/tests/common.go:1043 +0x195
    github.com/portworx/torpedo/tests.ValidateVolumes(...)
    	/go/src/github.com/portworx/torpedo/tests/common.go:1041
    github.com/portworx/torpedo/tests.ValidateContext.func2.1()
    	/go/src/github.com/portworx/torpedo/tests/common.go:685 +0x14d

Cluster Details
IKS 1.28.6 --flavor bx2.4x16 --workers 4
Image:      icr.io/ext/portworx/px-backup:2.6.0'

@trenukarya-px @kshithijiyer-px  Is there any known impact for torpedo tests
cc: @arahamad

Hi @kshithijiyer-px
I've noticed that the tests have been consistently passing for the last two days. We haven't made any modifications from the Jenkins side. If any changes have been made in the Torpedo repository to address the issue, could you please create a release? This way, our Jenkins configuration can always reference that specific release. Currently, it's pointing to the Torpedo master branch, and occasional commits could cause certain tests to fail.

Hey @ambiknai
This was mostly due a code change at the Framework level which we have reverted within a day.

Hi @kshithijiyer-px  I understand there was a fix delivered. Could you please create a release at this point of commit so that I can pick the branch in Jenkins instead of master. and it would be stable

Hi @kshithijiyer-px
Do you see any similar issue in your test run
+ cat px-install.json
{
    "apikey": "****",
    "namespace": "px-torpedo-ns",
    "resource_group": "vpc-e2e-test",
    "clusters": "vpc-jp-tok-mzkwmdu1",
    "storageClassName": "ibmc-vpc-block-5iops-tier"
}

++ pwd -P
+ PWD=/home/jenkins/workspace/Containers-Volumes/pxbackup-torpedo-e2e/src/github.com/IBM/ibm-csi-common
+ ibmcloud resource service-instance-create my-px-backup px-backup px-backup-enterprise jp-tok -p @/home/jenkins/workspace/Containers-Volumes/pxbackup-torpedo-e2e/src/github.com/IBM/ibm-csi-common/px-install.json
Creating service instance my-px-backup in resource group vpc-e2e-test of account IBM as<EMAIL_ADDRESS>OK
Service instance my-px-backup was created.

Name:             my-px-backup
ID:               crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:aacb1b76-b3b9-4294-ab55-7832b2d61a68::
GUID:             aacb1b76-b3b9-4294-ab55-7832b2d61a68
Location:         jp-tok
State:            provisioning
Type:             service_instance
Sub Type:
Allow Cleanup:    false
Locked:           false
Created at:       2024-02-28T08:58:28Z
Updated at:       2024-02-28T08:58:29Z
Last Operation:
                  Status    create in progress
                  Message   Started create instance operation

+ kubectl get nodes
+ awk 'NR==2{print $1}'
+ xargs -I '{}' kubectl label node '{}' px/enabled=false
node/<IP_ADDRESS> labeled
+ sleep 90
++ kubectl describe deployment px-backup -n px-torpedo-ns
++ grep Image:
Error from server (NotFound): namespaces "px-torpedo-ns" not found
+ version=

Hey @ambiknai
I haven't see the issue in any of our runs, from the logs what I see is that the namespace px-torpedo-ns doesn't exist. Can you share the some more details and probably check the logs to see if there is some issue with the parameters you are passing to the px-backup terraform script?

Nothing changed from jenkins configuration. Pasting logs of last successful build
+ cat px-install.json
{
    "apikey": "****",
    "namespace": "px-torpedo-ns",
    "resource_group": "vpc-e2e-test",
    "clusters": "vpc-jp-tok-mzm2mta3",
    "storageClassName": "ibmc-vpc-block-5iops-tier"
}

++ pwd -P
+ PWD=/home/jenkins/workspace/Containers-Volumes/pxbackup-torpedo-e2e/src/github.com/IBM/ibm-csi-common
+ ibmcloud resource service-instance-create my-px-backup px-backup px-backup-enterprise jp-tok -p @/home/jenkins/workspace/Containers-Volumes/pxbackup-torpedo-e2e/src/github.com/IBM/ibm-csi-common/px-install.json
Creating service instance my-px-backup in resource group vpc-e2e-test of account IBM as<EMAIL_ADDRESS>OK
Service instance my-px-backup was created.

Name:             my-px-backup
ID:               crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:ba00898e-7fed-4548-8553-63a9acb86b8e::
GUID:             ba00898e-7fed-4548-8553-63a9acb86b8e
Location:         jp-tok
State:            provisioning
Type:             service_instance
Sub Type:
Allow Cleanup:    false
Locked:           false
Created at:       2024-02-26T08:58:40Z
Updated at:       2024-02-26T08:58:41Z
Last Operation:
                  Status    create in progress
                  Message   Started create instance operation

+ kubectl get nodes
+ awk 'NR==2{print $1}'
+ xargs -I '{}' kubectl label node '{}' px/enabled=false
node/<IP_ADDRESS> labeled
+ sleep 90
++ kubectl describe deployment px-backup -n px-torpedo-ns
++ grep Image:
+ version='    Image:      icr.io/ext/portworx/px-backup:2.6.0'

The error we see is
ibmcloud resource service-instance my-px-backup
Retrieving service instance my-px-backup in resource group vpc-e2e-test under account IBM as<EMAIL_ADDRESS>OK

Name:                  my-px-backup
ID:                    crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:64804d75-5408-4c08-8cd0-c7a585248785::
GUID:                  64804d75-5408-4c08-8cd0-c7a585248785
Location:              jp-tok
Service Name:          px-backup
Service Plan Name:     px-backup-enterprise
Resource Group Name:   vpc-e2e-test
State:                 failed
Type:                  service_instance
Sub Type:
Locked:                false
Created at:            2024-03-04T12:18:06Z
Created by<EMAIL_ADDRESS>Updated at:            2024-03-04T12:18:31Z
Last Operation:
                       Status    create failed
                       Message   Cannot provision px-backup: Message: Cannot get cluster configuration, ID: crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:64804d75-5408-4c08-8cd0-c7a585248785::, Err: Provision [ crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:64804d75-5408-4c08-8cd0-c7a585248785:: ] : Cannot get cloud configuration: Err: Request failed with status code: 500, internal_error: , details:
                                 	ClusterName: vpc-jp-tok-mzc5mty4, Region: jp-tok, OrgID: , SpaceID , AccountID: e242f140687cd68a8e037b26680e0f04
                                 	ServiceID: 3eb2d5a0-24ff-11eb-9437-631d7272fff5, PlanID: 8026f9e7-f908-404f-b2e6-8f61b197eb0f, ResourceGroup: crn:v1:bluemix:public:resource-controller::a/e242f140687cd68a8e037b26680e0f04::resource-group:1938876b2c8941e89a93a26e6103ef6b, ServiceName: px-backup, InstanceID: crn:v1:bluemix:public:px-backup:jp-tok:a/e242f140687cd68a8e037b26680e0f04:64804d75-5408-4c08-8cd0-c7a585248785::

@kshithijiyer-px  could you check this

Update from the webex call:
Backup is not installed, namespace itself is not created.  From the error message it looks like the catalog is not able fetch the clusters this could be due to the API key which we need to pass in the IBM Catalog for px-backup to install px-backup is having some issue.
AI: @ambiknai  to check the API key and try to run the job with a new API key.


Export Canvas.ImageData constructor

node-canvas defines its own ImageData constructor.  Previously it was not exposed by module.exports, but it is since 1.3.0.  I have found this addition helpful, maybe others will too.

Closing because this repo appears to be abandoned


Ability to limit triggering event to ctrl+click and get event details in custom handler functions

Hello,
I needed this functionality for a project. It's quite possible to bind clipboard.js to non-action (so to speak) HTML elements such as s or s but in that case click to copy might not be desirable.
The feature works as follows. You add option ctrl:true to the constructor options:
import Clipboard from 'clipboard'

let clip = new Clipboard('.clip', {
  ctrl: true
})

And now elements with .clipboard CSS class only copy to clipboard if ctrl key was pressed when the element was clicked.

Added Ctr+click option to options { ctrl: true }
Custom handlers can now receive firing event as a second parameter if some logic should be applied based in it's value
ClipboardAction object now contains event as a property

Hey @bmarkovic. I appreciate the pull request but if we're going to support other events besides click, then we need to rethink this implementation and create one that is more flexible to others like keydown, etc.


JetBrains

Add the file
my-aolcc.txt

@theiphoner Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@theiphoner You might miss my previous comment. Please react.


another logo try

👷 Deploy Preview for johare-cv processing.

Name
Link

🔨 Latest commit
20267142492623ff9d46d9c45f026042749ac287

🔍 Latest deploy log
https://app.netlify.com/sites/johare-cv/deploys/65db9e32d37e010009ca415e


Incorrect detection of Windows version

I was trying to run this, and got this error:

My Windows version:

I am definitely meeting the requirement stated.  I altered Capture_IsSupported to simply return TRUE and that prevents the error but the program still doesn't appear to run; I've just hidden the error.
I don't know enough about C++ to be able to print out dwMajorVersion and dwBuildNumber to the command line.  Apparently, adding #include <stdio.h> at the top of the file isn't enough to make printf work.

Hmm, that's strange. You're right, it should work for your Windows version.
stdio.h won't work because this is GUI application, there's no console.
Maybe those version numbers are different for Enterprise edition, not sure.
Can you put following code after RtlGetVersion - that will display message box with version numbers you have:
WCHAR Text[1024];
wsprintfW(Text, L"Major=%d\nMinor=%d\nBuild=%d\n", Version.dwMajorVersion, Version.dwMinorVersion, Version.dwBuildNumber);
MessageBoxW(NULL, Text, L"Version", 0);

---------------------------
Version
---------------------------
Major=0
Minor=19042
Build=2

---------------------------
OK
---------------------------

Did you compile code yourself (for case when initial error message box shows up)? If so, I think you did it as 32-bit code. I don't really support it. RtlGetVersion function declaration will be wrong for 32-bit and it will fill Version structure incorrectly.
There are probably other places where similar issue will happen later.
Basically compile code as 64-bit.
You can check what architecture wcap.exe file is with dumpbin /headers wcap.exe | findstr machine command from VS commandline.

ah that's it.  Thank you.  So, instead of using the Visual Studio 2019 Dev Prompt, I should be using the Visual Studio 2019 x64 Native Tools prompt.  It's so clear and obvious because of the naming, lol.
thank you.

Added extra check in build.cmd so you'll get error now for 32-bit environment.


Rename 'Role' to 'Job title' in contacts table and fix adviser label in interaction form

Ports a couple of small changes from https://github.com/uktrade/data-hub-prototype.

One small thing. The PR is to merge to master. Github seems to default to merge to the default branch. I do this all the time. Updated the PR


LocalProjectMixin before PackitAPIWithUpstreamMixin

Since PackitAPIWithUpstreamMixin uses the LocalProjectMixin we should define it first (probably)
fix #1861

this should fix #1861 , right?

Yes, it should

Aside from those 2 new tests cases, what can we do to prevent this in future?

I don't really know. But when I did the refactoring, I did not create new tests for the new Mixins classes, I just re-used the old tests, but probably a more broader coverage would have been useful.

I think that after this fix and change in inheritance structure, we are less prone to such bugs in the future. Overriding mixins is complicated and tricky due to MRO so inheriting from mixins at the lowest level possible is IMO a way to prevent this.