Backend improvements

Some backend improvements:

Why are we creating the docker image with a specific requirements-docker.txt file instead of the requirements.txt file? I think that that makes everything more complex. I was hit by this, and I just did not understand what's going on: I added some dependencies to requirements.txt on development, build the docker image, deploy it, and my dependencies were missing. Why not use the same file to build the docker image? That's what I do in the PR.
Running the update_locale script installed in the virtualenv is wrong. What if several packages install the same script? Which one wins? Nobody knows! I was hit by this too: I had a package installed as a dependency (collective.contentrules.telegram), which is a package generated with bobtemplates.plone boilerplate which also installs the update_locale script in bin (btw, the backend_addon also does this), so when running make i18n in my backend add-on, the installed one was executed, and in my case the collective.contentrules.telegram one was executed. I guess that when running make i18n in our backend folder, we want to update our own package's locales! That's what this PR does, calling update.sh in this very add-on.

I will open a PR removing the requirements-docker.txt
I talked to Érico and he has some ideas about the update_locales scripts, so I will leave that out of the PR.

Sounds like we should close this one then.


Label all problems with the compatible version of swift

A simple comment like so
//  09-14-15 Swift 2.0

This will be a real pain to maintain. What's the long term purpose?

Could we put a small text file in the root dir, like .version and write a script that would replace the line in all of the problems?
Is the 09-14-15 a date? If so, can we use 2015-14-09 so that Europeans don't get confused? When I see things like 02-06-15 I never know if it's February 6th or June 2nd.

This is something that should be part of the language as a @ directive but I don't believe there is a way to mark the swift version of a file yet.
nshipster.com/swift-system-version-checking/
I don't think maintaining this will be a problem if we use a "master" Xcode project so that we could just do a global search and replace in the project when versions change again.
Where should we place such project in the repo directory?
I saw many submittiions of the current problems already using swift beta. The hope is that in the long run this will communicate to the user the version of swift that the file was tested on.

I'm not sure what a master project looks like. Is it a directory? Could we put it at the root level and then put it under "ignored" in the config.json file?

cool. I'll place it in a folder and update the configure file when I do the PR for the update to swift 2.0
as for the comment, I am just going to include this
// Apple Swift version 2.0
This is the standard way the version gets reported in the Swift REPL
http://stackoverflow.com/questions/30790188/how-do-i-see-which-version-of-swift-im-using-in-xcode

With swift 2.2 now we have the ability to check the version using #swift(). I deleted the version string from all the files that had it and added some pre-emptive swift 3.0 checks to the test files in case some people wanted to use the pre-released swift 3.0.
https://github.com/exercism/xswift/commit/ccaa687e3f22b793f8098646e8047de0728b1639


Blender 2.79 frozen when export too hard models

When export to glTF these models, such this...
https://www.cgtrader.com/3d-models/sports/game/chess-set-1549cdc3-f6f0-4625-b1e1-54a541f2d992
Blender freeze. Here are 2 million polygons.

We know this issue and the goal is to integrate critical runtime features of the exporter into Blender.
Also, can you pelase do the following:
Export again and just wait a looooooooooooooooooooooooooooong time. Before this, please open the Blender window console. Maybe you can provide me the output, as I do not have access to the 3D model.

I waited 15 minutes, and exports all happened without stopping.

Thats the reason, why I would like to have the console output. Normally, debug and profiling is enabled.
Also, with this trace, I can see where the exporter did get stuck.
Also, if you could provide me excatly this model does help.

Also, maybe Blender did run out of memory and just crash internally.

Although my rendering is not very fast, 200,000 polygons can hardly endure (the same sponza), not to mention the millions where only 3 fps from strength. This is real-time path tracing.

Can confirm, exporting 1mil polygon mode, waiting for 30 min, still not doing anything.
Will see if i can get a log together.

I'm having trouble with my model, > 200k verts. It does work, it's just very slow.
Do you have any pointers about how to collect profiling data? I'm new to blender, but otherwise a competent programmer. I could give you a few stacktraces, I just don't know where to begin to debug a blender plugin.

Great, that you would like to help on this.
Before export, please open the system console of Blender. This can be done by menu entry "Window->Toggle System Console". During export, there are profiling messages, which indicates, how much time a specific section needs.
For developing, I am using Eclipse plus the PyDev plug-in:
https://wiki.blender.org/index.php/Dev:Doc/Tools/Debugging/Python_Eclipse
We are aware of some bottlenecks and we hope to get some of the Python code into Blender and executed as a C++ method.
But please go ahead, maybe you find something which can already be improved.

Can you guys please try out this fix:
https://github.com/KhronosGroup/glTF-Blender-Exporter/commit/810b522e7f26810f86d39778e445eba336b524a9
A typo could cause a crash for large models.

For my use cases, most of the slow code is the "extract_primitives" function.
It looks like there is code to try to de-dupe vertices, based on your choice of exported data. That sort of micro-processing will be hard to optimise in general. It may not be a big deal in the end, as you seem to limit the search on a per-triangle basis. (forgive me if my interpretation is wrong). Consider having the ability to switch that off.
I'm not a python expert, but I don't expect a hash lookup like this:
attributes['NORMAL'] = xxx
to be fast in any case. A simple optimisation would be to alias those to local variables.
If you are able to get rid of the processing, and to more of a copy operation, then you can also skip the incremental allocations of the arrays;. that should save you some time.
I found another implementation of an exporter that uses a few more tricks:
https://github.com/Kupoman/blendergltf/blob/master/blendergltf.py#L569-L671
This pattern looks like it would be more performant:
vdata = buf.add_accessor(view, 0, vertex_size, Buffer.FLOAT, num_verts, Buffer.VEC3)
...
for j in range(3):
vdata[(i * 3) + j] = co[j]
ndata[(i * 3) + j] = normal[j]
the array access like above, assuming it's not hiding some sort of complex getter/setter, should be fast enough to be used in this type of workload.
In a few minutes I can paste the results of my timings.

Read blend: C:\Users\ncoder\Downloads\Large Cruiser\Starship-blend\Starship.blend
Info: Read library:  'C:\Users\ncoder\extern\glTF-Blender-Exporter\pbr_node\glTF2.blend', '//......\extern\glTF-Blender-Exporter\pbr_node\glTF2.blend', parent ''
Info: Read library:  'C:\Users\ncoder\extern\glTF-Blender-Exporter\pbr_node\glTF2.blend', '//......\extern\glTF-Blender-Exporter\pbr_node\glTF2.blend', parent ''
INFO: Starting glTF 2.0 export
PROFILE: Delta time: 0.0 (asset)
PROFILE: Delta time: 0.0 (images)
PROFILE: Delta time: 0.0 (textures)
PROFILE: Delta time: 0.0010001659393310547 (materials)
PROFILE: Delta time: 0.0 (cameras)
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 59094 Vertices: 59094
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 9474 Vertices: 9474
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 252 Vertices: 252
DEBUG: Adding primitive without splitting. Indices: 25674 Vertices: 25674
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive with splitting. Indices: 65535 Vertices: 65535
DEBUG: Adding primitive with splitting. Indices: 4734 Vertices: 4734
DEBUG: Creating temporary primitive for splitting
DEBUG: Adding primitive with splitting. Indices: 3 Vertices: 3
INFO: Primitives created: 3
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 252 Vertices: 252
DEBUG: Adding primitive without splitting. Indices: 25674 Vertices: 25674
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 6270 Vertices: 6270
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 30 Vertices: 30
DEBUG: Adding primitive with splitting. Indices: 65535 Vertices: 65535
DEBUG: Adding primitive with splitting. Indices: 1602 Vertices: 1602
DEBUG: Creating temporary primitive for splitting
DEBUG: Adding primitive with splitting. Indices: 3 Vertices: 3
INFO: Primitives created: 4
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 3144 Vertices: 3144
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 11880 Vertices: 11880
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 72 Vertices: 72
DEBUG: Adding primitive without splitting. Indices: 49416 Vertices: 49416
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 30 Vertices: 30
DEBUG: Adding primitive without splitting. Indices: 282 Vertices: 282
DEBUG: Adding primitive with splitting. Indices: 65535 Vertices: 65535
DEBUG: Adding primitive with splitting. Indices: 64026 Vertices: 64026
DEBUG: Creating temporary primitive for splitting
DEBUG: Adding primitive with splitting. Indices: 3 Vertices: 3
INFO: Primitives created: 5
INFO: Extracting primitive
DEBUG: Adding primitive with splitting. Indices: 65535 Vertices: 65535
DEBUG: Adding primitive with splitting. Indices: 37728 Vertices: 37728
DEBUG: Creating temporary primitive for splitting
DEBUG: Adding primitive with splitting. Indices: 3 Vertices: 3
DEBUG: Adding primitive without splitting. Indices: 426 Vertices: 426
INFO: Primitives created: 4
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 171 Vertices: 171
DEBUG: Adding primitive without splitting. Indices: 52197 Vertices: 52197
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 216 Vertices: 216
DEBUG: Adding primitive without splitting. Indices: 27720 Vertices: 27720
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 3144 Vertices: 3144
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 47043 Vertices: 47043
INFO: Primitives created: 1
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 78 Vertices: 78
DEBUG: Adding primitive without splitting. Indices: 1368 Vertices: 1368
DEBUG: Adding primitive with splitting. Indices: 65535 Vertices: 65535
DEBUG: Adding primitive with splitting. Indices: 8424 Vertices: 8424
DEBUG: Creating temporary primitive for splitting
DEBUG: Adding primitive with splitting. Indices: 3 Vertices: 3
INFO: Primitives created: 5
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 768 Vertices: 768
DEBUG: Adding primitive without splitting. Indices: 25848 Vertices: 25848
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 108 Vertices: 108
DEBUG: Adding primitive without splitting. Indices: 44664 Vertices: 44664
INFO: Primitives created: 2
INFO: Extracting primitive
DEBUG: Adding primitive without splitting. Indices: 4806 Vertices: 4806
INFO: Primitives created: 1
PROFILE: Delta time: 1348.4236624240875 (meshes)
PROFILE: Delta time: 0.007995843887329102 (nodes)
PROFILE: Delta time: 0.0 (animations)
PROFILE: Delta time: 0.0 (scenes)
PROFILE: Delta time: 0.0 (scene)
INFO: Finished glTF 2.0 export
22 minutes for 348k vertices...

Thank you very much for your investigations.
I agree, that the approach from the link is faster but it does not work, as soon as flat shaded surfaces and/or specific modifiers are used: The exported result does not look like the scene from Blender. We had several issues because of this.
Can you please provide a trace of the same file, where the indices are integers and not shorts?
But I will have another look at the code and investigate, if organizing the data in a different way does speed up things.

Indeed, it's much easier to make fast code if it doesn't need to be correct!
Integers and not shorts: I think you answered why I may be missing the backside of my model after this export.

You are missing the backside in your viewer, but the primitives are in the glTF file, right?
If not, this would be a bug.

The blendergltf addon supports flat shaded surfaces. I double-checked this last night using BlenderPanda, which makes use of blendergltf. Exporting a UV sphere with enough subdiv operations to reach about two million faces took about two and a half minutes in one of our recent tests.
If blendergltf is exporting models incorrectly, we welcome bug reports. One of our key goals is performance, but not at the cost of correctness.

Can oyu guys please try out the fix mentioned here:
https://github.com/KhronosGroup/glTF-Blender-Exporter/issues/85

Seems to be fixed/does not appear on our side anymore.


New version: Bloqade v0.1.14

Registering package: Bloqade
Repository: https://github.com/QuEraComputing/Bloqade.jl
Created by: @Roger-luo
Version: v0.1.14
Commit: 6854d20eb188822592622c2631a31ee9857b3c62
Reviewed by: @Roger-luo
Reference: https://github.com/QuEraComputing/Bloqade.jl/commit/6854d20eb188822592622c2631a31ee9857b3c62#commitcomment-88097084
Description: Package for the quantum computation and quantum simulation based on the neutral-atom architecture.

@Roger-luo please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]

Thanks this is due to https://github.com/cjdoris/MicroMamba.jl/issues/9
I'll wait for that issue to be fixed before trying again
[noblock]


Update Repo

Update your Pex repo to be equal with the actual Pex repo.

We use a different branch.
See:
https://github.com/LuckyPrison/PermissionsEx/tree/1.23.x


pyarrow darwin debug

This is not a PR. I will try to debug build failure of pythonPackages.pyarrow on hydra/ofborg darwin.

Success on x86_64-darwin (full log)
Attempted: arrow-cpp
Partial log (click to expand)
/nix/store/nwzslpknyj47wvn8a92jzk4hnghfsxvk-arrow-cpp-0.11.0

Success on aarch64-linux (full log)
Attempted: arrow-cpp
Partial log (click to expand)
copying path '/nix/store/h6chbrl3id66ix25qxi6wfgcaxrww4li-zlib-wrap' from 'https://cache.nixos.org'...
copying path '/nix/store/86qhx77m6arqv48asri32rf87di9c4h0-flex-2.6.4' from 'https://cache.nixos.org'...
copying path '/nix/store/xjkv63j8zx3ncsl1bc7ys891qiwr96p7-lz4-1.8.3-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/xaqc8a6781v43g0n4fr454fwj7pmlh1q-brotli-1.0.7' from 'https://cache.nixos.org'...
copying path '/nix/store/pfyf2ylncaa100lp68wryjcnc8p8r9fj-lz4-wrap' from 'https://cache.nixos.org'...
copying path '/nix/store/1az0lanjb64an8fhh10bazkyh9v8mlqv-thrift-0.11.0' from 'https://cache.nixos.org'...
copying path '/nix/store/6nfr1mycib6kvyg8973xwydnmcxrc9ja-brotli-1.0.7-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/in2n6136vr9irr7b96ilw6vdml1ppzdc-brotli-wrap' from 'https://cache.nixos.org'...
copying path '/nix/store/ynnd3lx3fzfn5kza1rv8yx8ns6bpg4mf-arrow-cpp-0.11.0' from 'https://cache.nixos.org'...
/nix/store/ynnd3lx3fzfn5kza1rv8yx8ns6bpg4mf-arrow-cpp-0.11.0

Success on x86_64-linux (full log)
Attempted: arrow-cpp
Partial log (click to expand)
these paths will be fetched (2.17 MiB download, 20.91 MiB unpacked):
  /nix/store/c2gwp55la3ki703qd095zkcgzjc4s3qh-brotli-wrap
  /nix/store/jwmryl6i1qrksnizml0jx7ldxxy59j17-arrow-cpp-0.11.0
copying path '/nix/store/c2gwp55la3ki703qd095zkcgzjc4s3qh-brotli-wrap' from 'https://cache.nixos.org'...
copying path '/nix/store/jwmryl6i1qrksnizml0jx7ldxxy59j17-arrow-cpp-0.11.0' from 'https://cache.nixos.org'...
/nix/store/jwmryl6i1qrksnizml0jx7ldxxy59j17-arrow-cpp-0.11.0

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/3bbn9cwdw9hhm3f1vicnkv51hdc381yb-compiler-rt-5.0.2-dev/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/3bbn9cwdw9hhm3f1vicnkv51hdc381yb-compiler-rt-5.0.2-dev/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/d5jmx80825gx48dq15q1a16h71yi6l8b-openblas-0.3.3/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/d5jmx80825gx48dq15q1a16h71yi6l8b-openblas-0.3.3/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/0mha803yql9q7b6h93m8940z3sjbhiy8-python3-3.6.6/include' [-Wunused-command-line-argument]
clang-5.0: warning: argument unused during compilation: '-isystem /nix/store/0mha803yql9q7b6h93m8940z3sjbhiy8-python3-3.6.6/include' [-Wunused-command-line-argument]
building of '/nix/store/5dm1i908szra6mr8bwwbhrv81isbcjx5-python3.6-scipy-1.1.0.drv' timed out after 1800 seconds
cannot build derivation '/nix/store/cqcnfzagb9qyg42qhqggiwnavw3959xx-python3.6-pandas-0.23.4.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/g0cnxwfnmcqmbl614djz94m80a6w0r04-python3.6-pyarrow-0.11.0.drv': 2 dependencies couldn't be built
error: build of '/nix/store/g0cnxwfnmcqmbl614djz94m80a6w0r04-python3.6-pyarrow-0.11.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/g0cnxwfnmcqmbl614djz94m80a6w0r04-python3.6-pyarrow-0.11.0.drv' failed with exit code 1
error: build of '/nix/store/g0cnxwfnmcqmbl614djz94m80a6w0r04-python3.6-pyarrow-0.11.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/f4d6ccir0p6008p6ds3x4my9hsggzxss-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/f4d6ccir0p6008p6ds3x4my9hsggzxss-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: python3Packages.pyarrow
Partial log (click to expand)
Cannot nix-instantiate `python3Packages.pyarrow' because:
error: while evaluating 'callPackageWith' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndndx-vm/lib/customisation.nix:108:35, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndndx-vm/pkgs/top-level/python-packages.nix:399:13:
while evaluating 'makeOverridable' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndndx-vm/lib/customisation.nix:67:24, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndndx-vm/lib/customisation.nix:112:8:
undefined variable 'attrs' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndndx-vm/pkgs/development/python-modules/pyarrow/default.nix:58:23

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)
Cannot nix-instantiate `python3Packages.pyarrow' because:
error: while evaluating 'callPackageWith' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:108:35, called from /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/pkgs/top-level/python-packages.nix:399:13:
while evaluating 'makeOverridable' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:67:24, called from /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:112:8:
undefined variable 'attrs' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/pkgs/development/python-modules/pyarrow/default.nix:58:23

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)
Cannot nix-instantiate `python3Packages.pyarrow' because:
error: while evaluating 'callPackageWith' at /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/lib/customisation.nix:108:35, called from /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/pkgs/top-level/python-packages.nix:399:13:
while evaluating 'makeOverridable' at /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/lib/customisation.nix:67:24, called from /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/lib/customisation.nix:112:8:
undefined variable 'attrs' at /var/lib/gc-of-borg/nix-root/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/gleber-bastion/pkgs/development/python-modules/pyarrow/default.nix:58:23

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/i6vfgcm28c6l6571wwdxpqb0swfavs97-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/i6vfgcm28c6l6571wwdxpqb0swfavs97-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/kj7bf3ngw1cqq9lf1wfvf1w4qfpkdwrr-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/kj7bf3ngw1cqq9lf1wfvf1w4qfpkdwrr-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python2Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python2Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python2Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python2Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/blvdim54mlnx4kpg8ndlaj47wv25243q-python2.7-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/blvdim54mlnx4kpg8ndlaj47wv25243q-python2.7-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/w64cawvadna4d9jmv2s93s3ag4s8ynzy-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/w64cawvadna4d9jmv2s93s3ag4s8ynzy-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
builder for '/nix/store/gfdqcp5sz2ayckggn8jf3n0wlm6il9xj-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/gfdqcp5sz2ayckggn8jf3n0wlm6il9xj-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=1 errors=1 failures=0>
builder for '/nix/store/j6z7dqghrm78kgnba77b8fd74l70gc0g-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/j6z7dqghrm78kgnba77b8fd74l70gc0g-python3.6-pyarrow-0.9.0.drv' failed

Failure on aarch64-linux (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
  /nix/store/i2a86rn0ashqnsgh0f9gj7kaxb772zw9-python3.6-pandas-0.23.4/lib/python3.6/site-packages/pandas/core/internals.py:312: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
    return self.values[slicer]
  /nix/store/i2a86rn0ashqnsgh0f9gj7kaxb772zw9-python3.6-pandas-0.23.4/lib/python3.6/site-packages/pandas/core/indexes/datetimelike.py:428: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
    result = getitem(key)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 5 failed, 16897 passed, 1027 skipped, 11896 deselected, 37 xfailed, 2 xpassed, 10 warnings in 615.13 seconds
builder for '/nix/store/4xw8mkbil3jmnjpr51bp78abrr76hk38-python3.6-pandas-0.23.4.drv' failed with exit code 1
cannot build derivation '/nix/store/fridzab52s62wqxxrkwb6ccm30x1k80q-python3.6-pyarrow-0.9.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/fridzab52s62wqxxrkwb6ccm30x1k80q-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on aarch64-linux (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
  /nix/store/i2a86rn0ashqnsgh0f9gj7kaxb772zw9-python3.6-pandas-0.23.4/lib/python3.6/site-packages/pandas/core/internals.py:312: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
    return self.values[slicer]
  /nix/store/i2a86rn0ashqnsgh0f9gj7kaxb772zw9-python3.6-pandas-0.23.4/lib/python3.6/site-packages/pandas/core/indexes/datetimelike.py:428: FutureWarning: Using a non-tuple sequence for multidimensional indexing is deprecated; use `arr[tuple(seq)]` instead of `arr[seq]`. In the future this will be interpreted as an array index, `arr[np.array(seq)]`, which will result either in an error or a different result.
    result = getitem(key)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
 5 failed, 16897 passed, 1027 skipped, 11896 deselected, 37 xfailed, 2 xpassed, 10 warnings in 599.36 seconds
builder for '/nix/store/4xw8mkbil3jmnjpr51bp78abrr76hk38-python3.6-pandas-0.23.4.drv' failed with exit code 1
cannot build derivation '/nix/store/mw53qazb353421rjzzvw6yjm3a7sw08m-python3.6-pyarrow-0.9.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/mw53qazb353421rjzzvw6yjm3a7sw08m-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
++ '[' -z '' ']'
++ return 0
+ set -u
+ eval 'set +o nounset'
++ set +o nounset
+ return 0
+ '[' -n '' ']'
+ exit 1
builder for '/nix/store/gpkvm65gazpq3sd9k9mn5x8q51cyf11b-python3.6-pyarrow-0.9.0.drv' failed with exit code 1
error: build of '/nix/store/gpkvm65gazpq3sd9k9mn5x8q51cyf11b-python3.6-pyarrow-0.9.0.drv' failed

@GrahamcOfBorg build python3Packages.pyarrow

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: python3Packages.pyarrow
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: python3Packages.pyarrow
Partial log (click to expand)
tests/test_parquet.py::test_backwards_compatible_index_multi_level_named
  /private/tmp/nix-build-python3.6-pyarrow-0.9.0.drv-0/apache-arrow-0.9.0/python/tests/test_parquet.py:1607: ParserWarning: Falling back to the 'python' engine because the 'c' engine does not support regex separators (separators > 1 char and different from '\s+' are interpreted as regex); you can avoid this warning by specifying engine='python'.
    sep=r'\s{2,}', index_col=['cut', 'color', 'clarity'], header=0

tests/test_parquet.py::test_backwards_compatible_index_multi_level_some_named
  /private/tmp/nix-build-python3.6-pyarrow-0.9.0.drv-0/apache-arrow-0.9.0/python/tests/test_parquet.py:1633: ParserWarning: Falling back to the 'python' engine because the 'c' engine does not support regex separators (separators > 1 char and different from '\s+' are interpreted as regex); you can avoid this warning by specifying engine='python'.
    sep=r'\s{2,}', index_col=['cut', 'color', 'clarity'], header=0

-- Docs: https://docs.pytest.org/en/latest/warnings.html
======== 617 passed, 75 skipped, 3 xfailed, 8 warnings in 13.53 seconds ========


Open links in new tab

On the main anthology page, clicking on a conference could open it in a new tab. Also, on the proceedings page, clicking on papers could open them in  new tabs. This is helpful when browsing a number of proceedings in parallel. Of course, one can have the same effect with Ctrl+click or middle click.

Thanks for the feedback!
I think forcing new tabs would take away control from the user. When you're just browsing the IR Anthology, opening new tabs for these clicks would be rather annoying IMO. If a user intends to open a new tab, they can easily do this using Ctrl or MMB (as you've pointed out already). However, we might have a look into additional navigational elements on every site.
The only case where I would see a benefit is when linking to PDFs, as they usually don't provide links/navigation. (To some degree this also applies to 3rd party sites.)

Thanks Sebastian for the response. Yes, you are right, opening links in new
tabs and windows is more of a personal preference - some like it, some not
so much. One could also right click and open in a new window. My
suggestions were also motivated by the Google SERP, where clicking on a
link opens a new tab. However, I see that this is customizable, and I may
have set this option long back :). It's also probably best to stick to the
tried and tested design principles of the ACL anthology, where links open
in the same window.
Yes, new tabs could be useful for opening PDFs or the ACM DL or Springer
links (there's often quite some latency in going back to the IR anthology
page, that in fact can sometimes be annoying - the ACL one doesn't have
this problem as it's all internal).
Regards,
Rishi.
On Mon, Jul 19, 2021 at 3:27 PM Sebastian Günther @.***>
wrote:

Thanks for the feedback!
I think forcing new tabs would take away control from the user. When
you're just browsing the IR Anthology, opening new tabs for these clicks
would be rather annoying IMO. If a user intends to open a new tab, they can
easily do this using Ctrl or MMB (as you've pointed out already). However,
we might have a look into additional navigational elements on every site.
The only case where I would see a benefit is when linking to PDFs, as they
usually don't provide links/navigation. (To some degree this also applies
to 3rd party sites.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ir-anthology/ir-anthology/issues/68#issuecomment-882547437,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4DFHROFX5LBFGP7DBF5U3TYQR4JANCNFSM5AQUOUWQ
.

--
Senior Researcher
Databases and Information Systems Group (D5)
Max Planck Institute for Informatics
Campus E1.4, 66123 Saarbrücken, Germany.
Office phone: +49-681-93255007
Web: http://people.mpi-inf.mpg.de/~rsaharo/

i opened a new issue for the requested change.

Thanks for your feedback!


controllers: fix typo for volumereplicationclasses

Fix a typo for volumereplicationclasses because of which the container was not starting.
Followup for: https://github.com/red-hat-storage/ocs-client-operator/pull/276

/jira backport release-4.18


Add a simple template API object that assists with config parameterization

Description
Simple config parameterization is an important tool for extending the utility of example config. This feature will add an API object that represents a set of standard parameters and a list of objects with replacement syntax, a minimal set of CLI commands that transform templates + parameters into a list of API objects, and an API endpoint that allow templates to be stored.
Progress Tracker

[ ] Before Alpha

[ ] Design Approval

[ ] Design Proposal
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is: @smarterclayton for now

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Before Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials

Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

[ ] Thorough API review

cc @kubernetes/api

[ ] Before Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md

cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

Not in 1.4

Some relevant discussion has taken place here: kubernetes/kubernetes#30716

I propose removing the 1.5 milestone from this feature.
I'd like to be involved in the discussion about it, but I cannot do that and help drive PetSet to Beta at the same time, so I'd like it to wait until after 1.5.

@smarterclayton do you have any comments regarding @erictune's suggestion above? If it's ok for you, I'll proceed with milestone changes.

/subscribe @mtaufen
/cc @mikedanese @thockin
So we stay in the loop as this seems related to configmaps/dynamic kubelet/other component config/etc.

Moving this out of 1.5 - there's not enough bandwidth right now to implement and the time window is too short.  Work will continue in the background.

@smarterclayton is this relevant anymore?

No, this is out of date and can be closed.


How to convert mcap file to rosbag?

Description
I want to convert a nuscenes mcap file to rosbag, how to do this?

Version:
Platform:

Steps To Reproduce

Expected Behavior

@poodarchu This is a question and not a bug. Please be mindful of what label you use when opening an issue. Questions are better routed to the discussion board here: https://github.com/orgs/foxglove/discussions or our community slack.


monitor rss updates

Can this plugin be used to monitor the frequency of updates on an RSS feed and be used as a source for alerts when expected updates are not available? I have approximately 100 feeds to monitor that should be updating several times a week.

@tomdavidson It's an interesting question. This plugin was designed to display an RSS feed, monitoring is a different use case.
I am thinking of collecting feed updates as time series. Then adding monitoring and alerting using a time series panel.
Let me know if there is anything else.

Thanks for the quick response and clarity. It does seem to a different concern and prob worth a different plugin.


Update list of frontend examples in README

This list contained an example that is no longer rendered by Whitehall, so that has been removed. Also adding examples of all other document types rendered by Whitehall, so there are examples of all currently rendered documents.
Updates can be made when rendering is moved away, until the list is fully removed.
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Thanks @kevindew, I'd forgotten about these things.  I've added them to the README.


Move Constraints to API

Looking for feedback on what would be sufficient to include in the Constraint Environment interface.

It may make sense to move constraints package into the public API like like was done with iterators.  Thinking this for the following reasons.

All the types in the package could easily be moved to the public API
Except for KeyExtent I think the types referenced by the package are in the public api in the data and security packages.
The interfaces have been stable since at least 2012 Accumulo (except for the addition of a single method I think), but probably since Accumulo was open sourced.
Users have been encouraged to use the interfaces by Documentation for a very long time https://accumulo.apache.org/docs/2.x/getting-started/table_configuration#constraints
Like iterators these classes deal with user data, for me when something has that purpose I think public API.
The method that returns a KeyExtent could be deprecated for removal for now if the package is promoted to public API.

ConstraintCheckerTest is failing due to this change:
https://github.com/apache/accumulo/pull/1985/files#diff-9b57b5f5a5804a57cdd64ac2b0aaeb91bea33de80cc1f11023c3c175376d0ed6R88
I will rewrite the Mocks once we finalize the rest of this PR.

@ctubbsii @keith-turner would like to get your thoughts on the Constraints API. I made a new Constraint and Violations in org.apache.accumulo.core.data.constraints. I made the Constraint interface and Violations class extend the new ones. I copied over the Constraint implementations that we have provided to users (DefaultKeySizeConstraint, NoDeleteConstraint and VisibilityConstraint) to the new package. I am not sure if this is what we want though. I didn't think it necessary to create new versions of these classes since they aren't changing but the move will break usage of the classes and break any user classes extending them.
Also, do you think we need to create 2 versions of tests? I currently just copied the old tests to the new package and made them use the new classes. I think it would be nice to at least have a test that maintains the deprecated functionality to ensure I haven't broken anything.

@ctubbsii @keith-turner would like to get your thoughts on the Constraints API. I made a new Constraint and Violations in org.apache.accumulo.core.data.constraints. I made the Constraint interface and Violations class extend the new ones. I copied over the Constraint implementations that we have provided to users (DefaultKeySizeConstraint, NoDeleteConstraint and VisibilityConstraint) to the new package. I am not sure if this is what we want though. I didn't think it necessary to create new versions of these classes since they aren't changing but the move will break usage of the classes and break any user classes extending them.
Also, do you think we need to create 2 versions of tests? I currently just copied the old tests to the new package and made them use the new classes. I think it would be nice to at least have a test that maintains the deprecated functionality to ensure I haven't broken anything.

I think I found a good solution in 667880f. I moved the old tests to the new API package and created a new test called OldConstraintTest. The OldConstraintTest is a consolidation of all the old tests so we can maintain backwards compatibility. I also had to create a new method name for the check method because I couldn't get around the ambiguous method name error. Let me know what you guys think.

@milleruntime if someone configures one of the constraints that ship w/ Accumulo using the old package, like org.apache.accumulo.core.constraints.VisibilityConstraint is there anything that will make this work?  I looked and did not see anything.

@milleruntime if someone configures one of the constraints that ship w/ Accumulo using the old package, like org.apache.accumulo.core.constraints.VisibilityConstraint is there anything that will make this work? I looked and did not see anything.

No there is nothing to handle that. I assume as this PR is now, a runtime error like a ClassNotFoundException would occur. I think we could add something to the upgrade code to check configuration for old package names and either rename or warn the user. Otherwise I am not sure how we could handle this cleanly internally.

Otherwise I am not sure how we could handle this cleanly internally.

Would it be possible to create classes in the old package and that extend the new classes?  Like a VisConstraint class in the old package that simple extends the new VisConstraint class.  This makes it easy to configure either.

I fired up Uno, created a table and then updated the core jar with these changes. I didn't see any errors until I tried to insert data into the table:

root@uno test> insert row3 cf cq val1
	Constraint Failures:
		ConstraintViolationSummary(constrainClass:org.apache.accumulo.tserver.constraints.UnsatisfiableConstraint, violationCode:-1, violationDescription:Failed to load constraints, not accepting mutations., numberOfViolatingMutations:1)

I also noticed that the table came with org.apache.accumulo.core.constraints.DefaultKeySizeConstraint=1 by default. So this may be trickier than I had originally thought.

Otherwise I am not sure how we could handle this cleanly internally.

Would it be possible to create classes in the old package and that extend the new classes? Like a VisConstraint class in the old package that simple extends the new VisConstraint class. This makes it easy to configure either.

I think so but the existing check() method causes a "method does not override or implement a method from a supertype" cause of the Override annotation. I don't think that the Override annotation will make a difference (my understanding is that it is just for the compiler to check your code but doesn't change the actual compiled code) but the classes will compile if I remove it. I can also override the new method and make it call the old one like I did with the old Constraint interface.

@Override
  public List checkMutation(Environment env, Mutation mutation) {
    return check(env, mutation);
  }

I tested the latest changes on an upgrade and they work fine. I created the table test with the old code, installed new code and then ran:

root@uno test> constraint -l
org.apache.accumulo.core.constraints.DefaultKeySizeConstraint=1
org.apache.accumulo.core.constraints.VisibilityConstraint=2
root@uno test> insert row3 cf cq val1
root@uno test> scan
row1 cf:cq []	val1
row2 cf:cq []	val2
row3 cf:cq []	val1
root@uno test> createtable test2
root@uno test2> constraint -l
org.apache.accumulo.core.data.constraints.DefaultKeySizeConstraint=1
root@uno test2> constraint -a org.apache.accumulo.core.constraints.VisibilityConstraint
Added constraint org.apache.accumulo.core.constraints.VisibilityConstraint to table test2 with number 2
root@uno test2> insert row3 cf cq val1
root@uno test2> scan
row3 cf:cq []	val1
root@uno test2> constraint -l
org.apache.accumulo.core.constraints.VisibilityConstraint=2
org.apache.accumulo.core.data.constraints.DefaultKeySizeConstraint=1

I think the only other thing we could do is to print a warning if someone uses the deprecated Constraints.

There are two possible options, one is to extend and make the class final like the following. This supports configuring the class, but does not support anyone extending the class in java. This would break any class extending the class.

What if we don't make the class final? This would allow users to keep their current class that extends the deprecated class. I think they would get a warning about their class being deprecated then. Although they will probably only see the warning if they recompile after upgrading.

What if we don't make the class final?

That could be a possibility.  Would need to look at the new class hierarchy and make a determination about what the behavior is relative to prev Accumulo release.  I just threw the final in to avoid that analysis w/ the assumption that it no longer offers the same behavior.  But I have no idea if the behavior is the same.

Next I am going to redo OldConstraintsTest and have it test old classes extending the new ones to make sure they work.

I started creating a test to test a class that extends a deprecated constraint but I think I found a bug in one of the old classes https://github.com/apache/accumulo/pull/2025
This is on hold again until I get that fixed. Then I will update the tests to test a user extending the deprecated classes.

I added a test for extending the deprecated constraint and tested upgrading in Uno. Regardless of what happens with #2025, I think the Constraint API is ready to go. @ctubbsii @keith-turner do you want to give it one final look?

It looks like DefaultKeySizeConstraintTest is failing because of the recent change to reuseForks. I tested locally and setting <surefire.reuseForks>false</surefire.reuseForks> allows the test to pass.

I added DefaultKeySizeConstraintTest to reuseForks exceptions and tests are now passing. I think this is ready to merge.


Looking for a new Jupyter Server/Kernel's Meeting Host!

Hey folks,
After emceeing the Jupyter Server/Kernels meeting for nearly 5 years, I think it's time (long overdue probably 😅) for me to step aside and let someone else drive these meetings.
In case you were worried, I'm not going anywhere 😉. I still plan to show up to every meeting that I can. The Jupyter Server call is one of my favorite places to hang, but I'd live to give the opportunity for someone else to run these.
If you're interested, but maybe a little intimidated, that's okay too! I'm also happy to co-host for a little while, or alternate weeks with someone until they feel comfortable enough to drive on their own. Just reach out here, or privately over email, and I'm happy to coordinate with you.

It's important to note that hosting meetings is not necessarily a responsibility of the SSC repo. I did both at the same time, and probably shouldn't have. I, personally, think it's better if two different people do these roles, but totally up to the team here.

Thanks for calling this out and helping drive the meetings so far. I can help with this, maybe on a part time basis initially before committing full-time.


Add all operations through the UI and APIs as metadata operations

Feature
We support a few UI operations such as editing descriptions, adding tags, etc..
As part of this task, we are going to instrument all the operations in JsonSchema such as adding a test, view data profiler, view schema, etc..
This will allow admins to create policies by grouping operations and associating this policy with a role.

This has been addressed by work so far done in #4199


Possible to bind to specific IP for outgoing requests?

Hi!
Is it possible to bind outgoing requests to a specific IP given to the machine's NIC? Usually done through ServicePoint.BindIPEndpointDelegate
Thanks

Yes.
https://github.com/justcoding121/Titanium-Web-Proxy/blob/develop/Titanium.Web.Proxy/ProxyServer.cs#L124
Adjust ProxyServer.UpStreamEndPoint

Rockstar! Thanks!


Changes for internal compatibility

FixMatchAll assertion to do untyped comparison by default
stringify to strip tailing 0 in fraction (float 0.0 => '0')
bind_entry to return the assertion result without converting to bool
add RE class

Yet to add some test for FixMatchAll assertion...


CODEX

Hello, thanks for an awesome package! I am currently trying to extract image features within a segmentation mask and here is my set up so far:
mpif = tiff.imread('mpif_cropped.ome.tiff')
mask = tiff.imread('cellpose_mask_cropVFS-25489.ome.tif')
hae = tiff.imread('hae_cropped.ome.tiff')
image = sq.im.ImageContainer(mpif, layer='mpif')
image.add_img(mask, layer='mask')
image.add_img(hae, layer='hae')
adata = ad.AnnData(obs=pd.DataFrame(index=range(len(centroids))), obsm={"spatial": centroids})
adata.uns['spatial'] = {'images' : image}
sq.im.calculate_image_features(     adata,     img=image,     layer='mpif',     features='segmentation',     n_jobs=16,     features_kwargs={         'segmentation': {             'props': ['area', 'centroid'],             'label_layer': 'mask'         }     } )
I'm thinking there's a problem with the way I'm registering adata.uns['spatial'], another option I've tried is:
spatial_key = "spatial"
library_id = "CHANGE"
adata.uns[spatial_key] = {library_id: {}}
adata.uns[spatial_key][library_id]["images"] = {}
adata.uns[spatial_key][library_id]["images"] = {"hires": np.transpose(mpif, (1,2,0))}
adata.uns[spatial_key][library_id]["scalefactors"] = {     "tissue_hires_scalef": 1,     "spot_diameter_fullres": 0.5, }
Which is closer to the documentation but still I am unable to get the feature extraction to work. It seems that it cannot find the segmentation mask. Is there a way around this? Thanks!

I think part of the problem is that when you run calculate_image_features() it attempts to first do spot cropping. any way around that?

Hi @matthew-lee1, thank you for using squidpy.
For loading CODEX data i would highly recommend to use the specified reader codex() from spatialdata-io. This package makes reading spatial omics data very easy and efficient.


[fix] Opendata::Dataset::ExportJob : use perform_later

Coverage decreased (-20.8%) to 63.839% when pulling ce19dc8087d49a66b300488181634375e83d5ed0 on itowtips:fix-opendata-export-job into d9225e6b94ad2869d2c377d1fddce89c2b3d8f8d on shirasagi:master.


Replicator throws exception

Hello,
I when run the replicator it thows exception in cbl_service.dart file. The method return type needs integer but its returning no thing when i run the app it gets crashed .
i am using   cbl_flutter: ^2.0.6 , cbl_flutter_ee: ^2.1.6 in my pub file
to fix this issue i did some work around which starts the replication process smoothly here is my work around
**//first i added try catch block**
 try {
      final replicator = await FfiReplicator.create(
        config,
        // The isolate running this service should not be crashed by unhandled
        // errors in the callbacks registered by the client. The client is
        // responsible for reporting those errors as unhandled in its isolate.
        ignoreCallbackErrorsInDart: true,
      );
      return _objectRegistry.addObject(replicator); **// --> removed await from here**
    } catch (e) {
      // Handle the exception here
      print('An exception occurred creating the replicator: $e');
    }

    return 1; **// <--- then returned integer**

name: crud_app
version: 1.0.0+1
publish_to: none
description: A new Flutter project.
environment:
  sdk: '>=2.19.6 <3.0.0'

dependencies:
  cupertino_icons: ^1.0.2
  get: 4.6.5
  flutter:
    sdk: flutter
  flutter_animated_dialog: ^2.0.1
  dropdown_button2: ^2.1.0
  cbl: ^2.1.8
  cbl_flutter: ^2.0.6
  cbl_flutter_ee: ^2.1.6
  intl: ^0.18.0
  flutter_animator: ^3.2.2

dev_dependencies:
  flutter_lints: ^2.0.0
  lints: 2.0.1
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true

my replication method

static Future replicateIniDb() async {
    try {
      final replicator = await Replicator.create(
        ReplicatorConfiguration(
          database: DbConnection.getIniDatabaseInstance!,
          target: UrlEndpoint(
            Uri.parse('ws://localhost:4984/$iniBucket'),
          ),
          continuous: true,
          replicatorType: ReplicatorType.pushAndPull,
          authenticator:
              BasicAuthenticator(username: 'sync', password: 'sync12345'),
          enableAutoPurge: false,
        ),
      );

      await replicator.addChangeListener((change) {
        print('Replicator activity ini db: ${change.status.activity}');
      });

      await replicator.start();
    } catch (e) {
      // Handle the exception here
      print('An exception occurred: $e');
    }
  }

Error it throws is
ERROR: ../../.pub-cache/hosted/pub.dev/cbl-2.1.8/lib/src/service/cbl_service.dart:551:15: Error: A non-null value must be returned since the return type 'int' doesn't allow null.
cbl_service.dart:551
ERROR:   Future<int> _createReplicator(CreateReplicator request) async {
ERROR:               ^
ERROR: Target kernel_snapshot failed: Exception
Exception: Build process failed
Exited (sigterm)

Thanks for the additional infos. Please also provide the output of running flutter --version.

Flutter 3.7.11 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f72efea43c (2 weeks ago) • 2023-04-11 11:57:21 -0700
Engine • revision 1a65d409c7
Tools • Dart 2.19.6 • DevTools 2.20.1

Hm, unfortunately I'm unable to replicate this issue. Could you provide a complete example with all the steps necessary to reproduce the problem?


Bug: some raster colours don't display hazard value on hover

Not all raster cells have numerical value displayed in tooltip on hover
Compare two cells from cyclones layer:

The issue seems to be with the looking up of the colour value. Perhaps the colour comparison has inaccuracies that cause no lookup value to be returned from the legend.

After a bit of investigation - when this happens, the RGB value of the raster colour doesn't match any of of the entries in the legend/colormap. The r,g,b colour components can be off by just 1, which then results in no value being found for this colour.
Need to investigate further to establish if the problem is in the rendering of correct images received from the tile server, or if it's Terracotta that send images and legend values that don't match up.

The values in the raster tiles are indeed mismatched with the values from Terracotta's /colormap endpoint. I filed an issue here: https://github.com/DHI-GRAS/terracotta/issues/249


Game scanner not working with EA play

Installed the games, game scanner doesn’t pick them up at all. Unsure what to do other than play the ea play each time but this is frustrating as I need to rebind all my controls.

@corbett3289 using desktop or plugin? Any logs? Should be in the downloads folder

Was using desktop. I ended up reinstalling the launcher and repairing the install and it was able to find the game then. Not sure what the issue was. But since its resolved i'll close the issue.


Subnet scanner > Unable to get mac address in target 33

I am unable to retrieve the MAC address from the IP, and the list of devices in the subnet scanner option is incomplete.

Hello, sorry for not responding in such a long time.
This is not a bug, Google has restricted access to this part of API for non-system apps (and devices without root access) targeting targetSdk 32 and higher.
According to Android Developers - MAC address availability changes in Android 11, they have announced a change to the MAC address availability if you target Android 11 (or higher):

In addition, non-privileged apps can't access the device's MAC address; only network interfaces with an IP address are visible. This impacts the getifaddrs() and NetworkInterface.getHardwareAddress() methods, as well as sending RTM_GETLINK Netlink messages.
The following is a list of the ways that apps are affected by this change:

NetworkInterface.getHardwareAddress() returns null for every interface.
Apps cannot use the bind() function on NETLINK_ROUTE sockets.
The ip command does not return information about interfaces.
Apps cannot send RTM_GETLINK messages.

I'm going to close this issue as I'm not currently aware of any possible fix or workaround for this behaviour.

I figured it out using API


Can't load avatar textures in pakaged build

Describe the bug
After I package your example, I can load avatar textures when playing the avatar creator map in the build.
But when I package my project, I can't.
To Reproduce
Steps to reproduce the behavior:

Create third person C++ project.
Add plugins ready player me, avatar creator and glTF plugins.
Migrate the avatar creator widget and game mode from example project.
Package the project using Project Launcher tool
Play.

Expected behavior
Avatar textures should be loaded properly.
Screenshots
https://github.com/readyplayerme/rpm-unreal-avatar-creator/assets/65440815/4dc649dc-7cd1-45eb-827a-9efeb9f1fc44
Desktop (please complete the following information):

RpmAvatarCreator plugin version: https://github.com/readyplayerme/rpm-unreal-avatar-creator/tree/5e67a9727383b3548cf4579b9ed28da6ef4ea123
ReadyPlayerMe plugin version: https://github.com/readyplayerme/rpm-unreal-sdk/tree/3313e5c47105f52744b6d401049ce8279ea4269f
glTFRuntime plugin version: https://github.com/rdeioris/glTFRuntime/tree/0b67abfd22f873c06fd8abee6b68f5696a535e96
Unreal Engine version 5.0.3
Operating System: Windows
Platform: Windows Build

Please add the /glTFRuntime to the te additional asset directories to cook. We will automate this process in the next release.
Docs

Thank you. I would like to contribute the automation: https://github.com/readyplayerme/rpm-unreal-sdk/pull/30


fixed escape chars in css highlighting

Resolves #3965
before

after

Checklist

[x] Added markup tests, or they don't apply here because...
[ ] Updated the changelog at CHANGES.md

Sorry, each PR will need to be it's own separate branch - including just that work - not all the other work you've done.

Sorry, each PR will need to be it's own separate branch - including just that work - not all the other work you've done.

understood,apologies ive made a new branch synced with main and made a pr please review


meta-balena-raspberry: Rename resin-extra-udev-rules

This recipe has been renamed in upstream meta-balena.
Change-type: patch
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@alexgg is this needing https://github.com/balena-os/meta-balena/pull/2765 to be merged first?

hey @floion it needs https://github.com/balena-os/meta-balena/pull/2756/

@balena-ci rebase

Rebased over https://github.com/balena-os/balena-raspberrypi/pull/941, can close once that merges.

Once again rebased over #941, can close once that merges.

@resin-jenkins retest this please

@balena-ci rebase


Fix tests README.

the directory was renamed by 27ffa0f.
also the dso feature had deprecated by e4987ad.

Signed-off-by: u5surf<EMAIL_ADDRESS>

Thanks, I have pulled a new request to remove this file. tengine DSO is deprecated. This file is created for DSO before.
link https://github.com/alibaba/tengine/pull/1669
So I closed this pr, feel free to open other pull requests if have new idea.

@chobits Thanks, reviewing. Now I have a plan to add test in the CI which we added in a several days ago. Well, I'd like to work on it.


add a ToC to the readme.

It would certainly make it easier to find "what's in the REAMDE at all"

@Pomax this can be closed as its done and released :)

haha, good point.


Adding zone disablement during deletion of the range plus one more tr…

Description

Disabling the execution of tests that SystemVMs acquire mocked public IPs, since it's braking other tests along the execution.

Types of changes

[X] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[X] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
NA
How Has This Been Tested?

The tests were executed and passed locally

ping @PaulAngus
@blueoranguran package

@blueoranguran package

@blueorangutan package

@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2441

@blueorangutan test

@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3180)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 20279 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3028-t3180-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_multipleips_per_nic.py
Intermittent failure detected: /marvin/tests/smoke/test_vpc_redundant.py
Smoke tests completed. 68 look OK, 2 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_nic_secondaryip_add_remove
Error
23.07
test_multipleips_per_nic.py

test_04_rvpc_network_garbage_collector_nics
Failure
441.25
test_vpc_redundant.py

@PaulAngus are you lgtm on this?

Yes LGTM

@borisstoyanov can you keep any @-mentions out of the description and put them in a first comment please? They'll keep coming up and end up in the merge commit message as well. tnx


[FLINK-16802][hive] Set schema info in JobConf for Hive readers

What is the purpose of the change
Some Hive readers rely on table schema for schema evolution, name mapping, etc. So we should set the schema in JobConf when creating the reader.
Brief change log

Set schema info in JobConf for Hive readers.
Add test cases.

Verifying this change
Existing and added test cases. Also manually run tests for all Hive versions.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? N/A

cc @JingsongLi and @bowenli86

@JingsongLi Thanks for reviewing. Comments addressed.


[web] Virtual Keyboard on Raspberry Pi

I am still struggling with this issue.  I saw this issue that seemed somewhat related:
https://github.com/flutter/flutter/issues/32763
So if flutter web is used on an iphone, the virtual keyboard sounds like it will come up?  I'm wondering then how does flutter know when you're in an environment with or without a physical keyboard?  If I'm running in a web browser for example on a raspberry pi, and there is no keyboard plugged in (I haven't gotten hardware to try this yet...) then does the virtual keyboard come up?
Is there a way to force flutter to think I do NOT have a physical keyboard?  If I test this on my laptop, the flutter web app works great with my physical keyboard, but I'd like to test with virtual and ultimately I want to us it on a pi with a touch screen so that may already work?

Ok, I just confirmed, if I unplug the keyboard on the pi, and just have a usb mouse, the textinput fields do NOT trigger a virtual keyboard in flutter to come up.

Hi @jdeltoft
I'm aware of this issue about "not open keyboard on TextField focus" ,
but if I understand correctly what you want to achieve
is making Flutter Web unaware of a Physical keyboard attached,
is that correct?
This is certainly something achievable,
but if your goal is to force a virtual keyboard to show up,
I'm not sure this is the correct approach.
Out ouf curiosity I've just tested flutter web app with a simple TextField
on Win10 (touchscreen + keyboard):

in tablet mode + open :  no virtual keyboard,
in tablet mode + folded :  virtual keyboard comes out;

as expected since the virtual keyboard is provided by the OS and not by Flutter.
Does make Flutter "ignore" keyboard events still match your needs
given that it might not trigger a virtual keyboard?
thank you

@iapicca Yes, I'm trying to use flutter web on a raspberry pi with a touch panel.  So it would have mouse (touch) input, but it has no keyboard attached.  Ideally I would love for the web app to act very similar to if I run my app on a tablet emulator.  I've tested on AVD tablets (800x480 so the same screen resolution) and it looks great and the flutter keyboard also looks and fits great.  But I wasn't sure yet how to trigger this to come up with my web app.
Thats interesting on win10 (surface pro?).  So it provides it's own virtual keyboard, correct?  That is a keyboard from windows OS.
So am I actually thinking of this wrong?  Is the virtual keyboard I see when I use an Android AVD actually the Android OS keyboard?  Hmmm, so is there any such keyboard if running chrome on a raspberry pi?  Perhaps not?

@jdeltoft I believe you are correct in your last assertion,
when you run Flutter on a Raspberry Pi with touch screen
will be used the virtual keyboard of the OS installed on the device.
(BTW I have a Yoga 720, not Surface Pro :) )
What OS is installed on your Raspberry Pi?
thank you

@iapicca I'm using raspbian OS on the pi, but we're launching it into "kiosk" mode where chrome launches and you see the web app.  The concern I have with the virtual keyboards I've seen on raspbian is that they look like "x windows" type of keyboards.  So those aren't probably going to show well or at all in my case.
I think what I'll have to do is try something like this:
https://pub.dev/packages/virtual_keyboard
and launch this only when I see that a text field has focus.  Not sure how feasible/viable that is to detect focus changes.  Looks like I have some homework.  :)
I will try the raspbian matchbox keyboard though just to see if it works.

We're not setup to test on Raspberry Pi, unfortunately. However, perhaps @nturgut has some ideas for you to try.

We're not setup to test on Raspberry Pi, unfortunately. However, perhaps @nturgut has some ideas for you to try.

This is a really crucial need that opens up a new dimension of IOT possibilities. We can build  Kiosk applications like Mc Donald's Self-ordering app using a low-cost device like Raspberry Pi with Flutter Web. That kind of application needs a virtual keyboard so that the users feel like using a native mobile app. Looking forward to this.
CC @eseidelGoogle

Perhaps someone with a Raspberry Pi is willing to attempt a fix? Web-specific text editing logic lives in this file: https://github.com/flutter/engine/blob/master/lib/web_ui/lib/src/engine/text_editing/text_editing.dart
Searching for browserEngine will reveal various browser-specific hacks we had to put in place for things to work uniformly across all browsers.

I think we may have our wires crossed on my original question and the need.   Sorry for this, but I'm also learning as I go on this one.  So my initial (wrong) thought was that the keyboard was coming up from flutter when I'm on Android or iOS.  But of course it's those OS's that are showing the virtual keyboard when you have a text entry widget with focus.
I think part of the confusion also comes in here from the fact that when using Safari on iOS, there was some other issues with the iOS virtual keyboard and Flutter?  I'm not yet clear on this, but assume it was when trying to use flutter web pages in safari on iOS?
Anyway, in my ideal world, flutter would have it's own virtual keyboard that you could use either instead of the OS one, or as a keyboard when you don't have one.  In my case on Raspberry Pi in Kiosk (touch screen) mode where the OS is Raspbian (Debian on pi) and the browser is Chrome, there is no virtual keyboard that ever shows up.  If I have a usb keyboard on the pi, that works, but I want to just have a touch screen.
Some things I'm wondering if they could work:

Pure flutter solution: https://pub.dev/packages/virtual_keyboard
Possible flutter solution: https://pub.dev/packages/keyboard_actions (@diegoveloper maybe you could comment?
JS solution: https://github.com/hodgef/simple-keyboard

I have NO idea yea how to add a keyboard like that last JS one.  The point of me doing flutter was partly because I've never developed in JS.  I'm an embedded C/C++ firmware developer mainly.  :)

@jdeltoft The difficulty with implementing a keyboard is only partially from writing the keyboard widget itself that's idiomatic and accessible. A big part is integration with all the operating systemy things, such as integration with the clipboard, auto-suggest, auto-correct, auto-fill. Since browsers do not provide an API for implementing custom keyboards we instead use the one provided by the OS.
I'm guessing Raspberry Pi does not have an onscreen OS keyboard? If so, then a widget-based implementation might be a good workaround, but you'd need the underlying EditableText to play along. I'm not sure if the Flutter framework has that mode though.
@goderbauer or @HansMuller might know more about this: Do we (want to) support on-screen keyboard that are implemented in the framework (like we have for context menus on some platforms)?

We currently do not have any plans to implement a keyboard in Flutter. Maybe somebody from the community would be interested in implementing a keyboard widget for use cases like this?

@yjbanov Thanks for pointing that out, I was definitely not fully aware of the complexity here.  I was starting to notice it though when I started testing out https://pub.dev/packages/virtual_keyboard.  Based on their example they just update a global string, and display it as a Text widget.  I am using some nicer looking TextFormField widgets but of course I can update the TextEditingController.text with the virtual keyboard output.  I'll try this route for now.
I was able to use animated container also to demo the keyboard coming and going.  I get a render overflow during that animation, so I'll start a new bug/question on that I think.
Here's basically the example with the animation added:
class _MyHomePageState extends State<MyHomePage> {
  // Holds the text that user typed.
  String text = '';

  // True if shift enabled.
  bool shiftEnabled = false;

  // is true will show the numeric keyboard.
  bool keyboardVisible = true;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          children: <Widget>[
            Text(
              text,
              style: Theme.of(context).textTheme.display1,
            ),
            SwitchListTile(
              title: Text(
                'Keyboard Visible = ' +
                    (keyboardVisible
                        ? 'Yes'
                        : 'No'),
              ),
              value: keyboardVisible,
              onChanged: (val) {
                setState(() {
                  keyboardVisible = val;
                });
              },
            ),
            Expanded(
              child: Container(),
            ),
            AnimatedContainer(
              duration: Duration(milliseconds: 200),
              height: keyboardVisible? 280:0,
              child:
            Container(
              color: Colors.deepPurple,
              child: VirtualKeyboard(
                  height: 300,
                  textColor: Colors.white,
                  type: VirtualKeyboardType.Numeric,
                  onKeyPress: _onKeyPress),
            ),
            ),
          ],
        ),
      ),
    );
  }

We currently do not have any plans to implement a keyboard in Flutter. Maybe somebody from the community would be interested in implementing a keyboard widget for use cases like this?

Thanks @goderbauer for the reply, as mentioned I'll try to see if I hit any blockers using that package: https://pub.dev/packages/virtual_keyboard

Just as and FYI, this is working out well for me.  One thing others might be interested in if they come across this same ticket.  I am using focus nodes to know where the cursor is, and then I wanted to debug sometimes on an actual android device so I wanted to prevent the soft keyboard from ever coming up.
This solves that.  Use the "readonly" parameter to the TextFormField.
https://github.com/flutter/flutter/issues/16863#issuecomment-522745415

@goderbauer Sorry if my question was unclear. I didn't mean that we bundle an implementation in the framework. What I meant was whether we want EditableText to allow implementations that are not tied to a built-in method channel. It is entirely possible that such a thing is already possible, and that I'm simply not aware of it.

So far it's working out well.  I'm using focus nodes to even add prev and next custom action keys to my app.  I will need to clean up some contributions back to the package after I complete this.  I wanted key outlines etc. also.

@kf6gpe removing milestones puts issues back in our triage queue? How should we retriage these issues? As of right now, we triage by assigning milestones. Issues without a milestone go back to triage.

Got the same problem. For me the keyboard is working when served as a plain PWA (directly serving out of the build dir). But when I try to use it within a website with an iframe tag which uses href="path/to/the/index.html(of FlutterWebApp) the keyboard doesn't show up anymore.

So far it's working out well. I'm using focus nodes to even add prev and next custom action keys to my app. I will need to clean up some contributions back to the package after I complete this. I wanted key outlines etc. also.

I just used an animated container to raise this keyboard up from the bottom in 300ms nicely. Love it!!

Very nice indeed!!!! How did you use the animated container?

Also you can add Raspberry Pi On Screen Keyboard With below Steps:
(1)

(2)

(3)

(4)

(5)

(6)


Compatibility tests

This PR add scripts to perform compatibility tests: run leaves against models built in different versions of third party libraries (lightgbm & xgboost for now).
See compatibility.md for results

Pull Request Test Coverage Report for Build 151

1 of 42 (2.38%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.3%) to 68.666%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mat/mat.go
0
7
0.0%

mat/mat_io.go
0
34
0.0%

Totals

Change from base Build 143:
-1.3%

Covered Lines:
1797

Relevant Lines:
2617

💛  - Coveralls


optionally turn off doclint when building with sun's jdk, and

remove some dupe declarations of plugin versions.

Merged and pushed to Apache Git repo. Thank you.


Store selected imagery dates with sample values for PlanetDaily and SecureWatch imagery types

This should be passed with the imagery attribution json blob.  If not, it should be easy to add here.


Formalize code for getting gage data

[x] Meet OSW standards for 'year complete'
[x] Review other rules from Robert Mason
[x] Once data are in hand, get into SB

make sure we capture site, lat, lon, huc, etc.

Unfortunately, hitting the 355 day standard means pulling 10k sites vs about 6k sites from NWIS.  Fortunately, I can cheat somewhat since I still have all the 6k sites downloaded from last time, and I can only download the new ones.

#30

https://www.sciencebase.gov/catalog/item/58c18c7ae4b014cc3a3d3706?groupId=JQUERY-FILE-UPLOAD-e82437ad-3cd1-4c8c-b879-aa0670dd7730
Final output on SB

Can we consider this 'closed' @wdwatkins ?

yep


Sheets Quickstart fails due to NoMethodError

When I ran Sheets API's Quickstart, I encountered the error below.
hash@hh-mbp ~/w/google-sheets-api-sample> ruby quickstart.rb
Name, Major:
Traceback (most recent call last):
quickstart.rb:48:in `<main>': undefined method `each_values' for #<Google::Apis::SheetsV4::ValueRange:0x00007fb11c1f1dd0> (NoMethodError)

I submitted CLA just a few minutes ago, and I created a PR for this issue.
I'd be glad that you merge this PR if there are no problems 🍪

Now the relevant PR was merged, so I'll close this issue. Thanks :tea:

@hashedhyphen it appears as if this issue has popped up again. The code in master is calling response.each_value again instead of response.values.each on line 51.
https://github.com/gsuitedevs/ruby-samples/blob/master/sheets/quickstart/quickstart.rb

@grant It seems this issue is caused by the commit https://github.com/gsuitedevs/ruby-samples/commit/ec561977b79c48f73c3fba77139e404251777fde#diff-63afab8a1f801a8eb06ca639724fa587
What is the purpose of that change?

I believe this was a rubocop lint error at the time of change.
Can you state the ruby version and client library version?
https://apidock.com/ruby/Hash/each_value

It looks like @grant reverted the fix in 06ee87f4f55116252ecef445970678e51f2ef3e0.
@sqrrrl - As someone that knows Ruby well, do you know what's happening here? Is the confusion here because

Likely just an accidental revert, @grant rolled the fix forward. Thanks for catching this!


Change Dropdown List appear effect

Author the user story for this feature
As a designer, I want to change the dropdown list appear effect so I can make sure that it looks more pleasing to user.

Is your feature request related to a problem? Please describe.
Can we change the dropdown appear effect? - just simply appearing with small transparency fade in/ fade out  after clicking and without moving up / down.
Describe the solution you'd like
Change appear effect to fade in/fade out without moving up/down.
Describe alternatives you've considered
Additional context

Pass animation to the Dropdown Body base widget (make configurable)


Not working?

I get three different Fingerprints for Firefox, Chromium and Tor Browser (all three with supposedly vulnerable versions according to your README file). All three manage to miscalculate the apps that are installed. Firefox reports almost every app as installed (although I don't have all the reported ones) while the other two browsers report fewer apps installed than what's present on my pc. Running Archlinux with a few typical privacy-preserving Add-Ons on Firefox and an Adblocker on Chromium.
I can send you more exact information about my setup if you're interested, but I don't want to post that publicly.
I would be interested to see what part of my setup "breaks" the detection.

Hi Max, Thanks for the feedback.
Feel free to contact me on<EMAIL_ADDRESS>Will mark it as duplicate of #5


support ubuntu 18.04

netdata_install.rb currently fails because ubuntu 18.04 seems to make use of package iproute2 instead of iproute. This PR fixes that.
Tests fail locally with the following errors:
>>>>>> Message: 3 actions failed.
>>>>>>     Converge failed on instance <general-centos-67>.  Please see .kitchen/logs/general-centos-67.log for more details
>>>>>>     Converge failed on instance <general-chef12-centos-67>.  Please see .kitchen/logs/general-chef12-centos-67.log for more details
>>>>>>     Converge failed on instance <general-chef12-fedora-25>.  Please see .kitchen/logs/general-chef12-fedora-25.log for more details

However, this seems to be the case with current master as well, so this should not be related to this PR.

@st-h Thanks for the PR.
I'll include it on the 1.0.0 release.


ctrld: init at 1.3.3

Description of changes
Homepage: https://github.com/Control-D-Inc/ctrld/

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3134

Could you add a nixos test?

How so? Do you want to test if the binary can run or the service works?

The tests are failing, both on ofborg and locally. I took it for a spin locally but didn't see anything obvious. Does the test perhaps need something in settings?

The tests are failing, both on ofborg and locally. I took it for a spin locally but didn't see anything obvious. Does the test perhaps need something in settings?

Sorry! Forgot to add the default settings.

Still getting the same error

I no longer have time/interest in adding this package, so I'll close this PR.


Many-to-Many through with Join Model

My database is designed as follows...
User has many Account through AccountUser.  AccountUser also has some properties/relationships other than the Account and User.  It also has a Role.
Fetching the Accounts for a User is no problem, but is it also possible to include the AccountUser model (and its Role, etc.) with each Account returned for a User?

Hi @offmadisonave. There are two ways to achieve this.
var User = bookshelf.Model.extend({
  tableName: 'users',
  accountUser: function() { return this.hasOne(AccountUser); },
  account: function() { return this.hasOne(Account).through(AccountUser); }
});
User.fetch({withRelated: ['accountUser.account']});

Comment edited (I pressed submit by accident).

Awesome.  Thanks so much!


FancyZones "space around windows" doesn't go to 0 on one monitor only

Microsoft PowerToys version
0.51.1
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones, FancyZones Editor
Steps to reproduce
Editing the zone layout on of three monitors. Setting "space around windows" to 0 or turning it off completely still leaves space around the windows on that monitor only. Works fine on the other 2 monitors, the windows touch on those monitors when "space around windows" is set to 0 or turned off.
built-in monitor 3000 x 2000
2nd monitor 1920 x 1080 <-- spacing around windows doesn't work
3rd monitor 5120 x 1440
See attached images

.
✔ Expected Behavior
Expectation is that when "space around windows" is turned off or set to zero that the background image on that monitor is not visible and all windows touch each other.
❌ Actual Behavior
All windows on that specific monitor have gaps around them that the background image is visible. Works fine on the other two monitors.
Other Software
No response

Can you confirm this issue is still relevant in v0.73? /needinfo

Can you confirm this issue is still relevant in v0.73? /needinfo

No, has not been a bug for a couple of releases. Not an issue on v0.73.