NULL values and data truncation due to automatic data types conversion

Driver version or file name: php-sqlsrv-5.1.2~preview-1.el7.remi.7.0.x86_64
SQL Server version: Microsoft SQL Server 2016 (SP1-GDR) (KB4019089) - 13.0.4206.0 (X64)
Client operating system: Windows Server 2012 64-bit
PHP version: 7.0
Microsoft ODBC Driver version: 13
We are migrating from FreeTDS to Doctrine PDOSQLSrv or SQLSrv (trying both at the monent) and have encountered the problem with the data truncation of the fields that are not updated.
Our update statements look like
update tbl set field1 = isnull(?, field1), field2 = isnull(?, field2) where id = ?
We have investigated that it is caused by the data type conversion. FreeTDS runs the queries as is, so when you pass the NULL value, NULL is used. However PDOSQLSrv and SQLSrv run queries with sp_prepexec stored procedure, so it is not NULL any more, but a NULL-valued variable.
Unfortunately both libraries convert PHP nulls to char(1) (in documentation https://docs.microsoft.com/en-us/sql/connect/php/default-sql-server-data-types it is said to be varchar(1) but still it doesn't help, I can see char(1) in the Profiler), so when the field is not updated and we pass NULL, it truncates the data.
Full code example:

use Doctrine\DBAL\DriverManager;

include_once __DIR__ . '/vendor/autoload.php';

$connectionOptions = array_merge(
    ['driverClass' => '\Doctrine\DBAL\Driver\PDOSqlsrv\Driver'],
    ['host' => '<IP_ADDRESS>', 'port' => 1433, 'dbname' => 'users', 'user' => '', 'password' => '']
);

try {
    $conn = DriverManager::getConnection($connectionOptions);
} catch (\Exception $e) {
    die($e->getMessage());
}

$userId = 1;
$nick = 'test';

try {
    $result = $conn->executeUpdate(
        'UPDATE users.users SET user_nick = isnull(:nick, user_nick) WHERE user_id = :userId',
        ['nick' => $nick, 'userId' => $userId],
        ['nick' => \PDO::NULL_EMPTY_STRING, 'userId' => \PDO::PARAM_INT]
    );
} catch (\Exception $e) {
    die($e->getMessage());
}

So the question is how to pass null correctly?

hope it's minor bug and you can fix it soon, cause we want to use Microsoft's driver in our new projects.

Hi @atlix ,
This isn't a bug in the driver. See the ISNULL documentation:
https://docs.microsoft.com/en-us/sql/t-sql/functions/isnull-transact-sql:

ISNULL ( check_expression , replacement_value )

Returns the same type as check_expression. If a literal NULL is provided as check_expression, returns the datatype of the replacement_value. If a literal NULL is provided as check_expression and no replacement_value is provided, returns an int.

In other words, your SQL worked fine as long as FreeTDS used the literal NULL for the check_expression. But since you are now using variables via the PHP driver, check_expression is no longer the literal NULL and the return value is of the same type as the variable being passed as the check_expression instead of the replacement_value.
You can observe similar behavior in SQL Server simply by running:
select ISNULL(CAST(null as varchar(1)), 'its just i') as using_isnull, COALESCE(CAST(null as varchar(1)), 'its all there') as using_coalesce
Which returns:

using_isnull
using_coalesce

i
its all there

You need to modify your SQL. I think the easiest change for you may simply be to change your ISNULL functions to COALESCE:
https://docs.microsoft.com/en-us/sql/t-sql/language-elements/coalesce-transact-sql
Regards,
David

Thank you for detailed explain, COALESCE works fine for us.


Allow non-string specification of stores

For compatibility with Arraylake, we would want to expand this type
https://github.com/cubed-dev/cubed/blob/738b70d5578cf9dd68bb36fa813d96ffd0dd7302/cubed/types.py#L21
to allow passing a Zarr Store object (rather than a string), plus optionally a group argument.
We would probably like to call to_zarr like this
from arraylake import Client
client = Client()
repo = client.get_repo("earthmover/foo")

to_zarr(x, store=repo.store, group="sub/group")

The repo.store object is serializable.

Thanks for opening the issue @rabernat.

we would want to expand this type

I'm not sure what the best type signature is here, so probably Any?
I've opened #391 to allow a group argument (in from_zarr too), which should support your use case. I've called it path as that is what Zarr seems to call it, but I notice Dask calls it component. Any thoughts about naming?

I'm not sure what the best type signature is here, so probably Any?

It would be one of the base types from Zarr, e.g. https://github.com/zarr-developers/zarr-python/blob/f80f697c2612cf41c5bdb158a602c1ae8a737e70/zarr/_storage/store.py#L164
(However, these are going to evolve soon with the Zarr V3 refactor.)

I've called it path as that is what Zarr seems to call it, but I notice Dask calls it component

To make it even more fun, Xarray calls it group! 🙃 path is fine.


Ignore test factories in coverage

Ignores test factories in coverage ie.: test files that are under any subfolder __tests__ and end in .factory.ts or .factory.js

Coverage decreased (-0.2%) to 89.424% when pulling a88d686b4e5bad8d219af187b88c561191e631eb on ignore-test-factories-coverage into a8fb9c2cd1a2802aff27c809d95a53a0fec1324b on main.


Japanese Localization

I'm loving Bruno and plan on trying to get my coworkers on board as well.
However, it being English only will definitely be a roadblock.
I know that localization is a huge undertaking, and so I don't expect this to be accomplished anytime soon, but I am making this anyway in hopes that it can become part of the pipeline down the road. At the very least, Japanese documentation would be helpful.

I am a native Japanese speaker and I believe I can contribute to translating the documentation. I will send a pull request when I have time!


tell user to clear application data if they get authorization error

References: #490
Description
Appears that the api doesn't like the user's cookie. The session cookie exists but there is no user data in the db. In this instance the user will have to create a new session by clearing their browsers application data. This is an annoying work around for now.

For contributor use:

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the standards mentioned here.
[ ] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Appears that the api doesn't like the user's cookie. The session cookie exists but there is no user data in the db.

Can you elaborate on this? The way API works is by keeping a database of user session IDs, if the request contains an existing session it's authorized if not it fails. The only time we delete session database on staging is when we manually clear the database otherwise it shouldn't happen (cc @DylanTinianov can you confirm), so it seems weird to me that this error would be shown at any time. Were you able to reproduce the issue?

Appears that the api doesn't like the user's cookie. The session cookie exists but there is no user data in the db.

Can you elaborate on this? The way API works is by keeping a database of user session IDs, if the request contains an existing session it's authorized if not it fails. The only time we delete session database on staging is when we manually clear the database otherwise it shouldn't happen (cc @DylanTinianov can you confirm), so it seems weird to me that this error would be shown at any time. Were you able to reproduce the issue?

I think this is actually caused by force migration being active on backend staging deployments. Disabling this should fix the issue.

I'll close this PR, updating the message to the user isn't helpful.


Allow disable of recent history in "go to file" command

I'd like the ability to disable showing the "recent history" portion of the file list in the go to file command, or at least collapsed so I don't have to visually scan to find the files list.
For me, it quickly becomes both noisey (lots of false matches that I have to visually skip) and incorrect (debugger files, old files, etc).
I find myself clearing the history multiple times daily to limit the noise.  The pattern matching as currently implemented is great, quickly gets me a short list of matching files, and the "recent" list just adds noise.

I suppose there hasn't been any update on this one in the meantime, right? Tried searching a bit, but didn't see anything that could be a solution yet...

+1, really annoying

+1
Really hoping for an update to this. Slows down the workflow of wanting to search current project files, but other projects' files (Recently Opened) are listed first (some times with the same names as files you're looking for in the current project).

+1, having major issues as I have to folders for a current project one for dev efforts and one for technical debt and constantly keep opening the wrong version of a file due to this feature

+1 also.
Can be really counterproductive.

+1 i keep going to the wrong files because of this due to similar filenames under different folders (main.html, component.jsx, style.scss, etc)

I added a new setting search.quickOpen.includeHistory to control this. Default is true.

Verify: if search.quickOpen.includeHistory is configured, typing into Cmd+P will not show any results from the "recently opened" bucket. The list of recently opened is still shown when initially opening quick open or having no search at all.

This will be a nice companion to this feature as well: https://github.com/Microsoft/vscode/pull/55752


Missing documentation on using HealthChecker Problem Daemon

Looking at the documentation it is unclear on how we can use the HealthChecker problem daemon.
For SystemLogMonitor and SystemStatsMonitor there are clear flags (--config.system-stats-monitor and --config.system-log-monitor) which accept configuration files.
What is the proper process for enabling the HealthCheckers? It looks like they are custom plugin monitor, however the documentation lists them as a separate Daemon which is a bit confusing.

In order to enable the HealthCheck, we need to enable it through custom-plugin-monitor. NPD creates a daemon for each of the custom-plugins in order to monitor the system. This is why it is listed as a separate daemon. The Healther checker can be enabled by `--config.custom-plugin-monitor=/path/to/health-checker-docker.json or health-checker-containerd.json.
The health-checker-docker.json is present here

In order to enable the HealthCheck, we need to enable it through custom-plugin-monitor. NPD creates a daemon for each of the custom-plugins in order to monitor the system. This is why it is listed as a separate daemon. The Healther checker can be enabled by `--config.custom-plugin-monitor=/path/to/health-checker-docker.json or health-checker-containerd.json.
The health-checker-docker.json is present here

Thanks @vteratipally - is there any documentation on what this plugin checks?


Security Issue

DO NOT PROVIDE ANY DETAILS HERE. Please privately report to https://github.com/louislam/uptime-kuma/security/advisories/new.
Why need this issue? It is because GitHub Advisory do not send a notification to @louislam, it is a workaround to do so.
Your GitHub Advisory URL:

Your GitHub Advisory URL:

I cannot see any reports in my side, feel free to reopen if it will be available.


eng, fix for disabled jacoco in DPG/Cadl

Enable jacoco for DPG/Cadl lib, with some jacoco.min
In future, autorest.java will not generate pom with jacoco.skip https://github.com/Azure/autorest.java/issues/1979
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

/azp run azure-security-confidentialledger

/azp run java - confidentialledger

/azp run java - purview

/azp run java - purview

/azp run java - confidentialledger


Wrong values logged when using MDLC with TPL Dataflow

When using TPL Dataflow (I'm not blaming it) probably due to high concurrency usage NLog starts messing up the logged mdlc values inside scope.
NLog version: 4.6.7
TPL Dataflow package: System.Threading.Tasks.Dataflow, version 4.9.0
Platform: .Net 4.7.2
Current NLog config (xml or C#, if relevant)
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      throwConfigExceptions="true"
      throwExceptions="true"
      internalLogFile="logs\internal.log"
      internalLogLevel="Trace">
  <variable name="FileLayout"
            value="${longdate} | ${threadid} | ${level} | ${mdlc:item=context-data} | ${message}" />

  <targets async="true">
    <default-target-parameters type="File" layout="${FileLayout}" keepFileOpen="true" concurrentWrites="false" />
    <target name="Main" type="File" fileName="logs\application.log" />
  </targets>

  <targets>
    <target name="ConsoleLogger" type="ColoredConsole" layout="${FileLayout}" detectConsoleAvailable="true" />
  </targets>

  <rules>
    <logger name="*" minlevel="Trace" writeTo="Main, ConsoleLogger" />
  </rules>
</nlog>

Sample C# code:
internal class Input : TaskCompletionSource<string>
    {
        public int Value { get; }

        public Input(int value)
        {
            Value = value;
        }
    }

    class Program
    {
        private static readonly ILogger Logger = LogManager.GetCurrentClassLogger();

        static async Task Main(string[] args)
        {
            var mesh = CreateMesh();

            var computeTasks = Enumerable.Range(1, 3)
                .Select(async i =>
                {
                    using (MappedDiagnosticsLogicalContext.SetScoped("context-data", i))
                    {
                        Logger.Info($"Started processing within context {i}");

                        var input = new Input(i);
                        await mesh.SendAsync(input);
                        var result = await input.Task;

                        Logger.Info($"Finished processing within context {i}");
                    }
                });

            await Task.WhenAll(computeTasks);

            Console.ReadLine();
        }

        private static ITargetBlock<Input> CreateMesh()
        {
            var options = new ExecutionDataflowBlockOptions
            {
                MaxDegreeOfParallelism = DataflowBlockOptions.Unbounded,
                EnsureOrdered = false
            };

            var incrementer = new TransformBlock<Input, (long, Input)>(input =>
            {
                Logger.Info($"Inside incrementer - context: {{{input.Value}}}...");
                return (input.Value + 1, input);
            }, options);

            var toStringConverter = new TransformBlock<(long number, Input input), (string, Input)>(tuple =>
            {
                var (number, input) = tuple;
                Logger.Info($"Inside hashedStringMaker - context: {{{input.Value}}}...");

                return ($">>{number}<<", input);
            }, options);

            var resultProvider = new ActionBlock<(string hash, Input input)>(tuple =>
            {
                var (hash, input) = tuple;
                Logger.Info($"Inside resultProvider - context: {{{input.Value}}}...");
                input.TrySetResult(hash);
            });

            var linkOptions = new DataflowLinkOptions {PropagateCompletion = true};

            incrementer.LinkTo(toStringConverter, linkOptions);
            toStringConverter.LinkTo(resultProvider, linkOptions);

            return DataflowBlock.Encapsulate(incrementer, toStringConverter);
        }
    }

What is the current result?

${longdate}
${threadid}
${level}
${mdlc:item=context-data}
${message}

2019-09-20 15:48:06.2936
1
Info
1
Started processing within context 1

2019-09-20 15:48:06.3916
1
Info
2
Started processing within context 2

2019-09-20 15:48:06.3986
5
Info
1
Inside incrementer - context: {1}...

2019-09-20 15:48:06.3986
1
Info
3
Started processing within context 3

2019-09-20 15:48:06.4126
6
Info
2
Inside incrementer - context: {2}...

2019-09-20 15:48:06.4426
6
Info
2
Inside incrementer - context: {3}...

2019-09-20 15:48:06.4586
7
Info
1
Inside hashedStringMaker - context: {1}...

2019-09-20 15:48:06.4586
6
Info
2
Inside hashedStringMaker - context: {2}...

2019-09-20 15:48:06.4586
7
Info
1
Inside hashedStringMaker - context: {3}...

2019-09-20 15:48:06.4936
6
Info
1
Inside resultProvider - context: {1}...

2019-09-20 15:48:06.5126
6
Info
1
Finished processing within context 1

2019-09-20 15:48:06.5126
6
Info
1
Inside resultProvider - context: {2}...

2019-09-20 15:48:06.5126
6
Info
2
Finished processing within context 2

2019-09-20 15:48:06.5126
6
Info
1
Inside resultProvider - context: {3}...

2019-09-20 15:48:06.5126
6
Info
3
Finished processing within context 3

What is the expected result?

${longdate}
${threadid}
${level}
${mdlc:item=context-data}
${message}

2019-09-20 15:48:06.2936
1
Info
1
Started processing within context 1

2019-09-20 15:48:06.3916
1
Info
2
Started processing within context 2

2019-09-20 15:48:06.3986
5
Info
1
Inside incrementer - context: {1}...

2019-09-20 15:48:06.3986
1
Info
3
Started processing within context 3

2019-09-20 15:48:06.4126
6
Info
2
Inside incrementer - context: {2}...

2019-09-20 15:48:06.4426
6
Info
23
Inside incrementer - context: {3}...

2019-09-20 15:48:06.4586
7
Info
1
Inside hashedStringMaker - context: {1}...

2019-09-20 15:48:06.4586
6
Info
2
Inside hashedStringMaker - context: {2}...

2019-09-20 15:48:06.4586
7
Info
13
Inside hashedStringMaker - context: {3}...

2019-09-20 15:48:06.4936
6
Info
1
Inside resultProvider - context: {1}...

2019-09-20 15:48:06.5126
6
Info
1
Finished processing within context 1

2019-09-20 15:48:06.5126
6
Info
12
Inside resultProvider - context: {2}...

2019-09-20 15:48:06.5126
6
Info
2
Finished processing within context 2

2019-09-20 15:48:06.5126
6
Info
13
Inside resultProvider - context: {3}...

2019-09-20 15:48:06.5126
6
Info
3
Finished processing within context 3

Did you checked the Internal log?

Yes, nothing helpful

Could you try and run this on the targetplatform netcoreapp2.1  ? (MDLC will use AsyncLocal on NetCore)

I can see these are good:
Started processing within context 1 - MDLC = 1
Started processing within context 2 - MDLC = 2
Started processing within context 3 - MDLC = 3
Finished processing within context 1- MDLC = 1
Finished processing within context 2 - MDLC = 2
Finished processing within context 3 - MDLC = 3
So I guess some kind of thread-optimization happens inside (skipping cloning of execution context):
await mesh.SendAsync(input);
NLog makes use of CallContext on net45 (and net472), so I guess you need to investigate if there pitfalls when combining TPL with CallContext.

I can see these are good:
Started processing within context 1 - MDLC = 1
Started processing within context 2 - MDLC = 2
Started processing within context 3 - MDLC = 3
Finished processing within context 1- MDLC = 1
Finished processing within context 2 - MDLC = 2
Finished processing within context 3 - MDLC = 3
So I guess some kind of thread-optimization (skipping cloning of execution context) happens inside:
await mesh.SendAsync(input);
NLog makes use of CallContext on net45 (and net472), so I guess you need to investigate if there are pitfalls when combining TPL with CallContext.

Yeah, tested TPL Dataflow in multiple ways and with other logging frameworks as well. Even tried pure AsyncLocal. Seems to be that TPL Dataflow somehow optimizes away the tasks and messes up ExecutionContext.


Update ValueDeserializer protocol docstring

Describe the bug
The docstring on line 12 is describing the serialization in a KPN way which is incorrect and It should not reflect that. Removing the line is enough

closed by #43


Gradle Setup for com.fima.cardsui

Hi , If I need to use your lib in my app, it shows error in com.fima.cardsui. This library has documentation how to include their lib in gradle. can you please advise?
Thanks.
Jaya

@jayakanthang this library does not contain the com.fima.cardsui project. just the sample project.
it seems you did not setup the lib with the gradle dependency for your project?

Hi, What should I do if I want to include this lib as gradle dependency?
Sent from my iPad

On 12 Jul 2015, at 6:51 pm, Mike Penz<EMAIL_ADDRESS>wrote:
@jayakanthang this library does not contain the com.fima.cardsui project. just the sample project.
it seems you did not setup the lib with the gradle dependency for your project?
—
Reply to this email directly or view it on GitHub.

https://github.com/mikepenz/AboutLibraries#using-maven


where is "Spatial Reference" data in timeseries excel file?

@horsburgh and @sreeder I am implementing to convert data in timeseries excel file into python objects (or, actually, ODM2 objects) using xlwings python package. Based on that, also YODA file can be generated. In your generated YODA file, this spatial reference data below was given. But, when looking into excel file, I can see only "SRSName" data in "Sampling Features" sheet.
In order to get other data for spatial reference, do you use the external interface?
SpatialReferences:
  - &SRSID0001 {SRSCode: "EPSG:4326", SRSName: "WGS84", SRSDescription: "Horizontal component of 3D system. Used by the GPS satellite navigation system and for NATO military geodetic surveying.", SRSLink: "http://www.epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::4326"}

@cdesyoun - this is something that @SRGDamia1 implemented and we didn't change. There is a worksheet in the template that is currently hidden that is called "SpatialReferences". The drop down on the "SamplingFeatures" sheet is populated from that sheet, and when the YODA file is created, the details of the spatial reference are copied into the YODA file from the SpatialReferences worksheet.  It's hidden because there are only a couple of valid options and so I think @SRGDamia1 didn't want people to have to think about those details (or chance them getting them wrong).

Yes, exactly what Jeff said.
On 2/23/2016 10:31 AM, Jeff Horsburgh wrote:

@cdesyoun https://github.com/cdesyoun - this is something that
@SRGDamia1 https://github.com/SRGDamia1 implemented and we didn't
change. There is a worksheet in the template that is currently hidden
that is called "SpatialReferences". The drop down on the
"SamplingFeatures" sheet is populated from that sheet, and when the
YODA file is created, the details of the spatial reference are copied
into the YODA file from the SpatialReferences worksheet. It's hidden
because there are only a couple of valid options and so I think
@SRGDamia1 https://github.com/SRGDamia1 didn't want people to have
to think about those details (or chance them getting them wrong).
—
Reply to this email directly or view it on GitHub
https://github.com/ODM2/YODA-File/issues/52#issuecomment-187744667.

--
Sara Geleskie Damiano
Technician
Stroud Water Research Center
970 Spencer Road
Avondale, PA 19311
(610) 268-2153 x 248

@horsburgh and @SRGDamia1 Thank you so much for letting me know about hidden sheet list. I see several hidden sheet list on that timeseries excel file.


[CAMEL-3552] Added PDF component to camel.

OK so this component ended up being quite bigger than I expected initially. This is my first component so feel free to review and suggest any modifications.
Basically this component supports following operations:

create (creates new pdf document)
append (appends provided text to provided pdf document)
extractText (extracts text from provided pdf document)

Also it has two text writing strategies:

lineTermination (default) - takes provided text, splits it by line termination(\n) and writes these lines to pdf document regardless line fits in the document or not. With this strategy its users responsibility to provide text that will fit in the pdf document.
autoFormatting - this strategy is a little more complicated. It takes provided text and splits it by words.  Then it builds lines with a maximum amount of words that fit in the line.

This component supports only default PDFBox fonts (which are ASCII).

@nkukhar thanks a lot I just pushed the code to master branch.

Do you mind closing this PR and if you have more work on the way, then please create a new PR based on the latest code from master branch


[PE-D][Tester B] Foreign country numbers not accepted

Vendors/Applicants can have overseas mobile numbers. '+' sign should be allowed.

Labels: severity.Medium type.FunctionalityBug
original: Saezenn/ped#10

currently a feature flaw, can put in future enhancements

Resolved by #238.


[WIP] Accommodation page

@b-ishan could you create your own PRs in the future? Also, provide us edit access to your repo so that if needed, we can push changes to your branch and then merge them. :)

I am still a little new to GitHub. Will try to help y'all out as much as
possible. I try to do whatever Abhilash bhaiya asks me.
Regards,
Ishan Bansal
On 19-Oct-2017 14:47, "Rohitt Vashishtha"<EMAIL_ADDRESS>wrote:

@b-ishan https://github.com/b-ishan could you create your own PRs in
the future? Also, provide us edit access to your repo so that if needed, we
can push changes to your branch and then merge them. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/crux-bphc/fest-manager/pull/241#issuecomment-337849756,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcCJCeeb7eMvYY9_MMd-sIvCaJP3xbr9ks5stxPEgaJpZM4P-xYQ
.


CLI refactor: introduce rerun rrd <compare|print|compact> subscommand

Title.
$ rerun rrd --help
Usage: rerun rrd <COMMAND>

Commands:
  compare  Compares the data between 2 .rrd files, returning a successful shell exit code if they match
  print    Print the contents of an .rrd or .rbl file
  compact  Compacts the contents of an .rrd or .rbl file and writes the result to a new file
  help     Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help

DNM: Requires #6860

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

@rerun-bot full-check


[Feature Request] Having binaries downloadable from releases page

I'm convinced that your project will have more traction if you propose directly some built binaries ready to be downloaded in the releases section.
It gives me the opportunity to ask you which architecture is it suited for? Will it only work on macOS or could we built it for Linux also?
In such case an AppImage will be wonderful 😄 OK yes I'm a Linux user 😋

I just published a release with some binaries. Can you try it and let me know if it runs?

Sooooo cool! AppImage works like a charm! Many thanks


WHAT IS THIS!

Literally couple days a go worked fine and now its boosting by itself my CPU cant stream cant record!

And without OBS?
If you record with scrcpy --record file.mp4 for example.

Pretty normal
On Wed, Mar 16, 2022, 10:47 Romain Vimont @.***> wrote:

And without OBS?
If you record with scrcpy --record file.mp4 for example.
—
Reply to this email directly, view it on GitHub
https://github.com/Genymobile/scrcpy/issues/3119#issuecomment-1068928614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMGD3WRZJTXTS3FODON5MDVAGUZJANCNFSM5Q3JEE7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Switch license check to use unshare/mounted env

In order to use native file operations, switch the license check to
use the unshare and mounted environment.
Fixes #170
Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

/hold

/hold cancel


TaxonomyPicker Component does not handle large termsets well

When loading 1000+ terms the recursive DOM node creator logic runs at what seems to be like O(2N) and results in a 42 second (blocking) runtime on my well speced workstation.

I've got a client reporting the same problem... I will have to do some tests and could say if I am facing similar issues

I started experimenting with ways to improve this. So far I have concluded a few things.

Javascript being single threaded still makes things like looping over "large" datasets painful
jQuery does A LOT of DOM manipulation when doing things like .append

My current solution tries to unblock the browser and notifies the user about the progress.
Right now I have not cleaned it up enough to warrant a pull request so I figured I might get some feedback on the general idea by posting some code here.
The general idea is to replace the way that the node tree is built with a more async way.
Thougts? Ping @jansenbe
                var nodeList = $('.cam-taxpicker-treenode-ul');
                var that = this;

                nodeList.append('

');

                var buildTermSetTree = function (terms, index, isRootNode) {
                    for (var i = 0; i < terms.length - 1; i++) {
                        createNode(terms, i, isRootNode);
                    };
                }

                var createNode = function (terms, index, isRootNode) {
                    setTimeout(function () {
                        var tHtml = terms[index].toHtmlLabel();

                        //handle children here as well, see prev implementation above

                        tHtml += '

';

                        nodeList.append(tHtml);

                        $('#termCounter').text("(" + (index + 1) + "/" + (terms.length - 1) + " laddade)");

                        if (terms.length - 1 === index + 1) {
                            $('.cam-taxpicker-treenode-title').click(Function.createDelegate(that, that.termNodeClicked));
                            $('.cam-taxpicker-treenode-title').dblclick(Function.createDelegate(that, that.termNodeDoubleClicked));
                            that._dlgSelectButton.click(Function.createDelegate(that, that.dialogSelectButtonClicked));
                            that._dlgCloseButton.click(Function.createDelegate(that, that.dialogCancelClicked));
                            that._dlgOkButton.click(Function.createDelegate(that, that.dialogOkClicked));
                            that._dlgCancelButton.click(Function.createDelegate(that, that.dialogCancelClicked));
                            that._dlgAddNewTermButton.click(Function.createDelegate(that, that.dialogNewTermClicked));

                        }
                    }, 1 + index * 2);
                }

                buildTermSetTree(this.TermSet.Terms, true);

Closed after merging Patrick's PR.


Integrate suggestions from Luca about quality metrics

Codecov Report

Merging #290 (eb2dcfe) into master (3c60c87) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head eb2dcfe differs from pull request most recent head 72099bf. Consider uploading reports for the commit 72099bf to get more accurate results

@@           Coverage Diff           @@
##           master     #290   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          46       46
  Lines        1226     1226
  Branches      167      167
=======================================
  Hits         1197     1197
  Misses         12       12
  Partials       17       17

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3c60c87...72099bf. Read the comment docs.


Relay: support fragments on query

Describe the bug
It's possible I'm holding it wrong but it appears relay pagination on any of the root collection queries will fail, even with the recent node additions.
This is because Fragments on the root query object don't work. This means relay usePaginationFragments using @refetchable  can't be placed on root query.
Given the data architecture in the docker compose, suppose we wanted to page through a list of all blog posts in the system, relay would recommend something like:
const query = usePreloadedQuery<BlogPostsQuery>(graphql`
  query BlogPostsQuery($filter: BlogPostFilter, $first: Int, $after: Cursor) {
    ...blogPosts_query
  }
`, queryRef)
// ...

// ...
const { data } = usePaginationFragment<BlogPostsQuery, BlogPostsList_query>(
    graphql`
      fragment BlogPostsList_query on Query {
        blogPostCollection(
          filter: $filter
          first: $first
          after: $after
          orderBy: { createdAt: DescNullsLast }
        )
          @connection(key: "BlogPostList_blogPostCollection")
          @refetchable(queryName: "BlogPostsQuery") {
          edges {
            node {
              id
              title
              createdAt
            }
          }
        }
      }
    `,
    query
  );

This won't work as pg_graphql doesn't support fragments on the query object. You can confirm this in GraphiQL with the following:
query {
  ...blogPosts_query
}

fragment blogPosts_query on Query {
  blogPostCollection(first:2) {
    edges
    {
      node {
        id
        title
        createdAt
      }
    }
  }
}

Reports
{
  "code": "XX000",
  "details": null,
  "hint": null,
  "message": "only Selections are supported"
}

Workaround
Since you can add @refetchable to nodes you can modify the above to use a fragment under a blog node and it will work correctly. This will of course only page the posts for that particular blog. In many cases there is an acceptable "root node" to attach @refetchable and perform pagination on child collections. The argument does however get tricky as we climb the relationships. If we wanted a pageable list of blogs we'd have to fetch them by author nodes, and then the question becomes how do we page through authors.
Additional context
More details on relay pagination and the @refetchable directive can be found here: https://relay.dev/docs/guided-tour/list-data/rendering-connections/

thanks, this was an uncaught regression
Resolved in #272 + added tests for fragments on Query and Mutation types
If you send me your project ref/s I'll roll the fix out to your project asap
otherwise the fix will be out on the platform in a main release NLT the 12th

Absolutely, I'm working against qtrzyzcvkevkmayocdka at the moment

Seeing an error ... A reboot cleared that up but worth adding a note to the upgrade instructions

thanks, it isn't supposed to need a reboot so I'll double check that

Glad you fixed the above because the schemaConfig.nodeInterfaceIdField breaks pagination on the relay side. I added a note to https://github.com/supabase/pg_graphql/issues/209 for folks who end up looking here for answers

One perhaps minor quality of life enhancement; it'd be nice if the Filter inputs supported the nodeId field

@kav tracking at #274 and #275


chore: centauri update

i weird thing to use nix flake here, appeard during last couple month
warning: Git tree '/home/dz/github.com/ComposableFi/composable' is dirty
error:
       … while calling the 'derivationStrict' builtin

         at /builtin/derivation.nix:9:12: (source not available)

       … while evaluating derivation 'devnet-xc-cosmos-fresh'
         whose name attribute is located at /nix/store/z6w242l49pbrdawkz5vdhfxh2mvsj36c-source/pkgs/stdenv/generic/make-derivation.nix:311:7

       … while evaluating attribute 'text' of derivation 'devnet-xc-cosmos-fresh'

         at /nix/store/z6w242l49pbrdawkz5vdhfxh2mvsj36c-source/pkgs/build-support/trivial-builders/default.nix:148:16:

          147|     runCommand name
          148|       { inherit text executable checkPhase allowSubstitutes preferLocalBuild;
             |                ^
          149|         passAsFile = [ "text" ];

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: function 'outputs' called without required argument 'nixpkgs'

       at /nix/store/nf026zrw1r24cba0isi0s0x6pf4nwlkq-source/flake.nix:7:13:

            6|
            7|   outputs = {
             |             ^
            8|     self,

that is sbt-derivation. how it possibe?

it is impossible, but happens,
file is
{
  description = "Nix interop for sbt projects";

  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
  inputs.flake-utils.url = "github:numtide/flake-utils";

  outputs = {
    self,
    nixpkgs,
    flake-utils,
  }:
    {


fix the issue that chart axis's min/max value can't be zero

This PR fixes #3538
noticed this today while testing the feature and found this old issue.
Root cause: we are not differentiating 0 and undefined when processing the options.
Fix: check for undefined explicitly.
With the fix:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 47.998%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
15005

Relevant Lines:
29640

💛  - Coveralls


Problem with checkmark outline icon inside Switches

I'm finding a problem with the Switches. When I try to create one with the checkbox icon inside, the icons are not displaying correct. On the demo site, I'm referring to the "Switch with icon"
http://coreui.io/demo/Angular_Demo/#/components/switches
The HTML looks like so:
                       <input type="checkbox" class="switch-input" checked>
With this the checkmark doesnt display and instead shows "#xf00c". If I change the switch-label to the following, the checkmark then correctly appears. I'm not sure what this special character difference is though. Could I get an explanation on this?
                      <input type="checkbox" class="switch-input" checked>

fixed


Allow parent .. and self . references in absolute paths

I use ammonite-ops not in the shell but as regular lib in a scala project. It took me quite a while to understand how to add a parent dir segment to an absolute path.
First try which feel naturally
cwd / ".." / "server" / "build" / "install" / "server"
throws an
InvalidSegment: [..] on absolute path #387
In order to get it right I'm required to construct a RelPath("..") object, which does not smoothly fit to the DSL:
cwd / RelPath("..") / "server" / "build" / "install" / "server"
Wouldn't it be possible to allow the following paths:
cwd / ".." / "server" / "build" / "install" / "server"

val externallyDefinedRelPath = "install/server"
cwd / ".." / "server" / "build" / externallyDefinedRelPath

The latter one is useful if I need to construct paths with externally (not under my control) defined path segments.
With the current behavior I would need to pre-process all path segments I receive from others before I could use it. Which means split into segments and create RelPath objects for special segments like "." and "..".  This would not be worth the effort. The j.n.f.Path would deal with it like expected but its just not so nice like the ammonite dsl.

For ".." what you really want is the up operator.
If you are taking paths from outside which include multiple segments and possible ..s, the correct thing to do is to use the Path(...) or RelPath(...) constructors. You don't need to split it, just call RelPath on the whole thing:
haoyi-Ammonite@ RelPath("abc/def")
res0: RelPath = 'abc/'def
haoyi-Ammonite@ RelPath("abc/def/../ghi/./jkl")
res1: RelPath = 'abc/'ghi/'jkl

I'll add the up suggestion to the error message, and make the absolute path error message better, but the behavior overall is probably not going to change. It's an explicit goal to provide some level of inconvenience when you want to deal with "raw" paths, making you wrap them in Path or RelPath if you want to parse them, and making sure none of them "leak into" your Ammonite program unless you explicitly want them


Jf mvn deploy Unable to locate server on WIndows

Describe the bug
Jfrog Client, when performing jf mvn deploy, fails to locate private artifactory server when attempting to deploy artifacts.
This is occurring on Windows Platforms and Docker Containers.
I have a separate Linux Container that deploys to the same Artifactory instance with jfrog cli, but has no issue with deploying artifacts at all.

I have a need to build artifacts on both linux and windows distributions, so I can't simply just drop windows.

Current behavior
ace\test\test\target\test-2.0.3-14.jar.
 Skipping deployment of remaining artifacts (if any) and build info.
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.lambda$deploy$4 (ModuleParallelDeployHelper.java:57)
    at java.lang.Iterable.forEach (Iterable.java:75)
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.deploy (ModuleParallelDeployHelper.java:44)
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.lambda$null$1 (ModuleParallelDeployHelper.java:34)
    at java.util.concurrent.CompletableFuture$AsyncRun.run (CompletableFuture.java:1736)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:834)
Caused by: java.io.IOException: JFrog service failed. Received 504: <TITLE>Unknown Host</TITLE>

Unknown Host

Description: Unable to locate the server named "REDACTED" --- the server doe
s not have a DNS entry.  Perhaps there is a misspelling in the server name, or the server no longer exists.  Double-c
heck the name and try again.

    at org.jfrog.build.extractor.clientConfiguration.client.JFrogService.throwException (JFrogService.java:49)
    at org.jfrog.build.extractor.clientConfiguration.client.artifactory.services.Upload.handleUnsuccessfulResponse (U
pload.java:59)
    at org.jfrog.build.extractor.clientConfiguration.client.JFrogService.execute (JFrogService.java:121)
    at org.jfrog.build.extractor.clientConfiguration.client.artifactory.services.Upload.execute (Upload.java:77)
    at org.jfrog.build.extractor.clientConfiguration.client.artifactory.ArtifactoryManager.upload (ArtifactoryManager
.java:284)
    at org.jfrog.build.extractor.clientConfiguration.client.artifactory.ArtifactoryManager.upload (ArtifactoryManager
.java:279)
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.lambda$deploy$4 (ModuleParallelDeployHelper.java:46)
    at java.lang.Iterable.forEach (Iterable.java:75)
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.deploy (ModuleParallelDeployHelper.java:44)
    at org.jfrog.build.extractor.ModuleParallelDeployHelper.lambda$null$1 (ModuleParallelDeployHelper.java:34)
    at java.util.concurrent.CompletableFuture$AsyncRun.run (CompletableFuture.java:1736)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    at java.lang.Thread.run (Thread.java:834)```

### Reproduction steps

Running jfrog client and maven builds on a custom windows docker image
- base image is dotnet/framework/runtime3.5-windowsservercore-ltsc2019

Attempted running on multiple jfrog verisons
- 2.53.2
- 2.58.0
- 2.59.0

Maven version 3.8.5
JAVA Version
- openjdk 11.0.10 2021-01-19 LTS
- OpenJDK Runtime Environment Zulu11.45+27-CA (build 11.0.10+9-LTS)
- OpenJDK 64-Bit Server VM Zulu11.45+27-CA (build 11.0.10+9-LTS, mixed mode)

Using Chocolatey to install:
- jfrog-cli-v2-jf --version=2.59.0
- maven --version=3.8.5

Utilizing a private artifactory server
- has a remote proxy of frog-releases

Environment Variable:
$env:JFROG_CLI_RELASES_REPO="artifactory/remote-jfrog-releases"

jf c add artifactory --url https://REDACTED --user user --password "blah" -interactive=false

jf mvn-config --server-id-deploy artifactory --repo-deploy-releases feature-repo --repo-deploy-snapshots snapshot-repo

jf mvn deploy --build-name test --build-number 777

### Expected behavior

Jfrog client deploys maven build artifacts to privary artifactory instance

### JFrog CLI version

2.59.0

### Operating system type and version

Windows Docker Image: dotnet/framework/runtime3.5-windowsservercore-ltsc2019

### JFrog Artifactory version

7.84.14

### JFrog Xray version

_No response_

Additionally, for more details.
The maven build alone completes just fine when using jf mvn install and sources maven dependencies for the build just fine.
The issue only occurs when using jf mvn deploy and the jfrog client tool attempts to deploy artifacts

Further testing steps.
I found that nslookup artifactory.< domain > was not resolving.
So I tried adding DNS to my daemon.json and restarting my dockerd service.
While that allowed the running windows container execution of nslookup artifactory.< domain > to lookup and return the proper IP address.
This had no affect on the execution of jf mvn deploy --build-name test --build-number 777
I am still experiencing:
Caused by: java.io.IOException: JFrog service failed. Received 504: <TITLE>Unknown Host</TITLE>

Unknown Host

Description: Unable to locate the server named "REDACTED" --- the server doe
s not have a DNS entry.  Perhaps there is a misspelling in the server name, or the server no longer exists.  Double-c
heck the name and try again.

Does anyone have any insight into the above error at all?

Update
I have tried adding the ip and hostname to the C:\Windows\System32\drivers\etc\hosts
Add-Content -Path C:\Windows\System32\drivers\etc\hosts -V alue 'XXX.XXX.XXX.XXX      hostname.domain'
and including "-Djdk.net.hosts.file=C:\Windows\System32\drivers\etc\hosts"  in my execution of:jf mvn deploy --build-name test --build-number 777 "-Djdk.net.hosts.file=C:\Windows\System32\drivers\etc\hosts"
Which gets the execution further along, but not it fails with an unkownHostException on my proxy's hostname
If I add the proxy hostname.domain and IP to my hosts file, it turns right back around to an unknown host on the artifactory address


Change in html file.

PR of issue no #10

sorry to say this @abuharish02 but there are few conflicts in the files you pushed could you please rectify them


[Announcements] Code release

Hit the subscribe button on the right of this issue if you wish to be notified of the code release. Please do not reply to this issue to not spam other subscribers. Please do not contact us to ask for early-access to the code.

subscribe

Looking forward to the code of PixLoc!!!

subscribee

subscribe

subscribe

Subscribe

Subscribe

subscribe

Hi all, we have now finally released the code! This has taken far more time than we expected, sincere apologies for the delay. We have worked hard to turn our research code into a nice Python package with significantly improved usability, accuracy, and scalability. It integrates well with COLMAP and hloc and is highly configurable to fit many use case. I am very proud of this release and excited to see what the community will do of it. Please give it a try and let us know if you run into any trouble or need advice!


Fix sender of issue notifications

It is the FROM field in mailer configuration that needs be used,
not the USER field, which is for authentication.
Migrated from https://github.com/gogits/gogs/pull/3616

LGTM, but needs to be rebased.

Sorry, I'm confused, should this target develop or master branch ?

according to consensus in Gitter, it should go into master :slightly_smiling_face:

@bkcsoft  :scream: is possible to change target or only with new PR?

The others that has been merged targeted develop, so leave it at that :)

It was a bogus base (master) -- now based on develop branch, should be fine.

LGTM

Please reopen this against master

LGTM


Add missing doc links and update broken ones

First pass at docs.
There'll be another pass converting them all to permalinks, but this gets the
final destinations in place so that I can do a single perma pass after we get
the OK on the permalinks themselves.
All links should be correct as of this change.

Current dependencies on/for this PR:

main

PR #133   👈

This comment was auto-generated by Graphite.


gha poc 1

Summary of Changes

details of changes go here
include link(s) to any Confluence pages with additional detail

Associated JIRA Ticket

IN-nnn - title of ticket

Associated Pull Request(s)

IN-nnn - title of PR
link(s) to additional related PR(s)

Testing
Test Plan

test procedure details (include link to Confluence page with test plan, if applicable)
mention of any new unit/functional/etc. tests that have been added

-tf=plan -chdir=sample_instance -workspace=dev -var-file=env/dev.tfvars

-tf=plan -chdir=sample_bucket -backend-config=backend/dev.tfbackend


[FLINK-16180][runtime] Replace the nullable vertexExecution in ScheduledUnit with a non-null executionVertexId

What is the purpose of the change
ScheduledUnit#vertexExecution is nullable but ProgrammedSlotProvider requires it to be non-null to work. This makes ProgrammedSlotProvider not able to be used by new scheduler tests since vertexExecution is never set in the new scheduler code path. It blocks us from reworking tests which are based legacy scheduling to base on the new scheduler.
Thus I opened this PR to replace the nullable vertexExecution with a non-null executionVertexID.
It also naturally fixes 2 other issues:

The log printed in SchedulerImpl#allocateSlotInternal(...) can be broken since the vertexExecution can be null.
an NPE issue reported in FLINK-16145.

Brief change log
See commits.
Verifying this change
This change is already covered by existing tests, such as ExecutionTests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

In f58f5c06cad5f4fd0da9ef1d81e37d1a458ba190 it is not clear to me what issue you are trying to solve. The commit message mentions that it fixes potential NPEs but does not specify where exactly. Moreover, I think that a commit of that size warrants a separate ticket.

@GJL

In f58f5c0 it is not clear to me what issue you are trying to solve. The commit message mentions that it fixes potential NPEs but does not specify where exactly. Moreover, I think that a commit of that size is beyond the scope of a hotfix and warrants a separate ticket.

The NPE issue happens because getID() is not mocked in SchedulerTestUtils. So that several test would break with the change on {{ScheduledUnit}}.
And you are right that we can have a separate PR to ticket to remove this mockito dependency in SchedulerTestUtils. I will open a new ticket for it.

@zhuzhurk Ok, let me know if you have opened a new ticket. How important is it to get rid of mockito now? I  am asking because subclassing ExecutionVertex so that we can control the return value of getPreferredLocations() does not look particularly clean either.

@GJL FLINK-16300 is opened to rework SchedulerTestUtils to create a test Execution and the PR is #11230.
It's not very urgent to get rid of mockito. However, in my previous experience, we can leave it as is if we do not touch it, but should not continuing make changes to those mockito usages.
I'm not pretty sure whether creating testing subclasses is not clean. But I can see in Flink we have already doing it like this for tests, e.g. TestingSlotPoolImpl.

I would recommend for now to introduce only minimal changes to fix the NPE. The usage of mockito is discouraged for good reasons. However, by introducing TestExecutionVertex with the setter setPreferredLocationFutures(), we are conceptually not doing anything different than what a Mockito Spy (or partial mock) does. Partial mocks have problems such as that we can easily violate the contract of the class. In this particular example, the results of getPreferredLocationsBasedOnInputs() and getPreferredLocationBasedOnState() will not be aligned with the result of our mocked method (getPreferredLocations()).
Here are more opinions that I found about the Subclass To Test pattern:

https://wiki.c2.com/?SubclassToTestAntiPattern
https://medium.com/android-testing-daily/subclass-and-override-1492f0564b35

Let me know what you think.

The problem is that we are unable to manipulate the state of the ExecutionVertex easily such that getPreferredLocations() returns the desired result

That's true and subclassing is just to solve this kind of problems. From the references you list, I find most people also think so. It's not perfect but better than no way. And Flink already uses it for the testing of SlotPoolImpl with TestingSlotPoolImpl.
Another problem of SchedulerTestUtils which currently uses mockito is that it only mocks what are needed by existing tests. So future tests may encounter NPE issue again when it uses these utils, e.g. getResourceProfile().
If you think it's better to have a minimal fix (i.e. using mockito to mock ExecutionVertex#getID()) first to unblock higher priority tasks, we can do it first and discuss #11230 later.
WDYT?

Thanks for the reviewing @GJL .
Will merge it once travis gives green.


Wrapping around for a single stack? (As opposed to wrapping around for an entire space)

I saw @dominiklohmann 's commands here for cycling through every window in a space, including stacks, with wraparound. I'm wondering if it's possible to simply add wraparound to the default behavior of stacks. That is, cycling through a stack as you can do by default except that when you reach the end (or the beginning) it cycles to the first (or last)? (I'm not familiar with queries/jq/xargs)

Just use yabai -m window --focus stack.next || yabai -m window --focus stack.first instead for cycling stacks to do the wraparound manually.
The || is a logical or, i.e., if the first command fails the latter is executed.

That works perfectly! Thank you


is.array and is.object bug

var a = {
"No":["1000","200"],
"Date":"22/12/2012"
}
is.array(a["No"])
// --> true
is.object(a["No"])
// -->true   .....this should be false. because a["No"] is array ...

In Javascript, everything except primitives (strings, numbers, bool, null, undefined) is an object, so basically, an Array IS an object.


create better test cases/data

Create better archives/storage examples for testing. Preferably use the DIFF_HASH algorithm, as it will allow to copy over the files to temporary directories, without messing with the diff method.
Better test cases are espesially needed for the following tests:

pybacked.backup.backup tests

Fixed by #96


How do you use pdfjs-dist with Angular for Internet Explorer?

Configuration:

Web browser and its version: Internet Explorer 11
Operating system and its version: Windows
PDF.js version: v2.6.347

Steps to reproduce the problem:

npm install --save pdfjs-dist
import * as pdfjs from 'pdfjs-dist'
pdfjs: any
use pdfjs functions like getDocument() etc

What is the expected behavior?
PDF should load.
What went wrong?
This will work perfectly fine for Chrome, but in IE will get errors like "Object action not supported". Which is expected I guess because it's not using the es5 files. In the readme it says "please refer to the es5 folder", but have no documentations on actually how to make the package resolve to es5 folder only.
I tried to modify the pdfjs-dist in the node modules to resolve to the es5 folder by running a script during build to replace contents under /build with /es5/build, or modifying webpack.js to read the es5 folder instead, but at the end when I load my component I got an error saying Weakset undefined or something other weird errors that I have no idea how to debug.
I also tried manually imported the scripts dynamically and append it by using document.createElement('script') and document.getElementsByTagName("head")[0].appendChild(sc). This method will work the best, but performance wise it's very bad because it needs to wait for the scripts to finish loading before you can actually do anything.
What is the proper way to use this package for IE??

What is the proper way to use this package for IE??

Please note that as mentioned in the FAQ, IE 11 is now essentially unsupported; see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support (emphasis mine):

While the library and the default viewer should still work in IE 11/Edge (non-Chromium-based) for the time being, some functionality/features may not be available and the performance will be worse compared to modern browsers. However, this support will be dropped after stable version 2.6.347.


Configurable instances

Allow the user to set export variable values for a scene in the dock.
Use case, i have a generic enemy scene which operates on resources for stats, visuals, etc... I'd like to be able to store enemy configurations in the dock instead of having to configure them every time i add an instance to the scene.

That might be complicated to implement, but I'll see 🤔
In the meantime you can use inherited scenes.

Implemented in d271a351ef6fa30b374707eb6b55c03b6c12f3f8
https://github.com/KoBeWi/Godot-Instance-Dock/assets/2223172/d0808e70-af1c-4ab4-8955-66c74d10177e


Revert Unsupported Commands back to Deprecated for 0.4.0 release

This reverts the commit that moved the original ember-cli-deploy commands to unsupported for users coming to this project from the original ember-cli-deploy package. It also lists a few original ember-deploy commands as deprecated also.
@achambers thanks for deprecating and then un-supporting in 2 commits. Made this an easy item to knock out this morning.
This closes issue #72

@danshultz  Don't thank me yet. We need the original commands to actually work, which they don't currently with that DeprecatedCommand object. You'll see that it's overwriting the run command.

Ha, thanks, I'll wire that up now....
womp womp womp on my :)

I added a couple of achambers/ember-cli-deploy specific commands there
too. Do we need to somehow replicate them, for the time being, for people
that might have upgraded from my repo to this one?
I am currently adding a post install warning to users installing v 0.4.0+
that look to have the config from my repo set ( it sure how else to tell if
they are upgrading from my repo). But I'm not sure that's enough. We don't
really any to break their experience either.
On Tue, 3 Mar 2015 at 12:56 Dan Shultz<EMAIL_ADDRESS>wrote:

Ha, thanks, I'll wire that up now....
womp womp womp on my :)
--
Reply to this email directly or view it on GitHub
https://github.com/ember-cli/ember-cli-deploy/pull/74#issuecomment-76940286
.

@achambers I'm using your readme still here --> https://www.npmjs.com/package/ember-cli-deploy although if you have your old repo, maybe put it up as ember-cli-deploy-old or something so I can have that as reference.
At the moment, I'm cross checking your readme to update the commands from the original ember-cli-deploy (deploy activate and deploy:versions). I'll have a PR momentarily with some added comments for you to review

I think I renamed it to ember-cli-deploy-original.
I'm about to take lunch shortly so can chat about things on slack if you
want.
On Tue, 3 Mar 2015 at 13:10 Dan Shultz<EMAIL_ADDRESS>wrote:

@achambers https://github.com/achambers I'm using your readme still
here --> https://www.npmjs.com/package/ember-cli-deploy although if you
have your old repo, maybe put it up as ember-cli-deploy-old or something so
I can have that as reference.
At the moment, I'm cross checking your readme to update the commands from
the original ember-cli-deploy (deploy activate and deploy:versions). I'll
have a PR momentarily with some added comments for you to review
--
Reply to this email directly or view it on GitHub
https://github.com/ember-cli/ember-cli-deploy/pull/74#issuecomment-76942201
.

I should be around we can chat in slack - couple of questions this PR opens up...

Users who update will need to install the ember-deploy-s3 plugin as it looks to be that deploying to s3 was included in the original ember-cli-deploy package.
Users will most likely have https://github.com/achambers/ember-cli-deploy-redis-index-adapter installed. We'll need to verify that it still works with 0.4.0 if we are aiming not to break them.

I figure we might handle that in the upgrade notes? If we are however breaking those users, should we leave the ember deploy:versions and ember activate commands as "unsupported"?

Yo @danshultz .  Where does this PR currently sit? Is this good to go for 0.4.0?

This PR is working in its entirety.
This PR re-enables 'deploy: index', 'deploy: assets'  and adds support for 'deploy: versions' and 'activate' which provides command compatibility with previous versions of ember deploy and ember cli deploy.
@lukemelia mentioned removing the deprecation of the deploy: index and deploy: asset command but thinking it through, we did want to remove these commands in favor of using 'deploy' which does the build and deploying all assets and the index.
I'm out at the moment but if others can chime in on their opinions I can make any changes to this PR today. Otherwise I think this is ok to merge unless anyone thinks we should do something different.

My primary concern here is that I don't think deploy:activate should be deprecated, and certainly not before we have another way for someone to deploy without immediately activating the new version. @achambers @danshultz Agree/disagree?

Ah, I see the confusion. deploy: activate is not deprecated but the bare 'ember activate' is. This was a command from 0.6.0

Ah, got it. In that case, +1 to merge.


Add gleamgrammar

Hi @pokey
Thanks for all your work on cursorless! It's literally saved my career.
I'm hoping to add support for the gleam programming language. I followed the readme for adding a new tree-sitter grammar here. I believe I have the correct set of changes; however, I was unable to get this to install and run locally for the life of me. (I got emscripten installed but actually generating the wasm stuff is being stubborn) I see from prior issues that this can be tricky to set up so I'm hoping you can run the yarn install and give things a quick test for me since you (probably) have a working dev environment.
Thanks!

shipped in parse-tree extension version 0.30.0


Add unit tests for Jobs perspective filter creation

Adding test coverage for filters conditions generation in Jobs perspective.
The added test methods and accompanying code re-factoring in the Presenter class are aligned with the approach taken for Process Instances and Tasks perspectives (e.g DataSetProcessInstanceWithVariablesListPresenter.java).

@bsremac thanks!


Atom constructor is using two function calls

Consider the example
type T
    A x y

main =
    x = T.A 1 2

The T.A 1 2 expression is  executed in two steps:

Unresolved symbol A is resolved to a method T.A (method A with a self parameter T) https://github.com/enso-org/enso/blob/ab159238ddb27a3a2d1ea228b2dd23a4e19694f6/engine/runtime/src/main/java/org/enso/interpreter/runtime/callable/atom/AtomConstructor.java#L176-L185
Method T.A then returns a function with two arguments x and y that constructs the A instance https://github.com/enso-org/enso/blob/ab159238ddb27a3a2d1ea228b2dd23a4e19694f6/engine/runtime/src/main/java/org/enso/interpreter/runtime/callable/atom/AtomConstructor.java#L162-L173

Issue
When instrumented, the T.A 1 2 expression returns the underlying method call A self. Instead, we want to report a method A x y as it looks from the user (and the suggestion database) perspective.

Do we have a test case? Or a test case which is close in behavior to the requested one?

When I save t.enso with content:
type T
    A x y

main = T.A 1 2

and save an enso_insight.js with:
insight.on('enter', (ctx, frame) => {
  print(`${ctx.name} at ${ctx.source.name}:${ctx.line} variables: ${Object.keys(frame)}`);
}, {
  roots : true
});

then running JAVA_OPTS=-Dpolyglot.insight=enso_insight.js enso --run t.enso produces following tracing output:
t::t::main at t.enso:4 variables:
T.A at t.enso:2 variables: x,y

e.g. there are two function/method invocations. One is main on line four and one is the constructor on line two.

I put in the description two functions that are created in order to build an instance. The instrument only sees the first one T.A

I am supposed to run this test to reproduce the problem.

I see the failure:
sbt:runtime-with-instruments> testOnly *RuntimeServerTest -- -z constructors
[info] - should send method pointer updates of partially applied constructors *** FAILED ***
[info]   List(Response(Some(41a6e6de-4439-4623-84c3-9fcf290fd170),PushContextResponse(963843f9-e196-4968-b3bb-b0a5e85e7b43)), Response(None,ExpressionUpdates(963843f9-e196-4968-b3bb-b0a5e85e7b43,Set(ExpressionUpdate(00000000-0000-00aa-449f-8119429d4528,Some(Standard.Builtins.Main.Function),Some(MethodCall(MethodPointer(Enso_Test.Test.Main,Enso_Test.Test.Main.T,A),Vector())),Vector(ExecutionTime(0)),false,true,Value(None))))), Response(None,ExpressionUpdates(963843f9-e196-4968-b3bb-b0a5e85e7b43,Set(ExpressionUpdate(00000000-0000-00ab-6949-6fba1ffb4eac,Some(Enso_Test.Test.Main.T),None,Vector(ExecutionTime(0)),false,true,Value(None))))), Response(None,ExecutionComplete(963843f9-e196-4968-b3bb-b0a5e85e7b43)), Response(None,BackgroundJobsStartedNotification())) did not contain the same elements as List(Response(None,BackgroundJobsStartedNotification()), Response(Some(41a6e6de-4439-4623-84c3-9fcf290fd170),PushContextResponse(963843f9-e196-4968-b3bb-b0a5e85e7b43)), Response(None,ExpressionUpdates(963843f9-e196-4968-b3bb-b0a5e85e7b43,Set(ExpressionUpdate(00000000-0000-00aa-449f-8119429d4528,Some(Standard.Builtins.Main.Function),Some(MethodCall(MethodPointer(Enso_Test.Test.Main,Enso_Test.Test.Main.T,A),Vector(1))),Vector(ExecutionTime(0)),false,true,Value(None))))), Response(None,ExpressionUpdates(963843f9-e196-4968-b3bb-b0a5e85e7b43,Set(ExpressionUpdate(00000000-0000-00ab-6949-6fba1ffb4eac,Some(Enso_Test.Test.Main.T),Some(MethodCall(MethodPointer(Enso_Test.Test.Main,Enso_Test.Test.Main.T,A),Vector())),Vector(ExecutionTime(0)),false,true,Value(None))))), Response(None,ExecutionComplete(963843f9-e196-4968-b3bb-b0a5e85e7b43))) (RuntimeServerTest.scala:855)

time to debug it.

Thinking about the issue more, I believe we are trying to tackle it from a wrong angle. What's @Frizi's request? When there is a partially applied function, then we want to know what arguments have been applied.
However that is not information about "a call" that has happened, but about a "future call" - we have function value and the IDE needs to know what to do with it. Right?

That mean (in my opinion) that ProgramExecutionSupport.scala needs to do following when composing sendExpressionUpdate:

when the value.getType is Standard.Builtins.Main.Function
accompany the information with a MethodPointer to the function definition
use (value.value : runtime.Function).getSchema() to obtain hasPreApplied array and send it to the IDE somehow

Superseded by #6957


scripts to reproduce the results in paper

Hi, thanks for your awesome work.
According to the code in this repo, you perform 3-stages training: detection, tracking, tracking-plus-mask, right? Could you please provide the scripts (with specific hyper-parameters, e.g., batch size) to reproduce the results shown in your paper?

@wangjk666 Hi, yep, the whole training can be divided into three stages: object detection pre-training, box-level tracking training (SOT-MOT), and mask-level tracking training (VOS-MOTS).
In fact, we already provided scripts in train.md to reproduce our results. By default, Unicorn is trained using 16 GPUs (2 nodes with 8 GPUs). So please use the Multiple-node Training commands. The batch size given in the train.md is just what we adopted.

Ok, thanks a lot for your reply.
Have a good day :)

BTW, several links that you shared to download BDD100K dataset are inaccessible,
e.g., "https://bdd-data-storage-release.s3.us-west-2.amazonaws.com/bdd100k/2021/bdd100k_ins_seg_labels_trainval.zip"

@wangjk666 Hi, the data can also be downloaded from the web browser. The site is https://bdd-data.berkeley.edu/portal.html#download

Hi, I am trying to reproduce the results of the box-level tracking training (as mentioned above), however, it seems that the program got stuck in the dataset building, i.e., after "creating index... index created!", there was no update. I wonder whether you have encountered this problem, or do you have any suggestions?

@wangjk666 Hi, it does need some time to load training data. From my experience, it may take 1-5 minutes depending on the computing power of your CPU. Please try waiting for a while. If it does not work, please determine which dataset causes the stuck.


Publish BOM

See https://s01.oss.sonatype.org/content/repositories/releases/org/shakespeareframework/bom/


Windows paths beginning with \?\ open in separate tab when opened from the integrated terminal

Related to https://github.com/microsoft/vscode/pull/95147
When alt-clicking paths beginning with \\?\ in the integrated terminal, they will open in a separate tab from those opened without the prefix.
E.g.
cd %userprofile%
mkdir foo && cd foo
echo bar > baz
echo %userprofile%\foo\baz VS \\?\%userprofile%\foo\baz

these two paths will open in separate tabs despite being the same file.
In addition, some extensions not expecting paths to contain \\?\ (namely, rust-analyzer v0.2.135) will crash when one opens a file in this way.

/duplicate https://github.com/microsoft/vscode/issues/12448

@bpasero support was just added in the terminal https://github.com/microsoft/vscode/issues/94961


Compile SLSC Switch configuration to compiled data cluster

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Compile the SLSC Switch configuration to the compiled data cluster added in cb4ec4d4bf56746fc2726a875d596bd8e70137eb.
This does not compile down FIFO indices for status channels, however it makes it clear where this would be done.
Why should this Pull Request be merged?
We need a way to send data to the engine for further development.
What testing has been done?
Set the ActionVIOnCompile to show its front panel when called, and confirmed that the data shown in the compiled control matched the expected.

[ ]  Pull the output cluster outside the case structure, but everything else looks good.

Opting to delete it entirely, since it is not needed.


Publicly shareable map URL

Generate a URL to the map that can be viewed anonymously, but not edited.

I propose that we add a "Share" button in the header. Clicking on that would open a dropdown, revealing a url that can be easily copied. For the copy to clipboard, I recommend using https://github.com/wsmd/use-clipboard-copy. If a developer can get the basic functionality in, I'd be glad to do a style pass.


Jolokia support

Elassandra version: elassandra-<IP_ADDRESS>
JVM version: 1.8.0_131
OS version: Ubuntu 16.04
Description of the problem including expected versus actual behavior:
Cannot use Jolokia with elassandra due to jar hell error when starting up elassandra.
Steps to reproduce:

Put Jolokia.jar in ${CASSANDRA_HOME}/lib
Start Elassandra
It'll fail with the errors shown below.

Provide logs (if relevant):
	at org.elasticsearch.plugins.PluginsService.loadBundles(PluginsService.java:421)
	at org.elasticsearch.plugins.PluginsService.<init>(PluginsService.java:115)
	at org.elasticsearch.node.Node.<init>(Node.java:161)
	at org.elasticsearch.node.Node.<init>(Node.java:143)
	at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:153)
	at org.apache.cassandra.service.ElassandraDaemon.setup(ElassandraDaemon.java:339)
	at org.apache.cassandra.service.ElassandraDaemon.activate(ElassandraDaemon.java:143)
	at org.apache.cassandra.service.ElassandraDaemon.main(ElassandraDaemon.java:432)
Caused by: java.lang.IllegalStateException: jar hell!
class: org.json.simple.ItemList
jar1: /opt/elassandra/elassandra-<IP_ADDRESS>/lib/jolokia-jvm-1.3.7-agent.jar
jar2: /opt/elassandra/elassandra-<IP_ADDRESS>/lib/json-simple-1.1.jar

Hi,
For code quality insurance, elasticsearch use jarHell to ensure that the classpath does not contains several copies of the same class, potentially in different version that could cause unexpected results depending ont the class loading order.
Here, jolokia-jvm-1.3.7-agent.jar contains a class org.json.simple.ItemList already available in json-simple-1.1.jar. Jokolia should remove this class from its jar and have a dependency to json-simple (or at least rename its version of org.json.simple.ItemList).
Thanks.

understood. thank you for the explanation. I have submitted an issue ticket to Jolokia side instead.


Async Jobs fail to callback (or restart?) with error on unexpected child process exit

Async jobs are handled in a child process by bull. If the child process exits unexpectedly, such as with SIGABRT (presumably due to out-of-memory exception), the job is marked as failed with the appropriate error, however no callback is made, meaning that the client server is never notified of the job failure.
Additionally, it appears that jobs that fail in this manner might not be restarting properly.
In the case of ARS, this means that the job is left marked as 'running' indefinitely.

Mistakenly closed, reopening

Fix merged+deployed, closing issue.

Reopening as cases such as SIGABRT still do not callback correctly

Moving to on hold / non-critical as the situations where this arise would appear to be exceedingly rare.

@tokebe Do you know how this can be reproduced, the webpage from your original comment gives a 404 and process.abort is apparently not allowed in a child process?

No, I currently don't have a means of reproducing this. Possibly worth just leaving (or even closing) this issue, as it is evidently very rare and hard to debug.

Closing as this issue is extremely rare and hard to reproduce/debug, while other issues are much higher priority.


Function for JobCompleted servicebus message

Description
We need a function listening for a ServiceBus message called JobCompleted that should fetch relevant data from SQL based on the JobId in the message.
The function's task should be to create new ServiceBus message called ResultReadyForConversion that should consist of:
{
	"JobId": "{Id from job in SQL}",
	"SnapshotId": "{Id from Snapshot in SQL}",
	"ResultId": "{Id from Result in SQL}",
	"JobType": "{JobType enum from SQL}",
	"ProcessType": "{ProcessType from Job in SQL}",
	"ProcessVariant": "{ProcessVariant from Job in SQL}",
	"Resolution": "{Resolution from Job in SQL}",
	"ResultPath": "{Path from JobResult in SQL}",
	"Grouping": "{Grouping from Result in SQL}",
	"FromDate": "{FromDate from Snapshot in SQL}",
	"ToDate": "{ToDate from Snapshot in SQL}"
}

The  ResultReadyForConversion message should be published to the internal ServiceBus.
ResultReadyForConversion message should be consumed in #348
Acceptance Criteria:

Function is created which is triggered by JobCompleted ServiceBus message.
Function publishes ResultReadyForConversion ServiceBus message with data from SQL based on JobId from JobCompleted message.

Should ResultPath be ResultPaths and contain a list of ResultPath.
Are we missing receiver_MarketParticipant.marketRole.type in the object


Your RubyGems version (<IP_ADDRESS>) has a bug that prevents required_ruby_version from working for Bundler

Description
i am trying to install react native and give many errors for two days.please help me to fix my errors
I tried to install everythings are explained here 'https://reactnative.dev/docs/environment-setup?guide=native' but at least when i run init project gives me error

error Your RubyGems version (<IP_ADDRESS>) has a bug that prevents required_ruby_versionfrom working for Bundler. Any scripts that usegem install bundlerwill break as soon as Bundler drops support for your Ruby version. Please upgrade RubyGems to avoid future breakage and silence this warning by runninggem update --system 3.2.3Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /Users/apple/Desktop/template/vendor/bundle/ruby/2.6.0/gems/ffi-1.15.5/ext/ffi_c /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby -I /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0 -r ./siteconf20230508-4891-11u18l.rb extconf.rb --enable-system-libffi checking for ffi_prep_closure_loc() in -lffi... no checking for ffi_prep_closure_loc() in -llibffi... no checking for ffi_prep_closure_loc() in -llibffi-8... no system libffi is not usable *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers.  Check the mkmf.log file for more details.  You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/$(RUBY_BASE_NAME) --with-ffi_c-dir --without-ffi_c-dir --with-ffi_c-include --without-ffi_c-include=${ffi_c-dir}/include --with-ffi_c-lib --without-ffi_c-lib=${ffi_c-dir}/lib --enable-system-libffi --with-libffi-config --without-libffi-config --with-pkg-config --without-pkg-config --with-ffilib --without-ffilib --with-libffilib --without-libffilib --with-libffi-8lib --without-libffi-8lib To see why this extension failed to compile, please check the mkmf.log which can be found here: /Users/apple/Desktop/template/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-21/2.6.0/ffi-1.15.5/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /Users/apple/Desktop/template/vendor/bundle/ruby/2.6.0/gems/ffi-1.15.5 for inspection. Results logged to /Users/apple/Desktop/template/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-21/2.6.0/ffi-1.15.5/gem_make.out /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:99:inrun' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/ext_conf_builder.rb:47:in block in build' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/tempfile.rb:295:in open' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/ext_conf_builder.rb:29:in build' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:185:in block in build_extension' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/monitor.rb:235:in mon_synchronize' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:181:in build_extension' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:229:in block in build_extensions' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:226:in each' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/ext/builder.rb:226:in build_extensions' /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/installer.rb:830:in build_extensions' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/rubygems_gem_installer.rb:72:in build_extensions' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/rubygems_gem_installer.rb:28:in install' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/source/rubygems.rb:198:in install' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/installer/gem_installer.rb:54:in install' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/installer/gem_installer.rb:16:in install_from_spec' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/installer/parallel_installer.rb:156:in do_install' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/installer/parallel_installer.rb:147:in block in worker_pool' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/worker.rb:62:in apply_func' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/worker.rb:57:in block in process_queue' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/worker.rb:54:in loop' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/worker.rb:54:in process_queue' /Users/apple/.gem/ruby/2.6.0/gems/bundler-2.4.12/lib/bundler/worker.rb:90:in block (2 levels) in create_threads' An error occurred while installing ffi (1.15.5), and Bundler cannot continue. In Gemfile: cocoapods was resolved to 1.12.1, which depends on cocoapods-core was resolved to 1.12.1, which depends on typhoeus was resolved to 1.4.0, which depends on ethon was resolved to 0.16.0, which depends on ffi error Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS. Error: Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS. at createFromTemplate (/Users/apple/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/commands/init/init.js:131:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.initialize [as func] (/Users/apple/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/commands/init/init.js:184:3) at async Command.handleAction (/Users/apple/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/index.js:106:9)`
After this error created a folder with enesial react native codes but does not run at all

**My macbook pro mid 2015 **

React Native Version
0.71
latest version (i run react-native@latest)
Output of npx react-native info
error: unknown command 'info'
(Did you mean init?)

Tried to update rubygem but

Steps to reproduce
these things make problem
cocopods
bundle install
ruby
Snack, code example, screenshot, or link to a repository
just run simple command in terminal
npx react-native@latest init AwesomeProject

Errors when installing cocoapods with gem
Fixed
sudo xcodebuild -license accept
ruby -rrbconfig -e 'puts RbConfig::CONFIG["rubyhdrdir"]'
Need to install 'libffi' and 'libffi-dev'
Fixed
install port at first from here
sudo port install libffi
OR try with brew
brew install libffi
Installing xcodeproj 1.22.0 error
Fixed
I had this same error on macOS Monterey 12.6.2 with Xcode 13.4, Xcode 14.0.1 and Xcode 14.2 installed. Changing the default Xcode (Xcode / Preferences / Locations - "Command Line Tools:) from the latest (14.2) to 13.4 and trying again was successful. With 14.2 as the default: sudo gem install cocoapods -v 1.11.2 => #fail sudo gem install cocoapods => #fail (different error message) After changing to 13.4 as the default: sudo gem install cocoapods -v 1.11.2 => success, and pod --version => 1.11.2
Install Gcc
I had this issue today. install GCC prior to executing bundle install
installing ffi 1.15.5 with native extensions building native extensions with: '--enable-system-libffi'
Fixed
bundle config --local build.ffi --with-cflags=-Wno-error=implicit-function-declaration
bundle install
i think we can comment --enable-system-libffi from bundle config file in ~/.bundle/config

That's a duplicate of https://github.com/facebook/react-native/issues/37183

That's a duplicate of #37183
there is not perfect and complete soulution for this issue there...

This steps work for me perfectly to create react native project without error
1- npx react-native init testproject --skip-install -—npm
2- cd testproject
3- npm install or yearn install
4- cd ios
5- bundle config --local build.ffi --with-cflags=-Wno-error=implicit-function-declaration
6- bundle install
7- bundle exec pod install

This steps work for me perfectly to create react native project without error
1- npx react-native init testproject --skip-install -—npm
2- cd testproject
3- npm install or yearn install
4- cd ios
5- bundle config --local build.ffi --with-cflags=-Wno-error=implicit-function-declaration
6- bundle install
7- bundle exec pod install
Chek https://github.com/facebook/react-native/issues/37301 more information


ShellTreeView: Drag & Drop-Images look crippled using Win7

Since switching to Windows 7, the Drag and Drop-Images in the ShellTreeView look crippled:

However, we have to rewrite those codes anyways to have the new, larger Drag'n'Drop-Images introduced with Windows Vista...

Solved with Issue #13


Feat/add randomized benchmarking

This pull request includes Clifford operators, randomized benchmarking, and new quantum circuit manipulation tools. Before merging the pull request, the get_num_qubits function in pull request #26 should be added to get_clifford_operator and the quantum gate parameters from pull request #24 should be added to the new quantum_gate functions.
Fixes #29.

This pull request also fixes #38.


ui-variable to set the tree view line height

This theme is really great!
Would it be possible to add a ui-variable or a setting to decrease the line height in the tree view? There's a lot of whitespace between the lines which renders the tree view less useful than it could be.

I think this issue belongs on atom/one-light-ui actually!

Ouch, you're right, thanks for the hint!


vg images link is invalid,and

Hello，vg images link is invalid. Could you  tell me how to download it?

@Silentssss
Hello, we provide the  torrent file  to download VG data by thunder(迅雷) or other platforms.
This torrent link includes all the files of VG data and you can only download the  images.zip and images2.zip used in our model, and merge all image file into image fold.

@Silentssss
你好，partImagenet 是一个单独的数据集，具体请参考该链接.

感谢您的回复，我已获取到谷歌网盘权限，已经下载到了


general clean up of ui, moved js and css in to files under ui folder

did some general clean up on the front end. created a ui folder and moved all css and js in there
also added local versions of jquery and d3, located in ui/js/vendor
updated all html files to use newly created files

Thanks! Looks good to me.

Found an issue with other architectures https://github.com/adrianco/spigo/issues/5


Combine docker tests and publish steps

This will allow testing of the same image that is published
by using image: localhost:5000/sut in a compose file.
Change-type: patch
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>

@balena-ci I self-certify!


Chrome scrollbar disappearing

Having a scrollbar issue on websites with SVGInjector on Chrome (Mac & Windows). Occasionally the scrollbar disappears as soon as a page loads, and reappears scrolling down. Happens on pages where SVGInjector is being used. Removing SVGInjector plugin resolves the issue. The issue appears on all websites we know that has SVGInjector (Both versions 1 & 2).
Any idea what might be causing this?
URL for testing: https://sandbox.elemisthemes.com/test/
Screencasts for demonstration:
https://user-images.githubusercontent.com/608547/146539023-0322a9b4-1b81-44f2-a106-0abe06b44755.mov
https://user-images.githubusercontent.com/608547/146539057-b570c99b-0d7a-4451-9315-d9416f1ff964.mov

I think thats neither a bug of svg-injector nor any other js, html or css on the page.. its a setting that controls if the browser will always render scrollbars, or only on demand..
on macOS the os  controls this behaviour. Attched you find a screenshot of the preferences menu:

@flobacher Already have this setting as Always. Also as mentioned before the issue occurs on Windows Chrome as well, here's a screencast from Windows:
https://user-images.githubusercontent.com/8955300/146879606-b4bd512f-083d-4c9b-9a37-1ce8007726d8.mp4

@flobacher Already have this setting as Always. Also as mentioned before the issue occurs on Windows Chrome as well, here's a screencast from Windows:
https://user-images.githubusercontent.com/608547/146879791-aac8d9b2-0a60-4890-a8a4-ecb7bea11816.mp4

@elemis I justed tried on mac os catalina in latest stable chrome (96) and safari (15.2) with the "show always" scrollbar setting and I always see scrollbars when navigating betwenn project2 and pricing sandbox.elemisthemes.com/test.. cannot think of any possible way svg-injector could be the reason for this behavior... might it be some other js on the page or even some chrome extension?


Cryptomatte Metadata names from Blender still not fully supported

Hi there,
This is a follow-up ticket on the Metadata naming issue. Basically, when Nuke imports the Layers, it replaces certain characters with an underscore, but does not update the metadata that comes with it. This is known and handled partially in the other report.
The problem is that Nuke replaces much more than just dots. Actually it seems that only alphanumeric digits plus underscores and dashes are ok. The fact that the default view layer name in Blender is View Layer, which Nuke turns into View_Layer, doesn't exactly help. To fix this, I suggest changing the def _legal_nuke_layer_name to the code below:
def _legal_nuke_layer_name(name):
    """ Blender produces channels with certain characters in the name, which Nuke
    changes to "_". We have to make sure we handle Cryptomattes
    that are built this way. Doing this by only allowing alphanumeric
    output plus dash and underscores
    """
    return "".join([x if x.lower() in 'abcdefghijklmnopqrstuvwxyz1234567890_-' else '_' for x in name])

This reverses the logic. Instead of stripping out illegal characters, it allows the legal ones. We tested this internally and it proved to work for our cases.

I have opened a pull request for easier merge

Thanks for that, @aliasguru. Sorry it's taken so long to get to this.


I18n module locale extraction is broken

readTranslation doesn't consider the relativeness of the path:
file.split("/").slice(3);

Same applies to the uploadTranslations in the crowdin.js there we again using split and slice, which is again wrong.

Same here:
let getLocaleFromPath = function(url)
{
  let locale = url.split(path.sep).slice(1).shift();
  return locales.includes(locale) ? locale : null;
};

again in i18n


[plugin-prisma/relay] Error in full select mode when not selecting anything from node

When you have defined a prisma node with full select mode (select: {}) and then have defined a t.prismaConnection for this node, queries throw an error when nothing from node is selected: The select statement for type X must not be empty.
Sample query that fails:
query {
  myPrismaConnection {
    totalCount
    edges {
      cursor
    }
  }
}

Some ideas:

Don't run the resolver defined in t.prismaConnection at all, when no fields from node are selected. I don't know if this is possible, there might be other side-effects that I am not aware of right now (e.g. you have to load nodes in order to calculate the cursor).
Always add the cursor field, defined in t.prismaConnection to the selection set
Always add the id field, defined in t.prismaNode to the selection set

This should be fixed in the latest release, let me know if you have an more issues after upgrading!

The query no longer throws errors, but only the id is selected instead. Thanks again for the quick fix :)

Slight clarification here, the selection for this case is now the cursor field (or fields in case the cursor is a compound index).  This will give us enough information to calculate cursors and pageInfo.


umzug.up({to: '...'}) runs all pending migrations instead of only those from the current state to the given name

According to the readme:

It is also possible to pass the name of a migration in order to just run the migrations from the current state to the passed migration name.
umzug.up({ to: '20141101203500-task' }).then(function (migrations) {});

However, this doesn't appear to work as described. Using umzug 1.6.0, when I pass an options object like {to: '201510301204-add-index'}, umzug runs all pending migrations, not just the migrations between the current state and<PHONE_NUMBER>04-add-index. It also runs all pending migrations if I pass a completely bogus migration name like {to: 'bogus'}.
I peeked at the unit tests to see if they held any clues, but passing an options object to up() doesn't seem to be tested. Does this feature actually exist?

It seems that the feature has been implemented before v1.6.0, so it exists. It is implemented in umzug._findMigrationsUntilMatch. There is even tests for umzug.up and umzug.down with name 'when to option is passed' in files test/index/up.test.js and test/index/down.test.js.
In a week, I'll try to figure out how is it working and check if there is a bug or not.

@jukkah I sense a good amount of interest in this project?! I'm excited

https://github.com/sequelize/umzug/blob/master/test/index/up.test.js#L77-L105 @rgrove

Hmm. If those tests are passing, then I guess I can't explain the behavior I was seeing. I couldn't get the to option to limit my migrations no matter what I tried. In any event, I ended up not using MySQL for this project after all, so it's a moot point for me now.
Thanks for the help!

I found one potential problem.
Lets say we have migrations 1-migration, 2-migration, and 3-migration. If 1-migration is executed, calling umzug.up({to: '1-migration'}) executes all the pending migrations because pending migrations doesn't contain 1-migration. Also, calling umzug.up({to: 'bogus'}) does the same.
I think, in these cases no migrations should be executed. It would be nice to log something like 'Migration 1-migration has already been executed. Aborting...' and 'Migration bogus not found. Aborting...'.
@rgrove This explains your bogus example but not your original problem. The only solution I can see is that you tried to remigrate to an already migrated point.

@jukkah Thanks for investigating! I definitely saw this while trying to remigrate to an already migrated point, but my memory is hazy on whether I also tried reproducing the issue from a clean state. I think the issue you fixed is probably what I was seeing though.


Change installation section

It's much better to install gulp-ng-config in our package.json.
npm install gulp-ng-config is syntax for global installation.

npm install gulp-ng-config is syntax for global installation.

I wouldn't say it's a global installation unless it has -g, but more so a local installation that won't be tracked & managed by the package file

@ajwhite Ok.

I don't think you should necessarily dismiss it, just think we should use --save-dev if we're going to add it :+1:

--save-dev for me is not a good option.
Main purpose / goal of gulp-ng-config is too have different configuration for development and production environment.
For me correct flag should be: --save and need to add explanation, why plugin use --save flag.
What do you think ?

I suppose that leaves us to a different interpretation of --save-dev. To me, devDependencies are dependencies that you use for your development and building of the project. Whereas regular dependences would be the actual node_modules that your application will use and require as part of the application codebase.
This is not a dependency, it's a devDependency for preparing and building the application. The application itself does not use this, therefor it is not a dependency. By counter logic, that would mean that gulp should also be your dependency and not a devDependency.
As their docs state

Install gulp in your project devDependencies

https://github.com/gulpjs/gulp/blob/master/docs/getting-started.md

Ok, I am agree with your comment. I have different point of view, but never mind.


[AutoPR sql/resource-manager] [DO NOT MERGE] Add DatabaseVulnerabilityAssessments swagger

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3275

Can one of the admins verify this patch?

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2138