Uncommited changes not maintained for vscode-wasm when cloning repository in a container volume

Testing #158798

Logs says: Skipping applying 4 changes from edit session with ref 832cd542-e4a2-4ea2-8145-5b151d932f35 as no matching workspace folder was found.
Complete logs:
[2022-08-23 12:18:29.112] [editsessions] [info] Resuming edit session...
[2022-08-23 12:18:29.112] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 12:18:31.336] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 12:18:35.493] [editsessions] [info] Matching identity {"remote":"https://monacotools@dev.azure.com/monacotools/Monaco/_git/Sandbox","ref":"main","sha":"721bb39b6f12475e3c2f9f4af957b936caa0a575"} against edit session folder identity {"remote":"https://monacotools@dev.azure.com/monacotools/Monaco/_git/Sandbox","ref":"main","sha":"721bb39b6f12475e3c2f9f4af957b936caa0a575"}...
[2022-08-23 12:18:36.729] [editsessions] [info] Deleting edit session with ref 3e05f32b-ce38-45b7-a27a-823ab8feb7b5 after successfully applying it to current workspace...
[2022-08-23 12:18:36.835] [editsessions] [info] Deleted edit session with ref 3e05f32b-ce38-45b7-a27a-823ab8feb7b5.
[2022-08-23 13:58:32.504] [editsessions] [info] Resuming edit session...
[2022-08-23 13:58:32.941] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 13:58:35.768] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 13:58:35.954] [editsessions] [info] Skipping applying 4 changes from edit session with ref 832cd542-e4a2-4ea2-8145-5b151d932f35 as no matching workspace folder was found.
[2022-08-23 14:02:08.919] [editsessions] [info] Resuming edit session...
[2022-08-23 14:02:09.344] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:02:11.224] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:02:11.392] [editsessions] [info] Matching identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"} against edit session folder identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"}...
[2022-08-23 14:02:17.469] [editsessions] [info] Deleting edit session with ref 832cd542-e4a2-4ea2-8145-5b151d932f35 after successfully applying it to current workspace...
[2022-08-23 14:02:17.568] [editsessions] [info] Deleted edit session with ref 832cd542-e4a2-4ea2-8145-5b151d932f35.
[2022-08-23 14:02:31.041] [editsessions] [info] Storing edit session...
[2022-08-23 14:02:31.126] [editsessions] [info] Stored edit session with ref 03f97d98-19c5-4c89-bee6-5cd1f123a462.
[2022-08-23 14:02:37.380] [editsessions] [info] Resuming edit session...
[2022-08-23 14:04:31.248] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:04:33.898] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:04:34.343] [editsessions] [info] Matching identity undefined against edit session folder identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"}...
[2022-08-23 14:04:34.343] [editsessions] [info] Skipping applying 4 changes from edit session with ref 03f97d98-19c5-4c89-bee6-5cd1f123a462 as no matching workspace folder was found.
[2022-08-23 14:07:27.558] [editsessions] [info] Storing edit session...
[2022-08-23 14:07:27.713] [editsessions] [info] Stored edit session with ref dd7672f0-05e9-467b-949d-a014e1c46ca5.
[2022-08-23 14:07:31.929] [editsessions] [info] Resuming edit session...
[2022-08-23 14:07:49.197] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:07:50.349] [editsessions] [info] Resuming edit session...
[2022-08-23 14:07:50.746] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:07:53.114] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:07:53.190] [editsessions] [info] Skipping applying 2 changes from edit session with ref dd7672f0-05e9-467b-949d-a014e1c46ca5 as no matching workspace folder was found.
[2022-08-23 14:08:04.096] [editsessions] [info] Resuming edit session...
[2022-08-23 14:08:04.096] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:08:04.706] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:08:06.262] [editsessions] [info] Matching identity {"remote":"https://monacotools@dev.azure.com/monacotools/Monaco/_git/Sandbox","ref":"main","sha":"721bb39b6f12475e3c2f9f4af957b936caa0a575"} against edit session folder identity {"remote":"https://monacotools@dev.azure.com/monacotools/Monaco/_git/Sandbox","ref":"main","sha":"721bb39b6f12475e3c2f9f4af957b936caa0a575"}...
[2022-08-23 14:08:07.526] [editsessions] [info] Deleting edit session with ref dd7672f0-05e9-467b-949d-a014e1c46ca5 after successfully applying it to current workspace...
[2022-08-23 14:08:07.590] [editsessions] [info] Deleted edit session with ref dd7672f0-05e9-467b-949d-a014e1c46ca5.
[2022-08-23 14:08:14.530] [editsessions] [info] Storing edit session...
[2022-08-23 14:08:14.644] [editsessions] [info] Stored edit session with ref 7deb00b9-eff5-4d47-a46a-867c9d6f3f00.
[2022-08-23 14:08:17.864] [editsessions] [info] Resuming edit session...
[2022-08-23 14:08:34.433] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:08:35.540] [editsessions] [info] Resuming edit session...
[2022-08-23 14:08:35.912] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:08:38.086] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:08:38.211] [editsessions] [info] Skipping applying 2 changes from edit session with ref 7deb00b9-eff5-4d47-a46a-867c9d6f3f00 as no matching workspace folder was found.

Unable to reproduce this anymore as well, logs:
[2022-08-23 14:15:10.257] [editsessions] [info] Resuming edit session...
[2022-08-23 14:15:10.575] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:15:12.552] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:15:16.138] [editsessions] [info] Skipping applying 6 changes from edit session with ref 55a438ac-cc12-43be-860f-5626a1f1704d as no matching workspace folder was found.
[2022-08-23 14:15:20.022] [editsessions] [info] Resuming edit session...
[2022-08-23 14:15:20.411] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:15:22.621] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:15:23.387] [editsessions] [info] Matching identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"} against edit session folder identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"}...
[2022-08-23 14:15:23.481] [editsessions] [info] Deleting edit session with ref 55a438ac-cc12-43be-860f-5626a1f1704d after successfully applying it to current workspace...
[2022-08-23 14:15:23.543] [editsessions] [info] Deleted edit session with ref 55a438ac-cc12-43be-860f-5626a1f1704d.
[2022-08-23 14:18:17.161] [editsessions] [info] Resuming edit session...
[2022-08-23 14:18:17.585] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:18:19.715] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:18:20.101] [editsessions] [info] Matching identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"} against edit session folder identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"}...
[2022-08-23 14:18:24.054] [editsessions] [info] Deleting edit session with ref f702ee34-a47c-4bb9-975f-ee381fd8b119 after successfully applying it to current workspace...
[2022-08-23 14:18:24.099] [editsessions] [info] Deleted edit session with ref f702ee34-a47c-4bb9-975f-ee381fd8b119.
[2022-08-23 14:18:28.719] [editsessions] [info] Storing edit session...
[2022-08-23 14:18:28.825] [editsessions] [info] Stored edit session with ref e06ca35e-60b0-446b-b16c-0c83eff07b42.
[2022-08-23 14:18:40.306] [editsessions] [info] Resuming edit session...
[2022-08-23 14:18:54.173] [editsessions] [info] Searching for existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:18:56.625] [editsessions] [info] Found existing authentication session with ID 6e72af97-c8eb-4d45-9254-159fcdeb27ec
[2022-08-23 14:18:56.802] [editsessions] [info] Matching identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"} against edit session folder identity {"remote":"https://github.com/microsoft/vscode-wasm","ref":"main","sha":"805feaf2fbd578f4bc1bac898856e954822aa163"}...
[2022-08-23 14:19:00.491] [editsessions] [info] Deleting edit session with ref e06ca35e-60b0-446b-b16c-0c83eff07b42 after successfully applying it to current workspace...
[2022-08-23 14:19:00.578] [editsessions] [info] Deleted edit session with ref e06ca35e-60b0-446b-b16c-0c83eff07b42.

Closing based on https://github.com/microsoft/vscode/issues/158983#issuecomment-1224899600. Please reopen if you encounter this again!


Q: How to mark as Replace-by-fee?

Hello.
How to mark transaction as Replaceable-by-fee?
Link to more info about the feature: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki

Hi, so it's possible to detect the transaction which opts into RBF since an input sequence will be < INPUT_SEQUENCE_MAX. TransactionInput::isFinal(): bool tells you this
You won't be able to detect 0conf spends that don't opt into RBF as replaceable, unless you bobserve the RBF-optin transaction, then mark all child transactions in the tree as replacable until the RBF transaction confirms or is replaced.

@afk11 , Hi. I don't need to detect RBF, I need to mark my transaction as RBF. I construct it with TxBuilder and after that broadcast to network.

Oh, I see. When building the transaction, set the inputs sequence to a value < 0xfffffffe.
$txBuilder->spendOutPoint($utxo->getOutPoint(), null, $sequence);

or

$txBuilder->input($txid, $vout, null, $sequence);

Then you sign & broadcast. To replace the transaction, you need adhere to BIP125, but essentially it means adding an input to bump the fee and bumping the sequence number of existing inputs by one or more.
I put together an automated test for regtest, you can also run these scenarios on your dev machine by calling BITCOIND_PATH=/path/to/bitcoind vendor/bin/phpunit -c phpunit.rpc.xml

@afk11 , thanks. it's a little more clear now :)
one more question - can $sequence be just any positive integer like 0x1?
if i retransmit transaction it should be in any arbitrary larger number like 0xf?
should it be hex or can be dec?
can you recommend some tutorial or learning course on the whole bitcoin subject or may be even bit-wasp/bitcoin-php tutorial in particular? :) I started working in this industry, but still have a lot of questions and I don't want to annoy people with them :)
Thank you.

The tx structure is documented here: https://en.bitcoin.it/wiki/Protocol_documentation#tx
Yea, the sequence can be any positive integer from 0x0 -> 0xffffffff (uint32 max) is valid. Pass them as scalar integers (int|string), but not a hex string, that could cause problems.
Yea I'm not sure - I did most of my learning by reading https://en.bitcoin.it, the https://github.com/bitcoin/bitcoin repo, and looking at how different libraries implemented the specs. https://bitcoin.org has some developer oriented documentation around the protocol as well.
Another good place is the BIP's repo, which covers a lot of changes.. Just reading through all the ones roughly related to your areas of interest is a nice way to get acquainted with it all. IRC is often helpful as well if you have a quick question and need some help (#bitcoin, #bitcoin-dev, #bitcoin-wizards, #bitcoin-core-dev)
You can always post here too, but make sure you've looked into what you're trying to do first :) a lot of "how do I build a wallet" questions tend to go unanswered because it's too broad, and has too many possible answers :P but specific questions are great, and usually worth adding as an example anyways.

Did you resolve this issue?

Oh, yes. Sorry, i forgot to close the issue.
Thanks a lot.


Newest version 120 shows an error in the about-section

System Details

OS: MacOs Sonoma 14.3
Thorium Version 120.0.6099.235

Screenshots
https://prnt.sc/Qg43eRUikMuF

Confirmed. We try to fix that in the next version.

@midzer
One more thing:
This release is stressed to be M120.0.6099.273

However, I still get M120.0.6099.235 in About

Is there something wrong with it?

I just built vanilla Chromium tip-of-tree. The issue exists there, too.

Also did on Version 121.0.6167.204 (Official Build) (arm64)

Looks like it's fixed upstream starting at GoogleUpdater 122.0.6217.0 (or later?), going by the comments in this issue.


[DISCUSS][alert-spi] alert spi provides the implementation of script calls

Hi, most companies have their own set of alarm systems. It is relatively troublesome for users to expand the implementation of spi by themselves. Can we provide such an implementation for alert spi: support the call of shell or python scripts, the user writing scripts, alert center（support script call） is only responsible for calling the alert script.
大多数企业内部都有自己的一套告警体系，用户自己去扩展spi实现的话相对来讲比较麻烦，我们alert spi是否可以提供这样一种实现：支持调用shell或者python脚本的形式，用户自己编写脚本，alert只负责告警信息传递给相关的告警脚本。

close by #4063


Error encountered resolving symbol values statically

Please provide us with the following information:

OS?

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

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
@angular/cli: 1.0.0-beta.32.3 [1.0.0-beta.24]
node: 6.10.0
os: linux x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/flex-layout: 2.0.0-beta.5
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
@angular/compiler-cli: 2.4.8
@angular/cli: 1.0.0-beta.32.3

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
We did development on Windows/Mac. For production, we chose ubuntu. Fresh machine. Everything installed fresh. When we compile, we get following error

package.json file
{
  "name": "glam",
  "version": "0.0.0",
  "license": "MIT",
  "angular-cli": {},
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "lint": "tslint \"src/**/*.ts\"",
    "test": "ng test",
    "pree2e": "webdriver-manager update --standalone false --gecko false",
    "e2e": "protractor"
  },
  "private": true,
  "dependencies": {
    "@angular/common": "^2.3.1",
    "@angular/compiler": "^2.3.1",
    "@angular/core": "^2.3.1",
    "@angular/flex-layout": "^2.0.0-beta.1",
    "@angular/forms": "^2.3.1",
    "@angular/http": "^2.3.1",
    "@angular/material": "^2.0.0-beta.2",
    "@angular/platform-browser": "^2.3.1",
    "@angular/platform-browser-dynamic": "^2.3.1",
    "@angular/router": "^3.3.1",
    "@angular2-material/core": "^2.0.0-alpha.8-2",
    "angular-2-local-storage": "^1.0.0",
    "angular2-onsenui": "^1.0.0-rc.4",
    "core-js": "^2.4.1",
    "hammerjs": "^2.0.8",
    "ng2-material": "^0.8.1",
    "ng2-page-scroll": "^4.0.0-beta.2",
    "onsenui": "^2.0.5",
    "primeng": "^1.1.2",
    "rxjs": "^5.0.1",
    "ts-helpers": "^1.1.1",
    "zone.js": "^0.7.2"
  },
  "devDependencies": {
    "@angular/compiler-cli": "^2.3.1",
    "@types/jasmine": "2.5.38",
    "@types/node": "^6.0.42",
    "@angular/cli": "1.0.0-beta.32.3",
    "codelyzer": "~2.0.0-beta.1",
    "jasmine-core": "2.5.2",
    "jasmine-spec-reporter": "2.5.0",
    "karma": "1.2.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-cli": "^1.0.1",
    "karma-jasmine": "^1.0.2",
    "karma-remap-istanbul": "^0.2.1",
    "protractor": "~4.0.13",
    "ts-node": "1.2.1",
    "tslint": "^4.0.2",
    "typescript": "~2.0.3"
  }
}

The log given by the failure.

Normally this include a stack trace and some more information.

ng build
10% building modules 3/3 modules 0 active(node:24869) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Hash: aadb17976632b415a446
Time: 23846ms
chunk    {0} main.bundle.js, main.bundle.js.map (main) 180 kB {2} [initial] [rendered]
chunk    {1} styles.bundle.js, styles.bundle.js.map (styles) 194 kB {3} [initial] [rendered]
chunk    {2} vendor.bundle.js, vendor.bundle.js.map (vendor) 5.22 MB [initial] [rendered]
chunk    {3} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
ERROR in Error encountered resolving symbol values statically. Calling function 'FlexLayoutModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in /home/glamstudios/mobilesite/src/app/app.module.ts, resolving symbol AppModule in /home/glamstudios/mobilesite/src/app/app.module.ts
Mention any other details that might be useful.

Thanks! We'll be in touch soon.

This is an Angular compiler problem really not CLI problem.
convert any lambda () => something or function function something() {} to use export like:
export function getFlexLayoutModule() {
  return FlexLayoutModule;
}

@Meligy There seems to be a lot of confusion in regards to the AOT compiler, myself included. I am also running into some of these errors. Is there a guide anywhere on how to use the AOT compiler with angular cli? I see in the Angular guide https://angular.io/docs/ts/latest/cookbook/aot-compiler.html they recommend creating a separate tsconfig, tsconfig-aot.json. If so shouldn't this be a part of @angular/cli when a new project is created?
I have also read in the change log a while back that AOT is default when using --prod flag (which is fine). But I don't think most people will realize this right away, I know I didn't. With that said, is there a way to build --prod with the JIT compiler? This also doesn't appear to be documented anywhere. Or I am just not looking in the right places.  Any enlightenment/guidance on this subject would be much appreciated. Thanks,

Other relevant AOT issues:

https://github.com/angular/angular-cli/issues/4647
https://github.com/angular/angular-cli/issues/4551
https://github.com/angular/angular-cli/issues/4865
https://github.com/angular/angular-cli/issues/4294
https://github.com/angular/angular-cli/issues/4673
https://github.com/angular/angular-cli/issues/4239
https://github.com/angular/angular-cli/issues/4624
https://github.com/angular/angular-cli/issues/4043
https://github.com/angular/angular-cli/issues/3707

@deebloo, Thanks for the response. That at least clears up my confusion about tsconfig-aot.json. I will be looking forward to those updated docs.

Heya, errors like Error encountered resolving symbol values statically mean that there has been some problem in statically analyzing your app.
The CLI always runs statical analysis on code to ensure it will run when compiled with AOT. This may cause a lot of static analysis errors to surface when importing your project into the CLI, or upgrading for older versions where we didn't run this kind of analysis.
A good resource on how to to debug these errors is https://github.com/rangle/angular-2-aot-sandbox#aot-dos-and-donts.
Also, the examples shown in https://angular.io/docs/ts/latest/cookbook/aot-compiler.html are not using the CLI so they are very different.

I've been getting stuck on this issue with the error
Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 9:15 in the original .ts file)
I don't understand what's going on. Originally my file included
export const testIndexedDBCache = new InjectionToken('testIndexedDBCache');

export let testIndexedDBCacheProvider : Provider = {
  provide: testIndexedDBCache,
  useFactory: () => new IndexedDBCache('test')
  //          ^--- position of error
};

But even when I change the arrow function it still gets stuck on the same position!
export const testIndexedDBCache = new InjectionToken('testIndexedDBCache');

export let testIndexedDBCacheProvider : Provider = {
  provide: testIndexedDBCache,
  useFactory: function() { return new IndexedDBCache('test'); }
  //          ^--- position of error
};

Why exactly can't the AoT compiler use arrow functions for NgModule?

Karasuni, Angular 2 AOT is broken right now.  I wasted over a week trying to update my project to work with AOT. Now I am extremely far behind, and AOT still doesn't work. My advice is to just use the Uglify plugin.

I have a project that has been ejected to Webpack that seems to build AoT ok, but when I use NGC manually I run into this error.  What's the difference?

I get this error, when i first run build watch, but later when i change a file, it builds fine, :/ strange
ERROR in Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 36:31 in the original .ts file), resolving symbol routes in E:/www/htdoc
s/website/admin-src/src/app/app.routing.ts, resolving symbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts, resolving symbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts, resolving s
ymbol AppRoutingModule in E:/www/htdocs/website/admin-src/src/app/app.routing.ts

Is AOT even worth all the pain it causes? Why does angular need this while other libraries are doing just fine without it? Looks a lot like a fix to a problem that shouldn't exist.

@lifenautjoe probably because Angular is a few times larger than other libraries that do the same job, like vue.js. To be more precise, vue.js supports AOT through its loaders out of the box, but they don't talk about it that much so people don't even know that (maybe because vue.js is much smaller even without AOT, or because Angular causes so much pain while trying to set it up).

Without going into too much details, I worked around this by doing what the error's details suggested. Code that was erring out is:
import * as Modules from './modules'; ... imports: [ BrowserModule, RouterModule, ].concat(Object.keys(Modules).map(key => Modules[key]))
Fixed by creating a function and "exporting" it that creates an array out of the object Modules, like so:
export function joinImports() {   return {     Modules: Object.keys(Modules).map(key => Modules[key]),     LayoutComponents: Object.keys(LayoutComponents).map(key => LayoutComponents[key])   }; }
and then
imports: [     BrowserModule,     RouterModule   ].concat(joinImports().Modules),

@irtazabbas i tried your solution, compiling is ok, but modules are not imported

With the option -aot, I had to remove the dynamic references, meaning I had to explicitly import or declare components and modules, so that it can be analyzed statically. It was a bummer because I had to and will have to write more code, but you also do get the benefits of aot compilation mode. @skoropadas

Bug Report

[x] bug report
I cannot understand why all issues are closed but it got me annoyed to the death... Wasted whole day on this and still cannot understand why this code is not working

@NgModule({
    imports: [CommonModule]
})
export class StoreModule {
    static provideStore(): ModuleWithProviders {
        return {
            ngModule: StoreModule,
            providers: [ added some providers]
        };
    }
}

throwing an error:
"Calling function 'SotreModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule"

I compared it with RouterModule in .ts and .js all the same. Tried to many of work arounds and nothing.
In dev mode all works fine, when this code is added stright to project it works fine too, but when exported as a separate package - BAM - nothing!
Anybody?
For example RouterModule:
@NgModule({declarations: ROUTER_DIRECTIVES, exports: ROUTER_DIRECTIVES})
export class RouterModule {
  constructor(@Optional() @Inject(ROUTER_FORROOT_GUARD) guard: any, @Optional() router: Router) {}
  static forChild(routes: Routes): ModuleWithProviders {
    return {ngModule: RouterModule, providers: [provideRoutes(routes)]};
  }
}

If this thing will not be resolved I will not have any other way just to drop Angular support and stay only in react since this issue with ngc aot is very old.
More than that - when compiling AOT with webpack all works fine, just after upgrading to Angular 5.0.0 ngc-weback plugin is not working any more.
here is complete code of ng-state.module.ts:
import { Inject, Injector, ModuleWithProviders, NgModule, InjectionToken } from '@angular/core';
import { CommonModule } from '@angular/common';
import { Dispatcher } from './services/dispatcher';
import { Router } from '@angular/router';
import { RouterState } from './state/router-state';
import { ServiceLocator } from './helpers/service-locator';
import { State } from './state/state';
import { StateHistory } from './state/history';
import { StateHistoryComponent } from './state/state-history';
import { Store } from './store/store';

export const INITIAL_STATE = new InjectionToken('INITIAL_STATE');
export const COLLECT_HISTORY = new InjectionToken('COLLECT_HISTORY');
export const STORE_HISTORY_ITEMS = new InjectionToken('STORE_HISTORY_ITEMS');
export const IS_PROD = new InjectionToken('IS_PROD');

export function stateFactory(initialState) {
    return new State(initialState);
}

export function storeFactory(state: State<any>) {
    return new Store(state);
}

export function historyFactory(store: Store<any>) {
    return new StateHistory(store);
}

export function routerStateFactory(store: Store<any>, router: Router) {
    return new RouterState(store, router);
}

@NgModule({
    imports: [CommonModule],
    declarations: [StateHistoryComponent],
    exports: [StateHistoryComponent]
})
export class StoreModule {
    static provideStore(initialState: any, isProd?: boolean, collectHistory?: boolean, storeHistoryItems?: number): ModuleWithProviders {
        return {
            ngModule: StoreModule,
            providers: [
                { provide: STORE_HISTORY_ITEMS, useValue: storeHistoryItems },
                { provide: COLLECT_HISTORY, useValue: collectHistory },
                { provide: INITIAL_STATE, useValue: initialState },
                { provide: IS_PROD, useValue: isProd },
                { provide: State, useFactory: stateFactory, deps: [INITIAL_STATE] },
                { provide: Store, useFactory: storeFactory, deps: [State] },
                { provide: StateHistory, useFactory: historyFactory, deps: [Store, INITIAL_STATE] },
                { provide: RouterState, useFactory: routerStateFactory, deps: [Store, Router] },
                Dispatcher
            ]
        };
    }

    constructor(
        injector: Injector,
        stateHistory: StateHistory,
        routerState: RouterState,
        @Inject(INITIAL_STATE) initialState: any,
        @Inject(STORE_HISTORY_ITEMS) storeHistoryItems: any,
        @Inject(COLLECT_HISTORY) collectHistory: any,
        @Inject(IS_PROD) isProd: any
    ) {
        if (storeHistoryItems !== undefined) {
            StateHistory.collectHistory = collectHistory;
        }

        if (collectHistory !== undefined) {
            StateHistory.storeHistoryItems = storeHistoryItems;
        }

        ServiceLocator.injector = injector;
        stateHistory.init(initialState);
        routerState.init();

        if (!isProd) {
            (<any>window).state = StateHistory;
        }
    }
}

@vytautas-pranskunas- I know what you mean. the Angular team seems to be in denial about the scope of bug. One time, a legitimate issue was raised, and the bug was closed, with the comment "Thats the way it works"

i too have same issue
typescript error
Error encountered resolving symbol values statically. Expression form not supported (position 90:18 in the
original .ts file), resolving symbol AppModule in E:/Working Project/ngo/src/app/app.module.ts

I also met with the same issue has anybody resoved this type of issue when running in (ng build --prod ) my angular version is 4
ERROR in Error: Error encountered resolving symbol values statically. Reference to a local (non-                                             exported) symbol 'myDpStyles'. Consider exporting the symbol (position 9:7 in the original .ts file), resolving symbol MyDatePicker in D:/User/Karthik/test/07thaptilangular/AngularClient/node_modules/angular4-datepicker/src/my-date-picker/my-date-picker.component.ts

Hi , did anybody find the solution for that , i too get the same issue. It is strange we can able  to run it when we run as "ng build --env=prod". But facing issue with ng build --prod. Are they both same .


Fix for issue #63

Fix for issue #63 by introducing a new Brackets preference useLocalESLint.

Published as 3.1.0


[ZEPPELIN-682] New interpreter for Apache Beam (incubating)/DataFlow

What is this PR for?
The PR is a interpreter for Apache Beam which is an open source unified platform for data processing pipelines. A pipeline can be build using one of the Beam SDKs.
The execution of the pipeline is done by different Runners . Currently, Beam supports Apache Flink Runner, Apache Spark Runner, and Google Dataflow Runner.
What type of PR is it?

Feature

Todos

Test case
Review Comments
Documentation

What is the Jira issue?

[ZEPPELIN-682]

How should this be tested?

Start the Zeppelin server
The prefix of interpreter is %beam and then write your code with required imports and the runner

Screenshots (if appropriate)

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? yes

Thank you for contributing @mfelgamal ! Apache Beam interpreter is a valuable contribution many people are looking for.
There are few things that need to be done before we can merge it though:

this branch need to be rebased on top of the latest master (git rebase master) and conflicts must be resolved
establish the authorship of this work: this PR includes commits by you and @FouadMA
make sure that every file in this PR, as any other file in ASF project, contain Apache2.0 license header
make sure that every file is formatted according to project's code conventions: pom.xml, .jave, etc.
From the quick glance at the Java code:

please make sure you follow the conventions that are used in Zeppelin projects: brackets, sl4j logging. Best way is to look at other interpreters code
classes should have comments explaining their purpose and extra empty lines as well as @author tags need to be removed

zeppelin-distribution/src/bin_license must be updated to include ALL dependencies, AND their transitive dependencies that were added in this PR. You can see all of them in mvn dependency:tree.

Please, feel free to ping me after those issues are addressed and will be happy to look more into it and help you getting this merged!

@bzz The required changes is done, in the recent commit.

Thank you for addressing the feedback promptly! Please let me take another pass on it and get back to you here.

Before proceed with review - I have noticed that CI is failing.
@mfelgamal could you please take a look and make sure that there are no Beam-related failures? Thanks!
So far there is
[INFO] Zeppelin: Beam interpreter ......................... FAILURE [  6.632 s]
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:46 min
[INFO] Finished at: 2016-08-16T23:45:31+00:00
[INFO] Final Memory: 97M/414M
[INFO] ------------------------------------------------------------------------
....
[ERROR] Failed to execute goal on project zeppelin-beam: Could not resolve dependencies for project org.apache.zeppelin:zeppelin-beam:jar:0.7.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.beam:beam-runners-flink_2.11:jar:0.1.0-incubating, org.apache.beam:beam-runners-flink_2.11-examples:jar:0.1.0-incubating: Could not find artifact org.apache.beam:beam-runners-flink_2.11:jar:0.1.0-incubating in central (http://repo.maven.apache.org/maven2) -> [Help 1]

Which includes dependencies that I can not find mentioned in ./zeppelin-distribution/src/bin-license/LICENSE.

zeppelin-distribution/src/bin_license must be updated to include ALL dependencies, AND their transitive dependencies that were added in this PR

Could you take a look into it one more time please?

@bzz Kindly be noted that there is no maven Scala 2.11 build for beam runner Flink. The only available build is beam-runners-flink_2.10 .
https://mvnrepository.com/artifact/org.apache.beam/beam-runners-flink_2.10/0.1.0-incubating
Our pom file :
<artifactId>beam-runners-flink_2.10</artifactId>
<version>${beam.beam.version}</version>

That is why we hardcode it.
While the failure logs claims that maven can not find beam-runners-flink_2.11
It seems that your builder enforces the usage of Scala 2.11

Good work guys, probably this is the one other approach I missed in the JIRA, to have a static repl to compile the full class and then run it, this is nice because this can be reused for any full file Java case.
Just two comments:
I think that it is probably a good idea to move StaticRepl and BeamInterpreter to a more appropriate java package because this thing is a generic Java Repl/Interpreter (restricted to full class definitions). And I don't know if this is the case if it is worth dividing this into two PRs, one for the generic Java thing and other for the Beam specific part (notice that you can easily imagine reusing the java part e.g. to run a Spark or Flink note written in pure Java against a java ambient for example).
However I don't know the details of how (if) this reuse is possible in zeppelin, any hints @bzz ?

Oups I forgot the second comment, I don't know if it is also worth to separate every runner as a different interpreter (leaving probably the DirectRunner as the default Beam one). And having the others: beam-spark, beam-flink, beam-cloud-dataflow, as different ones.
Notice that this will reduce the size of the dependencies for casual use cases (that mostly can be run in local), but let open the option to run those in cluster mode extrictly when needed.

Let's make sure the new doc is added to the list in _navigation.html?
https://zeppelin.apache.org/docs/0.6.1/development/writingzeppelininterpreter.html#contributing-a-new-interpreter-to-zeppelin-releases

@felixcheung the requied changes is done.

It seems that your builder enforces the usage of Scala 2.11

@mfelgamal  you are right, .travis.yml contains Scala 2.11 as well as scala 2.10 profiles.
In this case, could you please explicitly exclude -pl "\!beam" from all such CI build profiles and put a comment\commit message like there is no maven Scala 2.11 build for Beam runner on Flink

@bzz I updated .travis.yml and there is an error while building Could not find the selected project in the reactor: '!beam' but the command -pl '!beam' run on local without any error.

@AhyoungRyu the changes is done.

@mfelgamal Thank you! Please let me look into CI and get back to you

@bzz Gentle reminder!

@mfelgamal thank you for kind reminder! Will try it more today and get back to you asap.
Meanwhile, it looks like it needs to be rebased on latest master.

@bzz rebased

Few questions after another pass:

Right now Beam interpreter uses Beam version 0.1.0-incubating, but didn't Beam project release 0.2.0-incubating on 2016-08-09? Do you think it would be useful to update it right here, before the merge or do you plan to do that in a separate PR later on?

AFAIK there are multiple "runners" for Beam, and right only be reading the doc you can see how to switch them. Do you think it would fit Zeppelin use case better if there are 3 different interpreters %beam.flink, %beam.spark, etc each with it's own appropriate configuration options and a user could just skip creating a class and defining main() {} in every paragraph?

Here is the list of dependencies from mvn dependency:tree. All of them will become part of the convenience binary for the next Zeppelin release. What is needed to be done, in order for us to merge it is:

make sure that ALL these dependencies
and ALL their transitive dependencies
have an appropriate licence, and are logged under the ./zeppelin-distribution/src/bin_license/LICENSE
and for non-Apache license, full text of the license need to be added to ./zeppelin-distribution/src/license/`

For your convenience I have listed all current dependencies of beam module below, please feel free to verify and mark those that satisfy the above criterias.
- [ ] org.apache.zeppelin:zeppelin-beam:jar:0.7.0-SNAPSHOT
- [ ] +- org.apache.spark:spark-core_2.10:jar:1.4.1:compile
- [ ] |  +- com.twitter:chill_2.10:jar:0.5.0:compile
- [ ] |  |  \- com.esotericsoftware.kryo:kryo:jar:2.21:compile
- [ ] |  |     +- com.esotericsoftware.reflectasm:reflectasm:jar:shaded:1.07:compile
- [ ] |  |     +- com.esotericsoftware.minlog:minlog:jar:1.2:compile
- [ ] |  |     \- org.objenesis:objenesis:jar:1.2:compile
- [ ] |  +- com.twitter:chill-java:jar:0.5.0:compile
- [ ] |  +- org.apache.spark:spark-launcher_2.10:jar:1.4.1:compile
- [ ] |  +- org.apache.spark:spark-network-common_2.10:jar:1.4.1:compile
- [ ] |  +- org.apache.spark:spark-network-shuffle_2.10:jar:1.4.1:compile
- [ ] |  +- org.apache.spark:spark-unsafe_2.10:jar:1.4.1:compile
- [ ] |  +- net.java.dev.jets3t:jets3t:jar:0.7.1:compile
- [ ] |  +- org.apache.curator:curator-recipes:jar:2.4.0:compile
- [ ] |  |  \- org.apache.curator:curator-framework:jar:2.4.0:compile
- [ ] |  |     \- org.apache.curator:curator-client:jar:2.4.0:compile
- [ ] |  +- org.eclipse.jetty.orbit:javax.servlet:jar:3.0.0.v201112011016:compile
- [ ] |  +- org.apache.commons:commons-lang3:jar:3.3.2:compile
- [ ] |  +- org.apache.commons:commons-math3:jar:3.4.1:compile
- [ ] |  +- com.google.code.findbugs:jsr305:jar:1.3.9:compile
- [ ] |  +- org.slf4j:slf4j-api:jar:1.7.10:compile
- [ ] |  +- org.slf4j:jul-to-slf4j:jar:1.7.10:compile
- [ ] |  +- org.slf4j:jcl-over-slf4j:jar:1.7.10:compile
- [ ] |  +- log4j:log4j:jar:1.2.17:compile
- [ ] |  +- com.ning:compress-lzf:jar:1.0.3:compile
- [ ] |  +- org.xerial.snappy:snappy-java:jar:<IP_ADDRESS>:compile
- [ ] |  +- net.jpountz.lz4:lz4:jar:1.2.0:compile
- [ ] |  +- org.roaringbitmap:RoaringBitmap:jar:0.4.5:compile
- [ ] |  +- commons-net:commons-net:jar:2.2:compile
- [ ] |  +- org.scala-lang:scala-library:jar:2.10.4:compile
- [ ] |  +- org.json4s:json4s-jackson_2.10:jar:3.2.10:compile
- [ ] |  |  \- org.json4s:json4s-core_2.10:jar:3.2.10:compile
- [ ] |  |     +- org.json4s:json4s-ast_2.10:jar:3.2.10:compile
- [ ] |  |     \- org.scala-lang:scalap:jar:2.10.0:compile
- [ ] |  |        \- org.scala-lang:scala-compiler:jar:2.10.0:compile
- [ ] |  +- com.sun.jersey:jersey-server:jar:1.9:compile
- [ ] |  |  \- asm:asm:jar:3.1:compile
- [ ] |  +- com.sun.jersey:jersey-core:jar:1.9:compile
- [ ] |  +- org.apache.mesos:mesos:jar:shaded-protobuf:0.21.1:compile
- [ ] |  +- com.clearspring.analytics:stream:jar:2.7.0:compile
- [ ] |  +- io.dropwizard.metrics:metrics-core:jar:3.1.0:compile
- [ ] |  +- io.dropwizard.metrics:metrics-jvm:jar:3.1.0:compile
- [ ] |  +- io.dropwizard.metrics:metrics-json:jar:3.1.0:compile
- [ ] |  +- io.dropwizard.metrics:metrics-graphite:jar:3.1.0:compile
- [ ] |  +- com.fasterxml.jackson.core:jackson-databind:jar:2.4.4:compile
- [ ] |  +- com.fasterxml.jackson.module:jackson-module-scala_2.10:jar:2.4.4:compile
- [ ] |  |  +- org.scala-lang:scala-reflect:jar:2.10.4:compile
- [ ] |  |  \- com.thoughtworks.paranamer:paranamer:jar:2.6:compile
- [ ] |  +- org.apache.ivy:ivy:jar:2.4.0:compile
- [ ] |  +- oro:oro:jar:2.0.8:compile
- [ ] |  +- org.tachyonproject:tachyon-client:jar:0.6.4:compile
- [ ] |  |  \- org.tachyonproject:tachyon:jar:0.6.4:compile
- [ ] |  +- net.razorvine:pyrolite:jar:4.4:compile
- [ ] |  +- net.sf.py4j:py4j:jar:<IP_ADDRESS>:compile
- [ ] |  \- org.spark-project.spark:unused:jar:1.0.0:compile
- [ ] +- org.apache.spark:spark-streaming_2.10:jar:1.4.1:compile
- [ ] +- org.apache.hadoop:hadoop-mapreduce-client-core:jar:2.3.0:compile
- [ ] |  +- com.google.protobuf:protobuf-java:jar:2.5.0:compile
- [ ] |  +- org.apache.avro:avro:jar:1.7.4:compile
- [ ] |  +- com.google.inject.extensions:guice-servlet:jar:3.0:compile
- [ ] |  \- io.netty:netty:jar:3.6.2.Final:compile
- [ ] +- org.apache.hadoop:hadoop-common:jar:2.3.0:compile
- [ ] |  +- com.google.guava:guava:jar:15.0:compile
- [ ] |  +- commons-cli:commons-cli:jar:1.2:compile
- [ ] |  +- xmlenc:xmlenc:jar:0.52:compile
- [ ] |  +- commons-httpclient:commons-httpclient:jar:3.1:compile
- [ ] |  +- commons-codec:commons-codec:jar:1.5:compile
- [ ] |  +- commons-io:commons-io:jar:2.4:compile
- [ ] |  +- commons-collections:commons-collections:jar:3.2.1:compile
- [ ] |  +- javax.servlet:servlet-api:jar:2.5:compile
- [ ] |  +- org.mortbay.jetty:jetty:jar:6.1.26:compile
- [ ] |  +- org.mortbay.jetty:jetty-util:jar:6.1.26:compile
- [ ] |  +- com.sun.jersey:jersey-json:jar:1.9:compile
- [ ] |  |  +- org.codehaus.jettison:jettison:jar:1.1:compile
- [ ] |  |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile
- [ ] |  |  +- org.codehaus.jackson:jackson-jaxrs:jar:1.8.3:compile
- [ ] |  |  \- org.codehaus.jackson:jackson-xc:jar:1.8.3:compile
- [ ] |  +- tomcat:jasper-compiler:jar:5.5.23:compile
- [ ] |  +- tomcat:jasper-runtime:jar:5.5.23:compile
- [ ] |  +- javax.servlet.jsp:jsp-api:jar:2.1:compile
- [ ] |  +- commons-el:commons-el:jar:1.0:compile
- [ ] |  +- commons-logging:commons-logging:jar:1.1.1:compile
- [ ] |  +- commons-lang:commons-lang:jar:2.5:compile
- [ ] |  +- commons-configuration:commons-configuration:jar:1.9:compile
- [ ] |  +- org.codehaus.jackson:jackson-core-asl:jar:1.8.8:compile
- [ ] |  +- org.codehaus.jackson:jackson-mapper-asl:jar:1.8.8:compile
- [ ] |  +- org.apache.hadoop:hadoop-auth:jar:2.3.0:compile
- [ ] |  |  \- org.apache.httpcomponents:httpclient:jar:4.3.6:compile
- [ ] |  |     \- org.apache.httpcomponents:httpcore:jar:4.3.3:compile
- [ ] |  +- com.jcraft:jsch:jar:0.1.42:compile
- [ ] |  +- org.apache.zookeeper:zookeeper:jar:3.4.5:compile
- [ ] |  \- org.apache.commons:commons-compress:jar:1.4.1:compile
- [ ] |     \- org.tukaani:xz:jar:1.0:compile
- [ ] +- org.apache.hadoop:hadoop-hdfs:jar:2.3.0:compile
- [ ] |  \- commons-daemon:commons-daemon:jar:1.0.13:compile
- [ ] +- org.apache.hadoop:hadoop-client:jar:2.3.0:compile
- [ ] |  +- org.apache.hadoop:hadoop-mapreduce-client-app:jar:2.3.0:compile
- [ ] |  |  \- org.apache.hadoop:hadoop-mapreduce-client-shuffle:jar:2.3.0:compile
- [ ] |  +- org.apache.hadoop:hadoop-yarn-api:jar:2.3.0:compile
- [ ] |  \- org.apache.hadoop:hadoop-mapreduce-client-jobclient:jar:2.3.0:compile
- [ ] +- org.apache.hadoop:hadoop-annotations:jar:2.3.0:compile
- [ ] |  \- jdk.tools:jdk.tools:jar:1.7:system
- [ ] +- org.apache.hadoop:hadoop-yarn-common:jar:2.3.0:compile
- [ ] |  +- javax.xml.bind:jaxb-api:jar:2.2.2:compile
- [ ] |  |  +- javax.xml.stream:stax-api:jar:1.0-2:compile
- [ ] |  |  \- javax.activation:activation:jar:1.1:compile
- [ ] |  +- com.google.inject:guice:jar:3.0:compile
- [ ] |  |  +- javax.inject:javax.inject:jar:1:compile
- [ ] |  |  \- aopalliance:aopalliance:jar:1.0:compile
- [ ] |  \- com.sun.jersey.contribs:jersey-guice:jar:1.9:compile
- [ ] +- org.apache.hadoop:hadoop-mapreduce-client-common:jar:2.3.0:compile
- [ ] |  +- org.apache.hadoop:hadoop-yarn-client:jar:2.3.0:compile
- [ ] |  \- org.apache.hadoop:hadoop-yarn-server-common:jar:2.3.0:compile
- [ ] +- org.apache.hadoop:hadoop-core:jar:1.2.1:compile
- [ ] |  +- org.apache.commons:commons-math:jar:2.1:compile
- [ ] |  +- org.mortbay.jetty:jsp-api-2.1:jar:6.1.14:compile
- [ ] |  |  \- org.mortbay.jetty:servlet-api-2.5:jar:6.1.14:compile
- [ ] |  +- org.mortbay.jetty:jsp-2.1:jar:6.1.14:compile
- [ ] |  |  \- ant:ant:jar:1.6.5:compile
- [ ] |  +- hsqldb:hsqldb:jar:<IP_ADDRESS>:compile
- [ ] |  \- org.eclipse.jdt:core:jar:3.1.1:compile
- [ ] +- com.thoughtworks.qdox:qdox:jar:2.0-M3:compile
- [ ] +- org.apache.beam:beam-runners-parent:pom:0.1.0-incubating:compile
- [ ] +- org.apache.beam:beam-runners-core-java:jar:0.1.0-incubating:compile
- [ ] |  \- org.apache.beam:beam-sdks-java-core:jar:0.1.0-incubating:compile
- [ ] |     +- io.grpc:grpc-all:jar:0.12.0:compile
- [ ] |     |  +- io.grpc:grpc-core:jar:0.12.0:compile
- [ ] |     |  +- io.grpc:grpc-okhttp:jar:0.12.0:compile
- [ ] |     |  |  +- com.squareup.okio:okio:jar:1.6.0:compile
- [ ] |     |  |  \- com.squareup.okhttp:okhttp:jar:2.5.0:compile
- [ ] |     |  +- io.grpc:grpc-protobuf-nano:jar:0.12.0:compile
- [ ] |     |  |  \- com.google.protobuf.nano:protobuf-javanano:jar:3.0.0-alpha-4:compile
- [ ] |     |  +- io.grpc:grpc-netty:jar:0.12.0:compile
- [ ] |     |  |  +- io.netty:netty-codec-http2:jar:4.1.0.Beta8:compile
- [ ] |     |  |  |  \- io.netty:netty-codec-http:jar:4.1.0.Beta8:compile
- [ ] |     |  |  \- com.twitter:hpack:jar:0.10.1:compile
- [ ] |     |  +- io.grpc:grpc-protobuf:jar:0.12.0:compile
- [ ] |     |  +- io.grpc:grpc-stub:jar:0.12.0:compile
- [ ] |     |  \- io.grpc:grpc-auth:jar:0.12.0:compile
- [ ] |     +- com.google.auth:google-auth-library-oauth2-http:jar:0.4.0:compile
- [ ] |     |  \- com.google.auth:google-auth-library-credentials:jar:0.4.0:compile
- [ ] |     +- io.netty:netty-handler:jar:4.1.0.Beta8:compile
- [ ] |     |  +- io.netty:netty-buffer:jar:4.1.0.Beta8:compile
- [ ] |     |  |  \- io.netty:netty-common:jar:4.1.0.Beta8:compile
- [ ] |     |  +- io.netty:netty-transport:jar:4.1.0.Beta8:compile
- [ ] |     |  |  \- io.netty:netty-resolver:jar:4.1.0.Beta8:compile
- [ ] |     |  \- io.netty:netty-codec:jar:4.1.0.Beta8:compile
- [ ] |     +- com.google.api.grpc:grpc-pubsub-v1:jar:0.0.2:compile
- [ ] |     |  \- com.google.api.grpc:grpc-core-proto:jar:0.0.3:compile
- [ ] |     +- com.google.apis:google-api-services-pubsub:jar:v1-rev10-1.22.0:compile
- [ ] |     +- com.google.apis:google-api-services-storage:jar:v1-rev71-1.22.0:compile
- [ ] |     +- com.google.http-client:google-http-client-jackson:jar:1.22.0:runtime
- [ ] |     +- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile
- [ ] |     \- com.google.cloud.bigdataoss:gcsio:jar:1.4.5:compile
- [ ] +- org.apache.beam:beam-runners-direct-java:jar:0.1.0-incubating:compile
- [ ] |  +- com.google.http-client:google-http-client-protobuf:jar:1.22.0:runtime
- [ ] |  +- joda-time:joda-time:jar:2.4:compile
- [ ] |  \- com.fasterxml.jackson.core:jackson-annotations:jar:2.7.2:compile
- [ ] +- org.apache.beam:beam-runners-flink_2.10:jar:0.1.0-incubating:compile
- [ ] |  +- org.apache.flink:flink-streaming-java_2.10:jar:1.0.0:compile
- [ ] |  |  +- org.apache.flink:flink-core:jar:1.0.0:compile
- [ ] |  |  |  \- org.apache.flink:flink-annotations:jar:1.0.0:compile
- [ ] |  |  +- org.apache.flink:flink-runtime_2.10:jar:1.0.0:compile
- [ ] |  |  |  +- org.javassist:javassist:jar:3.18.2-GA:compile
- [ ] |  |  |  +- com.typesafe.akka:akka-actor_2.10:jar:2.3.7:compile
- [ ] |  |  |  |  \- com.typesafe:config:jar:1.2.1:compile
- [ ] |  |  |  +- com.typesafe.akka:akka-remote_2.10:jar:2.3.7:compile
- [ ] |  |  |  |  \- org.uncommons.maths:uncommons-maths:jar:1.2.2a:compile
- [ ] |  |  |  +- com.typesafe.akka:akka-slf4j_2.10:jar:2.3.7:compile
- [ ] |  |  |  +- org.clapper:grizzled-slf4j_2.10:jar:1.0.2:compile
- [ ] |  |  |  \- com.github.scopt:scopt_2.10:jar:3.2.0:compile
- [ ] |  |  +- org.apache.sling:org.apache.sling.commons.json:jar:2.0.6:compile
- [ ] |  |  \- org.apache.flink:force-shading:jar:1.0.0:compile
- [ ] |  +- org.apache.flink:flink-java:jar:1.0.0:compile
- [ ] |  |  \- org.apache.flink:flink-shaded-hadoop2:jar:1.0.0:compile
- [ ] |  |     +- com.jamesmurty.utils:java-xmlbuilder:jar:0.4:compile
- [ ] |  |     +- commons-digester:commons-digester:jar:1.8.1:compile
- [ ] |  |     \- commons-beanutils:commons-beanutils-bean-collections:jar:1.8.3:compile
- [ ] |  \- org.apache.flink:flink-clients_2.10:jar:1.0.0:compile
- [ ] |     \- org.apache.flink:flink-optimizer_2.10:jar:1.0.0:compile
- [ ] +- org.apache.beam:beam-runners-flink_2.10-examples:jar:0.1.0-incubating:compile
- [ ] |  \- org.apache.flink:flink-connector-kafka-0.8_2.10:jar:1.0.0:compile
- [ ] |     +- org.apache.flink:flink-connector-kafka-base_2.10:jar:1.0.0:compile
- [ ] |     |  \- com.101tec:zkclient:jar:0.7:compile
- [ ] |     \- org.apache.kafka:kafka_2.10:jar:<IP_ADDRESS>:compile
- [ ] |        +- org.apache.kafka:kafka-clients:jar:<IP_ADDRESS>:compile
- [ ] |        \- com.yammer.metrics:metrics-core:jar:2.2.0:compile
- [ ] +- org.apache.beam:beam-runners-google-cloud-dataflow-java:jar:0.1.0-incubating:compile
- [ ] |  +- com.google.api-client:google-api-client:jar:1.22.0:compile
- [ ] |  +- com.google.apis:google-api-services-datastore-protobuf:jar:v1beta2-rev1-4.0.0:compile
- [ ] |  +- com.google.oauth-client:google-oauth-client:jar:1.22.0:compile
- [ ] |  +- com.google.http-client:google-http-client:jar:1.22.0:compile
- [ ] |  +- com.google.apis:google-api-services-dataflow:jar:v1b3-rev26-1.22.0:compile
- [ ] |  +- com.google.apis:google-api-services-clouddebugger:jar:v2-rev8-1.22.0:compile
- [ ] |  +- com.google.apis:google-api-services-bigquery:jar:v2-rev295-1.22.0:compile
- [ ] |  +- com.google.cloud.bigdataoss:util:jar:1.4.5:compile
- [ ] |  |  +- com.google.api-client:google-api-client-java6:jar:1.20.0:compile
- [ ] |  |  \- com.google.api-client:google-api-client-jackson2:jar:1.20.0:compile
- [ ] |  \- com.fasterxml.jackson.core:jackson-core:jar:2.7.2:compile
- [ ] +- org.apache.beam:beam-runners-spark:jar:0.1.0-incubating:compile
- [ ] |  +- org.apache.beam:beam-examples-java:jar:0.1.0-incubating:compile
- [ ] |  |  \- javax.servlet:javax.servlet-api:jar:3.1.0:compile
- [ ] |  \- org.apache.avro:avro-mapred:jar:hadoop2:1.7.7:compile
- [ ] |     +- org.apache.avro:avro-ipc:jar:1.7.7:compile
- [ ] |     |  \- org.apache.velocity:velocity:jar:1.7:compile
- [ ] |     \- org.apache.avro:avro-ipc:jar:tests:1.7.7:compile
- [ ] +- org.apache.commons:commons-exec:jar:1.3:compile

Hope this helps, and please let me know if you have any questions!

@bzz  kindly be noted for point # 2:
Making user do minimal amount of code is good but the only cons is that the user will be given the default implementations and configurations and can not change it. This constraint is because we are using a very basic java REPL implementation. If this is fine, we can proceed and implement it!
What do you think about that?

@bzz  The following updates are made:
1 - Updating beam version from 0.1 to 0.2
2 - License report is updated for all dependencies
Regarding point #2 in the previous message, do you have any further discussion on it. I think we should make it as is for now.

I think having it as it is now sounds as a good start. It can be always enhanced it later on, based on user feedback.
Changes look great to me, thank you!
If that is ok - please let me test it more over the weekend and merge it early next week, if there is no further discussion!

After running it locally, I think it is great but the last thing that would be very nice to have, is to expand the example in the docs to be self-contained, meaning easily runnable by the the first-time Beam user.
Also rebase this branch on the latest master is needed (I guess .travis.yaml was changed a bit by skipping RAT in all default profiles)

@bzz all required changes are done.

Looks great to me, thank you @mfelgamal !
I think it's ready to be merged.
The only minor thing that looks a bit off - re-formatted pom.xml is not consistent with the other modules, where just two spaces indentation is used, see root pom.xml as an example.
If that is not hard - could you format pom.xml again please, for maintainability, with 2 white space indentation settings?
I'll be happy to merge it right after!

@mfelgamal to address 1-2 can you please try to update .travis.yml:  -pl \!beam -> -pl !beam ?

@bzz the changes are done, could you take a look at pom file and CI ?

CI is still failing.
Sorry for confusion, after a bit more thinking it looks like simplest way here actually will be - to follow the same convention as with any other interpreters, like geode, sparkr,  pyspark  or scalding:

create a beam profile in root ./pom.xml that brings Beam module. See i.e scalding
explicitly add -Pbeam only to CI envs lines in .travis.yml, that already have scala 2.10
create a ./beam/README.md file and add some implementation details about interpreter impl there i.e it's a good place to mention that right now only Scala 2.10 is supported due to Flink runner.

This will allow avoid any possible CI issues in future and keep build modular.

@bzz done.

@bzz Gentle reminder!

@felixcheung required changes are done.

@felixcheung done, and now it checks if the main method is static or not.

Last 2 profile in CI are failing
[INFO] Zeppelin: Display system apis ...................... FAILURE [  2.537 s]

- should provide onclick method *** FAILED ***
  The code passed to eventually never returned normally. Attempted 1 times over 193.154233 milliseconds. Last failure message: 0 was not equal to 1. (AbstractAngularElemTest.scala:72)
AngularElem

and
[INFO] Zeppelin: Server ................................... FAILURE [07:56 min]

Tests in error:
  AuthenticationIT.testGroupPermission:179->AbstractZeppelinIT.pollingWait:96 Â» Timeout

Tests run: 15, Failures: 0, Errors: 1, Skipped: 0

which seems not related to changes.
Let's wait if @felixcheung have more feedback, and merge to master if all issue are addressed.

LGTM other than the minor comment on static check

@bzz @felixcheung Thank you for your reviews.

Great, thank you @mfelgamal for great job laying foundation for Apache Beam integration! I hate to ask but, could you please rebase it on latest master one more time? Looks like it have diverged a bit..
I will be happy to merge it to master ASAP right after that.

@bzz rebased.

Thank you @mfelgamal !
Merging to master, if there is no further discussion

@bzz For me, no further discussion. looking forward to seeing the PR merged.

Thank you so much @mfelgamal !

Congratulations guys, excellent work !

@mfelgamal or @bzz you must announce this milestone in the beam mailing list too.

:+1:!

Great work guys!


feat: cookie parameters in proxy configuration

This PR fixes https://github.com/IdentityPython/SATOSA/issues/344 introducing the following paramenters to be optionally handled in the proxy global configuration.
Secure
Now can be disabled via COOKIE_SECURE: no in proxy_conf.yaml.
Default: True
that's only for dev purpose!
HttpOnly
To avoid cross-site scripting (XSS) attacks, cookies set with the HttpOnly directive are inaccessible to the JavaScript Document.cookie API. For example, session cookies don't need to be accessed by JavaScript and should therefore be set with the HttpOnly flag.
Default: True
parameter name eg: COOKIE_HTTPONLY: no
Domain, COOKIE_DOMAIN
Max-Age, COOKIE_MAX_AGE
it come also  with some minor code linting and f-strings, few things.
All Submissions:

[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you added an explanation of what problem you are trying to solve with this PR?
[x] Have you added information on what your changes do and why you chose this as your solution?
[ ] Have you written new tests for your changes?
[x] Does your submission pass tests?
[x] This project follows PEP8 style guide.

It seems that here we have a collision
https://github.com/IdentityPython/SATOSA/blob/1def9986e5c32baa5f95be835cf5843d9f9ab5d8/src/satosa/frontends/saml2.py#L558
anyway, with my PR I tested in the user-agent debugger and it seems that SATOSA cookie respects the global configuration parameter, instead of the frontend ones.
I think that we should have to decide if keep cookie paramenters in the plugins or move them in the global configuration and refactor/cleanup/reduce all those hardcodings

@peppelinux we will be merging this PR.
The SimpleCookie created by the frontend is a separate one, it has a different purpose and should not conflict the cookie that the proxy is using to store state.

closed by 1206ea5

This PR should have been taken
Since the code committed Is equal or similar
There are some cases where a PR Is not perfect but it's 80% Is
In these cases the mantainers can add their commits Upon the PR made by the community
This preserve the contribution in the history of the commits, giving a gratificazione to contributions
If this doesn't happen, what would be the value to contribute in a project?
This Is not project management or product design, this Is social Exchange and I think that out community needs should be able to apply these mechanism to gather contributions and value in the projects

@peppelinux you are right and I will try to do that in the future ❤

Even if the priority Is the release (output, the "what") the process to achieve this is important (the how)
I'm Happy of this brand new release, at the same time we may had a pull request to understand the "what" and the "how"
We should also take in account that a release that introduces these features needs testing, because i dont know which Will be the impact of this release on the systems in production and there might be the possibility to test these in a PR/branch, before a release
This Is just for sharing, I look forward with you
Ad maiora


add force isolation, add force register to create

Change to import isolation logic means that we're importing things via that logic, this yields tests failing.


Bug: PD tip positioning graphic doesn't match value

See https://github.com/Opentrons/opentrons/issues/9227
Expected behavior: tip position graphic more closely matches value

closed by RQA-164


fix: Resolve list widget Error

Description
This PR resolves an issue with the List widget caused by infinite auto height update loops. The child widgets of the List widget already have the isMetaWidget flag, which prevents auto height updates. However, the List widget itself did not have this flag, leading to the issue. This fix ensures that the isMetaWidget flag is also applied to the List widget, preventing the infinite update loop.
Fixes #37683
Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Summary by CodeRabbit

New Features

Introduced a new property isMetaWidget for the ListWidgetV2, enhancing its configuration.

Bug Fixes

Resolved an issue causing an infinite loop of auto height updates in the List widget.

@albinAppsmith review

Hi @rahulbarwal,
I added tests. Could you please check the PR?

@saharAdem I think the solution is incorrect here, we shouldn't add isMetaWidget to the default props as it would lead to isMetaWidget: true for every dropped list widget and this will have some implications.
I was checking out the issue and it seems if I have 2 buttons outside the list, use one to close and the other to open; it does not crashes so something else goes wrong when the list item is clicked and List1.setVisibility(false) is triggered.

I believe the issue is caused by an infinite loop of auto-height updates. I will investigate further. However, this has occurred multiple times when using the list widget.


Version 0.4.29

This will publish fixes for https://github.com/metarhia/impress/issues/852
Also we can include this fixes https://github.com/metarhia/impress-cli/pull/36
@belochub @lundibundi

Landed in fa5c176


kernel error, but saspy works

The sas_kernel installed successfully, but when I tried to run the jupyter notebook, the console says:
No module named sas_kernel.__main__; 'sas_kernel' is a package and cannot be directly executed

I've verified that the saspy module works.

@yinhao,
Can you give me some details about your setup so we can track this down?

Did the steps in the install guild work as expected? https://sassoftware.github.io/sas_kernel/install.html

What OS is your jupyter notebook server running on?

What OS is your SAS server running on?

What browser are you using?

What is you output when you run

import saspy
saspy.__version__
import sas_kernel
sas_kernel.__version__

@jld23
Thank you for the prompt reply.
I found the reason why the kernel failed. As the server I am using has no network connection, I have to upload the source file and setup it on my own. Then I create a folder named 'sas_kernel' in the home root directory to store the source files.
The issue was fixed after I moved the install file to somewhere else.


How to configure a map rotation through maps in northstar

Given the following how do I give it a set of maps to rotate through, while staying in gungame??
Currently when the map ends it switches to attrition
---
version: '3'
services:
  titanfall2-gungame:
    image: ghcr.io/pg9182/northstar-dedicated:1-tf<IP_ADDRESS>
    pull_policy: always
    environment:
      - NS_PORT=37015
      - NS_SERVER_NAME=Test
      - |
        NS_EXTRA_ARGUMENTS=
          +setplaylist private_match
          +mp_gamemode gg
          +map mp_glitch
          +ns_should_return_to_lobby 0
          +net_compresspackets_minsize 64
          +net_compresspackets 1
          +spewlog_enable 0
          +sv_maxrate 127000
          +ns_auth_allow_insecure 1
    volumes:
      - /home/james/Titanfall2:/mnt/titanfall:ro
      - /home/james/Titanfall2/mods:/mnt/mods:ro
    ports:
      - '37015:37015/udp'

bump @GeckoEidechse ☝

Sorry, forgot to respond to this. I think the most common approach to achieve a specific map rotation is to use the MapSelect mod from Thunderstore.
+map only specifies the initial map, after that it follows rotation specified in the playlist. No clue why it jumped to Attrition as the gamemode for you though.


Not working with filenames containing text after the date

Figured out an easy solution with a simple modification in the plugin source code:
edit main.js under .obsidian/plugins/journal-review
locate the following line in funtion getDateFromFilename(file, granularity)
const noteDate = window.moment(filename, format, true);
change the last argument "true" to "false" to disable strict parsing: https://momentjs.com/guides/#/parsing/strict-mode/

Hello and thanks for using my simple plugin :)
Unfortunately, the piece of code you are referring to is not part of my plugin itself, but another library used to access the daily notes.
Therefore, I cannot directly implement this feature here, but would have to adjust said library.
Can you also give an example how you have configured your daily notes to work with text after the dates? I quickly tried this with my current setup with the periodic notes plugin, but this doesn't seem to work for me, as there seems to be no way to configure the note format to include other arbitrary texts. How did you configure your daily notes for that?

Hello and thanks for your reply.
My Daily Notes date format is configured with the default "YYYY-MM-DD" but
I like to add a title after the date to my notes, like this "2023-06-12
Beach day". Since the resulting filename doesn't strictly match the format,
these notes are not taken into account, but with the proposed change they
are.
It would be nice to have support for these types of notes somehow in your
plugin.
Thank you.
On Mon, Jun 12, 2023 at 11:31 AM Kageetai @.***> wrote:

Hello and thanks for using my simple plugin :)
Unfortunately, the piece of code you are referring to is not part of my
plugin itself, but another library used to access the daily notes.
Therefore, I cannot directly implement this feature here, but would have
to adjust said library.
Can you also give an example how you have configured your daily notes to
work with text after the dates? I quickly tried this with my current setup
with the periodic notes plugin, but this doesn't seem to work for me, as
there seems to be no way to configure the note format to include other
arbitrary texts. How did you configure your daily notes for that?
—
Reply to this email directly, view it on GitHub
https://github.com/Kageetai/obsidian-plugin-journal-review/issues/6#issuecomment-1586956256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAPP55BPZQNJO7UA5MSRVLLXK3OYLANCNFSM6AAAAAAZCMHZQQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hmm, out of curiosity, with your current configuration, does it still open the same note after adding a name to it, when you click "open today" or so?
I mean for me when I try that, add a name to my daily note today, and then use the command "open daily note", it creates a new note, instead of reopening the note I just edited before.
I can look into supporting that, but I think it might not be entirely possible, as I am just using the same configuration the core daily note plugin is using to create and open notes.

Yes, you're right. The core Daily Notes plugin doesn't take into account these notes which do not strictly match the configured date format.
The thing is that I'm using the Calendar community plugin with the same behavior by default but I've done the same proposed change in the call to the moment() function to make it work. See https://github.com/liamcain/obsidian-calendar-plugin/discussions/90#discussioncomment-6144763

I see, this same solution has the same problem as here for me, you are not adjusting the calendar plugin itself, but the code from the library it uses to fetch the daily notes. Therefore we cannot fix this on our side (me or the developer of the calendar plugin), but it needs to be fixed on with that underlying library here.
You can bring this up to that repo over there. But maybe that developer had a reason to use the strict mode.

Well it looks like the library you mentioned is developed by the same author than the Calendar plugin. I guess he could parameterize the call to the parsing function to be strict or not, based on a plugin setting... Although this wouldn't fix the core "open daily note" functionality, the Calendar and Journal Review would support non-strict daily notes filenames.
Just an idea...
Thanks

Yes, making this somewhat adjustable via plugin settings would be ideal. You can suggest this to the developer of these plugins.
From the same person is also the Period Notes plugin, which I am currently using instead of the core plugin, maybe this can just be fixed there for all places then.

Feature requested in the underlying library: https://github.com/liamcain/obsidian-daily-notes-interface/issues/27

Awesome, thanks for that. Whenever that might be merged, I can adjust settings on my plugin if needed.