feat(exposeConfig): nested properties

While working on #582, I've also looked into how to create exports for nested properties in the large tailwind configuration, and these properties can be accessed using exports in camelCase. There have been use-cases (for me at least) where I need a small part of the configuration, such as theme.screens or theme.colors.neutral instead of all of theme (which is quite big), so I can just do
import { themeScreens, themeColorsNeutral } from '#tailwind-config'

and that should do it!
I believe this isn't a major requirement right now, and may need feedback as well (hence I'm also putting this as a draft PR).
Edit: see changes at this point through - https://github.com/nuxt-modules/tailwindcss/compare/main...ineshbose:nuxt-tailwindcss-module:ba8bf7e2f3e1d907e0ab7b1a29a03dfd6d0bcde7

If this approach isn't desirable, potentially this can be altered to have each object as a module (eg #tailwind-config/theme)?
https://github.com/nuxt-modules/tailwindcss/blob/96adbbd676959ace17ef28885ec1a84b486cf636/src/module.ts#L163

Refactored to use templates instead (still need to look into type declarations). Example usage would be:
import screens from '#tailwind-config/theme/screens' // or import { _screens } from '#tailwind-config/theme'
import neutral from '#tailwind-config/theme/colors/neutral' // or import { _neutral } from '#tailwind-config/theme/colors'

Admittedly, these are a lot of files, so the previous approach can be considered if required.

Updated function to allow developers to choose how deep they want the templates to go. There's also a commented-out condition that can give the option to not create exports for single non-object values if required (tried to merge it with the previous condition using Object.entries(value) but doesn't work).

Sorry for the late answer, updated the level to start a 1 (which makes sense IMO, 0 being the whole tailwind.config).
This means tat exposeLevel: 2 will expose

And more, easy to check with http://localhost:3000/_vfs
I am happy with current state, could you please update the documentation to explain those changes and the benefits of it please?

Updated docs (also for inclusive language), and added a test. My concern is still with type definitions I feel!

Beautiful work!


Improve isDeeplyNestedType for homomorphic mapped types

This PR builds on #55638 to further improve tracking of deeply nested homomorphic mapped types. In particular, with this PR we handle "indirect" homomorphic mapped types like Pick, and we handle homomorphic mapped types applied to intersections.
Fixes #56138.

@typescript-bot test top100
@typescript-bot user test this
@typescript-bot run dt
@typescript-bot perf test this faster

Tests look good and performance is unaffected.


[IOTDB-3268] Add the Chinese version of TSDB-Comparison document

Description

There is an English version of TSDB-Comparison document. This pr adds a corresponding Chinese version, which would be more friendly to native Chinese speakers.
This pr also summarizes an overview table at the beginning of the docs, hoping saving the time of people who just want to have a glance.
This pr by the way happens to fix a very minor problem in the Zepplin-IoTDB user guide. Refer to "[IoTDB-3212] Cannot get the jar-with-dependencies as the Zepplin-IoTDB UserGuide says".

This PR has:

[ ] been self-reviewed.

[ ] concurrent read
[ ] concurrent write
[ ] concurrent read and write

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods.
[ ] added or updated version, license, or notice information
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
[ ] added integration tests.
[ ] been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

Hi, would you like to add this Chinese doc to our website?  You may refer the website js codes below.
https://github.com/apache/iotdb/blob/8b1ee93c51932d72cb7fd7c5268f40f7b3a74f25/site/src/main/.vuepress/config.js#L763-L777

Hi, would you like to add this Chinese doc to our website? You may refer the website js codes below.
https://github.com/apache/iotdb/blob/8b1ee93c51932d72cb7fd7c5268f40f7b3a74f25/site/src/main/.vuepress/config.js#L763-L777

Thanks, I was seeking how to add this to the website. Now I get it.


runtime_stoptheworld deadlock on ppc64le

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version go1.4.2 gccgo (GCC) 5.3.0 linux/ppc64le

What operating system and processor architecture are you using (go env)?

ppc64le
linux

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Unfortunately haven't been able to come up with a simple repro, but core dump and binary are provided (all of the interesting source information is within gccgo's libgo c implementation).

What did you expect to see?

Something other than a hard deadlock across all threads.  If this is an application derived deadlock, perhaps deadlock detection triggering.

What did you see instead?

All threads stuck in runtime_futexsleep without a timeout.
One thread is in runtime_stoptheworld, all other threads are blocked.  On inspection, the stoptheworld thread is waiting because one of the outstanding P's is still in Psyscall (runtime_sched.stop_wait == 1).  Values for that P:
(gdb) p runtime_allp[1][0]
$1 = {{key = 0}, id = 1, status = 2, link = 0x0, schedtick = 88, syscalltick = 10, m = 0x0, mcache = 0x3fff90df0898,
  deferpool = 0x0, goidcache = 37, goidcacheend = 49, runqhead = 21, runqtail = 21, runq = {0xc2094b0000, 0xc2094b0000,
    0xc20a10ba00, 0xc20a10c700, 0xc20a10d400, 0xc2094b0000, 0xc20a10e100, 0xc20a10e100, 0xc20a10e100, 0xc20bd8a000,
    0xc20bd8ad00, 0xc20bd8ba00, 0xc2094b0000, 0xc20d592700, 0xc2094b0000, 0xc2094b0000, 0xc2094b0000, 0xc20d590000,
    0xc20bd82d00, 0xc20d594e00, 0xc20b526100, 0x0 <repeats 235 times>}, gfree = 0x0, gfreecnt = 0,
  pad = '\000' <repeats 63 times>}

All of the other P's are in status 3, I.e. Pgcstop
I'm partly suspicious of the doentersyscall() edge, which seems to do a non-atomic load of runtime_sched.gcwaiting, which feels like it could race with the gc'ing thread:
// doentersyscall()
...
      runtime_atomicstore(&m->p->status, Psyscall);
      if(runtime_sched.gcwaiting) {
              runtime_lock(&runtime_sched);
              if (runtime_sched.stopwait > 0 && runtime_cas(&m->p->status, Psyscall, Pgcstop)) {
                      if(--runtime_sched.stopwait == 0)
                              runtime_notewakeup(&runtime_sched.stopnote);
              }
              runtime_unlock(&runtime_sched);
      }
...

Coredump with binary and goroutine stack output:
https://www.dropbox.com/s/3lht3xs4fgi7fub/hang_info.tgz?dl=0

I've written a smaller piece of code that seems to exhibit the same behavior. Running this with a higher GOMAXPROCS seems to make it more likely to deadlock. On the 80 core machine I'm running this on I run it with GOMAXPROCS=200. For me, it hangs somewhere between 15 and 60 seconds.
package main

import (
        "syscall"
        "fmt"
)

func main() {
        n := 200
        count := make([]int,n)
        for i:=0;i<n;i++ {
                go func(x int) {
                        for {
                                syscall.Nanosleep(&syscall.Timespec{ 0, 100} ,&syscall.Timespec{})
                                count[x]++
                                _ = make([]byte,1024)
                        }
                }(i)
        }
        for i := 0;;i++ {
                syscall.Nanosleep(&syscall.Timespec{ 1, 0} ,&syscall.Timespec{})
                fmt.Printf("%v %#v\n",i, count)
        }
}

With this patch, my reproo program no longer deadlocks.
[ec2-user@ubuntu1404-ppc-2 gabriel]$ diff  -u -r gcc-5.3.0 gcc-5.3.0-fix                                                                                diff -u -r gcc-5.3.0/libgo/runtime/proc.c gcc-5.3.0-fix/libgo/runtime/proc.c
--- gcc-5.3.0/libgo/runtime/proc.c      2015-04-29 21:32:07.000000000 +0000
+++ gcc-5.3.0-fix/libgo/runtime/proc.c  2016-04-01 16:04:01.471160881 +0000
@@ -2042,7 +2042,7 @@
        m->mcache = nil;
        m->p->m = nil;
        runtime_atomicstore(&m->p->status, Psyscall);
-       if(runtime_sched.gcwaiting) {
+       if(runtime_atomicload(&runtime_sched.gcwaiting)) {
                runtime_lock(&runtime_sched);
                if (runtime_sched.stopwait > 0 && runtime_cas(&m->p->status, Psyscall, Pgcstop)) {
                        if(--runtime_sched.stopwait == 0)

Thanks for tracking this down.


Splits stats pod into two subspecs

Closes #338
Splits the stats pod into two subspecs - UI and Services. This will help facilitate movement towards frameworks and improvement in code for use when not in a UI environment (or when operation aren't available like in WatchKit.)
Needs Review: @sendhil, @koke, @bummytime

Aside from one comment looks good to me @astralbodies

Thanks for reviewing @sendhil - I fixed the spacing issue.
@koke for now you can point the pod at the develop branch and specify only WordPressCom-Stats-iOS/Services in the Today Widget Podfile.

StatsGroup.h imports StatsSection.h which is in the UI subspec, so the Today Widget fails to build

D'OH! Thanks for catching! Reopening.


Settings v2 saves wrong value

Environment
PowerToys version: 1891bd494c32401e9531a6ff212ae82bcccff837
PowerToy module for which you are reporting the bug (if applicable): Settings

# Steps to reproduce
- Change value of any fancyzone color to  R 150 G 160 B 170 (96A0AA)

# Expected behavior
- Opacitiy settings should be displayed for each color should not be visible
- Saves RGB value

# Actual behavior
- Opacity settings are displayed for each color
- Saves ARBG value which causes fz to crush
"value": "#FF96A0AA"

Changing any color resets fancyzones_highlight_opacity.
Changing fancyzones_highlight_opacity resets colors (fancyzones_zoneHighlightColor, fancyzones_zoneBorderColor, fancyzones_zoneColor)


IndexError: tuple index out of range

when I run python train.py --conf_path=model_zoo/demo/conf.json . An Error occurs, anyone meet this error:
Traceback (most recent call last):
File "train.py", line 275, in
main(params)
File "train.py", line 227, in main
lm.train(optimizer, loss_fn)
File "~/NeuronBlocks-master/LearningMachine.py", line 156, in train
logits_softmax = self.model(inputs_desc, length_desc, *param_list)
File "~/anaconda3/envs/py35/lib/python3.5/site-packages/torch/nn/modules/module.py", line 477, in call
result = self.forward(*input, **kwargs)
File "~/NeuronBlocks-master/Model.py", line 357, in forward
inputs, lengths = transform_tensors2params(inputs_desc, length_desc, param_list)
File "~/NeuronBlocks-master/utils/common_utils.py", line 176, in transform_tensors2params
lengths[key] = param_list[length_desc[key]]
IndexError: tuple index out of range

Hi caijie，found that you are using python 3.5. currently we support Python 3.6. we are trying to the issue you met.

Hi caijie, this issue is caused by python 3.5.x, you can update python to 3.6.x .

Thank you!


history does not show an external payout that happened

https://gratipay.com/~simonmichael/history/ -> June 29, 2017 — Weekly Payday #265 shows no Outside activity, but I did receive $0.98 from gratipay to paypal on that day.
Related to #838.

(It is shown under July 6, 2017 — Weekly Payday #266 , but it happened on June 29).

Thanks for reporting, @simonmichael.

One of those was initiated by me (payday 266), the other (payday 265) by @whit537. Looks like this is due to https://github.com/gratipay/inside.gratipay.com/issues/1110#issuecomment-312103882. We had a bug that prevented us from being able to record paypal payouts in our database. It was fixed in the next week, and records added.
We could change the times on those records... Hmm, wonder if that would that mess with anything. I suppose we could try it out locally and run the 'check_accounts' cron to see.


"Janitor" command: clean up blank notes

Is your feature request related to a problem? Please describe.
My problem: I find myself creating blank notes relatively frequently in my workflow. My workflow tends to be: breakfast, then sit down and open up 2 daily journals: 1 for personal, 1 for work. Sometimes I don't write anything in them, but I do like to create them.
Describe the solution you'd like
a la doctor, a janitor command which cleans up blank notes. The command should ideally be able to run like Doctor (CTRL SHIFT P, Dendron: Doctor) or after X amount of time (i.e. a week) after the note was created/the day the journal entry was based off of.
Blank notes can be roughly described as:

Only has a header
Has content, but content just matches the template

Describe alternatives you've considered

Not creating notes until i'm actually going to write something in them.
Notes not saving notes until they have more than a header / diff from the template.
Lightweight templates + snippets

Additional context
n/a

What constitutes a "blank" note might get trickier over time if things like logic/conditionals for templates are introduced (i.e. weekday-only blocks).

Thanks for the feature request. Janitor is a great idea. I've been thinking of having a long running background thread that would run Dendron: Doctor on saved notes, do the sort of clean up you described, and in the future maybe auto-commit notes via git.
As for what constitutes a blank note, I think this will be different for different people. We would probably make this configurable on a global and a per-hierarchy basis. Configuration options I'm thinking of:

BlankFrontmatterCriteria: determine if note frontmatter is "blank"
BlankNoteContentCriteria: determine if note content is "blank"
BlankNoteCleaningSchedule: when Janitor cleans up a blank note

BlankFrontmatterCriteria:
- noFrontmatter
- noCustomFrontmatter
- noMatchRegex

BlankNoteContentCriteria:
- noContent
- noNonHeaderContent
- noNonTemplateContent
- noMatchRegex

BlankNoteCleaningSchedule:
- {num}{hours|days|weeks|months|custom}

Another alternative to consider (more of a tips-and-tricks):

Aim to have lightweight templates + lots of snippets.

This will help you avoid having too much unused cruft lingering around in notes.

@tsnieman love the suggestion about templates + Snippets. I find that really useful too. Also, blank notes are useful as a mechanism for keeping track of how long an idea/stub takes to flush out. Personally, I don't think we want to do too many hacks here but rather invest in a more general purpose "hooks" mechanism that's been talked about in Discord recently: https://discordapp.com/channels/717965437182410783/735365126227493004/837316216929517598


[ui] [build] Build the frontend for the native architecture

This modifies the build container in the multi-stage build to always use the native architecture, since the resulting JavaScript files are platform independent. This will still result in linux/amd64 and linux/arm64 images in the end, but the code will only have to be built once.

Going to just take the time hit and build it emulated for now for simplicity. Main builds should not be frequent


python311Packages.protoc-gen-swagger: init at b572618d0aadcef63224bf85ebba05270b573a53

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

The target version of grpc-gateway looks quite different. Is it still a valid package?

I needed this to package https://github.com/flyteorg/flytekit/. I now see that protoc-gen-swagger has been renamed protoc-gen-openapiv2. Let me check if this is actually being used in the upstream repository.


Fix incorrect replacement in markdown image links

Fix #26548
When the repo name is src:

/<user>/src/src/branch/ => /<user>/media/src/branch/

it should be:

/<user>/src/src/branch/ => /<user>/src/media/branch/

Please also check: if we are not inserting the image link into DB.

Please also check: if we are not inserting the image link into DB. <--- Less probable situation.

ok ,  but I'm puzzled about this unit test case that didn't pass

Please also check: if we are not inserting the image link into DB. <--- Less probable situation.

ok , but I'm puzzled about this unit test case that didn't pass

Your unit test cases are failing, you changed the path of image so you need to change in the unit test cases.
I am wondering, it should not affect in older versions of gitea.
https://github.com/go-gitea/gitea/actions/runs/5887628224/job/15967326590?pr=26562#step:8:112

Your unit test cases are failing, you changed the path of image so you need to change in the unit test cases.
I am wondering, it should not affect in older versions of gitea.

I am confused about this test case. For both test cases, the rendering before and after my changes in the page display is consistent:

 =>  http://localhost:3000/caicandong/wire-examples/media/branch/main/Link
=>http://localhost:3000/caicandong/wire-examples/media/branch/main/icon.png

Link

{{.Link}}

Your unit test cases are failing, you changed the path of image so you need to change in the unit test cases.
I am wondering, it should not affect in older versions of gitea.

I am confused about this test case. For both test cases, the rendering before and after my changes in the page display is consistent:

 =>  http://localhost:3000/caicandong/wire-examples/media/branch/main/Link
=>http://localhost:3000/caicandong/wire-examples/media/branch/main/icon.png

Can you push your code. I can take a look.

At first, I also considered to add /branch/, but it seems that we do not only have /branch behind /media/:
https://github.com/go-gitea/gitea/blob/c6b92c84fe5e4b1fad1711611d8a0d453fd7e311/routers/web/web.go#L1312-L1319
Is it ok that just support /branch here?

Is it ok that just support /branch here?

That's not my concern, I do think there's something wrong with this test case. For the current gitea it is actually the rendered result below.

 =>  http://localhost:3000/caicandong/wire-examples/media/branch/main/Link
=>http://localhost:3000/caicandong/wire-examples/media/branch/main/icon.png
And the test case is:
 =>  http://localhost:3000/caicandong/wire-examples/media/main/Link
=>http://localhost:3000/caicandong/wire-examples/media/main/icon.png

Check line

in  html_test.go

What I mean is that there is something wrong with the writing of this test case, the expected results are not the same as what I see on the gitea page. @puni9869 @yp05327
https://try.gitea.io/CaiCandong/abc/src/branch/main/README.md

// "/*" route is deprecated, and kept for backward compatibility

It seems that in old version the media link is /media/<branchname>
but now it is /media/branch/<branchname>

I see why this fix is not good.
As I have mentioned in https://github.com/go-gitea/gitea/pull/26562#issuecomment-1681820849
If you select to a tag or commit, the media link will become /media/tag/<TagName>
for example:
https://try.gitea.io/yp05327/testrepo/src/tag/testtag222

// "/*" route is deprecated, and kept for backward compatibility

It seems that in old version the media link is /media/<branchname> but now it is /media/branch/<branchname>

So, this test case TestRender_RelativeImages is outdated.

I see why this fix is not good.

I'm not saying that my current solution is right, I think we need to address this outdated test case first and then consider a good solution.

There are other places which replace /src/ with /raw/ for example which will fail too. The whole string replacing solution is buggy.

Maybe split string on /, replace at n-th position, then re-join.

No good solution for now, this bug only affects users or repositories with the name src.

No worries, You have tried , Appreciated for the great efforts.

I will post another solution.

Added a fix with #26745


Use v0.45.0 for controller image tag

This PR updates the controller image to 0.45.0
Other changes:

The monitoring port in the values file has been changed to 10254
The values schema for resources has been fixed
tests on kube-app-testing and go based integration tests have been replaced by tests running through app-build-suite

@piontec can you take a look at the tests? https://github.com/giantswarm/nginx-ingress-controller-app/pull/188/files#diff-ab211efb7db46ad971eb187ba932bc0f489ff32ca5c1ebdeb2cf3b7a42282661
I know the functional test is not perfect but a customer is waiting on the change @ced0ps did to the values schema. We can iterate on the test later if you don't see a show stopper

LGTMIT


Temp

Coverage remained the same at 100.0% when pulling 4242ae9959f066064501480bad158a058237c9a5 on temp into d44de33750d68de45005c0648f72da7aa68af213 on master.


Disable weekends and color them red

Hi Team,
I couldn't figure out an easy way to disable the weekends (Saturday, Sunday) and highlight them in red. The only option is to use "disabledDays" but it only accepts an array of Dates. This will be huge considering in my case, the user can navigate back and forth between years.
Also for middle east, the weekend will be Friday and Saturday.
Is it possible to re-implement the option:
disabledWeekDays: [5, 6]
There was a similar issue opened before:
https://github.com/Paul-DS/bootstrap-year-calendar/issues/16
Thanks,
Hari

Hi, if not wrong you just need to change the parameters of disabledWeekDays to [4,5] what will be Friday and Saturday for the styling i'm not sure, but probably those elements that are disabled have a specific and/or unique class that way you could identify them and set a background red

disabledWeekDays : [4,5] does not have any effect. For styling (highlighting in red) I used "customDayRenderer" function and it worked like a charm.
Still waiting for a solution to disable Weekdays.

Hi,
This option is available only in the current version of the calendar (not released yet).
If you want to use it without waiting for the next release, you have to download the last code version on GitHub.


fix failing tests

This patch fixes the following ShapeFactorytests.

ShapeHasAttributesType
CreateShapeWithNamedArguments
CallSyntax
CallInitializer
CallInitializerWithBaseType

The kind of PR that won't take days to be merged ;)


translation and rotation of functions

I will add steps on when the function changes what should be the steps
ex - if f(x)-> f(-x) then how will the graph of function change
if f(x)->|f(x)| how will the graph change

Go ahead
Deadline 31 March,2021 (11:59 PM IST)

@sairish2001 Attached a PR Have a look

@sairish2001 Just a small request . If possible could you please increase the level of the issue because I personally feel level 1 is a level low. If possible.
Thanx


Failed building wheel for pyarrow. Raspbian/debian

Describe the bug, including details regarding any error messages, version, and platform.
Hello all,
I am running into an intractable error when I try to install pyarrow on a Raspberry Pi 4 running Raspbian 10.
CMake Error at CMakeLists.txt:261 (find_package):
        By not providing "FindArrow.cmake" in CMAKE_MODULE_PATH this project has
        asked CMake to find a package configuration file provided by "Arrow", but
        CMake did not find one.

        Could not find a package configuration file provided by "Arrow" with any of
        the following names:

          ArrowConfig.cmake
          arrow-config.cmake

        Add the installation prefix of "Arrow" to CMAKE_PREFIX_PATH or set
        "Arrow_DIR" to a directory containing one of the above files.  If "Arrow"
        provides a separate development package or SDK, be sure it has been
        installed.

      -- Configuring incomplete, errors occurred!
      See also "/tmp/pip-install-p4u5ohc7/pyarrow_6542d2c5cfb040c6bf8cf552a7c8e0e1/build/temp.linux-aarch64-cpython-37/CMakeFiles/CMakeOutput.log".
      See also "/tmp/pip-install-p4u5ohc7/pyarrow_6542d2c5cfb040c6bf8cf552a7c8e0e1/build/temp.linux-aarch64-cpython-37/CMakeFiles/CMakeError.log".
      error: command '/usr/bin/cmake' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pyarrow
Failed to build pyarrow
ERROR: Could not build wheels for pyarrow, which is required to install pyproject.toml-based projects

I am really not sure how to resolve this! If anyone has any advice it would be greatly appreciated.
Thank you!
Component(s)
Python

You need to install Apache Arrow C++ before you install pyarrow:
https://arrow.apache.org/docs/developers/python.html#using-system-and-bundled-dependencies

I appreciate the tip. I've just tried to work through it a few times and the installation process is failing at the make -j4 step. I'm not sure if this might be related or not
[ 15%] Building CXX object src/arrow/CMakeFiles/arrow_objlib.dir/vendored/double-conversion/bignum-dtoa.cc.o
In file included from /home/redacted/arrow/cpp/src/arrow/util/utf8.cc:28:
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h: In function ‘bool arrow::util::ValidateAsciiSimd(const uint8_t*, int64_t)’:
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:235:29: error: ‘make_sized_batch_t’ in namespace ‘xsimd’ does not name a template type
   using simd_batch = xsimd::make_sized_batch_t<int8_t, 16>;
                             ^~~~~~~~~~~~~~~~~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:238:11: error: ‘simd_batch’ does not name a type; did you mean ‘rpmatch’?
     const simd_batch zero(static_cast<int8_t>(0));
           ^~~~~~~~~~
           rpmatch
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:240:5: error: ‘simd_batch’ was not declared in this scope
     simd_batch or1 = zero, or2 = zero;
     ^~~~~~~~~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:240:5: note: suggested alternative: ‘rpmatch’
     simd_batch or1 = zero, or2 = zero;
     ^~~~~~~~~~
     rpmatch
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:243:7: error: ‘or1’ was not declared in this scope
       or1 |= simd_batch::load_unaligned(reinterpret_cast<const int8_t*>(data));
       ^~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:243:14: error: ‘simd_batch’ is not a class, namespace, or enumeration
       or1 |= simd_batch::load_unaligned(reinterpret_cast<const int8_t*>(data));
              ^~~~~~~~~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:244:7: error: ‘or2’ was not declared in this scope
       or2 |= simd_batch::load_unaligned(reinterpret_cast<const int8_t*>(data2));
       ^~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:244:7: note: suggested alternative: ‘log2’
       or2 |= simd_batch::load_unaligned(reinterpret_cast<const int8_t*>(data2));
       ^~~
       log2
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:244:14: error: ‘simd_batch’ is not a class, namespace, or enumeration
       or2 |= simd_batch::load_unaligned(reinterpret_cast<const int8_t*>(data2));
              ^~~~~~~~~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:251:5: error: ‘or1’ was not declared in this scope
     or1 |= or2;
     ^~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:251:12: error: ‘or2’ was not declared in this scope
     or1 |= or2;
            ^~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:251:12: note: suggested alternative: ‘log2’
     or1 |= or2;
            ^~~
            log2
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:252:16: error: ‘any’ is not a member of ‘xsimd’
     if (xsimd::any(or1 < zero)) {
                ^~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:252:26: error: ‘zero’ was not declared in this scope
     if (xsimd::any(or1 < zero)) {
                          ^~~~
/home/redacted/arrow/cpp/src/arrow/util/utf8_internal.h:252:26: note: suggested alternative: ‘bzero’
     if (xsimd::any(or1 < zero)) {
                          ^~~~
                          bzero
[ 16%] Building CXX object src/arrow/CMakeFiles/arrow_objlib.dir/vendored/double-conversion/fast-dtoa.cc.o
make[2]: *** [src/arrow/CMakeFiles/arrow_objlib.dir/build.make:1324: src/arrow/CMakeFiles/arrow_objlib.dir/util/utf8.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
[ 16%] Building CXX object src/arrow/CMakeFiles/arrow_objlib.dir/vendored/double-conversion/cached-powers.cc.o
make[1]: *** [CMakeFiles/Makefile2:2203: src/arrow/CMakeFiles/arrow_objlib.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

output_cmake_make.txt

Could you try cmake -DARROW_CXX=-march=native ... and cmake -DARROW_SIMD_LEVEL=NONE ...?

Okay I got a lot farther now. Thank you
First, here's the output for both commands you suggested:
output_cmake_make (1).txt
And here's the new error:
[ 56%] Building CXX object src/parquet/CMakeFiles/parquet_objlib.dir/encryption/local_wrap_kms_client.cc.o
[ 56%] Built target parquet_objlib
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_test.cc.o: in function `arrow::ArrayData::SetNullCount(long long)':
/usr/include/c++/8/bits/atomic_base.h:374: undefined reference to `__atomic_store_8'
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_test.cc.o: in function `arrow::ArrayData::MayHaveNulls() const':
/usr/include/c++/8/bits/atomic_base.h:396: undefined reference to `__atomic_load_8'
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_test.cc.o: in function `arrow::ArrayData::MayHaveLogicalNulls() const':
/usr/include/c++/8/bits/atomic_base.h:396: undefined reference to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/bits/atomic_base.h:396: undefined reference to `__atomic_load_8'
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_test.cc.o: in function `std::__atomic_base<long long>::operator long long() const':
/usr/include/c++/8/bits/atomic_base.h:396: undefined reference to `__atomic_load_8'
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_test.cc.o: in function `std::__atomic_base<long long>::operator=(long long)':
/usr/include/c++/8/bits/atomic_base.h:374: undefined reference to `__atomic_store_8'
/usr/bin/ld: CMakeFiles/arrow-array-test.dir/array/array_list_test.cc.o: in function `std::__atomic_base<long long>::operator+=(long long)':
/usr/include/c++/8/bits/atomic_base.h:312: undefined reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[2]: *** [src/arrow/CMakeFiles/arrow-array-test.dir/build.make:203: debug/arrow-array-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:2379: src/arrow/CMakeFiles/arrow-array-test.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

I'd be grateful for any other ideas you ahve!

Okay after one run hanging, I'm now even further, but hitting the following errors:
[ 67%] Linking CXX executable ../../../../debug/arrow-compute-aggregate-test
/usr/bin/ld: CMakeFiles/arrow-compute-aggregate-test.dir/aggregate_test.cc.o: file not recognized: file truncated
/usr/bin/ld: CMakeFiles/arrow-compute-scalar-type-test.dir/test_util.cc.o: file not recognized: file truncated
Scanning dependencies of target arrow-compute-kernel-utility-test
Scanning dependencies of target arrow-compute-scalar-utility-test
collect2: error: ld returned 1 exit status
collect2: error: ld returned 1 exit status
make[2]: *** [src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-type-test.dir/build.make:143: debug/arrow-compute-scalar-type-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:3026: src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-type-test.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [src/arrow/compute/kernels/CMakeFiles/arrow-compute-aggregate-test.dir/build.make:113: debug/arrow-compute-aggregate-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:2958: src/arrow/compute/kernels/CMakeFiles/arrow-compute-aggregate-test.dir/all] Error 2
[ 68%] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-kernel-utility-test.dir/codegen_internal_test.cc.o
[ 69%] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-utility-test.dir/scalar_random_test.cc.o
[ 69%] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-utility-test.dir/scalar_set_lookup_test.cc.o
[ 69%] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-utility-test.dir/scalar_validity_test.cc.o
[ 69%] Linking CXX executable ../../../../debug/arrow-compute-kernel-utility-test
[ 69%] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-utility-test.dir/test_util.cc.o
[ 69%] Built target arrow-compute-kernel-utility-test
[ 69%] Linking CXX executable ../../../../debug/arrow-compute-scalar-utility-test
[ 69%] Built target arrow-compute-scalar-utility-test
make: *** [Makefile:141: all] Error 2

Genuinely happy this is helping others troubleshoot as well! Thank you for commenting @Trompettesib

It seems that it's a concurrent build problem.
Does make (no -j4) work?

make by itself yielded:
[ 53%] Built target arrow-compute-expression-test
[ 53%] Linking CXX executable ../../../../debug/arrow-compute-aggregate-test
/usr/bin/ld: CMakeFiles/arrow-compute-aggregate-test.dir/aggregate_test.cc.o: file not recognized: file truncated
collect2: error: ld returned 1 exit status
make[2]: *** [src/arrow/compute/kernels/CMakeFiles/arrow-compute-aggregate-test.dir/build.make:113: debug/arrow-compute-aggregate-test] Error 1
make[1]: *** [CMakeFiles/Makefile2:2958: src/arrow/compute/kernels/CMakeFiles/arrow-compute-aggregate-test.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

Okay that worked! 100% install of Arrow. Thank you :)
Unfortunately I still get the same error again described at the very top of this thread. Output here: output_pip3_install_pyarrow.txt

Could you ensure setting CMAKE_PREFIX_PATH?
https://arrow.apache.org/docs/developers/python.html#using-system-and-bundled-dependencies describes it too.

I'm not familiar enough with C to be confident that I've done this right, but I ran make clean and then went back to make sure to run
export ARROW_HOME=$(pwd)/dist
export LD_LIBRARY_PATH=$(pwd)/dist/lib:$LD_LIBRARY_PATH
export CMAKE_PREFIX_PATH=$ARROW_HOME:$CMAKE_PREFIX_PATH

And I'm still getting the same errors.
I'm not sure if this is helpful for debugging, but when I run $CMAKE_PREFIX_PATH I get No such file or directory
Thank you so much for all your help with this!

Success! Successfully installed pyarrow-12.0.0 Thank you so much for your persistent help @kou . Your final suggestion to look at CMAKE_PREFIX_PATH helped me finish the job because I found that $CMAKE_PREFIX_PATH wasn't pointing anywhere even after I had run the code to define it, which helped me go back and check dist and realize it wasn't in the right place. Issue closed as far as I'm concerned!

Okay I think I was running mkdir dist from the wrong location, so the later path references weren't pointing to an existing directory. This was probably due to me trying to debug and then go back and rerun the installation instructions from halfway points, rather than starting from the very beginning each time. In this case I think that when I was running mkdir dist I was not in /arrow because I had not started all the way back in the environment setup section and so had not run pushd arrow first. After manually navigating to /arrow and then mkdir dist etc it now seems to be installing correctly, and now pyarrow has actually started installing for the first time. I have to step away right now but will let you know how it went when I can.

Hi there, I'm having the exact same problems as you had so I guess the solution would be the same but I'm having a hard time understanding what exactly led to the solution here. Could you please elaborate a bit what exactly you did here?

Hey @starsnpixel. Basically, some of the intermediate steps assume that all previous blocks have been run, and that they've been run in order. Specifically, when I was running some of the later steps I was pointing to the wrong directory, and a previous step would have put me in the right one. It's annoying, but as you debug I would try starting from the very beginning each time. I hope that helps!

Were you following the official guideline on https://arrow.apache.org/docs/developers/python.html#python-development or working on your own? Because I am doing exactly what is told there and still I run into this problem.

I was following that guide you linked to


Procedural Sky Shader - we love 'em, we need 'em.

We started discussing procedural Sky Shader for Godot on IRC.
Idea is to create at least basic one for starters.
Some refs:
https://threejs.org/examples/webgl_shaders_sky.html
https://docs.blender.org/manual/en/dev/render/cycles/nodes/types/textures/sky.html
http://blog.camposanto.com/post/112703721804/this-blog-post-is-an-in-detail-explanation-of-part
https://blenderartists.org/forum/showthread.php?245954-preethams-sky-impementation-HDR
Papers:
http://www.cs.utah.edu/~shirley/papers/sunsky/sunsky.pdf
http://cgg.mff.cuni.cz/projects/SkylightModelling/HosekWilkie_SkylightModel_SIGGRAPH2012_Preprint_lowres.pdf
http://cgg.mff.cuni.cz/projects/SkylightModelling/

Fire watch talk from GDC - useful insights how procedural skies and gradient fog was used:
https://youtu.be/ZYnS3kKTcGg?t=452

This topic is also related to - #8060

I think there is an asset-driven part, so we should look at what the engine lacks for them to be implemented.

@Zylann
This is one of many pieces you refer too :) It's first step.
Sun will be part of Shader (at lest visual part) you will be able to control it's inclination and azimuth with Uniform shader params, so you then can connect it by script with DirectionalLamp.
Although I plan to make SunLamp node which will have DirectionalLamp node that will be easy to connect with SkyShader. This is sooo common task, that this type of node will be good to have as part of engine.
Clouds, stars, moon/planets will be added also but later :P

here's another one, for reference: https://github.com/Tw1ddle/Sky-Particles-Shader

You have custom particle code and asset lib anybody should be able to
contribute
On May 6, 2017 4:46 PM, "Nuno Donato"<EMAIL_ADDRESS>wrote:

here's another one, for reference: https://github.com/Tw1ddle/
Sky-Particles-Shader
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/8668#issuecomment-299648151,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2-1-KVz1mVX0sR6emVP36Kbi180Xks5r3JXsgaJpZM4NStJG
.

@reduz
Yup.
Initially I plan it as Asset Lib. When I will have something we can discuss - if or what we should move as default Godot toolset.
I'm open for discussion :)

I'm not sure what's the status of this issue. We have procedural shader for the skybox in 3.0, is it solved then?

I think the sky isn't a procedural shader though. Isn't it entirely generated on CPU? There is no way to make our own as well.

Isn't this obsoleted by #17510?

The procedural sky just calculates the skytexture on the CPU. The thing to keep in mind is that it's not enough to just render the background with a shader like many engines do. You need to calculate the full 360 degree map from which Godot generates radiance maps to be able to do all the PBR lighting and such. That is a lot of overhead to do real time for each frame. You can get away with it when just rendering the sky color and sun as the sun generally doesn't move so you can recalculate once a minute or something like that, but if you want to add clouds that are animated you need to do add the clouds later on with some other technique.
@bojidar-bg is correct, the issues for making it work are fixed though there were more fixes, the last ones are in #19029, I don't know if that made it into the latest 3.0.3 RC yet but it has been cherry picked.
With that PR in place you can see it in action with with this project: https://github.com/BastiaanOlij/godot-sky-asset/tree/use_proxy_fix
(I'll be merging that branch once 3.0.3 is released and submitting a new version to the asset library)
The shader itself could use a few improvements, it's getting the horizon wrong, but it shows how to do this all on the GPU

Owh and note that this: #19030 would be a worthwhile improvement so things work more automatic.

Closing as per the above comment, since it is already possible to make procedural skies.

This is now implemented in 4.0: https://docs.godotengine.org/en/latest/tutorials/shaders/shader_reference/sky_shader.html
3.x doesn't have sky shaders, but you can use a MeshInstance with a ViewportTexture applied on it to create a real-time animated sky. However, the radiance map won't be updated in real-time when doing this.


Replace Deprecated abc Decorators (#1)

The @abstractproperty, @abstractclassmethod, and @abstractstaticmethod decorators from abc has been deprecated since Python 3.3. This is because it's possible to use @property, @classmethod, and @staticmethod  in combination with @abstractmethod.
Our changes look like the following:
 import abc

 class Foo:
-   @abc.abstractproperty
+   @property
+   @abc.abstractmethod
    def bar():
        ...

and similarly for @abstractclassmethod and @abstractstaticmethod.

More reading

https://docs.python.org/3/library/abc.html#abc.abstractproperty
https://docs.python.org/3/library/abc.html#abc.abstractclassmethod
https://docs.python.org/3/library/abc.html#abc.abstractstaticmethod

FYI - This change was autogenerated from a GitHub app - called Pixeebot. A code-quality GitHub App; like Dependabot, but for source code. Feel free to check it our for more details for how you can install it onto your project's repo for continued code hardening and code security recommendations.


To reproduce:

go to landscape mode
trigger Ultrasound at least once
open Spotlight menu

I can confirm this exact behaviour. iPadAir2, IOS 12.1.1
Seem to only affect spotlight search; havn't seen the effect in any apps yet...

Likely linked to the window we create and how its meant to stay in portrait, will take a look

I remember @the-casle had the same issue with Nine, I don't know if he ever fixed it, maybe he could help

Further testing on the latest release version confirms that this was fixed by 6664eb68.


Finish Boilerplating Code

Problem
As a developer,
I want to have boiler plated fonts,
So I can speed up development
As a developer,
I want boiler plated scaffolding,
So I can begin development as soon as possible
Link to Asana Ticket #1
Link to Asana Ticket #2
Solution
To begin working on our MVP site with the newly released high-fidelity mockups, we had to redefine our repository structure. These following changes are being implemented in the PR:

Restructured scaffolding

Within our /src folder we have components and views folders. Within our components folder, all the components of our site will live there. Components include navbar, email subscription component, and Postcard Stack components for now. This will allow us to reuse these components throughout our entire web app. Hooray for refactoring! Each component will contain their own scss file where styling of the component should happen independent of the rest of the web application.
Additionally, within our views folder, we will have the 5 views that we plan to implement:  Home, Schedule, Information, Sponsorship, and Team. For our MVP, we will mainly be developing within our Home view. Each individual view will be imported into the routes directory and be rendered through there. Each individual component will also contain their own scss file and this is where you will style the placement and responsiveness of these views.

Boilerplated Fonts and Constants

All the font sources will be found within the src/fontsfolder
Within the src/stylesheets folder, you will find partial scss files and a base.scss file. One main takeaway from these files is that we want to move away from using @import in order to get rid of global mixins. We want to be more implicit as to where certain mixins come from. base.scss will contain only constants. The current files that contain constants are _spacers, _fonts, and _variables. _typography is an example of a partial that you will need to explicit import using @use "~stylesheets/typograpy" provided by scss. Here is more documentation for the @use command.

Relative vs. Absolute Paths

For a while now, we have had issues with relative paths. If we are in our views/Home/index file and we want to import Navbar from components/Navbar/index, we have to import using ../../components/Navbar/index. This gets messy especially if we move around the structure of our entire repository of if we do renaming and redo our scaffolding. In order to prevent any issues from happen, we have the baseUrl being at src, which means that you can reference everything in relation to the src file. The import statement now becomes import * as Navbar from "components/Navbar/index". Be sure to make use of this neat tool as much as possible! This rule also pertains to scss files.

Deepcode CI Bot

This bot will check out our current PR's and check to see if there are any code improvements to be made or if there are any security vulnerabilities in our current codebase.

Steps to Verify:

Take a look at the repository as it is right now and make sure you are familiar with the structure.

Screenshots:
Current File Structure

@tim-nguyen-cs That's a really good question! I know right now it seems like refactoring this PostcardStack component is unnecessary, but moving forward when we bring animation and Lottie into the picture, I think this is where it'll become more prevalent. Take a look at the lottie documentation. I see a lot of places where refactoring this component will be valuable. For our MVP, I think it is ok to have this PostcardStack component either empty/not being used at all and have the PNG image being imported directly into the views/Home/index file.


Get started/interactive

Change the Azure CLI 'get started' to be leaner and link out to more concrete resources. Also tutorialize much of the existing Azure CLI content as "spinning up a static web server." First pass includes setting up a data disk, which can maybe be dropped from the final version. It feels a little out of place, but also distinguishes it from the Azure VM team's quickstart

:x: Validation status: errors

File
Status
Preview URL
Details

latest/docs-ref-conceptual/tutorial-azure-cli-server.yml
:x:Error

Details

:x:Error

Details

latest/docs-ref-conceptual/tutorial-azure-cli-server.yml

[Error] Unable to load file: latest/docs-ref-conceptual/tutorial-azure-cli-server.yml via processor: YamlDocumentProcessor.

[Error] YamlDotNet.Core.SyntaxErrorException: (Line: 247, Col: 1, Idx: 13366) - (Line: 247, Col: 1, Idx: 13366): While scanning a simple key, could not find expected ':'.
at Microsoft.DocAsCode.Build.Engine.SingleDocumentBuilder.GetInnerContexts(DocumentBuildParameters parameters, IEnumerable1 processors, TemplateProcessor templateProcessor, IHostServiceCreator creator) at Microsoft.DocAsCode.Build.Engine.SingleDocumentBuilder.BuildCore(DocumentBuildParameters parameters) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.BuildCore(DocumentBuildParameters parameter, IMarkdownServiceProvider markdownServiceProvider, BuildInfo currentBuildInfo, BuildInfo lastBuildInfo) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder.Build(IList1 parameters, String outputDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

latest/docs-ref-conceptual/get-started-with-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/media/tutorial-azure-cli-server/nginx-success.png
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/tutorial-azure-cli-server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@rloutlaw My biggest concern is the "data disk" segment of the tutorial, which doesn't fit with the rest of the theme of using the Azure CLI. However without it, this tutorial might be too close to the VM Quickstart. Interested in feedback on this and if I need to contact the VM services team to work with their docs.

Took a stab at some issues, some big, some small. You'll want to talk w/ Jason Shaver about this too.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

latest/docs-ref-conceptual/get-started-with-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/media/tutorial-azure-cli-server/nginx-success.png
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/tutorial-azure-cli-server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

latest/docs-ref-conceptual/get-started-with-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/media/tutorial-azure-cli-server/nginx-success.png
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-conceptual/tutorial-azure-cli-server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing this PR as I'm going to be taking a substantially different track from this point forward. Thanks for all the feedback, it's going into the new (and improved) work.


Undefined Fragment when spreading is used for an complex type

Describe the bug
Hello. I faced problem with types when using fragment spreading.
For example:
If you have this query and want to use in another query your IDE won't discover as a type
export const ItemListFragment = graphql(`
  fragment PageInfo on ItemsConnection {
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
      endCursor
    }
  }
`)

export const ItemListQuery = graphql(`
  query GetItems () {
    items() {
      totalCount
      ...PageInfo
      nodes {
        ...SomeAnotherFragment - same problem
      }
    }
  }
`, [ItemListFragment])

IDE WebStorm error:
{
  nodes: {
    [$tada.fragmentRefs]
  :
    {
      ItemListItem: "Flight";
    }
    ;
  }
  [] | null;
  [$tada.fragmentRefs]
:
  {
    PageInfo: "Undefined Fragment";
  }
  ;
  totalCount: number;
}

But if you use directly the object with its props without the fragment, everything works
export const ItemListQuery = graphql(`
  query GetItems () {
    items() {
      totalCount
      pageInfo {
        hasNextPage
        hasPreviousPage
        startCursor
        endCursor
      }
      nodes {
        ...SomeAnotherFragment - same problem
      }
    }
  }
`, [ItemListFragment])

Reproduction
No response
gql.tada version
gql.tada: 1.4.3
Validations

[X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

Hey,
With these sorts of issues we require you to create a reproduction, I also think your code fragments are either incorrect or out of date as you seem to allude to an issue being present with your description that that one works correctly 😅

OK, sorry, I'll try to prepare a real example.

@echocrow: It's likely not an incompatibility, but rather, the LSP extension is issuing its own warnings that look very similar to ours, given that there's an overlap with the GraphiQL diagnostics that both output.
There's not really much we can do about that.
We can check whether a .vscode/extensions.json file is present in the repo, and whether that contains the plugin during the gql.tada doctor check. But some people may still have it installed for legitimate reasons, and other may have it installed without .vscode/extensions.json being present.
Do you have a sample of your graphql-config file? That's the only other thing we could check for, and I'd assume that'd have to be present for this to become an issue even.

@kitten cheers for the response!
(this may be getting a bit off-topic from OP's post - unless OP was facing that exact issue too?)
Well, by "incompatibility" I meant that, as you described, the LSP extension would run its own checks and validation in the IDE. For most basic queries and mutations, that does not pose any issues. However, false errors do arise when using more "advanced" features, particularly around fragments. Those errors get flagged not by gql.tada or TS, but by the separate GraphQL LSP from the official extension. I assume these arise because that LSP does not recognize gql.tada's @_unmask directive, or imported fragments passed into queries via the fragments argument. These errors are safe to ignore once you know about this, but it certainly confused us initially when we evaluated gql.tada (and almost had us reconsider using it, thinking fragments weren't fully supported).
In an ideal world, maybe there's a way to either extend the extension LSP, helping it recognize gql.tada's extra features, or some way of instructing the GraphQL LSP to ignore gql.tada's queries function? I have no clue if either is possible though, as I know little to nothing about how that LSP works under the hood.
Short of a solution to have the two co-exist, that's why I suggested perhaps a note in the docs about this caveat (akin to the note about requiring VSCode to use the workspace TS version).

Do you have a sample of your graphql-config file?

Our exact setup is a little overly complex (monorepo and all). However, we're noticing this issue even with a relatively barebone graphql config file:
// .graphqlrc.ts
export default {
  projects: {
    foo: {
      schema: './packages/foo/schema.graphql',
      documents: './packages/foo/src/components/**/*.graphql',
    },
  },
}

For some reason, even this config has the GraphQL LSP validate  e.g. packages/bar/my-gql-tada-query.ts (notice the unrelated foo vs bar directory). Perhaps this is actually a bug in the GraphQL LSP extension(?).

I just took a look, and this doesn't seem to be reproducible if the output is limited to:
documents: './packages/foo/src/components/**/*.graphql',
i.e. if the documents are limited to *.graphql files. Otherwise, it does seem like by default VSCode GraphQL (or rather graphql-language-service-server) will try to discover documents in *.{ts,tsx} files.
There's obviously still the question of whether it's possible to avoid the conflict entirely, and this is likely something I'd like to add to our doctor command, but I'm still looking into what we could do about this

There doesn't seem to be a better option here than to issue a warning to check that your documents setting in your graphql-config file only includes .graphql files, but that's basically the solution we'll have to go for for now.

@kitten I'm pretty confident we ran into this issue even when documents was scoped to just .graphql files, or set to []. I can try to put together a repro later this week if that might be useful?

That'd be very helpful! 🙌 but potentially something that should also be reported to the graphql-config project itself.
Even if it turns out that, for some reason, documents isn't always fully respected, that's an issue for vscode-graphql and/or graphql-config.
There's also not a good setting in vscode-graphql that could be flipped in .vscode/settings.json (in your repo) to fully force-disable .{ts,tsx} parsing, but I'm hesitant to raise an issue there for now, since there's a limit to how many incompatibilities we can anticipate anyway.

@kitten repro available here:

https://github.com/echocrow/gql-tada-vs-lsp-repro

As per your comment, I suspect that this is a bug in the GraphQL LSP, validating gql.tada's GraphQL code, even when JS/TS files are not part of the configured documents.
Issue opened here:

https://github.com/graphql/graphiql/issues/3588

Until (if?) this is addressed, I'd still recommend calling out this caveat in the gql.tada docs. The only workaround we've found so far was to outright disable the VSCode extension.

@echocrow: we don't have editor-specific docs yet and I have a feeling that's something we'd want to avoid for as long as possible for instead leaning into TS LSP+plugin support.
The problem is, as you can see in the WebStorm issue, it's often external problems and it's unclear how people arrive at solutions. We may even be talking about very personal setups here. While VSCode is the most common, there's also issues with the extension marketplace (for instance the official extensions aren't even the first that pop up in the search)
So, for now, the warnings have been added to the gql.tada doctor command instead, since there we can add setup-specific rules and checks

we don't have editor-specific docs yet

except you kinda do 😅 (there is a VSCode specific note RE using the workspace version of TypeScript; but I understand the aversion, and arguably that note is more crucial and less niche.)
I was picturing a similar note (even if buried on the Fragment Colocation page) that other GraphQL LSPs should be configured to not check these ts(x) files, as they will incorrectly flag gql.tada's features as errors, and compete with gql.tada's auto-completion. (the latter is less of an issue, but we were also confused why ever field was suggested twice, thinking we spotted a minor gql.tada bug. now we know that both gql.tada and GraphQL LSP were echoing suggestions at the same time.)
in any case, won't press the matter further! 🫡 thanks for the time and support! we have the LSP disabled for now, and hope the extraneous file checking gets fixed sometime (or we migrate fully to gql.tada before!)
(and sorry again @ OP for completely hijacking this issue 🙃)


End-to-end examples of transforms

Issue Description
As a total newcomer to datavec transform processes, it was very difficult for me to infer how to build a full transform pipeline. With the exception of @tomthetrainer's easy to follow video, I was lost on how to properly work with CSV data.
This issue is to address the need for an example that does the following:

Works with a complex CSV of different types (categorical, integers, doubles strings)
Shows how to use custom conditions and transforms to replace null values
Shows how to do advanced transformation, including applying advanced code on string values (for example, CSV has human input text and we want to classify it before passing further into pipeline)
Shows how to save to Hadoop map file, then load it into an MLP into training.
Shows how to do advanced schemas for complex CSVs (what happens when you have 5,000 columns!?).

Version Information
Please indicate relevant versions, including, if relevant:
Master, current, etc.
Contributing
I'm very happy to contribute here. First, I'd like to find out if there's more that should be on this example before continuing.

As part of this, I think I will write a MagicSchema class that extends our SchemaFromFile tool and open a PR.

Having https://github.com/deeplearning4j/DataVec/issues/357 included in this would really be valuable.

I agree with this suggestion.
We could make a video, make a blog, build an example or a mix of all three.
I need to add more datavec stuff to the training class as well so there is crossover into digging into this.
First step:
Some sample data that provides a decent challenge but is not too complex. Too complex and it distracts, too simple and we do not have enough to work on.

@tomthetrainer is a dataset of 129 rows too much?

@AlexDBlack how much is the datavec overhaul going to affect this?

@crockpotveggies apologies, I missed your question until now.
The overhaul will change just about everything about the TransformProcess. It would make more sense to create these sorts of examples after it's done.


add RegularExpressionRandomizer

Coverage increased (+0.04%) to 93.097% when pulling 4e03fe9057fd6863c47b535803b4ad1466f728d6 on PascalSchumacher:add_regular_expression_randomizer into c810e406e14ab961c6e56cce259a62e0531c93f6 on benas:master.

Coverage increased (+0.04%) to 93.097% when pulling 597b6b582ced0ef63871db37313e46466eeb994a on PascalSchumacher:add_regular_expression_randomizer into c810e406e14ab961c6e56cce259a62e0531c93f6 on benas:master.

Great! as usual 😄


Update FilePickerLauncher.ios.kt

[IOS] Gallery picker only call onResult one time (like in file picker)

Hi,
Thanks for your contribution!
I will check this later today, can you explain how onResult can called twice?. How can I reproduce it.

In iOS, when using the gallery image picker to select multiple images (2 or more), the onResult callback is expected to return a list of files. However, currently, it triggers the onResult callback multiple times (n times), each time with a list containing only a single image.

I Use the Image/video picker

I did some refactoring to your code using coroutines, feel free to check it out here: #129


bioin-973 report: display filtered indels in table, separate hmer from non-hmer…

… tables

redid the commit on top of master head which already fixed the problems with present_columns


Current project (repo) status

Hi @didierthevenard, I was wondering if this project is still actively maintained as I was going to fork it and file a pull request later on.

Yes it it still active. Feel free to fork it and submit a pull request if you wish.

Thanks. Please see: #2.


Could not find method veclasspathrsionName

after updating flutter and android studio I cannot run my flutter application
Error :
Could not find method veclasspathrsionName() for arguments
flutter run output :
flutter run
Launching lib/main.dart on LG in debug mode...
Initializing gradle...                                              2.9s
Resolving dependencies...
* Error running Gradle:
ProcessException: Process "/Users/user/Desktop/projects/myproject/android/gradlew" exited abnormally:

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/user/Desktop/projects/myproject/android/app/build.gradle' line: 41

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not find method veclasspathrsionName() for arguments [1.0.0] on DefaultConfig_Decorated{name=main, dimension=null, minSdkVersion=DefaultApiVersion{mApiLevel=16,
mCodename='null'}, targetSdkVersion=DefaultApiVersion{mApiLevel=27, mCodename='null'}, renderscriptTargetApi=null, renderscriptSupportModeEnabled=null,
renderscriptSupportModeBlasEnabled=null, renderscriptNdkModeEnabled=null, versionCode=1, versionName=null, applicationId=org.myname.myname, testApplicationId=null,
testInstrumentationRunner=null, testInstrumentationRunnerArguments={}, testHandleProfiling=null, testFunctionalTest=null, signingConfig=null, resConfig=null,
mBuildConfigFields={}, mResValues={}, mProguardFiles=[], mConsumerProguardFiles=[], mManifestPlaceholders={}, mWearAppUnbundled=null} of type
com.android.build.gradle.internal.dsl.DefaultConfig.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
  Command: /Users/user/Desktop/projects/myproject/android/gradlew app:properties

Please review your Gradle project setup in the android/ folder.

flutter run --verbose output :
flutter run --verbose
[  +60 ms] executing: [/Users/user/Documents/flutter/] git log -n 1 --pretty=format:%H
[  +60 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[   +1 ms] 7a4c33425ddd78c54aba07d86f3f9a4a0051769b
[        ] executing: [/Users/user/Documents/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +18 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.5.4-hotfix.2-0-g7a4c33425
[  +19 ms] executing: [/Users/user/Documents/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +14 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/user/Documents/flutter/] git ls-remote --get-url origin
[  +13 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +100 ms] executing: [/Users/user/Documents/flutter/] git rev-parse --abbrev-ref HEAD
[  +19 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] stable
[ +152 ms] executing: /Users/user/Library/Android/sdk/platform-tools/adb devices -l
[  +10 ms] Exit code 0 from: /Users/user/Library/Android/sdk/platform-tools/adb devices -l
[        ] List of devices attached
           LGc913b9a2         device usb:4195549184X product:h1_global_com model:LG device:h1 transport_id:3
[  +21 ms] executing: idevice_id -h
[  +35 ms] /Users/user/Library/Android/sdk/platform-tools/adb -s LGc913b9a2 shell getprop
[ +124 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +6 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FuchsiaCacheArtifacts' is not required, skipping update.
[ +148 ms] Found plugin fluttertoast at /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.0/
[  +19 ms] Found plugin sqflite at /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-1.1.6+1/
[  +78 ms] Found plugin fluttertoast at /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/fluttertoast-3.1.0/
[  +15 ms] Found plugin sqflite at /Users/user/Documents/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-1.1.6+1/
[  +92 ms] ro.hardware = h1
[        ] ro.build.characteristics = default
[  +75 ms] Launching lib/main.dart on LG in debug mode...
[  +26 ms] Initializing gradle...
[  +11 ms] Using gradle from /Users/user/Desktop/projects/myproject/android/gradlew.
[+1567 ms] executing: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info
[  +40 ms] Exit code 0 from: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info
[        ] {
               CFBundleDevelopmentRegion = English;
               CFBundleDocumentTypes =     (
                           {
                       CFBundleTypeExtensions =             (
                           ipr
                       );
                       CFBundleTypeIconFile = "studio.icns";
                       CFBundleTypeName = "Android Studio Project File";
                       CFBundleTypeRole = Editor;
                   },
                           {
                       CFBundleTypeExtensions =             (
                           "*"
                       );
                       CFBundleTypeName = "All documents";
                       CFBundleTypeOSTypes =             (
                           "****"
                       );
                       CFBundleTypeRole = Editor;
                       LSTypeIsPackage = 0;
                   }
               );
               CFBundleExecutable = studio;
               CFBundleGetInfoString = "Android Studio 3.4, build AI-183.6<IP_ADDRESS>22156. Copyright JetBrains s.r.o., (c) 2000-2019";
               CFBundleIconFile = "studio.icns";
               CFBundleIdentifier = "com.google.android.studio";
               CFBundleInfoDictionaryVersion = "6.0";
               CFBundleName = "Android Studio";
               CFBundlePackageType = APPL;
               CFBundleShortVersionString = "3.4";
               CFBundleSignature = "????";
               CFBundleURLTypes =     (
                           {
                       CFBundleTypeRole = Editor;
                       CFBundleURLName = Stacktrace;
                       CFBundleURLSchemes =             (
                           idea
                       );
                   }
               );
               CFBundleVersion = "AI-183.6<IP_ADDRESS>22156";
               JVMOptions =     {
                   ClassPath =
                   "$APP_PACKAGE/Contents/lib/bootstrap.jar:$APP_PACKAGE/Contents/lib/extensions.jar:$APP_PACKAGE/Contents/lib/util.jar:$APP_PACKAGE/Contents/lib/jdom.jar:$AP
                   P_PACKAGE/Contents/lib/log4j.jar:$APP_PACKAGE/Contents/lib/trove4j.jar:$APP_PACKAGE/Contents/lib/jna.jar";
                   JVMVersion = "1.8*,1.8+";
                   MainClass = "com.intellij.idea.Main";
                   Properties =         {
                       "idea.executable" = studio;
                       "idea.home.path" = "$APP_PACKAGE/Contents";
                       "idea.java.redist" = Bundled;
                       "idea.paths.selector" = "AndroidStudio3.4";
                       "idea.platform.prefix" = AndroidStudio;
                   };
                   WorkingDirectory = "$APP_PACKAGE/Contents/bin";
               };
               LSApplicationCategoryType = "public.app-category.developer-tools";
               LSArchitecturePriority =     (
                   "x86_64"
               );
               LSMinimumSystemVersion = "10.8";
               LSRequiresNativeExecution = YES;
               NSHighResolutionCapable = 1;
               NSSupportsAutomaticGraphicsSwitching = 1;
           }
[  +20 ms] executing: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[  +43 ms] Exit code 0 from: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[        ] 3.4
[ +115 ms] executing: /Users/user/Desktop/projects/myproject/android/gradlew -v
[+1095 ms]
                    ------------------------------------------------------------
                    Gradle 4.10.2
                    ------------------------------------------------------------

                    Build time:   2018-09-19 18:10:15 UTC
                    Revision:     b4d8d5d170bb4ba516e88d7fe5647e2323d791dd

                    Kotlin DSL:   1.0-rc-6
                    Kotlin:       1.2.61
                    Groovy:       2.4.15
                    Ant:          Apache Ant(TM) version 1.9.11 compiled on March 23 2018
                    JVM:          1.8.0_152-release (JetBrains s.r.o 25.152-b01)
                    OS:           Mac OS X 10.13.6 x86_64
[  +25 ms] Initializing gradle... (completed in 2.9s)
[   +1 ms] Resolving dependencies...
[   +1 ms] executing: [/Users/user/Desktop/projects/myproject/android/] /Users/user/Desktop/projects/myproject/android/gradlew app:properties
[+1244 ms]
                    FAILURE: Build failed with an exception.

                    * Where:
                    Build file '/Users/user/Desktop/projects/myproject/android/app/build.gradle' line: 41

                    * What went wrong:
                    A problem occurred evaluating project ':app'.
                    > Could not find method veclasspathrsionName() for arguments [1.0.0] on DefaultConfig_Decorated{name=main, dimension=null,
                    minSdkVersion=DefaultApiVersion{mApiLevel=16, mCodename='null'}, targetSdkVersion=DefaultApiVersion{mApiLevel=27, mCodename='null'},
                    renderscriptTargetApi=null, renderscriptSupportModeEnabled=null, renderscriptSupportModeBlasEnabled=null, renderscriptNdkModeEnabled=null, versionCode=1,
                    versionName=null, applicationId=org.myname.myname, testApplicationId=null, testInstrumentationRunner=null, testInstrumentationRunnerArguments={},
                    testHandleProfiling=null, testFunctionalTest=null, signingConfig=null, resConfig=null, mBuildConfigFields={}, mResValues={}, mProguardFiles=[],
                    mConsumerProguardFiles=[], mManifestPlaceholders={}, mWearAppUnbundled=null} of type com.android.build.gradle.internal.dsl.DefaultConfig.

                    * Try:
                    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

                    * Get more help at https://help.gradle.org

                    BUILD FAILED in 1s
[   +8 ms] Resolving dependencies... (completed in 1.3s)
[   +5 ms] * Error running Gradle:
           ProcessException: Process "/Users/user/Desktop/projects/myproject/android/gradlew" exited abnormally:

           FAILURE: Build failed with an exception.

           * Where:
           Build file '/Users/user/Desktop/projects/myproject/android/app/build.gradle' line: 41

           * What went wrong:
           A problem occurred evaluating project ':app'.
           > Could not find method veclasspathrsionName() for arguments [1.0.0] on DefaultConfig_Decorated{name=main, dimension=null,
minSdkVersion=DefaultApiVersion{mApiLevel=16,
           mCodename='null'}, targetSdkVersion=DefaultApiVersion{mApiLevel=27, mCodename='null'}, renderscriptTargetApi=null, renderscriptSupportModeEnabled=null,
           renderscriptSupportModeBlasEnabled=null, renderscriptNdkModeEnabled=null, versionCode=1, versionName=null, applicationId=org.myname.myname, testApplicationId=null,
           testInstrumentationRunner=null, testInstrumentationRunnerArguments={}, testHandleProfiling=null, testFunctionalTest=null, signingConfig=null, resConfig=null,
           mBuildConfigFields={}, mResValues={}, mProguardFiles=[], mConsumerProguardFiles=[], mManifestPlaceholders={}, mWearAppUnbundled=null} of type
           com.android.build.gradle.internal.dsl.DefaultConfig.

           * Try:
           Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

           * Get more help at https://help.gradle.org

           BUILD FAILED in 1s
             Command: /Users/user/Desktop/projects/myproject/android/gradlew app:properties

[  +12 ms] "flutter run" took 5,033ms.
[        ] "flutter run" took 5,033ms.
Please review your Gradle project setup in the android/ folder.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:24:3)
#1      _readGradleProject (package:flutter_tools/src/android/gradle.dart:158:7)
<asynchronous suspension>
#2      _gradleProject (package:flutter_tools/src/android/gradle.dart:111:34)
<asynchronous suspension>
#3      getGradleAppOut (package:flutter_tools/src/android/gradle.dart:105:29)
<asynchronous suspension>
#4      AndroidApk.fromAndroidProject (package:flutter_tools/src/application_package.dart:154:23)
<asynchronous suspension>
#5      ApplicationPackageFactory.getPackageForPlatform (package:flutter_tools/src/application_package.dart:46:32)
<asynchronous suspension>
#6      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:345:56)
<asynchronous suspension>
#7      HotRunner.run (package:flutter_tools/src/run_hot.dart:253:39)
<asynchronous suspension>
#8      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:428:37)
<asynchronous suspension>
#9      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
#10     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#11     _rootRunUnary (dart:async/zone.dart:1132:38)
#12     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#13     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#14     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#15     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#16     Future._complete (dart:async/future_impl.dart:473:7)
#17     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#18     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:28:18)
#19     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:294:13)
#20     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#21     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:77:64)
#22     _rootRunUnary (dart:async/zone.dart:1132:38)
#23     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#24     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#25     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#26     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#27     Future._complete (dart:async/future_impl.dart:473:7)
#28     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#29     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async-patch/async_patch.dart:33:20)
#30     _rootRun (dart:async/zone.dart:1124:13)
#31     _CustomZone.run (dart:async/zone.dart:1021:19)
#32     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#33     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#34     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#35     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:115:13)
#36     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:5)

@rashcms did you manage to solve the issue? Do you experience it while using current flutter stable?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Copds 1193 configuration file

Added

Read setting from configuration file ($HOME/.cads-api-client) (priority: parameters > environment variables > configuration file > defaults) (COPDS-1193)

I refactored the global variables out.


Remove reset menu entries

Removes the resetting of menu entries after a loading screen

before:

after:

Not sure if this is good thing to do, maybe Jagex is doing it on purpose?

Their code has a bug here: https://github.com/runelite/runelite/pull/893/files#diff-73ec26a3b1497d01c9b7f3387d9e4f42R123 where they are missing a --var0; maybe we can patch that in?

@Adam- That logic bug shouldn't matter because at the moment I made it restore the menu entries after that code is called


Add meta tags, site properties, and update resources

Added

site.keywords
site.owner.telegram
twitter meta tags
open graph meta tags

Changed

the format of title (ex. "Categories | Leonids")

Updated

jquery 3.2.1
chart.js 2.6.0,
font awesome 4.7.0

Nice work! Thanks for the PR, I'll test it locally coz you updated some libraries and config file. Normally, I'll merge it this weekend if everything works well. 👍

Did you have any problems on testing the commits?

Sorry man, I forgot to get it merged. I've tested and it's fine. Thanks for the PR!

thanks!


Beta - Finding WhiteSpace

Challenge http://beta.freecodecamp.com/challenges/finding-whitespace has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
The second validation does not correctly validate this exercise. The first one is correct (it counts 7 spaces), but the second one should test if the expression equals /\s+/gi and now it only checks /s+/gi the first / is missing imo.
Sidenote: 'sentance' in the testString should be 'sentence'.
var test = (function(){
 var testString = "How many spaces are there in this sentance.";

//Do Not Modify Above

 var expression = /\s+/gi;

//Do Not Modify Below

 return(testString.match(expression).length);
})();(function(){return(test);})();

I've found similar error's in http://beta.freecodecamp.com/challenges/inverting-a-match and http://beta.freecodecamp.com/challenges/finding-numbers


Add sphinx documentation skeleton

@pgrinaway : Since I knocked out the openmmtools documentation skeleton, it took me half an hour to put together a perses docs skeleton too. This can obviously be significantly updated as things get refactored, but it's useful to have at least a starting point since we're going to be working with external users.

That's odd. It's not finding the installed perses for some reason:
Running Sphinx v1.3.5
making output directory...
loading translations [en]... done
loading pickled environment... not yet created
[autosummary] generating autosummary for: analysis.rst, annihilation.rst, bias.rst, changelog.rst, index.rst, installation.rst, rjmc.rst, samplers.rst, storage.rst
WARNING: [autosummary] failed to import u'perses.analysis.Analysis': no module named perses.analysis.Analysis
WARNING: [autosummary] failed to import u'perses.annihilation.HybridTopologyFactory': no module named perses.annihilation.HybridTopologyFactory
WARNING: [autosummary] failed to import u'perses.annihilation.ncmc_switching.NCMCAlchemicalIntegrator': no module named perses.annihilation.ncmc_switching.NCMCAlchemicalIntegrator
...

@pgrinaway : Let me know once you've linked your github account to readthedocs and I'll add you as a maintainer.

Tried that one too...  :)


ref data exac

Exac data computation. This is already run.

If nobody objects, I can delete this PR next week.


Reintroduce generic mobile vr interface

I've only tested this on iPhone, in theory it should work on Android as well. I've also not had any time to polish things up any further. Also right now it gets included on all platforms, I'll change the detect.py file soon to just compile on mobile devices.
There are loads of enhancements possible, definitely room for some more auto detection to setup sensible default values for the hardware you're on.
In essence this is a pretty basic cardboard-esk implementation for mobile VR including using the gyro and accelerometer data for head orientation. It is very similar to my pure GDScript navmesh implementation but now purely done as an ARVR interface.

As always you can use this sample project to test this PR:
https://github.com/BastiaanOlij/godot3_test_projects/tree/master/TestGodotARVR
I'll probably do a video soon to detail things out a little bit

I've also not had any time to polish things up any further. Also right now it gets included on all platforms, I'll change the detect.py file soon to just compile on mobile devices.

I guess it's still needed to build it for tools=yes build so that you can use the API during development, right? But yeah for desktop export templates it could be disabled, unless it prevents making a game use both this API and something else on desktop using simple platform checks.
It seems like you have two lens_distorted.glsl shaders, is that expected?

There are a few specific properties on the interface. I have this problem with ARKit as well where the interface is only available on iPhone and you can't access these functions that are specific to that platform. Kinda hard to avoid but whether that is a good enough reason to compile these interfaces into a desktop version?
In this case we should be able to query the hardware to find out what type of phone you're on and have tables of settings for popular devices. But even then, we don't know which of the hundreds of cheap Chinese HMDs we're using and we can't stock dimensions on all available devices.
Having some control over these parameters may not be avoidable.
I'm not 100% sure what the best course of action is here.
And yes, one of those glsl files should not be there.. oops :)


create is not a member of object com.microsoft.azure.eventhubs.EventHubClient

Hello guys,
I tried to run this on my databricks cluster but it does not work. I tried all the work around mentioned in previous comments but still it does not work. Can you please let me know the fix?
command-4117866950448516:19: error: value create is not a member of object com.microsoft.azure.eventhubs.EventHubClient
val eventHubClient = EventHubClient.create(connStr.toString(), pool)

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

ID: 6fbd2747-9807-4c9b-e07f-819570e054f8
Version Independent ID: 03a288c1-c704-a2d8-b2d1-b200f1463e38
Content: Use Azure Databricks for sentiment analysis
Content Source: articles/azure-databricks/databricks-sentiment-analysis-cognitive-services.md
Service: azure-databricks
GitHub Login: @lenadroid
Microsoft Alias: alehall

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

@prashant-kumar-mishra Thanks for reaching out on this. Just wanted to check if you have tried  using com.microsoft.azure:azure-eventhubs-spark_2.11:<IP_ADDRESS> by changing EventHubClient.create(connStr.toString(), pool) to EventHubClient.createFromConnectionString(connStr.toString(), pool)

Thanks Kranthi, I used the same  and it worked for me.

@prashant-kumar-mishra  We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


FacetStore Per Facet Config and Range Store Option

Slider Min/Max Ranges
There is no way to opt-out of the RangeFacet storage of the min and max ranges. This forces sliders to always retain the starting min and max values. A new option storeRange should be created to prevent the storage of the min and max ranges so that the slider will 'reset' on selection. This option should be configurable on a per facet basis.
Per Facet Configuration
The FacetStore currently has configuration to trim and pinFiltered (and soon to be storeRange) - however these options apply to all facets. We should allow configuration on a 'per facet' basis.
Example showing the facet with field item_price set to not store the range:
settings: {
    facets: {
        fields: {
            item_price: {
                storeRange: false,
            }
        }
    }
}

Work is completed on this branch:
https://github.com/searchspring/snap/tree/facet-store-per-facet-config
Need to finish up with documentation updates and testing - will wait to do testing once controller testing has been completed.


Basic question: How to identify when draggable element is over a particular DOM element?

Like drag:over and drag:out, but for a DOM element with a particular ID.

I have come up with this complex workaround. I think there should be a more simple solution, but coudn't find anything in docs or google.
First I define two different divs both with "draggable" class. First one is the draggable element, the second one is drag over target. I set "display:none;" by default for the second one, so that it is not selectable or draggable when the user loads the page.

Then on drag start I show the hidden div. When the draggable is over it, I get its ID and if it's a correct one, I switch "over" variable to true. And then use this variable to identify if the draggable ended over that particular element or not.

Hey @dziungles
So is the issue here that you want to know when your current draggable mirror is over top some arbitrary element that is not a another draggable "item" (source) or container or dropzone?
If that is true, then I would probably just listen for a mouseover event on these "non-draggable" items you are concerned with, and execute some logic while you are dragging (you could toggle a boolean variable on drag start/end that enables/disables listening for this mouseover).
When it comes to all items being a draggable source or container or dropzone... there are a few examples of this type of behaviour available within the examples folder of this directory. For instance:
https://shopify.github.io/draggable/examples/unique-dropzone.html
In this Droppable example, we are looking for a particular data-attr value to lets us restrict where an element can be dropped.
Another useful example might be the 3 capacity limit:
https://shopify.github.io/draggable/examples/multiple-containers.html
All source code for those examples is available in this repo. Please take a look and let us know if you still have questions.
Cheers!

I was thinking about using 'mouseover', but the problem is that mouseover listener doesn't get the dragging event on mobile.
I think that this "Draggable over the dom element" feature is a very common need, strange that it is not available. For example, in another project I have a draggable element, and then I have a DOM CSS grid. I need to be able to know which grid square the draggable element is over.

Hmm, I may be confused here, but you just want to know when you are over a particular draggable DOM element? drag:over only fires when you are dragging over another draggable element, if you want to find out if you are over a none draggable element (across devices, e.g. including touch), you can use the drag:move event and inspect .on(dragMoveEvent => dragMoveEvent.sensorEvent.target), which tells you which element you are over.
Let me know if that helps, or if I misunderstood something

Yes @dziungles what @tsov suggests should be exactly what you need. I was making the solution more complicated than it needed to be.

Yes, it works great. Thank you for the solution.
Just in tsov's first sentence it should be written: ...over a particular nondragabble DOM element.
Anyway, thanks for a great library. Even though it is quite difficult to understand, the possibilities are amazing. I'm going to continue learning and experimenting with it.

fy6ii


Updated promoted options to tagged options

Campaigns team doesn't always want to promote reportbacks with good photos/captions or sponsors

[ ] remove promoted flag boolean from the database
[ ] Update column name to tagged_options
[ ] Display tagged_options by default on reportback admin form by default, only hide it when flagged is clicked

sounds like we don't want to go this way anymore ¯\_(ツ)_/¯


Integrate standard tests into java SDK

Move the https://github.com/stormeye2000/cspr-sdk-standard-tests-java into the casper-java-sdk repo using the https://github.com/stormeye2000/cspr-standard-tests-resources as a source for SDK test resources.
Will need to create a https://github.com/casper-network/sandard-tests-resources for long-term support across all SDKs

Moved in to [terminus]https://github.com/casper-sdks/terminus-java-tests


use @typedefn rather than @typedef

@typedef is a real thing. We should use a different name to avoid confusing JSDoc.

:herb:


Pan what is inside the element not the element itself.

Hello i have used your awesome plugin and it is really an amazing thing. I have a question that is it possible to move the things inside of the element. Like i have a canvas in which there are different elements. So is it possible to not to move whole canvas but move what is inside the canvas? I have also a chart in canvas and when i pan it moved whole canvas div not the chart only. waiting for your response.

The canvas doesn't contain "different elements". It's just a bitmap surface. There are no "elements" to move.
Options:

Multiple, overlaid canvases
Use some graphics libraries that maintains a list of objects - either bitmap or vector - offscreen and then renders when the object list changes. They usually have some means of appearing to manipulate "objects" on the canvas. (But they are just re-rendering from off-screen list in response to mouse/touch input.) Example: fabric.js


standardize the response variable in the data

Instead of having different columns like key_press, button_pressed, and response, normalize these names to response.

Data variable names need to be checked/changed in the following places:

[ ] all plugin files (jsPsych/plugins)
[ ] test.js files (jsPsych/tests)
[ ] example files  (jsPsych/examples)

And in the following documentation pages:

[ ] https://www.jspsych.org/tutorials/rt-task/
[ ] https://www.jspsych.org/overview/timeline/#looping-timelines
[ ] https://www.jspsych.org/overview/timeline/#conditional-timelines
[ ] https://www.jspsych.org/overview/trial/#the-on_finish-event
[ ] https://www.jspsych.org/overview/trial/#dynamic-parameters
[ ] https://www.jspsych.org/overview/data/#adding-data-to-a-particular-trial-or-set-of-trials
[ ] https://www.jspsych.org/overview/callbacks/#on_finish-trial
[ ] https://www.jspsych.org/plugins/overview/#data-collected-by-plugins
[ ] all plugin docs

@jodeleeuw if a plugin collects multiple responses, should this be called responses or response in the data?

Data variable names need to be checked/changed in the following places:

[ ] all plugin files (jsPsych/plugins)
[ ] test.js files (jsPsych/tests)
[ ] example files  (jsPsych/examples)

And in the following documentation pages:

[ ] https://www.jspsych.org/tutorials/rt-task/
[ ] https://www.jspsych.org/overview/timeline/#looping-timelines
[ ] https://www.jspsych.org/overview/timeline/#conditional-timelines
[ ] https://www.jspsych.org/overview/trial/#the-on_finish-event
[ ] https://www.jspsych.org/overview/trial/#dynamic-parameters
[ ] https://www.jspsych.org/overview/data/#adding-data-to-a-particular-trial-or-set-of-trials
[ ] https://www.jspsych.org/overview/callbacks/#on_finish-trial
[ ] https://www.jspsych.org/plugins/overview/#data-collected-by-plugins
[ ] all plugin docs

@jodeleeuw if a plugin collects multiple responses, should this be called responses or response in the data?

Let's call everything response so there's always one column regardless of which plugins are used.

Let's call everything response so there's always one column regardless of which plugins are used.

The following data properties have been renamed to response in v6.3:

animation: responses
audio-button-response: button_pressed
audio-keyboard-response: key_press
canvas-button-response: button_pressed
canvas-keyboard-response: key_press
categorize-animation: key_press
categorize-html: key_press
categorize-image: key_press
cloze: answers
html-button-response: button_pressed
html-keyboard-response: key_press
iat-html: key_press
iat-image: key_press
image-button-response: button_pressed
image-keyboard-response: key_press
maxdiff: left and right now stored in response object with left and right keys
rdk: key_press
same-different-html: key_press, and key_press_stim1 renamed response_stim1
same-different-image: key_press, and key_press_stim1 renamed response_stim1
serial-reaction-time: key_press
serial-reaction-time-mouse: response_row and response_column now stored in response array as [row,col]
survey-html-form: responses
survey-likert: responses
survey-multi-choice: responses
survey-multi-select: responses
survey-text: responses
video-button-response: button_pressed
video-keyboard-response: key_press
visual-search-circle: key_press
vsl-animate-occlusion: responses


Research how customers configure the  dex app, especially when using k8s-authenticator in WCs

Towards https://github.com/giantswarm/roadmap/issues/489
Fernando might be a good person to ask

Asked in Slack

At the present moment, the CA has to be part of the values.yaml that is used to configure the dex-app.


Improve binary name detection for --upgrade-only

Thanks for --upgrade-only. It's a step in the right direction.
However it fails to work when the last component of the repo is different from the binary name.
Case in point:
❯ agrind --version
ag 0.18.0

❯ ls -lah agrind
-rwxr-xr-x 1 szafar infra 140M May 29 20:15 agrind

# The binary is already latest, but eget starts downloading.

❯ eget --upgrade-only rcoh/angle-grinder -a musl
https://github.com/rcoh/angle-grinder/releases/download/v0.18.0/agrind-x86_64-unknown-linux-musl.tar.gz

# This is because it is trying to find a binary called "angle-grinder", which doesn't exist.

# At first I thought, -f would work, but it doesn't
❯ eget --upgrade-only rcoh/angle-grinder -a musl -f agrind
https://github.com/rcoh/angle-grinder/releases/download/v0.18.0/agrind-x86_64-unknown-linux-musl.tar.gz

And now that I think about it, -f should not be used for this functionality.
We could use another switch for it perhaps? -b isn't used yet, -a for asset, -b for binary?
This would help in cases where we rename binaries from the packages, for eg. releases of GDU: https://github.com/dundee/gdu/ usually have binaries with long name like: gdu_linux_amd64_static, which I manually rename to gdu via mv gdu* gdu.
So, I guess for eget, something like this should work: eget --upgrade-only dundee/gdu -a static -b gdu

This can be achieved by using --to with --upgrade-only
eget --upgrade-only rcoh/angle-grinder -a musl -f agrind --to agrind


Release for v14 support

@ihabzee please can you do a new release for the official REDCap repo? The latest official release there is v1.0.2, which does not work with projects created on REDCap v14+ (i.e. with the new redcap_dataX tables). Thanks!

Hi @lsgs I submitted a new release to the community. I will keep you posted when this is published.
Thanks.

Perfect @ihabzee! Thanks very much for your prompt action!


Added early stopping call back class for python users

Added EarlyStopping class in callback.py for python users to use early stopping strategy.
The modifications are in both callback.py and base_module.py. This is for solving #4965 and #3737.
This new class is following the style of Keras which gives a patience for users to control the rounds they can wait before cancelling out the training.

I've updated the early stopping class so that it saves the model now when the early stopping happens.

I'm going to close the PR since there is no activity for more than 1 month. But please feel free to re-open it and update with the master.