Try to improve performance of Dataflow Errors

The benchmarks in #8130 show that our handling of Panics is super fast, however the dataflow errors are far behind them - being 200x - 8500x slower.
It would be good if we could get the dataflow errors performance a bit closer to that of panics, because dataflow errors are the primary way of reporting errors in Enso standard library.
While at it, it would be good to still retain the ability to query the stack trace of a dataflow error, when needed. In most scenarios the stack trace is ignored (so the computational effort used to create it is wasted), but in some cases the stack trace may be very helpful - e.g. when reporting test suite failures or debugging. Somehow, Panics seem to be able to retain on-demand stack traces while also being fast - ideally it would be great to have the same for dataflow errors, if possible.

See this comment in the related PR for instructions how to run the benchmarks on JMH.

DataflowError creation used to be slow. It slowed down at:
cc73338 - Radosław Waśko<EMAIL_ADDRESS>Mar 18, 2022
The library developer should be able to handle specific types of Panics while passing through others (#3344)
Also ensures that Dataflow Errors have proper stack traces (earlier they did not point at the right location).

DataflowError creation used to be slow. It slowed down at:
cc73338 - Radosław Waśko<EMAIL_ADDRESS>Mar 18, 2022 The library developer should be able to handle specific types of Panics while passing through others (#3344)
Also ensures that Dataflow Errors have proper stack traces (earlier they did not point at the right location).

Yes, I suspected fixing stack traces was likely the cause for slowdown. We probably need to add them in a smarter 'more lazy' way.
Note that before this fix the error stack traces were completely useless and misleading - as IIRC if you queried the error stack trace, you were getting the location of the first time stack trace of that error was queried - i.e. usually just your current Runtime.get_stack_trace.

I was curious and did a little bit of digging into TruffleStackTrace.
So apparently, while unwinding the stack after an exception is thrown, whenever passing a CallTarget, the DefaultRuntimeAccessor.LANGUAGE.onThrowable is called, which in turn calls TruffleStackTrace.addStackFrameInfo which lazily adds stack frames to AbstractTruffleException.
Thus, if a Panic is caught not many frames later, and its full stack trace is never queried - we are saved from the overhead of constructing the full stack trace - hence the awesome performance.
Case for dataflow errors
The nice performance of panics is mostly due to 'lazy' adding of stack frames when we are unwinding the stack, looking for a try-catch clause.
Unfortunately, we cannot re-use this cool effect for Dataflow errors - because they do not propagate through stack unwinding, but are simply propagated by value passing. So most likely, we cannot easily perform such lazy optimization.
I guess a simple thing we still could do is to limit the depth of the stack trace - for many use cases, knowing only a few frames may still be enough to debug it.

Issue with panics
When looking into this, I noticed:

Note that if the Throwable is caught, its stack trace should be filled eagerly with TruffleStackTrace.fillIn(Throwable), unless it can be guaranteed to be re-thrown in the same call target, or that the stack trace will not be used.

within the TruffleStackTrace docs.
I realised that this would make Panics less efficient than they are now.
And indeed - we don't do what is described there. Is that ok?
Well, apparently not exactly. This actually proved to me something of which I was suspicious for a long time. When working with Enso library tests, I've been sifting through tons of Enso Panic stack traces. And I felt like sometimes the stack trace may be a little bit off, but I never digged deeper into this and thought I was mistaken. Apparently I was right.
See this repro:
from Standard.Base import all

type My_Error
    Error

handler caught_panic =
    do_the_handling caught_panic

do_the_handling caught_panic =
    st = caught_panic.stack_trace
    st.each el->
        IO.println el.to_display_text

f1 = f2
f2 = f3
f3 =
    Panic.catch Any handler=handler <|
        f4

f4 = f5
f5 = Panic.throw My_Error.Error

main =
    f1

running it yields:
at Panic.throw (Unknown location)
at stacks.f5 (C:\NBO\repr\stacks.enso:21:6-31)
at stacks.f4 (C:\NBO\repr\stacks.enso:20:6-7)
at stacks.f3<arg-1> (C:\NBO\repr\stacks.enso:18:9-10)
at Panic.type.get_attached_stack_trace (Unknown location)
at Caught_Panic.stack_trace (built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Base\0.0.0-dev\src\Panic.enso:233:9-43)
at stacks.do_the_handling (C:\NBO\repr\stacks.enso:10:10-33)
at stacks.handler (C:\NBO\repr\stacks.enso:7:5-32)
at Panic.catch (Unknown location)
at stacks.f3 (C:\NBO\repr\stacks.enso:17-18)
at stacks.f2 (C:\NBO\repr\stacks.enso:15:6-7)
at stacks.f1 (C:\NBO\repr\stacks.enso:14:6-7)
at stacks.main (C:\NBO\repr\stacks.enso:24:5-6)

This stacktrace is actually wrong. It should be:
at Panic.throw (Unknown location)
at stacks.f5 (C:\NBO\repr\stacks.enso:21:6-31)
at stacks.f4 (C:\NBO\repr\stacks.enso:20:6-7)
at stacks.f3<arg-1> (C:\NBO\repr\stacks.enso:18:9-10)
at Panic.catch (Unknown location)
at stacks.f3 (C:\NBO\repr\stacks.enso:17-18)
at stacks.f2 (C:\NBO\repr\stacks.enso:15:6-7)
at stacks.f1 (C:\NBO\repr\stacks.enso:14:6-7)
at stacks.main (C:\NBO\repr\stacks.enso:24:5-6)

So we have additional 4 frames:
at Panic.type.get_attached_stack_trace (Unknown location)
at Caught_Panic.stack_trace (built-distribution\enso-engine-0.0.0-dev-windows-amd64\enso-0.0.0-dev\lib\Standard\Base\0.0.0-dev\src\Panic.enso:233:9-43)
at stacks.do_the_handling (C:\NBO\repr\stacks.enso:10:10-33)
at stacks.handler (C:\NBO\repr\stacks.enso:7:5-32)

added in the middle that are not related with the 'throw' site of the panic, but are part of the panic handler.
Why?
Because when we catch a Panic, we do not fill in the stack trace (hence catching it is very cheap - that is the cool part). Truffle fills in the stack trace for us the first time we request it. So the stack trace gets filled in at the location we request it, which may not exactly be the location we caught it at (that is the less cool part). Usually it is 'close' to the 'correct' location, so it is off only by a few frames - so the stack trace may still be useful.
However, it is technically incorrect.
Should we improve it?
I think it is not good to return invalid stack traces, even if they are off by just a few frames. Technically, if I save my caught_panic and pass it around, I can get a completely 'crazy' stack trace, not very related to the actual panic - the top few frames will come from the panic, but the filled in bottom can really be arbitrary.
Of course, filling it in on catch comes with a cost - catching panics would no longer be as fast. It would likely start to be closer to the current Dataflow error performance. Well this ticket was about making dataflow errors faster, not slowing down Panics to make stuff equal 😓
The issue only arises when we want to access the stack trace. Oftentimes, we catch the panic and actually ignore the stack trace - and that's when we expect the good performance.
My suggestion is to create two versions of Panic.catch: Panic.catch_with_stacktrace and Panic.catch_without_stacktrace (I guess one of these could still be named Panic.catch):

Panic.catch_with_stacktrace would fill in the missing part of the stack trace at the 'catch-site', ensuring that the stack trace is correct. This variant will be slower, but it will ensure correct stack trace. Users that want to access the stack trace (when they would pay this price anyway) can use this variant. This will not really be slower, as code accessing the stacktrace was suffering from the price of filling it in anyway.
Panic.catch_without_stacktrace would not fill the stack trace, and it would set a flag boolean isStackTraceAvailable to false. This way, if caught_panic.stack_trace is ever accessed, we can throw something like IllegalStateException telling the user that this is not allowed. Thus, we will not expose an invalid stack trace. This variant could be used by users that want better performance but do not care about the stack trace anyway.

I think with such solution we can still retain good performance of catching panics and ensure that our stack traces are not misleading.

We can fix the stacktrace (thanks for such a detailed investigation), but that's probably task for another bug, not one titled _ Try to improve performance of Dataflow Errors_.

We can fix the stacktrace (thanks for such a detailed investigation), but that's probably task for another bug, not one titled Try to improve performance of Dataflow Errors.

Fair, I will create a separate ticket for this.

Here is a guaranteed way to speed benchmarks up:
enso$ git diff
diff --git engine/runtime/src/main/java/org/enso/interpreter/runtime/error/DataflowError.java engine/runtime/src/main/java/org/enso/interpreter/runtime/error/DataflowError.java
index 5ca69cda53..695a695076 100644
--- engine/runtime/src/main/java/org/enso/interpreter/runtime/error/DataflowError.java
+++ engine/runtime/src/main/java/org/enso/interpreter/runtime/error/DataflowError.java
@@ -41,7 +42,7 @@ public final class DataflowError extends AbstractTruffleException {
   public static DataflowError withoutTrace(Object payload, Node location) {
     assert payload != null;
     DataflowError result = new DataflowError(payload, location);
-    TruffleStackTrace.fillIn(result);
+    // TruffleStackTrace.fillIn(result);
     return result;
   }

obviously with such a change the benchmarks run lightening fast. DataflowError becomes just a value with recorded location of origin (e.g. the top of the stack trace). With following change
diff --git engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin/error/ThrowErrorNode.java engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin/error/ThrowErrorNode.java
index 12ebeb6d41..20db654b05 100644
--- engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin/error/ThrowErrorNode.java
+++ engine/runtime/src/main/java/org/enso/interpreter/node/expression/builtin/error/ThrowErrorNode.java
@@ -8,7 +8,9 @@ import org.enso.interpreter.runtime.error.DataflowError;
 @BuiltinMethod(
     type = "Error",
     name = "throw",
-    description = "Returns a new value error with given payload.")
+    description = "Returns a new value error with given payload.",
+    inlineable=true
+  )
 public class ThrowErrorNode extends Node {
   public Object execute(VirtualFrame giveMeAStackFrame, Object payload) {
     return DataflowError.withoutTrace(payload, this);

we make sure the real location of Error.throw is recorded (instead of some internal builtin location). As a result following x.enso program
from Standard.Base import all
import Standard.Base.Errors.Illegal_Argument.Illegal_Argument

deep n = if n <= 0 then Error.throw (Illegal_Argument.Error "Problem") else deep n-1

main =
    d = deep 10
    d.get_stack_trace_text

generates following output:
at <enso> x.deep<arg-1>(x.enso:4:25-70)

I consider such output satisfactory to locate where the error is coming from. Am I (totally) wrong?
Btw. the Java method to construct the DataflowError is called withoutTrace - I believe that's what my change does, right? Constructing an DataflowError without a stack trace!

I consider such output satisfactory to locate where the error is coming from. Am I (totally) wrong?

Unfortunately, it is often far from enough to locate the error.
i. The error may be thrown within a helper method deeper down the call chain, so it may not tell us the particular operation where the error failed.
ii. Even more, we are using an 'idiom' where we often catch a Java exception and 'convert' it to a dataflow error. Since the logic for conversion of the same error is most of the time the same, we use helper functions to handle this catch-and-throw. Examples: Illegal_Argument.handle_java_exception, handle_sql_errors and tons more.

I think we rather need to still support this idiom, changing this abstraction into code duplication is not a path we could take.
So with that, most often the location of the error will be within some handle_ function - which really does not tell us anything useful at all.

Debugging
i. Obviously, knowing the full stack trace is invaluable for debugging. I cannot imagine a world where we do not have traces on dataflow errors - when debugging various tests it is just immensely helpful to be able to read the stacktrace of where the error originated from, with all the context of the full call-chain. I don't think we can lose that and retain good developer experience.
ii. This may be less of a concern because: If we get some solution to (1), I guess we could enable some 'debug mode' flag to enable the full stack traces only during development. But we do need some way to enable this, as otherwise working on library development would get significantly less efficient.

often catch a Java exception and 'convert' it to a dataflow error.

This is done via DataflowError.withTrace - that one is still inheriting the top of the stack trace from Panic and (slowly) recording the rest (possibly with some limit) of the stack trace.

enable some 'debug mode' flag to enable the full stack traces only during development

There is JAVA_OPTS=-ea now which could be used for such a purpose.

often catch a Java exception and 'convert' it to a dataflow error.

This is done via DataflowError.withTrace - that one is still inheriting the top of the stack trace from Panic and (slowly) recording the rest (possibly with some limit) of the stack trace.

Yeah, although that is only used when we convert the Panic instance into dataflow error (we catch it and change how it flows through the computation), while still remaining a Java interop instance. What we do most of the time, is we rethrow a new Enso Atom instance as dataflow error - which is a more user-oriented value. I guess we'd need to attach the original Java error as cause to be able to access its stack trace.

enable some 'debug mode' flag to enable the full stack traces only during development

There is JAVA_OPTS=-ea now which could be used for such a purpose.

I think we should not override -ea with so many implications. Why not use a separate env var? Although I guess -ea could be OK too.

As of https://github.com/enso-org/enso/pull/8608/commits/891b08d766eacf7e3b043c57d62a9aabd9e619e4 the Benchmark run indicates the Panics_And_Errors_10000_Dataflow_Error test (created by #8130 pull request) has been sped up significantly:

Previously it took 329ms, now it runs in 0,045ms.


Create 1448-Count-Good-Nodes-in-Binary-Tree.cs

File(s) Modified: "1448-Count-Good-Nodes-in-Binary-Tree.cs"
Language(s) Used: c#
Submission URL: https://leetcode.com/submissions/detail/752828632/

Thanks, @notauserx!


Add trigger character to SignatureHelpProvider

Problem
Some signature help providers need to know why they are triggered. See https://github.com/Microsoft/TypeScript/pull/24915 for more details on one use case
Proposal
Pass the triggerCharacter to the provideSignatureHelp call. This could be introduced in a context  parameter at the end of the parameter list:
export interface SignatureHelpContext {
    triggerCharacter?: string;
}

export interface SignatureHelpProvider {

	provideSignatureHelp(document: TextDocument, position: Position, token: CancellationToken, context: SignatureHelpContext): ProviderResult<SignatureHelp>;
}

Moving to more generic proposal: #54972


embedding Flow components into TypeScript views does not work

If I follow the Creating an Embedded Vaadin Application Tutorial in order to embed a server-side Vaadin component into a TypeScript Vaadin view, my application does not work as expected:

the tutorial tells me that I need to include the webcomponents-loader script and gives code snippets how to do that. These code snippets do not work. Moreover, the entire step of loading WebComponents polyfils is not needed because all browsers supported by Vaadin 15+ do support Web Components natively.
If I skip the WC polyfils (or if I manage to find my way to load them), embedding still fails with a Uncaught TypeError: window.Vaadin.Flow.initApplication is not a function error:

ServerCounter.java:
public class ServerCounter extends Div {

    public ServerCounter() {
        add(new Label("Server-side counter"));
    }

    public static class Exporter extends WebComponentExporter<ServerCounter> {
        public Exporter() {
            super("server-counter");
        }

        @Override
        protected void configureInstance(
                WebComponent<ServerCounter> webComponent,
                ServerCounter counter) {
        }
    }
}

index.html:
<script type="module" src="web-component/server-counter.js"></script>

main-layout.ts:
render() {
  return html`
      <server-counter></server-counter>
      <slot></slot>
  `;
}

Proper embedding support has been implemented and documented for Vaadin 24.4


Error compiling module in sibling directory

Does TS require to run in the directory containing the module(s) to be compiled? Here's what happens when I try to compile a module in a sibling directory. (FWIW, the module in question doesn't have any imports.)
Michaels-Mac-mini:app-ace-interface mellis$ transcrypt -b -n ../modules/aceconfig.py

Transcrypt (TM) Python to JavaScript Small Sane Subset Transpiler Version 3.6.24
Copyright (C) Geatec Engineering. License: Apache 2.0

list index out of rangeTraceback (most recent call last):
  File "/Users/mellis/anaconda3/lib/python3.5/site-packages/transcrypt/modules/org/transcrypt/compiler.py", line 143, in __init__
    moduleMetadata = ModuleMetadata (self, self.mainModuleName)
  File "/Users/mellis/anaconda3/lib/python3.5/site-packages/transcrypt/modules/org/transcrypt/compiler.py", line 64, in __init__
    '\n\tCan\'t find any of:\n\t\t{}\n'.format ('\n\t\t'. join (searchedModulePaths))
org.transcrypt.utils.Error: <unprintable Error object>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/mellis/anaconda3/lib/python3.5/site-packages/transcrypt/__main__.py", line 119, in main
    compiler.Program (compilerPath, __symbols__)
  File "/Users/mellis/anaconda3/lib/python3.5/site-packages/transcrypt/modules/org/transcrypt/compiler.py", line 148, in __init__
    message = '\n\t{}'.format (str (exception))
  File "/Users/mellis/anaconda3/lib/python3.5/site-packages/transcrypt/modules/org/transcrypt/utils.py", line 124, in __str__
    result += '\n\tFile \'{}\', line {}, namely:'.format (program.importStack [-1][0] .sourcePath, self.lineNr)
IndexError: list index out of range

EDIT: Same error if the module is in a child directory.
Compiles w/o error if I cd to the directory containing the file.
Michaels-Mac-mini:app-ace-interface mellis$ cd ../modules
Michaels-Mac-mini:modules mellis$ transcrypt -b -n aceconfig.py

Transcrypt (TM) Python to JavaScript Small Sane Subset Transpiler Version 3.6.24
Copyright (C) Geatec Engineering. License: Apache 2.0

Saving result in: /Users/mellis/PGC-SmartTabletPlus/modules/__javascript__/aceconfig.js

Ready

Yes, currently Transcrypt has to run in the directory where the "main module" is.
This is something that is planned to be changed, but currently not with a high priority.
How much of a hindrance this is to your development?

Thanks, Jacques.  It's not a showstopper for me as long as sys.path is honored at compile time. If it's easy to do, I'd suggest arranging for a less cryptic error message that explains the limitation.

For the occasional reader: Other modules can be in the places indicated in:
http://www.transcrypt.org/docs/html/special_facilities.html#transcrypt-s-module-mechanism

Pull request #362 should have solved this.
If not feel free to reopen.
KR
J


MetricsTestKit: expose all metrics publicly. This allows users to run checks on counters when they might not know the exact label

Provide functions on TestMetrics to retrieve all counters/timers/recorders
Motivation:
Users may want to iterate over metrics to perform some complex assertions. For example, they might want to confirm that no metrics have been emitted with a certain dimension
Modifications:
Added functions for allRecorders, allTimers and allCounters which return arrays of TestRecorder, TestTimer and TestCounter

@swift-server-bot add to allowlist

This has a merge conflict now due to the introduced meters on main, could you rebase @hamzahrmalik ?
Otherwise LGTM so let's merge this and the follow up which adds tests to this 👍

I actually think we should merge #128 first
That one is simply a refactor, and will make this one very simple (just adding public modifiers)

Yeah that works, merged #128 👍


UI view of Swap platform completed

Description
Concise description of proposed changes, We recommend using screenshots and videos for better description
I have successfully completed every UI visuals required for the ScrollSwap Ether Wrapper
What is left now is the implementation of the smart contract with its test suites.
Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
Closes #{issue number}
Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.
Your ENS/address:
0xDB9B936373f859Ce8C580Bbc35b0Eab89cA9fd70

Great


media-type: add a media-type for descriptor

For the "image layout" that can be tar'd, zip'd, etc we need to create the spec and media-type for the "descriptor"
https://github.com/opencontainers/image-spec/blob/master/schema/defs-image.json#L23
Relevant IRC convo:
4:08 PM <philips> stevvooe: this response? https://github.com/opencontainers/image-spec/pull/82#issuecomment-221980346
4:09 PM <stevvooe> philips: yes
4:09 PM <stevvooe> philips: it just means that we deserialize a descriptor, rather than a few fields of the manifest
4:09 PM <philips> stevvooe: I don't know what you mean by half-deserialized still
4:09 PM <philips> stevvooe: what is a descriptor?
4:09 PM <stevvooe> philips: "partially-serialized" would probably be more accurate
4:10 PM <stevvooe> stevvooe: this structure: {"size": 4096, "digest": "sha256:afff3928", "mediatype": "application/vnd.oci.image.manifest.v1+json"}
4:10 PM <philips> stevvooe: ah, ok. well, did you see my concern about mime types?
4:10 PM <stevvooe> philips: yea, and now i think i understand your example
4:11 PM <philips> stevvooe: like my structure is identical but allows for N media types: https://github.com/opencontainers/image-spec/pull/82#issuecomment-221760143
4:11 PM <stevvooe> philips: i think if we push that dispatch to a manifest list, we can avoid a large amount of unverified content
4:12 PM <philips> stevvooe: so you suggest always force a manifest list?
4:12 PM <philips> stevvooe: like the manifest list is always the thingie we point to in this "container"
4:12 PM <stevvooe> philips: so, the options are <descriptor> -> <manifest list> or <new format: [descriptor]> -> <arbitrary>
4:13 PM <stevvooe> philips: that might be the right approach
4:13 PM <philips> stevvooe: yea, not opposed to the descriptor thing for "file transport containers"
4:13 PM <philips> stevvooe: and always pointing to a manifest list makes sense, I think.
4:13 PM <stevvooe> philips: btw, here is the descriptor def : https://github.com/opencontainers/image-spec/blob/master/schema/defs-image.json#L14
4:15 PM <philips> stevvooe: got it, we only ever refer to it that way in code instead of in the spec so I wasn't familiar with the term
4:15 PM <philips> stevvooe: thanks, makes sense
4:17 PM <stevvooe> philips: great! we may want to pull out the descriptors into another specification, maybe post-.10
4:17 PM <wking> philips: re: "always pointing to a manifest list makes sense".  If you don't assume that, it's easy to check and have tooling error out if it hits an unsupported MIME type
4:18 PM <wking> If you do assume that, you're stuck with it for as long as you want to keep backwards compatability with old tooling
4:18 PM <philips> stevvooe: like into their own mime-type?
4:18 PM <wking> (assuming the old tooling also assumed that and didn't check the descriptor MIME type https://github.com/opencontainers/image-spec/blob/master/schema/defs-image.json#L23
4:19 PM <stevvooe> philips: yes. file an issue and i'll take that on
4:20 PM <philips> wking: ack, right, I think the list is sufficiently dumb/flat enough to not require breaking changes for a long time.
4:20 PM <philips> stevvooe: sounds good, thanks.
4:20 PM <wking> sure, but what's the benefit to taking that risk in the spec?
4:20 PM <philips> wking: what are you suggesting as an alternative?
4:21 PM <wking> that the spec not require a particular MIME type for the reference descriptors
4:21 PM <philips> wking: so a descriptor sans mediatype? {"size": 4096, "digest": "sha256:afff3928"}
4:21 PM <wking> I am +1 on clients only supporting the manifest list for as long as they make sense, but if the spec *requires* a given MIME type it makes the eventual upgrade awkward
4:22 PM <wking> philips: no, include the linked MIME type in the descriptor, just don't say "reference descriptors MUST set ...manifest.list... as their mediaType"
4:22 PM <philips> oh, right, yes, +1
4:22 PM <philips> that was my intention/plan

@stevvooe Are you still able to take this one?

Yes.

And the JSON schema for this (which should be very straight forward)


Can't set trust_remote_code to True to be able to load custom class.

System Info
Optimum version: 1.6.1 [onnxruntime-gpu]
Python version: 3.10.8
Platform: Ubuntu 20.04 LTS

I have slightly modified classification model, I just customized the head a little bit and I need to import the model from a python file in my local folder.

So I tried this code after I got an error asking me to set `trust_remote_code` to `True`, but then I got an error.

Is it by design or is it a bug? The pipeline works fine on `transformers`.

Who can help?
@philschmid @lewtun @mic
Information

[ ] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
model = ORTModelForSequenceClassification.from_pretrained(
    "./test-model",
    from_transformers=True,
    provider="CUDAExecutionProvider",
    trust_remote_code=True,
)

Expected behavior
TypeError: ORTModel._from_transformers() got an unexpected keyword argument 'trust_remote_code'

Hi @LiamNiisan , thank you for the feedback! The option was added in the linked PR, it will be there in the next Optimum release.


Aliases don't seem to work when defined in blueprints

https://stackblitz.com/edit/nuxt-starter-5qj9ao?file=nuxt.config.ts
Defaults work, but components inside aliases have a Component is missing template or render function warning and don't render.
From a quick look at source code, I think it's because they don't get mapped to the components properly like the regular aliases config property.
Current hack solution
// vuetify.config.ts
...
blueprint: {
  defaults: blueprint.defaults,
},
aliases: blueprint.aliases,
...

// blueprint.ts
import type { ComponentName } from 'vuetify-nuxt-module'

export default {
  aliases: {
   MyBtn: 'VBtn',
  } as Record<string, ComponentName>,
  ...
}

Bonus tip for anyone dealing with Typescript and needing Intellisense on your virtual components:
declare module '@vue/runtime-dom' {
  export interface GlobalComponents {
    MyBtn: typeof import('vuetify/components')['VBtn']
  }
}

Check the docs, you cannot use Vuetify blueprints, it has some limitations, I need to review the logic.
I'll check if I can register global aliases.

Check the docs, you cannot use Vuetify blueprints, it has some limitations, I need to review the logic.
I'll check if I can register global aliases.

According to the docs, you can use blueprints, though.
https://vuetify-nuxt-module.netlify.app/guide/vuetify-blueprints.html
It says aliases can be used if used with string components. If this is not possible, the aliases option should be marked as unsupported.

Do you want me to close this? It has been a year and the docs are still the same.


Unable to import xclim in conda environment

xclim version: 0.27.0
Python version: 3.8.10
Operating System:

Platform Info:
  OS: Linux (x86_64-redhat-linux)
  CPU: Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.1 (ORCJIT, skylake)

Description
Created an environment with Conda and installed xarray, cartopy and xclim.
What I Did
# bash
$ conda create --name xclim_test python=3.8
$ conda activate xclim_test
$ conda install pip xclim xarray cartopy

# python
>>> import xclim as xc
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/xclim/__init__.py", line 17, in <module>
    build_indicator_module_from_yaml(f, mode="raise")
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/xclim/core/indicator.py", line 1252, in build_indicator_module_from_yaml
    yml = safe_load(f)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/__init__.py", line 162, in safe_load
    return load(stream, SafeLoader)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/__init__.py", line 112, in load
    loader = Loader(stream)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/loader.py", line 34, in __init__
    Reader.__init__(self, stream)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/reader.py", line 85, in __init__
    self.determine_encoding()
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/reader.py", line 135, in determine_encoding
    self.update(1)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/reader.py", line 169, in update
    self.check_printable(data)
  File "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/yaml/reader.py", line 143, in check_printable
    raise ReaderError(self.name, position, ord(character),
yaml.reader.ReaderError: unacceptable character #x0097: special characters are not allowed
  in "/gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/xclim/data/icclim.yml", position 2033

I am attaching the yml env file, hoping it helps in the investigation (yml file inside the zipped file).
Thanks!
xclim_env.zip

This problem is really strange! I can't replicate it on any of my machines (all linux 64-bit). I also can't find the "x0097" character in the icclim.yml file....
Can you try to reinstall xclim? With pip?
Also, could you send here the file: /gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/xclim/data/icclim.yml ? The error make it look like it is different from the one on github...

This makes me wonder if your environment supports UTF-8 characters...

This makes me wonder if your environment supports UTF-8 characters...

That might be it! The 2033th character of icclim.yml is "◦" (which doesn't translate to 0x0097, but rather 25e6 in hex and 9702 in dec. well). The full line reads: long_name: Summer days (TX>25◦C).
@Balinus  What is the result of:
import sys
sys.maxunicode

?
Anyway, ◦ is "White bullet"  and not °, "Degree Sign", which should be accepted by most machines (maybe @Balinus you could try is your python understands "\u00B0"?). Sorry, that was copy-pasta from the ECAD docs on my part, I didn't realize the character was wrong!

The problem was indeed utf-8!
For reference, here's my previous locale default configuration
(xclim_test) [dl2594@login-9-1 ~]$ locale
LANG=fr_CA.utf8
LC_CTYPE="en_US.iso885915"
LC_NUMERIC="en_US.iso885915"
LC_TIME="en_US.iso885915"
LC_COLLATE="en_US.iso885915"
LC_MONETARY="en_US.iso885915"
LC_MESSAGES="en_US.iso885915"
LC_PAPER="en_US.iso885915"
LC_NAME="en_US.iso885915"
LC_ADDRESS="en_US.iso885915"
LC_TELEPHONE="en_US.iso885915"
LC_MEASUREMENT="en_US.iso885915"
LC_IDENTIFICATION="en_US.iso885915"

Here's the new one (changed every setting... probably overkill!):
LANG=fr_CA.utf8
LC_CTYPE="fr_CA.utf8"
LC_NUMERIC="fr_CA.utf8"
LC_TIME="fr_CA.utf8"
LC_COLLATE="fr_CA.utf8"
LC_MONETARY="fr_CA.utf8"
LC_MESSAGES="fr_CA.utf8"
LC_PAPER="fr_CA.utf8"
LC_NAME="fr_CA.utf8"
LC_ADDRESS="fr_CA.utf8"
LC_TELEPHONE="fr_CA.utf8"
LC_MEASUREMENT="fr_CA.utf8"
LC_IDENTIFICATION="fr_CA.utf8"
LC_ALL=fr_CA.utf8

Re-opening because we still need to fix the wrong degree signs in the yamls.
But happy you were able to workaround it on your side!

Do you still need the /gpfs/groups/gc086/DL2495/s2s_conda/lib/python3.8/site-packages/xclim/data/icclim.yml file?

No, thanks! We'll change the "white circle" to "degree sign" in the current file and test with "en_US.iso885915" for good measure.


assign crashes assignment not adding up

when assign crashes finishes, reports that the total number of crashes doesn't equal assigned + unassigned. need to figure out what's going on here

@jessnoo could you help me understand how the sample data for #54 was generated? I will test against the full states data and all route types to see if the problem starts there. However, when I run BasicSegmentation on Prince George's county only the result dataset I get is quite different than what was attached to #54 and I don't reproduce this issue with that data.

@jessnoo I ran BasicSegmentation on the full states data and then ran Assign Crashes and was unable to reproduce the situation above. I received the email with a screenshot of your inputs and will dig through it further.

@jessnoo so it ended up being a PY3 Pro, vs PY2 Map issue. We were calling SelectLayerByAttribute then creating an UpdateCursor. In Pro the cursor does not honor the selection. Modified it to pass the where clause directly to the cursor.

validated


[Fix][WRS-1658] Add PDF export (out of experimental)

This PR adds PDF as the export setting

Approved by aqa


API connection failed

API connection failed
Hi people!
I can't get any API data (local or remote) on Android version 10.
Did anyone really have a problem?

Hi @zaumaiano
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample?
Thank you

Hi @zaumaiano
Can you please provide your flutter doctor -v, your flutter run --verbose and a minimal complete reproducible code sample?
Thank you

Hi, @pedromassango!
Is a problem that is occurring with unsecured http links.

flutter doctor -v:

➜  list_project flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on Linux, locale en_US.UTF-8)
    • Flutter version 2.0.4 at /path/snap/flutter/common/flutter
    • Framework revision b1395592de (6 days ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /path/Android/Sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /usr/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_282-8u282-b08-0ubuntu1~20.04-b08)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at google-chrome
[✓] Linux toolchain - develop for Linux desktop
• clang version 10.0.0-4ubuntu1
• cmake version 3.16.3
• ninja version 1.10.0
• pkg-config version 0.29.1
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
[✓] IntelliJ IDEA Community Edition (version 2020.3)
• IntelliJ at /snap/intellij-idea-community/289
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] Connected device (3 available)
• Nokia 6 2 (mobile) • N0AA002824K52602007 • android-arm64  • Android 10 (API 29)
• Linux (desktop)    • linux               • linux-x64      • Linux
• Chrome (web)       • chrome              • web-javascript • Google Chrome 89.0.4389.90
! Doctor found issues in 1 category.

flutter doctor -v:

[  +61 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +30 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] b1395592de68cc8ac4522094ae59956dd21a91db
[        ] executing: [/home/ghost/snap/flutter/common/flutter/] git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[  +12 ms] Exit code 0 from: git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[        ] 2.0.4
[  +35 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/home/ghost/snap/flutter/common/flutter/] git ls-remote --get-url origin
[   +4 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +37 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[   +4 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +55 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +55 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb devices -l
[  +41 ms] List of devices attached
N0AA002824K52602007    device usb:1-9 product:Starlord_00WW model:Nokia_6_2 device:SLD_sprout transport_id:3
[   +7 ms] /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell getprop
[  +38 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +83 ms] Skipping pub get: version match.
[ +137 ms] Generating /home/ghost/Documents/learning/flutter/list_project/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +64 ms] ro.hardware = qcom
[  +40 ms] Initializing file store
[  +10 ms] Skipping target: gen_localizations
[   +6 ms] complete
[   +5 ms] Launching lib/main.dart on Nokia 6 2 in debug mode...
[   +5 ms] /home/ghost/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/ghost/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/ghost/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names
--experimental-emit-debug-metadata --output-dill /tmp/flutter_tools.JUBWTR/flutter_tool.PBDSUM/app.dill --packages
/home/ghost/Documents/learning/flutter/list_project/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation
--filesystem-scheme org-dartlang-root --initialize-from-dill build/cache.dill.track.dill
[  +10 ms] executing: /home/ghost/Android/Sdk/build-tools/30.0.3/aapt dump xmltree
/home/ghost/Documents/learning/flutter/list_project/build/app/outputs/flutter-apk/app.apk AndroidManifest.xml
[   +4 ms] Exit code 0 from: /home/ghost/Android/Sdk/build-tools/30.0.3/aapt dump xmltree
/home/ghost/Documents/learning/flutter/list_project/build/app/outputs/flutter-apk/app.apk AndroidManifest.xml
[        ] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1e
A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
A: package="com.example.list_project" (Raw: "com.example.list_project")
A: platformBuildVersionCode=(type 0x10)0x1e
A: platformBuildVersionName=(type 0x10)0xb
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=16)
A: android:label(0x01010001)="list_project" (Raw: "list_project")
A: android:icon(0x01010002)=@0x7f080000
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=21)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.example.list_project.MainActivity" (Raw: "com.example.list_project.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: meta-data (line=35)
A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
A: android:resource(0x01010025)=@0x7f0a0001
E: meta-data (line=45)
A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
A: android:resource(0x01010025)=@0x7f040000
E: intent-filter (line=49)
E: action (line=50)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=52)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=59)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[   +8 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell -x logcat -v time -t 1
[  +13 ms] <- compile package:list_project/main.dart
[  +41 ms] --------- beginning of main
04-07 20:52:33.524 D/StatusBarMobileView( 2254):  applyMobileState updateState done
[   +9 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb version
[   +4 ms] Android Debug Bridge version 1.0.41
Version 31.0.1-7187441
Installed as /home/ghost/Android/Sdk/platform-tools/adb
[   +2 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb start-server
[   +6 ms] Building APK
[  +20 ms] Running Gradle task 'assembleDebug'...
[   +3 ms] Using gradle from /home/ghost/Documents/learning/flutter/list_project/android/gradlew.
[        ] /home/ghost/Documents/learning/flutter/list_project/android/gradlew mode: 33277 rwxrwxr-x.
[   +7 ms] executing: [/home/ghost/Documents/learning/flutter/list_project/android/] /home/ghost/Documents/learning/flutter/list_project/android/gradlew -Pverbose=true
-Ptarget-platform=android-arm64 -Ptarget=/home/ghost/Documents/learning/flutter/list_project/lib/main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
assembleDebug
[+3112 ms] > Task :app:compileFlutterBuildDebug
[        ] [  +78 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [  +33 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] [        ] b1395592de68cc8ac4522094ae59956dd21a91db
[        ] [        ] executing: [/home/ghost/snap/flutter/common/flutter/] git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[        ] [  +11 ms] Exit code 0 from: git tag --points-at b1395592de68cc8ac4522094ae59956dd21a91db
[        ] [        ] 2.0.4
[        ] [  +40 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[        ] [   +3 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] [        ] origin/stable
[        ] [        ] executing: [/home/ghost/snap/flutter/common/flutter/] git ls-remote --get-url origin
[        ] [   +3 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] [        ] https://github.com/flutter/flutter.git
[        ] [  +36 ms] executing: [/home/ghost/snap/flutter/common/flutter/] git rev-parse --abbrev-ref HEAD
[        ] [   +3 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] [        ] stable
[        ] [  +46 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [  +44 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] [        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[        ] [        ] Artifact Instance of 'PubDependencies' is not required, skipping update.
[        ] [  +61 ms] Initializing file store
[        ] [  +11 ms] Skipping target: gen_localizations
[        ] [   +5 ms] kernel_snapshot: Starting due to {}
[   +1 ms] [   +9 ms] /home/ghost/snap/flutter/common/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/home/ghost/snap/flutter/common/flutter/bin/cache/artifacts/engine/linux-x64/frontend_server.dart.snapshot --sdk-root
/home/ghost/snap/flutter/common/flutter/bin/cache/artifacts/engine/common/flutter_patched_sdk/ --target=flutter --no-print-incremental-dependencies -Ddart.vm.profile=false
-Ddart.vm.product=false --enable-asserts --track-widget-creation --no-link-platform --packages
/home/ghost/Documents/learning/flutter/list_project/.dart_tool/package_config.json --output-dill
/home/ghost/Documents/learning/flutter/list_project/.dart_tool/flutter_build/5a3719e9a9b3d9d67e77af132653a352/app.dill --depfile
/home/ghost/Documents/learning/flutter/list_project/.dart_tool/flutter_build/5a3719e9a9b3d9d67e77af132653a352/kernel_snapshot.d package:list_project/main.dart
[+7369 ms] [+8690 ms] kernel_snapshot: Complete
[ +500 ms] [ +443 ms] debug_android_application: Starting due to {}
[ +199 ms] [ +238 ms] debug_android_application: Complete
[ +600 ms] [ +598 ms] Persisting file store
[        ] [   +6 ms] Done persisting file store
[        ] [   +5 ms] build succeeded.
[        ] [  +10 ms] "flutter assemble" took 10,148ms.
[        ] [   +3 ms] ensureAnalyticsSent: 0ms
[        ] [        ] Running shutdown hooks
[        ] [        ] Shutdown hooks complete
[        ] [        ] exiting with code 0
[ +207 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[        ] > Task :app:preBuild UP-TO-DATE
[        ] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[        ] > Task :app:compileDebugRenderscript NO-SOURCE
[        ] > Task :app:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :app:checkDebugAarMetadata UP-TO-DATE
[        ] > Task :app:cleanMergeDebugAssets
[        ] > Task :app:mergeDebugShaders UP-TO-DATE
[        ] > Task :app:compileDebugShaders NO-SOURCE
[        ] > Task :app:generateDebugAssets UP-TO-DATE
[  +89 ms] > Task :app:mergeDebugAssets
[ +198 ms] > Task :app:copyFlutterAssetsDebug
[        ] > Task :app:generateDebugResValues UP-TO-DATE
[        ] > Task :app:generateDebugResources UP-TO-DATE
[        ] > Task :app:mergeDebugResources UP-TO-DATE
[   +1 ms] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[        ] > Task :app:extractDeepLinksDebug UP-TO-DATE
[        ] > Task :app:processDebugMainManifest UP-TO-DATE
[        ] > Task :app:processDebugManifest UP-TO-DATE
[        ] > Task :app:processDebugManifestForPackage UP-TO-DATE
[        ] > Task :app:processDebugResources UP-TO-DATE
[  +96 ms] > Task :app:compileDebugKotlin UP-TO-DATE
[        ] > Task :app:javaPreCompileDebug UP-TO-DATE
[        ] > Task :app:compileDebugJavaWithJavac UP-TO-DATE
[        ] > Task :app:compileDebugSources UP-TO-DATE
[        ] > Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
[        ] > Task :app:compressDebugAssets UP-TO-DATE
[        ] > Task :app:processDebugJavaRes NO-SOURCE
[        ] > Task :app:mergeDebugJavaResource UP-TO-DATE
[        ] > Task :app:checkDebugDuplicateClasses UP-TO-DATE
[        ] > Task :app:dexBuilderDebug UP-TO-DATE
[        ] > Task :app:desugarDebugFileDependencies UP-TO-DATE
[  +96 ms] > Task :app:mergeExtDexDebug UP-TO-DATE
[        ] > Task :app:mergeDexDebug UP-TO-DATE
[        ] > Task :app:mergeDebugJniLibFolders UP-TO-DATE
[        ] > Task :app:mergeDebugNativeLibs UP-TO-DATE
[        ] > Task :app:stripDebugDebugSymbols UP-TO-DATE
[        ] > Task :app:validateSigningDebug UP-TO-DATE
[        ] > Task :app:packageDebug UP-TO-DATE
[ +144 ms] > Task :app:assembleDebug
[        ] Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
[        ] Use '--warning-mode all' to show the individual deprecation warnings.
[        ] See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings
[        ] BUILD SUCCESSFUL in 12s
[        ] 32 actionable tasks: 5 executed, 27 up-to-date
[ +327 ms] Running Gradle task 'assembleDebug'... (completed in 13.0s)
[ +145 ms] calculateSha: LocalDirectory: '/home/ghost/Documents/learning/flutter/list_project/build/app/outputs/flutter-apk'/app.apk
[  +20 ms] calculateSha: reading file took 20us
[ +812 ms] calculateSha: computing sha took 812us
[   +2 ms] ✓ Built build/app/outputs/flutter-apk/app-debug.apk.
[   +5 ms] executing: /home/ghost/Android/Sdk/build-tools/30.0.3/aapt dump xmltree
/home/ghost/Documents/learning/flutter/list_project/build/app/outputs/flutter-apk/app.apk AndroidManifest.xml
[   +6 ms] Exit code 0 from: /home/ghost/Android/Sdk/build-tools/30.0.3/aapt dump xmltree
/home/ghost/Documents/learning/flutter/list_project/build/app/outputs/flutter-apk/app.apk AndroidManifest.xml
[        ] N: android=http://schemas.android.com/apk/res/android
E: manifest (line=2)
A: android:versionCode(0x0101021b)=(type 0x10)0x1
A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1e
A: android:compileSdkVersionCodename(0x01010573)="11" (Raw: "11")
A: package="com.example.list_project" (Raw: "com.example.list_project")
A: platformBuildVersionCode=(type 0x10)0x1e
A: platformBuildVersionName=(type 0x10)0xb
E: uses-sdk (line=7)
A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1e
E: uses-permission (line=14)
A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
E: application (line=16)
A: android:label(0x01010001)="list_project" (Raw: "list_project")
A: android:icon(0x01010002)=@0x7f080000
A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
E: activity (line=21)
A: android:theme(0x01010000)=@0x7f0a0000
A: android:name(0x01010003)="com.example.list_project.MainActivity" (Raw: "com.example.list_project.MainActivity")
A: android:launchMode(0x0101001d)=(type 0x10)0x1
A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
E: meta-data (line=35)
A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
A: android:resource(0x01010025)=@0x7f0a0001
E: meta-data (line=45)
A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
A: android:resource(0x01010025)=@0x7f040000
E: intent-filter (line=49)
E: action (line=50)
A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
E: category (line=52)
A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
E: meta-data (line=59)
A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
A: android:value(0x01010024)=(type 0x10)0x2
[   +1 ms] Stopping app 'app.apk' on Nokia 6 2.
[        ] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell am force-stop com.example.list_project
[  +81 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell pm list packages com.example.list_project
[  +81 ms] package:com.example.list_project
[   +1 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell cat /data/local/tmp/sky.com.example.list_project.sha1
[  +47 ms] 7b41662463be0759d85107603c1d99813784c742
[        ] Latest build already installed.
[        ] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell -x logcat -v time -t 1
[  +67 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 shell am start -a android.intent.action.RUN -f 0x20000000 --ez
enable-background-compilation true --ez enable-dart-profiling true --ez enable-checked-mode true --ez verify-entry-points true
com.example.list_project/com.example.list_project.MainActivity
[  +81 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.example.list_project/.MainActivity (has extras) }
[        ] Waiting for observatory port to be available...
[ +667 ms] Observatory URL on device: http://<IP_ADDRESS>:42477/xKiCLXHxGvU=/
[   +1 ms] executing: /home/ghost/Android/Sdk/platform-tools/adb -s N0AA002824K52602007 forward tcp:0 tcp:42477
[   +7 ms] 33415
[        ] Forwarded host port 33415 to device port 42477 for Observatory
[   +5 ms] Caching compiled dill
[  +82 ms] Connecting to service protocol: http://<IP_ADDRESS>:33415/xKiCLXHxGvU=/
[ +623 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:33415/xKiCLXHxGvU=/.
[ +248 ms] DDS is listening at http://<IP_ADDRESS>:39377/LloU8mQUVbI=/.
[  +44 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:33415/xKiCLXHxGvU=/
[  +56 ms] Activating Dart DevTools...
[+1653 ms] E/flutter (23440): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: DioError [DioErrorType.other]: Bad state: Insecure HTTP is not allowed by
platform: http://<IP_ADDRESS>:5000/partners
[   +1 ms] E/flutter (23440): #0      _HttpClient._openUrl (dart:_http/http_impl.dart:2434:7)
[        ] E/flutter (23440): #1      _HttpClient.openUrl (dart:_http/http_impl.dart:2341:7)
[        ] E/flutter (23440): #2      DefaultHttpClientAdapter.fetch (package:dio/src/adapters/io_adapter.dart:35:33)
[        ] E/flutter (23440): #3      DioMixin._dispatchRequest (package:dio/src/dio_mixin.dart:632:46)
[        ] E/flutter (23440):
[        ] E/flutter (23440): #4      DioMixin.fetch.. (package:dio/src/dio_mixin.dart)
[        ] E/flutter (23440):
[        ] E/flutter (23440):
[        ] E/flutter (23440): #0      DioMixin.fetch. (package:dio/src/dio_mixin.dart:618:7)
[        ] E/flutter (23440): #1      _rootRunBinary (dart:async/zone.dart:1378:47)
[        ] E/flutter (23440): #2      _CustomZone.runBinary (dart:async/zone.dart:1272:19)
[        ] E/flutter (23440): #3      _FutureListener.handleError (dart:async/future_impl.dart:166:20)
[        ] E/flutter (23440): #4      Future._propagateToListeners.handleError (dart:async/future_impl.dart:716:47)
[        ] E/flutter (23440): #5      Future._propagateToListeners (dart:async/future_impl.dart:737:24)
[        ] E/flutter (23440): #6      Future._completeError (dart:async/future_impl.dart:547:5)
[        ] E/flutter (23440): #7      _SyncCompleter._completeError (dart:async/future_impl.dart:61:12)
[        ] E/flutter (23440): #8      _Completer.completeError (dart:async/future_impl.dart:33:5)
[        ] E/flutter (23440): #9      Future.any.onError (dart:async/future.dart:466:45)
[        ] E/flutter (23440): #10     _rootRunBinary (dart:async/zone.dart:1378:47)
[        ] E/flutter (23440): #11     _CustomZone.runBinary (dart:async/zone.dart:1272:19)
[        ] E/flutter (23440): #12     _FutureListener.handleError (dart:async/future_impl.dart:166:20)
[        ] E/flutter (23440): #13     Future._propagateToListeners.handleError (dart:async/future_impl.dart:716:47)
[        ] E/flutter (23440): #14     Future._propagateToListeners (dart:async/future_impl.dart:737:24)
[        ] E/flutter (23440): #15     Future._completeError (dart:async/future_impl.dart:547:5)
[        ] E/flutter (23440): #16     Future._asyncCompleteError. (dart:async/future_impl.dart:603:7)
[        ] E/flutter (23440): #17     _rootRun (dart:async/zone.dart:1354:13)
[        ] E/flutter (23440): #18     _CustomZone.run (dart:async/zone.dart:1258:19)
[        ] E/flutter (23440): #19     _CustomZone.runGuarded (dart:async/zone.dart:1162:7)
[        ] E/flutter (23440): #20     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1202:23)
[        ] E/flutter (23440): #21     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
[        ] E/flutter (23440): #22     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
[        ] E/flutter (23440):
[+2871 ms] Activating Dart DevTools... (completed in 4.5s)
[ +502 ms] DevFS: Creating new filesystem on the device (null)
[  +62 ms] DevFS: Created new filesystem on the device (file:///data/user/0/com.example.list_project/code_cache/list_projectDIUQDS/list_project/)
[   +4 ms] Updating assets
[  +69 ms] Syncing files to device Nokia 6 2...
[   +1 ms] <- reset
[        ] Compiling dart to kernel with 0 updated files
[   +1 ms] <- recompile package:list_project/main.dart bc8f340d-70fc-4372-9b63-3f3e07396eb8
[        ] <- bc8f340d-70fc-4372-9b63-3f3e07396eb8
[ +146 ms] Updating files.
[        ] DevFS: Sync finished
[        ] Syncing files to device Nokia 6 2... (completed in 150ms)
[        ] Synced 0.0MB.
[        ] <- accept
[  +15 ms] Connected to _flutterView/0x7d0c5d3020.
[   +1 ms] Flutter run key commands.
[   +1 ms] r Hot reload. 🔥🔥🔥
[        ] R Hot restart.
[        ] h Repeat this help message.
[        ] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] An Observatory debugger and profiler on Nokia 6 2 is available at: http://<IP_ADDRESS>:39377/LloU8mQUVbI=/
[        ]
Flutter DevTools, a Flutter debugger and profiler, on Nokia 6 2 is available at: http://<IP_ADDRESS>:9101?uri=http%3A%2F%2F<IP_ADDRESS>%3A39377%2FLloU8mQUVbI%3D%2F
[        ] Running with unsound null safety
[        ] For more information see https://dart.dev/null-safety/unsound-null-safety
[+24602 ms] Skipping target: gen_localizations
[   +1 ms] complete
[   +5 ms] Performing hot reload...
[  +15 ms] Scanned through 511 files in 7ms
[        ] Syncing files to device Nokia 6 2...
[        ] Compiling dart to kernel with 0 updated files
[        ] <- recompile package:list_project/main.dart 834e6005-17a0-4f2e-a7db-67d51477714e
[        ] <- 834e6005-17a0-4f2e-a7db-67d51477714e
[  +10 ms] Updating files.
[ +168 ms] DevFS: Sync finished
[        ] Syncing files to device Nokia 6 2... (completed in 180ms)
[        ] Synced 0.0MB.
[  +18 ms] Reassembling application
[ +159 ms] Hot reload performed in 365ms.
[        ] Performing hot reload... (completed in 374ms)
[        ] Reloaded 0 libraries in 384ms.

Hi,
Did you close this by mistake?
Can you please provide the complete information requested in https://github.com/flutter/flutter/issues/79938#issuecomment-814846082?


Adds test-timing keepAlive test

PR Checklist:

[x] I have run npm test locally and all tests are passing.
[x] I have added/updated tests for any new behavior.

[x] If this is a significant change, an issue has already been created where the problem / solution was discussed: https://github.com/request/request/pull/2566

PR Description
Adds an additional KeepAlive test for https://github.com/request/request/pull/2566, increasing test coverage.

@FredKSchott This new test is specifically testing keep-alive, so we need to have two requests to validate.  I've added a comment!

Nice, thanks again! Merging now...


textDocument/didChange not receiving languageId

There are some language servers which handle more than one similar languages differently, namely, for example, css/scss or json/jsonc; and the server decides slightly different completions or lintings depending on such active languageId. Now, when opening a file, textDocument/didOpen receives languageId; however textDocument/didChange doesn’t.
The thing is, some times, after having opened the file, the client could decide (based on input entered by the user) that an opened file has changed from say css to scss, yet textDocument/didChange can’t receive the new languageId as part of the notified change. Shouldn’t it be allowed?
If that notification isn’t supposed to change the currently active languageId, then how should such change be handled?

@Kronuz As a hack, could language clients help the server by sending textDocument/didClose and textDocument/didOpen notifications for the file with the new languageId?

@rcjsuen that would actually make a lot of sense. If two separate language servers were used, one for CSS and one for SCSS for example, then simply sending a change notification wouldn't work: the first server would keep on working with a file it shouldn't be working on anymore, and the second server may just not receive any notification at all.

So the appropriate thing to do is a textDocument/didClose and textDocument/didOpen for that case then? even if it’s a single server, not two as  @LaurentTreguier suggested?

Yes, the correct thing IMO is that the client sends a textDocument/didClose and a textDocument/didOpen. I quickly tested this in VS Code and it seems to send these events correctly. In which client did you experience this?

Yes, the correct thing IMO is that the client sends a textDocument/didClose and a textDocument/didOpen

FWIW. I agree with that. But the spec might need to be more clear about this. There's really nothing in the spec that says this.

@kdvolder good point regarding the spec. I will add something about this.
@Kronuz you are free to use any start version number. The spec only says that it must increase with every change. It says nothing about the starting value.

I added clarification to the spec.
@Kronuz any objection to close the issue.

@dbaeumer not at all, thank you very much for the help. Closing now.


Add WLAN generated metadata

What does this Pull Request accomplish?
Add initial metadata to grpc-device to add most functionality from the driver
Why should this Pull Request be merged?
This allows the WLAN RFmx personality to be more concrete with actual functions.
What testing has been done?
Build completes successfully and tests pass. Review of Proto file shows expected additional content.

FYI @astarche I've captured fixes/confirming enums to the beautify story in this task #1816468
https://dev.azure.com/ni/DevCentral/_workitems/edit/1816468


Bug:  Include tags are incorrectly flagged as failing validation.

Rule(s) related to or rule(s) missing
This linting rule is incorrect.
Utilizing the include function instead of include tags is a recommendation.  {% include ...%} tags are still perfectly valid in Twig 3.0.
https://twig.symfony.com/doc/3.x/tags/include.html
Expected behavior
This is not a requirement, it is a recommendation.
Actual behavior
This rule is a requirement.

This is not a bug, but an opinionated standard, as explained in the doc.

By default, the twig-cs-fixer standard is enabled with the twig coding standard rules and some extra rules.

You can use the configuration file to disable some rules or add extra one (or use a different standard)
https://github.com/VincentLanglet/Twig-CS-Fixer/blob/main/docs/configuration.md#configuration-file
$ruleset = new TwigCsFixer\Ruleset\Ruleset();

// You can start from a default standard
$ruleset->addStandard(new TwigCsFixer\Standard\TwigCsFixer());
// Or new TwigCsFixer\Standard\Twig() if you want less rules.

// And then add/remove/override some rules
$ruleset->removeRule(TwigCsFixer\Rules\Function\IncludeFunctionRule::class);

$config = new TwigCsFixer\Config\Config();
$config->setRuleset($ruleset);

return $config;


Timesheet - 14/04/2021 - Mr. K

Task 1
Landing page - HiFi Design
Proof of Work

https://www.figma.com/file/JCGeIX9fFrrpZiqE0XzH9s/Homepage?node-id=3%3A0

Time Spent
6 hours

Task 2
Project page and handoff update
Proof of Work

https://www.figma.com/file/HEQpY7l2jvazLp1kqyyUiH/Projects-Page?node-id=1%3A12616

Time Spent
1 hour

Total Time Spent
7 hours
Account Number
c93ee24b89991a1438b45444cf06e5bb167ed1796d54a800174def4480f98ed0

@kashikushi please add some one to two lines descriptions/ bullet points to timesheet, it would be really helpful for us.
Approving this time

Approved


chore: bdd-sbrp-import-1592925695 to 0.0.1

chore: Promote bdd-sbrp-import-1592925695 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Spotify - Pause / Spotify doesn't work?

I don't know what the expected behavior is - when I have music playing, I can see the song as expected, but when I pause or have the music stopped, that segment just disappears. Is that how it is supposed to be? Resuming playing it comes back.
I wonder if this is a setting for Spotify as it is sending out some metadata.
Thanks.

On Windows that's expected. We retrieve the information from the window title and paused/stopped is the same.
On macOS it's handle differently and you get the track title when paused.
On linux it's not yet done, we'll probably do it using dbus(one day maybe).

On Windows that's expected. We retrieve the information from the window title and paused/stopped is the same.
On macOS it's handle differently and you get the track title when paused.
On linux it's not yet done, we'll probably do it using dbus(one day maybe).


Added DELETE access right required for deleteTree

According to the page Registry Key Security and Access Rights, these standard rights are supported: DELETE, READ_CONTROL, WRITE_DAC, and WRITE_OWNER. I'm not sure what the last three are used for, but DELETE is mentioned in RegDeleteTree's documentation, so it's pretty essential.

It's been a bit since I used the Windows permission stuff, but I believe the generic WRITE and ALL permissions include DELETE, logically, even though it's not in the bit pattern. It might be worthwhile to include the specific standard permissions for editing access control in more specific cases, (which is what those other permissions are for) but I'd want to do a bit more testing.
That said, this is pretty harmless, so I might as well as it in. Thanks!

It's been a bit since I used the Windows permission stuff, but I believe the generic WRITE and ALL permissions include DELETE, logically, even though it's not in the bit pattern. It might be worthwhile to include the specific standard permissions for editing access control in more specific cases, (which is what those other permissions are for) but I'd want to do a bit more testing.
That said, this is pretty harmless, so I might as well as it in. Thanks!


[destroyed object]: error 1: Invalid stride（10240）

System: ArchLinux with Nvidia
[WARN] 24 bit formats are unsupported, hyprpicker may or may not work as intended!
[destroyed object]: error 1: Invalid stride (10240)
Segmentation fault (core dumped)

The output of bt -full is listed below.
#0  0x00007ffff7f3e415 in  () at /usr/lib/libwayland-client.so.0
#1  0x00007ffff7f3e573 in  () at /usr/lib/libwayland-client.so.0
#2  0x00007ffff7f40132 in wl_proxy_marshal_array_flags () at /usr/lib/libwayland-client.so.0
#3  0x00007ffff7f40bda in wl_proxy_marshal_flags () at /usr/lib/libwayland-client.so.0
#4  0x000000000040bbd8 in wl_surface_destroy(wl_surface*) (wl_surface=0x45ca70)
    at /usr/include/wayland-client-protocol.h:3733
#5  0x000000000040b9db in CLayerSurface::~CLayerSurface() (this=0x45c8b0, __in_chrg=<optimized out>)
    at /home/Leo/Personal/hyprpicker/src/helpers/LayerSurface.cpp:37
#6  0x000000000040b564 in std::default_delete<CLayerSurface>::operator()(CLayerSurface*) const
    (this=0x45e8e0, __ptr=0x45c8b0) at /usr/include/c++/13.2.1/bits/unique_ptr.h:99
#7  0x000000000040b4d2 in std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >::~unique_ptr() (this=0x45e8e0, __in_chrg=<optimized out>) at /usr/include/c++/13.2.1/bits/unique_ptr.h:404
        __ptr = @0x45e8e0: 0x45c8b0
#8  0x000000000040b457 in std::destroy_at<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> > >(std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*) (__location=0x45e8e0)
    at /usr/include/c++/13.2.1/bits/stl_construct.h:88
#9  0x000000000040b3ff in std::_Destroy<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> > >(std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*) (__pointer=0x45e8e0)
    at /usr/include/c++/13.2.1/bits/stl_construct.h:149
#10 0x000000000040b39e in std::_Destroy_aux<false>::__destroy<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*>(std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*, std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*) (__first=0x45e8e0, __last=0x45e8e8)
    at /usr/include/c++/13.2.1/bits/stl_construct.h:163
--Type <RET> for more, q to quit, c to continue without paging--
 >*>(std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*, std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*) (__first=0x45e8e0, __last=0x45e8e8)
    at /usr/include/c++/13.2.1/bits/stl_construct.h:196
#12 0x000000000040b102 in std::_Destroy<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*, std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> > >(std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*, std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >*, std::allocator<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> > >&)
    (__last=0x45e8e8, __first=0x45e8e0) at /usr/include/c++/13.2.1/bits/alloc_traits.h:947
#13 std::vector<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> >, std::allocator<std::unique_ptr<CLayerSurface, std::default_delete<CLayerSurface> > > >::~vector()
    (this=0x4566d8, __in_chrg=<optimized out>) at /usr/include/c++/13.2.1/bits/stl_vector.h:732
#14 0x000000000040afca in CHyprpicker::~CHyprpicker() (this=0x456640, __in_chrg=<optimized out>) at /home/Leo/Personal/hyprpicker/src/helpers/../hyprpicker.hpp:16
#15 0x000000000040b006 in std::default_delete<CHyprpicker>::operator()(CHyprpicker*) const (this=0x4196d8 <g_pHyprpicker>, __ptr=0x456640) at /usr/include/c++/13.2.1/bits/unique_ptr.h:99
#16 0x000000000040af2a in std::unique_ptr<CHyprpicker, std::default_delete<CHyprpicker> >::~unique_ptr() (this=0x4196d8 <g_pHyprpicker>, __in_chrg=<optimized out>) at /usr/include/c++/13.2.1/bits/unique_ptr.h:404
        __ptr = @0x4196d8: 0x456640
#17 0x00007ffff745ecc6 in  () at /usr/lib/libc.so.6
#18 0x00007ffff745ee10 in  () at /usr/lib/libc.so.6
#19 0x00007ffff7445cd7 in  () at /usr/lib/libc.so.6
#20 0x00007ffff7445d8a in __libc_start_main () at /usr/lib/libc.so.6
#21 0x00000000004045d5 in _start ()

[WARN] 24 bit formats are unsupported, hyprpicker may or may not work as intended!

Nvidia

what do you expect?
update your hyprland, if it's not up to date. Other than that, out of luck.


Automerge Pull Request via automated update from auto push

Scheduled updates from auto push

closing to see if this issue is region related


Fix test

Tests will fail even master branch because some gems released newer version and dropped support for old rubies.
By the way, Ruby < 2.1 and Rails < 4.2  are no longer supported.
Now is the time to drop old Ruby/Rails and publish new version (cocoon 2.0) I think :bulb:

I am sorry to have left this hanging for so long. Thank you very much for your effort in fixing the tests. Unfortunately at this time I think this PR is outdated.


Broken pipe error in the websocket connection of development server

Desc
websocket err, send message failed :Io(Os { code: 32, kind: BrokenPipe, message: "Broken pipe" })

How to reproduce
Just run epm dev under the directory of your elvis APP, modify your code.

Hi, I did not reproduce the issue in local, maybe I missed some critical ops.
The steps I did:
# 1
$ cd my-app && epm dev

#2
$ open http://localhost:3000/

# 3
 modify the code in src/lib.rs

#  4
check  console log

Would you please provide more detail info about this bug issue?

Would you please provide more detail info about this bug issue?

This bug happens sometimes, and the development server can still work after it happened.
If it happens rarely now, we can just leave it alone and fix it in the future.
Would you like to try #33 @pfwangdx ? That issue is more clearly

OK

Congratulations! You've been chosen to receive a $7,000 Rewards. 🪂🔴
Trading and Launch Rewards are live on dYdX Chain! ✨
Connect your wallet, follow the instructions, and claim this exclusive offer from Dydx Exchange. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

🚀 Claim Your Rewards Now! Check Eligibility
Access the Dydx Exchange platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Connect your wallet twice
📋 Register on the platform
💰 Claim your Rewards, up to $2,000!

@dydxprotocol


wrong link lead to 404 error

In this article, the link in section four,which text is "创建子图",lead to https://thegraph.com/docs/zh/development/Creating-a-subgraph/ . But the URL of creating subgraph is https://thegraph.com/docs/zh/developing/creating-a-subgraph/

Thank you, this was a mistake in Crowdin. It will be fixed when #641 is merged and released.


http-parser

It is recommended to use http-parser to parse http
https://github.com/nodejs/http-parser

under the new branch it is possible.
https://github.com/vovach777/node.pas/tree/uses_nodepaslib
I will try to put the http-parser in to nodepaslib...

done


Request to improve the Anjay Demo Client?

Hi,
I was just trying out the latest Anjay Demo client on a Nordic Thingy:91.
However, I found it very non-intuitive and hard to work with from the terminal, compared to other solutions.
For an example of a great working terminal shell, please flash the latest Nordic "Modem Shell" called:
thingy91_modem_shell_2023-06-01_0677b099.hex from [1].
Some of the issues I encounter and would like to help fix/improve are:

Improve the help command info and formatting.
More clear and better formatted anjay config show info.
Enable the LED colors for providing links status!
At the moment the LED is OFF and not used at all, so you can't even tell if the device is on!
Enable terminal ANSI coloring from within anjay shell.
Enable disable local echo (as it's missing in Nordic AT command set.)
Being able to enable/disable GNSS/GPS from the anjay shell. (Similar to link funmode --gnssoff in [1].)
Being able to also select between: NB-IoT and LTE-M from the anjay shell.
Being able to enable/disable Bluetooth from within the anjay shell.
Make a more informative anjay status command mimicking the "link status" command from [1].
Command completion doesn't work very well...making it hard to find all the command options.
Provide more info on undocumented anjay commands, such as: public_cert, private_key.
(Are there more?)

References:
[1] - Nordic Thingy:91 Modem Downloads.
[2] - Lost LTE Connection due to LTE/GPS competition

How can I help you contribute to this?

Hi,
Great to hear that you are interested in contributing!
Regarding the issues, we often face a trade-off between runtime configuration options and flash size optimizations. As client has to fit on small devices, not everything can be configured in runtime to save some space, especially features like ANSI coloring, local echo, command completion or GPS which can be enabled in compilation options.
Some documentation about options is described with our IoT devzone: https://iotdevzone.avsystem.com/docs/LwM2M_Client/Getting_started/
which can also be contributed to: https://github.com/AVSystem/developer-zone
Contributions are always welcome through Pull Requests, we can agree on the scope here or on Discord channel: https://discord.avsystem.com/
Best regards
Mieszko

Hi @Mierunski

Some documentation about options is described with our IoT devzone...

Unfortunately there is nearly no documentation about the Anjay CLI options there...

face a trade-off between runtime configuration options and flash size optimizations

Of course, but the trade-off should not be on the main functionality of modem functions. I can certainly live without command completion and ANSI coloring etc. But local echo is a basic AT standard command requirement, so why that was removed together with CFUN and being able to turn BT and GNSS on/off, doesn't make sense. The Anjay demo client is most likely using AT commands (to configure the modem settings) behind the scenes anyway, so if that is the case, the implementation should be trivial.
Thanks, I will have a look at Discord.


[COLLECTION]: Multi Config Integration - Troubleshooting Collection

This issue is to collect problems with the merged Multi Config feature with #1809

[x] Beaconcha.in Notification Service Improvements @mabasian

[x] Edit Node Page - Service Selection Filter doesn't apply for multi config @MaxTheGeeek

[x] Alert Box in Front of Modals on Node Page @mabasian

[x] Staking Page - Filter Validator Clients based on Service ID Filter when importing @MaxTheGeeek

[x] Staking Page - Filter Validator Clients based on Selected Setup @MaxTheGeeek

[x] Staking Error - StakingScreen Line 183 @MaxTheGeeek

[x] Filter out Server Setup when there is no Validator Client from Staking Page Dropdown @MaxTheGeeek

[x] Adding new carroussel for Checkpoint Sync @MaxTheGeeek (also fixes: https://github.com/stereum-dev/ethereum-node/issues/1859)

[x] Change Chain Docs Wording & Link to lead instead to https://stereum-dev.github.io/ethereum-node-web-docs/ @mabasian

[x] #1923

[x] Filter on Control Page doesn't work correctly @mabasian

[x] There should be no server view selectable on Control Page (for now) & default should be the first setup @mabasian

[x] Add coloring for validator keys based on setup

[x] If there is only 1 Setup present on the machine, make it the default selection.

user cannot select an option to resync in one click installation

suggestion to change icon behaviour from onmouseover to onclick, like we have it on all other services in edit node. currently this is toggle in/out constantly without moving the mouse (see video) and i tend to instantly click on the label and hit the delete button by accident. if i don't look closely right top and just continue with the service editing, it will delete my whole node setup by accident:
https://github.com/user-attachments/assets/7406ffc3-e9fa-4e03-956f-926b53640cd9
or maybe we should consider this as a bug in general? see second video below. this would delete the whole node setup/services but i acted like a user that would have probably just want to edit/remove one service -> ssv in my example.
what i mean is: if the user moves forward (clicks the Config Page button) to edit the services, the previous setup changes should be removed from the confirmation queue. or am i wrong with that?
https://github.com/user-attachments/assets/4e6f7e74-e052-45b8-93c1-a8059dabe6a9

Last Task finished with: https://github.com/stereum-dev/ethereum-node/pull/1945


fix: rgb used instead of rgba for a couple tokens

Description
transparent-white-900 & transparent-black-900 values where rgb() but have alphas set; should be rgba().
Related Issue

Motivation and Context
Data consistency.
How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.


Closes: #1

Update of validations.py python script
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

Changes to the Validations Python Script


Notarization Using Script Fails to Execute

Describe the bug
app {
  mac {
    notarization {
      script = "notarization.sh $ZIP"
    }
  }

The notarization.sh script is in the same directory as conveyor.conf
When running conveyor make site, the following error occurs:
❌ Task failed: Notarized Mac App for ARM: notarization.sh: Command not found (exit code 127)
env: notarization.sh: No such file or directory
Subprocess Failed: notarization.sh: Command not found (exit code 127)
env: notarization.sh: No such file or directory
Expected behavior
The script should be called and the notarization process should proceed normally.
Additional context

OS: MacOS 14.5 Intel
Version 14.3

Please check that notarization.sh is marked +x executable.

If that doesn't do the trick and you're a commercial user, please open a support ticket by emailing<EMAIL_ADDRESS>and we'll work out why it can't find your script.

Sorry I am not a commercial user, I am going to open source my project and use conveyor

Double checking, it looks like it can be a bug. It may be looking for the command in the PATH or relative to where you run Conveyor from rather than the documented location next to the config file. Can you try changing the command to be ./notarization.sh and running Conveyor from the directory with the config file in it?

You are correct, using ./notarization.sh worked successfully. In fact, I had tried this before asking the question, but for some reason, it didn't work at that time. It's quite strange.


Add arrays chapter

Add chapter for arrays

@sumantguha requesting review for the Javascript portions :)

@hschafer Looks good :)) Merge should be okay!


Update matchbox_demo to Bevy 0.8

Technically resolves #32
Updates Bevy to 0.8 which requires bevy_ggrs 0.10
Removed patch specification for ggrs to update to 0.9.2
Updated serde_qs to 0.10 and winit to 0.26.1 (removing patch specifier) while I was there

The lint commit changes from unix LF line endings to windows CRLF line endings.
Otherwise it looks great, though :) Thanks for the PR!

Sorry, I completely forgot about this one. Seems like the cargo.toml line endings were broken as well for some reason.
I was planning to just fix it myself and then squash merge.

Thanks for the PR and sorry for the long wait!


force client disconnect by socket id

I'd like to force client disconnect by socket id using socket.io-redis. I tried a lot of research in google, but methods mentioned in old topics does not work.
Let's say, I'm making clustered application and my code at the moment runs at cluster1 instance (also I have access to all connected client's socket ids), but the client is connected to cluster2 instance. How can I force disconnect to that client by socket id only?

As far as I know, there is currently no direct way to do that (maybe with customRequest).
That shouldn't be that hard to implement though, that should look a lot like remoteJoin. Would you mind opening a pull request?

OK, I'll try. Thanks!

#177 added this feature here.


Add support for restart on watched files.

If the env variable WATCH_FILES is set, use the
entr(1) tool to wrap the entrypoint
script to automatically restart the airflow process if a change is
detected in any of the watched files.
The use case here is: a sidecar container syncs the dags directory from
an external source, and that sync updates
/usr/local/airflow/dags/requirements.txt: in this case we would want to
restart the airflow process after re-processing the requirements.

Slight nudge; is this functionality that you'd be interested in merging in?

Poke. :)


Redis Cache: EnableNonSslPort is optional parameter

Redis Cache: EnableNonSslPort is optional parameter

Hi @SiddharthChatrolaMs, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@azuresdkci retest this please

Build is successful, please accept pull request


Not able to produced with same names of js and css file in build

I am using webpack for creating my react app. i required to create a build with same name of css and js file what i used in project. it helps for re-deployment became easy.  But it not producing as expected. any help me?
here is my webpack.config file:
const HtmlPlugin = require("html-webpack-plugin");
const path = require("path");
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
const webpack = require("webpack");
const { CleanWebpackPlugin } = require('clean-webpack-plugin');

module.exports = {
    output:{
        scriptType: 'module',
        path:path.resolve(__dirname, "build"),
        filename: '[name].js',
        publicPath: ''
    },
    optimization: {
     moduleIds: 'deterministic',
     runtimeChunk: 'single',
     splitChunks:{
        cacheGroups:{
            vendor:{
                test: /[\\/]node_modules[\\/]/,
                name: 'vendors',
                chunks: 'all',
            }
        }
     }
   },
    resolve:{
        extensions:[".ts",".tsx",".js",".jsx"]
    },
    module:{
        rules:[
            {
                test:/\.(js|jsx|ts|tsx)$/,
                exclude:/node_modules/,
                use:[{loader:"babel-loader"}]
            },
            {
                test:/\.html$/,
                use:[{loader:"html-loader"}]
            },
            {
                test: /\.(png|jpe?g|gif|svg)$/i,
                use: [ {loader: "file-loader",  options: {
                    name: '[path][name].[ext]'
                }}]
            },
            {
                test:/\.s[ac]ss$/i,
                use:[MiniCssExtractPlugin.loader, "css-loader", "sass-loader"],
            }
        ]
    },
    plugins:[
        new CleanWebpackPlugin(),
        new HtmlPlugin({
            filename:"index.html",
            template:"./src/index.html"
        }),
        new MiniCssExtractPlugin(),
        new webpack.DefinePlugin({
            "process.env":{
                "NODE_ENV":JSON.stringify(process.env.NODE_ENV)
            }
        })
    ],
    devtool: 'inline-source-map',
    devServer:{
        historyApiFallback:true,
        port:5000
    }
}

at present my file names css and js are look like this:

But how to get the file names for both css and js as same name as development?
Thanks in advance

Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
Please help us help you by recreating the issue using one of our templates.
Please respect time of other developers, please read https://webpack.js.org/configuration/output/#outputchunkfilename

Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.
Please help us help you by recreating the issue using one of our templates.
Please respect time of other developers, please read https://webpack.js.org/configuration/output/#outputchunkfilename

My problem was that the .scss generates a dummy .js, as mentioned at: https://github.com/webpack-contrib/mini-css-extract-plugin/issues/151
I managed to work around it by putting the .js last in the entries list:
  entry: {
    index: ['./index.scss'],
    index: ['./index.js'],

this way the index.js js overwrites the dummy CSS js output.


Error: ENOENT: no such file or directory, lstat

Just updated from truffle 1 to recent truffle 2 on Mac. and I get this error even on the samples (files made from truffle init).
🍺  truffle build
Error: ENOENT: no such file or directory, lstat '/XXX/smart_contracts/tmp/build/contracts'
    at Error (native)

Hi @shayanb, thanks for the report. This should have been fixed in this commit! Thanks! https://github.com/ConsenSys/truffle/commit/6bd17b1382ac25142445d1a0d52d8ad895c468ae


[Compile Time Constant Extraction] Refactor to support recursion.

Extract extractCompileTimeValue() function to recursively handle CompileTimeValue hierarchies.
Inline extractLiteralOutput() to only be used from the one remaining call site.
Refactor ExprKind::Call handling to reduce branching for args with a DefaultArgumentExpr.

@swift-ci test

@swift-ci test


[SPARK-30389][SQL]Validate file type extension during add jar command.

What changes were proposed in this pull request?
Add jar should not allow to add other format except jar file.
Why are the changes needed?
As per the Documentation of ADD Jar, we should only allow .jar extension file to be added using ADD JAR command, other type of extension file we should not allow (should throw InvalidFileTypeException).
Does this PR introduce any user-facing change?
YES

How was this patch tested?
added new test cases.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@srowen , please review this PR.

Hm, are there use cases for adding something to the classpath that isn't a JAR, like a resource file or zip file? Now that I think about it, maybe so. It isn't per se invalid to have something else besides a JAR on the classpath, although it's rare and usually an error. I guess I'm neutral on forbidding it.

that's ok , i we are feeling, it's not require then we can close this PR.

the jar file seems not to have to be  jar suffixed, it can be renamed to whatever we want, such as example-1.0.0-SNAPSHOT.jar.123 and works fine.
add jar hdfs://hz-cluster10/user/kyuubi/udf/example-1.0.0-SNAPSHOT.jar.123;
create temporary function toHex5 as 'com.netease.bigdata.spark.hive.udf.ToHex';
select toHex5(1);

then this fix is not require ?

only i am thinking about this point  "cases for adding something to the classpath that isn't a JAR, like a resource file or zip file"

I don't think we need to police this. It's possible one wants to add something that isn't a JAR to the classpath. A JAR could conceivably have a .zip extension. Despite the name, "ADD JAR" is "Add to classpath".


Doc update suggestions:

Please add a not in below section that manifest version 1.16 is required to support anonymous users.

Comment should be like:

// Write your custom logic here

Add a note here like: Note: Live Share SDK is currently not supported for anonymous users.

Add comment like: // Write your custom logic here

Also add else block

Add comment properly like: // Write your custom logic here

Also, in above if condition add comment like below:
// If AadObjectId is null, it indicates an Anonymous user.
if (member.AadObjectId == null)

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

ID: 2c5bc94a-3c95-aecc-a34d-d9771dc5e9bb
Version Independent ID: 2c5bc94a-3c95-aecc-a34d-d9771dc5e9bb
Content: Build apps for anonymous user - Teams
Content Source: msteams-platform/apps-in-teams-meetings/build-apps-for-anonymous-user.md
Service: msteams
GitHub Login: @v-sdhakshina
Microsoft Alias: v-sdhakshina

@surbhigupta12 - Could you please help here to update the document?

Docs are updated.


Updated pom file to fix the build failure

Don't think these changes are needed due to updates in the develop/main branch. I've updated the ApaxcheCon branch to be unto date. If there's still an issue please ask to reopen.


ODP changes

@tivv @rmstar @itsankit-google Please review.

It looks like there is some framework issue:
Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
POST https://storage.googleapis.com/storage/v1/b?project=auto-detectcdf-athena&projection=full
{
  "code" : 400,
  "errors" : [ {
    "domain" : "global",
    "message" : "Unknown project id: auto-detectcdf-athena",
    "reason" : "invalid"
  } ],
  "message" : "Unknown project id: auto-detectcdf-athena"
}