Removed use of catch_warnings

Closes #5536.
Removed catch_warnings, by moving the functionality to parse_cell_methods()

Before:

After:

Compare with https://github.com/SciTools/iris/pull/5506#issuecomment-1729102179

Should there have been a What's New entry here?


launchTestNode on 0.90.0 ts returns _FuelError: Unknown field "alocDependentCost" on type "GasCosts".

What version of fuels-ts are you using?
0.90.0
Steps to Reproduce
Create nodejs test script:
import { launchTestNode } from "fuels/test-utils";

(async () => {
    try {
        console.log("Starting node");
        while (true) {
            const launched = await launchTestNode();
            console.log("Launched node");
            console.log(launched);
        }
    } catch (e) {
        console.error(e);
    }
})();

And run through node --loader ts-node/esm localNode.ts
Expected Behavior
Launch a local fuel-core test node.
Actual Behavior
Errors out with
_FuelError: Unknown field "alocDependentCost" on type "GasCosts".
    at responseMiddleware (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/account/dist/test-utils.mjs:3898:19)
    at /Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/graphql-request/dist/index.js:284:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async _Provider.fetchChain (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/account/dist/test-utils.mjs:3964:23)
    at async _Provider.fetchChainAndNodeInfo (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/account/dist/test-utils.mjs:3862:19)
    at async _Provider.create (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/account/dist/test-utils.mjs:3793:5)
    at async setupTestProviderAndWallets (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/account/dist/test-utils.mjs:8995:16)
    at async launchTestNode (file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/node_modules/@fuel-ts/contract/dist/test-utils.mjs:69:42)
    at async file:///Users/calvin/Documents/DO/0172_Props/projects/fuel/fuel-scripts/localNode.ts:6:30 {
  VERSIONS: { FORC: '0.60.0', FUEL_CORE: '0.30.0', FUELS: '0.90.0' },
  metadata: {},
  code: 'invalid-request'
}

@xpluscal Which version of fuel-core are you using? It should be 0.30.0. Please run fuel-core --version and get back to us.

@nedsalk interesting! My error code returned 0.30.0 but fuel-core --version returned 0.26.0!
How do I separately update fuel-core? I have not seen instructions in the docs. Thx!

@nedsalk FYI I used the default suggested fuelup installation including fuelup update

@nedsalk latest toolchain in fuelup returns:
Installed:

forc 0.60.0
forc-explore 0.28.1
forc-wallet 0.7.1
fuel-core 0.26.0
fuel-core-keygen 0.26.0

@xpluscal the best way to go about this until the latest tag issue is sorted out is for you to setup a custom toolchain:
fuelup toolchain new my_toolchain && fuelup component add<EMAIL_ADDRESS>&& fuelup component add<EMAIL_ADDRESS>This will work with version 0.90.0 of the TS SDK. Version 0.91.0 will be released soon, at which point I suggest you update forc to 0.61.1: fuelup component add<EMAIL_ADDRESS>

Another option is to use the nightly toolchain:

https://docs.fuel.network/guides/installation/#installing-nightly-toolchain

fuelup toolchain install nightly
fuelup default nightly
fuelup show

It seems like the automation here didn't work, probably because of the multiple label and status changes, etc. so I'll close it manually.


chore: make oxc_index dependency on serde optional.

nothing fancy here, just a simple change.

#3103  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rzvxa and the rest of your teammates on  Graphite

Merge activity

Apr 26, 8:34 AM EDT: @Boshen started a stack merge that includes this pull request via Graphite.


[5.5] Implement iterable Gate::check() and Gate::any()

Premise
This is a simplified version of PR #19900, which adds two new capabilities to the Gate class:

updates check() method to allow an array or collection of abilities to test that every ability passes.
adds an any() method that takes an array or collection of abilities and checks if any one of those abilities passes.

In conjunction with the new Blade::if shorthand methods, this will make checking multiple abilities for a model in one go very simple.
Background
The initial PR was unable to be resolved as we couldn't come up with a good method name that succinctly captured the intent and different to the @can Blade directive, or the can() method in the Authorizable trait. Should a suitable name for the Gate::any() method be found, a subsequent PR will implement it as a new Blade directive and method on the Authorizable trait, as well as update the @can directive and can() method.
Examples
Blade::if('canEvery', function ($abilities, $arguments) {
    return app(Gate::class)->forUser(auth()->user())
        ->check($abilities, $arguments);
});

Blade::if('canAny', function ($abilities, $arguments) {
    return app(Gate::class)->forUser(auth()->user())
        ->any($abilities, $arguments);
});

Thanks

Thanks Taylor! :)


modal boxes for cards

updated home.jsp with modal box functionality.
allows user to click on cards, opening and closing a view with text specific to the card

not sure why
Alexandria/target/m2e-wtp/web-resources/META-INF/maven/Alexandria/Alexandria/pom.properties
is different. it's specified by the .gitignore

I removed the Servers folder from the branch.
Please correct if incorrect.


About RPC errors

When I run "docker logs bucket",
rpc err: [ws://<IP_ADDRESS>:9944] [st] [Sminer.Expenders] CreateStorageKey: module Sminer not found in metadata

I get the above error.
I added "wss://testnet-rpc2.cess.cloud/ws/" to config.yaml but it does not improve.
Is there any way to deal with this?

@unkomoreta11 Your old chain from the last version seems to still be running, and your block height is already higher than the latest version of the chain, so you'll have to stop the old chain before running it again.


Requirement for storage mount points to be specified breaks payu from conda

NCI have turned on the requirement to specify all gdata and scratch mount points explicitly in the qsub call. It does default to including the /scatch/$PROJECT mount point.
For those using payu from a conda environment under a /g/data mount point it means this gdata mount must be included in the qsub call or payu will fail as soon as the job is launched as  the conda environment will not be accessible.
A work-around is to include:
qsub_flags: -l storage=gdata/hh5

in the config.yaml of an experiment.
I am looking into code changes to support this. An immediate thought is to inspect the path to payu and add any gdata or scratch mount point found.
This would be very very NCI specific, which this tool is, but also moves further away from the goal of making this as general as possible.
I would also like to add code to inspect include and executable paths and add mount points as appropriate.
Another option is to just add every possible mount point a user can access automatically to every qsub, but that seems a rather crude approach.

I think platform-specific stuff like this is inevitable, seems fine to me.
Maybe the easiest thing is to just add a storage: record to config.yaml and make it mandatory on NCI?

Good idea. A storage flag would make it easier to specify, could do something like
storage:
      - gdata:
              - ik11
              - v45
      - scratch:
              - x77

to make it easier to specify.
My main issue with having to specify this stuff independently is that it is error prone and annoying.
Ideally payu should parse all the input, exe and laboratory paths and extract the necessary storage information and add it automatically.
It is easy to do this for the python interpreter path, and the path to payu itself (in the case of the conda environment, this is the same root path). Doing it for the other paths, input etc, requires payu to work differently than it does currently. At the moment payu run only parses config.yaml for the PBS information necessary to submit the job.
Obtaining all the path information would either require duplicating code to extract path information from config.yaml, or using the existing code to instantiate an experiment and extract the path information once that is done. That sounds a bit like doing payu setup before the run is submitted, which I know was something you were toying with @marshallward.
I think your idea of a storages variable is necessary, and might even be required in case there were storage mount points that were required that could not be automatically determined.
BRAIN WAVE!
We could use the manifest to determine paths and mount points, so no need for payu setup in general. It would require a manifest to be present, which would mostly be the case. When not present a simple payu setup would generate them for those less common occasions.

Hi @aidanheerdegen - just checking, does the closure of this issue mean I can remove this line from config.yaml?
qsub_flags: -l storage=gdata/hh5+gdata/qv56+gdata/ik11+gdata/ua8
https://github.com/COSIMA/01deg_jra55_iaf/blob/9f431cba76a4665c6966ebd26cc842fc71bce0ef/config.yaml#L68

Yes, but I think you'll need to add
storage:
    gdata:
           - hh5

As hh5 is not in any of the paths that payu searches for storage path information, and you'll need that mounted to sync data. If you change to sync to ik11 it shouldn't be necessary as that is in the input paths IIRC.

we don't want any more storage to hh5 so I'll leave that out of the new configs.


Display contribution policy in contribution flow

We want to display collective's contribution policies in the contribution flow FAQ when they have one.
Design: https://www.figma.com/file/ZQBMWhnGGtRWeIZknFW1eP/[OC.com]-Production-Ready-✅?node-id=4489%3A3180

@Betree can i assist you on this?

Sorry I missed you message @vickywane, thanks for proposing your help, I already have a resolution for this issue that should be pushed today along with other updates to the contribution flow.

Alright


Update README.md

Updated installation instructions for when #29 is merged

Added these onto #29 - thank you!


gulp.watch significantly slows compilation

According to the docs gulp.watch should be used for incremental compilation.
This is, however, significantly slower than using tsc --watch.
Consider a tsconfig.json similar to this:
{
  "compilerOptions": {
    "target": "es6",
    "declaration": false,
    "noImplicitAny": true,
    "removeComments": false,
    "noLib": false,
    "sourceMap": true,
    "jsx": "react",
  }
}

and a gulp task similar to:
var shell = require("gulp-shell");

gulp.task("ts_watch", shell.task([
        "tsc --watch"
]));

re-compilation speed is improved significantly.
Unless I'm incorrectly using the steps outlined in the docs?
Thoughts?

Can you post your gulpfile?

I've spotted where I think the problem might be (and it's on my side). Apologies, let me revert once I've tested my hypothesis.

Apologies, it turns out this is something of my own making. Closing


[Toolchain] Combine the requests to the toolchain into ToolchainProvider

This commit combines the requests to the toolchain into ToolchainProvider.
ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>

Please review this PR :)

@jyoungyun I'd like to know a few things. Maybe others do too. 😃

Is is a reactoring task?
or why is it necessary? (I ask because the commit message doesn't contain the reason.)
No UI change?

Is is a reactoring task?

Yes, this is a refactoring task for managing all toolchain job at toolchainProvider.
There was no main ui changes but it added several error logs like this:
              Logger.error(this.tag, 'Installation is failed');
              vscode.window.showErrorMessage('Installation is failed');


Fix: Update all terms to lower case

#52

Hi, I would be interested in contributing to this. Would also need clarification I'm seeing terms.json is in lowercase should it be capitalised or which file with terms are you referring to ✊🚀

Hi, I would be interested in contributing to this. Would also need clarification I'm seeing terms.json is in lowercase should it be capitalised or which file with terms are you referring to ✊🚀

Thank you @jebitok-dev
The issue was to fix the content inside the terms.json, not the name itself. Someone already sent a PR. 🥲


Add support for signature_request/files/[:id]?get_url=1

Closes issue #43

@cmpaul made the requested changes, if you don't mind taking a look 👍


Grey water texture with optifine G5 custom colors

This is without a resource pack

This is with

"Brighter Water"=false, "New Water"=false, "New Water Fog"=false
There are no other mods except MixinBootstrap, AquaAcrobatics and OptiFine G5

Something was wrong with the settings. It's working now.


[Bug] mlc4j:compileDebugKotlin FAILED, upertypes of the following classes cannot be resolved

When running ./gradlew assembleDebug, an error occurs:
> Task :mlc4j:compileDebugKotlin FAILED
e: Supertypes of the following classes cannot be resolved. Please make sure you have the required dependencies in the classpath:
    class ai.mlc.mlcllm.JSONFFIEngine, unresolved supertypes: Object
    class ai.mlc.mlcllm.JSONFFIEngine.KotlinFunction, unresolved supertypes: Object
    class kotlin.Pair, unresolved supertypes: java.io.Serializable
    class org.apache.tvm.TVMValue, unresolved supertypes: java.lang.Object
Adding -Xextended-compiler-checks argument might provide additional information.

e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:12:13 Unresolved reference: util
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:13:13 Unresolved reference: util
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:18:9 Cannot access class 'java.lang.Thread'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:18:9 Cannot access class 'java.lang.ClassLoader'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:36:23 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:37:34 Cannot access class 'String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:37:34 Type mismatch: inferred type is String! but kotlin.String? was expected
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:41:13 Unresolved reference: Thread
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:41:36 Variable expected
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:41:47 Unresolved reference: Thread
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:42:27 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:46:27 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:64:23 Cannot access class 'String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:64:23 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:64:30 Type mismatch: inferred type is kotlin.String but String! was expected
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:68:23 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:72:23 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:83:26 Unresolved reference: Logger
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:83:62 Cannot access class 'java.lang.Class'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:83:67 Unresolved reference: name
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:92:25 Unresolved reference: UUID
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:97:23 Cannot access class 'String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:97:23 Cannot access 'java.lang.Object' which is a supertype of 'ai.mlc.mlcllm.JSONFFIEngine'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:97:38 Type mismatch: inferred type is kotlin.String but String! was expected
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:112:77 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.Boolean'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:128:18 Type mismatch: inferred type is kotlin.Exception /* = java.lang.Exception */ but Throwable was expected
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:129:56 Cannot access class 'java.lang.Exception'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:170:13 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.Boolean'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/MLCEngine.kt:171:19 Unresolved reference: IllegalArgumentException
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:17:13 Unresolved reference: util
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:66:26 Unresolved reference: UUID
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:71:5 Cannot access 'java.io.Serializable' which is a supertype of 'ai.mlc.mlcllm.OpenAIProtocol.ChatCompletionRole'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:73:9 Cannot access 'java.io.Serializable' which is a supertype of 'ai.mlc.mlcllm.OpenAIProtocol.ChatCompletionRole.system'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:74:9 Cannot access 'java.io.Serializable' which is a supertype of 'ai.mlc.mlcllm.OpenAIProtocol.ChatCompletionRole.user'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:75:9 Cannot access 'java.io.Serializable' which is a supertype of 'ai.mlc.mlcllm.OpenAIProtocol.ChatCompletionRole.assistant'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:76:9 Cannot access 'java.io.Serializable' which is a supertype of 'ai.mlc.mlcllm.OpenAIProtocol.ChatCompletionRole.tool'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:88:25 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:96:56 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:117:91 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:123:31 Unresolved reference: IllegalStateException
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:153:38 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.Float'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:154:28 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:156:37 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.Float'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:158:32 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies
e: file:///share/Repository/mlc-llm/android/MLCChat/dist/lib/mlc4j/src/main/java/ai/mlc/mlcllm/OpenAIProtocol.kt:160:28 Cannot access 'java.io.Serializable' which is a supertype of 'kotlin.String'. Check your module classpath for missing or conflicting dependencies

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':mlc4j:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 5s
32 actionable tasks: 15 executed, 17 up-to-date

JDK version: jdk-17.0.11

Please folllow the Android SDK docs https://llm.mlc.ai/docs/deploy/android.html
Likely this is related to JDK version and setup.  You will need to use the jdk that comes with NDK.


Intellisense support for bindings

Depends on #154 and #152. Also need to somehow obtain the type of DataContext. Possible solution is extracting one from loaded XAML. For DataTemplates it should be easy to extract the type from DataType property.

Migrated to https://github.com/Perspex/PerspexVS/issues/18

Use d:DataContext

The problem with the data context is that it's only viable for the root element and it's hard to actually determine the resulting type without actually evaluating the XAML. Another problem is that we could  do that reliably only for the root element which should be possible when previewer is running.
BTW, d:DataContext is currently not supported due to the lack of XAML compatibility support in Portable.Xaml. The support for that was merged in February, but we need to actually update our fork of OmniXAML first. The issue is tracked here.


Traefik doesn't work when you create services using docker api

Do you want to request a feature or report a bug?
Bug

What did you do?
I am running traefik on top of docker swarm, some services are created using compose and cli others using the docker api (dockerpy).

What did you expect to see?
To see all the services inside the dashboard.
What did you see instead?
Only the ones created using compose and the cli.
Output of traefik version: (What version of Traefik are you using?)

traefik:1.5.0-rc2-alpine

What is your environment & configuration (arguments, toml, provider, platform, ...)?
Docker version:
Client:
 Version:      17.09.1-ce
 API version:  1.32
 Go version:   go1.8.3
 Git commit:   19e2cf6
 Built:        Thu Dec  7 22:22:25 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.09.1-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   19e2cf6
 Built:        Thu Dec  7 22:28:28 2017
 OS/Arch:      linux/amd64
 Experimental: true

debug = true
logLevel = "INFO"

defaultEntryPoints = ["http"]
[entryPoints]
    [entryPoints.http]
    address = ":80"
    compress = true

[api]

dashboard = true

[docker]

endpoint = "unix:///var/run/docker.sock"
watch = true
exposedbydefault = false
swarmmode = true

If applicable, please paste the log output in debug mode (--debug switch)
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:05Z" level=debug msg="Configuration received from provider docker: {"backends":{"backend-whoami0":{"servers":{"server-whoami0-1":{"url":"http://<IP_ADDRESS>:80","weight":0}},"loadBalancer":{"method":"wrr"}}},"frontends":{"frontend-Host-gigi-docker-localhost-0":{"entryPoints":["http"],"backend":"backend-whoami0","routes":{"route-frontend-Host-gigi-docker-localhost-0":{"rule":"Host:gigi.docker.localhost"}},"passHostHeader":true,"priority":0,"basicAuth":[],"headers":{}}}}"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:05Z" level=info msg="Skipping same configuration for provider docker"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Filtering disabled container gatekeeper_consul.1"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Filtering disabled container gatekeeper_traefik.1"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Could not load traefik.frontend.whitelistSourceRange labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Could not load traefik.frontend.entryPoints labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Could not load traefik.frontend.auth.basic labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Validation of load balancer method for backend backend-whoami0 failed: invalid load-balancing method ''. Using default method wrr."
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=debug msg="Configuration received from provider docker: {"backends":{"backend-whoami0":{"servers":{"server-whoami0-1":{"url":"http://<IP_ADDRESS>:80","weight":0}},"loadBalancer":{"method":"wrr"}}},"frontends":{"frontend-Host-gigi-docker-localhost-0":{"entryPoints":["http"],"backend":"backend-whoami0","routes":{"route-frontend-Host-gigi-docker-localhost-0":{"rule":"Host:gigi.docker.localhost"}},"passHostHeader":true,"priority":0,"basicAuth":[],"headers":{}}}}"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:20Z" level=info msg="Skipping same configuration for provider docker"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Filtering disabled container gatekeeper_consul.1"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Filtering disabled container gatekeeper_traefik.1"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Could not load traefik.frontend.whitelistSourceRange labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Could not load traefik.frontend.entryPoints labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Could not load traefik.frontend.auth.basic labels"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Validation of load balancer method for backend backend-whoami0 failed: invalid load-balancing method ''. Using default method wrr."
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=debug msg="Configuration received from provider docker: {"backends":{"backend-whoami0":{"servers":{"server-whoami0-1":{"url":"http://<IP_ADDRESS>:80","weight":0}},"loadBalancer":{"method":"wrr"}}},"frontends":{"frontend-Host-gigi-docker-localhost-0":{"entryPoints":["http"],"backend":"backend-whoami0","routes":{"route-frontend-Host-gigi-docker-localhost-0":{"rule":"Host:gigi.docker.localhost"}},"passHostHeader":true,"priority":0,"basicAuth":[],"headers":{}}}}"
gatekeeper_traefik.1.oknygyzd99ro@moby    | time="2017-12-18T00:48:35Z" level=info msg="Skipping same configuration for provider docker"

To test this, with traefik running as service connected on cassiny-public.
using dockerpy
service_labels = {
    "traefik.port": "80",
    "traefik.enable": "true",
    "traefik.frontend.rule": "Host:pinco.docker.localhost",
    "traefik.docker.network": "cassiny-public",
}

client.services.create("emilevauge/whoami", name="whoami1",
                       networks=["cassiny-public"], labels=service_labels)

docker cli
docker service create \
--name whoami0 \
--label traefik.port=80 \
--label traefik.enable=true \
--label traefik.frontend.rule="Host:gigi.docker.localhost" \
--label traefik.docker.network="cassiny-public" \
--network=cassiny-public \
emilevauge/whoami

The issue seems related to Traefik's version.
With traefik:v1.4.5 it works properly (just removed traefik and created again with the old version):

Hi @barrachri, thanks for your interest on Træfik.
After some investigations, this difference between 1.4 and 1.5 is due to this change
When you create a service with docker cli you can see that there is an EndpointSpec defined
docker service inspect whoami0 --format "{{json .Endpoint}}" | jq
{
  "Spec": {
    "Mode": "vip"
  },
  "VirtualIPs": [
    {
      "NetworkID": "md4yvaj1gerxyp5qd2k97324v",
      "Addr": "<IP_ADDRESS>/24"
    }
  ]
}

And when you create with docker-py you can see that there is no EndpointSpec defined
docker service inspect whoami1 --format "{{json .Endpoint}}" | jq
{
  "Spec": {},
  "VirtualIPs": [
    {
      "NetworkID": "md4yvaj1gerxyp5qd2k97324v",
      "Addr": "<IP_ADDRESS>/24"
    }
  ]
}

To fix your issue you can specify the EndpointSpec
client.services.create("emilevauge/whoami", name="whoami1", networks=["cassiny-public"], labels=service_labels, endpoint_spec=docker.types.EndpointSpec(mode="vip"))

In docker cli there is a default value https://github.com/moby/moby/pull/30180 but not in docker-py https://github.com/docker/docker-py/pull/1468
@containous/docker WDYT about the EndpointSpec not setted ?

Thanks @mmatur!

I run into a very similar issue using docker stack.
When I create service using docker service create ... it's fine but when I create service from docker stack deploy ... container is filtered.
mydomain@root:~/docker$ docker service create \
> --name whoami0 \
> --label traefik.port=80 \
> --label traefik.enable=true \
> --label traefik.frontend.rule="Host:test.dev.mydomain.io" \
> --label traefik.docker.network="webgateway" \
> --network=webgateway \
> emilevauge/whoami

mydomain@root:~/docker$ cat whoami.yml
version: '3.4'

services:
  whoami:
    image: emilevauge/whoami
    networks:
      - webgateway
    deploy:
      mode: replicated
      replicas: 2
      placement:
        constraints:
          - node.role == worker
    labels:
      traefik.enable: "true"
      traefik.port: "80"
      traefik.docker.network: "webgateway"
      traefik.frontend.rule: "Host:whoami.dev.mydomain.io"

networks:
  webgateway:
    external: true

mydomain@root:~/docker$docker stack deploy -c whoami.yml whoami

Traefik log
time="2018-02-08T18:26:23Z" level=debug msg="Provider connection established with docker 17.12.0-ce (API 1.35)"
time="2018-02-08T18:26:23Z" level=debug msg="Filtering disabled container traefik_socat.1"
time="2018-02-08T18:26:23Z" level=debug msg="Filtering disabled container whoami_whoami.2"
time="2018-02-08T18:26:23Z" level=debug msg="Filtering disabled container whoami_whoami.1"
time="2018-02-08T18:26:23Z" level=debug msg="Filtering disabled container traefik_proxy.1"
time="2018-02-08T18:26:23Z" level=debug msg="Could not load traefik.frontend.whitelistSourceRange labels"
time="2018-02-08T18:26:23Z" level=debug msg="Could not load traefik.frontend.entryPoints labels"
time="2018-02-08T18:26:23Z" level=debug msg="Could not load traefik.frontend.auth.basic labels"
time="2018-02-08T18:26:23Z" level=debug msg="Validation of load balancer method for backend backend-whoami0 failed: invalid load-balancing method ''. Using default method wrr."
time="2018-02-08T18:26:23Z" level=debug msg="Configuration received from provider docker: {"backends":{"backend-whoami0":{"servers":{"server-whoami0-1":{"url":"http://<IP_ADDRESS>:80","weight":0}},"loadBalancer":{"method":"wrr"}}},"frontends":{"frontend-Host-test-dev-mydomain-io-0":{"entryPoints":["https","http"],"backend":"backend-whoami0","routes":{"route-frontend-Host-test-dev-mydomain-io-0":{"rule":"Host:test.dev.mydomain.io"}},"passHostHeader":true,"priority":0,"basicAuth":[]}}}"
time="2018-02-08T18:26:23Z" level=debug msg="Creating frontend frontend-Host-test-dev-mydomain-io-0"
time="2018-02-08T18:26:23Z" level=debug msg="Wiring frontend frontend-Host-test-dev-mydomain-io-0 to entryPoint https"
time="2018-02-08T18:26:23Z" level=debug msg="Creating route route-frontend-Host-test-dev-mydomain-io-0 Host:test.dev.mydomain.io"
time="2018-02-08T18:26:23Z" level=debug msg="Creating backend backend-whoami0"
time="2018-02-08T18:26:23Z" level=debug msg="Creating load-balancer wrr"
time="2018-02-08T18:26:23Z" level=debug msg="Creating server server-whoami0-1 at http://<IP_ADDRESS>:80 with weight 0"
time="2018-02-08T18:26:23Z" level=debug msg="Wiring frontend frontend-Host-test-dev-mydomain-io-0 to entryPoint http"
time="2018-02-08T18:26:23Z" level=debug msg="Creating route route-frontend-Host-test-dev-mydomain-io-0 Host:test.dev.mydomain.io"
time="2018-02-08T18:26:23Z" level=debug msg="Creating entryPoint redirect http -> https : ^(?:https?:\/\/)?([\w\._-]+)(?::\d+)?(.*)$ -> https://$1:443$2"
time="2018-02-08T18:26:23Z" level=debug msg="Creating backend backend-whoami0"
time="2018-02-08T18:26:23Z" level=debug msg="Creating load-balancer wrr"
time="2018-02-08T18:26:23Z" level=debug msg="Creating server server-whoami0-1 at http://<IP_ADDRESS>:80 with weight 0"
time="2018-02-08T18:26:23Z" level=info msg="Server configuration reloaded on :80"
time="2018-02-08T18:26:23Z" level=info msg="Server configuration reloaded on :443"
time="2018-02-08T18:26:23Z" level=info msg="Server configuration reloaded on :8080"
time="2018-02-08T18:26:23Z" level=debug msg="LoadCertificateForDomains [test.dev.mydomain.io]..."
time="2018-02-08T18:26:23Z" level=debug msg="Looking for provided certificate to validate [test.dev.mydomain.io]..."
time="2018-02-08T18:26:23Z" level=debug msg="No provided certificate found for domains [test.dev.mydomain.io], get ACME certificate."
time="2018-02-08T18:26:23Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:25Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:27Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:29Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:31Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:33Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:35Z" level=debug msg="Basic auth success..."
time="2018-02-08T18:26:37Z" level=debug msg="Basic auth success..."

Hi @cypx,
I think it is because your labels are not set under deploy but under service
You should try with
version: '3.4'

services:
  whoami:
    image: emilevauge/whoami
    networks:
      - webgateway
    deploy:
      mode: replicated
      replicas: 2
      placement:
        constraints:
          - node.role == worker
      labels:
        traefik.enable: "true"
        traefik.port: "80"
        traefik.docker.network: "webgateway"
        traefik.frontend.rule: "Host:whoami.dev.mydomain.io"

networks:
  webgateway:
    external: true

Documentation is available here

Hi @mmatur
You are right, i just get it after my coffee this morning ^.^
Thanks for your help!

Same issue here with traefik:latest. Is it really still not fixed?


(Dropdown list) Programming languages with alphabet "K"

Many projects need to show a list of programming languages as a dropdown list in their application. Hence the idea. Can someone help me finish the alphabet K in A-Z-dropdown.html?
Here is the list from which I have referred to the list of programming languages
https://en.wikipedia.org/wiki/List_of_programming_languages

Hi I can work on this!

Sure @si-ddhant

Closed with PR #116


feat: Initial Commit for Terraform Application Insights AVM Resource

Description

Initial development for Application Insights AVM Module

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] I did run all  pre-commit checks

This linting failed on the pre-check but I can't figure out what it is complaining about.


Remainder of Manual RPC tracker

From the looks of it e8c2f56 may have been previously backported

From the looks of it e8c2f56 may have been previously backported

yes, I mean it doesn't make sense to have this commit, should be dropped imo.
basically this PR could be turned into backport #18499: rpc: Make rpc documentation not depend on call-time rpc args (with an addition of bf354d6dbb to be complete)


'Resend code' API returns status code as 201 even at failure case.

Describe the issue:
Even if the resend code API failed to send the code in an attempt it returns 201 as the HTTP status code. Expected it will indicate a failure.
How to reproduce:
Call the resend API for an unsupported scenario.
Expected behavior:
Provide an indication of the error status in the HTTP status code.
Code - https://github.com/wso2-extensions/identity-governance/blob/master/components/org.wso2.carbon.identity.user.endpoint/src/main/java/org/wso2/carbon/identity/user/endpoint/impl/ResendCodeApiServiceImpl.java#L66-L67

Fixed with https://github.com/wso2-extensions/identity-governance/pull/431
Need to improve to identify and address the 400 bad request case separately.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Linearized Pair-Density Functional Theory

Implementation of Linearized Pair-Density Functional Theory (as described here https://doi.org/10.26434/chemrxiv-2023-7d0gv).
This is a new multi-state PDFT method which takes a different approach/philosophy for computing off-diagonal coupling elements. As such, the code is placed in its own lpdft.py file. In general, it uses the mcpdft.multi_state() function but uses the method="lin" argument (whereas CMS-PDFT uses method="cms").
Hybrid L-PDFT is performed using hybrid_kernel until the hybrid veff_1, veff_2 is sorted out.
Tests for lih with 2 and 4 states is provided as well.
A simple example is given and an update to the mcpdft doc is also added.

Updated L-PDFT so that hybrid functionals (like tPBE0) can be used directly with the kernel function and deleted the hybrid_kernel function. Added a kwarg to make it clear in get_pdft_veff that the derivatives do not have the mcwfn component and is purely the functional term (this was a discussion with Matt Hermes)


Fix a few (more) oopsies in the CI

Use TSan (matching the workflow for pushes to main) with the unit tests, actually invoke brew correctly for the macOS tests.

Test failures are expected until vapor/fluent-postgres-driver#186 is merged.

Codecov Report

Merging #200 (8f39b3d) into fix-decimal (aba2e3a) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           fix-decimal     #200   +/-   ##
============================================
  Coverage        41.84%   41.84%
============================================
  Files              116      116
  Lines             7779     7779
============================================
  Hits              3255     3255
  Misses            4524     4524

Flag
Coverage Δ

unittests
41.84% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 aba2e3a...8f39b3d. Read the comment docs.

Whoops. Somehow this PR got targeted to the fix-decimal branch rather than main.

Resolved by cherry-picking the squashed merge to main and force-pushing a revert of fix-decimal.


Langflow run | Migration Issue

Describe the bug
SAWarning: WARNING: SQL-parsed foreign key constraint '('user_id', 'user', 'id')' could not be located in PRAGMA foreign_keys for table flow
context.run_migrations()
[05/23/24 09:56:47] ERROR    2024-05-23 09:56:47 - ERROR    - service - AutogenerateDiffsDetected: {exc}                                                                                service.py:162
ERROR    2024-05-23 09:56:47 - ERROR    - utils - Something went wrong running migrations. Please, run langflow migration --fix utils.py:51
ERROR    2024-05-23 09:56:47 - ERROR    - utils - Something went wrong running migrations. Please, run langflow migration --fix
Browser and Version
Chrome
To Reproduce
Steps to reproduce the behavior:
pip install langflow
langflow run
Screenshots

Additional context
Python: Python 3.11.9
Langflow: langflow 0.6.19

python -m langflow migration --fix worked for me on Mac

Hey all.
This is in version 0.6.19, correct?
You can try running python -m langflow migration --test to see if you can get some info on what is not working.


Improve compile-time error messages from log-derive

Misspelling a meta-item name (or other errors) cause error messages that highlight the entire attribute and don't clearly spell out what's wrong.

My fix for this in the past has been twofold:

Have a Result type for parsing options, and a Vec for collecting all errors encountered during parsing. The error type should be remembering the span where the error was encountered.
Before building the Attributes struct, check if the list of errors is empty. If so, emit each error. syn::Error works well for this.

Note that I found this tedious enough that I created a library to help with the bookkeeping, called darling. The darling::Error type has the functionality you'd need for this, though you could also directly wrap syn's error if you want to keep the dependency list small.

Ha. You're saying I should use syn::Error instead of panicking?
I was just talking with @dtolnay about compile errors in proc-macros (actually about code errors not erros in the macro, and he pointed me to this: https://github.com/rust-lang/rust/issues/43081 )
I'll look into this.
Thanks for the thorough review and issues :)


fix: prefer exports when resolving

Description
Closes https://github.com/vitejs/vite/issues/10352
Additional context
Svelte has a package.json in each directory to support older versions of Node since exports is only present in Node 12 and newer. Vite is preferring these nested package.json files over the exports field which is incorrect
The code was also assuming all modules are required, which is wrong since it uses a dynamic import for everything

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

I created a test project since I was having a hard time interpreting the spec. What I found is that it will only use exports from the package.json in the package root, but it will use the package.json in subdirectories to determine whether to interpret the file as ESM or CJS, which sounds like what you said.

It seems dangerous to infer Node's intended behavior from its implementation instead of its specification, as the observed behavior could be unintended and fixed in Node later on without us the wiser.

Svelte has a package.json in each directory to support older versions of Node since exports is only present in Node 12 and newer. Vite is preferring these nested package.json files over the exports field which is incorrect

What issue does this cause? Can't you just keep the main/module fields in each nested package.json aligned with the exports field from the top-level package.json?

@benmccann Does Node.js only check the "root package" for an exports field, or does it search in each parent directory of the import ID and stop at the first exports field it finds?

It seems dangerous to infer Node's intended behavior from its implementation instead of its specification, as the observed behavior could be unintended and fixed in Node later on without us the wiser.

I don't think Node could change its behavior and randomly break working packages.

What issue does this cause?

Vite was resolving to the wrong file

Can't you just keep the main/module fields in each nested package.json aligned with the exports field from the top-level package.json?

They are

Does Node.js only check the "root package" for an exports field, or does it search in each parent directory of the import ID and stop at the first exports field it finds?

If I recall correctly, I believe it only checks the root package

What issue does this cause?

Vite was resolving to the wrong file

Can't you just keep the main/module fields in each nested package.json aligned with the exports field from the top-level package.json?

They are

These two answers seem to conflict, or am I missing something? How was Vite resolving to the wrong file if both the root and nested package.json point to the same file?

I can't recall anymore. I'd have to go back to an old version of Vite and run it against Svelte again. That being said, I'm not sure the answer would change much. This is part of the Node resolution algorithm and is something we should probably support regardless.

I went back and looked at the original bug report and it refreshed my memory.
The root package.json looks like:
    "./internal": {
      "types": "./types/runtime/internal/index.d.ts",
      "import": "./internal/index.mjs",
      "require": "./internal/index.js"
    },

And then the sub-directory or sub-package or whatever you want to call it looks like:
{
  "main": "./index",
  "module": "./index.mjs",
  "types": "./index.d.ts"
}

I believe the issue here is that the module field is only used when the package is in ssr.noExternal. I'm thinking now that we probably could add an exports map to the Svelte sub-package as a workaround. But that's really just a workaround and it's better to fix Vite.

Yup, to add on Ben's explanation, Node.js treats exports differently, that if the exports is define in the root package.json, it should respect that instead of any subdirectories' package.json. Previously Vite was checking closest package.json regardless which deviates from Node.js resolution algorithm. https://nodejs.org/api/esm.html#resolver-algorithm-specification (PACKAGE_RESOLVE no11 > no5, where packageSpecifier doesn't include the import subpath)


Fixes space key

In #36 I made a mistake and put empty string "" for space rather than correct string with space in it " ".

Done. Release in 0.8.2.


Deploy with tutum (docker)

I made this new pull with an automated build of parse-server-example as you can see it here. Indeed it's better than a manual build ...
Dockerfile is better with explicit environment variables
Readme has now a Tutum deployment button linked with his tutum.yml
Package.json express and parse dependencies are unnecessary there are in already in "parse-server": "~2.0"

Can you rebase and squash this?

I made this to get it running instantly https://github.com/didierfranc/parse-docker

How do you keep it up to date?

It's based on the latest npm version of parse-server and parse-dashboard and the docker image is build on every Github pull.

That's good then :) I guess we can close this.


Add html css and js files

Apply best practices in HTML code.
Use semantic HTML tags.
Use CSS selectors correctly.
Use CSS box model.

INVALID ❌ ❌ ❌
Hi @AbdelazizSoliman,
While you have made a great effort in this project, I cannot proceed to review your code.
Invalid Code Review Request ❌

This project required you to play the role of a code reviewer and perform a code review in a past project you did. Unfortunately, you did not perform any code review and I have to invalidate your project for this reason. Please follow the project instructions and conduct a code review of your project.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
✅ Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.
⚠ Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise
Invalid Code Review Request does not count into the code reviews limit.


[SPARK-42435][UI] Update DataTables to 1.13.2

What changes were proposed in this pull request?
Update javascript library DataTables, used in the UI, to 1.13.2.
Why are the changes needed?
The 1.10.25 version of DataTables, that Spark currently uses, seems vulerable: https://security.snyk.io/package/npm/datatables.net/1.10.25. The vulnerability may not affect Spark but it is safer to update.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual test.

cc @srowen, @dongjoon-hyun, @gengliangwang, @wangyum

cc @gengliangwang FYI

I did a quick test and the UI looks ok. Also I tried git grep and all the old version 1.10.25 is gone.
@peter-toth Thanks for the work. Merging to master.

LGTM if the UI works

I played a bit with the UI while making this PR and it looked ok to me.
Actually, I'm not sure that anything from our customizations in core/src/main/resources/org/apache/spark/ui/static/webui-dataTables.css is still needed after this version update, but I removed only the u/dpwn arrows related part that caused issues...
E.g. the executor "show ... entries" box (https://github.com/apache/spark/pull/36226#issuecomment-1100810575) looked ok without this last fix: https://github.com/apache/spark/pull/36226/files#diff-e96c8dc10974b7da0c5dd4f675702462124b66c4bf2f7a0682f2ec1482a2eee3


How about keeping just the core (max,+) algebraic part in the package and moving the systems-related part into a separate package?

I was just wondering: How about keeping just the core (max,+) algebraic part in the package and moving the discrete-event systems-related part into a separate package?
In contrast to some languages like Matlab, here in Julia we pay no price for having the functionality split into several (and possibly even a larger number of) smaller packages. The package manager in Julia can manage the dependencies easily and – and that is crucial – transparently for the user.
In case you find the idea reasonable, how about name such system-related package as something like MaxPlusLinearSystems.jl?
But it is not urgent at all. It is just that now as you are refreshing and updating the package, it is perhaps an opportunity for such move. And, in fact, it can make further maintaining and developing easier. Just my 2 cents.

@hurak Do you mean to move syslin.jl and flowshop.jl apart and create their own repo ? Why not ! But the Scilab toolbox did not offer more than "composing" systems (parallel, serie ... explicit and implicit). In my sense would be more logical that a new repo MaxPlusLinearSystems.jl solves/offers more things than what this current toolbox offers.

Yes, that is what I meant. I view this max-plus algebra simply as "another algebra", similar to linear algebra, that is, computation with matrices and vectors, for which we have LinearAlgebra in Julia. I do not expect anything more from it. Then we have some other package that have LinearAlgebra as their dependency. For example, ControlSystems,jl package that defines a state-space model of a system and some basic manipulation and computation.
The fact that initially the package MaxPlusLinearSystems.jl will not contain much is not a problem, is i? Smaller packages are fine too. But the mission of the two packages will be quite clear. And perhaps some more goodies will come later. I can think of adding some optimization-based control design (in the spirit of Bart De Schutter's papers). And on the other hand, guys who are not interested in the system-theoretic applications will have a clean package just for max-plus algebra where they can get oriented quickly and start using or even contributing.


Rust binding example missing

Hi there, looks like the example in the Rust binding section is 404ing. Do you have a link to the source? I’m betting Noria for an R&D project and would like to use it as a reference.
Also does Noria have a license term declared yet? If so I’d recommend putting it at the bottom of the README :-)
Thanks!

Fixed, thanks!


Plugin bug: @FieldNameConstants for array type fields not working

Short description
Lombok config:
lombok.fieldNameConstants.uppercase = true

Lombok pojo:
@FieldNameConstants
class TestClassWithDifferentDataTypes {

    private Date dateField;
    private List<?> collectionField;
    private List<Date> dateCollectionField;
    private Date[] dateArrayField; // <- problem with this field

}

Usage in other class - the screenshot:

The line 26 has red source code, but there is no compilation issue (if you compile class via maven). Most probably it is caused by the array type of the field.
Expected behavior
Is there a specific expected behavior?
The field is recognized in IDEA editor.
Version information
Lombok: 1.18.12
IDEA: 2020.2
Plugin: 0.30-EAP

IDEA Version: Please provide full IntelliJ IDEA Version - available from About view
JDK Version: What is your JDK version, including update level?
OS Type & Version: Are you on Mac/Windows/Linux? Provide as much information as possible about versions
Lombok Plugin Version: What is the version of the plugin installed?`
Lombok Dependency Version: What version of lombok.jar are you using?

Steps to reproduce
What steps do we need to take to reproduce this issue?

Create a pojo with array type field and @FieldNameConstants
???
PROFIT

Sample project
it's too trivial
Please provide a sample project that exhibits the problem.
You should also include .idea folder so we can inspect the settings.

[ ] Sample project provided
[ ] I am able to reproduce this error on the sample project by following the steps described above

Additional information
Is there any additional information you can provide to help us understanding and solving the issue?
Stacktrace
If you are experiencing an issue and IntelliJ throws an error please provide the stacktrace.

STACKTRACE HERE (inside code markup)

Thanks @mplushnikov. I can confirm that now I cannot reproduce it either.


RenderFlex overflowed when adding a longer text to any of the toasts type but normal

When adding a longer text to the toast for any type with an icon (any type but normal) the widget gets a RenderFlex overflowed error and the text overflows on the right side of the toast.
To replicate simply add a text longer than 50 characters in length to any toast of type info, error, warning or success.
Here are some screenshots that may show this with better detail:

Here it is how this same text looks on the normal toast:

I am working on a solution already and may send a pull request once solved but I wanted to open issue just in case to keep track of it.

Thanks @toniremi


Running tests with coverage broken in dev channel

Steps to Reproduce

Run tests with coverage flutter -v test --coverage --concurrency=2

Logs

[  +24 ms] executing: [/home/cirrus/sdks/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +35 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/dev
[        ] executing: [/home/cirrus/sdks/flutter/] git rev-parse --abbrev-ref HEAD
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] dev
[        ] executing: [/home/cirrus/sdks/flutter/] git ls-remote --get-url origin
[   +6 ms] Exit code 0 from: git ls-remote --get-url origin
[        ]<EMAIL_ADDRESS>[        ] executing: [/home/cirrus/sdks/flutter/] git log -n 1 --pretty=format:%H
[   +5 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 13684e4f8e9edb4c2b2a0fd8e1439f93e6e30fde
[        ] executing: [/home/cirrus/sdks/flutter/] git log -n 1 --pretty=format:%ar
[   +5 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 3 days ago
[        ] executing: [/home/cirrus/sdks/flutter/] git describe --match v*.*.* --first-parent --long --tags
[   +6 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v0.9.6-0-g13684e4f8
[ +145 ms] Found plugin device_info at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/device_info-0.2.1/
[   +3 ms] Found plugin firebase_analytics at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_analytics-1.0.3/
[   +1 ms] Found plugin firebase_dynamic_links at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.1.0/
[   +2 ms] Found plugin firebase_messaging at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-2.0.0/
[  +31 ms] Found plugin image_picker at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/image_picker-0.4.10/
[   +1 ms] Found plugin intercom_flutter at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/intercom_flutter-1.0.7/
[  +11 ms] Found plugin package_info at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/package_info-0.3.2/
[  +11 ms] Found plugin shared_preferences at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.4.3/
[  +10 ms] Found plugin url_launcher at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/url_launcher-3.0.3/
[  +29 ms] Found plugin device_info at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/device_info-0.2.1/
[        ] Found plugin firebase_analytics at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_analytics-1.0.3/
[        ] Found plugin firebase_dynamic_links at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.1.0/
[        ] Found plugin firebase_messaging at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-2.0.0/
[   +6 ms] Found plugin image_picker at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/image_picker-0.4.10/
[        ] Found plugin intercom_flutter at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/intercom_flutter-1.0.7/
[   +5 ms] Found plugin package_info at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/package_info-0.3.2/
[   +6 ms] Found plugin shared_preferences at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/shared_preferences-0.4.3/
[   +5 ms] Found plugin url_launcher at /home/cirrus/.pub-cache/hosted/pub.dartlang.org/url_launcher-3.0.3/
[  +34 ms] switching to directory LocalDirectory: 'test' to run tests
[        ] running test package with arguments: [--no-color, -r, compact, --concurrency=2, --, /home/cirrus/project/test/src/app_test.dart, /home/cirrus/project/test/src/route/dynamic_link_bloc_test.dart, /home/cirrus/project/test/src/route/navigation_test.dart, /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart, /home/cirrus/project/test/src/configuration_test.dart, /home/cirrus/project/test/src/api/api_client_test.dart, /home/cirrus/project/test/src/address/address_api_test.dart, /home/cirrus/project/test/src/address/address_test.dart, /home/cirrus/project/test/src/address/address_bloc_test.dart, /home/cirrus/project/test/src/address/address_validator_test.dart, /home/cirrus/project/test/src/alert/alert_bloc_test.dart, /home/cirrus/project/test/src/alert/alert_message_dialog_test.dart, /home/cirrus/project/test/src/alert/alert_dialog_provider_test.dart, /home/cirrus/project/test/src/tracker/tracker_test.dart, /home/cirrus/project/test/src/nps/nps_bloc_test.dart, /home/cirrus/project/test/src/nps/nps_api_test.dart, /home/cirrus/project/test/src/profile/profile_bloc_test.dart, /home/cirrus/project/test/src/profile/profile_api_test.dart, /home/cirrus/project/test/src/profile/profile_validator_test.dart, /home/cirrus/project/test/src/error/error_reporter_test.dart, /home/cirrus/project/test/src/verification/verification_files_api_test.dart, /home/cirrus/project/test/src/verification/verification_bloc_test.dart, /home/cirrus/project/test/src/verification/verification_api_test.dart, /home/cirrus/project/test/src/user/login/login_api_test.dart, /home/cirrus/project/test/src/user/login/reset_password_validator_test.dart, /home/cirrus/project/test/src/user/login/reset_password_bloc_test.dart, /home/cirrus/project/test/src/user/login/login_bloc_test.dart, /home/cirrus/project/test/src/user/mfa/multi_factor_api_test.dart, /home/cirrus/project/test/src/user/mfa/multi_factor_bloc_test.dart, /home/cirrus/project/test/src/user/privacy/privacy_settings_api_test.dart, /home/cirrus/project/test/src/user/privacy/privacy_settings_bloc_test.dart, /home/cirrus/project/test/src/user/signup/signup_bloc_test.dart, /home/cirrus/project/test/src/user/user_api_test.dart, /home/cirrus/project/test/src/user/user_test.dart, /home/cirrus/project/test/src/ui/text/copy_to_clipboard_test.dart, /home/cirrus/project/test/src/ui/input/text_field_test.dart, /home/cirrus/project/test/src/ui/input/country_field_test.dart, /home/cirrus/project/test/src/ui/input/checkbox_field_test.dart, /home/cirrus/project/test/src/ui/currency_icon_test.dart, /home/cirrus/project/test/src/ui/subhead_test.dart, /home/cirrus/project/test/src/ui/progress/progress_bar_test.dart, /home/cirrus/project/test/src/ui/paper_test.dart, /home/cirrus/project/test/src/ui/heading_test.dart, /home/cirrus/project/test/src/ui/currency_detail_test.dart, /home/cirrus/project/test/src/screen/main/bottom_navigation_test.dart, /home/cirrus/project/test/src/screen/main/screen/settings/mfa_confirm_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/settings/settings_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/settings/mfa_setup_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/market/market_info_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/pin/card_enter_security_code_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/pin/card_view_pin_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/card_dashboard_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/card_tab_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/order/order_card_shipping_address_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/order/order_card_delivery_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/order/order_card_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/order/order_card_activation_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/card/card_fees_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/overview/overview_screen_test.dart, /home/cirrus/project/test/src/screen/main/screen/overview/start_token_swap_element_test.dart, /home/cirrus/project/test/src/screen/main/screen/overview/make_first_investment_test.dart, /home/cirrus/project/test/src/screen/auth/signup_screen_test.dart, /home/cirrus/project/test/src/screen/auth/reset_password_screen_test.dart, /home/cirrus/project/test/src/screen/auth/otp_screen_test.dart, /home/cirrus/project/test/src/screen/auth/login_screen_test.dart, /home/cirrus/project/test/src/screen/survey/survey_screen_test.dart, /home/cirrus/project/test/src/screen/nps/nps_screen_test.dart, /home/cirrus/project/test/src/screen/privacy/privacy_settings_screen_test.dart, /home/cirrus/project/test/src/screen/verification/widget/verification_file_upload_test.dart, /home/cirrus/project/test/src/screen/verification/loader/file_upload_loader_test.dart, /home/cirrus/project/test/src/screen/verification/screen/address_verification_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/profile_form_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/getting_started_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/selfie_verification_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/verification_screens_render_test.dart, /home/cirrus/project/test/src/screen/verification/screen/choose_document_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/address_verification_by_letter_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/resident-verification/resident_verification_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/resident-verification/securities_resident_verification_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/resident-verification/default_resident_verification_screen_test.dart, /home/cirrus/project/test/src/screen/verification/screen/address_form_screen_test.dart, /home/cirrus/project/test/src/screen/securities/token_swap_intro_screen_test.dart, /home/cirrus/project/test/src/screen/securities/securities_onboarding_final_screen_test.dart, /home/cirrus/project/test/src/screen/securities/token_transfer_screen_test.dart, /home/cirrus/project/test/src/screen/order/add_funds_screen_test.dart, /home/cirrus/project/test/src/screen/order/source_of_funds_screen_test.dart, /home/cirrus/project/test/src/screen/wallet/wallet_balance_screen_test.dart, /home/cirrus/project/test/src/screen/wallet/wallet_send_screen_test.dart, /home/cirrus/project/test/src/screen/wallet/wallet_payment_method_screen_test.dart, /home/cirrus/project/test/src/screen/conversion/conversion_screen_test.dart, /home/cirrus/project/test/src/screen/conversion/conversion_confirmation_screen_test.dart, /home/cirrus/project/test/src/streaming/streaming_bloc_test.dart, /home/cirrus/project/test/src/device/device_info_retriever_test.dart, /home/cirrus/project/test/src/device/device_test.dart, /home/cirrus/project/test/src/device/device_api_test.dart, /home/cirrus/project/test/src/introslider/dotsindicator/dots_indicator_test.dart, /home/cirrus/project/test/src/introslider/intro_slider_test.dart, /home/cirrus/project/test/src/order/order_bloc_test.dart, /home/cirrus/project/test/src/order/bank_account_details_screen_test.dart, /home/cirrus/project/test/src/wallet/wallet_validator_test.dart, /home/cirrus/project/test/src/wallet/wallet_bloc_test.dart, /home/cirrus/project/test/src/wallet/wallet_api_test.dart, /home/cirrus/project/test/src/wallet/wallet_test.dart, /home/cirrus/project/test/src/wallet/wallet_send_confirmation_screen_test.dart, /home/cirrus/project/test/src/wallet/sourceOfFunds/source_of_funds_bloc_test.dart, /home/cirrus/project/test/src/wallet/wallet_send_bloc_test.dart, /home/cirrus/project/test/src/card/card_bloc_test.dart, /home/cirrus/project/test/src/card/card_account_api_test.dart, /home/cirrus/project/test/src/card/card_api_test.dart, /home/cirrus/project/test/src/state/bloc_provider_test.dart, /home/cirrus/project/test/src/state/securities_bloc_test.dart, /home/cirrus/project/test/src/state/persistent_store_test.dart, /home/cirrus/project/test/src/state/authentication_bloc_test.dart, /home/cirrus/project/test/src/intercom/intercom_button_test.dart, /home/cirrus/project/test/src/intercom/intercom_bloc_test.dart]

00:00 +0: loading /home/cirrus/project/test/src/app_test.dart                                                                                [ +183 ms] test 0: starting test /home/cirrus/project/test/src/app_test.dart
[  +13 ms] test 0: starting shell process
[   +2 ms] Stopping scan for flutter_test_config.dart; found project root at /home/cirrus/project
[   +1 ms] Compiler will use the following file as its incremental dill file: /tmp/flutter_test_compiler.TUGZFV/output.dill
[        ] Listening to compiler controller...
[   +2 ms] Compiling /tmp/flutter_test_listener.JGYJQF/listener.dart
[   +3 ms] /home/cirrus/sdks/flutter/bin/cache/dart-sdk/bin/dart /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --strong --target=flutter --output-dill /tmp/flutter_test_compiler.TUGZFV/output.dill --packages /home/cirrus/project/.packages --initialize-from-dill /home/cirrus/project/build/testfile.dill --unsafe-package-serialization
[   +1 ms] test 1: starting test /home/cirrus/project/test/src/route/dynamic_link_bloc_test.dart
[        ] test 1: starting shell process
[        ] Stopping scan for flutter_test_config.dart; found project root at /home/cirrus/project
[        ] test 2: starting test /home/cirrus/project/test/src/route/navigation_test.dart
[        ] test 2: starting shell process
[        ] Stopping scan for flutter_test_config.dart; found project root at /home/cirrus/project
[        ] test 3: starting test /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart
[        ] test 3: starting shell process
[        ] Stopping scan for flutter_test_config.dart; found project root at /home/cirrus/project

00:05 +0: loading /home/cirrus/project/test/src/app_test.dart                                                                                [+5090 ms] Compiling /tmp/flutter_test_listener.JGYJQF/listener.dart took 5100ms
[        ] Compiling /tmp/flutter_test_listener.KZNEVP/listener.dart
[   +1 ms] Copying platform_strong.dill file from /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/platform_strong.dill
[   +5 ms] /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --flutter-assets-dir=/tmp/flutter_test_bundle.APJCHP --enable-checked-mode --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/cirrus/project/.packages /tmp/flutter_test_listener.JGYJQF/listener.dart.dill
[        ] Using this directory for fonts configuration: /tmp/flutter_test_fonts.SSIIQJ
[   +9 ms] test 0: awaiting initial result for pid 929
[  +52 ms] Shell: Observatory listening on http://<IP_ADDRESS>:41123/
[        ] test 0: using observatory uri http://<IP_ADDRESS>:41123/ from pid 929
[ +170 ms] test 0: process with pid 929 connected to test harness
[        ] test 0: awaiting test result for pid 929

00:05 +0: /home/cirrus/project/test/src/app_test.dart: App smoke test                                                                                [ +242 ms] Compiling /tmp/flutter_test_listener.KZNEVP/listener.dart took 484ms
[        ] Compiling /tmp/flutter_test_listener.KAFMXI/listener.dart
[        ] Copying platform_strong.dill file from /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/platform_strong.dill
[   +3 ms] /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --flutter-assets-dir=/tmp/flutter_test_bundle.RHCHEE --enable-checked-mode --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/cirrus/project/.packages /tmp/flutter_test_listener.KZNEVP/listener.dart.dill
[   +8 ms] test 1: awaiting initial result for pid 936
[  +51 ms] Shell: Observatory listening on http://<IP_ADDRESS>:37379/
[        ] test 1: using observatory uri http://<IP_ADDRESS>:37379/ from pid 936
[ +137 ms] Compiling /tmp/flutter_test_listener.KAFMXI/listener.dart took 202ms
[        ] Compiling /tmp/flutter_test_listener.YIIXLS/listener.dart
[        ] Copying platform_strong.dill file from /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/platform_strong.dill
[   +3 ms] /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --flutter-assets-dir=/tmp/flutter_test_bundle.WFQIET --enable-checked-mode --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/cirrus/project/.packages /tmp/flutter_test_listener.KAFMXI/listener.dart.dill
[   +9 ms] test 2: awaiting initial result for pid 942
[   +2 ms] test 1: process with pid 936 connected to test harness
[        ] test 1: awaiting test result for pid 936

00:05 +0: /home/cirrus/project/test/src/app_test.dart: App smoke test
Disposing StateContainer
Disposing Bloc provider of DynamicLinkBloc

00:05 +1: loading /home/cirrus/project/test/src/route/dynamic_link_bloc_test.dart                                                                                [  +52 ms] test 0: process with pid 929 no longer needed by test harness
[        ] test 0: collecting coverage
[        ] pid 929: collecting coverage data from http://<IP_ADDRESS>:41123/...
[  +15 ms] Shell: Observatory listening on http://<IP_ADDRESS>:37018/
[        ] test 2: using observatory uri http://<IP_ADDRESS>:37018/ from pid 942

00:05 +2: loading /home/cirrus/project/test/src/route/navigation_test.dart                                                                                [  +26 ms] test 1: process with pid 936 no longer needed by test harness
[        ] test 1: collecting coverage
[        ] pid 936: collecting coverage data from http://<IP_ADDRESS>:37379/...
[  +55 ms] Compiling /tmp/flutter_test_listener.YIIXLS/listener.dart took 167ms
[   +1 ms] Copying platform_strong.dill file from /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/platform_strong.dill
[   +3 ms] /home/cirrus/sdks/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --flutter-assets-dir=/tmp/flutter_test_bundle.IUIYXV --enable-checked-mode --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/cirrus/project/.packages /tmp/flutter_test_listener.YIIXLS/listener.dart.dill

00:06 +2: loading /home/cirrus/project/test/src/route/navigation_test.dart                                                                                [  +20 ms] test 3: awaiting initial result for pid 949
[  +67 ms] test 2: process with pid 942 connected to test harness
[        ] test 2: awaiting test result for pid 942
[        ] Shell: Observatory listening on http://<IP_ADDRESS>:37624/
[        ] test 3: using observatory uri http://<IP_ADDRESS>:37624/ from pid 949

00:06 +6: /home/cirrus/project/test/src/route/navigation_test.dart: navigates on app link
https://example.com/update-password
Navigating to reset password screen

00:06 +7: /home/cirrus/project/test/src/route/navigation_test.dart: tracks link if not handled
https://example.com/test

00:06 +8: loading /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart                                                                                [ +113 ms] test 2: process with pid 942 no longer needed by test harness
[        ] test 2: collecting coverage
[        ] pid 942: collecting coverage data from http://<IP_ADDRESS>:37018/...
[  +12 ms] test 3: process with pid 949 connected to test harness
[        ] test 3: awaiting test result for pid 949

00:06 +8: /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart: Dynamic Link Provider renders child
Setting up test method channel plugins.flutter.io/firebase_dynamic_links
Disposing Bloc provider of DynamicLinkBloc
Tearing down test method channel plugins.flutter.io/firebase_dynamic_links

00:06 +9: /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart: Dynamic Link Provider updates link
Setting up test method channel plugins.flutter.io/firebase_dynamic_links
Disposing Bloc provider of DynamicLinkBloc
Tearing down test method channel plugins.flutter.io/firebase_dynamic_links

00:06 +10: /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart: Dynamic Link Provider updates link                                                                                [ +226 ms] test 3: process with pid 949 no longer needed by test harness
[        ] test 3: collecting coverage
[        ] pid 949: collecting coverage data from http://<IP_ADDRESS>:37624/...

00:07 +10: /home/cirrus/project/test/src/route/dynamic_link_provider_test.dart: Dynamic Link Provider updates link                                                                                [ +638 ms] test 1: error caught during test; reporting to console
[        ] unhandled error during test:
           /home/cirrus/project/test/src/route/dynamic_link_bloc_test.dart
           Exception: Failed to collect coverage, process terminated prematurely with exit code -11.
           #0      CoverageCollector.collectCoverage.<anonymous closure> (package:flutter_tools/src/test/coverage_collector.dart:53:9)
           #1      StackZoneSpecification._registerUnaryCallback.<anonymous closure>.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:129:26)
           #2      StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:209:15)
           #3      StackZoneSpecification._registerUnaryCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:129:14)
           #4      _rootRunUnary (dart:async/zone.dart:1132:38)
           #5      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #6      _FutureListener.handleValue (dart:async/future_impl.dart:129:18)
           #7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:642:45)
           #8      Future._propagateToListeners (dart:async/future_impl.dart:671:32)
           #9      Future._completeWithValue (dart:async/future_impl.dart:486:5)
           #10     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:516:7)
           #11     StackZoneSpecification._run (package:stack_trace/src/stack_zone_specification.dart:209:15)
           #12     StackZoneSpecification._registerCallback.<anonymous closure> (package:stack_trace/src/stack_zone_specification.dart:119:48)
           #13     _rootRun (dart:async/zone.dart:1124:13)
           #14     _CustomZone.run (dart:async/zone.dart:1021:19)
           #15     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
           #16     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
           #17     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #18     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #19     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
           #20     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

[   +1 ms] test 1: cleaning up...
[        ] test 1: ensuring end-of-process for shell
[        ] test 1: deleting temporary bundle directory
[   +2 ms] test 1: deleting temporary directory
[   +9 ms] test 1: shutting down test harness socket server
[   +2 ms] test 1: finished with out-of-band failure

Running "flutter packages get" in project...                     4.0s
Analyzing project...
No issues found! (ran in 13.2s)

Downloading Dart SDK from Flutter engine f6af1f20ba92a819401d66ae4b2179b0775b0e12...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

100 70.5M  100 70.5M    0     0  77.8M      0 --:--:-- --:--:-- --:--:-- 77.7M
Building flutter tool...
The --packages-dir flag is no longer used and does nothing.
Resolving dependencies... (1.0s)(1.1s)(1.2s)(1.3s)(1.4s)(1.5s)(1.6s)(1.7s)(1.8s)(1.9s)(2.0s)(2.1s)(2.2s)(2.3s)(2.4s)(2.5s)(2.6s)(2.7s)(2.8s)(2.9s)(3.0s)(3.1s)(3.2s)(3.3s)(3.4s)(3.5s)(3.6s)(3.7s)(3.8s)(4.0s)
> analyzer 0.33.0-alpha.0 (was 0.31.2-alpha.2) (0.33.0 available)
> archive 2.0.4 (was 2.0.0)
> args 1.5.0 (was 1.4.3)
> async 2.0.8 (was 2.0.7)
> boolean_selector 1.0.4 (was 1.0.3)
> charcode 1.1.2 (was 1.1.1)
> cli_util 0.1.3+2 (was 0.1.3)
> collection 1.14.11 (was 1.14.6)
+ completion 0.2.1+1
> convert 2.0.2 (was 2.0.1)
> coverage 0.12.2 (was 0.11.0)
> crypto 2.0.6 (was 2.0.5)
> csslib 0.14.5 (was 0.14.4) (0.14.6 available)
+ dart2_constant 1.0.2+dart2
> file 5.0.6 (was 5.0.1)
> file_testing 2.0.3 (was 2.0.0)
+ flutter_goldens_client 0.0.0 from path ../flutter_goldens_client
> front_end 0.1.5 (was 0.1.0-alpha.12) (0.1.6 available)
> glob 1.1.7 (was 1.1.5)
> html 0.13.3+3 (was 0.13.3+1)
> http 0.12.0 (was 0.11.3+16)
  http_multi_server 2.0.5
> http_parser 3.1.3 (was 3.1.2)
> intl 0.15.7 (was 0.15.6)
> io 0.3.3 (was 0.3.2+1)
> js 0.6.1+1 (was 0.6.1)
> json_rpc_2 2.0.9 (was 2.0.8)
> json_schema 1.0.10 (was 1.0.8) (2.0.0-RC2 available)
> kernel 0.3.5 (was 0.3.0-alpha.12) (0.3.6 available)
> linter 0.1.66 (was 0.1.53) (0.1.68 available)
> logging 0.11.3+2 (was 0.11.3+1)
> matcher 0.12.3+1 (was 0.12.2) (0.12.4 available)
> meta 1.1.6 (was 1.1.5)
> mime 0.9.6+2 (was 0.9.6+1)
> mockito 3.0.0 (was 3.0.0-beta)
> multi_server_socket 1.0.2 (was 1.0.1)
> mustache 1.0.2 (was 1.0.1)
> node_preamble 1.4.4 (was 1.4.2)
> package_config 1.0.5 (was 1.0.3)
> package_resolver 1.0.6 (was 1.0.3)
> path 1.6.2 (was 1.6.1)
> petitparser 2.0.2 (was 1.7.6)
> platform 2.2.0 (was 2.1.2)
> plugin 0.2.0+3 (was 0.2.0+2)
> pool 1.3.6 (was 1.3.5)
> process 3.0.5 (was 3.0.1)
> pub_semver 1.4.2 (was 1.4.1)
> quiver 2.0.0+1 (was 0.29.0+1)
> shelf 0.7.3+3 (was 0.7.3+1)
> shelf_packages_handler 1.0.4 (was 1.0.3)
> shelf_static 0.2.8 (was 0.2.7+1)
> shelf_web_socket 0.2.2+4 (was 0.2.2+2)
> source_map_stack_trace 1.1.5 (was 1.1.4)
> source_maps 0.10.7 (was 0.10.5) (0.10.8 available)
> source_span 1.4.1 (was 1.4.0)
> stack_trace 1.9.3 (was 1.9.2)
> stream_channel 1.6.8 (was 1.6.7+1)
> string_scanner 1.0.4 (was 1.0.2)
> term_glyph 1.0.1 (was 1.0.0)
> test 1.3.3 (was 0.12.41) (1.3.4 available)
> typed_data 1.1.6 (was 1.1.5)
> usage 3.4.1 (was 3.4.0)
> utf 0.9.0+5 (was 0.9.0+4)
> vm_service_client 0.2.6 (was 0.2.4+3)
> watcher 0.9.7+10 (was 0.9.7+8)
> web_socket_channel 1.0.9 (was 1.0.8)
> xml 3.2.3 (was 3.0.0)
> yaml 2.1.15 (was 2.1.14)
Downloading mockito 3.0.0...
Downloading file_testing 2.0.3...
Downloading collection 1.14.11...
Downloading yaml 2.1.15...
Downloading logging 0.11.3+2...
Downloading shelf_packages_handler 1.0.4...
Downloading json_schema 1.0.10...
Downloading archive 2.0.4...
Downloading convert 2.0.2...
Downloading plugin 0.2.0+3...
Downloading stack_trace 1.9.3...
Downloading usage 3.4.1...
Downloading csslib 0.14.5...
Downloading crypto 2.0.6...
Downloading typed_data 1.1.6...
Downloading args 1.5.0...
Downloading package_resolver 1.0.6...
Downloading front_end 0.1.5...
Downloading linter 0.1.66...
Downloading source_maps 0.10.7...
Downloading vm_service_client 0.2.6...
Downloading js 0.6.1+1...
Downloading string_scanner 1.0.4...
Downloading shelf 0.7.3+3...
Downloading source_span 1.4.1...
Downloading process 3.0.5...
Downloading completion 0.2.1+1...
Downloading utf 0.9.0+5...
Downloading multi_server_socket 1.0.2...
Downloading stream_channel 1.6.8...
Downloading term_glyph 1.0.1...
Downloading shelf_web_socket 0.2.2+4...
Downloading json_rpc_2 2.0.9...
Downloading io 0.3.3...
Downloading xml 3.2.3...
Downloading http 0.12.0...
Downloading charcode 1.1.2...
Downloading async 2.0.8...
Downloading test 1.3.3...
Downloading coverage 0.12.2...
Downloading node_preamble 1.4.4...
Downloading analyzer 0.33.0-alpha.0...
Downloading http_parser 3.1.3...
Downloading path 1.6.2...
Downloading intl 0.15.7...
Downloading cli_util 0.1.3+2...
Downloading pub_semver 1.4.2...
Downloading glob 1.1.7...
Downloading platform 2.2.0...
Downloading pool 1.3.6...
Downloading kernel 0.3.5...
Downloading html 0.13.3+3...
Downloading package_config 1.0.5...
Downloading quiver 2.0.0+1...
Downloading watcher 0.9.7+10...
Downloading mime 0.9.6+2...
Downloading dart2_constant 1.0.2+dart2...
Downloading source_map_stack_trace 1.1.5...
Downloading boolean_selector 1.0.4...
Downloading matcher 0.12.3+1...
Downloading meta 1.1.6...
Downloading web_socket_channel 1.0.9...
Downloading petitparser 2.0.2...
Downloading mustache 1.0.2...
Downloading file 5.0.6...
Downloading shelf_static 0.2.8...
Changed 67 dependencies!
Precompiling executables... (1.0s)(1.1s)(1.2s)(1.3s)(1.4s)(1.5s)(1.6s)(1.7s)(1.8s)(2.0s)(2.1s)(2.2s)(2.3s)(2.4s)(2.5s)(2.6s)(2.7s)
Precompiled json_schema:gensamples.
Precompiled json_schema:schemadot.
Precompiled completion:shell_completion_generator.
Precompiled kernel:count_breakdown.
Precompiled csslib:css.
Precompiled kernel:dump.
Precompiled kernel:size_breakdown.
Precompiled kernel:eval.
Precompiled kernel:split.
Precompiled archive:tar.
Precompiled kernel:type_check.
Precompiled kernel:transform.
Precompiled coverage:run_and_collect.
Precompiled coverage:format_coverage.
Precompiled coverage:collect_coverage.
Precompiled linter:linter.
Precompiled test:test.
Downloading package sky_engine...                                0.2s
Downloading common tools...                                      0.3s
Downloading linux-x64 tools...                                   1.0s
Downloading android-arm-profile/linux-x64 tools...               0.1s
Downloading android-arm-release/linux-x64 tools...               0.1s
Downloading android-arm64-profile/linux-x64 tools...             0.1s
Downloading android-arm64-release/linux-x64 tools...             0.1s
Downloading android-arm-dynamic-profile/linux-x64 tools...       0.4s
Downloading android-arm-dynamic-release/linux-x64 tools...       0.1s
Downloading android-arm64-dynamic-profile/linux-x64 tools...      0.2s
Downloading android-arm64-dynamic-release/linux-x64 tools...      0.1s
Downloading android-x86 tools...                                 0.4s
Downloading android-x64 tools...                                 0.3s
Downloading android-arm tools...                                 0.1s
Downloading android-arm-profile tools...                         0.3s
Downloading android-arm-release tools...                         0.2s
Downloading android-arm64 tools...                               0.1s
Downloading android-arm64-profile tools...                       0.2s
Downloading android-arm64-release tools...                       0.1s
Downloading android-arm-dynamic-profile tools...                 0.2s
Downloading android-arm-dynamic-release tools...                 0.1s
Downloading android-arm64-dynamic-profile tools...               0.1s
Downloading android-arm64-dynamic-release tools...               0.1s
[✓] Flutter (Channel dev, v0.9.6, on Linux, locale en_US.UTF-8)
    • Flutter version 0.9.6 at /home/cirrus/sdks/flutter
    • Framework revision 13684e4f8e (3 days ago), 2018-10-02 14:15:17 -0400
    • Engine revision f6af1f20ba
    • Dart version 2.1.0-dev.6.0.flutter-8a919426f0

[✓] Android toolchain - develop for Android devices (Android SDK 26.0.2)
    • Android SDK at /opt/android-sdk-linux
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-26, build-tools 26.0.2
    • ANDROID_HOME = /opt/android-sdk-linux
    • Java binary at: /docker-java-home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-1~deb9u1-b12)
    • All Android licenses accepted.

[✗] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

It looks like you run flutter channel dev without flutter doctor and then flutter test --coverage
and then flutter doctor for the bug report did the actual updating to the dev channel.
What if you run
flutter -v test --coverage --concurrency=2

now again after Flutter is properly updated to dev channel?

Actually I just didn't post you all the logs...
Build runs in our CircleCI and it does the following on the cirrusci/flutter Docker image:
- checkout
- run: flutter channel dev
- run: flutter doctor -v
- run: flutter analyze
- run: flutter -v test --coverage --concurrency=2


steps to run under windows?

Has anyone successfully run the ava api server under windows? I was getting various errors under python 3.9 when trying to start the server. After installing dependencies, trying to start the server yields
File "[PATH]\my-vault\.obsidian\plugins\ava\semantic\env\lib\site-packages\obsidiantools\md_utils.py", line 273, in _get_md_front_matter_and_content
    return {}, file_string
UnboundLocalError: local variable 'file_string' referenced before assignment

Anyone managed to get it to start up?

maybe it would work with WSL
Inside WSL do
git clone https://github.com/louis030195/obsidian-ava.git
cd obsidian-ava/semantic
sh start-api.sh

(then skip the "start api" part in obsidian)

any news?


Re-release 0.18.0

금일 0.18.0으로 릴리즈 되었으나, 필요한 부분이 누락 되어 있는 것이 뒤늦게 발견(https://github.com/aicers/giganto-client/issues/123) 되어서, 기존의 tag를 취소하고 다시 tagging 합니다.

Thank you for the update and for your continuous efforts on the giganto-client project. However, I would like to express a concern regarding the modification of a public tag. As a public project, it is generally considered best practice to avoid modifying or deleting tags after they have been released. This can create confusion and potential issues for users who have already pulled the original version.
Instead of modifying the existing tag, it might be more appropriate to release a new version with the required fixes. This approach maintains a clear and consistent release history and ensures that anyone relying on the 0.18.0 version is not disrupted.

Thank you for your kind explanation. I will close this issue and open a new release issue.


Why the value function seems different from that in the paper?

I found the value function in the code is a Q table and is defined as (Q = np.zeros((n_agents, dim_Q_state, n_actions))).
However, the Q function in the paper is defined as (state,action1,action2). Why they are different?

@woaipichuli Hi, this repo currently contains the code for Ising model mentioned in Section 5.2, details can be found in Appendix C.2. Since the mean action here is the number of neighboring sites aligned in the same direction, we use a table to store the (action, action_mean) for each site.

Is the mean action a probability distribution?

@lyers179 yes

if the mean action is a probability distribution,how do you store the matrix Qtable Q(s,action,mean action)?because the index of Qtable(mean action)is a float not integer.

@lyers179 may you have some misunderstandings with deep reinforcement learning and MDPs. In stead of storing Q-table, we generally store many tuples (or transitions) like: <S_t, a_t, r_t, S_{t+1}>.

@lyers179 Hi, in the case of MFQ for Ising model, the mean action is the number of neighboring sites aligned in the same direction, which is a discrete distribution. Thus we can use a table to store the (action, action_mean) for each site.
For other applications, the definition of mean action could be different.

Thank you so much,i understand.


Infinite loop when running code

After playing around with Eve for a few minutes I found that the code below creates an infinite loop in the browser tab. I'm not sure whether this is intentional that this should not compute but it'd help if there were some feedback for the user if it is.
commit @browser
[#div text: "Hello World!"]

search @browser
divs = [#div]

commit @view
[#value value: divs]

It's already been reported I believe, and is happening because the view code is adding divs to the browser that can be seen by the search code.
You can work around it in a number of ways.
commit @browser
[#div #mydivs text: "Hello World!"]
search @browser
divs = [#div #mydivs]
Is probably the easiest.
Regards,
Cormac.

Thanks for the help. It looked like @browser only effects the application pane on the right.
Feel free to close this issue since it's based on a wrong assumption unless you think it makes sense for the editor to bind @browser to the application pane rather than the entire editor.

We're planning to make it behave more like you're intuition, so we'll keep
tracking this on the existing issue for it. The current behavior can be
surprising for a host of reasons including this one.
On Wed, Dec 7, 2016, 04:59 Thomas Greiner<EMAIL_ADDRESS>wrote:

Thanks for the help. It looked like @browser only effects the application
pane on the right.
Feel free to close this issue since it's based on a wrong assumption
unless you think it makes sense for the editor to bind @browser to the
application pane rather than the entire editor.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/witheve/Eve/issues/667#issuecomment-265440900, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATKDn13QZbRJ6aXyk-Xhw3_e7gBs1yIks5rFq2agaJpZM4LGYB-
.

Will Eve allow users to create view extensions/modes/plugins using the Eve language or will this only be possible in the implementation language? If yes, should there not be some kind of DOM access for the @view DB?


Webpack Beta 27?

Please provide us with the following information:

OS?

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

Versions.

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

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
N/A

The log given by the failure.

Normally this include a stack trace and some more information.
N/A

Mention any other details that might be useful.
I just wanted to ask if there were plans to update to the latest Webpack Beta in the near future? Thanks!

Thanks! We'll be in touch soon.

Sure, but it's unclear what features the latest beta would bring to us. We'll probably skip the beta until RC is available.