[MXNET-748] linker fixed on Scala issues

Description
This PR is for this issue: #11988
Problem found was the linker removed from this PR need to be addressed quickly...
@nswamy @andrewfayres
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] 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)
[x] 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

@lanking520 added the project.basedir as the relative path for OSX linker. I tested on my mac running make scalaunittest
Final few lines of the test run where it shows test completed is below.
[INFO] <<< scala-maven-plugin:3.3.2:doc-jar (attach-javadocs) < generate-sources @ mxnet-full_2.11-osx-x86_64-cpu <<<
[INFO]
[INFO]
[INFO] --- scala-maven-plugin:3.3.2:doc-jar (attach-javadocs) @ mxnet-full_2.11-osx-x86_64-cpu ---
[WARNING]  Expected all dependencies to require Scala version: 2.11.8
[WARNING]  org.apache.mxnet:mxnet-core_2.11:1.3.0-SNAPSHOT requires scala version: 2.11.8
[WARNING]  org.apache.mxnet:mxnet-core_2.11:1.3.0-SNAPSHOT requires scala version: 2.11.8
[WARNING]  org.apache.mxnet:mxnet-infer_2.11:1.3.0-SNAPSHOT requires scala version: 2.11.8
[WARNING]  org.apache.mxnet:mxnet-infer_2.11:1.3.0-SNAPSHOT requires scala version: 2.11.8
[WARNING]  org.apache.mxnet:mxnet-full_2.11-osx-x86_64-cpu:1.3.0-SNAPSHOT requires scala version: 2.11.8
[WARNING]  org.scala-lang:scala-reflect:2.11.8 requires scala version: 2.11.8
[WARNING]  org.scalatest:scalatest_2.11:3.0.4 requires scala version: 2.11.11
[WARNING] Multiple versions of scala libraries detected!
[INFO] No source files found
[INFO]
[INFO] --- maven-site-plugin:3.7:attach-descriptor (attach-descriptor) @ mxnet-full_2.11-osx-x86_64-cpu ---
[INFO] Skipping because packaging 'jar' is not pom.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] MXNet Scala Package - Parent ....................... SUCCESS [  3.860 s]
[INFO] MXNet Scala Package - Initializer .................. SUCCESS [  4.771 s]
[INFO] MXNet Scala Package - Initializer Native Parent .... SUCCESS [  0.309 s]
[INFO] MXNet Scala Package - Initializer Native OSX-x86_64  SUCCESS [  6.279 s]
[INFO] MXNet Scala Package - Macros ....................... SUCCESS [  8.000 s]
[INFO] MXNet Scala Package - Core ......................... SUCCESS [01:04 min]
[INFO] MXNet Scala Package - Native Parent ................ SUCCESS [  0.116 s]
[INFO] MXNet Scala Package - Native OSX-x86_64 CPU-only ... SUCCESS [  3.752 s]
[INFO] MXNet Scala Package - Inference .................... SUCCESS [  5.152 s]
[INFO] MXNet Scala Package - Examples ..................... SUCCESS [ 19.017 s]
[INFO] MXNet Scala Package - Spark ML ..................... SUCCESS [ 10.978 s]
[INFO] MXNet Scala Package - Full Parent .................. SUCCESS [  0.080 s]
[INFO] MXNet Scala Package - Full OSX-x86_64 CPU-only ..... SUCCESS [  6.159 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:14 min
[INFO] Finished at: 2018-08-01T22:11:20-07:00
[INFO] Final Memory: 140M/926M

@nswamy thanks for your hard work, I will also give a test run on this.


Replace the current navigation animation with a more subtle one

The current implementation suffers from some problems I'd like to alleviate:
Performance
Animating the height of the uppermost item in the DOM is slow and causes frame drops. Most of the time this is hidden by the fact the page is loading. For the best case where everything is delivered from cache this is jarring though.

Page jank
We invested quite some time into removing all notable page jank from the site. Animating the height of a early component foils this goal. The following example is a screencapture taken from hitting Cmd+R when looking at a part of the page further down. The shift happens without user interaction.

Proposal
Change to the following animation
Demo

I'd suggest to

Add z-index: 1 to .mod-story1  (or remove from mod-hero)
Increase height of .mod-hero by value n
Use negative margin-top of value n: margin-top: -var(--n); for .mod-story1
Add transform: translateY(var(--n)); to .mod-story1 and transition: transform 1s ease;
After page load set translateY to 0.

This gives you the same effect as desired but without the whole page being moved around after rendering.

Closing for now. Perhaps we should tackle this when progressively enhancing the site.


update-report: better handle user set bottle domain, core git remote.

Unset these variables and print a warning if they were set to non-default values.
@XuehaiPan let me know if this works for you?
Fixes #12283

@MikeMcQuaid Unset HOMEBREW_CORE_GIT_REMOTE works for me on brew update-report. However HOMEBREW_BOTTLE_DOMAIN is still used on brew install <formula>.
$ export HOMEBREW_CORE_GIT_REMOTE="https://mirrors.tuna.tsinghua.edu.cn/git/homebrew/linuxbrew-core.git"
$ export HOMEBREW_BOTTLE_DOMAIN="https://mirrors.tuna.tsinghua.edu.cn/linuxbrew-bottles"

$ brew install bat
HOMEBREW_CORE_GIT_REMOTE set: using https://mirrors.tuna.tsinghua.edu.cn/git/homebrew/linuxbrew-core.git for Homebrew/core Git remote.
Updating Homebrew...
remote: Enumerating objects: 4798, done.
remote: Counting objects: 100% (4798/4798), done.
remote: Compressing objects: 100% (1188/1188), done.
remote: Total 4798 (delta 3610), reused 4795 (delta 3610)
Receiving objects: 100% (4798/4798), 2.09 MiB | 9.12 MiB/s, done.
Resolving deltas: 100% (3610/3610), completed with 415 local objects.
From https://mirrors.tuna.tsinghua.edu.cn/git/homebrew/linuxbrew-core
   879a061c4f1..5be975b7335  master     -> origin/master
==> Re-running `brew update` for linuxbrew-core migration
Error: HOMEBREW_CORE_GIT_REMOTE was set. Unset for the migration.
You may need to change this from a linuxbrew-core mirror to a homebrew-core one.
Error: HOMEBREW_BOTTLE_DOMAIN was set. Unset for the migration.
You may need to change this Linuxbrew packages to Homebrew packages.
HOMEBREW_CORE_GIT_REMOTE set: using https://github.com/Homebrew/homebrew-core for Homebrew/core Git remote.
remote: Enumerating objects: 1483, done.
remote: Counting objects: 100% (1110/1110), done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 1483 (delta 1095), reused 1106 (delta 1091), pack-reused 373
Receiving objects: 100% (1483/1483), 948.37 KiB | 1001.00 KiB/s, done.
Resolving deltas: 100% (1101/1101), completed with 212 local objects.
From https://github.com/Homebrew/homebrew-core
 + 5be975b7335...c8ae85dcacf master     -> origin/master  (forced update)
==> Migrating formulae from linuxbrew-core to homebrew-core
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> New Formulae
goproxy                                                         iproute2
==> Updated Formulae
Updated 4732 formulae.
==> Renamed Formulae
selenium-server-standalone -> selenium-server
==> Deleted Formulae
<EMAIL_ADDRESS>                    kafkacat                        pandoc-citeproc                 vavrdiasm

==> Downloading https://mirrors.tuna.tsinghua.edu.cn/linuxbrew-bottles/zlib-1.2.11.x86_64_linux.bottle.tar.gz
######################################################################## 100.0%
Error: bat: SHA256 mismatch
Expected: db54bf590275839d3f4cdf31d9527aa3a4c19a8984b5605cedc3f7c22a65eea4
  Actual: 6f604280b9e056da163b81cef3076b2e39bbd2b8d3cc8c36d27c19c472c760a4
    File: /home/PanXuehai/.cache/Homebrew/downloads/e55c6ff773306acd751fe27be6944bd69a95c2095673d0d6fbc791cb4c9ea89a--zlib-1.2.11.x86_64_linux.bottle.tar.gz
To retry an incomplete download, remove the file above.

@XuehaiPan Updated to add another brew doctor check and make the messages (hopefully) clearer. Can you take another look? Thanks!

It works fine for me.


Stopped linting...

I've updated to these versions and now I'm not getting any linting at all:

atom 1.22.0 ia32
linter 2.2.0
linter-js-standard 4.0.2
linter-ui-default 1.6.10

I have standard 10.0.3 installed in my project, under devDependencies in package.json.
When editing a .js file I get no linter warnings when I deliberately do something like no space after a function name (function myFunc() {}).
Why would it not be linting now..?

I don't think it is "syntactically" wrong. What would happen is your myFunc would be out of scope and you have to reference this function to another variable if you have to use it.
See this

@grudra7714 I think you may have misunderstood.
Writing a function without a space after the name should give me a lint error (see the rules) when following JavaScript Standard Style.
The problem is that Atom isn't linting even with the setup I mentioned.
It's not a code issue.

Can you post the output of running Linter: Debug? It's possible you installed a custom language file that is making the foo.js file not look like JavaScript to Atom.

Platform: win32
Atom Version: 1.22.0
Linter Version: 2.2.0
Opened file is ignored: No
Matching Linter Providers:
  - js-standard
Disabled Linter Providers:
Standard Linter Providers:
  - js-standard
Indie Linter Providers:
UI Providers:
  - Linter
Ignore Glob: **/*.min.{js,css}
VCS Ignored Paths are excluded: true
Current File Scopes:
  - *
  - source.js

I have the same bug on a fresh installation. Since I had installed many packages, I deleted my ~/.atom entirely (is that sufficient or are there other places where config is saved?). linter-js-standard lints html embedded script, but not .js files...

Platform: linux
Atom Version: 1.22.1
Linter Version: 2.2.0
Opened file is ignored: No
Matching Linter Providers:

js-standard
Disabled Linter Providers:
Standard Linter Providers:
js-standard
Indie Linter Providers:
UI Providers:
Linter
Ignore Glob: **/*.min.{js,css}
VCS Ignored Paths are excluded: true
Current File Scopes:

source.js
meta.method-call.js
meta.arguments.js

I’ve tried to reproduce this on a fresh Ubuntu installation with Atom v1.22.0<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>(as specified in your original post) but I did not run into this issue.
A few questions:

Does running standard from the command line work?
Do you have any custom standard settings in your package.json?
Could you try installing<EMAIL_ADDRESS>to see if this bug has been introduced in one of the recent versions?

@vincenzoml Your issue seems to be different since the linter produces some errors, at least. Would you mind opening a new issue for that?

As soon as I return to my main machine I'll check and open a new issue.

If anyone is still running into this issue, let me and I’ll reopen.

linter-js-standard v5.1.0 adds support for Atom’s experimental Tree-sitter parsing system, see https://github.com/ricardofbarros/linter-js-standard/commit/46c803841d61a720aa45d72234fe7ac8267c531b.


[Sema] NFC: Reorder misc bits for better code gen

As a general rule, if one wants packs miscellaneous bits into what is
otherwise just a number, the low bits are preferable over the high bits,
at least on x86. On ppc64/ppc64le, the results are more of a wash. For
reference:
struct X {
unsigned kind : 3;
unsigned level : 29;
};
X example(X x, unsigned y) {
x.level += y;
return x;
}
bool example(X x) {
return x.level > 1;
}
==== x86_64 with 'kind' first ====
_Z7example1Xj:
leal    (%rdi,%rsi,8), %eax
retq
_Z7example1X:
cmpl    $15, %edi
seta    %al
retq
==== x86_64 with 'kind' last ====
_Z7example1Xj:
leal    (%rsi,%rdi), %eax
andl    $536870911, %eax        # imm = 0x1FFFFFFF
andl    $-536870912, %edi       # imm = 0xE0000000
orl     %edi, %eax
retq
_Z7example1X:
testl   $536870910, %edi        # imm = 0x1FFFFFFE
setne   %al
retq
==== PPC64 with 'kind' first ====
_Z7example1Xj:
add 5, 5, 4
rlwimi 5, 4, 0, 0, 2
stw 5, 0(3)
blr
_Z7example1X:
rlwinm 3, 3, 0, 3, 30
cntlzw  3, 3
srwi 3, 3, 5
xori 3, 3, 1
blr
==== PPC64 with 'kind' last ====
_Z7example1Xj:
slwi 5, 5, 3
add 4, 5, 4
stw 4, 0(3)
blr
_Z7example1X:
clrldi  3, 3, 32
subfic 3, 3, 15
rldicl 3, 3, 1, 63
blr
==== PPC64LE with 'kind' first ====
_Z7example1Xj:
slwi 4, 4, 3
add 3, 4, 3
blr
_Z7example1X:
clrldi  3, 3, 32
subfic 3, 3, 15
rldicl 3, 3, 1, 63
blr
==== PPC64LE with 'kind' last ====
_Z7example1Xj:
add 4, 4, 3
rlwimi 3, 4, 0, 3, 31
blr
_Z7example1X:
rlwinm 3, 3, 0, 3, 30
cntlzw  3, 3
srwi 3, 3, 5
xori 3, 3, 1
blr

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test


Copy and paste

When ever I make a paste from chrome or any other text editor, atom crashes.
Also when making a copy from it to chrome, the page in chrome freezes.
I am using atom on Ubuntu 14

I'm guessing you're on Atom 0.189.0 version (or a previous version)? Try updating to version 0.190.0 -- this sounds like https://github.com/atom/atom/issues/6221, which should be fixed in 0.190.0. Let us know if it doesn't help.


feat: show XML of XMLViews in elements registry

New XML View tab in Elements Registry showing XMLView content
This PR introduces a new feature for the Elements Registry for sap.ui.core.mvc.XMLView controls. It provides easy access to the definition of an XMLView.
XMLViews may be bundled and minified in a component or library preload and therefor not easy to read. On top of that SAP Fiori elements is generating XMLViews dynamically based on OData metadata.
Usage

Select the tab Elements Registry
Search and / filter for XMLView or sap.ui.core.mvc.XMLView
Select any control of that type
Select the tab XML View in the details area

The XML of the selected XMLView will be shown.
Screenshot

@kineticjs Thank you Diana


Svelte: storybook generator fail if NOT using eslintrc JSON file

When creating a storybook with the command
nx g @nxext/svelte:storybook-configuration tool

I get the error  NX  Cannot parse apps/tool/.eslintrc.js: InvalidSymbol in JSON at 1:1
When replacing the file .eslintrc.js with a file .eslintrc.json, then the installation works. Then after installation I can switch back to the eslintrc.js file and everything works like intended.

I encountered this as well while setting up Storybook with SvelteKit. The eslintrc file is the flat format, and it's dynamic. It isn't JSON serializable. What's the progress on fixing this?

For anyone who sees this in the future, this is not a nxext issue. This is a @nx/storybook issue. There are two closed issues on their repository listed below. Neither thread helped my use case.
https://github.com/nrwl/nx/issues/20951
https://github.com/nrwl/nx/issues/21739
Renaming the eslintrc file made it work without a hitch. Regardless, the issue is not with this repository.


Adding Changelog for v0.6.0-rc2, updating CRD approval annotations

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This introduces the changelog for v0.6.0-rc2 and updates CRD approval annotations.
Does this PR introduce a user-facing change?:
NONE

/lgtm


Remove merge conflict marker from SELECT diagram

Relates to #2836.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/270784f5cee9b1a39af785d7da92eae5fa8f892e/

Eric, requesting your review since I think this conflict got in via 58aa589.  No blame, just want to make sure that the diagram is the correct one you intended.
If what I have here is wrong, it might be easier to close this PR and for you to submit a new, correct diagram.  But let me know what you think!

@rmloveland
Thank you for catching this! I definitely should have caught this when merging that PR.
This looks correct, but to be sure, I just generated a new diagram and opened a new PR to merge that into the 20.1 docs. I'll add you as a reviewer.


How to train using main.py using multiple GPUs?

@yikangshen @shawntan Is there an easy way to train the model to replicate the experiments using main.py using multiple GPUs?
When using model = nn.DataParallel(model) before train(), the initialization goes into the LSTM stack and then the ONLSTM cell to return the weights but it throws an error.
We also tried doing the model = nn.DataParallel(model) after the hidden = model.init_hidden(args.batch_size) and it seems like the LinearDropConnect layer can't access the .weight tensors.

We didn't try to train the model with multiple GPUs. Maybe you need to rewrite the code for  LinearDropConnect function

Another question, it seems no speed up using GPU compared with CPU, have you met the same problem?
Both take 280-290 s each epoch

@yikangshen @shawntan Is there an easy way to train the model to replicate the experiments using main.py using multiple GPUs?
When using model = nn.DataParallel(model) before train(), the initialization goes into the LSTM stack and then the ONLSTM cell to return the weights but it throws an error.
We also tried doing the model = nn.DataParallel(model) after the hidden = model.init_hidden(args.batch_size) and it seems like the LinearDropConnect layer can't access the .weight tensors.

Hi,
Just want to know have you figured this out?
Best


Introduce u32(un)checked_trailing_zeros assembly instruction

This PR introduces u32(un)checked_trailing_zeros assembly instructions.

There is also similar work in https://github.com/0xPolygonMiden/miden-vm/pull/874 - I think these PRs are complementary but might be good to think through these instructions holistically.

There is also similar work in #874 - I think these PRs are complementary but might be good to think through these instructions holistically.

Looks like the idea is to use the advice provider in #874.  This would certainly make things more efficient.

Not needed anymore.


[BEAM-11205] Upgrade Libraries BOM dependencies to 24.3.0

Upgrading Google Cloud Libraries BOM to the latest version 24.3.0 and associated dependencies to the compatible versions.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java PostCommit

Run PostCommit_Java_Hadoop_Versions

Hi @suztomo, could you help me to review this?
I have updated the dependencies listed in https://storage.googleapis.com/cloud-opensource-java-dashboard/com.google.cloud/libraries-bom/24.3.0/artifact_details.html and I ran the Linkage Check but it is having new errors https://gist.github.com/benWize/0edd56b32d9b1e7b22d4cd9c231887c3, not sure how to proceed with those.

Thank you, @suztomo!


XGimi H5 code

Just managed to turn on my Xgimi H5 with code:
0x4d4b17d86c27e0ffffff3043524b544d

@rabdalov Congratulations and thank you for sharing the code! I will add it to the list of working codes: https://stackoverflow.com/questions/69921353/how-can-i-clone-a-non-paired-ble-signal-from-a-remote-to-trigger-a-device/


Revert "add collate"

Reverts CS2103JAN2017-F12-B1/main#79

Coverage remained the same at 81.533% when pulling b25da3a6d37b65e92d28812d112814248c867212 on revert-79-V0.5_original into 5e9289c4149424aa8d57b0c3c0af49dc7853ad80 on master.


QuickLook doesn't work

Describe the bug
QuickLook doesn't work in Files. Neither with the version from the Microsoft Store nor the .msi from here.
QuickLook works as intended in the native file explorer.
To Reproduce
Steps to reproduce the behavior:

Install Quick Look
Open Files
Select a file/folder
Hit the space bar
Nothing happens

Expected behavior
The QuickLook preview of the file/folder should be shown.
Screenshots
Not possible here since nothing happens.
Desktop (please complete the following information):

OS Version: Windows 10 20H2 Build 19042.844
App version: <IP_ADDRESS>

Additional context
QuickLook is showing up in the context menu.
Seems like you are aware of this issue, but only with insider builds.
Log file
debug.txt
debug_fulltrust.txt

Merging with #3823.

@yaichenbaum Are you sure that this is the same issue?

@Ein-Tim If it's coming up in the context menu, it might be a different issue, I will reopen this.

Thank you 👍

Dear all,
with the recent update of Windows insider to 21337 all the above now works pretty good.
Both QuickLook and the Cloud service folders (i.e. Onedrive)
What does not work is the automatic update of Files, which in my case is still at 1.3 while the 1.5 is out...
Thank you for the beautiful work.

Can confirm fix, works as intended now.
Thanks!

@trama v1.5 is rolling out in stages, so it's possible it's not yet available for your device.
@Ein-Tim Thanks for letting use know!


Switch groundwater sign

See https://github.com/inbo/niche_vlaanderen/issues/319 @geohydrodata updated the data files and executed the required adjustments to the code, ready to test.
Note this will require a breaking change when releasing.

To test in a separate environment:
conda create --name niche_dev python=3.11
activate niche_dev
conda install pandas pyyaml rasterio fiona git geopandas matplotlib jupyter
pip install git+ssh://git@github.com/inbo/niche_vlaanderen.git@DD-groundwater-sign

A small correction of a typing error in the name of the branch (underscore)

conda create --name niche_dev python=3.11
activate niche_dev
conda install pandas pyyaml rasterio fiona git geopandas matplotlib jupyter
pip install git+ssh://git@github.com/inbo/niche_vlaanderen.git@DD-groundwater-sign

should be
pip install git+ssh://git@github.com/inbo/niche_vlaanderen.git@DD-groundwater_sign

A small correction of a typing error in the name of the branch (underscore)

conda create --name niche_dev python=3.11
activate niche_dev
conda install pandas pyyaml rasterio fiona git geopandas matplotlib jupyter
pip install git+ssh://git@github.com/inbo/niche_vlaanderen.git@DD-groundwater-sign

should be
pip install git+ssh://git@github.com/inbo/niche_vlaanderen.git@DD-groundwater_sign

If ssh is not working, you can try
pip install git+https://github.com/inbo/niche_vlaanderen.git@DD-groundwater_sign

Many thx for the changes!
Not checked the code yet, but looked at test cases
Testing this first version of niche_vlaanderen 2 with my reference test dataset (aka FakeComplete, for further reference), for 3 scenario's, respectively:

a simple model only based on soil+mhw+mlw,
a full model,
a full model with posthoc limitation of the results with management and inundation (that is specifying set_input => "management_vegetation" + "inundation_vegetation" )

Results until now

the output files (vegetation predictions, e.g. mymodel_V27_detail.tif or mymodel_V27.tif ) seem to be OK in all scenario's: same result as in v 1 (contrary to what I told Sacha earlier this week)
the abiotic files (mymodel_acidity.tif & mymodel_nutrient_level.tif) seem to be OK
the deviation files (e.g. mymodel_mlw_19.tif and mymodel_mhw_19.tif) seem to have the same value as with niche_vlaanderen v 1.x but with a reverted sign (as expected given the reverted sign of the inputs)

Possible improvements

deviation files: it might be nice to use the same sign convention as with niche_vlaanderen v 1.x so the user doesn't have to change the way he interprets the output files and so he can use the same legend layers as before (lyr, sld, ..) (in other words: the sign of groundwater levels as input layers would change in v 2 but the sign of the deviation layers - the output files - would stay the same as in v1.x)
I have the impression that the colour scale for the groundwater level plots (plots of the input layers, for instance simple.plot("mlw")) is  still the same as in the previous version, at least in my example. Since the scale is asymmetrical (we expect many more pixels with groundwater levels under the ground than above ground) the result could be better (see printscreen, new dev version left)

Any thoughts on this?

Many thx for the changes!

Possible improvements
* deviation files: it might be nice to use the same sign convention as with `niche_vlaanderen v 1.x` so the user doesn't have to change the way he interprets the output files and so he can use the same legend layers as before (lyr, sld, ..) (in other words: the sign of groundwater levels _as input layers_ would change in v 2 but the sign of the deviation layers - _the output files_ - would stay the same as in v1.x)
* I have the impression that the colour scale for the groundwater level plots (plots of the input layers, for instance `simple.plot("mlw")`) is  still the same as in the previous version, at least in my example. Since the scale is asymmetrical (we expect many more pixels with groundwater levels under the ground than above ground) the result could be better (see printscreen, new dev version left)

OK, I will look into this. We must make sure that plotting then doesn't conflict with a sign change in one case, and no sign change in the other.

Possible improvements

deviation files: it might be nice to use the same sign convention as with niche_vlaanderen v 1.x so the user doesn't have to change the way he interprets the output files and so he can use the same legend layers as before (lyr, sld, ..) (in other words: the sign of groundwater levels as input layers would change in v 2 but the sign of the deviation layers - the output files - would stay the same as in v1.x)

The mhw, mlw deviation output files have changed sign as requested. Implementation (and update of according tests) in https://github.com/inbo/niche_vlaanderen/commit/8bc81541a6d3361e0a9cbfc92959bb05d5cecc25.

I have the impression that the colour scale for the groundwater level plots (plots of the input layers, for instance simple.plot("mlw")) is  still the same as in the previous version, at least in my example. Since the scale is asymmetrical (we expect many more pixels with groundwater levels under the ground than above ground) the result could be better (see printscreen, new dev version left)

This has been addressed in https://github.com/inbo/niche_vlaanderen/commit/b7527c698caa5ff237cf8c7305be9d2fcc3ae226

@cecileherr, @geohydrodata  updated this PR with the requested improvements on the sign changes of groundwater and the reference table integration with Zenodo. We did an effort to standardize the system-tables as much as possible (providing a 'description' and 'beschrijving'  column) and by using the column names of the niche_vegetation into the other system tables, clarifying the connection  between both.
Furhtermore, the procedure of the update when a new version in zenodo is published is included in the documentation:

clarify to users how to compare both
Add to the release documentation which adjustments need to be done

Note We also added a chart to illustrate the interconnection between the system tables -

Can you review and test the code again to make sure everything is adjusted correctly? If ok, everything is good to go for the version v2.0.

I tried the updated version on a few test cases (unfortunately no time yet to check the code itself)
Testing this second version of niche_vlaanderen 2 with my reference test dataset (aka FakeComplete, for further reference), for different scenarios, respectively:

a simple model only based on soil+mhw+mlw,
a full model,
a full model with posthoc limitation of the results with management and inundation (that is, specifying set_input => "management_vegetation" + "inundation_vegetation" )
a full model with a custom niche table,
a full model with a custom acidity layer
a niche delta for the difference between the results of a simple and a full model
a validation of the results of the full model with a vegetation map

I ran this both in niche 1.3 and niche dev (2) and compared the results: good news, I could not find differences in the output 👍
The deviation files (e.g. mymodel_mlw_19.tif and mymodel_mhw_19.tif) now have the same sign in version 2 as in niche 1.3 as requested: thx!
And the adapted colour scale for the groundwater level plots is fine! (as requested in https://github.com/inbo/niche_vlaanderen/pull/376#issuecomment-2137404453)
Nice that the version of the niche table now appears in the created log file!
# Niche Vlaanderen version: 1.3 (= dev version for niche_vlaanderen 2)
# Using latest niche_vlaanderen  1.3
# Reference values:
#     version: 12C
#     source: 10.5281/zenodo.10417821
#     original file: NICHE_FL_referencegroundwaterlevels_v12C.csv
# Run at: 2024-07-04 14:24:56.985587

But one remark/question: 10.5281/zenodo.10417821 is the source for all the versions (thus by default the latest published version). Should we refer explicitely to the used version instead of the whole dataset (in this case 12C thus 10.5281/zenodo.10521548)?
And a last comment:
there is a new warning when I use  mymodel.plot("mhw"):
C:\Users\cecile_herr\.conda\envs\niche_dev\Lib\site-packages\IPython\core\pylabtools.py:77: DeprecationWarning: backend2gui is deprecated since IPython 8.24, backends are managed in matplotlib and can be externally registered.
  warnings.warn(

Maybe I can post it as a new issue for later?
Many thx for the changes!

But one remark/question: 10.5281/zenodo.10417821 is the source for all the versions (thus by default the latest published version). Should we refer explicitely to the used version instead of the whole dataset (in this case 12C thus 10.5281/zenodo.10521548)?

Very good point, I updated the reference and the documentation.

there is a new warning when I use mymodel.plot("mhw"):
C:\Users\cecile_herr.conda\envs\niche_dev\Lib\site-packages\IPython\core\pylabtools.py:77: DeprecationWarning: backend2gui is deprecated since IPython 8.24, backends are managed in matplotlib and can be externally registered.
warnings.warn(
Maybe I can post it as a new issue for later?

This seems to be a deprecation of either Ipython/matplotlib versions when running the code inside a notebook.  I added a new issue, see https://github.com/inbo/niche_vlaanderen/issues/380


[UISceneConfiguration isEqualToString:]: unrecognized selector error with 0.4.0-beta1

After updating to the latest Cacao version (0.4.0-beta1) I get the following runtime error:
2023-06-09 08:43:58.534893+0200 viewer-rs-ios[87147:28872615] [Assert] BUG IN CLIENT OF UIKIT: Attempting to define a mismatched UISceneSessionRole! This will be an assert in future UIKit releases! Assigning a UISceneConfiguration with role "UIWindowSceneSessionRoleApplication" for a UISceneSession with role "<UISceneConfiguration: 0x600002ecd000; name: 0x0>".
2023-06-09 08:43:58.535361+0200 viewer-rs-ios[87147:28872615] -[UISceneConfiguration isEqualToString:]: unrecognized selector sent to instance 0x600002ecd000
2023-06-09 08:43:58.538850+0200 viewer-rs-ios[87147:28872615] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UISceneConfiguration isEqualToString:]: unrecognized selector sent to instance 0x600002ecd000'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000190e7f19c __exceptionPreprocess + 176
	1   libobjc.A.dylib                     0x000000019099e4d4 objc_exception_throw + 60
	2   CoreFoundation                      0x0000000190f26178 -[NSObject(NSObject) __retain_OA] + 0
	3   CoreFoundation                      0x0000000190de7150 ___forwarding___ + 1600
	4   CoreFoundation                      0x0000000190de6a50 _CF_forwarding_prep_0 + 96
	5   UIKitCore                           0x00000001bd201470 -[UIWindowScene _allowsEventUIWindowRouting] + 76
	6   UIKitCore                           0x00000001bc766cdc -[UIScene _updateTargetOfKeyboardEventDeferringEnvironment] + 52
	7   UIKitCore                           0x00000001bc4ff05c -[UIScene initWithSession:connectionOptions:] + 1340
	8   UIKitCore                           0x00000001bc4fe7d0 -[UIWindowScene initWithSession:connectionOptions:] + 92
	9   UIKitCore                           0x00000001bc4fde7c +[UIScene _sceneForFBSScene:create:withSession:connectionOptions:] + 416
	10  UIKitCore                           0x00000001bc4fcab4 -[UIApplication _connectUISceneFromFBSScene:transitionContext:] + 884
	11  UIKitCore                           0x00000001bc4fbd8c -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 372
	12  UIKitCore                           0x00000001bc4fbba0 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 288
	13  FrontBoardServices                  0x00000001a51cb0bc -[FBSScene _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 372
	14  FrontBoardServices                  0x00000001a51eea30 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke.102 + 120
	15  FrontBoardServices                  0x00000001a51b9cd0 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 196
	16  FrontBoardServices                  0x00000001a51ee664 __92-[FBSWorkspaceScenesClient createSceneWithIdentity:parameters:transitionContext:completion:]_block_invoke + 356
	17  libdispatch.dylib                   0x00000001053aa99c _dispatch_client_callout + 20
	18  libdispatch.dylib                   0x00000001053aed70 _dispatch_block_invoke_direct + 388
	19  FrontBoardServices                  0x00000001a51b9be4 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 48
	20  FrontBoardServices                  0x00000001a5209060 -[FBSSerialQueue _targetQueue_performNextIfPossible] + 220
	21  FrontBoardServices                  0x00000001a51b9b84 -[FBSSerialQueue _performNextFromRunLoopSource] + 28
	22  CoreFoundation                      0x0000000190e06710 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
	23  CoreFoundation                      0x0000000190e066a4 __CFRunLoopDoSource0 + 176
	24  CoreFoundation                      0x0000000190e06414 __CFRunLoopDoSources0 + 244
	25  CoreFoundation                      0x0000000190e0501c __CFRunLoopRun + 828
	26  CoreFoundation                      0x0000000190e0458c CFRunLoopRunSpecific + 612
	27  HIToolbox                           0x000000019a639df4 RunCurrentEventLoopInMode + 292
	28  HIToolbox                           0x000000019a639c30 ReceiveNextEventCommon + 648
	29  HIToolbox                           0x000000019a639988 _BlockUntilNextEventMatchingListInModeWithFilter + 76
	30  AppKit                              0x0000000194023f58 _DPSNextEvent + 636
	31  AppKit                              0x00000001940230f4 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
	32  AppKit                              0x0000000194017558 -[NSApplication run] + 464
	33  AppKit                              0x0000000193fee9a8 NSApplicationMain + 880
	34  AppKit                              0x00000001942470ec +[NSWindow _savedFrameFromString:] + 0
	35  UIKitMacHelper                      0x00000001a8434b08 UINSApplicationMain + 988
	36  UIKitCore                           0x00000001bc4e3fdc UIApplicationMain + 148
	37  viewer-rs-ios                       0x000000010430b7f8 _ZN5cacao5uikit3app20App$LT$T$C$W$C$F$GT$3run17h291a1bb9f07402c9E + 512
	38  viewer-rs-ios                       0x0000000104330bc4 _ZN5storm10standalone8platform3ios12execute_impl17hf160a36e57c1f169E + 156
	39  viewer-rs-ios                       0x000000010433d7e0 run_app + 32
	40  viewer-rs-ios                       0x00000001042fd10c main + 24
	41  dyld                                0x00000001909cff28 start + 2236
)

I have no issue when I use Cacao commit 64908e5.

Can you provide more information about how you're triggering/encountering this?
That doesn't show when I run the ios-beta example, so I'm guessing you may be in somewhat uncharted territory. We can definitely look at fixing it tho.

I tried to make it reproducible and after cloning Cacao and it started working. I've then used the official release and it works as well. So there might have been some build artefacts have been cached and I didn't realise it. So after a full clean build it seems to be working fine.
Thanks again for making a new release!

Ha, happens to the best of us. Glad it's working though!
Definitely curious as to what you built. :)

Just using Cacao to start up an iOS application and initialise a UIView to later draw into the surface using Metal API. So not much more than your example does I am afraid. But its great to not have to touch Objective C and have a pure Rust codebase, so I am very grateful for all your work! :)


Searching the tree (similar to filter)

Hi, what is the best way to search for a node in the tree by some function (just like filter), but without any side effects (ex: filter is hiding the nodes). I just want to receive the list of nodes. I need this to programatically focus a node on the tree that his name contains something (I will focus the first node of the filtered list)
The true flag in the filterNodes is still hiding the ones that did not match the comparison. I just want to list back. I can of course iterate the tree on my own recursively but maybe there is already an easier way :)
Edit: Searching like this seems to be okay:
let arr = []
let iter = (node) => {
      arr.push(...node.filter(child => {
        if (child.children)
          iter(child.children);
        return child.data.key == this.displayedNode.value.patternKey
      }));
    }
 iter(this.tree.treeModel.roots);
console.log(arr)

Currently there's no built-in iteration over treeNodes, but I can add it.
Something like this maybe:
treeModel.forEachNode((node) => ...)

?

ye, or treeModel.findNodes((node) => ...)
Could you also check (https://github.com/500tech/angular2-tree-component/issues/98#event-873634289) about _calculateExpandedNodes() to recreate the state but on an async nodes?

Hi,
tree.treeModel.filterNodes((node: TreeNode) => searchNodes(node, text), false);

If searchNodes here always returns true, then you nodes are not hidden and you can make a comparison in it to save matching nodes. Imho there is no really need of a second function.

We now have a doForAll method that iterates over the tree

Hi,
can you please post a full example about using filter?


Environment variables helper

Issue https://github.com/microsoft/Power-Fx/issues/2416.

✅ No public API change.

✅ No public API change.

✅ No public API change.


Provides a bug for Invalid hook call

The bug caused by dependencies.
Fix dependencies (reactandreact-dom have moved to peer.)


Summary metrics for AUC, FNR, TNR.

:+1: feel free to hit the pretty green "Merge pull request" button to merge your changes into the master branch.


Store digest of latest image in ImagePolicy status

TBD

[ ] add controller tests for digest fetching
[ ] add tests for the new internal/registry package

API changes
The new API field .status.latestDigest in the ImagePolicy kind stores the digest of the image referred to by the the .status.latestImage field.
This new field can be used to pin an image to an immutable descriptor rather than to a potentially moving tag, increasing the security of workloads deployed on a cluster.
The goal is to make use of the digest in IAC so that manifests can be updated with the actual image digest.
Implementation notes
ImagePolicyReconciler now fetches the digest of each image+tag after applying the policy for each ImagePolicy. To accomplish this it issues a HEAD request against the registry for the latest tag (after applying the policy) with the response carrying the digest in the headers.
closes #87
closes #214

@darkowlzz I pushed a much more lightweight approach where the ImagePolicyReconciler does the digest fetching now so that only the digest for the latest tag is fetched.

Next steps:

let IRC always reflect the current digest in the status
introduce .spec.recordDigest (default false) into ImagePolicy so that the controller records the digest in the .status field. Setting this to true makes the controller reconcile the given ImagePolicy at the interval defined in the associated ImageRepository's .spec.interval field.

Small nit: reflectDigest to follow the theme of "image reflection"?

@stefanprodan @hiddeco @darkowlzz this is now ready for another round of reviews, please.

Leaving a few initial comments after the first pass. I still need to manually test it more.
I've unresolved some of my old comments about missing license headers. Please have a look at them again.
I would like to bring some attention and discuss about the new v1beta3 API that's introduced in this change. I wasn't aware of the new API version before, not sure if any detailed discussion happened before. I found just https://github.com/fluxcd/image-reflector-controller/pull/368#discussion_r1274465810 which talks about the potential need for a new version. But looking at the changes, I don't think we need to introduce a new version. Having done it once for v1beta2 API, I know that it's a lot of work to introduce a new API version, but at the same time, it's also not so desirable for the users to have new API versions frequently, unless there's really a need for it.
Running a diff between the old and new ImagePolicy API:

A new field .spec.digestReflectionPolicy is introduced. We usually introduce new fields in the same API version.
Two status fields .status.latestImage and .status.observedPreviousImage were replaced by their new reference based alternatives. Since this is not a change where the users have to update the object spec, in the past, we usually handled such status changes within the controller without introducing a new API version. In SC, we did it for various fields in the status a couple of times. We didn't consider new status fields which are improvements over old fields to be a reason for new API version. We usually keep the old field, mark it as deprecated, but continue to populate it with values and at the same time write the new status fields. And when we go the the next API version, we drop the old fields.

If we are to follow what we've done before, I don't think we have a need to introduce a new API yet. But I may be wrong. Am I missing something?
Also, a new API version is a major change. It'd be good to at least mention it in the PR description to make the scope of this change more clear. I'd consider it critical as we need to perform a lot of upgrade testing whenever we introduce new API versions.

@darkowlzz i asked whether we'd be ready to introduce a new API version 4 weeks ago and no one objected. Coming back to this at this point, 4 weeks later is hard for me to comprehend.

BTW, I ran GCP integration test against this branch to make sure login continues to work https://github.com/fluxcd/image-reflector-controller/actions/runs/6090482584/job/16525378616 . The old integration tests only check if ImageRepository was able to fetch tags. We can extend the test to also create an ImagePolicy and check if it fetches the digest to verify that it's able to authenticate.

Good point. I created a separate issue for this.

@darkowlzz all comments are addressed. Please take a look.

@makkes Hi, As you did all the work on this PR and the one in image-automation-controller (thank you)  Is this something you still working on ?  if not,  should I try to understand more what is missing and write some change or is there any plan to make this feature happens ? thank you


fix: loadPreprocessor from both  configFile path and cwd fix(#2612)

Description
close  #2612

Additional context

What is the purpose of this pull request?

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

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

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

how about this PR, need I to resolve the conflicts?

how about this PR, need I to resolve the conflicts?

Yes please

Thanks for the PR @HomyeeKing, closing as it looks like #3988 was merged fixing #2612


Add polyline and earth support

add polyline and earth support.
add LngLat#approxEquals .

These are great changes. I'll target a 0.0.5 release in favour of 0.0.4 given there are a lot of changes

These are great changes. I'll target a 0.0.5 release in favour of 0.0.4 given there are a lot of changes

we'll also need to add TypeScript bindings

we'll also need to add TypeScript bindings

I think we'll have to do a quick consistency clean-up of the error messages as well. I'm happy to make these changes.

I think we'll have to do a quick consistency clean-up of the error messages as well. I'm happy to make these changes.

I'm going to merge this into a local repo branch so I can add PR changes.

I'm going to merge this into a local repo branch so I can add PR changes.


Fix chocolatey artifact package installation scripts

Added better error handling for startChocolatey.ps1
Updated all chocolatey artifact definitions to correctly call PS script to handle exit codes.
Implemented fix to work in Windows 2016.

LGTM


Neurons are being created that directly connect sensors to actions

No sensor should directly connect to an action - it defeats the purpose of having the internal nodes

This issue was created from coming back after a long time and forgetting this was an intentional design decision


Adding org-publish config.

Here's a rough version of an org-publish config. I haven't figured out how to get the org-to-rss functionality working, though, and the configuration assumes a particular directory structure:
Source Directories

~/work/website/
~/work/website/assets/
~/work/website/posts/
~/work/website/feed/

Target Directory

~/public_html/

I can't accept the PR itself (because it's a private module), but this is an excellent reference. I'll look into it next weekend and integrate it into lang/org. I'll see if I can get org-to-rss working too.

That's perfectly fine. I figured this would be more useful to you as a reference implementation than a direct patch. In any case, this config needs a little more work. The html-head, html-head-extra, etc. values need to point to functions if my config is going to read HTML from partials.

Gonna close this PR. Please expect another one tonight once I've finished testing/debugging a new iteration suited for public distribution.


fix: set dashboard duration to 60s

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Channel plays dashboard url or a fallback image is a url is not found
https://github.com/user-attachments/assets/b26b56dd-307c-4afb-9f36-d28d48bd08ae
Channel: https://adobe.sharepoint.com/:w:/r/sites/HelixScreensProjects/_layouts/15/Doc.aspx?sourcedoc={ADBBED9E-6552-429D-8171-985AEDBBDD63}&file=dashboard-images.docx&action=default&mobileredirect=true
Fix #
Test URLs:

Before: https://genai-analytics--dx-recognitions--hlxscreens.hlx.page/content/screens/org-amitabh/dashboards/analytics-genai-dashboard/dashboard-images
After: https://dx-grafana--dx-recognitions--hlxscreens.hlx.page/content/screens/org-amitabh/dashboards/analytics-genai-dashboard/dashboard-images

psi checks failing due to error in lighthouse score. Adding a loading spinner might help.

The grafana icon is acting as a spinner here. Anyway to include this as a spinner is LH metrics?


[Bug] Wrong behavior of manually located Dropdown

I have some interest in naive-ui and am browsing the documentation. This error occurs when I tried the demo in the documentation.
Environment Info

Naive UI version: 2.11.4
Browser Info: Edge 91.0.864.41
System Info: Windows 10

Reproduction link
https://www.naiveui.com/zh-CN/light/components/dropdown
Steps to reproduce
Right click in the green square more than three times.
For the first two click, the dropdown component opens where I clicked. But from the third click, it will never change position.

What is expected?
Maybe change the position?
What is actually happening?
See above.

I also tried the demo in the sandbox. I noticed that the xRef.value and yRef.value changed as I clicked, but the position of the component did not change. But I am new to vue3, so I can't locate where is the problem.

It's about position sync timing.

没想到隔壁的同学会看这个😂

没想到隔壁的同学会看这个😂

😄
刷知乎看到的，觉得做的很好，我又正好最近开始学习Vue。
好看的Vue3组件库，还有膜的成分，当然要支持一个XD


Any where or find clause with more than 1000 keys will fail with an exception

I'm attempting to do a lookup to Cassandra where I have greater than 1000 keys.  Example:
MyItem.where(the_key: keys).to_a
This fails every single time with the following exception:
NoMethodError: undefined method `name' for nil:NilClass
Stack trace:
0: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:796:in `range_key_name' 1: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:659:in `next_batch_from' 2: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:598:in `find_rows_in_batches' 3: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:569:in `find_each_row' 4: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:533:in `find_each' 5: /data/myapp/releases/20151117002754/vendor/bundle/ruby/2.2.0/bundler/gems/cequel-2803f748dcd4/lib/cequel/record/record_set.rb:517:in `each'

I added a failing spec to reproduce this: https://github.com/Geesu/cequel/commit/ff4d1106d270c890693a1201514e0f8151ab6ebf

I had the same problem, I think it's due to the fact that Cassandra uses 'limit 1000' by default. A temporary fix (for us) was to add '.limit(100000)' to the query (which we know will never reach that size).

Have you noticed any issue with performance? We actually ended up doing this:
https://gist.github.com/Geesu/36cbb67bedb194a19a48
For this use case we didn't need to worry about specifying the key as it was always the same.

Not really, because the size of the problem-query is about 2000 maximum, so not so large to cause performance issues.

I've encountered the same problem on a collection size of ~30 000 records, where
MyModel.select(:column1, :column2).to_a

throws
Don't know how to cast nil to a UUID

but adding the id column to the select seems to solve the issue:
MyModel.select(:id, :column1, :column2).to_a


Try to connect without system proxy

Since Qt5.8 system proxies are in use. After migration  to Qt5.12 TS can encounter problems in classrooms controlled by nerdy admins.

Download:
Environment: QT=5.12, ARCH=64, PYTHON_PATH=C:\Python35-x64
installer/trik-studio-installer-master-x86_64-auto.zip
installer/trik-studio-installer-master-x86_64.exe
trik-studio-master_qt5.12_x86_64.zip
Environment: QT=5.12, ARCH=32, PYTHON_PATH=C:\Python35
installer/trik-studio-installer-master-i686-auto.zip
installer/trik-studio-installer-master-i686.exe
trik-studio-master_qt5.12_i686.zip

Download:
Environment: QT=5.12, ARCH=64, PYTHON_PATH=C:\Python35-x64
installer/trik-studio-installer-master-x86_64-auto.zip
installer/trik-studio-installer-master-x86_64.exe
trik-studio-master_qt5.12_x86_64.zip
Environment: QT=5.12, ARCH=32, PYTHON_PATH=C:\Python35
installer/trik-studio-installer-master-i686-auto.zip
installer/trik-studio-installer-master-i686.exe
trik-studio-master_qt5.12_i686.zip


[$1000] Web - Compose box is distorted and messages are not loaded on reload after expand in compose box

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the NewExpensify app at https://staging.new.expensify.com
Click on an existing compose box or create a new compose box from a chat or task
Shift enter in compose box to enable expand button > press enter a few times to make the compose box window wide
Click on expand button
Reload and observe that expand button and + button in compose box are distorted and app does not load the chats

Expected Result:
App should load the chats and display expanded view on reload when we expand compose box and reload
Actual Result:
App does not load the chats and compose box is distorted when we expand compose box and reload
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[X] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.33-4
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/f330c59b-b2a4-4b96-919e-bfffd8b8bbe9
https://github.com/Expensify/App/assets/93399543/b522fc37-a160-41d2-a3f1-9d9942c6c140
Expensify/Expensify Issue URL:
Issue reported by: GH handle - @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687948877344299
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01cb137372e1458408
Upwork Job ID:<PHONE_NUMBER>237825024
Last Price Increase: 2023-06-30

I can reproduce it - seems to only be affecting Mac/Chrome/Safari. Adding external label

Hi,
I am from Callstack - an expert contributor group
I start to investigate this issue

Hi @Christinadobrzyn
Am I able to continue my investigation?
I was able to reproduce this issue and started some investigation.

Found some dependency between the isSidebarLoaded and isComposerFullSize flags.
Looks like isComposerFullSize prevents updating the isComposerFullSize if they are placed in the same component.
Created Slack thread related to this behavior.  https://expensify.slack.com/archives/C01GTK53T8Q/p1688570107740179

Hired in Upwork:
Internal job: https://www.upwork.com/ab/applicants/1674819530237825024/job-details
External job: https://www.upwork.com/jobs/~01cb137372e1458408
@aimane-chnaif as C+
@dhanashree-sawant as reporter
Let me know when we should add an eng label @aimane-chnaif

Found a few ways how to fix this issue.
I continue my investigation by looking for a better one.

Found a  better solution how to fix this issue.
I am preparing the proposal.

@pasyukevich is preparing the proposal!

Proposal
Please re-state the problem that we are trying to solve in this issue.
The problem we are trying to solve is the constant loading state for the content of the report after expanded composer and page reloading.
What is the root cause of that problem?
This issue is connected with Onyx behavior. It does not work as expected.
withOnyx HOC does not update boolean values that are initialized from the storage for components that are mounting not first. (I was able to reproduce constantly the same behavior in any components except the root - Expensify.js)
This reproduces in case there are boolean values that are already defined in the indexDb storage and stay the same till the full page rendering. (In such case another value, that was actually updated, would not be updated in the described component and will stay the same as the initial value)
The report loading state depends on the isSidebarLoaded value. To show content the isSidebarLoaded should be true.
In this flow isSidebarLoaded stay false inside the report while actually it is already updated to true for others.
In this case, isComposerFullSize blocks any updates of the isSidebarLoaded value.
I was also able to reproduce this with the collapsed and expanded composer. (it occurs when reportIsComposerFullSize_... is defined with value true/false/undefined in the indexDB for the current report)
Any of the proposed changes can be only a kind of workaround. I consider that after such fixes this issue should be fixed inside the Onyx library.
What changes do you think we should make in order to solve the problem?
Disable initialization of the isSidebarLoaded flag with stored value in the withOnyx hook by adding "initWithStoredValues: false" (ReportScreen). In this case, all updates will be triggered normally.
What alternative solutions did you explore?
Pass isSidebarLoaded from the upper component.

I guess this issue is related to this one - https://github.com/Expensify/App/issues/22122
Based on the information that I got from the issue description and Slack thread to the issue I assume that the root cause of the problem is the same - Onyx library. I am more than sure that it can be fixed in the same way as I described here. (before it will be patched on the Onyx side)

Asking for a review of combining these issues - https://github.com/Expensify/App/issues/22122#issuecomment-1629726677

Based on the information that I got from the issue description and Slack thread to the issue, I assume that the root cause of the problem is the same - the Onyx library. I am more than sure that it can be fixed in the same way as I described here. (before it will be patched on the Onyx side)

Sounds good to me. I'll hold the other issue.

I'm happy to go ahead and assign you @pasyukevich. It would be great if you can raise one PR with the fix (linking it to this issue and the Emulator issue), and depending on how many other potential instances of the initialization bug maybe we can bundle the others into the same PR.

@Julesssss
After implementing and checking the proposed approach I found out that the main approach broke the isSidebar logic on mobile/mobile web platforms.
Rechecked the alternative solution using the same flow - everything works well. To fix this issue, the isSidebar flag should be passed from the upper component (ReportScreenWrapper).
At the same time, the main proposal should work well for the other issue that is connected to the splash screen.
I believe that both approaches are workarounds.
After the fixes, I want to continue the investigation with the Onyx library and fix the root cause. Once the root cause is fixed, both of these fixes should be reverted.
Can I continue with this updated direction?

Hey @pasyukevich. Given the issues aren't suuuuuper critical maybe we can just hold in that case and focus on the underlying issue?

Sure, @Julesssss. In this case, I will focus on the investigation of the underlying issue.

Cool. I'll keep you assigned and will just put a hold on this for now.

Hi @Julesssss,
I'm not able to reproduce this issue locally and on the stage after the update of the ReportScreenWrapper to a functional component. (Now it has more re-renders and they just force React to update the ReportScreen.)
However, I'm still able to reproduce this issue elsewhere.
I'm continuing my investigation of the underlying issue by looking for a root cause.

I'm going to be ooo until August 31st so going to unassign and assign a new teammate.
At this time, we're on hold looking for the root cause - I'll assign this back to me when I'm back.

PR in draft still

@pasyukevich Any success in uncovering the underlying cause?

@conorpendergrast I've identified the root cause. As previously suspected, the issue is linked to Onyx updating the flow during loading.

@Julesssss Should I proceed to open a separate issue specifically for the Onyx repository and formulate a proposal within that context?

Hey @pasyukevich, no we can discuss that here! Please share your findings

@Julesssss
Issue connected with Onyx flow.

It becomes reproducible when the state is updated with value before the setWithOnyxState call.
Step-by-step flow  based on this issue (ReportScreen):

1. withOnyx setState called with ({ isSidebarLoaded: true }) while loading: true. (this.state = { loading: true, isSidebarLoaded: true })
2. setWithOnyxState called with isComposerFullSize: true
3. setWithOnyxState checked that loading: true and ignored the current state. (this.state = { loading: true, isSidebarLoaded: true })
4. Updated value of this.state with   {...this.tempState, loading: false}; (this.state = { loading: false, isSidebarLoaded: false,  isComposerFullSize: true, ………… } )
So in this flow updated state was ignored, I was able to fix this problem just by updating this.setState inside the setWithOnyxState with the additional spreading of the current state.
This issue is already not reproducible on the ReportScreen but I’m able to constantly reproduce that behavior if move the component with the same two flags upper the ReportWrapper.

Excellent, thank you! Please go ahead and raise the PR and we can review

Hey @pasyukevich, let us know when you have a PR ready for review 👍

Hi @Julesssss,
The PR is ready for review

@aimane-chnaif
Since I posted the message you forwarded, I haven't been able to reproduce the exact issue. However, I did encounter similar instances of broken flow in other areas.
Currently, I can't replicate it elsewhere in the latest app, but I can reproduce the same behavior from my forked branch that uses the latest Onyx library. Therefore, I believe we still need to fix the underlying cause to prevent future occurrences.
The reproduction steps: https://github.com/Expensify/react-native-onyx/pull/283#issuecomment-1653441265

It looks like work is ongoing on this one via https://github.com/Expensify/react-native-onyx/pull/283, correct?

@Christinadobrzyn is back, so I'm unassigning!

Working on https://github.com/Expensify/react-native-onyx/pull/283

watching this PR - https://github.com/Expensify/react-native-onyx/pull/283

watching this PR - https://github.com/Expensify/react-native-onyx/pull/283

watching this PR - https://github.com/Expensify/react-native-onyx/pull/283

Hey @aimane-chnaif can you confirm if we're holding for this https://github.com/Expensify/App/pull/26305 or something else?

Hi @Christinadobrzyn, since this job is older then job mentioned in PR, will it be eligible for reporting bonus? If so then I already have the offer for this job, can you approve that before closing it?

Hey @Julesssss do you have any thoughts on paying for https://github.com/Expensify/App/pull/26274
@dhanashree-sawant yes, you will be paid are the reporter.

Hey @Julesssss do you have any thoughts on paying for https://github.com/Expensify/App/pull/26274

Yeah that's fair. Someone else created a PR and merged it before mine, but it would have been a valid review still.

Soudns good, sorry for the delay in payment.
I'll pay this tomorrow.
@aimane-chnaif I'm thinking we'll pay 25% for the work on the PR? Let me know if you feel the payment should be different based on the work you did.  thanks!

Yeah I agree. @Christinadobrzyn this was only not merged because our internal review was too slow. We should pay 100% IMO

Sounds good, sorry @aimane-chnaif I should've asked you what seemed fair.
Payouts due:
Issue Reporter: $250 @dhanashree-sawant  (paid in Upwork with this job posting - now closed)
Contributor: NA
Contributor+: $1000 @aimane-chnaif (please accept the offer in this Upwork posting )
Eligible for 50% #urgency bonus? N
Upwork job is here.

Hello @Christinabrzyn
I hope you are doing well.
While reading the job post on Upwork and I am very interested in this project.
I can fix this project on time with high quality ASAP.
Please, let's make a contract.

<EMAIL_ADDRESS>https://www.upwork.com/freelancers/~01bb384137b6dfa7e5

Just awaiting payment now

Thanks @aimane-chnaif paid you in Upwork based on this payment plan - https://github.com/Expensify/App/issues/21881#issuecomment-1741510292
Closing!


Add aria20

ARIA20
Website: https://arianee.org/
Etherscan: https://etherscan.io/token/0xedf6568618a00c6f0908bf7758a16f76b6e04af9
CoinGecko: https://www.coingecko.com/en/coins/arianee
Twitter: https://twitter.com/ArianeeProject
Discord: https://discord.gg/tTER79v
Telegram: https://t.me/arianeeproject
Github: https://github.com/Arianee
Medium: https://medium.com/arianee

What does mean pending community activity ? more holders ? more transfer ?
When can I ping you ?

@gnarco seems that community activity is here - can you solve conflicts, please?

Hi !
Awesome !
Just pushed update to fix conflict

@xrn


[Bug]

Device
Phone/Tablet
Operating System
Windows
Browser
Chrome/Edge/Chromium
Browser Version
124.0
Better xCloud Version
3.5.3
Reproduction Steps
Good evening, The game does not open and a screen appears saying "we will be back soon". I tested other browsers without scripting and it worked. Does not start on the computer (edge browser).

If you are using Edge beta, try using the stable version.

If you are using Edge beta, try using the stable version.

The same has happened to me, edge version: 124.0.2478.51
not a test/dev/canaryan version
https://www.youtube.com/watch?v=kJ6O6PSMNgE
https://www.youtube.com/watch?v=GjFDEm3KLLM
Better xClooud 3.5.3
cleaned cookies, login again, same effect.

This sometimes helps to make things work again.

UA works perfect as default, but another as edge fail, thank u :D

The other UA profiles are about simulating other systems and/or browsers than what you are actually using. So if you are really using Edge on WIndows, there is no real reason to use the "Windows + Edge" UA profile. "Default" will use the real UA string of your installed browser. And it's recommended to always try this setting first and only change the UA profile if you have problems.


Anchor Links

This isn't an issue so much as an unintended, undocumented "feature".  I've discovered a neat url trick you can perform using Pico and HTML Anchors.  I haven't tried Pico 1.0 yet, so I'm only assuming it will still work with the new version.
Create a markdown file with no content, only metadata.  Give it a file name that contains a "#" followed by the name of an anchor on an existing page, for example "#anchor.md" or "page#anchor.md".
This file will show up in the navigation as a page on your site and it will use the name you specified in it's metadata.  However, when you click on this link, rather than bringing you to this blank page you created, it will bring you to the "anchor" in the "page" you specified.
You can see this in action on my NotePaper Theme site. I'll be updating the theme soon for Pico 1.0, and I guess I'll find out for myself if this still works.
Given that this is kind of a neat trick / URL hack, I feel like it should be mentioned somewhere in the documentation.  I've found it really useful, and I feel like others would too.

This behaviour is confirmed to happen in Pico 1.0.0-beta.1 as well. Perhaps this discovery can be included in the Creating Content section of the docs?
The theme looks great, btw @smcdougall :smile:

Nice hack. Same for the theme, looks great! :+1:
Unfortunately this reveals a practically relevant bug: The missing urlencode() in Pico::getPageUrl() (note to myself: It should be rawurlencode()...). Whereas the anchor sign (#) has the described, not so bad side-effect, ampersand (&) and question mark (?) break Pico - which one depends on enabled URL rewriting. Both are commonly used characters for page titles.
Therefore @smcdougall, I've to tell you that we have to fix (remove) this with the final Pico 1.0.0 :unamused:
Besides the possibility of writing a (unnecessary complex and very slow) plugin, I suggest you to use a toc meta header to implement TOCs. That's a pretty common solution for Markdown files. We're using the same technique on our website.
Example:
---
toc:
    item-on-level-1:
        _title: Item on Level 1
        item-on-level-2a: Item on Level 2 (a)
        item-on-level-2b: Item on Level 2 (b)
    another-level-1-item: Another Item on Level 1
---

    {% for sectionKey, section in meta.toc %}

            {% if section._title %}
                {{ section._title }}

                    {% for subSectionKey, subSection in section if subSectionKey != "_title" %}

{{ subSection }}

                    {% endfor %}

            {% else %}
                {{ section }}
            {% endif %}

    {% endfor %}

By the way: When a toc meta header is no suitable solution for you, please don't hesitate to tell us what you're trying to achieve, we'll find a solution :smiley:

@PhrozenByte It's okay, I sort of figured this would happen.  Your solution sounds really robust though.  I looked over the sources of the Pico site and I'm pretty intrigued by the concept (especially by the "collection" folders).  Is there a resource you could link to that goes into more detail?

Our website is unfortunately not realized with Pico, but with Jekyll (quite similar software, just worse... The reason why I'm saying this is not because I'm a Pico developer...). This is a compromise we had to make: our project has no server, so we're relying on GitHub Pages, what either supports static HTML pages or Jekyll. We decided to use Jekyll, even with its downsides it's better than maintaining static HTML pages.
Pico doesn't have something similar to Jekylls "collections" concept, as far as I can tell their only reason to exist is that you can't get the rendered contents of a arbitrary page with Jekyll. With Pico you have this ability (e.g. {{ "sub/page"|content }}). With Pico you can simply use any folder to realize what a collection does in Jekyll. Actually you're already doing it with your great widget system :smiley:

Okay, I figured out what I wasn't understanding in your example.  I went back and looked at the 1.0 changelog again and noticed that you can now make any meta headers that you want without needing to write a plugin to parse them.  Nice Work.
Glad you like my widget system. :smile:  At some point, I'll probably rework it to use custom meta headers instead of dedicated folders.  "if meta.widget" seems a little more elegant than "if "/widgets/" in page.url".
Back to the point though, glad to have squashed a last-minute bug before 1.0.  I'll see if I can work in your solution for TOCs into my theme.  Going forward it'll be a better solution than a URL hack anyway.
Congratulations on 1.0.  Glad to see development on Pico continuing.  Keep up the good work! :+1:

Thank you! If you have any question which is not answered in our docs, please don't hesitate to open a new Issue :smiley:

@PhrozenByte Thanks again for that example code.  I was able to get it working and customized a bit.  It'll be a feature included in the next update of my theme.  This new ability to use custom meta headers together with your example of using a meta array has got me thinking of a ton of potential customization ideas!

@PhrozenByte I made it recursive! :laughing:
{% import _self as macros %}
{% macro rnav(toc) %}
  {% import _self as macros %}

    {% for sectionKey, section in toc %}

        {% if section._title %}
          {{ section._title }}

            {{ macros.rnav(section) }}

        {% else %}
          {{ section }}
        {% endif %}

    {% endfor %}

{% endmacro %}

Thought I'd share.  If you'd like, one of us can put it in the cookbook whenever that gets done. :smiley:

Done, thank you @smcdougall!

Well, that was quick.  Glad I updated my comment before you looked at it.  It originally had two bugs I hadn't caught yet.


Revisit issue enablement for the repositories

Need to revisit all the repositories which allow for issue creation and disable if not needed or deemed to combine with other repo issues.

We should AUDIT all repo's and figure out which ones have ISSUE creation enabled.
Then we should rationalize the list down to the smallest number
We need to do a project wide announcement (and SLACK) defining...

How we want users & community to self-manage ISSUES ```  - (already done in /community/CONTRIBUTING.md)
What repos have ISSUES enabled

Decided not to proceed with this approach.


Draft implementation of draft/setname

Quick and dirty implementation of this proposed spec. Nice and simple for us, shouldn't give any dramas from the looks of it.

Awesome!
It's too bad we can't call this "REALNAME".


Supporting multiple remotes from git pull

Is there any way to know what remote we're pulling from in Git LFS commands?
$ git remote add something <url>
$ git pull remote master
# git lfs smudge...

Git LFS has no idea what remote was pulled from in the smudge command, so it defaults to origin. I don't think the post-checkout hook will help either:

This hook is invoked when a git checkout is run after having updated the worktree. The hook is given three parameters: the ref of the previous HEAD, the ref of the new HEAD (which may or may not have changed), and a flag indicating whether the checkout was a branch checkout (changing branches, flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of git checkout. -- http://git-scm.com/docs/githooks

I think as a work around, we'll do the following:

Add remote support to git lfs fetch
Add git lfs pull which is basically git pull + git lfs fetch

@mhagger: Any thoughts?

This is probably a bad idea, but I'll toss it out anyway. Wondering if it's possible to parse .git/logs/HEAD (or whatever) from the post-checkout:
16108cee8a4e10edc2b36bb871289bb98a060008 77d3aacf3fdfd9a32fe8eb40647eb3e57307a7ae rubyist<EMAIL_ADDRESS>1435163862 -0500	pull dev master: Fast-forward

For git pull we could use GIT_REFLOG_ACTION=pull <remote> <branch>, but that is not the case to solve, git checkout is.
Btw., it's not only about supporting multiple remotes, it's also about supporting repos with a single remote which is not named origin. Git LFS doesn't support that use case.

@technoweenie: I can't think of any tricks to help here, unless perhaps there happens to be some magic environment variable that gets set before calling the filter.
I can understand the inconvenience of trying to use LFS with a remote that is not called origin. But it is easy to configure around that problem, I would think?
But I'm having a little trouble understanding how LFS could possibly work with more than one remote at the same time. There are many contexts when the filters are run without any connection to a remote. For example, I can git checkout $SHA1. Git can't know where that SHA-1 came from so how can it possibly know which of multiple LFS servers it should use to fetch large objects?
I think LFS is by its nature limited to working with a single LFS server per repository.

@mhagger, @technoweenie maybe the solution isn't deciding which LFS remote is correct per Git remote but having a series of them, potentially, which allow fallback to get the binaries as needed. Since the files are named uniquely based on content hashes it doesn't matter which LFS remote the content is fetched from, so long as it is available.
Perhaps only supporting a single default LFS remote on push is correct, because I cannot see how anyone would want to push to multiple if they didn't need to.

I haven't tried it, but we shouldn't have problems with push, as we know which remote is being pushed to. git lfs pre-push and git lfs push require both a remote as argument.

I'm a bit confused here.  Imagine the following use cases:

I want to store my repo on GitHub, but I want the large files to be stored on a local computer with ssh.  This avoids having to rack up GitHub bandwidth costs, for example.

I want to store my repo on GitHub with some of the large files (e.g. demo data), but I want some other large files (e.g. proprietary data) to be stored on another remote.

Are these two use cases supported with the current git LFS?
Is the following workflow possible?
git lfs pulls from the GitHub remote, and then pulls from a second remote if it is available.

I want to store my repo on GitHub, but I want the large files to be stored on a local computer with ssh. This avoids having to rack up GitHub bandwidth costs, for example.

Yeah, but not easily. You'll have to maintain a fair amount of stuff (SSH, custom git-lfs-authenticate script, custom LFS server).

I want to store my repo on GitHub with some of the large files (e.g. demo data), but I want some other large files (e.g. proprietary data) to be stored on another remote.

That's possible, by being careful about what branches you push to which remotes. Seems like it'd be easy to mess up.


Keyboard pops up automatically after app goes to background and comes back

Steps to Reproduce
I was able to reproduce in two scenarios

Go to https://wen-el-sahra.web.app/destination/Sunset . Use the search feature and search for The Broad. Click on book now, now minimise the browser and come back again. The keyboard will start to appear. After the keyboard appears like this, it will keep on automatically popping up on navigating to new routes or popping and going back to previous ones.

This issue is only happening if there are buttons before a form, otherwise this is not happening.
To test the above theory go to
https://wen-el-sahra.web.app/destination/BirthdayBachelor and select the first card named se and click book now and perform the above steps the keyboard won't appear.

Go to https://wen-el-sahra.web.app/destination/Sunset use the search feature and search for something. Minimise and come back to the app and the keyboard will appear automatically.

This behaviour may be device specific as previously a similar issue was solved and closed in flutter framework that was device specific. Below are the specifications of the test device. I am testing on a real android device.

Expected results:
Keyboard should not auto pop up on app coming back from background on android
Actual results:
Keyboard automatically pops up on app coming back from background on android

Code sample

Logs

[√] Flutter (Channel beta, 2.7.0-3.0.pre, on Microsoft Windows [Version 10.0.19043.1288], locale en-IN)
    • Flutter version 2.7.0-3.0.pre at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c19845a8c3 (4 days ago), 2021-10-19 10:58:42 -0700
    • Engine revision bbba2b2437
    • Dart version 2.15.0 (build 2.15.0-178.1.beta)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\shata\AppData\Local\Android\Sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = C:\Users\shata\AppData\Local\Android\Sdk
    • Java binary at: D:\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.2)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.11.31624.102
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at D:\Android\Android Studio
    • 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
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] IntelliJ IDEA Ultimate Edition (version 2020.3)
    • IntelliJ at D:\IntelliJ IDEA 2020.3.1
    • Flutter plugin version 54.0.3
    • Dart plugin version 203.7759

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19043.1288]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 94.0.4606.81
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 94.0.992.38

• No issues found!

Video of the bug
https://user-images.githubusercontent.com/67138059/138547170-676c8fca-e1c3-41b1-8f36-781e831945b2.mp4

Not reproducible on stable 2.5.3

minimal code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: const Home(),
    );
  }
}

class Home extends StatelessWidget {
  const Home({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Material App Bar'),
      ),
      body: Center(
        child: ElevatedButton(
          child: const Text('Open Dialog'),
          onPressed: () {
            showDialog<void>(
              context: context,
              barrierDismissible: false, // user must tap button!
              builder: (BuildContext context) {
                return AlertDialog(
                  title: const Text('Test'),
                  content: const TextField(),
                  actions: <Widget>[
                    TextButton(
                      child: const Text('Search'),
                      onPressed: () {
                        Navigator.of(context).pop();
                      },
                    ),
                  ],
                );
              },
            );
          },
        ),
      ),
    );
  }
}

@LongCatIsLooong
Looks this is a regression from https://github.com/flutter/flutter/pull/86312
The keyboard doesn't pop up if we use any autofill-hint on the Android web, instead of returning AutofillConfiguration.disabled when no autofill hints
(source)
One way to fix is temporarily reverting autofill changes from material/text_field.dart and cupertino/text_field.dart or fixing the actual issue which I am not sure I can track the source of. Perhaps it is coming form flutter engine
TextField without autofill selected
https://user-images.githubusercontent.com/48603081/142895902-73592706-f073-44c2-bf57-f6b87cf9eb1a.mp4
TextField when autofill is selected
https://user-images.githubusercontent.com/48603081/142896042-ab83f7c4-3018-4d1e-95ff-1e2dd704296d.mp4

@yjbanov @mdebbar This seems to be a web bug, routing this to you guys.

I've run into possibly related issue with software keyboard re-appearing after using Autofill to pick some value. I'm unable to put some MVC or screen recording of this behavior right now, but the scenario is like this:

User clicks on username field, keyboard appears with some autofill hints
User picks entry to autofill
Both fields for username and password are filed properly, they also loose focus, but keyboard - you can see keyboard hide animation just after selecting autofill entry, but then it reappears
When user clicks on login button it'll call primaryFocus?.unfocus() - but without success, keyboard is still visible.

Looking at value of primaryFocus it is set to FocusScopeNode#7d3a1(_ModalScopeState\u003cdynamic\u003e Focus Scope [PRIMARY FOCUS])(context: FocusScope, PRIMARY FOCUS) when autofill was used, and to FocusScopeNode#e48dd([PRIMARY FOCUS])(context: FocusScope, PRIMARY FOCUS) when user wasn't using autofill.

Logs from session without autofill, user types values by hand, and after logging in "Save password?" appears
[GoRouter] pushReplacement /login
I/ImeTracker(18549): <<appId>>:1436197c: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
I/AssistStructure(18549): Flattened final assist data: 736 bytes, containing 1 windows, 4 views
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:1436197c: onShown
I/ImeTracker(18549): <<appId>>:ae1e3f9b: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:ae1e3f9b: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:e562268f: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:e562268f: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:5e7e3a52: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:5e7e3a52: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:3e551bf7: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:3e551bf7: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:6b24bfe7: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:6b24bfe7: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:5d8fd680: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:5d8fd680: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:d685255e: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:d685255e: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:d81c81bd: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:d81c81bd: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:e3807d17: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:e3807d17: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:1d3e7756: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring off
W/WindowOnBackDispatcher(18549): sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@251008021 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@1337c79
[login_username_password.dart] trying to unfocus
                               {
                                 "primaryFocus": "FocusScopeNode#e48dd([PRIMARY FOCUS])(context: FocusScope, PRIMARY FOCUS)"
                               }
[root_app.dart] AppLifecycleState changed to: AppLifecycleState.inactive
I/ImeTracker(18549): <<appId>>:6c677ab0: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
I/ImeTracker(18549): <<appId>>:1d3e7756: onHidden
W/AutofillManager(18549): setSaveUiState(36858526, false) called on existing session 36858526; cancelling it
[root_app.dart] AppLifecycleState changed to: AppLifecycleState.resumed

Session with autofill
[GoRouter] pushReplacement /login
I/ImeTracker(18549): <<appId>>:bb1186b6: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
I/AssistStructure(18549): Flattened final assist data: 736 bytes, containing 1 windows, 4 views
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:bb1186b6: onShown
I/ImeTracker(18549): <<appId>>:e6dc516e: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:e6dc516e: onCancelled at PHASE_CLIENT_APPLY_ANIMATION
I/ImeTracker(18549): <<appId>>:9a957930: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring off
W/WindowOnBackDispatcher(18549): sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@251008021 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@d526b6b
I/ImeTracker(18549): <<appId>>:e3b844e: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
I/ImeTracker(18549): <<appId>>:9a957930: onHidden
I/ImeTracker(18549): <<appId>>:2e85a316: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): <<appId>>:2e85a316: onShown
[root_app.dart] AppLifecycleState changed to: AppLifecycleState.inactive
W/WindowOnBackDispatcher(18549): sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@251008021 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@dc89c37
[root_app.dart] AppLifecycleState changed to: AppLifecycleState.resumed
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring off
I/ImeTracker(18549): <<appId>>:e3ffea4c: onRequestShow at ORIGIN_CLIENT_SHOW_SOFT_INPUT reason SHOW_SOFT_INPUT
D/InputMethodManager(18549): showSoftInput() view=io.flutter.embedding.android.FlutterView{b899532 VFE...... .F...... 0,0-1080,2274 #2 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
W/WindowOnBackDispatcher(18549): sendCancelIfRunning: isInProgress=falsecallback=ImeCallback=ImeOnBackInvokedCallback@251008021 Callback=android.window.IOnBackInvokedCallback$Stub$Proxy@dc89c37
D/InputConnectionAdaptor(18549): The input method toggled cursor monitoring on
D/InsetsController(18549): show(ime(), fromIme=true)
I/ImeTracker(18549): uid(10564):c660837f: onCancelled at PHASE_CLIENT_ANIMATION_CANCEL
I/ImeTracker(18549): <<appId>>:e3ffea4c: onShown
[login_username_password.dart] trying to unfocus
                               {
                                 "primaryFocus": "FocusScopeNode#7d3a1(_ModalScopeState\u003cdynamic\u003e Focus Scope [PRIMARY FOCUS])(context: FocusScope, PRIMARY FOCUS)"
                               }

If you are using any OnBoarding Functionality And or using GETX
So when you move from 1 page to another where you no longer require on that page use:
Example::
Get.offAll(const LoginScreen())?.then((value) async {
Get.delete();
});
This has solve mine.
Hope it helps someone.

If you are using any OnBoarding Functionality And or using GETX So when you move from 1 page to another where you no longer require on that page use: Example::
Get.offAll(const LoginScreen())?.then((value) async { Get.delete(); });
This has solve mine. Hope it helps someone.

this workaround doesnt work when you need the previous page.


Docker Integration

New repo on docker hub should be added: Create Docker Hub repo - Societal
New env var should be added to this GitHub repo: DOCKER_REPO that points to the docker hub repo created above.
Two more env vars should be added to this repo:
DOCKER_USERNAME
DOCKER_TOKEN

to make sure GitHub workflow agent has an access to publish images built.
P.S. Make sure all the env vars above are stored as a GitHub secrets.

@okalenyk, is this a problem that the check are failing? Should we fix this before merging?

@gfox1 If you merge the PR #23 then the check pipeline will get green for that PR. So you can merge the #23 before that - they're independent.

@okalenyk, new repo on docker hub has been added.
https://hub.docker.com/r/societal/societal-node


An runtime function for CamelCasedPropertiesDeep

Love this package. Is there any plan for implementing a runtime version of CamelCasedPropertiesDeep .
related to https://github.com/sindresorhus/type-fest/issues/375.

Also happy to make a PR if that's ok.

Check out: https://github.com/sindresorhus/camelcase-keys

Sad.
For ID, there's no problem.
For ReactDOM
CamelCasedPropertiesDeep will transform to be reactDOM
camelcase-keys will transform to be reactDom

https://github.com/sindresorhus/camelcase-keys/issues/88

This can be closed?


T265 relocation on an existing map

Required Info

Camera Model
T265

Firmware Version
<IP_ADDRESS>6

Operating System & Version
Win (8.1/10)

Kernel Version (Linux Only)

Platform
PC

SDK Version
2.32.1

Language
C++

Segment
Robot

Issue Description
I would like to know is there is a way that when the camera relocates on a loaded map it switches its coordinates to the 0,0,0 of the original map. I mean when the relocation event happens at the origin of the loaded map.
I know I could make that by saving the coordinates of the relocation event and then aplying a transformation to the actual device position, but I dont know if there is a way that the camera makes that by itself.

The camera does not do it. You have to do it by yourself. But it is possible :)
https://neilyoung.serveblog.net/jekyll/update/2020/02/13/an-application-of-the-intel-realsense-t.265.html


Add unit tests

The codebase is largely untested because it was built in a rapid prototyped "can this even work" style since I was dealing with new technologies.  As the shape of the system has become clearer, it's time to add unit tests to prevent regressions.
Here are the main areas that can be tested
Transform interpreter

Does it properly perform the transformations?
Can we add a Command and then use it
What do errors look like?
Can we build in testing to the Command class?

Py_Code_Gen interpreter

does the generated python code produce the same output as the corresponding transform python code when evaled

Widget python side

Do observers get properly called... can we set a property/model attribute and verify that the proper observer was called and state exists as expected.

Widget ts code (widget side)

can we instantiate the widget with known values and verify that no errors exist
do the sent python types match the typescript types expected

widget react code

Can we instantiate and display each component without errors
do the weird setter gymnastics work properly with a widget-ts analogue (add explanation)

In progress

Done.  test via pytest


Breadcrumb appearing on JP homepage

@sdmcraft

Fixed by adding nobreadcrumb flag true in metadata

Thank you @jindaliiita


Any plans to support simulate transactions from account contracts?

In addition to the current estimate_fee and send API, would be great to have a simulate endpoint that automatically signs for the transaction.

Yep that sounds reasonable. Will work on this.

I could just build on the current Account trait for this feature, but I'm not happy with how the trait itself looks right now. I'm working on a revamp of the Account trait before implementing this. The new interface should be a lot cleaner.


tex2chtml is not a function in MathJax v3

I am using MathJax v.3.2.0 in a Nuxt project, in which I use the MathJax Node API to render TeX to CHTML on the server-side.
const MathJax = await require('mathjax').init({
  tex: {
    inlineMath: [['$', '$']], displayMath: [['$$', '$$']], packages: ['base'],
  },
  loader: { load: ['adaptors/liteDOM', 'input/tex', 'output/chtml'] },
});

const rendered = MathJax.tex2chtml('\\frac{1}{x^2-1}', { em: 12, ex: 6, display: false });
console.log(rendered.outerHTML);

But I get the error MathJax.tex2chtml is not a function.
Strangely, if I replace tex2chtml with tex2svg it outputs the SVG perfectly. I didn't find any extra instructions for CHTML in the Node examples, is there anything extra that should be done in order for CHTML to work?
Technical details:

MathJax Version: 3.2.0
Client OS: Windows 10 (1809)
Browser: Chrome 101.0.4951.54
MathJax 3.2.0 installed with npm (Node version 16.14.0)

The problem is a conflict between your const MathJax and the global MathJax that the mathjax component creates.  Try changing const MathJax to const mathjax or some other name and I think it will work for you.