Add command to generate shell completion scripts

This PR adds a completion command to generate shell completion script #77
It uses the clap built-in way to do so.
Also, I don't think there's a straightforward way to complete projects yet. See https://github.com/clap-rs/clap/issues/1232
Example for zsh:
trackie completion zsh > /usr/local/share/zsh/site-functions/_trackie

Pull request checklist

[ ] The tests are passing locally as well as on CI
[ ] The changelog was updated (in CHANGELOG.md)
[ ] If commands were added/modified, the documentation was adapted

Thank you very much!


[Feature]: Support command line convars in fxrunner

Scope
Web
Feature Description
Add support for additional convars from the command line to be passed to the fxRunner component when starting the server.
Example:
FXServer.exe +set serverProfile "default" +set sv_licenseKey "xxxx" +set mysql_connection_string "xxxx"
Use Case
Working in multiple environments (development, production, etc) requires that environmental config variables be different between environments and so should not be committed to server.cfg. txAdmin's profile config may help in some cases, but in others, for instance developing with Docker, the profile would also be committed in the container image. Ideally, either environment variables and command line arguments would be used to provide environment configuration.
Proposed Solution
Passing all convars to fxrunner would probably be ideal, if able. Otherwise, something like +set extraArgs "+set sv_licenseKey 'xxx' +set mysql_connection_string 'xxx'" could be used to pass additional command line args to fxRunner
Additional Info
No response

I'm worried about conflicts, and how to handle tem. Mainly speaking about troubleshooting annoyances that can be caused by this.

Hey @shaunhardy, sorry for the delayed responde.
I decided against this feature due to:

Have not received any other request for this specific feature;
Worried about conflicts;
I'm not even sure if it's possible for me to get a list of convars that do not include default ones;
This is somewhat trivial to solve other ways, like instead of running fxserver, you can ran a bash script that adds those vars to a env.cfg and add it to txAdmin's Additional Arguments (Launch Parameters) as +exec env.cfg.


[CLOSED] Do not send email alerts for Drug Safety Update

 Issue by kalleth
Wednesday 17 December 2014 at 11:04 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/364

The Drug Safety Update is a monthly newsletter sent by the MHRA with custom
content (the full content of the document body). Therefore we're going to allow
the MHRA to send this out manually rather than alerting the user each time a
new one is published.

kalleth included the following code: https://github.com/alphagov/specialist-publisher/pull/364/commits

 Comment by james
Wednesday 17 December 2014 at 11:06 GMT

POW POW POW


Does jetcd support etcd v3.2.1 ?

I use jetcd with etcd version 3.2.1. Here is my scala code snippet:
val host = "http://<IP_ADDRESS>:2280" //a member of etcd cluster
  val client = ClientBuilder.newBuilder().setEndpoints(host).build()
  val kvClient = client.getKVClient
  val key = ByteSequence.fromString("k1")

  val value = ByteSequence.fromString("v1")
  kvClient.put(key,value).get()

  val resp = kvClient.get(key).get()
  println("resp:" + resp.getKvs.get(0).getValue.toStringUtf8)

  client.close()

I got the following log on etcd server console:

2017-07-03 19:09:22.784545 I | etcdserver/api/v3rpc: transport: http2Server.HandleStreams failed to read frame: read tcp <IP_ADDRESS>:2280-><IP_ADDRESS>:1670: read: connection reset by peer

And I can't find the key with etcdctl tool. Is there something I did wrong ?

Hey @baiwfg2. I was trying out jetcd with etcd v3.2.1 and had a similar problem. It seems that the problem was some misconfiguration in my etcd setup.
I was able to properly interact with etcd newest version through jetcd using a docker single node etcd. This is my docker run command:
export NODE1=<IP_ADDRESS>

docker run -d \
  -p 2379:2379 \
  -p 2380:2380 \
  --name etcd \
  quay.io/coreos/etcd:v3.2.1 \
  /usr/local/bin/etcd \
  --data-dir=/etcd-data \
  --name node1 \
  --initial-advertise-peer-urls http://${NODE1}:2380 \
  --listen-peer-urls http://${NODE1}:2380 \
  --advertise-client-urls http://${NODE1}:2379 \
  --listen-client-urls http://${NODE1}:2379 \
  --initial-cluster node1=http://${NODE1}:2380

And this is my Java code:
import com.coreos.jetcd.Client;
import com.coreos.jetcd.ClientBuilder;
import com.coreos.jetcd.KV;
import com.coreos.jetcd.kv.GetResponse;
import com.coreos.jetcd.kv.PutResponse;
import com.coreos.jetcd.api.RangeResponse;
import com.coreos.jetcd.data.ByteSequence;
import com.coreos.jetcd.data.KeyValue;

import java.util.List;
import java.util.concurrent.CompletableFuture;

public class Application {

  public static void main(String[] args) {
    try {
      Client client = ClientBuilder.newBuilder().setEndpoints("http://<IP_ADDRESS>:2379").build();
      KV kvClient = client.getKVClient();

      ByteSequence key = ByteSequence.fromString("test_key");
      ByteSequence value = ByteSequence.fromString("test_value");

      CompletableFuture<PutResponse> putFuture = kvClient.put(key, value);
      PutResponse putResponse = putFuture.get();

      CompletableFuture<GetResponse> getFuture = kvClient.get(key);
      GetResponse response = getFuture.get();
      List<KeyValue> kvs = response.getKvs();
      System.out.print("Response: ");
      for(KeyValue kv : kvs) {
        System.out.println(kv.getValue().toStringUtf8());
      }
    } catch(Exception e) {
      e.printStackTrace();
      System.exit(1);
    }
  }
}

One thing that helped out was testing if I could properly connect to the etcd node through etcdctl. Something like this:
ETCDCTL_API=3 etcdctl --endpoints=http://<IP_ADDRESS>:2379 put test_key test_value

@baiwfg2 jetcd supports etcd 3.2.1. does @embs's answer help you resolve your issue?

Yes. thank you @embs


[vault-operator] add OPERATOR_LOG_LEVEL setting to values for the vault-operator chart

Is your feature request related to a problem? Please describe.
It appears that the vault-operator (as installed by the Helm chart) has hard-coded the log-level to debug.  https://github.com/banzaicloud/bank-vaults/blob/1b3a8b7480c061866616a3563838d2214682479d/charts/vault-operator/templates/deployment.yaml#L50-L51
This is producing a lot of unnecessary log data for us.  It would be better to make this configurable.
Describe the solution you'd like
Expose OPERATOR_LOG_LEVEL in the values.yaml of the Helm chart for vault-operator so it can be changed as needed by end users.
Describe alternatives you've considered
I haven't tried this yet, but it may be possible to use a kustomize overlay to patch the rendered Helm chart with the desired log level.  Though having this as a configurable part of the Helm chart would be easier.

any update on this?


(Server-816) Display unknown extensions as Base64

This PR does two things.

There was a bug when attempting to decode some a General Name values, specifically in the case where an IP address or an OID. Previously an exception was being thrown. Now they are properly decoded.

Now unknown values are returned as Base64-encoded strings, preceded by base64: instead of byte arrays. Base64-encoded data is much easier to print to the screen and examine.

I'm basically :+1: on this beyond a couple of minor questions.  Probably shouldn't close the JIRA ticket for this out completely until this gets into a jvm-ssl-utils release and Puppet Server is bumped up to a new version of jvm-ssl-utils that uses the changes.  Would definitely like to get @nwolfe's take on these changes.

Everything should be addressed now.

The principal has been fulfilled.

:+1:

:+1:


AWS subnets are not tagged by default

Relevant issue https://github.com/kubernetes/kubernetes/issues/28586

Seems like dropping cluster in "default" subnets is a bad idea and we need avoid them (and tag created subnets).


chore(transform-lesson-overview): wires up the lesson overview page LESQ-102

Description

Wires up the Lesson Overview Page

Issue(s)
Fixes # LESQ-102
How to test

Go to https://deploy-preview-1755--oak-web-application.netlify.thenational.academy

Screenshots

look (delete if n/a):

Checklist

[x] Added or updated tests where appropriate
[x] Manually tested across browsers / devices
[x] Considered impact on accessibility
[x] Design sign-off
[x] Approved by product owner

:tada: This PR is included in version 1.203.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


documentation using jsdoc3

A lot of documentation is lost and it's difficult to see what is supposed to be what. JSDoc3 would allow us to doc props and params and mixins and what not.

Forked JSDoc3 and created enhancement issue #1 here:
https://github.com/obimod/jsdoc/issues/1
This would allow the documentation of AOP implementations.


[File Connector][Append]Provide an example of how we can append the text to an exact position

Description:
Doc: https://ei.docs.wso2.com/en/latest/micro-integrator/references/connectors/file-connector/file-connector-config/
It is better if we can provide the details on how to append the text and the behavior if it, and which input that we need to provide.

The Integration Studio properties view help tip tells about the property. Hence closing this ticket.


Initial Checkin for Wasm plugin

cc @bryancall
as discussed, this is the wasm plugin. Please take a look at how the library license is included.

Please note that the contents inside /lib directory are directly coming from the proxy-wasm repo.
And I accidentally run clang-format on them so i need to undo that.

Will there be Au tests for this feature?

Probably we can add au tests later.
For now, it is just the initial checkin

[approve ci autest]

[approve ci fedora]


Git commands are slow

Issue Type: Performance Issue
git actions like syncing or commiting to my repository (gitlab) are really slow. It only occurs on my laptop. I've already updated to the latest version of VSC and git (2.17.1.windows.2).
At my PC at home it takes about 3 seconds to sync with the repository, here it takes about 30s.
VS Code version: Code 1.24.0 (6a6e02cef0f2122ee1469765b704faf5d0e0d859, 2018-06-06T17:35:40.560Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2904)

GPU Status
2d_canvas: unavailable_softwareflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: unavailable_offnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarevpx_decode: unavailable_softwarewebgl: unavailable_offwebgl2: unavailable_off

Memory (System)
7.85GB (3.77GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    3	   134	  4192	code main
    0	    67	  7704	   shared-process
    0	    76	  8816	   shared-process
    0	   228	  8840	   window (website - Visual Studio Code)
    1	    62	  5232	     extensionHost
    0	     5	  7080	       "C:\Program Files\Git\cmd\git.exe" symbolic-ref --short HEAD
    0	     9	  3384	         console-window-host (Windows internal process)
    0	    38	  7920	       electron_node jsonServerMain.js
    0	    11	  6648	     electron-crash-reporter
    0	    32	  7220	     terminal
    0	     6	  3448	       winpty-process
    0	     9	  3780	         console-window-host (Windows internal process)
    0	    62	  5056	         C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
    0	    14	 11608	     watcherService
    0	     9	  7208	       console-window-host (Windows internal process)
    0	    27	 12836	   gpu-process

Workspace Info
|  Window (website - Visual Studio Code)
|    Folder (website): 180 files
|      File types: ts(80) html(27) scss(27) png(14) js(11) json(8) ico(4)
|                  xlf(2) gitignore(1) css(1)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1);

Extensions (1)

Extension
Author (truncated)
Version

vscode-language-pack-de
MS-
1.24.3

Interesting. We've been having a couple of other people with the same issue, but they have fixed it by updating to the latest git. Can you uninstall and reinstall the latest Git version? Let's see if that changes anything.

I just uninstalled and reinstalled git but it did not solve the problem...
Still really slow.

Do you have an Antivirus? If so, does it get better if you temporarily disable it?

Yes, I have eset nod32, but even with this being diabled it took about 30 seconds. So antivirus should not be the problem.
commit and push via command line are really fast (it takes about a second). It's just the vscode options that take forever.
Same with creating a new branch. it takes about 10s before I can see my new branch at the bottom and the little cloud-icon to push it appears.

Try to go through other similar issues, see if you find something which fixes it for you: #3873, #34898, etc

Too bad... let me know if you figure it out, I'd be very happy to know! I wish I could reproduce it and investigate it on my machine...


Speed up tests by moving IAP stubbing to the relevant specs

This PR improves test runs for spaceship by around 15% on my machine. From 77 seconds, to around 65 seconds.
The stubbing method itc_stub_iap has 21 calls to stub_request which would get executed on every single example. These stubs were only needed in the specs relevant to IAP. I am sure it can be scoped further, but it's probably not such an easy win.

Couldn't this also be worth to be done to the other stubbings?

Yes. From my preliminary benchmarks, these were the most bang for the buck.
Some stubbings like login, etc are used a lot more.
On Thu, Mar 21, 2019 at 16:23 Jan Piotrowski<EMAIL_ADDRESS>wrote:

Couldn't this also be worth to be done to the other stubbings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/pull/14208#issuecomment-475388166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAM8C-ZIRuAWo-4jPjRRonvPM71K4S6ks5vY-pXgaJpZM4anqef
.


Add make_header, read_header and write_header functions

See also: https://github.com/dwavesystems/dimod/pull/839/files#r650208852

Codecov Report

Merging #842 (0b2b4f0) into main (4fd10b0) will increase coverage by 0.03%.
The diff coverage is 96.15%.

@@            Coverage Diff             @@
##             main     #842      +/-   ##
==========================================
+ Coverage   88.56%   88.59%   +0.03%
==========================================
  Files          71       71
  Lines        6068     6058      -10
==========================================
- Hits         5374     5367       -7
+ Misses        694      691       -3

Impacted Files
Coverage Δ

dimod/discrete/discrete_quadratic_model.py
93.87% <88.88%> (+0.57%)
:arrow_up:

dimod/serialization/fileview.py
89.18% <96.42%> (+1.58%)
:arrow_up:

dimod/binary/binary_quadratic_model.py
90.10% <100.00%> (-0.01%)
:arrow_down:

dimod/constrained.py
88.02% <100.00%> (-0.31%)
:arrow_down:

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 4fd10b0...0b2b4f0. Read the comment docs.


Shutter close API

Fixes #35

I am not sure why you need a persistent std::string, two persistent char* and a heap allocated char* to do this. Can you not just read out the config into a (local) std::string, concatenate the position to the command prefix and then copy that string into a (global or class member) char*?


fixes

use model service for health check
update config schema validation config file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 23.254%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1132

Relevant Lines:
4868

💛  - Coveralls


Intellisense shows "mousewheel" as an applicable event

mousewheel should be removed from Javascript's intellisense as it is deprecated and only supported in IE6, Chrome 1, Opera 10, Safari 3, and surprisingly IE Edge. If not removed then it should have "(deprecated)" next to it so people don't accidentally use it instead of "wheel".

VSCode Version: 1.10.2
OS Version: Ubuntu 16.10

Steps to Reproduce:

type "window.addEventListener('mouse..." and notice "mousewheel" as an available option.

https://developer.mozilla.org/en-US/docs/Web/Events/mousewheel

I read the compatibility table as "supported by all major browsers except Firefox".

This issue was moved to Microsoft/TypeScript#15073


Project generated with Angular CLI ng new command fails e2e test out of the box if you use the --prefix option (angular-cli: 1.0.0-beta.11-webpack.2)

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Linux Ubuntu 16.04

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:

$ ng --version
angular-cli: 1.0.0-beta.11-webpack.2
node: 6.5.0
os: linux x64
3 Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
I generated a new project with angular-cli 1.0.0-beta.11-webpack.2 using the command
ng new pftest --prefix pft.
Then I successfully ran ng serve and ng test, but encountered a failure when I ran ng e2e.
4 The log given by the failure. Normally this include a stack trace and some
more information.
Results of command ng e2e:
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
><EMAIL_ADDRESS>pree2e /home/john/projects/pftest
> webdriver-manager update
selenium standalone is up to date.
chromedriver is up to date.
><EMAIL_ADDRESS>e2e /home/john/projects/pftest
> protractor "config/protractor.conf.js"
[14:36:55] I/direct - Using ChromeDriver directly...
[14:36:55] I/launcher - Running 1 instances of WebDriver
Spec started
  pftest App
    ✗ should display message saying app works
      - Expected 'app works!' to equal 'pft works!'.
**************************************************
*                    Failures                    *
**************************************************
1) pftest App should display message saying app works
  - Expected 'app works!' to equal 'pft works!'.
Executed 1 of 1 spec (1 FAILED) in 0.905 sec.
[14:36:56] I/launcher - 0 instance(s) of WebDriver still running
[14:36:56] I/launcher - chrome #01 failed 1 test(s)
[14:36:56] I/launcher - overall: 1 failed spec(s)
[14:36:56] E/launcher - Process exited with error code 1
npm ERR! Linux 4.6.0-040600-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "e2e" "--" "config/protractor.conf.js"
npm ERR! node v6.5.0
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>e2e: protractor "config/protractor.conf.js"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>e2e script 'protractor "config/protractor.conf.js"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the pftest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor "config/protractor.conf.js"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs pftest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls pftest
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/john/projects/pftest/npm-debug.log
Some end-to-end tests failed, see above.
5 Mention any other details that might be useful.
From e2e/app.e2e-spec.ts:
  it('should display message saying app works', () => {
    page.navigateTo();
    expect(page.getParagraphText()).toEqual('pft works!');
  });
After encountering this error with a new project and the prefix 'fam', I reproduced it by starting a brand new project (named pftest) with the ng new command and the --prefix option, using the prefix pft.

Good catch, we'll get on it.

I managed to fix it by changing app to <%= prefix %> when generating the initial component. Also I changed its spec (app.component.spec.ts) so it would pass too.
I'm submitting a PR right now.

Can be closed, since the fix has been merged.

Hello, i had the same issue...
I solved this issue running

su
Password: mypass
npm install -g angular-cli

Then i stayed in superuser and created the angular project

cd Desktop
ng new exampleApp


Include _ARRAY_DIMENSIONS metadata?

Ref https://ngff.openmicroscopy.org/0.4/#image-layout

├── .zgroup               # Each image is a Zarr group, or a folder, of other groups and arrays.
├── .zattrs               # Group level attributes are stored in the .zattrs file and include
│                         # "multiscales" and "omero" (see below). In addition, the group level attributes
│                         # must also contain "_ARRAY_DIMENSIONS" if this group directly contains multi-scale arrays.

Should we include this additional information?

Ref:

https://github.com/ome/ngff/issues/217

Closing, as of https://github.com/ome/ngff/issues/217#issuecomment-1766214155


stop ohmyzsh update prompts

https://stackoverflow.com/questions/11378607/oh-my-zsh-disable-would-you-like-to-check-for-updates-prompt


Channel balance should be in millisatoshis

Background
Channel in gRpc (https://api.lightning.community/#channel) contains balance but in satoshis instead of millisatoshis.
Your environment

version of lnd: 0.5.2-beta commit=v0.5.2-beta
which operating system: Linux lnd-tst-02 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
version of bitcoind: Bitcoin Core RPC client version v<IP_ADDRESS>-g4b4d7eb255
proto built for Java

Steps to reproduce
Call ListChannels gRpc method.
Expected behaviour
Local and remote balance should be msat values
Actual behaviour
Local and remote balance are in satoshis

The documentation is only tracking the master branch at the moment, not the v0.5.2 release.

But documentation also do not contains millisatoshis for channel amounts

That's how it currently is at the RPC level, so not an issue with the documentation.


Add "extract" function for fields

Fields should allow for a custom method to control how data is extracted from the model when IvhModel#extract is used.

This can probably just be an extract hook on the model class itself.


Feature request: add metrics endpoint

It would be cool if we could add a metrics endpoint that we can scrape with prometheus.
I have no clue how difficult would be but let's try to start with exposing a metrics endpoint that exposes the following metric:

jetspotter_aircraft_spotted

The following labels should be on the metric:

type
icao
registration

If we can get it to work, we can build a dashboard in grafana that displays the aircraft that you spotted.
Make it togglable and turn it off by default.

Closing as it has been added:
https://vvanouytsel.github.io/jetspotter/dashboards/


BUG: acbuild ignores proxy

http.ProxyFromEnvironment
see
https://github.com/appc/acbuild/blob/master/registry/fetch.go#L357
compared to
https://github.com/appc/spec/blob/master/discovery/http.go#L58

It looks like the http.DefaultTransport sets the proxy to be ProxyFromEnvironment, so I should just need to do that when the insecure flag is set and I don't use the default transport. I'll make a PR.

@Andrei-Pozolotin any chance you'd be willing to see if https://github.com/appc/acbuild/pull/239 fixes this for you?

@dgonyeo

thank you for the PR

test result: it does partially resolve the issue

remaining problem is: Proxy: http.ProxyFromEnvironment
should be applied regardless of --insecure /  r.Insecure, in other words: "proxy always applies"
https://github.com/appc/acbuild/blob/master/registry/fetch.go#L363

another issue came up, which has to do with quay.io servers,

for example, a portion of build script:

acbuild dep add quay.io/coreos/alpine-sh

produces the following proxy log:

2016-Jul-18 20:47:16    211 <IP_ADDRESS> TAG_NONE/200 0 CONNECT quay.io:443 - HIER_DIRECT/<IP_ADDRESS> -
2016-Jul-18 20:47:16    123 <IP_ADDRESS> TCP_MISS/302 719 GET https://quay.io/coreos/alpine-sh?ac-discovery=1 - HIER_DIRECT/<IP_ADDRESS> text/html
2016-Jul-18 20:47:16     79 <IP_ADDRESS> TCP_MISS/200 17961 GET https://quay.io/repository/coreos/alpine-sh?tag=latest - HIER_DIRECT/<IP_ADDRESS> text/html
2016-Jul-18 20:47:16    144 <IP_ADDRESS> TAG_NONE/200 0 CONNECT quay.io:443 - HIER_DIRECT/<IP_ADDRESS> -
2016-Jul-18 20:47:16    134 <IP_ADDRESS> TCP_MISS/302 1127 GET https://quay.io/c1/aci/quay.io/coreos/alpine-sh/latest/aci/linux/amd64/ - HIER_DIRECT/<IP_ADDRESS> text/html
2016-Jul-18 20:47:16    174 <IP_ADDRESS> TAG_NONE/200 0 CONNECT quay-registry.s3.amazonaws.com:443 - HIER_DIRECT/<IP_ADDRESS> -
2016-Jul-18 20:47:18   1174 <IP_ADDRESS> TCP_MISS/200 2652298 GET https://quay-registry.s3.amazonaws.com/sharedimages/5fed0187-c814-4eee-b340-cc7f26230872/layer?Signature=QZAkBUt4ly%2FDsHbikHuGMrNQcAI%3D&Expires=1468892898&AWSAccessKeyI

with response headers like:

< HTTP/1.1 200 OK
< Server: nginx/1.10.0 (Ubuntu)
< Date: Tue, 19 Jul 2016 02:32:28 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 78998
< X-FRAME-OPTIONS: DENY
< Cache-Control: no-cache, no-store, must-revalidate
< Set-Cookie: session=eyJfY3NyZl90b2tlbiI6eyIgYiI6IlpIRnpaRUZ1SzNGa2JUbHdNa2xHUWpOYVdtVklORmRMVG5wc1luWjFTVFl2ZFhGaEwySkdXRXQ0YkM4cmRIVm5lUzlFWmpaVFMzTlpTM0pTTm1SbVNRPT0ifX0.Cm8ivA.3I7V-56NSwDrPk_mgIQy95qH2ec; Secure; HttpOnly; Path=/
< X-Frame-Options: DENY
< Strict-Transport-Security: max-age=63072000; preload
< X-Cache: MISS from proxy
< X-Cache-Lookup: MISS from proxy:3128
< Connection: keep-alive

where

Cache-Control: no-cache, no-store, must-revalidate

means that quay/amazon produces transient resources, and makes proxy useless for the quay.io images

this happens for both tag=latest and tag=some-version-number

surely we can hack around this by header override on the proxy, but is it a feature or a bug?

re: quay.io servers:
one can make it work with squid 3.5 / store_id:
http://wiki.squid-cache.org/Features/StoreID
here is minimal working config
https://gist.github.com/Andrei-Pozolotin/0b65b5ab5813dca94886c1ebe9158a18
probably should document proxy setup for all sites: acbuild, rkt, quay.io

remaining problem is: Proxy: http.ProxyFromEnvironment
should be applied regardless of --insecure / r.Insecure, in other words: "proxy always applies"

Did what I wrote not work without the insecure flag? Weird, because the http.DefaultTransport does set http.ProxyFromEnvironment: https://golang.org/src/net/http/transport.go
I've pushed a change that always sets it now.
Also I'd be nervous about overriding headers, so probably better to just document how to setup a proxy for this stuff. As it touches rkt, acbuild, and quay.io, I'm not entirely certain where it should go. Adding it to acbuild is a start though, so if you don't mind I could at the very least pull in your minimal configs.
I'm also not familiar with squid at all myself, so if you have the time to write a short markdown thing explaining it I'd love to have that in acbuild docs.

I've pushed a change that always sets it now.

your change works, thank you

because the http.DefaultTransport does set http.ProxyFromEnvironment

not sure why this is needed, probably should comment code that proxy needs extra testing

not familiar with squid at all myself, so if you have the time

I can contribute to the following:
how about if you setup public demo build project somewhere?
which would need to:

spawn squid container, then
spawn build container to run acbuild against quay.io via squid
spawn runtime container to run rkt against that image via squid
then result would be self documenting on every stage
and documentation will go in relevant configuration files


Represent ResearchStudy Summary Information

We need a plan to address the fields in #36 and add them to the IG.

https://github.com/NIH-NCPI/NCPI_use_case_tracker/issues/28

Base Logical Object Model for dbGaP.
Base logical model.pdf


1BB4

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
1BB4

Source
Vaaran Bhai Gurdas Ji

Page
25

Line
Asur BBIKxu Bgqu hY; ibdru su ivKlIpq srxweI [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

Correction:
ivKlIpq ≠ ivKlI piq
Proof:
Vaaran Bhai Gurdaas Ji | November 2011 | Shamsher Singh Ashok | SGPC, Sri Amritsar
Image:


add a completed subcommand

I notice that I tend to archive completed todos immediately.  It would be nice to look back at what was checked off today.
todolist l completed today
todolist l completed this week

this should be marked as done as per #82


Fidesctl needs to be able to run in a local-only mode

Right now, even if all of the resources are available locally, the apply and evaluate commands will still call out to a server. This needs to be updated so that if all resources exist locally the server won't be checked, or some kind of flag prevents it and will error if there are missing resources
This is also critical to letting us remove database/server components and do a lightweight fidesctl install

blocks #186


ALB as a k8s API endpoint load balancer

Extracted from https://github.com/kubernetes-incubator/kube-aws/issues/598#issuecomment-297921158

In the meantime, I'm going to add apiEndpoints[].loadBalancer.classic which defaults to true, can be set to false  to turn it into an ALB.
Probably in v0.9.8, classic would start defaulting to false - ALB by default.

Let me note that in the future apiEndpoints[].loadBalancer.targetGroups[].arn could be added to reuse existing an ALB - not provision ELB nor ALB for an endpoint but just add controller nodes to target group(s).
This supports similar use-cases like one with specifying apiEndpoints[].loadBalancer.id to reuse an existing ELB.
Would anyone like to work on it?

"ALB as a K8S API load balancer" seems to be not a realistic option at the moment - please see my comments and the relevant discussion in https://github.com/kubernetes-incubator/kube-aws/pull/651
If no one would use it, I'm going to abandon the PR (at least for now).

Hi @Vrtak-CZ @gleeb @camilb, thanks for expressing your interests on this featur!
Could I have your thoughts?
Would you use ALB as API load balancer even if it degrades security?

Hi @mumoshu I'm forgot information about missing pass-through option for TLS connection in ALB. So for me classic ELB is better for security reasons.

@Vrtak-CZ Thanks for the confirmation! Yes, it is a major missing feature affecting us now.
On the other hand, I began to believe ALB as a L7 loadbalancer doesn't provide us an additional benefit over a classic ELB when what we want was L4(=tcp pass-through) - ALB will never support the pass-through thing.
The next best feature could be supported by ALB would be ALB filling a certain HTTP header with the client TLS cert so that apiserver could be modified to identify and authenticate the client with it but.. it will never happen as long as there's still ELB available.

Hi @mumoshu looks like the classic ELB fits better in this case.  At the moment ALB makes more sense when you have multiple backends, something like the alb-ingress-controller from CoreOS to expose several services using a single ALB.

Closing this issue until ALB by any chance start to support tls pass-through

Good news! https://aws.amazon.com/blogs/aws/new-network-load-balancer-effortless-scaling-to-millions-of-requests-per-second/

@Vrtak-CZ , created https://github.com/kubernetes-incubator/kube-aws/issues/937


Styling Broken on Account Request Page

Summary
On the account request page (https://humanessentials.app/account_requests/new) when a user clicks on the I am an Essentials Bank.. radio button it expands to borders outside the page. This is making a difficult user experience for new folks signing up.
Things to consider
We use the devise layout on the account request page -- it may need a custom layout.
Criteria for Completion

[ ] Layout doesn't overlap the page!
[ ] Works as before and all test pass

Hi Sean! I'm new to contributing to open source and I'd like to give this a try. Can this be assigned to me?
I looked into this locally. It seems like this can be corrected with two additional CSS attributes on login-page--user under custom.scss:
  background-attachment: fixed;
  flex-flow: wrap;

It doesn't affect the users/sign_in view and expands the page (with the background smoothly reaching the bottom of the screen) only when selecting the first radio button option on /account_requests/new.
Let me know if this seems like a viable solution -- otherwise happy to discuss other solutions. Thanks!

@tokyodaruma hey there, I think that sounds good. I can assign you :)


asp-append-version ignored when running on Mono 4.2 or 4.3

The <img>, <link> and <script> tag helpers mostly work on all platforms. However asp-append-version does nothing when running on Mono 4.2 or 4.3.
Since FileVersionProvider contains the only Uri.TryCreate() call in the MVC product code, the root cause is likely aspnet/External#21. Rather than waiting for a Mono fix, should work around the issue e.g. by confirming the new Uri has an "http" or "https" scheme.
Note it's been almost two months since @sornaks filed the Xamarin bug for aspnet/External#21. And we don't know when this bug will reach the Mono alpha channel.
Further the FileVersionProvider class looks fragile compared with FilePathResult. Though the notion of "absolute" is different for the two classes, they should probably share some of the same smarts.

I'm inclined not to fix this as I think the Mono behavior is incorrect.
What is the issue with FileVersionProvider and FilePathResult? Sounds like a separate issue.


Show labels and units of measurement automatically for plots by default

Some plots (like viz.map or viz.ts_cluster) don't show label names and units of measurement automatically, leaving that to the user.

Options as I see it:

Create a new type, say Outcome, which provides an interface to all metric/performance results, including relevant metadata.
This new type will otherwise behave identically to NamedDimsArray/AxisKey types.

Rewrite all metric/performance/analysis methods to accept a function, and use the metadata included in Metric types to determine auto-magically what to include/display in the visualizations.

There may be a third option that is inbetween these two extremes but I think the first is our cleanest way forward.
Unfortunately, the first option also requires rewrite of all visualization functions as well.


update for deprecated navigator.getUserMedia

updated
navigator.getUserMedia
to
navigator.mediaDevices.getUserMedia

Thanks for submitting a pull request :rocket: @JustinaPetr will take a look as soon as possible ✨


Unable to set data on Json field

Bug description
When trying to set JSON data on a field that is of type JSON I'm receiving the following error message.
Error parsing GraphQL query: query parse error: Parse error at 17:7
Unexpected `"version"[StringValue]`
Expected `Name`, `:` or `}`

And if I set data to an empty object ({}) I get this error:
Failed to validate the query `Error occurred during query validation & transformation:
Mutation (object)
  ↳ createOnePost (field)
    ↳ data (argument)
      ↳ PostCreateInput (object)
        ↳ data (field)
          ↳ Value types mismatch. Have: Object({}), want: Scalar(Json)` at `.Mutation.createOnePost.data.PostCreateInput.data`

Prisma information

...
model Post {
  id         Int    @default(autoincrement()) @id
  author     User   @relation(fields: [authorId], references: [id])
  authorId   Int    @map("author")
  title      String
  data       Json
}
...

//This generates the first error message
const post = await client.post.create({
  data: {
    author: {
      connect: {
        id: 1
      }
    }
    data: {
      version: 1,
    },
  },
});

//This generates the second error message
const post = await client.post.create({
  data: {
    author: {
      connect: {
        id: 1
      }
    }
    data: {},
  },
});

Environment & setup

OS: Mac OS
Database: PostgreSQL
Prisma version: 2.0.0-beta.4
Node.js version: v12.14.1

Hi, I have such problem. Here what I found.
If we create the field as String (not Object) it works.
data: '{ "version": 1 }'
and then findOne / findMany returns the field as String too: data: '{ "version": 1 }'
I think the problem is related to the typescript type.
Is it expected behaviour when we should create and get the field as String instead of Object?

This seems to be fixed in the latest release so closing this issue


Added the Perform (juggling) skill

Added the juggling skill for the Juggler archetype of the Bard.

I take it the Juggler archetype needs this? I'll review that first.
If I do accept this, it also needs adding in a whole bunch of other places as well, such as the script for generating a master list of string for translators to work on. Sadly, the project isn't very DRY when it comes to the list of Perform skills.

I'm sorry, I'm from Canada and I'm not sure what DRY stands for.

My fault, that's a bit of programmer's jargon. It stands for "Don't Repeat Yourself". The idea is that, when writing a program where the same value (such as a fixed number or the name of something) is needed in multiple places, you should have one definitive place for it, and all the other places should refer to that one. That way, if you need to change it, you only have to change it once; if you got something wrong and need to fix it, you only need to fix it once; etc. The opposite backronym, WET stands for "Written Every Time".
This project has grown up very organically, though, with bits of it written using all sorts of different programming languages and other tools, so there's no real sharing of information between them. Hence I have the skill lists repeated in a bunch of different places.

Looking at the text of the Juggler, I can't find anything that says it needs Perform (juggling) as skill. None of the abilities hang off it. And for the majority of bards, putting ranks into juggling would be wasted (for the purposes of Versatile Performance). So while you're free to write any unique Perform, Profession, Craft and Knowledge skills you wish into the list for your own character, I don't believe this belongs in the main list for everybody.

I was wondering about that, and I'm fine with it.
Thanks for looking at it.
On Feb 1, 2017 6:02 PM, "Marcus Downing"<EMAIL_ADDRESS>wrote:

Looking at the text of the Juggler, I can't find anything that says it
needs Perform (juggling) as skill. None of the abilities hang off it. And
for the majority of bards, putting ranks into juggling would be wasted (for
the purposes of Versatile Performance). So while you're free to write any
unique Perform, Profession, Craft and Knowledge skills you wish into the
list for your own character, I don't believe this belongs in the main list
for everybody.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dyslexic-charactersheets/website/pull/1#issuecomment-276823917,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYO3eZoZLHXsbqFCXZer8LWYzWYi-mMZks5rYRz8gaJpZM4LyJ6F
.


Unit coercion

Should map Unit to void if appropriate

Keep old Unit methods as synthetic and add new void methods.

Keep old Unit methods as synthetic and add new void methods.


Correct component function name for ChevronRIght

Simple change to fix the component function header. Doesn't change functionality, just a nitpick.

Thank you! Embarrassed I missed that! 😃


[question] query.All no longer return sql.ErrNoRows?

ive tested and found out query.First does return sql.ErrNoRows if no record matches,
but previously .All does the same thing if no record matches.
Is this the new behaviour?

I don't remember such a thing. Do you have a version of Pop where you saw this behavior?


edited atijagatī

@danbalogh : I've made the necessary changes to an item imported from Zaki's data. It has the pattern <seg type="xml">----+--+-----=</seg>. Please check.
@zakariyaaminullah : it was misleading, in your MA thesis, to make no difference between names of specific meters and names of classes of meters. The stanza 7.2 in your edition https://erc-dharma.github.io/tfd-nusantara-philology/output/critical-edition/html/DHARMA_CritEdCandrakirana.html follows a pattern unrecorded by Zoetmulder whose specific name seems not to be known. On how to encode such cases, see EGC <IP_ADDRESS>. Concretely, you should change @met="atijagatī" to @met="----+--+-----=" in your code to get a proper display.

Checked, made a small correction in the gaṇa code, removed the bars, and verified that it is not in Apte.

@zakariyaaminullah : when you have acted upon a github issue, you should close it. go to https://github.com/erc-dharma/project-documentation/issues/167 and press the close button.


Add glossary.md

A new file glossary.md, which is a first attempt at compiling and clarifying the jargon in the spec.

Regarding "repo regenesis" (https://github.com/ethereum-optimism/optimistic-specs/pull/40), I suggest we introduce a glossary and everyone introduces new definitions in it as needed.
Let's also immediately get into the habit of linking terms to their glossary page entry.

Merging this in advance of resetting the repo. Let's refer back here for the extra comments when importing things!


Cache insights not available within Application Insights and APIM Analytics

I have an APIM and Redis instance, the latter connected as "Default" cache. Added some cache policies, with explicit cache-store-value caching-type="external" configured. I can see the first request was served from backend, the next requests where served from cache: faster response, and via test inspector tracing a confirmation that response was served from cache (no request to backend). So far good.
Within the metrics of the Redis instance, I can see an increase of "cache hits. So far so good.
When I go back to Azure portal > APIM > Analytics blade, the Cache graph still doesn't show anything, also after some time.
Also, going to the Application Insights instances connected to my APIM, all requests still have the value "None" for the customDimensions["Cache"].

How do I get the cache graph working within the Analytics blade (APIM)
How can I gain insights in which requests were served from cache within AI (requests)

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

ID: ad05f88c-be94-58f8-b05c-a4a1a102e24f
Version Independent ID: 8f58d4b1-73f7-41f2-a15b-fe71d8bf82b0
Content: Add caching to improve performance in Azure API Management
Content Source: articles/api-management/api-management-howto-cache.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

Thank you for your feedback! We will review and update as appropriate.

@mike-urnun-msft I have configured APIM to use Redis Cache as external cache. I can confirm that - within Application Insights connected to APIM - customDimensions["Cache"] remains None. So I expect that it does not dependent on the type of cache store that is being used.

Hi @markdebruijne
I've gone through the steps and I wasn't able to reproduce this issue, screenshot below:

As our next step, given that this channel is more for driving improvements towards MS Docs and the issue that you've encountered appears to be unrelated to this documentation, we invite you to open a thread on MSDN forums for APIM where we may discuss this matter in more detail. Once you've opened a thread, please be sure to tag me here with the URL of your thread so I can be notified and ensure that your thread is resolved.
Based on the above, we will now proceed to close this thread for now. If there are further questions regarding a specific section or detail of this documentation, please reopen and we will gladly continue the discussion here as well.


top-p < 1 fails inf assertion

When I set top-p in the arguments to a value less than 1, I have this assert failing. Which seems to make sense since this line puts them in.
What's the solution and what is the inf_mask needed for?

inf_mask ensures that when the output distribution (probs) has zero values (like using top-p), logprobs will be assigned -float("inf") instead of nan.
You can try commenting out this line to use top-p.


"titleStyle" cant change text color

I try to change text color to  Colors.amber but it's still black.
SideMenuItemDataTile(
isSelected: _currentIndex == 3,
onTap: () => setState(() => _currentIndex = 3),
title: 'Demo',
icon: const Icon(Icons.car_crash),
titleStyle: GoogleFonts.notoSansThai(
textStyle: const TextStyle(
fontSize: 14,
color: Colors.amber,
),
),
),

Have you tried "selectedTitleStyle"?

I have the same problem ! It seems to only be the color, if I add a text decoration such as an underline it works fine but the color doesn't change.


SPA Implementation issue with mappings enabled

Good day! I would like to ask for help regarding SPA implementation. We have been using AEM mappings in our publish server, causing the path used by the ResourceRoute component become incorrect because it doesnt match any resource in the AEM instance (A screenshot of the console error is attached to the bottom of this post). This is the mappings config we're using:
# /project.company.com/.content.xml

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
    jcr:primaryType="sling:Mapping"
    sling:internalRedirect="[/content/project/home,/]">
    <redirect/>
</jcr:root>

# /project.company.com/redirect/.content.xml

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
    jcr:primaryType="sling:Mapping"
    sling:internalRedirect="[/content/project/home/$1,/$1]"
    sling:match="(.+)$"/>

Are there any modifications I need to make on the source code to enable support for mappings like the one mentioned above? Thanks in advance.

That seems to be a missing piece. The ResourceMapping should actually handle this but it is not used in the ClientSling. You should override/extend ClientSling like this:

export class MyClientSling extends ClientSling {
  public subscribe(
    listener: ResourceComponent<any, any, any>,
    path: string,
    options?: SlingResourceOptions
  ): void {
  let mappedPath = resourceMapping.map(path);
  super.subscribe(listener, mappedPath, options);
}

And then register it in client.tsx. The ResourceMapping must be environment specific (remove the "/content/project" path on publisher only).

Should I just create a new ResourceMapping instance or do I need to get it in this manner: this.context.aemContext.container.get("resourceMapping")?
And do I replace
let clientSling: ClientSling = new ClientSling(cache, host);
container.register("sling", clientSling);

with
let clientSling: MyClientSling = new MyClientSling(cache, host);
container.register("sling", clientSling);

?

No, just use the instance that you are registering. They are both defined in the same file.
Yes, replace it.

Please have a look at client.tsx: Both ClientSling and ResourceMapping are instantiated and registered with the container here. So you can just use the ResourceMapping instance in the creation of the MyClientSling (e.g. as constructor args) .

Okay, now I have these codes
my-client-sling.tsx
import ClientSling from "aem-react-js-fork/store/ClientSling";
import { ResourceComponent } from "aem-react-js-fork/component/ResourceComponent";
import { SlingResourceOptions } from "aem-react-js-fork/store/Sling";

export default class MyClientSling extends ClientSling {
  private resourceMapping;

  constructor(cache, host, resourceMapping) {
    super(cache, host);

    this.resourceMapping = resourceMapping;
  }

  public subscribe(
    listener: ResourceComponent<any, any, any>,
    path: string,
    options?: SlingResourceOptions): void {
    let mappedPath = this.resourceMapping.map(path);
    super.subscribe(listener, mappedPath, options);
  }
}

client.tsx
import MyClientSling from "./my-client-sling";
//...
let resourceMapping = new ResourceMappingImpl(".html");
let clientSling: UnimartClientSling = new UnimartClientSling(cache, host, resourceMapping);
container.register("sling", clientSling);
container.register("resourceMapping", resourceMapping);

However, the problem is still not fixed and the page failed to render correctly.
There are three errors in the console which all contains: Uncaught (in promise) SyntaxError: Unexpected token < in JSON at position 0.
This is what the page renders:

...the rest of the page is blank.

You must change the Implementation of ResourceMapping to remove the "/content/${project}/" part of the resource path to create the path for the ajax call. The standard implementation just appends the ".html".
e.g add another basePath prop which you set to "/content/xxxxx":
export default class BetterResourceMappingImpl {

    constructor(basePath: string="", extension?: string) {
        if (extension) {
            this.extension = extension;
        }
       this.basePath=basePath;
    }

    private extension: string = ".html";
     private basePath: string ="";

    public resolve(path: string): string {
        return basePath+path.substring(0, path.length - this.extension.length);
    }

    public map(path: string): string {
        return path.substring(basePath.length) + this.extension;
    }

}

I have applied the changes indicated above but I noticed that the state.resource of the DashboardPage (component right under RootComponent) is null, and the state.absolutePath having an .html extension.
I tried to revert the changes made to ResourceMappingImpl and used the default ClientSling again to find out what was the previous value of state.absolutePath, and it is the same url but without the .html extension. Also the state.resource has the correct values again.
I have also discovered the correct way of accessing the contents of the components under the DashboardPage.

Header component - http://localhost:4502/dashboard/subscriptions/jcr:content/structure/header.json.html
Dashboard component - http://localhost:4502/dashboard/subscriptions/jcr:content/structure/dashboard/content.json.html
Footer component - http://localhost:4502/dashboard/faq/jcr:content/structure/footer.json.html

However, with the current setup (meaning all changes indicated above are applied), each component are accessed this way

http://localhost:4502/content/intrl-unimart/home/dashboard/subscriptions/jcr:content/structure/header.html
http://localhost:4502/content/intrl-unimart/home/dashboard/subscriptions/jcr:content/structure.html/dashboard
http://localhost:4502/content/intrl-unimart/home/dashboard/subscriptions/jcr:content/structure.html/footer

I apologize for bombarding you with questions but please bear with me a little bit more :)
This is the react debugger to visualize the component hierarchy:

This issue is really important and I am grateful for you raising it. Let's solve this and then I will try to find a way to make it work in the lib.
Use a custom mapping in ClientSling instead of ResourceMapping. The path that is passed to ClientSling should be /content/projectname/home/dashboard/subscriptions/jcr:content/structure/header. ClientSling appends ".json.html". So you just need to remove /content/projectname. ResourceMapping is also changing the extension which is not appropriate in this case. The following should be ok:
export class MyClientSling extends ClientSling {
  public subscribe(
    listener: ResourceComponent<any, any, any>,
    path: string,
    options?: SlingResourceOptions
  ): void {
  let mappedPath = path.substring('/content/projectname'.length);
  super.subscribe(listener, mappedPath, options);
}

The only thing I don't get is why the ".html" is appended after "structure" and not at the end.

I narrowed down the error to the ClientSling.subscribe method. If I pass the mappedPath to the parent constructor of MyClientSling instead of the path only, the whole page doesn't load. But if I pass the path and resolve it manually before calling this.fetch.fetch() then everything works as expected. What do you think?

Yes, you need to override subscribe and pass the mappedPath to fetch - path is different for each call. Can you share the code?

This is inside the default ClientSling.subscribe
// this is what I mean when I say "resolve it manually"
if (pathMod.startsWith("/content/projectname/home")) {
  pathMod = pathMod.substring("/content/projectname/home".length);
}

var url = this.origin + pathMod + ".json.html"; // + depthAsString + ".json";
var serverRenderingParam = "serverRendering=disabled";
var serverRendering = window.location.search.indexOf(serverRenderingParam) >= 0;
if (serverRendering) {
  url += "?" + serverRenderingParam;
}

return this.fetch.fetch(url, { credentials: "same-origin" }).then(function (response) {
  if (response.status === 404) {
    return {};
  }
  else {
   // everything else here
  }
}

I now see the problem, mappedPath has an .html extension because it was processed thru resourceMapping.map, while path isn't. Now I just remove the extension from mapped path. Is there a more appropriate way to do this?

ResourceMapping is really where this code should reside. Maybe there should be another special method for this purpose. I will have a look in the next couple days.

I have come up with a temporary solution. Please note that I am changing codes inside the node_modules directory but it's pretty easy to see how it translates to the code base.
MyClientSling.js
export default class MyClientSling extends ClientSling {
  private resourceMapping;

  constructor(cache, host, resourceMapping) {
    super(cache, host);

    this.resourceMapping = resourceMapping;
  }
}

ResourceMappingImpl.js
var ResourceMappingImpl = (function () {
    function ResourceMappingImpl(extension, basePath) {
        this.extension = ".html";
        if (extension) {
            this.extension = extension;
        }
        this.basePath = basePath;
    }
    ResourceMappingImpl.prototype.resolve = function (path) {
        if (path.endsWith(this.extension))
            path = path.substring(0, path.length - this.extension.length);

        if (!path.startsWith(this.basePath))
            path = this.basePath + path;
        return path;
    };
    ResourceMappingImpl.prototype.map = function (path) {
        if (path.startsWith(this.basePath)) {
            path = path.substring(this.basePath.length);
        }

        return path + this.extension;
    };
    return ResourceMappingImpl;
}());

ClientSling.js
ClientSling.prototype.subscribe = function (listener, path, options) {
  // some code here...
  if (resource === null || typeof resource === "undefined") {
    var depthAsString = void 0;
    if (depth < 0) {
      depthAsString = "infinity";
    }
    else {
      depthAsString = options.depth + "";
    }
    let pathMod = this.resourceMapping.map(path);
    var url = this.origin + pathMod + ".json.html";
    var serverRenderingParam = "serverRendering=disabled";
    // fetch...
  }
  // some code here...
}

client.tsx
const BASE_PATH = "/content/projectname/home";
let resourceMapping = new ResourceMappingImpl(".html", BASE_PATH);
let clientSling: MyClientSling = new MyClientSling(cache, host, resourceMapping);
container.register("sling", clientSling);
container.register("resourceMapping", resourceMapping);

I haven't pushed this to the publish server yet but it looks good on localhost.
I observed that using resourceMapping.map inside ClientSling (when the resource is not found in the cache) works because we're supposed access resource sans the basepath specified. That's how I came up with this temporary solution. I am not sure if the reason why on page load, resources can be found in the cache, is because the page is rendered on the server, where the mappings are still completely bypassed? This is just a speculation though

You are probably right, that the ServerSling doesn't care about the mapping. So the cache's keys are resourcePaths.  Im happy to accept a Merge Request, we just need to create a test for this first.


Add wildcard expansion to matte list set generation

One of the guys on the alshaders list suggested adding wildcard expansion to the matte list field. This PR adds that functionality. As I mentioned, I'm no python guru so not sure if the implementation is pythonic or not, but it works. I'm also not familiar enough with the code to know if there are potential performance ramifications here (e.g. matching against the global list will presumably match against the manifests from every cryptomatte AOV in the Nuke script).
I chose glob matching using Python's fnmatch module over a regex mainly because regexes seem like overkill for the type of matches you'd typically want to make and I expect the average artist to be more familiar with glob matching.

Hi Anders,
I agree with using fnmatch instead of regex, and I'm not a Python guru either.
A couple issues- one is a bug, and the other is a design issue. The bug is that if you save a script with a wildcard selection in it, such as "flower*" on the bunny_CryptoMaterial example, when you load the script again the manifest hasn't loaded yet so it doesn't find anything that matches flower*, and creates an empty matte. (So we need to make sure somehow that the manifest is loaded).
The design issue is related. In an early iteration of Cryptomatte, we were relying on the manifest to generate the extraction expression from a list of names. What happened was if there was an object with animated visibility, a keyed object might not be present on certain frames, meaning different manifests on different frames. If the nuke script was saved on that frame, whenever it was re-opened (such as on the render farm) the matte would be broken.
There's a couple ways to get around this:

Expand the wildcard selection when the user types in a word containing * or ?. We could also warn the user here if the matte list that was about to be generated were impractically large.
Rebuild expressions every frame if there's a * or ?. Even though there's no frame-changed callback, I'm sure some way could be found to get around that.

That's weird, I thought I'd saved/loaded on my test scene but I just tested again and see that it's broken.
I'll give this some thought.

What probably happened was, if you have a wildcard selection, and then key something else, it expands the wildcard in the matte list field. If you save that scene, it works, becuase the matte list has been expanded.

This can turn into a can of worms with how Nuke wants to evaluate nodes and metadata.  If the expression needs to be dynamic, you don't want it to be getting set in the main thread, since there are all sorts of retimes in play, and a given node may be executed for multiple frames.
I believe you can get around this by treating the expression itself as a value, and calling a function that uses the incoming metadata directly.
For example, you can get something like this by setting a expression value like:
[python cryptomatte_utilities.get_keyer_expression()]
In that function, you should be able to fetch the node and its parent/gizmo body with thisNode() and thisParent().  From the node, you can get the metadata with nuke.thisNode().metadata().
From some rudimentary testing, that seems to work.  Interestingly, if you try to use a different knob for the expression, and then get the knob value, it works, but doesn't support multiple time offsets (unless you use a different expression node -- which doesn't solve the problem).  In my next post I'll paste a nuke graph that demonstrates this.
I think we'd want to test this in action before we run with it, but it's also possible that if we encounter evaluation bugs it could be Nuke's own fault.  I've certainly run into trouble with metadata expressions before.
In the example, the value in the red channel in both merge nodes should be 15, due to the frame holds.

set cut_paste_input [stack 0]
version 9.0 v8
Constant {
inputs 0
channels rgb
name Constant1
selected true
xpos 301
ypos -175
}
ModifyMetaData {
metadata {
{set expr_test "[frame]"}
}
name ModifyMetaData2
selected true
xpos 301
ypos -72
}
set N4ee54c00 [stack 0]
Expression {
expr0 "[python nuke.thisNode().metadata()\['expr_test'\]]"
name Expression1
selected true
xpos 207
ypos 13
addUserKnob {20 User}
addUserKnob {1 test_expression l Test}
test_expression "[python nuke.thisNode().metadata()\['expr_test'\]]"
}
set N4ee16800 [stack 0]
FrameHold {
first_frame 10
name FrameHold2
selected true
xpos 207
ypos 80
}
set N4ee40480 [stack 0]
push $N4ee54c00
Expression {
expr0 "[python nuke.thisNode().metadata()\['expr_test'\]]"
name Expression3
selected true
xpos 364
ypos 16
addUserKnob {20 User}
addUserKnob {1 test_expression l Test}
test_expression "[python nuke.thisNode().metadata()\['expr_test'\]]"
}
FrameHold {
first_frame 5
name FrameHold1
selected true
xpos 364
ypos 80
}
Merge2 {
inputs 2
operation plus
name Merge1
selected true
xpos 284
ypos 155
}
push $N4ee40480
push $N4ee16800
FrameHold {
first_frame 5
name FrameHold3
selected true
xpos 487
ypos 87
}
Merge2 {
inputs 2
operation plus
name Merge2
selected true
xpos 412
ypos 154
}

This can turn into a can of worms with how Nuke wants to evaluate nodes and metadata. If the expression needs to be dynamic, you don't want it to be getting set in the main thread, since there are all sorts of retimes in play, and a given node may be executed for multiple frames.
I believe you can get around this by treating the expression itself as a value, and calling a function that uses the incoming metadata directly.
For example, you can get something like this by setting a expression value like:
[python cryptomatte_utilities.get_keyer_expression()]
In that function, you should be able to fetch the node and its parent/gizmo body with thisNode() and thisParent(). From the node, you can get the metadata with nuke.thisNode().metadata().
From some rudimentary testing, that seems to work. Interestingly, if you try to use a different knob for the expression, and then get the knob value, it works, but doesn't support multiple time offsets (unless you use a different expression node -- which doesn't solve the problem). In my next post I'll paste a nuke graph that demonstrates this.
I think we'd want to test this in action before we run with it, but it's also possible that if we encounter evaluation bugs it could be Nuke's own fault. I've certainly run into trouble with metadata expressions before.
In the example, the value in the red channel in both merge nodes should be 15, due to the frame holds.

set cut_paste_input [stack 0]
version 9.0 v8
Constant {
inputs 0
channels rgb
name Constant1
selected true
xpos 301
ypos -175
}
ModifyMetaData {
metadata {
{set expr_test "[frame]"}
}
name ModifyMetaData2
selected true
xpos 301
ypos -72
}
set N4ee54c00 [stack 0]
Expression {
expr0 "[python nuke.thisNode().metadata()\['expr_test'\]]"
name Expression1
selected true
xpos 207
ypos 13
}
set N4ee16800 [stack 0]
FrameHold {
first_frame 10
name FrameHold2
selected true
xpos 207
ypos 80
}
set N4ee40480 [stack 0]
push $N4ee54c00
Expression {
expr0 "[python nuke.thisNode().metadata()\['expr_test'\]]"
name Expression3
selected true
xpos 364
ypos 16
}
FrameHold {
first_frame 5
name FrameHold1
selected true
xpos 364
ypos 80
}
Merge2 {
inputs 2
operation plus
name Merge1
selected true
xpos 284
ypos 155
}
push $N4ee40480
push $N4ee16800
FrameHold {
first_frame 5
name FrameHold3
selected true
xpos 487
ypos 87
}
Merge2 {
inputs 2
operation plus
name Merge2
selected true
xpos 412
ypos 154
}

Expand the wildcard selection when the user types in a word containing * or ?. We could also warn the user here if the matte list that was about to be generated were impractically large.
Rebuild expressions every frame if there's a * or ?. Even though there's no frame-changed callback, I'm sure some way could be found to get around that.

We had a similar tool internally and ended up with a third solution: a button which brought up a PySide-based GUI, which displayed the manifest as a tree (and could have also included a field to type in glob patterns for selection)
From artist point of view it meant they could, say, select flowerA and it would select all the flowerA.petal1.:1234 objects..
Since it was a modal dialog thing, it meant it could load the manifest for all frames, so every object was selectable regardless of changing visibility. Was also nice in that all the string matching was only done when the UI was being interacted with, which is better for general Nuke performance compared to a per-frame update
The only main drawback was the node wouldn't work as expected when copying between different renders - e.g if entering a glob pattern for flower* on a render containing flowerA and flowerB - it'd be nice if the node could be copied to a different render containing flowerB and flowerC.
If I get the time I'd like to try writing the Cryptomatte node as a plugin, as I suspect it would be relatively simple to get the per-frame glob matching done in a reliable and reasonably performant way

Hi all
I managed to implement a "regex" syntax in the matte selection list of the Fusion Fuse.
It supports the full Lua pattern syntax which is quite similar to your std regular expression. To implement this I had to tweak a decent amount of code, which was a great opportunity to clean it all up & improve performance in general.
To give an example of a pattern, when connecting the fuse to the test_grid sample image, transparent_grid.* will match all transparent grids from transparent_grid (not indexed) to transparent_grid7. Both dot and asterisk character handle the same way as in other regex languages, dot matches any character and asterisk matches 0 or more of the preceding expression.
When writing a regex as mentioned before, transparent_grid.*, this will match 8 grids total. If you would want to remove one of the grids out of the expression, you naturally would just pick the one you wish to remove, and click on the remove matte button. What would you expect to see in the matte selection list?

The names of all mattes currently picked (unfold the pattern)
Have a custom syntax for items that got excluded from a pattern (e.g. transparent_grid.*-transparent_grid7)

To give you my thoughts on this, 2 looked like an option, but not the most friendly one both programmatically and user interaction wise. So I chose to implement option one.
At first sight everything worked as expected. You enter transparent_grid.* and 8 grids get picked. You remove the transparent_grid7 with the button and the matte selection list then shows the following: transparent_grid, transparent_grid1, transparent_grid2, transparent_grid3, transparent_grid4, transparent_grid5, transparent_grid6. Which is great! Until you write a pattern such as .*. This ends up picking ALL mattes possible. On a crypto object EXR image, this results in 30000+ mattes. The picking goes very fast (1-2s), but if you then decide to add / remove something, the pattern unfolding goes out of hand. You could be waiting up to 30-60s before seeing the name list populated. Now the sad part is that if the FULL list of names would show up, this wouldn't be that much of a problem, but Fusion actually clamps the line edit text field after 32768 characters, which as you can tell is absolutely not enough.
Any thoughts on how to deal with this or feedback in general?
Cheers
Cedric
PS: Had to put the regex/patterns in code style blocks to prevent Markdown from going nuts.

Thanks a lot for doing this.

What would you expect to see in the matte selection list?

I agree with unfolding the as the way to handle this. In fact that sounds really good in general. The custom syntax could be borrowed from set theory, but I think asking people to learn a new syntax is a bit too much to ask.

Any thoughts on how to deal with this or feedback in general?

The main issue that makes this regex / wild card issue thorny is two questions, both "safety" issues-

What happens if the manifest changes from frame to frame?
What happens if the manifest is missing or incomplete on some frames?

Both of those are things that happen. #1 happens with animated visibility in 3D, and #2 can happen for more complicated reasons. To accommodate either case #1 or #2, you need to re-compute your list of IDs on every frame. Does this currently happen? If not, this can be a problem, and very confusing to users when their mattes stop working based on something like what frame their comp was on when they saved it.
It was a design choice that the manifest would not be a vital part of matte extraction for these reasons. I think we should stick with this principle, at least in the default behavior of the decoders.
Here's one idea of how to deal with this:

Add a checkbox to your advanced tab called "expand wildcards", default on.
If this checkbox is on if you type in a wildcard or regex selection it automatically expands it to the list of names on that particular frame of the manifest. If that checkbox is on, everything can function as usual and no paranoid rechecking is needed.
If that checkbox is off, then it stays as a wildcard selection, but now you need to make sure the list of IDs is recomputed every frame. This dynamically changing selection will only be as good as the manifest.

On top of that, I think a "max selections" control in the advanced tab may be a good idea as well, so that users don't accidentally select a huge number of objects. This could be 100 or so, and apply to only regex expansions.
About performance issues and what happens if users create an extraction of thousands of mattes- I just don't think people should be doing this right now. I certainly don't think they should be doing this by accident. We're not well set up for it, and are set up make more intelligent groupings instead, like materials or namespaces. I don't think the user experience will be good otherwise. If people really want to do this, I'd definitely prefer it takes them a couple extra steps to make it work.
Just to be clear, I think wild cards / regex are a great feature and very useful, I'm just skeptical about the wisdom of using them for extracting thousands of IDs simultaneously. Perhaps if we make a CPP plugin for Nuke I'll be surprised at how performant an extraction like that can be, but until then, I don't think they should be used in that way and we should do things that discourage using wildcards in slow or unsafe ways.

Hi Jonah
Thanks for the feedback!

Both of those are things that happen. #1 happens with animated visibility in 3D, and #2 can happen for more complicated reasons. To accommodate either case #1 or #2, you need to re-compute your list of IDs on every frame. Does this currently happen? If not, this can be a problem, and very confusing to users when their mattes stop working based on something like what frame their comp was on when they saved it.

Currently the manifest gets reloaded at every frame, which helps out a lot to cover the topics you mentioned.

Here's one idea of how to deal with this:

Add a checkbox to your advanced tab called "expand wildcards", default on.
If this checkbox is on if you type in a wildcard or regex selection it automatically expands it to the list of names on that particular frame of the manifest. If that checkbox is on, everything can function as usual and no paranoid rechecking is needed.
If that checkbox is off, then it stays as a wildcard selection, but now you need to make sure the list of IDs is recomputed every frame. This dynamically changing selection will only be as good as the manifest.

I am fond of letting the user control the unfolding of the regex, this being a Fusion issue anyway, it could be countered by just leaving the box off and not having any troubles unfolding. The only problem I have with this is of course if you don't unfold the regex when removing a matte for example, the regex is actually not correct. Meaning if you would save, close & reopen the comp, the fuse will rebuild the matte based on what names/regex' are in the selection box. This will then "fail" by correctly matching too many matte than previous session.
I currently have no way around this, I will try to contact Blackmagic as well to hopefully get their feedback on this clamping issue. If you remember at the start of my development, I had another clamping issue with the color picker. (Lewis has that too in Flame if I'm correct)

About performance issues and what happens if users create an extraction of thousands of mattes- I just don't think people should be doing this right now. I certainly don't think they should be doing this by accident. We're not well set up for it, and are set up make more intelligent groupings instead, like materials or namespaces. I don't think the user experience will be good otherwise. If people really want to do this, I'd definitely prefer it takes them a couple extra steps to make it work.
Just to be clear, I think wild cards / regex are a great feature and very useful, I'm just skeptical about the wisdom of using them for extracting thousands of IDs simultaneously. Perhaps if we make a CPP plugin for Nuke I'll be surprised at how performant an extraction like that can be, but until then, I don't think they should be used in that way and we should do things that discourage using wildcards in slow or unsafe ways.

To give you some personal thoughts on the whole regex idea. I share the same view on user experience, it's a great asset to artists and developers, but it gives a lot of freedom which means a lot of possible technical issues. On the good side, what surprised me is how fast it works in Lua. When picking all mattes with the .* pattern on the testgrid sample image, it takes between one to two seconds to create the keyable image and a little less than that when clicking the matte only checkbox. It's the unfolding that goes haywire when adding/removing on that pattern. I'll try to contact Blackmagic on the clamping subject since it's been the second blocker (color picker + text edit control) that I encounter which I have to code my way around. As Raymond Hettinger would say, there must be a better way.
Cheers
Cedric

Currently the manifest gets reloaded at every frame, which helps out a lot to cover the topics you mentioned.

Ah, good. Sounds like the safety issues are addressed then. Although a side question - are you also checking the manifest if there are no regexes? (The manifest is only needed to get a name from an ID. If you only need IDs from your selected names, you can produce them by hashing the names. )

The only problem I have with this is of course if you don't unfold the regex when removing a matte for example, the regex is actually not correct.

I think automatically unfolding when the user removes a matte from a regex'd matte is a totally reasonable behavior. I would not give them options that let them get into a state where the next time they reopen their comp the result is different or wrong.

On the good side, what surprised me is how fast it works in Lua. When picking all mattes with the .* pattern on the testgrid sample image, it takes between one to two seconds to create the keyable image and a little less than that when clicking the matte only checkbox.

If you don't have a problem, you don't have a problem! The performance with huge selections was only a secondary issue anyway- the only things I'm not willing to compromise on are the "safety" issues. It sounds like you have those pretty well in hand, so you should be good to go.

We're working on this very issue with some very generous contributions in pull request #99, so I'm finally going to close this one.


Hard code release version

Hard code release version.
Note : This PR will be finished after https://github.com/cryptape/cita-common/pull/299 .
After this PR merged, the micro-service version will be:
${SERVICE_NAME}-${HARD_CODE_VERSION}-${BRANCH_NAME}-${COMMIT_ID}

e.g.

CI...

CI...

Will be fixed after cryptape/cita-common#299

should not use BRANCH_NAME as part of the version info

should not use BRANCH_NAME as part of the version info

I am thinking about that BRANCH_NAME and COMMIT_ID can locate the source code for CITA developers.

https://github.com/cryptape/cita-bft/pull/130#issuecomment-529802166

should not use BRANCH_NAME as part of the version info

I am thinking about that BRANCH_NAME and COMMIT_ID can locate the source code for CITA developers.

BRANCH_NAME is not necessary

cryptape/cita-bft#130 (comment)

I will fix it.

should not use BRANCH_NAME as part of the version info

I am thinking about that BRANCH_NAME and COMMIT_ID can locate the source code for CITA developers.

BRANCH_NAME is not necessary

okay, It will fix in PR: https://github.com/cryptape/cita-common/pull/300

should not use BRANCH_NAME as part of the version info

I am thinking about that BRANCH_NAME and COMMIT_ID can locate the source code for CITA developers.

BRANCH_NAME is not necessary


Can I publish hybrid app (iOS) on AppCenter

Hi.
Is it possible now to publish hybrid app on AppCenter for testing ?
I tried it but it throws error
##[error]Xamarin.iOS task failed with error Error: /Library/Frameworks/Mono.framework/Versions/6_12_4/bin/msbuild failed with return code: 1. For guidance on setting up the build definition, see https://go.microsoft.com/fwlink/?LinkId=760847.
I even tried to do it with just default hybrid app template, didn't add any other code or libraries but throws same error.
And if is it not possible , is there any way to do it because I need it.
Thank you

Hi @AmirImam I've never published on AppCenter but it should be exactly the same as any Xamarin-based app (which includes Mobile Blazor Bindings native and hybrid apps).
Have you been able to publish a regular Xamarin-based app to AppCenter? I recommend trying that first to rule out certain problems related specifically to Mobile Blazor Bindings.

Hi @AmirImam I've never published on AppCenter but it should be exactly the same as any Xamarin-based app (which includes Mobile Blazor Bindings native and hybrid apps).
Have you been able to publish a regular Xamarin-based app to AppCenter? I recommend trying that first to rule out certain problems related specifically to Mobile Blazor Bindings.

Hi @AmirImam I've never published on AppCenter but it should be exactly the same as any Xamarin-based app (which includes Mobile Blazor Bindings native and hybrid apps).
Have you been able to publish a regular Xamarin-based app to AppCenter? I recommend trying that first to rule out certain problems related specifically to Mobile Blazor Bindings.

Yes I have published Xamarin forms app to AppCenter for testing, and distributed iOS app for some real devices.
If there is nothing in blazor hybrid that prevents publishing, then maybe the problem in my publishing steps.

Hi @AmirImam I've never published on AppCenter but it should be exactly the same as any Xamarin-based app (which includes Mobile Blazor Bindings native and hybrid apps).
Have you been able to publish a regular Xamarin-based app to AppCenter? I recommend trying that first to rule out certain problems related specifically to Mobile Blazor Bindings.

Yes I have published Xamarin forms app to AppCenter for testing, and distributed iOS app for some real devices.
If there is nothing in blazor hybrid that prevents publishing, then maybe the problem in my publishing steps.

Did you try the same publish steps in both apps? It's certainly possible that there are some Mobile Blazor Bindings specific steps required, but for the most part as far as the platform/publish is concerned, it's "just a regular Xamarin app."

Did you try the same publish steps in both apps? It's certainly possible that there are some Mobile Blazor Bindings specific steps required, but for the most part as far as the platform/publish is concerned, it's "just a regular Xamarin app."

Yes I tried same steps, and I'll try it again to make sure about it. But if there are MBB specific steps then I don't know them, so I thought that I can find them here

Yes I tried same steps, and I'll try it again to make sure about it. But if there are MBB specific steps then I don't know them, so I thought that I can find them here

Does the raw log on Azure DevOps show any other errors that might give insight on this? Unfortunately the error shown above doesn't say much.

Does the raw log on Azure DevOps show any other errors that might give insight on this? Unfortunately the error shown above doesn't say much.

No, only that error. I think the only available solution now is trying to publish again maybe I missing something

No, only that error. I think the only available solution now is trying to publish again maybe I missing something

If you can provide any additional info that would be very helpful. There could be an issue here in MBB but I probably won't have time to look at it very soon.

If you can provide any additional info that would be very helpful. There could be an issue here in MBB but I probably won't have time to look at it very soon.

_CoreCompileColladaAssets:
Skipping target "_CoreCompileColladaAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_CoreCompileSceneKitAssets:
Skipping target "_CoreCompileSceneKitAssets" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_CoreCompileTextureAtlases:
Skipping target "_CoreCompileTextureAtlases" because it has no inputs.
_BeforeCompileCoreMLModels:
  Directory "obj/iPhone/Debug/coremlc" doesn't exist. Skipping.
_CoreOptimizePngImages:
Skipping target "_CoreOptimizePngImages" because it has no outputs.
_CoreOptimizePropertyLists:
Skipping target "_CoreOptimizePropertyLists" because it has no inputs.
_CoreOptimizeLocalizationFiles:
Skipping target "_CoreOptimizeLocalizationFiles" because it has no inputs.
Done Building Project "/Users/runner/work/1/s/MyProject.V2.Mobile/MyProject.V2.Mobile.iOS/MyProject.V2.Mobile.iOS.csproj" (Rebuild target(s)) -- FAILED.
Done Building Project "/Users/runner/work/1/s/MyProject.V2.sln" (Rebuild target(s)) -- FAILED.

Build FAILED.

I found this in the AppCenter build log. Maybe it will be useful

_CoreCompileColladaAssets:
Skipping target "_CoreCompileColladaAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_BeforeCoreCompileSceneKitAssets:
Skipping target "_BeforeCoreCompileSceneKitAssets" because it has no inputs.
_CoreCompileSceneKitAssets:
Skipping target "_CoreCompileSceneKitAssets" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_BeforeCompileTextureAtlases:
Skipping target "_BeforeCompileTextureAtlases" because it has no inputs.
_CoreCompileTextureAtlases:
Skipping target "_CoreCompileTextureAtlases" because it has no inputs.
_BeforeCompileCoreMLModels:
  Directory "obj/iPhone/Debug/coremlc" doesn't exist. Skipping.
_CoreOptimizePngImages:
Skipping target "_CoreOptimizePngImages" because it has no outputs.
_CoreOptimizePropertyLists:
Skipping target "_CoreOptimizePropertyLists" because it has no inputs.
_CoreOptimizeLocalizationFiles:
Skipping target "_CoreOptimizeLocalizationFiles" because it has no inputs.
Done Building Project "/Users/runner/work/1/s/MyProject.V2.Mobile/MyProject.V2.Mobile.iOS/MyProject.V2.Mobile.iOS.csproj" (Rebuild target(s)) -- FAILED.
Done Building Project "/Users/runner/work/1/s/MyProject.V2.sln" (Rebuild target(s)) -- FAILED.

Build FAILED.

I found this in the AppCenter build log. Maybe it will be useful

Found these two
The application to execute does not exist: '/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/../../tools/netcoreapp3.0/rzc.dll'
/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/Microsoft.NET.Sdk.Razor.Component.targets(106,5): error : rzc generate exited with code 129. [/Users/runner/work/1/s/MarketTree.V2.Mobile/MarketTree.V2.Mobile/MarketTree.V2.Mobile.csproj]

Found these two
The application to execute does not exist: '/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/../../tools/netcoreapp3.0/rzc.dll'
/Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Sdks/Microsoft.NET.Sdk.Razor/build/netstandard2.0/Microsoft.NET.Sdk.Razor.Component.targets(106,5): error : rzc generate exited with code 129. [/Users/runner/work/1/s/MarketTree.V2.Mobile/MarketTree.V2.Mobile/MarketTree.V2.Mobile.csproj]

Last thing, I could publish my MMB hybrid iOS app on TestFlight successfully. So now the problem is with AppCenter

Last thing, I could publish my MMB hybrid iOS app on TestFlight successfully. So now the problem is with AppCenter

Is there any info here that helps? https://docs.microsoft.com/en-us/appcenter/build/troubleshooting/xamarin
There could be some limitation on App Center where the Razor SDK is somehow not available when building a Xamarin.Forms iOS app. Do you have the ability to specify which SDKs/dependencies your app requires on App Center?

Is there any info here that helps? https://docs.microsoft.com/en-us/appcenter/build/troubleshooting/xamarin
There could be some limitation on App Center where the Razor SDK is somehow not available when building a Xamarin.Forms iOS app. Do you have the ability to specify which SDKs/dependencies your app requires on App Center?

They do have some free support contact it seems as well: https://docs.microsoft.com/en-us/appcenter/help
I looked at the list of Supported Frameworks in https://docs.microsoft.com/en-us/appcenter/build/xamarin/ and I didn't see any mention of web/ASP.NET/Razor/Blazor so maybe there's a limitation on App Center's build system regarding Razor. That support link might help find some info.
I wish I could help more with this but I haven't tried App Center at all. I'm a bit more familiar with Azure Dev Ops but only for building libraries (such as Mobile Blazor Bindings) and not as much for building apps.

They do have some free support contact it seems as well: https://docs.microsoft.com/en-us/appcenter/help
I looked at the list of Supported Frameworks in https://docs.microsoft.com/en-us/appcenter/build/xamarin/ and I didn't see any mention of web/ASP.NET/Razor/Blazor so maybe there's a limitation on App Center's build system regarding Razor. That support link might help find some info.
I wish I could help more with this but I haven't tried App Center at all. I'm a bit more familiar with Azure Dev Ops but only for building libraries (such as Mobile Blazor Bindings) and not as much for building apps.


HereBeDragons-Pins-2.0: AddWorldMapIconMap: 'ref' must not be nil

ID: 2
Error occured in: Global
Count: 1
Message: ...icCodex\lib\HereBeDragons\HereBeDragons-Pins-2.0.lua line 683:
   HereBeDragons-Pins-2.0: AddWorldMapIconMap: 'ref' must not be nil
Debug:
   [C]: ?
   [C]: error()
   ...icCodex\lib\HereBeDragons\HereBeDragons-Pins-2.0.lua:683: AddWorldMapIconMap()
   RecipeRadarClassic\Worldmap.lua:43: RecipeRadar_Worldmap_UpdateButton()
   RecipeRadarClassic\Worldmap.lua:23: RecipeRadar_Worldmap_AddVendor()
   RecipeRadarClassic\Maps.lua:48: RecipeRadar_Maps_AddVendor()
   RecipeRadarClassic\DropDowns.lua:484: RecipeRadar_InitVendorFilters()
   ...ace\AddOns\RecipeRadarClassic\RecipeRadarClassic.lua:300: RecipeRadar_NewRegion()
   ...ace\AddOns\RecipeRadarClassic\RecipeRadarClassic.lua:190: RecipeRadar_OnEvent()
   [string "*:OnEvent"]:1:
      [string "*:OnEvent"]:1
Locals:```

The error from the addon RecipeRadarClassic, not ClassicCodex.

The reason you see the ClassicCodex path in the error message is because most Wow addons use LibStab to load the shared libraries.
The same library is only loaded once by LibStab. The addon that is loaded first will share its libraries to all other addons. So you may see ClassicCodex in the error tips of other addons. However, this error may have nothing to do with ClassicCodex. This is just that RecipeRadarClassic uses HereBeDragons-Pins-2.0 included in ClassicCodex.
Also, which addon is loaded first is completely undefined. Therefore, the path of the library file can not be used as a reference in the error reports.


Try to fix the gradle compilation in idea

I don't really understand it, but it worked for me. I cherry picked this patch, refreshed gradle in a still-running IDEA and then the build (which was failing) succeeded. I also tried exiting IntelliJ, restarting and "rebuild project" since IDEA seems to maintain mysterious state. This also worked. I did not try the other build option

I think this patch works for both "modes". I'm sure it can be done better (elasticsearch folks may have more expertise here since they have a much more complex build) but this seems to do the job for me. If you test it, Mike, please feel free to commit to main and 9x - I'll be away during the weekend and it's a change that helps people to work, if they use idea.

Thanks, @dweiss -- still seems to work for me after your latest fixes.


Uncaught TypeError: locale pt-br is not loaded from moment locales!

Hey guys, I'm using Browserify with the following code:
var datetimepicker = require('eonasdan-bootstrap-datetimepicker');
window.$ = window.jQuery = require('jquery');
var moment = require('moment');
require('moment/locale/pt-br');
window.moment = moment;
However, I'm facing this issue:

Uncaught TypeError: locale pt-br is not loaded from moment locales!

This occurs when I set locale:
$('#datetimepicker').datetimepicker({         locale: 'pt-br'     });
What should I do to fix that?

I am doing exactly like you.

I could not make it work with browserify, because it doesn't include module.exports in front of the factory, there is an issue for this already.
After I download the code and modify it then it works perfectly with moment locale (pt-br, I am brazillian too)

Same problem.. How to fix this?

Same problem and question. How to fix this S***? @melanke - where did you put module.exports? I need 'pl' locales.

You need to include moment-with-locale.js
http://momentjs.com/downloads/moment-with-locales.min.js


Autorest Regen Preview to 3.0.0-alpha.20230801.1 by Dapeng Zhang from refs/pull/3354/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3354

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