vep_or_lookup_vep failure due to different row types

Hi, I got the following error when running vep_or_lookup_vep with gnomAD reference. It looks like the public gnomAD site table and the current Hail's VEP output have different row types. Is there any workaround?
Code:
import hail as hl
from gnomad.utils.vep import vep_or_lookup_vep
from gnomad.resources.grch38.gnomad import public_release
ht = hl.read_table("gs://path/to/my/table.ht")
gnomad_ht = public_release("genomes").versions["3.1.2"].ht()
ht = vep_or_lookup_vep(ht, gnomad_ht)

Error log:
Welcome to
     __  __     <>__
    / /_/ /__  __/ /
   / __  / _ `/ / /
  /_/ /_/\_,_/_/_/   version 0.2.97-937922d7f46c
LOGGING: writing to /home/hail/hail-20220829-2015-0.2.97-937922d7f46c.log
Traceback (most recent call last):
  File "/tmp/ccdff56e83c24577aded8c147ecdd87d/annotate_vep.py", line 101, in <module>
    main(args)
  File "/tmp/ccdff56e83c24577aded8c147ecdd87d/annotate_vep.py", line 40, in main
    ht = vep_or_lookup_vep(ht, gnomad_ht)
  File "/tmp/ccdff56e83c24577aded8c147ecdd87d/pyscripts_a3_5gmef.zip/gnomad/utils/vep.py", line 230, in vep_or_lookup_vep
  File "<decorator-gen-1036>", line 2, in union
  File "/opt/conda/default/lib/python3.8/site-packages/hail/typecheck/check.py", line 577, in wrapper
    return __original_func(*args_, **kwargs_)
  File "/opt/conda/default/lib/python3.8/site-packages/hail/table.py", line 2124, in union
    raise ValueError(f"'union': table {i} has a different row type.\n"
ValueError: 'union': table 0 has a different row type.

Thanks!
Masa

This it likely related to the issue this PR should fix https://github.com/broadinstitute/gnomad_methods/pull/439

Thanks @jkgoodrich! I think now we should drop colocated_variants too.

What version of VEP is your cluster running? gnomAD v3.1.2 is used v101 and the default when starting a cluster with --vep GRCh38 is 95 I think. Also, rather than use the sites HT (which we exclude the colocated_variants from for release) we have run VEP 101 on the context HT which will be used by default if you don't supply a reference.
Start a cluster with:
hailctl dataproc start cluster_name --worker-machine-type=n1-highmem-8 --worker-boot-disk-size=200 --preemptible-worker-boot-disk-size=200 --metadata=VEP_CONFIG_PATH=/vep_data/vep-gcloud.json,VEP_CONFIG_URI=file:///vep_data/vep-gcloud.json,VEP_REPLICATE=us --init=gs://gcp-public-data--gnomad/resources/vep/v101/init-vep101.sh --pkgs="git+https://github.com/broadinstitute/gnomad_methods.git@main"

Then:
import hail as hl
from gnomad.utils.vep import vep_or_lookup_vep
hl.init(default_reference='GRCh38')

ht = hl.read_table("gs://path/to/my/table.ht")
ht = vep_or_lookup_vep(ht, vep_version="101")

I see, thanks! Yes, I was using --vep GRCh38.
Is this a correct way to refer the PR branch? I tried my script with this since the PR isn't merged yet, but had no luck.
--pkgs="git+https://github.com/broadinstitute/gnomad_methods.git@konradjk-patch-1"

Yes that is the correct way to start the cluster for that branch, but if you try out the method I showed above you shouldn't need the new branch, it should still work. You need the new branch though if using VEP 95

Thanks! Unfortunately, I got a following new error with your code and cluster configuration
Welcome to
     __  __     <>__
    / /_/ /__  __/ /
   / __  / _ `/ / /
  /_/ /_/\_,_/_/_/   version 0.2.98-f8833c1ae16b
LOGGING: writing to /home/hail/hail-20220830-1729-0.2.98-f8833c1ae16b.log
INFO (gnomad.utils.vep 204): Using VEPed context Table from genome build GRCh38 and VEP version 101
Traceback (most recent call last):                              (0 + 96) / 2798]
  File "/tmp/33ac4b66ef6b430dbf13669a0eccb335/annotate_vep.py", line 106, in <module>
    main(args)
  File "/tmp/33ac4b66ef6b430dbf13669a0eccb335/annotate_vep.py", line 50, in main
    ht = ht.checkpoint(
  File "<decorator-gen-1022>", line 2, in checkpoint
  File "/opt/conda/default/lib/python3.8/site-packages/hail/typecheck/check.py", line 577, in wrapper
    return __original_func(*args_, **kwargs_)
  File "/opt/conda/default/lib/python3.8/site-packages/hail/table.py", line 1291, in checkpoint
    self.write(output=output, overwrite=overwrite, stage_locally=stage_locally, _codec_spec=_codec_spec)
  File "<decorator-gen-1024>", line 2, in write
  File "/opt/conda/default/lib/python3.8/site-packages/hail/typecheck/check.py", line 577, in wrapper
    return __original_func(*args_, **kwargs_)
  File "/opt/conda/default/lib/python3.8/site-packages/hail/table.py", line 1335, in write
    Env.backend().execute(ir.TableWrite(self._tir, ir.TableNativeWriter(output, overwrite, stage_locally, _codec_spec)))
  File "/opt/conda/default/lib/python3.8/site-packages/hail/backend/py4j_backend.py", line 104, in execute
    self._handle_fatal_error_from_backend(e, ir)
  File "/opt/conda/default/lib/python3.8/site-packages/hail/backend/backend.py", line 181, in _handle_fatal_error_from_backend
    raise err
  File "/opt/conda/default/lib/python3.8/site-packages/hail/backend/py4j_backend.py", line 98, in execute
    result_tuple = self._jbackend.executeEncode(jir, stream_codec, timed)
  File "/usr/lib/spark/python/lib/py4j-0.10.9-src.zip/py4j/java_gateway.py", line 1304, in __call__
  File "/opt/conda/default/lib/python3.8/site-packages/hail/backend/py4j_backend.py", line 31, in deco
    raise fatal_error_from_java_error_triplet(deepest, full, error_id) from None
hail.utils.java.FatalError: HailException: VEP command '/vep --format vcf --json --everything --allele_number --no_stats --cache --offline --minimal --assembly GRCh38 --merged --fasta /opt/vep/.vep/Homo_sapiens.GRCh38.dna.toplevel.fa.gz --plugin LoF,loftee_path:/opt/vep/Plugins/,gerp_bigwig:/opt/vep/.vep/gerp_conservation_scores.homo_sapiens.GRCh38.bw,human_ancestor_fa:/opt/vep/.vep/human_ancestor.fa.gz,conservation_file:/opt/vep/.vep/loftee.sql --dir_plugins /opt/vep/Plugins/ -o STDOUT' failed with non-zero exit status 2
  VEP Error output:
Smartmatch is experimental at /opt/vep/Plugins/de_novo_donor.pl line 175.
Smartmatch is experimental at /opt/vep/Plugins/de_novo_donor.pl line 214.
Smartmatch is experimental at /opt/vep/Plugins/splice_site_scan.pl line 191.
Smartmatch is experimental at /opt/vep/Plugins/splice_site_scan.pl line 194.
Smartmatch is experimental at /opt/vep/Plugins/splice_site_scan.pl line 238.
Smartmatch is experimental at /opt/vep/Plugins/splice_site_scan.pl line 241.

-------------------- EXCEPTION --------------------
MSG: ERROR: Cache directory /opt/vep/.vep/homo_sapiens_merged not found

STACK Bio::EnsEMBL::VEP::CacheDir::dir /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/CacheDir.pm:311
STACK Bio::EnsEMBL::VEP::CacheDir::init /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/CacheDir.pm:227
STACK Bio::EnsEMBL::VEP::CacheDir::new /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/CacheDir.pm:111
STACK Bio::EnsEMBL::VEP::AnnotationSourceAdaptor::get_all_from_cache /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/AnnotationSourceAdaptor.pm:115
STACK Bio::EnsEMBL::VEP::AnnotationSourceAdaptor::get_all /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/AnnotationSourceAdaptor.pm:91
STACK Bio::EnsEMBL::VEP::BaseRunner::get_all_AnnotationSources /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/BaseRunner.pm:170
STACK Bio::EnsEMBL::VEP::Runner::init /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/Runner.pm:132
STACK Bio::EnsEMBL::VEP::Runner::run /opt/vep/src/ensembl-vep/modules/Bio/EnsEMBL/VEP/Runner.pm:203
STACK toplevel /opt/vep/src/ensembl-vep/vep:228
Date (localtime)    = Tue Aug 30 17:31:06 2022
Ensembl API version = 101
---------------------------------------------------

We identified that the init located here: gs://gcp-public-data--gnomad/resources/vep/v101/init-vep101.sh tries to copy resources that no longer exist because they were removed from gnomad-public-requester-pays after being moved to gcp-public-data--gnomad. I have fixed these links in the init and copied the fixed init to the following location gs://gnomad-public-requester-pays/resources/vep/v101/init-vep101.sh which will sync to gs://gcp-public-data--gnomad/resources/vep/v101/init-vep101.sh in the next day or so

Great, thank you so much for your help!


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2698

Questions ?
Please refer to the Backport tool documentation


glTF importer fails to import models with armatures

Same as #10130.
I haven't succeeded in importing any animated models with armatures, be with with khronos gltf exporter (mostly results in segfaults), blendergltf or a gltf model downloaded from sketchfab.

For the sake of argument, here is a simpler model which also crashes godot when importing the gltf file generated by khronos gltf exporter.

I can confirm this, I hope this stacktrace helps:

...
type float component type: Float stride: 4 amount 1
accessor offset0 view offset: 2000752 total buffer len: 2000768 view len 4
type vec3 component type: Float stride: 12 amount 1
accessor offset0 view offset: 2000756 total buffer len: 2000768 view len 12
total animations: 1
ERROR: Vector<class Skeleton *>::operator []: FATAL: Index p_index out of size (size()).
At: e:\godot\core\vector.h:137
CrashHandlerException: Program crashed
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/
godot/issues
[0] Vector<Skeleton * __ptr64>::operator[] (e:\godot\core\vector.h:137)
[1] Vector<Skeleton * __ptr64>::operator[] (e:\godot\core\vector.h:137)
[2] EditorSceneImporterGLTF::_generate_node (e:\godot\editor\import\editor_scene_importer_gltf.cpp:1
635)
[3] EditorSceneImporterGLTF::_generate_scene (e:\godot\editor\import\editor_scene_importer_gltf.cpp:
1988)
[4] EditorSceneImporterGLTF::import_scene (e:\godot\editor\import\editor_scene_importer_gltf.cpp:210
0)
[5] ResourceImporterScene::import (e:\godot\editor\import\resource_importer_scene.cpp:1048)
[6] EditorFileSystem::_reimport_file (e:\godot\editor\editor_file_system.cpp:1403)
[7] EditorFileSystem::reimport_files (e:\godot\editor\editor_file_system.cpp:1517)
[8] EditorFileSystem::_update_scan_actions (e:\godot\editor\editor_file_system.cpp:395)
[9] EditorFileSystem::_notification (e:\godot\editor\editor_file_system.cpp:1018)
[10] EditorFileSystem::_notificationv (e:\godot\editor\editor_file_system.h:100)
[11] Object::notification (e:\godot\core\object.cpp:851)
[12] SceneTree::_notify_group_pause (e:\godot\scene\main\scene_tree.cpp:913)
[13] SceneTree::idle (e:\godot\scene\main\scene_tree.cpp:488)
[14] Main::iteration (e:\godot\main\main.cpp:1670)
[15] OS_Windows::run (e:\godot\platform\windows\os_windows.cpp:2138)
[16] widechar_main (e:\godot\platform\windows\godot_win.cpp:149)
[17] _main (e:\godot\platform\windows\godot_win.cpp:171)
[18] main (e:\godot\platform\windows\godot_win.cpp:183)
[19] __scrt_common_main_seh (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283)
[20] BaseThreadInitThunk
-- END OF BACKTRACE --

Kupoman's gltf exporter is able to import the model, but not the skeleton

Can confirm this.
My baseman's foot is apparently also many parts of his body.

I'm kind of fed up of these formats,  will convert skeletons to global coordinates..


build fail ios 'UIImage+fixOrientation.m' file not found error

I am using ionic 4 and Capacitor framework.
I am using cordova-plugin-fingerprint-aio plugin for biometerics auth in app.
When i use  [https://github.com/Telerik-Verified-Plugins/ImagePicker] in the project it clash with the fingureprint-aio plugin and builds fail in ios with error 'UIImage+fixOrientation.m' file not found error

Same here.

you try
#import "UIImage+fixOrientation.h"  -->
#import "UIImage+fixOrientation.m"

same here

Solve in 2.3.6


feat: make workflow computable without instantiating dependents

Depends on #1648

Replaces #1641.

Do we still need the DependentResourceConfigurator interface?

Do we still need the DependentResourceConfigurator interface?

Unless you have a way to remove it, yes, we still need it as it's still used in the code.

Just added 2 remarks, 1 is just conceptuial idea, otherwise makes sense, I like the changes :)


Performance slowdown using http-instrumentation

What happened?
Steps to Reproduce
create a server running on main thread, offloads requests to node worker threads. implement open telemetry on main thread, requests/sec is reduced by 80% when http-instrumentation is applied to the main thread.
Expected Result
http-instrumentation shouldn't decrease performance by 80% when implemented.
Actual Result
http-instrumentation decreases requests/second performance by 80%
Additional Details
OpenTelemetry Setup Code
const os = require('os');
const { isMainThread } = require('worker_threads');
const { trace, propagation } = require('@opentelemetry/api');
const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
const { BatchSpanProcessor } = require('@opentelemetry/sdk-trace-base');
const {
  CollectorTraceExporter,
} = require('@opentelemetry/exporter-collector-proto');
const { registerInstrumentations } = require('@opentelemetry/instrumentation');
const { HttpInstrumentation } = require('@opentelemetry/instrumentation-http');
const {
  FastifyInstrumentation,
} = require('@opentelemetry/instrumentation-fastify');
const {
  SemanticResourceAttributes,
} = require('@opentelemetry/semantic-conventions');
const { Resource } = require('@opentelemetry/resources');
const {
  CompositePropagator,
  W3CTraceContextPropagator,
} = require('@opentelemetry/core');
const {
  B3Propagator,
  B3InjectEncoding,
} = require('@opentelemetry/propagator-b3');

const fastify = require('../../server/fastify');
const { serviceName, version } = require('../server-info');
const { register } = require('../../utils/register-to-close');
const { SemanticELFAttributes } = require('../SemanticELFAttributes');

propagation.setGlobalPropagator(
  new CompositePropagator({
    propagators: [
      new B3Propagator({ injectEncoding: B3InjectEncoding.MULTI_HEADER }),
      new W3CTraceContextPropagator(),
    ],
  })
);

const provider = new NodeTracerProvider({
  resource: new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: serviceName,
    [SemanticResourceAttributes.SERVICE_NAMESPACE]: 'xxxxx',
    [SemanticResourceAttributes.SERVICE_INSTANCE_ID]: os.hostname(),
    [SemanticResourceAttributes.SERVICE_VERSION]: version,
    [SemanticELFAttributes.SERVICE_CAR_ID]: 'xxxxxx',
    [SemanticELFAttributes.DEPLOYMENT_ENVIRONMENT]:
      process.env.EPAAS_ENV
      || (process.env.NODE_ENV === 'development' ? 'E0' : undefined),
  }),
});

provider.addSpanProcessor(
  new BatchSpanProcessor(
    new CollectorTraceExporter({
      // url: is configured via OTEL_EXPORTER_OTLP_TRACES_ENDPOINT env var
      serviceName,
      concurrencyLimit: 10, // pending requests limit, dropped after that
    }),
    {
      // basing numbers off of 700rps
      // past this size spans are dropped
      maxQueueSize: 400,
      // maximum batch size of every export (maxExportBatchSize <= maxQueueSize)
      maxExportBatchSize: 100,
      scheduledDelayMillis: 500, // interval between two consecutive exports
      exportTimeoutMillis: 15e3, // cancelled on failure
    }
  )
);

const tracer = trace.getTracer(serviceName, version);

const httpInstrumentationOptions = {
  ignoreIncomingPaths: ['/ReadMetrics.v1', '/ReadResponseCode.v1', '/favicon.ico'],
};

if (isMainThread) {
  // Initialie instrumentations on worker only
  const { httpRequestHook, buildHTTPResponseHook } = require('../hooks');

  Object.assign(httpInstrumentationOptions, {
    requestHook: httpRequestHook,
    responseHook: buildHTTPResponseHook(tracer),
  });

  registerInstrumentations({
    tracerProvider: provider,
    instrumentations: [
      new HttpInstrumentation(httpInstrumentationOptions),
      new FastifyInstrumentation({
        ignoreUrls: ['/ReadMetrics.v1', '/ReadResponseCode.v1', '/favicon.ico'],
        requestHook: (span, info) => {
          span.setAttribute('http.method', info.request.method);
        },
      }),
    ],
  });
}
  provider.register();
  register(() => provider.shutdown());

  fastify.log.info(`Tracing initialized for ${isMainThread ? 'server thread' : 'worker thread'}`);
module.exports = tracer;

package.json
{
  "name": "xxxx",
  "version": "1.2.7",
  "description": "",
  "main": "server.js",
  "scripts": {
    "test": "npm run test:lint && npm run test:unit",
    "test:unit": "echo test",
    "start": "node src/server",
    "test:lint": "eslint --ignore-path .gitignore --ext js,jsx,snap ."
  },
  "bin": {
    "server": "./bin/server.js"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@babel/polyfill": "^7.12.1",
    "@fastify/cors": "^8.2.1",
    "@fastify/helmet": "^10.1.0",
    "@opentelemetry/api": "^1.4.1",
    "@opentelemetry/core": "^1.5.0",
    "@opentelemetry/exporter-collector-proto": "^0.25.0",
    "@opentelemetry/exporter-prometheus": "^0.36.1",
    "@opentelemetry/instrumentation": "^0.41.2",
    "@opentelemetry/instrumentation-fastify": "^0.31.1",
    "@opentelemetry/instrumentation-http": "^0.45.1",
    "@opentelemetry/metrics": "^0.24.0",
    "@opentelemetry/propagator-b3": "^1.13.0",
    "@opentelemetry/resources": "^1.13.0",
    "@opentelemetry/sdk-metrics": "^1.10.1",
    "@opentelemetry/sdk-trace-base": "^1.10.0",
    "@opentelemetry/sdk-trace-node": "^1.10.1",
    "@opentelemetry/semantic-conventions": "^1.10.1",
    "decompress": "^4.2.1",
    "decompress-targz": "^4.1.1",
    "eslint": "^8.46.0",
    "etcd3": "^1.1.0",
    "fastify": "^4.17.0",
    "helmet": "^5.0.2",
    "ip": "^1.1.8",
    "jest": "^28.1.3",
    "jks-js": "^1.0.2",
    "node-fetch": "^2.6.7",
    "opentelemetry-node-metrics": "^3.0.0",
    "os": "^0.1.2",
    "path": "^0.12.7",
    "pino": "^8.14.1",
    "pino-opentelemetry-transport": "^0.2.0",
    "pino-pretty": "^10.2.0",
    "stream": "0.0.2",
    "util": "^0.12.4",
    "uuid": "^8.3.2"
  },
  "overrides": {
    "core-js": "3.28.0",
    "import-in-the-middle": "1.4.2",
    "protobufjs": "6.8.9"
  },
  "engines": {
    "node": "=18.x.x",
    "npm": "=9.x.x"
  }
}

Relevant log output
No response

Hey! I can help with this. May I be assigned?

Hey! I can help with this. May I be assigned?

Great! It's yours, thanks for picking this up :slightly_smiling_face:

Hello, any updates on this issue? I've noticed 2x slow down using open telemetry with node and graphql app

Do you happen to have any updates on this issue?
I've encountered the same and according to a stacktrace the problem might be in the incomingRequest method:

I am not sure if there's much that can be done as it's parsing the request in the Node internal server and that is for some reason very CPU-hungry.

Looks like it is produce big event loop lag in otl operations, but Im not sure.
So I have prometeus metrics on nodejs app, and got screenshot:

In left side tracing enabled, then I just disable it and we see different image on right side.
(I have 6 replica of app in kubernates running, that why we see many lines)
Some details about my code. It is Koa app and in Index file I have code like:
if (env.TRACING_ENABLED) {
    app.use(async (ctx, next) => {
      const tracer = trace.getTracer("myapp");

      const span = tracer.startSpan("http_request", {
        attributes: {
          "http.method": ctx.method,
          "http.path": ctx.path,
        },
      });

      try {
        await next();

        span.setAttribute("http.status_code", ctx.status);
      } catch (err) {
        span.recordException(err);
        span.setAttribute("http.status_code", 500);

        throw err;
      } finally {
        span.end();
      }
    });
  }

My tracing initialization like:
const traceExporter = new OTLPTraceExporter({
    url: env.TRACING_URL,
    compression: CompressionAlgorithm.GZIP,
  });

  const sdk = new NodeSDK({
    resource: new Resource({
      [ATTR_SERVICE_NAME]: env.SERVICE_NAME,
      [ATTR_SERVICE_VERSION]: env.VERSION,
    }),
    traceExporter,
    instrumentations: [
      getNodeAutoInstrumentations({
        "@opentelemetry/instrumentation-koa": {
          requestHook: (span, info) => {
            info.context.set("X-Request-Id", span.spanContext().traceId);
          },
        },
      }),
      new WinstonInstrumentation(),
      new BullMQInstrumentation(),
      new UndiciInstrumentation(), // for FetchAPI
      new SequelizeInstrumentation(),
    ],
  });

  try {
    sdk.start();
  } catch (err) {
    console.error(`Error starting OpenTelemetry SDK`, err);
  }

Also I think GZIP can affect on load. In next I will try disable GZIP and see what happen.

So yes. Problem in GZIP. I just disable it

@WilixLead nice find but with default configuration, the compression is set to NONE so it's probably not the only thing causing this. See https://github.com/open-telemetry/opentelemetry-js/blob/6515ed8098333646a63a74a8c0150cc2daf520db/experimental/packages/otlp-grpc-exporter-base/src/util.ts#L154

I know :) Just we use example founded in Internet with compression. Copy-paste coding...

I'm not sure the performance issues are limited to HTTP. Seeing as much as a ~40% decrease in requests p/ second on an express.js app. Disabling HTTP doesn't have much of an effect for me.


[PECO-1259] Implement retry behavior for CloudFetch

PECO-1259

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (a86f828) 90.33% compared to head (95cafb4) 90.34%.

:exclamation: Current head 95cafb4 differs from pull request most recent head 78d3bb0. Consider uploading reports for the commit 78d3bb0 to get more accurate results

Files
Patch %
Lines

lib/hive/Commands/BaseCommand.ts
66.66%
0 Missing and 3 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #211      +/-   ##
==========================================
+ Coverage   90.33%   90.34%   +0.01%
==========================================
  Files          59       61       +2
  Lines        1376     1409      +33
  Branches      228      233       +5
==========================================
+ Hits         1243     1273      +30
  Misses         84       84
- Partials       49       52       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Possibility to put this app below others apps.

Now is impossible to open others apps on top of this app.

In the Window menu, you'll find an option labelled "Keep in Front". Unchecking this will allow it to go behind other windows.


First commit of _trotter_qasm_conversion

Methods for taking in arbitrary quantum operator (composed of Pauli strings), and giving Trotter-Suzuki decomposition in QASM format. -- ES Fried and NPD Sawaya

Thanks for this contribution Nico and Eric! I am traveling until this evening so I am assigning the code review to @jarrodmcc. A few quick comments though. First, it looks like tests are failing in python3. This should be easy to fix. Likely there are some functions you are using that are not forward compatible; e.g. "print my_string" instead of "print(my_string)". Coverage is slightly too low but its pretty close so I am sure Eric's extra tests will fix things. Next, please download and run the PEP 8 linter and look for violations. This helps ensure compliance with style and will point out some things that jump out right away such as having multiple blank lines at the end of a file. I will also take a look at the actual code when I get a chance.

Another thing that jumps out is that all functions must come with doc strings that follow the format of the rest of our library.

 I will go through it momentarily and offer some inline comments.  The style stuff is annoying at first, but becomes more natural! It looks like a great contribution!

Another point we need to consider is that the routine converts from a QubitOperator that contains its terms as a dictionary, which are then converted to a list.  The list has well-defined order, which then determines the Trotter sequence, but the dictionary does not.  This means that this routine called on QubitOperators that test equal can produce different results, which could be problematic for testing and consistency across different users.  I think we need an intermediate routine that makes the order well-defined in the conversion from dict to list so 2 users running this on identical Hamiltonians expect the same results.
I see the term_order list that you have now that could perform this function, but I think it should be a general function with a default that is well-ordered.  The list system you used could always be passed as a special case.

Hi everyone, Thanks a bunch for all the feedback! Eric made a lot of changes yesterday, and I'm taking everything from here.
I need new units tests and I'll probably add some easier functionality for outputting the result as operator objects. Also some renaming and modularization. This will be finished at some point this week--thanks for allowing for that.
Btw next time we'll make smaller commits...
cheers, nicolas

Hi Jarrod, Ryan, Eric,
I just pushed again. Let me know if PR'ing incorrectly (:
Some highlights:

PEP8 compliance, though there were some W503 warnings that I simply couldn't figure out how to get rid of.
So, the code does output “trotterized” order of operators as lists, then makes a product of exponents after that. Just wanted to make that clear. And the QASM-related functions are entirely separated from the Troterrization/exponentiation portion
I renamed the module and its functions substantially.
There’s now a standard default ordering, which is simply the sorted dictionary keys.
Everything is written to streams, not files, which makes it more modular and easier for testing.

Let us know your thoughts.
Btw congrats on the arxiv release!
Nicolas

Apologies for my delay. Eric's updates have been pushed.

Note that the test coverage will come up once tests pass. So focus on fixing the breaking tests first and then see where things stand.

Yeah so we made a mistake in the commit and forgot to delete the old files - the only three files which you should comment on are _trotter_exp_to_qgates_test.py, _trotter_exp_to_qgates.py, and init.py. Changes requested for those will be made shortly. Hopefully test coverage will be better and the Travis CI will build, once we remove the old files

I uploaded to see what Travis CI says; not necessarily done yet. I guess Travis doesn't run right away though.
Btw, is there a standalone utility that tests py2/py3 compliance? (Ian said he didn't know of any.) Ditto for test coverage?

You need to install both python 2 and 3 in order to test for compliance in
both languages. But pytest-cov can be used to easily check coverage. Travis
tries to run immediately but depending on server load might get queued. It
usually runs within ten minutes.
On Nov 23, 2017 14:27, "nicolassawaya"<EMAIL_ADDRESS>wrote:

I uploaded to see what Travis CI says; not necessarily done yet. I guess
Travis doesn't run right away though.
Btw, is there a standalone utility that tests py2/py3 compliance? (Ian
said he didn't know of any.) Ditto for test coverage?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/quantumlib/OpenFermion/pull/63#issuecomment-346704658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANlTf5_WVhheIvdXVsvKsr2k5hVGPD8gks5s5fFsgaJpZM4P_Rez
.

@babbush  Great--thanks a bunch

Okay, just finished writing all the unit tests. We went from 32% to 100% coverage, according to py.test on my machine. pep8 passes. We'll see if Travis reflects all this. Let us know about any changes or revamps we should do.

@jarrodmcc go ahead and use admin override to squash and merge when you decide the PR is ready.

Sorry about that delay! I was in the middle of traveling.
Thanks for all the help on this guys! We learned a lot during the process. Please let us know about anything else.


Implement foreground tapping under assisted tap

[ ] Need to finish assisted tap flow
[ ] Change icon image based on phone OS (iPhone vs Android)

Can use this repo https://github.com/hgoebl/mobile-detect.js to detect if it's iOS (display the image with card tap on the top) and detect if it's Android (display the image with card in the center).


Building on Windows

Ideally, gir.core should be able to work 'out of the box' on Windows.
Building
I've managed to get the project building (see #37). This involves remapping shared library names to dll names in order to link with the proper libraries.
GTK Binaries
GTK Binaries must be installed manually at the moment. I am using the MSYS2 binaries since they are the recommended way to get GTK on Windows (from the website).
To link with the native libraries, I added a function that remaps the shared library name to the DLL name. This is problematic as MSYS2 and vcpkg use different DLL names (libglib-2-0.dll vs glib-2.dll). It looks like vcpkg might be updating their GTK builds to use meson directly, so hopefully this will be fixed.
Missing Libraries
There are a few other issues remaining, most notably that webkit2gtk doesn't build on Windows anymore (see PR for info). We might need some way of marking a lib as platform specific, so we don't unnecessarily generate wrappers.
Feedback is very much appreciated.

I think as long as there is no release we can create a Windows version if it is compiled under Windows.
If there is a first release we should somehow create a platform independent version of the libraries.
A possible way is using the new .net core APIs: https://developers.redhat.com/blog/2019/09/06/interacting-with-native-libraries-in-net-core-3-0/
In general I like the msys2 approach as we don't need to distribute the packages for Windows. If there are packages missing it would work automatically work if the packages are created.

Yeah, I agree.
At the moment it's probably fine to generate a Windows-specific version, but once we push for a major (or beta/usable) release, it might be better to use the new .NET apis to lookup the library in a cross-platform way. It would also solve the DLL name dilemma as we could prioritise libglib-2-0.dll and then lookup glib-2.dll as a fallback.

A quick update on actually building the libraries. Cairo has just landed a meson port, which means the entire GTK Stack should now be buildable with Meson. Previously, cairo used Autotools which was a nightmare to build with MSVC.
Hopefully this means it'll be much easier to get started with GTK (and by extension, gir.core) on Windows.

Finally managed to get to the bottom of an odd issue where OmniSharp thought it was running on linux and sometimes wouldn't give me Intellisense.
In Directory.Build.props#L4 we explicitly set the Runtime Identifier to 'linux'. Is there any particular reason for this line, or could we safely remove it?
@badcel

I just tested it. We can safely remove it. The document states that it is used for self contained deployments. As we don't need this at the moment we are good to go without it. I'm going to create a pull request.

Closing this since we already have full support for building on Windows. Having a way for end-users to get Gir.Core without building it (or obtaining Gtk) themselves would be nice, but is probably for another issue.


feat(docs): Meet the UI after installation

Description
After the user has installed Resoto, we should guide him through the UI.

Docs Version(s)

[x] edge
[x] 3.X
[ ] 2.X

To-Dos

[x] Format with yarn format
[x] Lint with yarn lint
[x] Build successfully with yarn build

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

This is very much needed! I'll take a look at this tomorrow :)
@holopin-bot @aquamatthias

@aquamatthias Sorry for the delay in reviewing this. It took some time because I didn't feel like it made sense to just add a page describing the UI at the end. Rather, the user now has two choices after installing Resoto: to use Resoto UI or Resoto Shell.
Still much more to do to improve this, but here's a start!


can't change the node color onclick

How to change the color of nodes on clicking on the custom  handle nodes, i think it is not re-rendering on elements value change.

I suspect the problem is because you are not creating a new object when changing the styling and thus react flow doesn't know things changed. In the documentation there's the following:

You can check the update node example.
Hope this helps!


Target Sum(Java and C++) and House Robber(C++ Solution)

Issue #73

You have added two solutions.

Yeah I did create pull request for House robber only, but then I solved Target Sum also. You can wait till I add Target Sum solution in java ... and then you can resolve two issues in one merge

issues #112 and #73

Create new pull request for java target sum. Try to solve different issues by creating different branches.


Secret management hitting maximum value size

Rancher Versions:
Server: 1.4.0
healthcheck: v0.2.3
ipsec: 0.0.4
network-services: v0.0.10
scheduler: v0.4.0
secrets: v0.0.1
kubernetes (if applicable):
Docker Version:
Docker 1.12.6
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16.04 on AWS
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher, with 1 agent
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Launch Rancher/server
Launch Rancher secrets from the catalog
Add host to server
Add secret with key = test, value anything bigger than 141 bytes. For example 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'

Results:
Container is launched but volume with secret is not mounted.
Logging rancher/server:
time="2017-02-06T20:02:01Z" level=error msg="Could not decrypt secret"
time="2017-02-06T20:02:01Z" level=error msg="crypto/rsa: message too long for RSA public key size"
time="2017-02-06T20:02:01Z" level=error msg="Error in request, code : 400: crypto/rsa: message too long for RSA public key size"

Logging secrets container:
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=create.request name=ea367a4f41c10362bebfa8a34a0b0a57dc0b00517418d45bfc8017d052dbe19c options=map[io.rancher.secrets.token:{"value":"eyJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJjYXR0bGUiLCJraWQiOiJkZWZhdWx0IiwiaXNzIjoiaHR0cDpcL1wvY2F0dGxlLmlvIiwiZXhwIjoxNTE3OTcwOTAzLCJ1dWlkIjoiNTg5ODNiNmYtM2ZhZi00ZTBjLTk3MzYtMjQ4NzQ4MjMyNmQ1IiwiaWF0IjoxNDg2NDEzOTc3fQ.lYMjBmSE3rhzb_DXmaU-aJSRYVATN8hBxx3yxoxQe9TSH75SjzUs4j7KCLIgsyXTaxNI3lJqrP2H8PGiyoP7i5W-Up0wIPwD8i7EZEjlcV6g7HkiC1Msia-6tXZfugik1A4-cW4XAzP4CxDNNzQuYXxwlTXxhO6e59HrU0C-AXIP2hrcCPGIew39H8bp4vqicV4wHCLMyKf47uxqcOaShIZwc-Lf3kA4DsgtPraXlU7oSkPlUhZv1xiiAG05eTU7COELbfJbPkPeDcePTYL791O4GxAQ7wdBn6jkLJWP0Ttvy6Rf1clLpAaqC5IazNEzHPUWj982uSBTdmS4SoqJQg"}]
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg="Updating volume ea367a4f41c10362bebfa8a34a0b0a57dc0b00517418d45bfc8017d052dbe19c (1v124) rancher-secrets:1sd1 on 1h2, state inactive => inactive" err=<nil>
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=create.response
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=attach.request name=ea367a4f41c10362bebfa8a34a0b0a57dc0b00517418d45bfc8017d052dbe19c
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=error msg="Unsuccessful request: 500 Internal Server Error"
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=attach.response
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=mount.request name=ea367a4f41c10362bebfa8a34a0b0a57dc0b00517418d45bfc8017d052dbe19c
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=error msg="Unsuccessful request: 500 Internal Server Error"
06/02/2017 21:46:17time="2017-02-06T20:46:17Z" level=info msg=mount.response mountpoint="/var/lib/rancher/volumes/rancher-secrets/ea367a4f41c10362bebfa8a34a0b0a57dc0b00517418d45bfc8017d052dbe19c"
06/02/2017 21:49:19time="2017-02-06T20:49:19Z" level=info msg=remove.request name=3f460ea0465e3da8fbbe9407908423399d83e7901dcdf99d5c90b62bf7961173
06/02/2017 21:49:19time="2017-02-06T20:49:19Z" level=info msg=remove.response
06/02/2017 21:49:19time="2017-02-06T20:49:19Z" level=info msg=remove.request name=0dda41d1971a25932b941189b47ea6b7b59abdf0fb1a1be2964bc5a2b4d51498
06/02/2017 21:49:19time="2017-02-06T20:49:19Z" level=info msg=remove.response

The fixes will be in 1.5.0-rc1.
You should now be able to store larger items such as private keys.
To test this:

Create secrets in 1.4.x both large/small.
Deploy containers (this is initial functionality, and should fail with large secrets)
Upgrade Rancher to 1.5.0-rcX
Upgrade secrets volume driver
Deploy containers (Both large and small secrets should be created)

1.5.0-rc1 is out now

I followed the same steps:

Create secrets in 1.4.x both large/small.
Deploy containers (this is initial functionality, and should fail with large secrets)
Upgrade Rancher to 1.5.0-rcX
Upgrade secrets volume driver
Deploy containers (Both large and small secrets should be created)

I was able to deploy the containers with mounted secrets after the upgrade from v1.4.1 to v.1.5.0-rc1.


[Add] Want to add our Contributor page in the website.

Details
Is your feature request related to a problem? Please describe.
Our Contributors page in the website
Describe the solution you'd like
We can add a Contributors page in the website. which is shows the name and the profile image of the contributor.and the number of commits is done by the contributor
Screenshots
No response
Type of Contribution

[X] Update to an existing Animated Button
[ ] Adding a new Button
[ ] Resolving a bug
[X] Proposal to the Repository
[ ] Changes related to documentation or README.md
[X] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

🎉 The GSSOC'23 program has reached its conclusion, prompting us to officially close all pull requests (PRs) and issues. We extend a heartfelt thank you for your amazing contributions! 🙌 Keep the coding spirit alive with the same enthusiasm, and may luck 🍀 favor you in all your future coding adventures!


Create wing_modal_example_script

Here is the python script for the wing modal example.
Description
Please provide a brief description of the changes made in this pull request.
Issue linked
Please mention the issue number or describe the problem this pull request addresses.
Checklist

[ ] I have visited and read Develop PyMAPDL.
[ ] I have tested my changes locally
[ ] I have added necessary documentation or updated existing documentation.
[ ] I have followed the PyMAPDL coding style guidelines.
[ ] I have added appropriate unit tests that also ensure the minimal coverage criteria.
[ ] I have reviewed my changes before submitting this pull request.
[ ] I have linked the issue or issues that are solved to the PR if any.
[ ] I have assigned this PR to myself.
[ ] I have marked this PR as draft if it is not ready to be reviewed yet.
[ ] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

@mcMunich I just realized you are doing a pull request from a fork... this does not trigger CICD.
Can you close both PRs #3392 and #3391, and do the PR from a cloned repo, I will add you as an external collaborator, so the fork won't be used in your case. Also, ideally, you should merge both PRs then you can do things like referring to the script instead of copy/paste parts of the script in between:
https://github.com/ansys/pymapdl/blob/e7a3ef6b81ec2a62937c0f899708138b617707d2/doc/source/examples/extended_examples/hpc/hpc_ml_ga.rst?plain=1#L42-L45

Related to #3391


nixos/manual: warn on missing xml:id

In order to keep the manual reproducible, we need to avoid randomly
generated ids. This patch enables warning on missing ids.
A further step could turn them to errors, but the case of partintro
blocks needs to be solved first.
See #55375

[X] Tested manual generation.
[X] Fits CONTRIBUTING.md.

Make sense. Let’s do it as is.
Sent from my iPhone

On Feb 7, 2019, at 10:43, Guillaume Maudoux<EMAIL_ADDRESS>wrote:
@layus commented on this pull request.
In nixos/doc/manual/default.nix:

@@ -265,6 +265,7 @@ in rec {
xsltproc
${manualXsltprocOptions}
--stringparam target.database.document "${olinkDB}/olinkdb.xml" \

   --stringparam id.warnings "1" \

Well, this seems to only impact HTML documents. But adding it to the global options may be better if someone only tests it with some other version without generating the HTML. Not too sure really. What do you think ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Installation

How can I install this on my site.
I'm so stuck. Please help s your guide is too  vague. Itried following this but I get an error http://jekyllbootstrap.com/usage/jekyll-theming.html
No such file or directory @ rb_sysopen - ./_theme_packages/_tmp/manifest.yml

@jesster2k10 Please follow the exact same instructions from the readme file. I do not use the way you linked me ;)


Fixing performance of evented set

In this PR I have added an option for the combiner function to consume the whole list of tuples at once.

When developing locally, pre-commit complains about line length, but I do not know how to break type declaration.
Also, mypy report problems with lack of Self (I see that on Ci, it does not happen).
I need to add type casting for reducer to satisfy mypy.

(Should I add benchmarks to tests/test_bench)?

(Should I add benchmarks to tests/test_bench)?

it's ok.  the asv benchmarks are nice because they can run retrospectively (and show the speedup you gained here), whereas codspeed and test_bench can only start measuring going forward.  I like codspeed in general, but the lack of retrospective monitoring is a bummer, so the one you added to asv is good enough


roslaunch tello_driver tello_node.launch   BUT: File "/home/smile/code_demo/tello_catkin_ws/src/tello_driver/src/tello_driver_node.py", line 14, in      import av ImportError: No module named av

`smile@smile-Vostro-3400:~/code_demo/tello_catkin_ws$ roslaunch tello_driver tello_node.launch
... logging to /home/smile/.ros/log/59a006b8-e9f1-11ec-8906-a4423b77d657/roslaunch-smile-Vostro-3400-10061.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://smile-Vostro-3400:37971/
SUMMARY
PARAMETERS

/rosdistro: melodic
/rosversion: 1.14.13
/tello/tello/connect_timeout_sec: 10.0
/tello/tello/local_cmd_client_port: 8890
/tello/tello/local_vid_server_port: 6038
/tello/tello/stream_h264_video: False
/tello/tello/tello_cmd_server_port: 8889
/tello/tello/tello_ip: <IP_ADDRESS>

NODES
/tello/
image_compressed (image_transport/republish)
tello (tello_driver/tello_driver_node.py)
auto-starting new master
process[master]: started with pid [10071]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 59a006b8-e9f1-11ec-8906-a4423b77d657
process[rosout-1]: started with pid [10082]
started core service [/rosout]
process[tello/tello-2]: started with pid [10086]
process[tello/image_compressed-3]: started with pid [10089]
terminate called after throwing an instance of 'pluginlib::LibraryLoadException'
what():  According to the loaded plugin descriptions the class image_transport/compressed_pub with base class type image_transport::PublisherPlugin does not exist. Declared types are  image_transport/raw_pub
Traceback (most recent call last):
File "/home/smile/code_demo/tello_catkin_ws/src/tello_driver/src/tello_driver_node.py", line 14, in
import av
ImportError: No module named av
[tello/tello-2] process has died [pid 10086, exit code 1, cmd /home/smile/code_demo/tello_catkin_ws/src/tello_driver/src/tello_driver_node.py __name:=tello __log:=/home/smile/.ros/log/59a006b8-e9f1-11ec-8906-a4423b77d657/tello-tello-2.log].
log file: /home/smile/.ros/log/59a006b8-e9f1-11ec-8906-a4423b77d657/tello-tello-2*.log
[tello/image_compressed-3] process has died [pid 10089, exit code -6, cmd /opt/ros/melodic/lib/image_transport/republish raw in:=image_raw compressed out:=image_raw __name:=image_compressed __log:=/home/smile/.ros/log/59a006b8-e9f1-11ec-8906-a4423b77d657/tello-image_compressed-3.log].
log file: /home/smile/.ros/log/59a006b8-e9f1-11ec-8906-a4423b77d657/tello-image_compressed-3*.log
`

`smile@smile-Vostro-3400:~$ pip install av
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Defaulting to user installation because normal site-packages is not writeable
Collecting av
Downloading av-9.2.0.tar.gz (2.4 MB)
|████████████████████████████████| 2.4 MB 250 kB/s
Installing build dependencies ... done
Getting requirements to build wheel ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python /home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpEjjUR3
cwd: /tmp/pip-install-Kw4jkO/av
Complete output (18 lines):
Traceback (most recent call last):
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in
main()
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 114, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-XzZKEb/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 146, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=['wheel'])
File "/tmp/pip-build-env-XzZKEb/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 127, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-XzZKEb/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 243, in run_setup
self).run_setup(setup_script=setup_script)
File "/tmp/pip-build-env-XzZKEb/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 142, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 3, in
import pathlib
ImportError: No module named pathlib
ERROR: Command errored out with exit status 1: /usr/bin/python /home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmpEjjUR3 Check the logs for full command output.
WARNING: You are using pip version 20.3.4; however, version 21.3.1 is available.
You should consider upgrading via the '/usr/bin/python -m pip install --upgrade pip' command.
smile@smile-Vostro-3400:~$
`

`
smile@smile-Vostro-3400:~$ pip install av
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Defaulting to user installation because normal site-packages is not writeable
Collecting av
Using cached av-9.2.0.tar.gz (2.4 MB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python /home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp_5eHT7
cwd: /tmp/pip-install-L7zLhN/av
Complete output (18 lines):
Traceback (most recent call last):
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in
main()
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py", line 114, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-3Qqyn1/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 146, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=['wheel'])
File "/tmp/pip-build-env-3Qqyn1/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 127, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-3Qqyn1/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 243, in run_setup
self).run_setup(setup_script=setup_script)
File "/tmp/pip-build-env-3Qqyn1/overlay/lib/python2.7/site-packages/setuptools/build_meta.py", line 142, in run_setup
exec(compile(code, file, 'exec'), locals())
File "setup.py", line 3, in
import pathlib
ImportError: No module named pathlib
ERROR: Command errored out with exit status 1: /usr/bin/python /home/smile/.local/lib/python2.7/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp_5eHT7 Check the logs for full command output.
WARNING: You are using pip version 20.3.4; however, version 21.3.1 is available.
You should consider upgrading via the '/usr/bin/python -m pip install --upgrade pip' command.
smile@smile-Vostro-3400:~$ /usr/bin/python -m pip install --upgrade pip
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Defaulting to user installation because normal site-packages is not writeable
Requirement already up-to-date: pip in ./.local/lib/python2.7/site-packages (20.3.4)
WARNING: You are using pip version 20.3.4; however, version 21.3.1 is available.
You should consider upgrading via the '/usr/bin/python -m pip install --upgrade pip' command.
smile@smile-Vostro-3400:~$ sudo /usr/bin/python -m pip install --upgrade pip
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
WARNING: The directory '/home/smile/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Requirement already up-to-date: pip in ./.local/lib/python2.7/site-packages (20.3.4)
smile@smile-Vostro-3400:~$ sudo /usr/bin/python -m pip install --upgrade pip --user
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
WARNING: The directory '/home/smile/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Requirement already up-to-date: pip in ./.local/lib/python2.7/site-packages (20.3.4)
`

In my case, installing av version 0.5.2 was worked.
you can try pip install av=0.5.2


release teeracle SDK

release a first version of our teeracle SDK nailed to a recent polkadot release

[x] write a tutorial how developers can change our teeracle to fetch some trading pair on coinmarketcap (i.e. DOT/USD) and send the data to L1 teeracle pallet (use a fork of our our solochain integritee-node as L1 for simplicity)

Existing version on https://integritee-network.gitbook.io/integritee-wiki/for-developers/teeracle
In GitBook https://integritee-network.gitbook.io

[ ] README.md in repository references the GitBook
[ ] New release branch version 0.10.0, polkadot 0.9.27

Do the release according to : https://github.com/integritee-network/worker/issues/990


Limelight targeting

We need the limelight to see multiple strips of tape as a target, we're not sure if it does.

We tested on a flat cardboard piece with an arc of targets, filtering by high using a single target seems to work well enough.


QBO – Unable to change preferred exporter in QBO connection

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.40-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5006859
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:
Action Performed:
Prerequisite
Workspace is connected to QBO
Another Admin is added to the workspace

Navigate to Accounting
Click on Export
Click Preferred Exporter
Select the unchecked workspace admin
Wait for the connection to sync and check the preferred exporter

Expected Result:
The newly selected exporter is displayed with a checkmark
Actual Result:
The selected exporter does not stay selected and the exporter is reverted back to the previous one
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[X] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/911fb40a-2e72-4343-8ba7-626426b95336

View all open jobs on GitHub

We think this is related to #wave-collect - Release 2

Proposal
Please re-state the problem that we are trying to solve in this issue.

Unable to update the QBO Preferred exporter

What is the root cause of that problem?

In QuickbooksPreferredExporterConfigurationPage we are using qboConfig?.export.exporter as the fallback value for optimistic update. But  qboConfig.export can be undefined when we first sync.

What changes do you think we should make in order to solve the problem?

In QuickbooksPreferredExporterConfigurationPage update code to qboConfig?.export?.exporter.

What alternative solutions did you explore? (Optional)

Proposal updated.

Oh dang, thanks for the proposals so far! Anyone know which PR the bug may have come from??

@Beamanator Likely https://github.com/Expensify/App/pull/48080/files#diff-afb3647e9a1c6b4d00a7047f997bffa23c873bbd6807e726807f48ebef608bcaR57

Yaaa i was kinda thinking that too ^

@shubham1206agra  @dangrous  @rushatgabhane @aldo-expensify can y'all look at this?

Investigating...

I think this is probably due to https://github.com/Expensify/Expensify/issues/431392#issuecomment-2377490529 which I just noticed today - basically I think we're ending up trying to update the export object to {exporter: {exporter: [actual value]}} but not 100% sure

The exporter is getting encoded and nested in a weird way:

This is a duplicate of https://github.com/Expensify/Expensify/issues/431392#issuecomment-2377490529.

This seems to fix it: https://github.com/Expensify/App/pull/49818
cc @dangrous

@aldo-expensify This might fix the API call but when I did a fresh connection, I could see the JS error for qboConfig?.export.exporter as qboConfig.export was undefined. May be we'll need to fix both?

@aldo-expensify This might fix the API call but when I did a fresh connection, I could see the JS error for qboConfig?.export.exporter as qboConfig.export was undefined. May be we'll need to fix both?

That sounds unrelated. Can you reproduce it in production?

About that second bug, I'm not sure what is proposed here is the "right" way to fix it: https://github.com/Expensify/App/issues/49797#issuecomment-2377460969
If the request to update the exporter fails, the "current value" we revert to could be wrong. The real value may have just been delayed.

Here's a recording, and it looks like reproducible on Prod too.
https://github.com/user-attachments/assets/354d87a6-32eb-4c77-8e90-eea6aa133a57

Here's a recording, and it looks like reproducible on Prod too.

nice, I think we should work on the right solution with more time, so I would avoid putting it together with the deploy blocker

Is the API being called in your solution? If you see the recording the API wasn't called at all. Adding optional chaining works as mentioned in my proposal.
https://github.com/user-attachments/assets/87b7d7b1-87a0-4711-9ee7-526d778d61cd
On a side note, I can help you review the DeployBlocker PR.

Adding optional chaining works as mentioned in my https://github.com/Expensify/App/issues/49797#issuecomment-2377428671.

I want to avoid adding optional chaining just to go around an issue that may require a better solution

Is the API being called in your solution?

yes, you can see it in the video I attached to the PR

Yeah I can see that. Thanks for clarifying.

Thanks so much for taking care of this since i had to peace out early yesterday @aldo-expensify 🙏

How's this one going, @aldo-expensify?

@johncschuster I believe the PR was deployed to fix the Deploy blocker. I had helped with the PR review, and there would be a payout for me. Can you please update the payment summary for this one?
Also @aldo-expensify do you think it's worth solving the FE error in this issue?

How's this one going, @aldo-expensify?

The deploy blocker (this issue) was solved by this PR: https://github.com/Expensify/App/pull/49818
@mananjadhav reviewed so we should pay
While we worked on that, another bug was found: https://github.com/Expensify/App/issues/49797#issuecomment-2377938528, but I would recommend creating a new clean issue for that with reproduction steps.

Also @aldo-expensify do you think it's worth solving the FE https://github.com/Expensify/App/issues/49797#issuecomment-2377958255 in this issue?

Yes, but I think we should open a new issue to avoid confusions. I'm not really sure about what kind of solution are we looking for... it sounds like we should maybe lock the inputs until we have received the data or something like that.

Could be related. I can check that one if you'd like.

@johncschuster the PR was deployed 2 weeks ago, we need to process @mananjadhav 's C+ payment.

Sorry folks! I action all my payment issues every day by filtering my assignments by HOLD for payment in the title and I missed this. Thank you for the pings!

Thanks @johncschuster for the help here.

$250 approved for @mananjadhav

@aldo-expensify / @mananjadhav can you provide a regression test step list if we need one?

@aldo-expensify / @mananjadhav can you provide a regression test step list if we need one?

I don't think we need a new one. This bug was caught while running the existing test: https://expensify.testrail.io/index.php?/tests/view/5006859


Errors when compiling

Each time I have 2 errors when compiling

pls help ;c

In the includes, rename #include <experimental/filesystem> to just #include

what to do now?

rename every instance of std::experimental::filesystem to std::filesystem

now i have it

go to config.cpp and menu.cpp and remove the experimental/ part of the include

double click on the first menu.cpp error show me what you did

remove ::filesystem once

make sure you set c++ version properly in the project settings and #include  properly

i just run sln file i wanna compile and got this

I understand but the project isn’t recommended to people with no knowledge of c++, deadcell is unfortunately still in development and isnt a finished product.

I understand thx for help


Maven 4.0.0-beta-1 updates

Parked just for reference.
Changes:

remove SystemScopeHandler (was added in alpha-8 and implemented in Maven 4 alpha-13)
scope configuration canonical source is Maven 4
RepositorySystem and SessionBuilder supplier canonical source is Maven 4

This build will fail, as it requires https://github.com/apache/maven/pull/1460 changes

Superseded by https://github.com/apache/maven-resolver/pull/480


Update to latest trust-core

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #66   +/-   ##
=======================================
  Coverage   98.39%   98.39%
=======================================
  Files           5        5
  Lines         311      311
=======================================
  Hits          306      306
  Misses          5        5

Impacted Files
Coverage Δ

Tests/AccountTests.swift
100% <100%> (ø)
:arrow_up:

Tests/KeystoreKeyTests.swift
97.33% <100%> (ø)
:arrow_up:

Tests/KeyStoreTests.swift
100% <100%> (ø)
:arrow_up:

Tests/WalletTests.swift
100% <100%> (ø)
:arrow_up:

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 8cb7532...a237de5. Read the comment docs.


remove duplicate tamper product to fix e2e test failure

This should get e2e tests passing when paired with #9 or the equivalent upstream change.
Changes:

remove the osaft product
update the product search query to zap from o-saft to get the frisby test to pass again

Having two tamper products breaks the e2e test unauthed "changeProduct" challenge in the following way:

the change product test uses the first product ID (in this case osaft with id 26)
data creator appends an osaft link to the description of products tagged useForProductTamperingChallenge and caches the last one as products.osaft (in this case zap with id 27)
so even though the test changes the osaft product, the scoreboard didn't update since it was looking for changes to products.osaft / zap and the test failed

r? @psiinon
cc @bkimminich re: multiple tamper products breaking an e2e test as described above. I think we want to check that only one product is tagged useForProductTamperingChallenge. I can make a PR upstream if that's the case.

Yep, there can be only one of each special product tags. Duplicates will cause weird effects.


⚠ Bofrost.lu has degraded performance

In 446f7a0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1689 ms

Resolved: Bofrost.lu performance has improved in fae0afd after 36 minutes.


Kalimba will not scroll to a note if it isn't already on screen

So if you start playback from a note off screen, the kalimba will not scroll to it

fixed in this commit https://github.com/oakleyaidan21/kalimba-tabs/commit/7914d31a400ddd64338894cab95252ca52e3e82e


Leaking open cursors when not using prepared statements

I just recently switched to v2 and started getting maximum open cursors exceeded errors. I'm using database/sql.DB.Query via jmoiron/sqlx.DB.Queryx. When tested using prepared statements (as is also shown in the readme), cursor count stays normal.
I've done some code digging, but found nothing interesting yet. Before I go further, I'd like to know if (and why) prepared statements are recommended (or required).
Version: v2.4.4
Oracle version: 18.3

yes you are correct
here is the code for ExecContext
func (conn *Connection) ExecContext(ctx context.Context, query string, args []driver.NamedValue) (driver.Result, error) {
	stmt := NewStmt(query, conn)
	defer func() {
		_ = stmt.Close()
	}()
	return stmt.ExecContext(ctx, args)
}

the Stmt is closed before function return
but I can't do it for Query because this will stop fetching
to solve the problem I will add stmt.Close in DataSet.Close thus
rows, err := conn.Query(sqlText)
if err != nil {
    return err
}
defer func() {
   // here close will close also the stmt
    err = rows.Close()
}()
for rows.Next() {
    err = rows.Scan(...)
    if err != nil {
        return err
    }
}
return rows.Err()

I make new release that fix the issue

Tested and confirming this has fixed the issue. Thank you!

can you test again for v2.4.11 I make some modification

Tested and everything seems to work.


Warn if checking the freshness of build script is slow

This how no-op build looks for Servo:
λ $cr build
warning: checking freshness of build script for `selectors` took 106ms, consider using `rerun-if-changed`
warning: checking freshness of build script for `servo_atoms` took 105ms, consider using `rerun-if-changed`
warning: checking freshness of build script for `compositing` took 117ms, consider using `rerun-if-changed`
warning: checking freshness of build script for `script` took 172ms, consider using `rerun-if-changed`
warning: checking freshness of build script for `servo` took 106ms, consider using `rerun-if-changed`
    Finished dev [unoptimized + debuginfo] target(s) in 1.95 secs

I fear that as is, this feels a bit heavy handed: there's no way to suppress the warning and preserve current behavior (sans of printing rerun-if-env-changed=RANDOM_STRING, but that is a hack). Perhaps we should support something like rerun-if-changed=*, as an explicit opt-in into default behavior?

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Nice! I agree though that we may not want to do this just yet. At the very least though we could switch it to a warn! and offer debugging support for anyone debugging and/or profiling Cargo. Additionally the check here should probably actually check if rerun-if-changed was used, right?

At the very least though we could switch it to a warn! and offer debugging support for anyone debugging and/or profiling Cargo

Oh, one can already CARGO_PROFILE=1 and see the timings, so we can do nothing at all here :-)
Let's ask some random servo folks as well perhaps?
@nox, @SimonSapin : no-op builds of servo with Cargo  (without mach overhead) need about one second, which seems unreasonably huge. Are you bothered by this at all?  If you are, one of the major slow-downs happen because various build scripts in servo do not specify conditions for re-running them, and cargo conservatively assumes that they depend on all files inside the respective package. Because the number of files in servo is huge, calculating the aggregate mtime is slow. To fix it, you should modify build script to print rerun-if-changed=PATH line. Offending build scripts are listed in the PR description.
Do you think that Cargo should give some form of heads-up about this situation?

one second, which seems unreasonably huge

Even multiple times that would be on the noise level, since incremental builds (those where rustc runs at all) still take several minutes. This is so insignificant that I would not want to spent time trying to figure out the respective appropriate set of paths for rerun-if-change in each of the many crates with build scripts in Servo’s dependency graph. (Even if it’s only path dependencies in the repo, we have like 30 of those though I don’t know at hand how many of them have build scripts.)
If this is to warn by default, I’d strongly prefer to have an easy way to silence the warning without changing the behavior.

Ok, so looks like it is not something we should try to fix!


Different keep_attrs behaviour than xarray : coords attrs dropped

I have observed that the keep_attrs argument of xarray_reduce drops the coordinates' attributes, but this seems not to be the normal behaviour for xarray where only the data attributes are dropped.
Example here with a resampling call:
import itertools as it
import xarray as xr

ds = xr.tutorial.open_dataset('air_temperature')

# Iterate over all possible combinations
for use_flox, keep_attrs in it.product([True, False], [True, False]):
    with xr.set_options(keep_attrs=keep_attrs, use_flox=use_flox):
         out = ds.air.resample(time='YS').mean()
         # Check if attrs were preserved on `lat`
         print(f"{use_flox=}, {keep_attrs=} :  {out.lat.attrs == ds.lat.attrs}")

prints:
use_flox=True, keep_attrs=True :  True
use_flox=True, keep_attrs=False :  False
use_flox=False, keep_attrs=True :  True
use_flox=False, keep_attrs=False :  True

Thus, even when keep_attrs=False, xarray's resample preserves attributes on (untouched ?) coordinates. But, when flox is used, attributes are dropped.
I looked at the code of xarray_reduce and couldn't find the spot where it goes wrong... I see that xarray.apply_ufunc is used, but that function seems to preserve coordinate attributes even when keep_attrs=False, which I assume is what is being passed in the problematic case above. I would be happy to help, but I'm kinda lost right now...

I would jump in a debugger here: https://github.com/xarray-contrib/flox/blob/cbd52efe83d4f3ae23fb9d2bcc16ad718f740472/flox/xarray.py#L432
And see if the attrs are present n actual.lat and ds_broad.lat.

Thanks ! After some rabbit hole debugging I stumbled upon the real source of this issue and it's in xarray : https://github.com/pydata/xarray/issues/7602 .

Great work!


Chest: silk does not explode out

Very rarely it does (see on the left).

Strange, this just started happening for me also.


Can't build from source code on Ubuntu

I am getting the following error log when I try to build from source as instructed in the readme.
 I'll give that a shot.
On Fri, Jun 23, 2023 at 2:15 PM Meghan Denny @.***>
wrote:

what zig version is that exactly? also try adding -j1 to your build
command
—
Reply to this email directly, view it on GitHub
https://github.com/nektro/zigmod/issues/96#issuecomment-1604759020, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5G7TBEAOXWBQUGNWBN2AE3XMXTORANCNFSM6AAAAAAZR3XMSM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Now I get pages and pages of invalid built-in function errors. A sample:

ah now that is because you're using a master version newer than what zigmod currently supports. i will update as soon as i can but i am currently stuck on 0.11.0-dev.3620+c76ce25a6 due to https://github.com/ziglang/zig/issues/16056

the -j1 issue was fixed by https://github.com/nektro/zigmod/commit/ba84a39193b88ab27cf6bf948244bfedcebfde4f

I see! Haven't quite learned the process for version rollbacks just yet,
but once I figure that out I'll let you know if it works for me.
On Sun, Jun 25, 2023 at 1:58 PM Meghan Denny @.***>
wrote:

the -j1 issue was fixed by ba84a39
https://github.com/nektro/zigmod/commit/ba84a39193b88ab27cf6bf948244bfedcebfde4f
—
Reply to this email directly, view it on GitHub
https://github.com/nektro/zigmod/issues/96#issuecomment-1606220109, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5G7TBCMVKZKCAOIZ7AML7LXNCC5JANCNFSM6AAAAAAZR3XMSM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Reporting back, it's unclear to me how I'm supposed to roll back to a
previous iteration of 0.11.0. Doesn't seem to be any documentation for how
that's done.
On Sun, Jun 25, 2023 at 5:30 PM Andrew Miller @.***>
wrote:

I see! Haven't quite learned the process for version rollbacks just yet,
but once I figure that out I'll let you know if it works for me.
On Sun, Jun 25, 2023 at 1:58 PM Meghan Denny @.***>
wrote:

the -j1 issue was fixed by ba84a39
https://github.com/nektro/zigmod/commit/ba84a39193b88ab27cf6bf948244bfedcebfde4f
—
Reply to this email directly, view it on GitHub
https://github.com/nektro/zigmod/issues/96#issuecomment-1606220109, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5G7TBCMVKZKCAOIZ7AML7LXNCC5JANCNFSM6AAAAAAZR3XMSM
.
You are receiving this because you authored the thread.Message ID:
@.***>

this should be fixed now as of https://github.com/nektro/zigmod/commit/50ccfe3d1d84b4f27a4bb66fd4321623663a0163


Remove unused code and commands deprecated in 0.4.0.

Addressed some jshint suggestions
Moved lib/utilities/pipeline.js to lib/models/pipeline.js

You beat me to it @lukemelia. I started this very same thing last night ;)

@lukemelia I hope I didn't have an itchy trigger finger merging this.  It didn't have [WIP] in the title which you normally do and looked fine to me so I figured it was good to go.


[AKS] az aks create -h sample command for enabling cluster autoscaler incorrect

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
A clear and concise description of what the bug is.
az aks create -h returns the following as an example for cluster autoscaler which does not work
Cluster autoscaler requires --enable-vmss flag.. Please not that i have the aks-preview cli extension enabled.
Create a kubernetes cluster with preview api version and cluster autosclaler enabled.
    az aks create -g MyResourceGroup -n MyManagedCluster --kubernetes-version 1.11.2 --node-
    count 3 --enable-cluster-autoscaler --min-count 1 --max-count 5

To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Should be
Create a kubernetes cluster with preview api version and cluster autosclaler enabled.
    az aks create -g MyResourceGroup -n MyManagedCluster --kubernetes-version 1.11.2 --node-
    count 3 --enable-cluster-autoscaler --min-count 1 --max-count 5 --enable-vmss

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
Additional context
Add any other context about the problem here.

Fix is here:
https://github.com/Azure/azure-cli-extensions/pull/878


Chore : for use waitFor in constructor

waitFor function in constructor component
Description
I add waitFor in new instance of component for use that in constructor
Motivation and Context
To be connected with mithril's class documentation. By using classes, I prefer to do without opinait and use the constructor to declare my variables and to be able to use the useStrict mode of typescript.
How Has This Been Tested?
nom run test => ok
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation change

Checklist:

[X ] My code follows the code style of this project.
[X ] My change requires a change to the documentation.
[X ] I have updated the documentation accordingly.
[X ] I have read all applicable contributing documents.
[X ] I have added tests to cover my changes.
[X ] All new and existing tests passed.
[X ] I have updated the change log (if applicable).

Hello ! 👋
@isiahmeadows @StephanHoyer it's ok for you ? thk's

@StephanHoyer you still maintain this repository ?

What's the impetus for the change other than "nice to have"?

Hello, To get closer to what is documented here https://github.com/MithrilJS/mithril.d.ts#classcomponent.
It say : " // The constructor can be used in place of oninit" However, this is not possible if you want to give him the waitFor.


Feature/tag editing

Changes Unknown when pulling 2ac3e7505026952599d49527987e51a62ea8c287 on feature/tag-editing into ** on master**.

hell yeah


Webpack is not building production build.

My webpack.config.js is
	var path = require('path');
	var webpack = require('webpack');

	module.exports = {
		devtool: 'cheap-module-eval-source-map',
		entry: [
			'webpack-hot-middleware/client',
			'./src/index'
		],
		output: {
			path: path.join(__dirname, 'dist'),
			filename: `[name].bundle.js`,
			// `chunkFilename` provides a template for naming code-split bundles (optional)
			chunkFilename: `[name].bundle.js`
		},
		plugins: [
			new webpack.HotModuleReplacementPlugin(),
			 new webpack.optimize.ModuleConcatenationPlugin(),
			new webpack.DefinePlugin({
			'process.env': {
							'NODE_ENV': JSON.stringify('production')
				}
			}),
			new webpack.optimize.UglifyJsPlugin(),
			new webpack.optimize.CommonsChunkPlugin({
			name: 'vendor',
			filename: `[name].bundle.js`,
			minChunks (module) {
				return module.context &&
							 module.context.indexOf('node_modules') >= 0;
			}
		})
		],
		module: {
			rules: [{
				test: /\.js$/,
				use: ['babel-loader'],
				include: path.join(__dirname, 'src')
			},{
				test: /(\.css)$/,
				use: ['style-loader', 'css-loader']
			},{
				test: /\.(jpe?g|gif|png)$/i,
				use: ["file-loader"],
				include:path.join(__dirname,'src')
			}
		 ]
		}
	};

I set NODE_ENV to production but the output is not according to it as chrome extension is showing this

I have done this similar before and it normal work with my other sites.
My package.json is
{
  "name": "website",
  "version": "1.0.0",
  "description": "nativeiconbase.com",
  "author": "Rajan",
  "license": "",
  "scripts": {
    "prestart": "babel-node tools/startMsg.js",
    "start": "babel-node tools/Server.js",
    "build": "webpack"
  },
  "dependencies": {
  ....
    "babel-polyfill": "6.8.0",
    "body-parser": "^1.18.2",
    "react": "15.0.2",
    "react-dom": "15.0.2",
    "react-loadable": "^5.4.0",
    "react-native-view-shot": "^2.4.0",
    "react-redux": "4.4.5",
    "react-router": "2.4.0",
    "redux": "3.5.2"
  },
  "devDependencies": {
    "babel-cli": "^6.8.0",
    "babel-core": "6.8.0",
    "babel-loader": "6.2.4",
    "babel-plugin-react-display-name": "2.0.0",
    "babel-plugin-syntax-dynamic-import": "^6.18.0",
    "babel-preset-es2015": "6.6.0",
    "babel-preset-es2016": "^6.24.1",
    "html-webpack-plugin": "^2.30.1",
    "webpack": "^3.10.0",
    "webpack-bundle-analyzer": "^2.11.1",
    "webpack-dev-middleware": "^1.12.0",
    "webpack-hot-middleware": "^2.22.1"
  }
}

I run my website by npm start
I ask the same question on stackover-flow here https://stackoverflow.com/questions/52888556/webpack-production-mode/52891709#52891709
but did not get any help.

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.


WIP, test multi sriov with baremetal rebased

For testing purposes only
None

/uncc @ormergi @kbidarkar

will wait for the official PRs to test it


Fix CDO/NCO compatibility checks that rely on empty stderr

The stderr may contain information which do not constitute failure of the check:

nco_module_compat

cdo_module_compat

@teojgo Does this fail now also on Daint?

No, just in dom.


Fix Segfault on Mac

ovector in PCRE2 wrapper was pointing to the freed memory location. Need to copy values to results and free only after that.

Please, port to 2024.3 if it's valid for that code base

For 2024.3 is not valid.


ParticleContainer handles negative scale incorrectly (probably in webkit browsers only)

If webgl is enabled, bunny sprite in ParticleContainer is shown upside down correctly, as scale x/y is set to -1:
WebGL: http://jsfiddle.net/sergebat/nj0ptqtz/1/
However, with the following fiddle I see bunny with its head up even though scale x/y is set to -1 in Chrome and Safari:
Canvas: http://jsfiddle.net/sergebat/z88xxgfb/
Chrome version 43.0.2357.130 (64-bit) on OSX 10.9.5 at least). Version/mode: Pixi.js 3.0.7 - ✰ Canvas ✰
Image of what I see in the Fiddle, in case this is limited to particular Chrome/OS version:

I'd like to add that the same scenario fails completely on Firefox.
Fiddle that proves that negative values for drawImage are indeed not working as expected neither in Firefox nor in other browsers now:
http://jsfiddle.net/53tm9pvk/1/
It seems that we need to add check for either negative x or y scale, in addition to rotation not null here:
https://github.com/GoodBoyDigital/pixi.js/blob/master/src/core/particles/ParticleContainer.js#L234

Is this still active using the latest dev of v4?

OK, after a couple of years I managed to test it out! :)
Unfortunately, negative scale still does not work as of PIXI 4.7: http://jsfiddle.net/z88xxgfb/5/.

Its only for CanvasRenderer, right?

Correct, WebGL renderer works fine.

I'm really busy, you have to wait while someone else takes that or make PR. You can also show me which line is wrong and I'll make PR myself, I just dont have time to investigate that thing.

The problem is in the optimization path here:
https://github.com/pixijs/pixi.js/blob/dev/src/particles/ParticleContainer.js#L284
If I make rotation = 0.0001, all works fine. So I think that only doing optimization if scales are > 0 should do the trick. But unfortunately I am too bit busy to test this hands on immediately, sorry. :)

Ok, I get it :) Will do PR shortly.


Working on a fork to integrate all changes

I got a bit bored lately. There is so much work done here lately, so many fixes and improvements, but it is not possible to test it all together because it is all scatterd throughout various branches, nothing is merged. To solve #217, a bigger refactoring is neccessary (at least in my opinion), but it's not possible (or advisable) to do this with so many open big PRs. And I did not want to wait. So I just went ahead and started working on my own fork (https://github.com/lukasf/FFmpegInterop). I done the refactoring there, I improved various things along the way. I merged (or re-implemented) almost all open PRs. I have done some initial testing, things look good so far. Some of the files that did not work before now work fine.
These are some of the things I improved, in addition to the PRs:

clean, separate processing loops for compressed and uncompressed sample providers
improved handling of AVPackets and AVFrames (no unneccessary alloc/dealloc, no copy to stack)
correct end-of-stream handling to get about a dozen missing frames out of the decoder
zero-copy for many uncompressed audio streams
support for 3 different audio output formats
smart audio format preselection to avoid resampler where possible
multi threaded audio decoding
gapless audio handling (maybe more work is needed)
skip unneccessary first seek on file open
report stream size to ffmpeg (important one for broken files!)
improved video output format handling (prefer NV12 for most cases)
chroma location handling
introduced FFmpegConfig class to avoid parameter hell and allow more customizations

Maybe it is a good idea to work on this fork, instead of making even more branches? We can test all the changes there. When we have a good and stable state, and when @khouzam is back from hibernation, we could merge everything back into the official repo.
The next big thing I would like to do is multi audio streams (which again requires bigger rework of the whole thing).
I would invite anyone who likes the idea, to join my fork and test with their files. Who is interested? @mcosmin222 @reego-fr ?

I am all for it. Lately i have been working on getting audio effects support into the stream source, I will bring this feature into the fork, but I will need to refactor it because it was meant to work with the Microsoft build.

Cool, I sent an invite. Feel free to create branches directly on the fork.


Publish to chrome app store

Adds required images so we can publish to the store and get a stable extension id during development. Please excuse the developer art.
Add manifest key so extension id is stable during development.
@jiayliu

Thx! lgtm


Is T-X+T (T2M) dataset uploaded?

I see "[2023.10.01] 📢📢 Release the T2M instruction dataset." on the News, but I do not see the download link.
Is the dataset uploaded?

The dataset has been released. You can find it in /data/IT_data/T-T+X_data file.


Building with WebAssembly support

Appears that LLVM can be built with WebAssembly support. It's still experimental, but it would provide a nice option for building WebAssembly and would provide us an option to do this on any platform given we support LLVM on any platform.
ref: https://github.com/llvm-mirror/llvm/tree/master/lib/Target/WebAssembly

Also related to issue ( https://github.com/conda/conda/issues/7619 ) about targeting WebAssembly as a platform.

Addressing with PR ( https://github.com/conda-forge/llvmdev-feedstock/pull/42 ).


1PC check in advertiser use case

https://github.com/criteo/addressable-network-proposals/blob/d0c18b9a4c5b516ddb7d215b6a44a40ac78f3444/mvp-spec/operator-requirements.md?plain=1#L298
Should this not happen on the browser layer? Why is it happening on the advertiser side here while for the publisher it's happening on the browser?

This is not clear in the diagram or in the text, indeed.
In this case, the assumption is that the publisher is not using an operator backend client but only the frontend library.

If the publisher would also have a backend client, then it would be detected at the backend level.
If the advertiser would not have the backend client, then it would be detected only at the frontend level (in the browser, I mean).

I will update the doc to make this assumption more clear and let you close the issue if you think this is enough.
Thanks

Ok I better understand now. How can I see the updates related to this issue? (I'm still ramping-up on Github... and getting lost from time to time)

Right here on this page, you will notice that after my previous comment (3 days ago), there is an automatic line mentioning that I "added a commit that referenced this issue".
If you click on the link below (Rephrase operator design & requirements), you will be taken to the related changes.


SELECT * FROM table syntax

The query SELECT * FROM table don't work for me. In fact return nothing but SELECT field FROM table work. I try on SQL Server 2005 and 2008 R2.

SELECT * FROM table should work.
You probably have some column or value which fails.  Can you isolate which column/value it is?

I am not really sure but i guess one of the problem come from SMALLDATETIME type. The documentation says this type is a two bytes int (uint16 in golang?) but if i query a particular smalldatetime field the result is 0 or nothing. I try with int types and even string type.
e.g.: a is a smalldatetime in SQL server
db.Query("select a from table")
var a int,int16,uint... result 0
var a string show nothing
the same problem seems to be with uniqueidentifier type columns.

We have a test for smalldatetime: https://github.com/denisenkom/go-mssqldb/blob/master/queries_test.go#L60
and for uniqueidentifier: https://github.com/denisenkom/go-mssqldb/blob/master/queries_test.go#L62
and they are passing.
Can you provide minimal reproducible program, including minimal mssql schema?
—
Sent from Mailbox
On Tue, Apr 7, 2015 at 3:49 AM, geosoft1<EMAIL_ADDRESS>wrote:

I am not really sure but i guess one of the problem come from SMALLDATETIME type. The documentation says this type is a two bytes int (uint16 in golang?) but if i query a particular smalldatetime field the result is 0 or nothing. I try with int types and even string type.
e.g.: a is a smalldatetime in SQL server
db.Query("select a from table")
var a int,int16,uint... result 0
var a string show nothing
the same problem seems to be with uniqueidentifier type columns.
Reply to this email directly or view it on GitHub:
https://github.com/denisenkom/go-mssqldb/issues/97#issuecomment-90431468

Windows Server 2008 R2
BULK INSERT articole
FROM 'c:\articole.csv'
WITH
(
FIELDTERMINATOR =','
ROWTERMINATOR = '\n'
)
in the picture atached select various fields works but select * return
nothing.
thank you for help.
On Sun, Apr 26, 2015 at 5:37 PM, denisenkom<EMAIL_ADDRESS>wrote:

We have a test for smalldatetime:
https://github.com/denisenkom/go-mssqldb/blob/master/queries_test.go#L60
and for uniqueidentifier:
https://github.com/denisenkom/go-mssqldb/blob/master/queries_test.go#L62
and they are passing.
Can you provide minimal reproducible program, including minimal mssql
schema?
--
Sent from Mailbox
On Tue, Apr 7, 2015 at 3:49 AM, geosoft1<EMAIL_ADDRESS>wrote:

I am not really sure but i guess one of the problem come from
SMALLDATETIME type. The documentation says this type is a two bytes int
(uint16 in golang?) but if i query a particular smalldatetime field the
result is 0 or nothing. I try with int types and even string type.
e.g.: a is a smalldatetime in SQL server
db.Query("select a from table")
var a int,int16,uint... result 0
var a string show nothing
the same problem seems to be with uniqueidentifier type columns.
Reply to this email directly or view it on GitHub:
https://github.com/denisenkom/go-mssqldb/issues/97#issuecomment-90431468

--
Reply to this email directly or view it on GitHub
https://github.com/denisenkom/go-mssqldb/issues/97#issuecomment-96392486
.

--
Cu stima | Best regards,
George
geosoft1.github.io
ubuntu http://ubuntu.com | mikrotik http://mikrotik.com | golang
http://golang.org

Please upload c:\articole.csv too

i put it in the preview mail but i send you again.see attach.
On Fri, May 1, 2015 at 5:14 AM, denisenkom<EMAIL_ADDRESS>wrote:

Please upload c:\articole.csv too
—
Reply to this email directly or view it on GitHub
https://github.com/denisenkom/go-mssqldb/issues/97#issuecomment-98024463
.

--
Cu stima | Best regards,
George
geosoft1.github.io
ubuntu http://ubuntu.com | mikrotik http://mikrotik.com | golang
http://golang.org

I still didn't get it, I think github strips attachments.  Try creating a gist: https://gist.github.com/ and posting link here.

http://w3.geosoftnet.ro:8081/files/articole.zip

Poster abandoned the project this was for and no longer reproduce.