9.0 Stage 2 Builds Failing in fsharp with error FS0064

Link to failues (internal Microsoft link)
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,36): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_codeopt has been constrained to be type 'Code'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,36): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_codeopt has been constrained to be type 'Code'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,46): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Macros has been constrained to be type 'Macro list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,46): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Macros has been constrained to be type 'Macro list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,55): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Rules has been constrained to be type 'Rule list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,55): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Rules has been constrained to be type 'Rule list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(36,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_macro has been constrained to be type 'Macro'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(36,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_macro has been constrained to be type 'Macro'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(41,31): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_regexp has been constrained to be type 'Regexp'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(41,31): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_regexp has been constrained to be type 'Regexp'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(46,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_rule has been constrained to be type 'Rule'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(46,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_rule has been constrained to be type 'Rule'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,30): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_args has been constrained to be type 'RuleArgument list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,30): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_args has been constrained to be type 'RuleArgument list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,33): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clauses has been constrained to be type 'Clause list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,33): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clauses has been constrained to be type 'Clause list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fs(411,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_optbar has been constrained to be type 'unit'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fs(411,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_optbar has been constrained to be type 'unit'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(65,44): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clause has been constrained to be type 'Clause'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(65,44): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clause has been constrained to be type 'Clause'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(84,78): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_charset has been constrained to be type ''a -> 'b'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(84,78): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_charset has been constrained to be type ''a -> 'b'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fs(260,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype__startspec has been constrained to be type 'obj'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fs(260,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype__startspec has been constrained to be type 'obj'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]

@dotnet/fsharp - can you please take a look?

Feel free to put ignore for this error when builds (we have it as warning). Not yet sure what caused it.

Had a discussion with @KevinRansom about this issue - it's likely related to this line  from https://github.com/dotnet/fsharp/pull/17649. The fsharp team is investigating.

fsharp team confirmed that they think there's a bug to fix. I'll make the change to disable the warnings on our end and close this issue with that PR. I'm also going to link the PR to the issue in the fsharp repo so that we can remove the ignore once the fsharp team has a fix for the bug.

The Stage 2 builds of 9.0.1xx-rc2 (internal Microsoft link) also failed with the same issue:
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,36): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_codeopt has been constrained to be type 'Code'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,36): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_codeopt has been constrained to be type 'Code'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,46): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Macros has been constrained to be type 'Macro list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,46): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Macros has been constrained to be type 'Macro list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,55): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Rules has been constrained to be type 'Rule list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(26,55): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_Rules has been constrained to be type 'Rule list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(36,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_macro has been constrained to be type 'Macro'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(36,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_macro has been constrained to be type 'Macro'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(41,31): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_regexp has been constrained to be type 'Regexp'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(41,31): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_regexp has been constrained to be type 'Regexp'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(46,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_rule has been constrained to be type 'Rule'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(46,26): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_rule has been constrained to be type 'Rule'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,30): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_args has been constrained to be type 'RuleArgument list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,30): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_args has been constrained to be type 'RuleArgument list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,33): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clauses has been constrained to be type 'Clause list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(52,33): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clauses has been constrained to be type 'Clause list'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fs(411,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_optbar has been constrained to be type 'unit'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fs(411,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_optbar has been constrained to be type 'unit'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(65,44): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clause has been constrained to be type 'Clause'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(65,44): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_clause has been constrained to be type 'Clause'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(84,78): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_charset has been constrained to be type ''a -> 'b'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fsy(84,78): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype_charset has been constrained to be type ''a -> 'b'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]
  /vmr/src/fsharp/buildtools/fslex/fslexpars.fs(260,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype__startspec has been constrained to be type 'obj'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj] [/vmr/artifacts/source-built-sdks/Microsoft.DotNet.Arcade.Sdk/tools/Build.proj]
##[error]/vmr/src/fsharp/buildtools/fslex/fslexpars.fs(260,20): error FS0064: This construct causes code to be less generic than indicated by the type annotations. The type variable 'gentype__startspec has been constrained to be type 'obj'. [/vmr/src/fsharp/buildtools/fslex/fslex.fsproj]

I think sdk workaround wasn't merged yet

I opened a backport PR - https://github.com/dotnet/sdk/pull/43548


feature fs - agent mkdir

Currently, configuring
{
  "feature": {
    "fs": {
      "read_write": "^/mnt/data/.*"
    }
  }
}

will only successfully create "ordinary" file entries in the remote filesystem. If the executable running in mirrord tries to create a directory the remote filesystem the mkdir call will actually be called locally.
The current behaviour is quite confusing, as xstat calls are forwarded to the agent (checking if directory exists) but actual mkdir call is done locally.

Yeah this has hit me before too, good to see an issue raised.

Yeah this has hit me too, good to see an issue raised. BTW, rmdir also has the same confusing behaviour.
please consider to support too: feature fs - agent rmdir


Consider moving custom Json encoding/decoding to xtp-python-bindgen

It might be getting to specific to live in the PDK, we should consider moving the custom Json encoder into the bindgen repo if possible.

Ben and I discussed and we think we want to move forward with this to make it more similar to other bindgens.


Integrals in plot/export function

There should be a way to define that integral values are also printed in the export graph. Currently, only the integral trail can be seen, but students would like to have a number (below the axis, e.g. ) that tells them the volumes

Also, it would be cool if the integral trails could be moved up/down or so, because currently, if watching the spectrum with the CA mode, the integrals look kind of weird.

@nes-cgn please open different tickets and don't mix 2 problems. Otherwise it is not possible to solve one of the problem and close the ticket.


docs: decide word-emphasizing best practice for future docs and review existing

Now we mainly use bold words in some docs but not very consistently. There may also be some italics and hopefully no underlines but it's possible (need to check).
Which one of these should we adopt? I think probably just one to keep things simple (so I would incline towards bold. What kind of words or phrases should it be applied to?

[ ] Decide;
[ ] Note to docs contrib guide; and
[ ] Start reviewing all existing docs (a little daunting 😓).

We should first come to a decision and remove the question label, then anyone can help with the rest 🙂


URL- Encoded Sessions

We could, hypothetically, compress a MicrobeTrace session (assuming we implement #3) and then affix that string in a GET parameter of a URL. That way, people could (possibly) "share" sessions.

The footprint of even small MicrobeTrace sessions (100 HIV sequences) is too large (~5MB) for URLEncoding. Won't do.


How to read data un-changed data

Is it possible to read a variable (via dataref) without subscribing to it? As I understand, if you subscribe to a dataref you will get a callback if the value changed. But what if the value didn't change yet, then how do I know what the value is?

Yes, once you subscribe to a DataRef you can always read its Value property to know the current value.


Incorrect null handling at boolean kernels

Describe the bug

null AND false should be false, instead of null.
null OR true should be true, instead of null.
Currently and and or are incorrect on null handling.
To Reproduce

Expected behavior

Additional context

Because NULLs are wild and counter-intuitive I double-checked this with DuckDB
>>> duckdb.query("SELECT TRUE OR NULL").fetchall()
[(True,)]

>>> duckdb.query("SELECT FALSE AND NULL").fetchall()
[(False,)]

Nice find :+1:

Thanks @tustvold. Yea, just encountered this issue on an internal project. I've verified with Spark SQL behavior.

Note the standard sql behavior is available in the separate and_kleene / or_kleene kernels introduced in #9772 (https://issues.apache.org/jira/browse/ARROW-11973). From the jira ticket it sounds like this distinction was kept because the C++ impl does the same.

Ah, thanks @jhorstmann. I didn't be aware there are separate kernels for the sql behavior. That makes sense.


a11y: ESC key should work on the Close modal

See https://issues.redhat.com/browse/RHODS-7015

This issue is related to quick starts, the ticket title was mislabelled.


Memory management is not correct when using cgroup v2

$ cat /sys/fs/cgroup/memory/memory.limit_in_bytes
cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory

JAVA_OPTS for memory limit 768Mi
before:  -XX:+ExitOnOutOfMemoryError -XX:MetaspaceSize=32m -XX:MaxMetaspaceSize=96m
after:  -Xmx384m -XX:+ExitOnOutOfMemoryError -XX:MetaspaceSize=32m -XX:MaxMetaspaceSize=96m

Thanks @amarkevich. Do you need this on the 14.x stream?

@ryanemerson yes please

https://github.com/infinispan/infinispan-images/pull/214

@amarkevich I'll probably not be able to merge the 14.x stream until next week due to other considerations,  but I'll let you know once the fix is able for consumption via a released image.


Rename dss! -> dss_op! in loop, update weighted_dss ops.

Avoids potential naming conflicts with existing dss! function in ClimaCore.jl
Updates weighted_dss operations to use latest methods.

Looks good to me.

bors try


Fix compatibility with LLVM 12 and up

Description
This pull request addresses a compatibility with LLVM 12 due to the change within LLVM itself. Additionally, this also fix the merge from release to master on #1402
Tests
N/A See https://reviews.llvm.org/D101650
Checklist:

[x] I have read the contribution guidelines.
[ ] I have previously submitted a Contributor License Agreement.
[ ] I have updated the documentation, if applicable.
[ ] I have ensured that the change is tested somewhere in the testsuite (adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

Can you please amend your commit with the Signed-off-by field to complete the DCO, and then push --force? Thanks.


No ValueIds available trough mqtt since 7.0.0

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Manually built (git clone - yarn build - yarn install
Z-Wave JS UI version
All since 7.0.0
ZwaveJS version
Each test was done with the built in ZwaveJs version from ZwaveJSUI
Describe the bug
I discoverer that when a node is included and inited. Any actions made trough mqtt results in a
No writeable valueId
LOG
0000|2022-11-24 18:09:09.176 INFO MQTT: Message received on zwave/196/37/0/targetValue/set: 'true'
0001|2022-11-24 18:09:09.176 DEBUG GATEWAY: No writeable valueId found for 196/37/0/targetValue
the only way to solve that is restart ZwaveJS UI after that no issue
or  go on zwavejs UI itself and trigger the action then the valueId becomes writable
To Reproduce
Include a fresh node that has some actions (a switch is enough)
Once included try to control it trough mqtt using  id based path
Notice the issue
Exclude the device
Use a version before 7.0.0
Do the same thing
The node is controlable directly after its inclusion and there is no valueId error
Expected behavior
Control a device after inclusion with mqtt without having to restart zwavejs or to have to make a first action from zwavejs ui
Additional context
Discussed on slack

Due to the discussion on slack, issue may be found and i may add some notes asked by @robertsLando
interview completed event  : may need
manufacturer
productDescription
productLabel
inited
those were removed among others to clean the payload.  But those are related to identification and may be usefull


[Deque Analysis] Header's "critical" accessibility issues

Critical: This issue results in blocked content for people with disabilities, and will definitely prevent them from accessing fundamental features or content. This type of issue puts your organization at risk. Prioritize fixing as soon as possible, within the week if possible. Remediation should be a top priority.

Deque Analysis Summary
A total of 9 Critical issues exist in the Header (visible on all pages). They are summarized here:

(ID 468402, 468403, 469227, 469228) IDs/Labels must be unique: Two elements exist having each of the ID=dropdownLang and ID=dropdownUser and ID=inputEmail and ID=inputPassword . It appears these elements appear twice in the generated HTML code, but only one is visible on the page.  (I'm not sure why this is?)
(ID 468406) Searchbox in header has no label.  It should either be given a label, or have the aria-label attribute added to describe it.  (Likely the latter is fine, as it doesn't have visible label text by default)
(ID 469259) Language dropdown should be a <select> instead of a
 as it is a "listbox".

(ID 469256) Also it needs to be accessible via keyboard (current you can tab to it, but cannot arrow down to select a different language)....this might be fixed by turning this into a <select> as well.

(ID 468465) Cannot open "All of DSpace" dropdown via keyboard (only triggers on mouse hover).  Likely this should be implemented  similar to the language dropdown or Login dropdown (as those both can be opened by tabbing and clicking Enter)
(ID 468473) Search icon button has no href value.  It MUST have an href value:

Fix this issue by providing an HREF value (even if JavaScript event handlers are used) for the link. (Note: Ensure that if JavaScript event handlers are used, they allow the link to be activated with the Enter key in addition to the mouse click.).
e.g. Quick view
e.g. Quick view

The full list of these issues (which includes links for more info) can be found at this link (requires login): https://axeauditor.dequecloud.com/test-run/0856438a-a19a-11eb-bc31-b7d5be387c86/issues?activeTab=dt-issue&page=0&pageSize=100&sortField=ordinal&sortDir=asc&row=9&filter[severity]=4&filter[component_number]=0&filter[page_number]=8
More Information / Tools

Consider using Deque's free Chrome plugin to check your work

(ID 469259) Language dropdown should be a  instead of a  as it is a "listbox".
(ID 469256) Also it needs to be accessible via keyboard (current you can tab to it, but cannot arrow down to select a different language)....this might be fixed by turning this into a  as well.

I'm not really sure how it can be turned to a select tag having the same behaviour of a dropdown menu, if the problem is that list item should be accessible via keyboard it can be resolved also maintaining the ul tag
For all of them I estimate about 1 hour to fix

Thanks @atarix83 , there's two issues noted with that Language dropdown (and you may want to read the full details in the Deque link)
* (ID 469259) Listbox: Listbox is missing appropriate roles and/or attributes.  -> The suggestion here from Deque was to turn it into a <select>.  However, this may be solvable in a different manner...it looks like we might be able to provide the missing roles via ARIA tags on the existing
...maybe somewhat similar to this example: https://a11y-guidelines.orange.com/en/web/components-examples/dropdown-menu/
* (ID 469256) Also it needs to be accessible via keyboard.  As you said, this can be solvable also as a
.  The above example link shows one option (there may be others).
All in all, your approach of keeping it a
 is fine with me, as long as we provide better ARIA tags to describe the role.
I'll add your estimate & assign to your team to work on when they are ready.


No specific User Agent for SageTV

When downloading content (or anything) using sage.FileDownloader, no user_agent is specifically set, so it uses the default "Java/x.x.x_xx" user_agent.  It seems to be more 'correct', it should be setting a user_agent that would be more like "SageTV/x.x.x".  This should be able to be done by either:

Adding it directly into FileDownloader, which would require some logic to build the string from the current build version.  This is the quickest way to implement this.  The downside is it would not allow a way to 'force' the user agent to something else, which might be required when trying to access some sources.
Using the already implemented requestProps argument in FileDownloader to pass the user agent from the calling library (usually Global.StartFileDownload).  This would then likely require adding an overloaded argument to the StartFileDownload function to allow the API call to set the User Agent, which if NOT set would default to "SageTV/x.x.x"

The immediate reason I am wanting this implemented is so that PlayOn can recognize SageTV, so SageTV can be white-listed as an HD capable player, which is the only way PlayOn will stream content in HD.  Option 2 would allow sage to emulate an already white-listed player to get PlayOn in HD immediately.  Option 1 would require PlayOn to have SageTV added to it's white-list before it would work in HD.

One thing I'm not following....is can't this already be done using the StartFileDownload API call?  It sounds like #2 is already implemented. Take a look at the overloaded StartFileDownload API call in sage/api/Global.java. IIRC, that's why I added that argument in the first place. :)
And the main reason this was never set as the default was I didn't want SageTV getting blacklisted from specific sites.

At a glance, it didn't look like StartFileDownload actually passed through anything but ServerAddress, SourceFile, and DestFile when it calls downloadFile.

On another look, it looks like StartBackgroundFileDownload handles the props...

but StartFileDownload and StartCircularFileDownload do not.

Ahh yes, you are correct. :)
OK, I'd propose making 2 changes then.

Have a property such as "use_sagetv_user_agent" which then uses "SageTVa.b.c" as the user agent (and it would default to not being on for backwards compatibility)

Add an overloaded StartFileDownload API call which takes a RequestProperties parameter so this can force the user agent to whatever it wants.

That all sound good?

Sounds prefect.  I had originally envisioned a single property that would simply override the user agent all the time, but later realized this would not really be proper, and any workaround user agent spoofing should be done on a case by case basis, so this solution should work best.  Default to old behavior, ideal having the property turned on which would have a "proper" default SageTV user agent, and provide a case by case way to workaround individual site issues with a spoofed user agent.
So, this would require downloadFile to generate a default, and apply it, if desired by global property, BEFORE the requestProps are iterated through.  Then the addition to the other Global API calls to pass through the props if there.

Looks like I'll need some help if I'm going to complete this issue.  I'm not sure how, or if, the API functions CAN be overloaded.  Or at least if they can, I'm not sure about the way to go about doing so.  This leaves the only option to create a new API call (StartFileDownloadWithProps) with the properties attached.  I'm guessing there's no problem with doing this, it just means that any stv's or libraries that might benefit from the change will have to make sure to use the proper call.

Take a look at the "SageCommand" API call in Global.java. That gives you an example of how it's done. The few things you need to notice are:

The # of parameters for the method is declared as -1 (in the constructor)
It uses the 'curNumberOfParameters' variable to determine how many arguments there are and then does the appropriate thing after that.
There's 2 javadoc comments, one for each method


Alpine stable image not available?

Title: Unable to pull Alpine image
Description:
Unable to pull image from https://hub.docker.com/r/envoyproxy/envoy-alpine.
docker pull envoyproxy/envoy-alpine
Using default tag: latest
Error response from daemon: manifest for envoyproxy/envoy-alpine:latest not found: manifest unknown: manifest unknown

hi @sptrakesh you need to use the version eg
docker pull envoyproxy/envoy-alpine:v1.16.0

Thanks.


add type boolean

resolves #189
Description
redshift component of https://github.com/dbt-labs/dbt-core/issues/5739
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

@jpmmcneill Now that https://github.com/dbt-labs/dbt-core/pull/5875 has been merged, just two things and then this should be ready!

Click the "update branch" button (or merge the latest changes from main some other way)
Restore the original version of dbt-requirements.txt

If all looks good after CI runs, then we'll merge.


how to add sound notification ?

how ican add some media file ext like .ogg or .wav to playing in popup box  when order !

https://jsfiddle.net/ad3quksn/69/

Hi limonte, it runs on FF for Windows.
I wasn't able to make it work on iPad: both on FF and Safari it doesn't work - no sound was played, is this due to some iOS limit?
Thanks

@xalexbo yes, for iOS tap is required to produce some sound. Here you go with the example which works in iOS: https://jsfiddle.net/ad3quksn/126/

in my case swal is fired by body onload so the question is: to make play a sound on iPad when swal is shown is it required a button click?
I mean more generally that also a page which loads on browser cannot play any sound without user interaction?
Thanks

@xalexbo yes, that's an iOS limitation aimed at not having sites annoy users with unwanted/autoplaying sounds


t/unit/lib-Git-Lint-Check-Message/message.t may fail with non-English locale

On systems with older perl (< 5.22) and non-English locale the test suite fails:
#   Failed test 'exception matches expected'
#   at t/unit/lib-Git-Lint-Check-Message/message.t line 48.
#                   'open: filename: Datei oder Verzeichnis nicht gefunden at /home/cpansand/.cpan/build/2022022602/Git-Lint-0.008-zktBqU/t/unit/lib-Git-Lint-Check-Message/../../../lib/Git/Lint/Check/Message.pm line 25.
# '
#     doesn't match '(?^:open: filename: No such file or directory)'
# Looks like you failed 1 test of 7.
t/unit/lib-Git-Lint-Check-Message/message.t .....
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/7 subtests

Note that it is possible to set $! and inspect the expected error message:
$ perl5.20.3 -MErrno=ENOENT -E '$!=ENOENT; say "$!"'
Datei oder Verzeichnis nicht gefunden
$ env LC_ALL=C perl5.20.3 -MErrno=ENOENT -E '$!=ENOENT; say "$!"'
No such file or directory

Thanks, I didn't think that test assertion through.  I'll update and push a new version.


Hide fileStatus when compileOnSave is false

Fixes issue #524
Hope it looks okay. I'm pulling the compileOnSave directly from the cache.

Ok thanks, that's clearer to me now. Is calling parent.getProjectFileDetails the correct approach?

Is calling parent.getProjectFileDetails the correct approach?

Yes :+1: However I would prefer you track down usages of updateFileStatus. I suspect they already have access to the projectFileDetails.  Look at https://github.com/TypeStrong/atom-typescript/blob/9a7680146e6b6ece5edaba3aebeeb9baa7b8a8cd/lib/main/atom/onSaveHandler.ts#L33
Maybe add a function like hideEmitStatus there :rose:

Unfortunately, not all other usages of updateFileStatus have immediate access to projectFileDetails, e.g.: https://github.com/TypeStrong/atom-typescript/blob/2a7b56303ae5b752fd35e0ae8d0950a895f520ee/lib/main/atomts.ts#L126
(in this case I could move the updateFileStatus up into the then on line 51)
And here I would have to fetch projectFileDetails, as it's not already called:
https://github.com/TypeStrong/atom-typescript/blob/2a7b56303ae5b752fd35e0ae8d0950a895f520ee/lib/main/atom/commands/commands.ts#L120
It seems to me to be a bit anti-DRY to have logic and code calling a hideEmitStatus wherever we currently call updateFileStatus (6 places at the moment), but I can do it if you like ...
Another idea would be to react to changes to the compileOnSave flag, and hide/show the emit status based on that. The updateFileStatus logic would still run for every file, but whether it's hidden or shown would be project-wide.
Let me know what you think.

It will be in the next release 🌹

Thanks!


build: remove minification from dist/index.js

Description
Minification of dist/index.js made it difficult to investigate #8. Sourcemaps were not too great
of a solution as it increased the bundle size from ~600KB to 4.5MB.
Stack

main

#9 :point_left:

+1 on this. We aren't that sensitive to bundle size, and seeing which files are in the bundle is really useful.


Unable to authenticate

Running on Windows PowerShell 7.4.2 inside Windows Terminal:
If I run "PowerSession.exe auth"
This error occurs ($env:RUST_BACKTRACE="full"):
thread 'main' panicked at src\commands\api\asciinema.rs:38:82:
called `Result::unwrap()` on an `Err` value: Error("missing field `api_server`", line: 1, column: 53)
stack backtrace:
   0:     0x7ff6a74e912a - <unknown>
   1:     0x7ff6a75045bb - <unknown>
   2:     0x7ff6a74e4a11 - <unknown>
   3:     0x7ff6a74e8eaa - <unknown>
   4:     0x7ff6a74eb64a - <unknown>
   5:     0x7ff6a74eb2b8 - <unknown>
   6:     0x7ff6a74ebcfe - <unknown>
   7:     0x7ff6a74ebbed - <unknown>
   8:     0x7ff6a74e9b19 - <unknown>
   9:     0x7ff6a74eb8f0 - <unknown>
  10:     0x7ff6a7519205 - <unknown>
  11:     0x7ff6a7519664 - <unknown>
  12:     0x7ff6a72898ce - <unknown>
  13:     0x7ff6a728a916 - <unknown>
  14:     0x7ff6a72ac046 - <unknown>
  15:     0x7ff6a72973f6 - <unknown>
  16:     0x7ff6a72a244c - <unknown>
  17:     0x7ff6a74de128 - <unknown>
  18:     0x7ff6a72adf9c - <unknown>
  19:     0x7ff6a750bbfc - <unknown>
  20:     0x7ffb741f7344 - BaseThreadInitThunk
  21:     0x7ffb75fe26b1 - RtlUserThreadStart

Thanks.

did you by any chance edit the config.json in the $APP_FOLDER/PowerSession/ ?

config.json

I don't have this file! I downloaded the 'PowerSession.exe' for the releases page (https://github.com/Watfaq/PowerSession-rs/releases/tag/v0.1.11) and put it on a folder indexed by "$env:PATH"!
Thanks.

that's weird.
do you have anything here C:\Users\YOUR_USERNAME\AppData\Roaming\PowerSession
if not can you create a config.json with content
{"install_id":"d9870be7-bd89-4b53-844a-07b9746b8790","api_server":"https://asciinema.org"}

that's weird.
do you have anything here C:\Users\YOUR_USERNAME\AppData\Roaming\PowerSession
if not can you create a config.json with content
{"install_id":"d9870be7-bd89-4b53-844a-07b9746b8790","api_server":"https://asciinema.org"}

I already have this file, but it contains:
{"install_id":"285d7599-d8eb-4786-ba3d-622dd68f733b"}
I added the 'api_server' key and now it works!
Maybe my config file was broken because I used the older version of PowerSession (https://github.com/Watfaq/PowerSession) and this new version don't fix the file!
I think you can close this issue, but I thing that this bug will appear if someone was migrating from the older version!
Thanks

yeah good point. glad you solved it!


Quick-craft with quality

CustomInputPrototype::selected_prototype does not yet include quality, so we cannot quick-craft with quality yet.
Add this to the API.

Turns out the crafting functions also don't support quality. :weary:


Fixing some lint issues for #171

any idea why this is failing?

By the way, I have no idea why this fails either, will be checking Travis logs.

            mockApplicationComponent = DaggerCommonsApplicationComponent.builder()
                                       ^
  symbol:   variable DaggerCommonsApplicationComponent
  location: class TestCommonsApplication```

Thanks @noloman !


Excecute only runs the first statement

Consider the following code
import { createClient } from "@libsql/client";

const file_name = process.cwd() + "/test.db";
const db_url = "file:" + file_name;

const db_client = createClient({
  url: db_url,
});

const rs = await db_client.execute(
  "CREATE TABLE a(a1 integer); CREATE TABLE b(b1 integer);"
);
console.log(rs);

Only the table a is created. The second create statement is silently ignored.
This is different from what better-sqlite3 does.
Supporting multiple statements would be useful for
reading sql statements form a file as in the example at
https://github.com/WiseLibs/better-sqlite3/blob/master/docs/api.md#execstring---this
const migration = fs.readFileSync('migrate-schema.sql', 'utf8');
db.exec(migration);

I have found that the code works by replacing excecute by executeMultiple. I think that this API difference is annoying and error-prone (if you won't output any error when multiple statements are in the input string).


cts force clk nets

Add CTS_FORCE_CLK_NETS that overrides clock nets defined by the provided sdc + other small logging message changes.
The motivation behind this is that the sdc file sometimes doesn't properly define clock net. This leads to unwanted behavior during cts (and perhaps in other stages too like sta). Arguably, one should go fix the sdc file, but I see no harm to have this new variable as a workaround.

Yes. I agree. I am having second thoughts about this and I changed it to draft. Especially, when I realized that it's likely I misunderstood CTS log file.


The new QnA Bot doesn't answer in Teams, but working in the WebChat

Bot Info
SDK Platform: .NET
SDK Version: current Azure version (do not know where I can check it in Azure)
Active Channels: MS Teams, Direct Line
Deployment Environment: Azure Bot Service
Issue Description
I've created the QnA Bot, activated the channel MS Teams (have status "run"). But the bot doesn't answer in MS Teams. In the WebChat all is ok.

Code Example
Standard QnA Bot in Azure, I haven't edited the code.
Reproduction Steps

Activated the channel MS Teams
Get the link for MS Teams
Send the messages to the bot in MS Teams - no answers
Send the message to the bot in the WebChat - receive the answer

Expected Behavior
I expect the answer in MS Teams.
Actual Results
No error messages. Just have no answer in MS Teams. But in the WebChat all is ok.

Web chat descrambled in the build _freged itself true buffer built for an hour then extracted its in the time of march web chat install err accured

Its missing support plug for mic

Hello world

@Jessica1980 I'm not sure I follow what your issue is, can you please share your code and explain what is going wrong for you?
@brandon1780 I have no idea what you are talking about here, can you please open a new issue detailing what your issue is?

Closing as no response


runtime: go test inconsistent line number (by runtime.Caller) with and w/o -race

go version
go version go1.5.1 linux/amd64
what I did

paste the following code to any_test.go (with no preceeding empty lines)
go test
go test -race

package any

import (
    "runtime"
    "testing"
)

func TestGetPos(t *testing.T) {
    line := someFunc( // this is the line that should be restored.
        0,
        1,
        2,
    )
    if expected := 9; line != expected {
        t.Fatalf(`Expect "%v" to be "%v"`, line, expected)
    }
}

func someFunc(int, int, int) int {
    return GetPos(1)
}

// GetPos get the current position of execution.
func GetPos(skip int) int {
    _, _, line, _ := runtime.Caller(skip + 1)
    return line
}

what I expected
both tests passed, regardless of -race option
what I saw instead
"go test" passed but "go test -race" failed, because of inconsistent line numbers returned by runtime.Caller.

same problem with go1.8, is there any way to detect the -race option in the code?

Actually, this bug is fixed in the upcoming 1.9 release.  I'm going to close this.
It's still broken in 1.8, though, and we won't fix it there.  The only way to detect the -race option in code is to  use a build tag.


Everspring - EH403 - Cannot change default configuration

Discussed in https://github.com/zwave-js/node-zwave-js/discussions/6828

Originally posted by @s8109csa May  8, 2024
Checklist

[X] I have read and followed the above instructions

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue
What is happening?
I cannot change default configuration on Everspring EH403. I have 3 of them, same issue on all. There are 3 parameters and for me the important would be the auto report lux value. I wanted to change 0 to 3 and when I clicked somewhere else in the Home Assisstant, there was only an error message: Error happened. Other Z-Wave devices are working as expected.
What did you expect to happen instead?
Update parameters
Steps to reproduce the behavior:

Go to Devices -> Z-Wave -> Everspring EH403 -> Settings -> Edit parameter 3 -> click out from the cell.
See error

Anything else we should know?
The devices are securely connected to Aeotec USB Z-Stick 7 - again, I can edit other devices. FW is default, I don't think there was ever a firmware update on these flood lights.
Software versions
Driver (node-zwave-js): ...
Z-Wave JS UI: ...
Home Assistant Z-Wave Integration: ...
Home Assistant Z-Wave JS Addon: ...newest but it was always the case
ioBroker.zwave2 Adapter: ...
If you are using something non-standard, tell us here: ...
Device information
Manufacturer: EverSpring
Model name: EH-403
Node ID: 11
Checklist

[X] I made sure to provide a driver log on level debug.

[X] The log includes a re-interview of the problematic device (if applicable).

[X] The log includes the problematic interaction with the device (if applicable).

[X] I provided the node ID of the problematic device (if applicable).

Upload Logfile
home-assistant_zwave_js_2024-05-08T15-09-55.901Z.log

Fix: Disable Supervision CC for this device.

Yeah that's something I have to do in Z-Wave JS.

@zwave-js-bot add compat flag to 0x0060:0x0012:0x0001
"commandClasses": {
	"remove": {
    	// The device does not support Supervision correctly
        "Supervision": {
			"endpoints": "*"
		},
	}
}

Hi, thank you for your efforts, I just want to inform you that I have just
installed 0.6.0 of Z-Wave JS and tested Everspring EH-403 parameter update,
it is still doesn't work, it just says error. Logs shows nothing at all, no
communication seen in the JS log file.
Can it be that it is S2 connected?
Thanks
Peter
AlCalzone @.***> ezt írta (időpont: 2024. máj. 14., K,
9:12):

Closed #6829 https://github.com/zwave-js/node-zwave-js/issues/6829 as
completed via #6847 https://github.com/zwave-js/node-zwave-js/pull/6847.
—
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-zwave-js/issues/6829#event-12797127383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARW5BUGG24PFSTI3O363PCTZCG2M7AVCNFSM6AAAAABHNNPEUSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSG44TOMJSG4ZTQMY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Did you re-interview the device after updating?

Great Support, that solved it, didn't know I have to do that.
Thank you
Peter
AlCalzone @.***> ezt írta (időpont: 2024. jún. 18., K,
19:31):

Did you re-interview the device after updating?
—
Reply to this email directly, view it on GitHub
https://github.com/zwave-js/node-zwave-js/issues/6829#issuecomment-2176622406,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARW5BUEIZ4IPGEKQDRVBY7DZIBVGLAVCNFSM6AAAAABHNNPEUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWGYZDENBQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Too many activities!

Reduce the number of activities (activity_mainXX.xml & .java)

Combined activities.  Remaining activities are:
MainActivity, Main3Activity, Main8Activity, Main10Activity, Main13Activity, Main17Activity, & Main20Activity.


Analysis of diagnostics and logging for track two adoption

Summary
The Event Hubs client has a rich set of logging and diagnostics information that it makes available, exposing via ETW events and the System.Activities constructs.  The current implementation for track two is relying on its internal track one client to produce the diagnostics information.
Scope of Work

Analyze the set of telemetry, both diagnostics and logging, produced by the track one clients and determine what is relevant to the track two implementation.

Determine if the telemetry should be captured within the public-facing clients (EventHubClient, EventHubProducer, EventHubConsumer, et al) or should continue to exist within the transport level (AmqpEventHubclient, et al) as it does in the track one code.

Document and propose a plan for adopting the telemetry into the track two implementation.

Capture the follow-up wokr.

Out of Scope

Changes to any references within the TrackOneClient code; that will remain as-is.

Implementation of any telemetry changes; that will be covered under a separate workstream.

Success Criteria

A plan for implementing the telemetry in the track two client has been documented, proposed, and agreed upon.

The breakdown of work has been identified captured as well-formatted issues with the appropriate metadata.

No longer needed;  Event Source has been created for logging and diagnostics are being handled by another workstream.


rawwrite fails with "Error: LAYOUT: no sectors in sector definition!"

According to the usage.md page this should be acceptable parameters:
fluxengine rawwrite -s <flux source> -d <flux destination>
But
./fluxengine rawwrite -s test.flux -d test2.flux results in:

Error: LAYOUT: no sectors in sector definition!

Running a self compiled version that is up to,date with the repo.

Yes, the docs are out of date. You need to specify a format so that it knows which tracks you want to copy.

Reopening as a reminder to fix the documentation.


Fix flipped images on macOS 10.15

MacOS Catalina fixes a flipping issue regarding the display of image attachments in attributed strings. Therefore the workaround included in CMImageTextAttachment.m is could cause markdown images to appear vertically flipped on macOS 10.15.
So this pull request conditionally removes the extra image flipping when the masOS version is 10.15 or above.
It also includes a new CMDocument init method added in a previous commit.

I'm still seeing the flipping issue in a specific circumstance. When building our app with Xcode 10, the images are still flipped, regardless of what macOS version is used to build the app. Could this be a difference in the SDK version instead of the macOS version?
I'm trying to find a good way to check the SDK version used when building the app within code (perhaps using a preprocessor macro), but haven't been able to figure it out yet.

We're testing a fix right now where it checks for the SDK instead of the OS version. I will submit a PR if it ends up working on our end.

Actually the code has to test both the SDK version used for compiling the application and the OS version on which the application is running.
Which is a reasonable choice on the Apple side: the image flipping issue has been fixed in macOS 10.15, but to avoid breaking compatibility with older applications, the flipping behavior is changed only if the App was compiled with a SDK posterior to the change.
Which way are you using to test the SDk version ?

This seems to fix the problem
#if !TARGET_OS_IPHONE
#ifdef __MAC_10_15
    if (! [NSProcessInfo.processInfo isOperatingSystemAtLeastVersion: (NSOperatingSystemVersion){10, 15, 0}])
#endif
    {
        // On macOS 10.14.6 and below, the image attachment is dislayed vertically flipped, so we need to flip it again to display it correctly
        // This issue has been fixed on macOS 10.15 for applications compiled with Xcode 11 or later (SDK version >= 10.15)
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wdeprecated-declarations"
        [self.image setFlipped:NSGraphicsContext.currentContext.isFlipped];
#pragma clang diagnostic pop
    }
#endif

Yep, that's pretty close to what I was testing. Here's what I have:
#ifdef __MAC_OS_X_VERSION_MAX_ALLOWED
#if __MAC_OS_X_VERSION_MAX_ALLOWED < 101500 // 101500 == macOS 10.15
    // In apps built with the macOS 10.14.6 SDK and earlier, the image attachment is dislayed vertically flipped, so we need to flip it again to display it correctly
    // This issue has been fixed on macOS 10.15.
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wdeprecated-declarations"
    [self.image setFlipped:NSGraphicsContext.currentContext.isFlipped];
#pragma clang diagnostic pop
#endif
#endif

In my testing, checking for the operating system wasn't needed, but I haven't finished testing all variants yet. Here's what I've tested so far:

Build with Xcode 10.3 on macOS 10.14.6, run on macOS 10.14.6: works
Build with Xcode 10.3 on macOS 10.14.6, run on macOS 10.15.1: works
Build with Xcode 11.2.1 on macOS 10.15.1, run on macOS 10.14.6: not yet tested
Build with Xcode 11.2.1 on macOS 10.15.1, run on macOS 10.15.1: works

It looks like both options work in my quick testing.

@hisaac If I run your proposed code in the following configuration, the image is flipped

Build with Xcode 11.2.1 (macOS 10.14.6), run on macOS 10.14.6: flipped

So the runtime OS version check is really needed.
For the rest, both ways to test the SDK version are equivalent :)

Ah yep, good catch. So many variables to test!
Would you like me to make a PR with these changes, or would you like to handle it? I'm fine either way.

So let's say I make the PR. 👍

Alrighty, thanks!


Replace createSomeImageryProvider functions with SomeImageryProvider class

Fixes #4812
This has been a pet peeve of mine for a while so I wanted to take 5 minutes to fix it.

createOpenStreetMapImageryProvider -> OpenStreetMapImageryProvider
createTileMapServiceImageryProvider -> TileMapServiceImageryProvider
Instead of using createSomeImageryProvider to return an instance of UrlTemplateImageryProvider, the SomeImageryProvider class inherits from UrlTemplateImageryProvider.
No code changes or refactoring other than moving some of the TileMapServiceImageryProvider functions onto prototype

@hpinkos, thanks for the pull request! Maintainers, we have a signed CLA from @hpinkos, so you can review this at any time.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks again for the pull request!
Looks like this pull request hasn't been updated in 30 days since I last commented.
To keep things tidy should this be closed? Perhaps keep the branch and submit an issue?
I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

I just ran into a dead link related to this:
https://cesiumjs.org/tutorials/Imagery-Layers-Tutorial/#imagery-providers
This links to:
https://cesiumjs.org/Cesium/Build/Documentation/TileMapServiceImageryProvider.html
Which doesn't exist yet, but it sounds like it will with this PR. Are we still planning on merging this @hpinkos  ?

@OmarShehata I would love to get this merged, but it's not really a priority.
TileMapServiceImageryProvider did exist a long time ago, then we made a bad decision and replaced it with the createTileMapServiceImageryProvider function, and I want to change it back so our API is more consistent.
For now, just change the doc to createTileMapServiceImageryProvider

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks again for your contribution @hpinkos!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

@mramato ready for review

Or @OmarShehata if you have a chance to review this first, please do =)

Looks good, I'll merge as soon as its green

I just noticed that this removed create*ImageryProvider but missed createWorldImagery and createWorldTerrain.  Was that intentional?

Yes, createWorldImagery and createWorldTerrain are helper functions that are a proxy to create whatever the default Cesium imagery/terrain are. They are not Imagery/Terrain providers in and of themselves.


fix(UI): fixed the jitter of the input component

The old version of the input component will have a length when you click the plus and minus buttons, use el-input-number instead.

The current input component clicks to increase only once.

The current input component clicks to increase only once.


[BUG] cython does not compile with current cpython main

Describe the bug
A clear and concise description of what the bug is.
https://github.com/python/cpython/pull/25729 /  https://bugs.python.org/issue40222 changed the signature of PyCode_NewWithPosOnlyArgs which results in
    gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/tcaswell/.virtualenvs/bleeding/include -I/home/tcaswell/.pybuild/bleeding/include/python3.11 -c /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c -o build/temp.linux-x86_64-3.11/tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.o
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c: In function ‘__Pyx_InitCachedConstants’:
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:429:11: error: too few arguments to function ‘PyCode_NewWithPosOnlyArgs’
      429 |           PyCode_NewWithPosOnlyArgs(a, p, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:8314:33: note: in expansion of macro ‘__Pyx_PyCode_New’
     8314 |   __pyx_codeobj__7 = (PyObject*)__Pyx_PyCode_New(1, 0, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__6, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_Cython_Plex_Scanners_py, __pyx_n_s_read, 110, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__7)) __PYX_ERR(0, 110, __pyx_L1_error)
          |                                 ^~~~~~~~~~~~~~~~
    In file included from /home/tcaswell/.pybuild/bleeding/include/python3.11/code.h:13,
                     from /home/tcaswell/.pybuild/bleeding/include/python3.11/Python.h:107,
                     from /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:31:
    /home/tcaswell/.pybuild/bleeding/include/python3.11/cpython/code.h:123:28: note: declared here
      123 | PyAPI_FUNC(PyCodeObject *) PyCode_NewWithPosOnlyArgs(
          |                            ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:429:11: error: too few arguments to function ‘PyCode_NewWithPosOnlyArgs’
      429 |           PyCode_NewWithPosOnlyArgs(a, p, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:8326:33: note: in expansion of macro ‘__Pyx_PyCode_New’
     8326 |   __pyx_codeobj__9 = (PyObject*)__Pyx_PyCode_New(1, 0, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__8, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_Cython_Plex_Scanners_py, __pyx_n_s_position, 297, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__9)) __PYX_ERR(0, 297, __pyx_L1_error)
          |                                 ^~~~~~~~~~~~~~~~
    In file included from /home/tcaswell/.pybuild/bleeding/include/python3.11/code.h:13,
                     from /home/tcaswell/.pybuild/bleeding/include/python3.11/Python.h:107,
                     from /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:31:
    /home/tcaswell/.pybuild/bleeding/include/python3.11/cpython/code.h:123:28: note: declared here
      123 | PyAPI_FUNC(PyCodeObject *) PyCode_NewWithPosOnlyArgs(
          |                            ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:429:11: error: too few arguments to function ‘PyCode_NewWithPosOnlyArgs’
      429 |           PyCode_NewWithPosOnlyArgs(a, p, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:8338:34: note: in expansion of macro ‘__Pyx_PyCode_New’
     8338 |   __pyx_codeobj__11 = (PyObject*)__Pyx_PyCode_New(1, 0, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__10, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_Cython_Plex_Scanners_py, __pyx_n_s_get_position, 308, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__11)) __PYX_ERR(0, 308, __pyx_L1_error)
          |                                  ^~~~~~~~~~~~~~~~
    In file included from /home/tcaswell/.pybuild/bleeding/include/python3.11/code.h:13,
                     from /home/tcaswell/.pybuild/bleeding/include/python3.11/Python.h:107,
                     from /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:31:
    /home/tcaswell/.pybuild/bleeding/include/python3.11/cpython/code.h:123:28: note: declared here
      123 | PyAPI_FUNC(PyCodeObject *) PyCode_NewWithPosOnlyArgs(
          |                            ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:429:11: error: too few arguments to function ‘PyCode_NewWithPosOnlyArgs’
      429 |           PyCode_NewWithPosOnlyArgs(a, p, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:8350:34: note: in expansion of macro ‘__Pyx_PyCode_New’
     8350 |   __pyx_codeobj__13 = (PyObject*)__Pyx_PyCode_New(1, 0, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__12, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_Cython_Plex_Scanners_py, __pyx_n_s_eof, 335, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__13)) __PYX_ERR(0, 335, __pyx_L1_error)
          |                                  ^~~~~~~~~~~~~~~~
    In file included from /home/tcaswell/.pybuild/bleeding/include/python3.11/code.h:13,
                     from /home/tcaswell/.pybuild/bleeding/include/python3.11/Python.h:107,
                     from /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:31:
    /home/tcaswell/.pybuild/bleeding/include/python3.11/cpython/code.h:123:28: note: declared here
      123 | PyAPI_FUNC(PyCodeObject *) PyCode_NewWithPosOnlyArgs(
          |                            ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c: In function ‘__Pyx_CreateCodeObjectForTraceback’:
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:429:11: error: too few arguments to function ‘PyCode_NewWithPosOnlyArgs’
      429 |           PyCode_NewWithPosOnlyArgs(a, p, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
          |           ^~~~~~~~~~~~~~~~~~~~~~~~~
    /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:12057:15: note: in expansion of macro ‘__Pyx_PyCode_New’
    12057 |     py_code = __Pyx_PyCode_New(
          |               ^~~~~~~~~~~~~~~~
    In file included from /home/tcaswell/.pybuild/bleeding/include/python3.11/code.h:13,
                     from /home/tcaswell/.pybuild/bleeding/include/python3.11/Python.h:107,
                     from /tmp/pip-req-build-cit9u2ev/Cython/Plex/Scanners.c:31:
    /home/tcaswell/.pybuild/bleeding/include/python3.11/cpython/code.h:123:28: note: declared here
      123 | PyAPI_FUNC(PyCodeObject *) PyCode_NewWithPosOnlyArgs(
          |                            ^~~~~~~~~~~~~~~~~~~~~~~~~
    error: command '/lib/ccache/bin/gcc' failed with exit code 1
    Running setup.py install for Cython ... error

To Reproduce
Attempt to compile cython with main branch of cpython (8940916a02)
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):

OS: [e.g. Linux, Windows, macOS]
Python version [e.g. 3.8.4]
Cython version [e.g. 0.29.18]

Additional context
Add any other context about the problem here.
@scoder is already aware of this: https://bugs.python.org/issue40222#msg393470
Sorry if this is just noise.

As long as it's not clear if this change will stay in CPython or not, the best we can do is sit and wait.

Also note that this is a change in CPython 3.11, which will only see its first alpha release in about half a year's time.


Implement basic mode

Would basically just be a normal terminal without all of the panels and such.

Implemented in <IP_ADDRESS>


Communication Channels?

Hey Everyone!
I wanted to contribute to this project as well as intel/edge-conductor... But as is the case for the main K8s project I couldnt find means to communicate and coordinate with other contributors , e.g slack... I was wondering if I just missed it, or there is none, or if so is it internal to intel?

Apologies for the delay, as of now this is the main way to communicate with the team, or you could email us directly, any feedback is greatly apricated.


GH Actions: various tweaks

Description
Workflow update in response to https://github.com/ramsey/composer-install/pull/210#issuecomment-1001898469
GH Actions: allow for manually triggering a workflow
Triggering a workflow for a branch manually is not supported by default in GH Actions, but has to be explicitly allowed.
This is useful if, for instance, an external action script or composer dependency has broken.
Once a fix is available, failing builds for open PRs can be retriggered manually instead of having to be re-pushed to retrigger the workflow.
Ref: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/
GH Actions: auto-cancel previous builds for same branch
Previously, in Travis, when the same branch was pushed again and the "Auto cancellation" option on the "Settings" page had been turned on (as it was for most repos), any still running builds for the same branch would be stopped in favour of starting the build for the newly pushed version of the branch.
To enable this behaviour in GH Actions, a concurrency configuration needs to be added to each workflow for which this should applied to.
More than anything, this is a way to be kind to GitHub by not wasting resources which they so kindly provide to us for free.
Refs:

https://github.blog/changelog/2021-04-19-github-actions-limit-workflow-run-or-job-concurrency/
https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#concurrency

GH Actions: change job order
The code coverage job is running the same command as the Expect tests.
I'd like to suggest to only run code coverage when the Expect tests actually pass. To that end, I'm suggesting to reverse the order of the jobs in the workflow (test first, code-coverage second) and make the code-coverage job dependent on the test run (via needs), so it only runs when the tests pass.
GH Actions: don't run code coverage on forks
Oftentimes, the "owner" of a fork won't have permission to upload code coverage data for the "main" repo and it would be very rare for them to have a CodeCov account setup linked to their fork, so a code coverage run can be limited to the "main" repo only.
GH Actions: version update for codecov/codecov-action
A while back the codecov/codecov-action released a new major.
As per the release notes:

On February 1, 2022, the v1 uploader will be full sunset and no longer function. This is due to the deprecation of the underlying bash uploader. This version uses the new uploader.

Considering Feb 2022 is creeping closer every day, updating seems prudent.

Multiple fields have not been transferred from the bash uploader or have been deprecated. Notably many of the functionalities and gcov_ arguments have been removed.

This repo does not seem to be affected by this.
Refs:

https://github.com/codecov/codecov-action/releases/tag/v2.0.0
https://github.com/codecov/codecov-action/releases/tag/v2.0.1
https://github.com/codecov/codecov-action/releases/tag/v2.0.2
https://github.com/codecov/codecov-action/releases/tag/v2.0.3
https://github.com/codecov/codecov-action/releases/tag/v2.1.0

GH Actions: only run the action tests when the "expect" tests pass
... to be kind to GitHub for the resources they so freely provide, as when the expect tests fail, a commit/PR isn't ready for merge yet anyway.
GH Actions: add a job to run Composer normalize
🆕 GH Actions: use ruby/setup-ruby
The actions/setup-ruby action has been archieved and is no longer maintained.
Per the note in the README:

Please note: This action is deprecated and should no longer be used. The team at GitHub has ceased making and accepting code contributions or maintaining issues tracker. Please, migrate your workflows to the ruby/setup-ruby, which is being actively maintained by the official Ruby organization.

This switches the workflow over to the ruby/setup-ruby action.
Ref: https://github.com/ruby/setup-ruby
Motivation and context
See the commit descriptions.
How has this been tested?
By running the workflow ;-)
PR checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING.md document.
[ ] I have added tests to cover my changes.

Found one more thing & added an extra commit to address it.

P.S.: critical review warranted. The "code cov not on forks" commit may still need to be removed.

The "code cov not on forks" commit may still need to be removed.

The only concern I have for this one is whether this means the coverage check will not run on PRs. However, it appears to have run on this PR, so maybe that's not an issue?

The "code cov not on forks" commit may still need to be removed.

The only concern I have for this one is whether this means the coverage check will not run on PRs. However, it appears to have run on this PR, so maybe that's not an issue?

Well, PRs should be regarded as coming from this repo, so it should be okay. I could add an extra condition github.event_name == 'push' to only limit it on pushes, not pull requests ?

I could add an extra condition github.event_name == 'push' to only limit it on pushes, not pull requests ?

I don't think that's necessary. I'll go ahead and merge it, and we'll see how it goes. 😄


Fixes in docs

Changed the docs url in readme
Added CorrelationId - PK warning in saga persistence

Hand picked.

Hmm, I rebaked just before committing

Yeah, I pushed my cache change before pulling.


[Bug] 主键模型出现2条相同的主键的数据

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
3.0.1
What's Wrong?

如图，出现了相同数据的主键；目前不确定是怎么导致的；
What You Expected?
希望有对应的解决方案或者能够快速解决问题
How to Reproduce?
难以复现
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

can't you reproduce this?


[Feature] GraalVM Native Image support (Experimental).

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[x] Update the documentation to include this new feature.

[ ] Tests(including UT, IT, E2E) are added to verify the new feature.

[ ] If it's UI related, attach the screenshots below.

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #11279 .

[x] Update the CHANGES log.

Notice, that the OSPP is reaching the deadline. SkyWalking community would not accept the PR until it is qualified.
Only two days left, and I can't be sure your PR can be merged at the last minute.


worked on login modal to implement forgot password

Yeah there's nothing yet. I have to work on it.


Node not unhighlighted when moving quickly on the highlight link

https://github.com/skydive-project/skydive/pull/831


Numpy Identity operator

Description
Implementation of numpy identity operator in mxnet.
The version that cherry-pick on new numpy branch, old pr -> #15511.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

add op identity
fix some typos/mistakes in doc of zeros and ones

Comments
Welcome @reminisce, @haojin2, and others for reviewing.

@hgt312 Can you look into the CI failures ?
@mxnet-label-bot Add [Numpy, operator]

@piyushghai
It a build error caused by mkl-dnn. There is a solution -> https://github.com/apache/incubator-mxnet/pull/15630/commits/128967b7e05ccc703d5a5165e802c0008103adbd.


Fixed failing tests

There are four more failing tests which fail due to puli/issues#198.

Thank you!


Regarding the Dataset availibility

Hi I am Manish, a masters student from IIT Patna. I am doing my research in this Radar and camera fusion. Can you share the dataset with me. It will be helpful.

您好，你的邮件我已经收到，我会尽快给您回复，谢谢。

感谢您的回复
On Thu, Nov 30, 2023 at 10:06 AM Sawyer Wu @.***> wrote:

您好，你的邮件我已经收到，我会尽快给您回复，谢谢。
—
Reply to this email directly, view it on GitHub
https://github.com/TJRadarLab/TJ4DRadSet/issues/19#issuecomment-1833095244,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXY5IHV5OR7JQPJL34LYNKDYHAENTAVCNFSM6AAAAABAART6LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGA4TKMRUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Tab key is extremely slow on medium-large files when emmet.triggerExpansionOnTab is enabled

Issue Type: Bug
When I open a large file (tried on .php and .html) and emmet.triggerExpansionOnTab option is enabled, then each pressing on TAB key (even on blank line) make my computer hung for about 1-2 seconds (depends on file size) with high CPU load.
This is true with current 1.33 version of VS CODE, with or without extensions (tried with code --disable-extensions), with or without project open. I also tried to download 1.34 insiders build and the behavior is still the same.
Steps to Reproduce:

Download a fresh 1.34 insiders build (or use 1.33 current).

Create new HTML file tmp.html with any content. Make sure it is 2000+ lines. Better 5000+ - the hang is more obvious when the file is more large. I attached an example file here.

Set cursor on any line and press TAB. You can press it many times in a row or press and hold - all should be fine.

Open preferences and enable Emmet: Trigger Expansion on Tab option (emmet.triggerExpansionOnTab).

Return to opened file and try to press TAB again. You should see a very notable delay between pressing the key and moving the cursor (you can enable Toggle render whitespace option to see this better).
If you press and hold the TAB key for about 5 seconds, then you should see no spaces/tabs characters entered (but notice high CPU load), you then can move cursor to anoter place in the editor, and after another 10-30 seconds have been passed (all that time with high CPU load), the delayed space characters will appear at the current cursor position (not where the cursor been when you actually pressed the TAB key).

So here is two problems:

A high CPU load and delay between pressing TAB key and appearing of spaces/tab characters.
The space/tab characters appears after the delay not where the cursor was when TAB key was pressed, but at the current position of the cursor.

I notice this problem only recently. I'm not sure with which build this comes in (not used VS Code recently), but 1-2 month ago there were no this problem.

VS Code version: Code - Insiders 1.34.0-insider (56f1b4795fed05677eb82a21dac4fc1ab62d747b, 2019-04-09T05:19:45.294Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (4 x 3400)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.93GB (1.39GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

I have the same problem with latest vscode.

Duplicate of #70371. Try tomorrow's Insiders which should have the fix.

@octref Tried today's insiders build. Nothing is changed.
I opened a html file with 3700 LOC, enabled emmet.triggerExpansionOnTab, and tried to press TAB. It extremely slow and consumes high CPU. For doing nothing (nothing to expand by emmet because I press TAB key on empty lines...).
Also, I can be not a duplicate of #70371 because in #70371 there is no high CPU load and there users try real emmet expansions. This bug on other hand not about emmet expansion, but about pressing TAB key on empty line (where emmet should not trigger at all).
VS Code version: Code - Insiders 1.37.0-insider (cf03ea3729dc37e439d724267ad29dc5840f903a, 2019-07-30T07:15:22.972Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (4 x 3400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.93GB (2.88GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

It's not in insider yet. Wait a bit.

It's not in insider yet. Wait a bit.

Is a bit - you mean we have no chance to resolve this critycal for developer problem?)
This problem follows from when vscode released emmet from the box. We have no problem before, but now we have a lot of problem with default emmet - it does not support a lot of shortcuts from original emmet and have a lot of bugs by default installation.
I loved vscode and developed several extensions, but now i start thinking about sublime text 3 again.

we have no chance to resolve

It's already resolved.

Is a bit

You can either build from source or wait for another release of Insiders version coming out this afternoon.

@octref
I downloaded a fresh copy of VS Code Insiders (I inlcuded version and commit hash on bottom of this message) and still nothing changed.
As I see, the commit 99d5ff9c0f5a66a9e1cd7d49f9af6892e13f96a4, that fixes #70371 is from PR #78207 and it is already included in insiders build (at least it is below of the current commit of downloaded build on master branch. The Insiders build is built from master, right?).
So, if you meant that this commit should fix this issue, it doesn't, unfortunately. :-(
I recored a video to show what it looks like: vc-code-slow-tab-and-high-cpu-usage2.zip. On 00:18 I pressed TAB key several times in a row and only on 00:43 the editor finally rendered all these spaces (in my case 4 spaces instead of "tab" character). Throughout its 25 seconds VS Code consumed 100% of a single CPU core, trying to render 10 TABs (I know, that it actually consumed the cpu for something else (Emmet I think), it's just a simplification).

VS Code version: Code - Insiders 1.37.0-insider (d5900c642b359fe7a9eb1e3f9e2d0977f6e0905c, 2019-07-31T05:24:41.973Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (4 x 3400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing:

enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|23.93GB (4.55GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
Extensions: none

I'm on d5900c642b359fe7a9eb1e3f9e2d0977f6e0905c and here's what I see in a 5k line HTML file:

Whereas this is stable:

NVM, I just realized that your bug is you are having "emmet.triggerExpansionOnTab" and expanding on empty lines, whereas the bug I fixed was for "emmet.triggerExpansionOnTab": false.

This is indeed a bug, thanks for narrowing it down to the setting for me to turn off to at least live while it's being worked on.

I made a cheap improvement, which is to disable expansion if the previous character is space or tab. For example div| expands, but div | doesn't. This makes tabbing on empty lines not that miserable, but a proper fix is still needed for the expansion.

We were parsing the whole document when we didn't have to.
Emmet 's tab-to-expand would need to analyze each Node when you have multiple selections. This is to expand things like:
div|
div|
div|

with multi cursor.
However, 99% of the time tab expansion happens without any selection. I avoided parsing (which is the bottleneck that could take between 2-4s for a 5k line HTML file) for when there's no selection or when selection doesn't need the parsed document, and it's much faster now.

Emmet using remote-ssh is extremely slow.

@octref I see a delay of 2-3 seconds after pressing tab after div| in a 5000 line html file, is that still what I expect to see?

That's not. Let me try to repro...

I'll switch to our html languageservice parser for December.

@xak2000 @andremacola @medzhidov does this issue occur for you in the latest vscode?
I know this issue hasn't been looked at for a year, and I want to see where things are at, now.
I noticed that pressing and holding down tab is causing a bunch of events to fire in the profile, though I haven't associated any directly with Emmet yet.
Will take a closer look tomorrow.

Don't worry, i started use PHPStorm, so this bug can be leaved for another one year =)

@rzhao271 I checked out the file tmp.html that I included in the issue description and no, it doesn't occur anymore if I press and hold TAB on an empty line.
But I managed to reproduce the issue in other way.

Open preferences and enable Emmet: Trigger Expansion on Tab option (emmet.triggerExpansionOnTab).
Put the cursor at the start of an empty line of tmp.html file (e.g. on line 11).
Enter div and press Esc to close the autocompletion popup menu.
Press and hold TAB for 5-10 seconds. Release it.
Nothing new will be entered in the editor (emmet expansion would not happen) in next 10-20 seconds (one expansion sometimes still happens so one instance of <tab></tab> text could appear), but you will notice one CPU thread that consume 100% CPU. Main editor thread is still responsive, I suppose. I can move cursor to another line and enter some new text here etc. It looks like VS Code is not frozen at all. To notice then something wrong I need to look at my CPU temperature and frequency and I see that it doing some hard work. And then after 10-20 seconds suddenly emmet will finish it's expansion and something like this will be printed in the editor at the location of cursor when you held TAB:

|
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>
v>

(the | indicates the cursor location).
And what is worse: cursor will be moved back into the position of the file when you pressed TAB (after first
). Even if you already was in another place of the file and entering some text at the moment, your input will be interrupted and part of text that you entered will be placed into the new position of cursor (after first
).

\closedWith 15ba9ae


[Launcher]: Fallback to history client to get app report before consider as APP_RM_RESYNC_LOST

Coverage increased (+21.7%) to 74.94% when pulling c868c6db47acbeb3d0f4676f7f2ecfe8e4cc533e on yqwang/launcher-dev into 9c3fc0f3c24d143ccb413120dc1c435a9c6f2396 on errorspec.


Constant properties whose value is not a single number cause the whole class to be not documented

Example code:
properties (Constant)
    %> Supported methods
    supportedMethods = {'A', 'B'};
end

Only the file documentation is produced, but not the class documentation.

I just tried it, meaning I added your code above into the classDocumentationExample.m, removed the old documentation folder and recompiled. The documentation file html/classclass_documentation_example.html contains everything (also the supportedMethods cell).
Did I misunderstand anything or may it have been a doxygen rather than doxymatlab issue?

Actually the problem was related to the naming of the variables. When they contain - the issue is triggered.
So also the example is wrong.
The naming problme is fixed by Fixed by 0a925f370453f4f263752020298384c027596ebc


Assert.equal not returning properly

Hi @DavertMik!
Since updating to v0.3.0 I am having problems with assert.equal when the assert fails:
Here a little code snippet to show what I mean:
Before((I) => {
I.amOnPage('/');
});

 Scenario.only(
   'Navigating to prev week check date picker value',
    function* prev(I, actionBarTop, appointmentPage) {
    assert.equal(true, false);
});

Navigation --
 Navigating to prev week check date picker value
 • I am on page "https://www.test.com"

and after that the test just finishes, without failing properly
On the otherhand with assert.equal(true, true) the tests passes
Is there some problem with assert?
UPDATE:
I have got the impression that is has to do with your new handling of errors in the scenario.js:
Line 22: recorder.add(() => done(err), true);
Might be the issue?

I have got the impression that is has to do with your new handling of errors in the scenario.js

That maybe it. It was important to make promise-based assertions work, didn't check for non-promises

This is pretty rare case, as if you
a) not using generator function
b) use yield before performing assertion
everything works fine. Anyway, going to fix that

Also hitting this. It seems worse than this description, though: no assertions work after the 1st yield. So it doesn't work under any circumstance where you've queried the page for data and need to assert its value.

I've had similar symptoms with custom helpers. The when the test passes the message is OK, if it fails I get no feedback out errors.

Tested in v0.6.3
Before((I, authPage) => {
   I.amOnPage(authPage.url);
});

Scenario.only('foo test', function*(I) {
    var bla = yield I.grabTextFrom('//button')
    assert.equal(bla, 'foo');
});

'Enter' == 'foo'
      + expected - actual

      -Enter
      +foo

Everything works as expected. Closing this issue